All of a sudden, the incoming and outgoing pstn calls started not working. When I checked the VG,I could observe everything as registered in the VG and CCM. I restarted the VG and showing the pri Lines unregistered in the VG and CCM.
After changing VG router name in the CCM issue got resolved.
The VG router name in the CCM was CS3845VG.TRV and we changed to CS3845VG.TRV.ustr.com and the issue got resolved. Since last 3-4 years, the voice gateway router is working with the present configuration in the ccm with the hostname CS3845VG.TRV.
MGCP registers based off of 'hostname' if no domain name is specified on the router. If you specify a domain name, the gateway will try to register with hostname.domainname.
What likely happend is that you recently configured a domain name on these gateways. Perhaps to configure SSH and generate the key? As a result, it changes the name the gateway will try to register to CM with. Hence, the next time the gateway needs to re-register to CM, it will fail.
The name as specified in CM should always match what shows up in the top of the 'sh ccm' output. You can get a 'debug mgcp pack' output to verify the full name the device is trying to register with.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...