 |
- Third-Party Database Updates (Optional): An OSS, BSS, or CCC updates the MPS server database with device and subscriber data.
- Device/Subscriber Data Updates: The MPS server continually updates the TFTP server database with subscriber and device data (the TFTP server monitors
MPS heartbeats on a multicast IP address in order to
synchronize their databases).
- Device Activation Request: The SIP device requests
an IP address and DHCP option information from the
DHCP server.
- DHCP Options Transfer: The DHCP server grants the
SIP device an IP address and a valid DNS server identifier.
For some SIP devices, the DHCP server also sends the device a TFTP or HTTP server name, as well as a configuration filename so that the device can request the file by name from the TFTP or HTTP server.
- Request for Configuration File: The SIP device requests the file from the TFTP or HTTP server.
- Generation of Configuration File: The TFTP or HTTP server dynamically generates a configuration file based
on the device type and subscriber-selected services. For security purposes, the device-specific encryption key
(set at the factory) is embedded in the file.
- Configuration File Download: The TFTP or HTTP server transmits the file to the SIP device. For HTTP transfers, the device places an HTTP GET request to the HTTP server, and the returned file is in XML format.
- Provisioning Status Update: If the SIP device doesn’t accept the configuration file (due to incorrect encryption or other configuration information), it notifies the TFTP server, which stores the failure status in the server logs.
|
|
|
|
|
