Can't get phones to register with CUCM through a VPN.
I'm trying to set up VoIP capabilities through a VPN to a remote site and cannot get the phones to register.
Possible relevant hardware info: The CUCM at the main site is version 7.1 The main site firewalls are ASA5585-X's running IOS 8.4.4 The remote site firewall is an ASA5520 running IOS 8.4.7
The remote site switch, a 3750E, is the DHCP provider for both phones and computers
The DHCP configuration for the phones includes the option 150 ip xxx.xxx.xxx.xxx line pointing to the IP address of the UCM.
This is how my other remote sites are set up, but they don't utilize a VPN for connectivity to the main site.
I can ping from the remote switch to the CUCM and I can ping from the CUCM to the remote phone vlan's IP address, which would infer that the issue is not a matter of non-connectivity.
When a phone is plugged in, the switch manager shows that the phone receives an IP address, but the phone does not respond to ping attempts.
Scrolling through the network configuration on the phone, the TFTP server sand other pertinent IP addresses are correct, but the phone was set up at the main site, so I don't know if it's receiving that info or if it's simply retained from the earlier configuration.
What would be the next step in tracking down the cause?
The first step would be packet captures from the phone or the switch port where the phone is connected so we see what the phone is doing. Is the phone supposed to establish VPN connection to main site or is the VPN tunnel transparent to it?
All Info from userid1run sql select * from enduser where userid='userid1'
userid selective info for multiple usersrun sql select eu.userid,eu.islocaluser,eu.status, eu.mailid, eu.directoryuri, dpc.name as ad_filter from enduser eu left join direct...
New update of Cisco Meeting Server book with Streamer and Scheduler components, the book will cover the following:certificates requirements, clustering, dial plan with call flow, WebRTC, WebBridge3, CallBridge, recorder, streamer, scheduler, NAT Traversal...
The Scheduler component was introduced as a beta feature in version 3.3. It was added as anew component that enabled Web app users to schedule meetings, modify the scheduledmeetings, and notify participants via email. From version 3.4, Scheduler is fully ...
A collection of the most important notes from different resources for Cisco CMS and vbrick integration. Live Streaming (Webcast) integration with VBrick DME allow users to watch any live streamed CMS conference anywhere inside the network from differ...