cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
611
Views
0
Helpful
6
Replies

VGs have both SCCP and MGCP - after CUCM moving - MGCP devices not wor

HillyardK
Level 1
Level 1

Hello,

We have a large number of VGs - 202, 204, and 224, that have been programmed as SCCP and MGCP.

We have moved our call managers to Cisco and since then, the devices on the SCCP protocol work fine, but all the devices on the MGCP don't work at all.

Has anyone experienced this before?  Or know what I need to add to the configuration to make the MGCP work?

6 Replies 6

What you mean by moved our call mangers to Cisco ?

what was your previous setup ?

what configuration you have on cucm and are you saying both SCCP and Mgcp protocol is configured on Same ports of vg?



Response Signature


Hi
Do you mean you moved from your / customer CUCM to Webex Calling Dedicated Instance?
If so did the partner / customer during the design stage/ ask for or point our MGCP was needed on the gateways? Please confirm if that was the case, if not open a case and ask for Cisco to open for those protocols.
Thx
ashish


Response Signature


Our CUCMs moved from our hosted manager service provider to Cisco.  It is not completely the Webex Calling Dedicated Instance.  It is still the standard 12.5 CUCM.

If so did the partner / customer during the design stage/ ask for or point our MGCP was needed on the gateways - answer no and it has been asked multiple times, and still nothing.

Hello,

Our Call Managers were hosted by a managed service provider and have now moved to Cisco.

Sorry - SCCP and MGCP are not configured on the same port - only on the same VG.
Example ports 2/0 and 2/3 are MGCP and the rest are all SCCP

DId you added VG gateways on CUCM ? Could you share VG complete config ?



Response Signature


HillyardK
Level 1
Level 1

This is the script I used:

 

config t

no sccp ccm group 1

yes

no sccp

no sccp ccm XXX.XXX.XXX.XXX identifier 1 version 7.0

no sccp ccm XXX.XXX.XXX.XXX identifier 2 version 7.0

sccp ccm XXX.XXX.XXX.XXX identifier 1 version 7.0

sccp ccm XXX.XXX.XXX.XXX identifier 2 version 7.0

sccp

no sccp

sccp ccm group 1

bind interf fas0/0

assoc ccm 1 pr 1

assoc ccm 2 pr 2

assoc ccm 3 pr 3

exit

sccp

ccm-manager redundant-host XXX.XXX.XXX.XXX

ccm-manager config server XXX.XXX.XXX.XXX XXX.XXX.XXX.XXX XXX.XXX.XXX.XXX

mgcp call-agent XXX.XXX.XXX.XXX 2427 service-type mgcp version 0.1

exit

sh run | s sccp

sh sccp

show run