MGCP E1 problem after SRST

Unanswered Question
Aug 31st, 2007


We have CM 5.0 at our center. On a remote location there is a 2811 router with one E1 port. Today there is a problem with our network, fiber connection to the remote office goes down and up sometimes. After this network problem, SRST works. But E1 port never registers with CM after connection goes up. When i restart the router E1 registers. I think there is a problem with MGCP after SRST.

MGCP related Router config below:

controller E1 0/2/0

framing NO-CRC4

pri-group timeslots 1-26 service mgcp

interface Serial0/2/0:15

no ip address

encapsulation hdlc

isdn switch-type primary-net5

isdn incoming-voice voice

no cdp enable

ccm-manager fallback-mgcp

ccm-manager redundant-host CM-MERTER CM-SARACHANE

ccm-manager mgcp

ccm-manager music-on-hold

ccm-manager config server

ccm-manager config



mgcp call-agent CM-AKOM 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

no mgcp explicit hookstate

mgcp rtp payload-type g726r16 static


mgcp profile default


secondary-dialtone 0

max-conferences 8 gain -6

transfer-system full-consult

ip source-address port 2000

max-ephones 32

max-dn 32

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Majdi Harb Fri, 08/31/2007 - 07:01

Hi yatisspor,

i think you missed one important command under interface Serial0/2/0:15

this command is

(isdn bind-l3 ccm-manager)

This command enables ISDN to backhaul Q.931. The Layer 3 information (Q.931 and above) is transported over TCP to the MGCP call agent which is Cisco CallManager in this case.

The isdn bind-l3 ccm-manager command shown under interface Serial1/0:15 is available only after you add the service mgcp keywords to the PRI group definition. If the command is unknown when you try to configure it, look at the controller to ensure that the PRI group is defined correctly.




This Discussion