Comments on: Cisco MGCP Gateway PRI D-Channel Fun

By: Joe

Joe — Tue, 11 Jan 2011 23:43:37 +0000

Hi Brandon - you’re welcome. I didn’t find it on Google so figured I could post it here… Funny thing - I had this happen yesterday. The PRI was the culprit this time, not the data line.

Thankfully I’ve moved most of my voice gateways to h.323 which doesn’t seem to be as picky with connections like MGCP. Never once have I had to reset h.323!

By: Brandon

Brandon — Tue, 11 Jan 2011 23:35:38 +0000

Just saved my butt!

Thanks for documenting I hate that its so hard to find good usable documentation on cisco topics.

I hope we all can take the time and document like you did!

By: Martin F.

Martin F. — Tue, 22 Dec 2009 10:18:39 +0000

Hi, our problem was fixed with this help also. A colleague used it.
What I want to add is that I found this same issue when doing a save of the config while in SRST Mode.
Best thanks

By: Hariharan.S

Hariharan.S — Tue, 31 Mar 2009 05:27:41 +0000

Hi All,

This is a very good post, i faced the same problem. Today morning my Wan link bounced , due to that it started working in SRST and the incoming calls were working but outgoing calls were not working.

While i look into config, i found that the l3 bind id missing form the router. ONce i included the command, i am able to make outbound calls and incoming calls are also working fine.

Very good post. Needs to be appreciated. Thanks to google !! which puts this in the first page on its serach link.

By: Joe

Joe — Mon, 09 Mar 2009 22:47:23 +0000

Dennis, I agree that SRST leaves a lot to be desired. My biggest gripe is how it cuts all active phone calls offline - which admittedly is a problem with MGCP. One of these days I’ll migrate all the voice gateways to h.323 to cut that out.

Just imagine if when an ethernet interface goes down it puts “shutdown” into the config - I’m sure that they would fix that real quick!

By: Dennis Weikel

Dennis Weikel — Mon, 09 Mar 2009 22:35:04 +0000

Thanks for this phenominal post. I found this post after resolving the issue with Cisco but wanted to troublshoot why this happened.

In my case the power went down causing the router to go into SRST mode.

SRST removes the command binding the interface to Call Manager.

The Cisco tech indicated that the command gets placed into the interface config after it registers with Call Manager.

Why does rebooting the router not resolve the issue? You would think that rebooting the router would register the interface and thus issue the bind command.

I’ve heard Avaya proponents point out that SRST mode is lacking failover features. If placing the router into SRST mode forces someone to perform manual steps in order to bring the system out of this mode then I would consider this to be lacking failover features.

By: Jacob

Jacob — Fri, 06 Mar 2009 13:32:16 +0000

Thank you! This solved my problem as well!

By: Stephen Macintosh

Stephen Macintosh — Mon, 17 Nov 2008 14:18:01 +0000

Wow, just browsed through pushkar bhatkoti ’s blog and there are a tons of informations.
He is CCIE certified in Voice. Very few people have this cert in the world.
pushkarbhatkoti.wordpress.com

His tips are great for CCIE labs. I am following his lab game plan too.

Stephen
Canada

By: Tom

Tom — Sat, 11 Oct 2008 14:17:20 +0000

Thanks pushkar for your help. Your solution really works and now I can have some relaxation.
I googled on your name and hit your blog too and I think you are more professional man then I thought.

pushkarbhatkoti.wordpress.com

keep it up and thanks for great share.

Tom from Iceland.

By: Brian

Brian — Sat, 11 Oct 2008 01:41:51 +0000

Thank You, Thank you, Thank You! Fix my problem too.