Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

Inbound call on FXO fail - hit pots dial-peer for PRI port. MGCP.

Having issue with 12.3(7)T on 1760

MGCP w/CCM 4.02a

On inbound calls to analog FXO lines, the call rings once and then busy. The calls work fine as long as we don't have dial-peer in router for PRI port which is for fallback mode.

This is what is 'show call hist voice brief':

1328 : 278 10488200ms.244 +-1 +10260 pid:1109 Answer 1234567890

dur 00:00:00 tx:0/0 rx:0/0 2C (no requested circuit (44))

Telephony 3/0 (278) [3/0] tx:0/0/0ms None noise:0dBm acom:0dBm

Notice the pid is of dial-peer with pri port which has direct-inward-dial.. so it should not be hitting this at all.

CONFIG for involved dial-peers:

dial-peer voice 999130 pots

application mgcpapp

port 3/0

dial-peer voice 1109 pots

destination-pattern 9[2-9]......

direct-inward-dial

port 1/0:23

forward-digits 7

4 REPLIES
New Member

Re: Inbound call on FXO fail - hit pots dial-peer for PRI port.

Is the FXO port correctly registered in CM?

Re: Inbound call on FXO fail - hit pots dial-peer for PRI port.

Also does this work properly if you reconfigure the gateway in h323 mode ?

Silver

Re: Inbound call on FXO fail - hit pots dial-peer for PRI port.

I have seen this sort of behaviour if you let the fallback peers appear earlier in the config than the mgcp peers, but when you remove them and add them back in, they should go to the bottom of the list and not interfere. It is also very strange that it picks the wrong peer, but knows the right port number..

Mary Beth

Silver

Re: Inbound call on FXO fail - hit pots dial-peer for PRI port.

Here is the little note that specifies that you should do the mgcp peers first, I don't remember ever actually seeing this declared before, but we run into the problem a lot lately:

Note If the ccm-manager config command is enabled and you separate the MGCP and H.323 dial peers under different tags, make sure that the MGCP dial peers are configured before the H.323 dial peers.

http://www.cisco.com/en/US/products/ps6441/products_configuration_guide_chapter09186a00805583bd.html#wp1068083

Mary Beth

439
Views
0
Helpful
4
Replies
CreatePlease login to create content