Incoming calls not working in SRST mode

[martin.franklyn]

Hello,

I am getting a problem with incoming calls in SRST mode.The only way I get incoming calls to work in SRST mode is that I have to shutdown all the following dial-peers which was automatically created.

dial-peer voice 999000 pots
 service mgcpapp
 port 0/0/0

 shutdown
 
dial-peer voice 999001 pots
 service mgcpapp
 port 0/0/1

 shutdown

voice-port 0/0/0
 supervisory disconnect dualtone mid-call
 timeouts call-disconnect 5
 timeouts wait-release 5
 timing hookflash-out 50
 timing guard-out 1000
 connection plar opx 21
 caller-id enable
!
voice-port 0/0/1
 supervisory disconnect dualtone mid-call
 timeouts call-disconnect 5
 timeouts wait-release 5
 timing hookflash-out 50
 timing guard-out 1000
 connection plar opx 21
 caller-id enable

dial-peer voice 868 pots
 service mgcpapp
 incoming called-number .
 direct-inward-dial
 port 0/0/0
!
dial-peer voice 869 pots
 service mgcpapp
 incoming called-number .
 direct-inward-dial
 port 0/0/1

I did this because when I did a debug I realized that the incoming call was using one of the above dial-peer and not using the dial-peer that was created for incoming calls. The problem is when I shutdown these dial-peers the ports do not work in normal mode.

Any ideas?

Thanks in advance,

Martin

[Brandon Buffin]

Couple of things:

1. Do you have MGCP fallback configured, such as:

R(config)#application
R(config-app)#global
R(config-app-global)#service alternate Default

2. You will need destination patterns on your POTS dial peers for when MGCP fallback is active:

dial-peer voice 999000 pots
 service mgcpapp
 destination-pattern 9T
 port 0/0/0

Brandon

[Dennis Mink]

Martin,

rip the service mgcpapp command off your dial peers, and only configure the mgcp global commands:

mgcp
mgcp call-agent 1.1.1.1 service-type mgcp version 0.1
mgcp rtp unreachable timeout 1000 action notify
mgcp modem passthrough voip mode nse
mgcp package-capability rtp-package
mgcp package-capability sst-package
mgcp package-capability pre-package
no mgcp package-capability res-package
no mgcp timer receive-rtcp
mgcp sdp simple
!
mgcp profile default

the dial-peer 869 should then take over as the incoming dial-peer.

the thing you will have to remember is that in a fail over scenario, you will need an independent dial plan on your VGW. a minumum of an inbound dial-peer and an outbound for PSTN calls, like the 9T pattern that Brandon suggested.

[martin.franklyn]

Hi Guys,

I will try these suggestions when I go back to the customer's site. Thanks for replying.

Martin.