New Integration for ISR 4300 with CUCM using MGCP

[chandru_bbc]

Hi

I am deploying a site in the same CUCM cluster. Integrating ISR4300 router and FXO module for analog lines. The router is configured as MGCP protocol and got registered with the CUCM. Connected the analog lines t FXO module. Doing a test call to the number, getting the announcement as "call cannot be completed as dialed, Please confirm your directory or contact administrator. This is a recording followed by fast busy signal". Whenever I do make a call, checking the sh voice port summary, showing the particular FXO port up. But the calls are not working.

Could you please provide me a checklist for CUCM configuration to get this analog lines working? Let me know what are the things to be configured in CUCM?

-Chandru

[TechLvr]

Per the details your provided, your FXO card seems to be correctly registered to the CUCM via MGCP. 

"Call cannot be completed as dialed" usually means the number that you dialed did not match any patterns, or the CSS of the calling device does not have access to the partition of the matching pattern. 

Now, did you create a route pattern and point it to your MGCP gateway in CUCM?
Does the CSS of the calling phone have access to partition of route pattern?

Lastly, make sure you set the route pattern to send the correct number of digits to the FXO card/Telco.

[Nithin Eluvathingal]

You must configure a plar for the calls to work by  mentioning  the attendee DN on MGCP gateway configuration page.

And make sure the gateway has CSS selected which can access the DN which is configured as Attendee..

MGCP for FXo is not much recommend. use H323/SIP instead.

Note- Cisco has announced sun setting for H323 so better to move to SIP.

voice-port 0/0

      connection plar opx <<Extension to be ringed>>

Add dial-peer to CUCM

2.12.0.0

2.12.0.0

[Roger Kallberg]

As H.323 is deprecated in later versions of IOS on the ISR4K platform I would recommend to use SIP instead.

[Nithin Eluvathingal]

Yes that correct. Aper the guides , No support for H.323 features will be provided from IOS XE release Bengaluru 17.6.1 onwards.

But i have customers who are in 17.6.3a which are using H323.

 

2.12.0.0

[Roger Kallberg]

I would recommend you to get these customers switched over to SIP. It's an quite easy process as most configuration stays the same.

[Nithin Eluvathingal]

Yes we are in process of moving them.. 

[TechLvr]

@chandru_bbc 
If you are having trouble with outbound calls follow the steps that I provided in my previous post. I assume this is the case because the announcement you referenced in your post is typically one that is played by the CUCM annunciator on failed outbound calls. 

If you are having trouble with inbound calls, follow the steps provide by @Nithin Eluvathingal. 

Also, I agree with @Roger Kallberg on using SIP as it the most standard protocol with a lot of flexibility. You get almost get no flexibility with MGCP. 

[chandru_bbc]

Hi All

Thank you so much for your answers and got it worked as per your suggestions.

regards

BBC