MGCP ccm fallback

Answered Question
May 10th, 2007
User Badges:

Having an issue related to MGCP when phones are in SRST mode.


Phones register OK with SRST

Phones can call each other OK

No calls can be made in and out of the site via the E1


Under normal call manager mode it works fine.


Config is below:


ccm-manager fallback-mgcp

ccm-manager mgcp

ccm-manager music-on-hold

ccm-manager config server x.x.x.x

ccm-manager config


mgcp

mgcp call-agent xxxxxxxx 2427 service-type mgcp version 0.1

mgcp dtmf-relay voip codec all mode out-of-band

mgcp rtp unreachable timeout 1000 action notify

mgcp modem passthrough voip mode nse

mgcp package-capability rtp-package

no mgcp package-capability res-package

mgcp package-capability sst-package

no mgcp package-capability fxr-package

mgcp package-capability pre-package

no mgcp timer receive-rtcp

mgcp sdp simple

mgcp rtp payload-type g726r16 static

mgcp bind control source-interface Loopback0

mgcp bind media source-interface Loopback0

!

mgcp profile default


call-manager-fallback

secondary-dialtone 9

max-conferences 8 gain -6

transfer-system full-consult

timeouts interdigit 3

ip source-address x.x.x.x port 2000

max-ephones 96

max-dn 192

application default

keepalive 10

voicemail xxxx

time-format 24


Thanks in Advance to any suiggestions,


The answer is that it wont pull any info from callmanager.


The MGCP is master/slave relationship between gateway and CCM. Once lose connectivity between gateway and CCM, then MGCP will also lose the funtionality.


So you have add dial-peer for H.323.


You can just copy and paste the command below:


dial-peer voice 123 pots

incoming called-number .

direct-inward-dial

port 1/0:23 --> please change the port number T1/E1 PRI, BRI or FXO whatever you have

!

dial-peer voice 911 pots

destination-pattern 911

port 1/0:23

forward-digits 3

!

dial-peer voice 9911 pots

destination-pattern 9911

port 1/0:23

forward-digits 3

!

dial-peer voice 7 pots

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

port 1/0:23

forward-digits 7

!

dial-peer voice 11 pots

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

port 1/0:23

forward-digits 11

!

dial-peer voice 9011 pots

destination-pattern 9011T

port 1/0:23

prefix 011



Please rate the helpful post.


Ken

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3.2 (6 ratings)
Loading.
Correct Answer

During SRST kick in, it will change from MGCP to H.323 mode. I dont see any dial-peer you post at the forum.


Therefore, you need dial-peer in order to make calls and recieve calls.


Here is the example:


http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00807f8b31.shtml


If you go through the above, you will see dial-peer voice for incoming call, 911, local, LD and INTL.


Please rate a helpful post.


Ken

bartymil123 Thu, 05/10/2007 - 18:08
User Badges:

Thanks for the response Ken,


I thought MGCP takes care of all of the setup of these once the gateway loses its call manager connection, doesn't it pull the info from Call Manager?





Correct Answer

The answer is that it wont pull any info from callmanager.


The MGCP is master/slave relationship between gateway and CCM. Once lose connectivity between gateway and CCM, then MGCP will also lose the funtionality.


So you have add dial-peer for H.323.


You can just copy and paste the command below:


dial-peer voice 123 pots

incoming called-number .

direct-inward-dial

port 1/0:23 --> please change the port number T1/E1 PRI, BRI or FXO whatever you have

!

dial-peer voice 911 pots

destination-pattern 911

port 1/0:23

forward-digits 3

!

dial-peer voice 9911 pots

destination-pattern 9911

port 1/0:23

forward-digits 3

!

dial-peer voice 7 pots

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

port 1/0:23

forward-digits 7

!

dial-peer voice 11 pots

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

port 1/0:23

forward-digits 11

!

dial-peer voice 9011 pots

destination-pattern 9011T

port 1/0:23

prefix 011



Please rate the helpful post.


Ken

bartymil123 Sat, 05/12/2007 - 15:03
User Badges:

Hi,

I have added the following:

dial-peer voice 4 pots

destination-pattern 9T

port 0/0/0:15

!

dial-peer voice 1 pots

incoming called-number .

direct-inward-dial

port 0/0/0:15


If I now try and dial in to an extenstion will in srst mode I get:


beep beep beep, a few times then a message that the call can't be connected



Hi bartymil123,

Did you find a solution to your issue? I have a very similar issue that when my callmanager 4.13 is connected it works fine, but can not dial out when in SRST mode. I do get incoming calls however.


When I dial out in SRST mode, I get an error message to the effect of "I am sorry, the number your dialed can not be completed in your area.." voice ccapi and q931 debug show the call matched the dial-peer and sent out to the ISDN.


Here is the kicker, If I made the call to my cell phone from inside the router with the csim command, the call got out and rang my cellphone. The debug looks the same in both case.


I was on the phone with TAC but they had no clues yet.


It is very strange...


bartymil123 Sun, 07/01/2007 - 17:37
User Badges:

The problem was solved, we did not have any translation patterns configured to allow calls to go from extension to full number and visversa incoming and outgoing


It is working now with the addition of translation patterns and dial peers


sr2290723 Thu, 05/10/2007 - 21:26
User Badges:

I think you miss the dial-peer configuration. When fallback to SRST, the voice gateway will use H323 protocol. That means that you have to configure dial-peer to direct outgoing call. For example :


dial-peer voice 1 pots

destination-pattern 9T

port 1/0:15


dgahm Thu, 05/10/2007 - 22:19
User Badges:
  • Blue, 1500 points or more

In addition to ccm-manager fallback-mgcp, be sure you have the call application alternate command.


http://www.cisco.com/en/US/products/sw/iosswrel/ps5207/products_configuration_guide_chapter09186a0080393a3c.html#wp1445728


MGCP Gateways and SRST


MGCP fallback is a different feature than SRST and, when configured as an individual feature, can be used by a PSTN gateway. To use SRST as your fallback mode on an MGCP gateway, SRST and MGCP fallback must both be configured on the same gateway. MGCP and SRST have had the capability to be configured on the same gateway since Cisco IOS Release 12.2(11)T.


To make outbound calls while in SRST mode on your MGCP gateway, two fallback commands must be configured on the MGCP gateway. These two commands allow SRST to assume control over the voice port and over call processing on the MGCP gateway. With Cisco IOS releases prior to 12.3(14)T, the two commands are the ccm-manager fallback-mgcp and call application alternate commands. With Cisco IOS releases after 12.3(14)T, the ccm-manager fallback-mgcp and service commands must be configured. A complete configuration for these commands is shown in the "Enabling SRST on an MGCP Gateway" section on page 34.


Note The commands listed above are ineffective unless both commands are configured. For instance, your configuration will not work if you only configure the ccm-manager fallback-mgcp command.


Please rate helpful posts.


Dave

Actions

This Discussion