- Oct 11, 2000
- 56,336
- 11
- 0
While I'm waiting for my hardware to arrive, I built the following network in GNS3.
R1 and R3 are running CME. R1 handles the call processing for the phones to the left of the serial link. R3 hands the call processing for the phones on the right of the serial link. R1 and R3 have been configured as VoIP dial peers. Auto-registration is enabled on both but auto-extension isn't. All the other routers are just routers. EIGRP has been configured on all routers and have routes to all subnets in the network.
In the VMnetX networks, there are virtual machines connected and running Cisco IP Communicator (IPC). All IPCs can call each other. When I move an IPC from one subnet to another subnet that is being managed by the same CME, e.g. VMnet1 to VMnet3, it works as intended. The phone extension remains the same even though a different IP address but in the correct range is assigned to the phone, etc.
But if I move an IPC from a subnet on the left to the one on the right, or vice versa, then the IPC fails. And it fails because during the phone boot process, the IPC gets an IP address from the local DHCP server and also the option 150 that tells it to download the XMLDefault.cnf.xml from the local CME which doesn't have the peer CME listed in the configuration.
What are my options? Do I just have to create a VPN back to the managing CME? Add the other CME IP address to the configuration file so that when registration fails with the local CME, it tries the second one?
R1 and R3 are running CME. R1 handles the call processing for the phones to the left of the serial link. R3 hands the call processing for the phones on the right of the serial link. R1 and R3 have been configured as VoIP dial peers. Auto-registration is enabled on both but auto-extension isn't. All the other routers are just routers. EIGRP has been configured on all routers and have routes to all subnets in the network.
In the VMnetX networks, there are virtual machines connected and running Cisco IP Communicator (IPC). All IPCs can call each other. When I move an IPC from one subnet to another subnet that is being managed by the same CME, e.g. VMnet1 to VMnet3, it works as intended. The phone extension remains the same even though a different IP address but in the correct range is assigned to the phone, etc.
But if I move an IPC from a subnet on the left to the one on the right, or vice versa, then the IPC fails. And it fails because during the phone boot process, the IPC gets an IP address from the local DHCP server and also the option 150 that tells it to download the XMLDefault.cnf.xml from the local CME which doesn't have the peer CME listed in the configuration.
What are my options? Do I just have to create a VPN back to the managing CME? Add the other CME IP address to the configuration file so that when registration fails with the local CME, it tries the second one?
Last edited:
Facebook
Twitter