 |
- Device Action Request: The MTA requests an IP address and DHCP options from the
DHCP server.
- DHCP Options Transfer: The DHCP
server responds with an IP address,
MPS server FQDN, other network parameters, and if using Secure PacketCable, the KDC server realm.
Note: A DNS server resolves MPS
and KDC FQDNs into IP addresses (after
resolving the KDC server realm into an FQDN).
- Optional PacketCable SNMPv3 Security (Secure PacketCable):
- The KDC server first provides
the MTA with Kerberos session tickets.
- Using Kerberos protocol, the
MTA requests an SNMPv3 subkey from the MPS server.
The MPS server generates the SNMPv3 subkey, sends the subkey
to the MTA, and adds
the MTA to the
MPS server database.
- Enrollment Request: The MTA
requests provisioning enrollment via an SNMPv2 Enrollment Inform, or
SNMPv3 for Secure PacketCable.
- Generation of Configuration File:
The MPS server dynamically generates
the MTA configuration file using the default voice settings, CMTS (identified
in the MTA’s lease information), and
the MTA-specific voice settings (if any).
- The MPS server retrieves the MTA’s default voice settings
and line properties from the
MTA using an SNMPv2 or SNMPv3 GET request.
- The MPS server asks the DHCP server for the MTA’s lease information.
- If the MPS is integrated with a customer care center, it queries the customer care center for voice settings pre-configured for the MTA at the factory.
- Configuration File Upload: The MPS server uploads the file to the TFTP server.
- Configuration File Location: The MPS server sends the location and name of the configuration file to the MTA.
- Request for Configuration File: The MTA requests its file from the TFTP server.
- Configuration File Download: The TFTP server downloads the file to the MTA.
- Provisioning Status Update: The MTA sends an SNMPv2 or SNMPv3 status update to the MPS server.
|
|
|
|
|
