I am running Call Manager 512 using MGCP for my gateways. Recently i bought a 2911 voice gateway, but have to configure it as a h323 gateway because, the router type is not available under the MGCP configuration. I add the 2911 gateway to a route group and I try to add this to an existing route list that contains my MGCP gateways. When I try and add the the h323 VG route group to the existing route list, it does not show up as an available device.
If I add a new route list, the 3 route groups show up, but if I add the h323 VG route group as the first route group in the route list, the MGCP route groups disappears. It looks like MGCP and h323 can not coexist in the same route list in this CCM version. Has anyone come across this issue before?.
Route List cannot contain Q.SIG (MGCP) and non-Q.SIG(H323) Route Groups
Route List cannot contain Q.SIG (MGCP) and non-Q.SIG(H323) Route Groups.
Conditions: 3.3 4.0 Route Group A contains an H.323 gateway and Route Group B contains an MGCP gateway assigned a switch type of PRI ISO QSIG T1. Route Group A and Route Route Group B need to be in the same Route List.
Symptoms: Unable to add a non-Q.SIG and Q.SIG route group in a Route List.
This helped me a lot! I had 80 circuits - E1 Pri-ISDN - configured with MGCP (QSIG). I wanted to add in one Route List a Route Grupo with a SIP trunk and this was not working because SIP trunks are always (non-Qsig) After reading your comment, I set the all MGCP (non-QSIG) and I was able to insert the route group MGCP and route group SIP on the same Route List.
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: email@example.com 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 ...