Cisco MGCP Gateway PRI D-Channel Fun
A lot of my sites at work have Cisco Call Manager controlled mgcp gateway routers, which are connected to the Call Manager via WAN connection. This morning the WAN connection went down for over an hour at one of the sites, causing the router to kick into SRST mode which meant calls still came through. Life was good - fallback working.
After the telco fixed the issue with WAN connection, phones stopped working. No calls in, no calls out. This is what I was seeing in syslog (or by doing ‘debug isdn q921′):
*Jul 3 20:50:50.074: ISDN Se0/1/0:23 Q921: User RX < - SABMEp sapi=0 tei=0
*Jul 3 20:50:50.074: ISDN Se0/1/0:23 **ERROR**: L2IF_SendPkt: idb is NULL
*Jul 3 20:50:50.074: ISDN Se0/1/0:23 **ERROR**: process_rxdata:L2IF_SendPkt Failed
Looked to me like a layer 2 isdn issue, which usually (in my experience) means issue with your provider.
After many hours troubleshooting, an IOS upgrade, etc finally opened TAC case and this is what he found. Sometimes when an MGCP gateway loses connection to call manager, it removes a line in the config that tells the ISDN to be controlled by Call Manager. The router was registering, but since the line was missing it wasn’t bringing the interface up.
This is what you want to look for:
interface Serial0/1/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn incoming-voice voice
isdn bind-l3 ccm-manager
no cdp enable
Go into the isdn sub-interface and make sure that the ‘isdn bind-l3 ccm-manager’ is there. That’s the line that was removed. Without it the router wasn’t giving control to Call Manager so the interface wasn’t coming up. After something like this you usually feel dumb that it was something so simple. It happens to the best of us it seems.
Hope this helps anyone searching Google for answer, I couldn’t find any pertaining to my problem so here it is!
isdn bind-l3 ccm-manager
As soon as I started reading the conundrum in your post, I immediately thought this. Good problem solving. hahahahah.
Lordy, lordy, I wish I knew just what you were talking about. It was an impressive bunch of words, and I’m so happy your problem was solved. Gotta go sling some mud. Love you!
Just wanted to drop you a line to let you know that this post helped me solve an issue I was having. Thanks!
Hi folks,
i had the same issue this morning ! We lost the layer 2 ISDN on some gateways ISR 2851.
We had the line command isdn bind-l3 ccm-manager on it and the layer 2 was getting up.
On some others gateways, the layer 2 isdn q921 was up(isdn bind-l3 ccm-manager was on running config) but the incoming calls were dropped.
Just removing and adding the line command isdn bind-l3 ccm-manager on it, the incoming calls were coming back good !
I don’t understand the behaviour ?? !!!
In my opinion, in the normal behaviour, the layer 2 q921 is operating by the gateways and the q931 is doing by the Call Manager.
Do you more about what happens ?
isdn bind-l3 ccm-manager, called MGCP backhaul. basically it put all Layer 2 isdn information into layer 3 packets and transfer to the Callmanager via IP network. Without this command, Callmanager cannot receive the layer 2 q921 information. that is why cause the layer 2 problem.
This post was a life-saver! Thank you thank you!
Cool stuff. Thank you for this. Lots of help.
Do you know how to fix the problem definitely ? and how this error comes from ?
My Case is different folks,
I don’t have any L3 backhauling command in D channel but it still shows in ccm that gw is registered:
Current configuration : 244 bytes
!
interface Serial0/2/0:23
description — d channel for isdn pri —
no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn incoming-voice voice
isdn bchan-number-order ascending
isdn outgoing display-ie
no cdp enable
end
But I am still getting those errors.
siteb#c
*Dec 24 04:16:32.403: ISDN Se0/2/0:23 **ERROR**: L2IF_SendPkt: idb is NULL
*Dec 24 04:16:32.407: ISDN Se0/2/0:23 **ERROR**: process_rxdata:L2IF_SendPkt Failed
*Dec 24 04:16:33.403: ISDN Se0/2/0:23 **ERROR**: L2IF_SendPkt: idb is NULL
*Dec 24 04:16:33.403: ISDN Se0/2/0:23 **ERROR**: process_rxdata:L2IF_SendPkt Failed
siteb#show ccm hosts
*Dec 24 04:16:34.403: ISDN Se0/2/0:23 **ERROR**: L2IF_SendPkt: idb is NULL
*Dec 24 04:16:34.403: ISDN Se0/2/0:23 **ERROR**: process_rxdata:L2IF_SendPkt Failed
siteb#show ccm hosts
MGCP Domain Name: siteb
Priority Status Host
============================================================
Primary Registered 142.2.64.12
First Backup Backup Ready 142.2.64.11
Second Backup None
siteb#
*Dec 24 04:16:35.403: ISDN Se0/2/0:23 **ERROR**: L2IF_SendPkt: idb is NULL
*Dec 24 04:16:35.403: ISDN Se0/2/0:23 **ERROR**: process_rxdata:L2IF_SendPkt Failed
siteb#
*Dec 24 04:
But as soon as I put the command back into the D channel config, everything came to normal:
b#
siteb#sh run int s0/2/0:23
Building configuration…
Current configuration : 270 bytes
!
interface Serial0/2/0:23
description — d channel for isdn pri —
no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn incoming-voice voice
isdn bind-l3 ccm-manager
isdn bchan-number-order ascending
isdn outgoing display-ie
no cdp enable
end
siteb#
siteb#
siteb(config)#
*Dec 24 04:18:38.707: %ISDN-6-LAYER2UP: Layer 2 for Interface Se0/2/0:23, TEI 0 changed to up
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/DPM/dp_handle_isdn_is_signalling_channel_up:
idb 0×46DC3A8C status 1
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/DPM/dp_check_and_notify_all_dp_state:
Peer=1 Previous state=0 Current state=0
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
— controller id=0, shelf=0, slot=0, cdb=0×46B54AE8
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
cdb->cdb_state=4
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
ISDN Interface Layer1 and Layer2 are both up, idb=0×46DC3A8C
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/DPM/dp_check_and_notify_all_dp_state:
Peer=911 Previous state=0 Current state=1
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/
siteb(config)#DPM/dpSendTransitionEvent:
sending DP_CB_UP event
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/DPM/dp_check_and_notify_all_dp_state:
Peer=9911 Previous state=0 Current state=0
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
— controller id=0, shelf=0, slot=0, cdb=0×46B54AE8
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
cdb->cdb_state=4
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
ISDN Interface Layer1 and Layer2 are both up, idb=0×46DC3A8C
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/DPM/dp_check_and_notify_all_dp_state:
Peer=7 Previous state=0 Current state=1
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/DPM/dpSendTransitionEvent:
sending DP_CB_UP event
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
*Dec 24 04:18:38.707: //-1/xxx
siteb(config)#xxxxxxxxx/DPM/dpCheckTerminationStatus:
— controller id=0, shelf=0, slot=0, cdb=0×46B54AE8
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
cdb->cdb_state=4
*Dec 24 04:18:38.707: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
ISDN Interface Layer1 and Layer2 are both up, idb=0×46DC3A8C
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dp_check_and_notify_all_dp_state:
Peer=11 Previous state=0 Current state=1
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dpSendTransitionEvent:
sending DP_CB_UP event
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dp_check_and_notify_all_dp_state:
Peer=9011 Previous state=0 Current state=0
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
— controller id=0, shelf=0, slot=0, cdb=0×46B54AE8
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dpCheckTermi
siteb(config)#
siteb(config)#
siteb(config)#enationStatus:
cdb->cdb_state=4
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
ISDN Interface Layer1 and Layer2 are both up, idb=0×46DC3A8C
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dp_check_and_notify_all_dp_state:
Peer=4000 Previous state=0 Current state=1
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dpSendTransitionEvent:
sending DP_CB_UP event
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
— controller id=0, shelf=0, slot=0, cdb=0×46B54AE8
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
cdb->cdb_state=4
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
ISDN Interface Layer1 and Layer2 are both up, idb=0×46DC3A8C
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dp_check_and_notify_all_dp_state:
Peer=2000 Previous state=0 Current state=1
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dpSendTr
siteb(config)#exit
siteb#
siteb#
siteb#ansitionEvent:
sending DP_CB_UP event
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
— controller id=0, shelf=0, slot=0, cdb=0×46B54AE8
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
cdb->cdb_state=4
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
ISDN Interface Layer1 and Layer2 are both up, idb=0×46DC3A8C
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dp_check_and_notify_all_dp_state:
Peer=3002 Previous state=0 Current state=1
*Dec 24 04:18:38.711: //-1/xxxxxxxxxxxx/DPM/dpSendTransitionEvent:
sending DP_CB_UP event
*Dec 24 04:18:38.715: //-1/xxxxxxxxxxxx/DPM/dp_handle_isdn_is_signalling_channel_up:
idb 0×46DC3A8C status 1
*Dec 24 04:18:38.715: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
*Dec 24 04:18:38.715: //-1/xxxxxxxxxxxx/DPM/dp_check_and_notify_all_dp_state:
Peer=1 Previous state=0 Current state=0
siteb#
siteb#
*Dec 24 04:18:38.715: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
*Dec 24 04:18:38.715: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
— controller id=0, shelf=0, slot=0, cdb=0×46B54AE8
*Dec 24 04:18:38.715: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
cdb->cdb_state=4
*Dec 24 04:18:38.715: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
ISDN Interface Layer1 and Layer2 are both up, idb=0×46DC3A8C
*Dec 24 04:18:38.715: //-1/xxxxxxxxxxxx/DPM/dp_check_and_notify_all_dp_state:
Peer=911 Previous state=1 Current state=1
*Dec 24 04:18:38.715: //-1/xxxxxxxxxxxx/DPM/dpSendTransitionEvent:
sending 0xFFFFFFFF event
*Dec 24 04:18:38.715: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dp_check_and_notify_all_dp_state:
Peer=9911 Previous state=0 Current state=0
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
—
siteb#controller id=0, shelf=0, slot=0, cdb=0×46B54AE8
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
cdb->cdb_state=4
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
ISDN Interface Layer1 and Layer2 are both up, idb=0×46DC3A8C
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dp_check_and_notify_all_dp_state:
Peer=7 Previous state=1 Current state=1
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpSendTransitionEvent:
sending 0xFFFFFFFF event
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
— controller id=0, shelf=0, slot=0, cdb=0×46B54AE8
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
cdb->cdb_state=4
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
ISDN Interface Layer1 and Layer2 are both up, idb=0×46DC3A8C
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dp_check_and_notify_all_dp_st
siteb#ate:
Peer=11 Previous state=1 Current state=1
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpSendTransitionEvent:
sending 0xFFFFFFFF event
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dp_check_and_notify_all_dp_state:
Peer=9011 Previous state=0 Current state=0
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
— controller id=0, shelf=0, slot=0, cdb=0×46B54AE8
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
cdb->cdb_state=4
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
ISDN Interface Layer1 and Layer2 are both up, idb=0×46DC3A8C
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dp_check_and_notify_all_dp_state:
Peer=4000 Previous state=1 Current state=1
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpSendTransitionEvent:
sending 0xFFFFFFFF event
*De
siteb#c 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
— controller id=0, shelf=0, slot=0, cdb=0×46B54AE8
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
cdb->cdb_state=4
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
ISDN Interface Layer1 and Layer2 are both up, idb=0×46DC3A8C
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dp_check_and_notify_all_dp_state:
Peer=2000 Previous state=1 Current state=1
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpSendTransitionEvent:
sending 0xFFFFFFFF event
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
— controller id=0, shelf=0, slot=0, cdb=0×46B54AE8
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminationStatus:
cdb->cdb_state=4
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpCheckTerminat
siteb#ionStatus:
ISDN Interface Layer1 and Layer2 are both up, idb=0×46DC3A8C
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dp_check_and_notify_all_dp_state:
Peer=3002 Previous state=1 Current state=1
*Dec 24 04:18:38.719: //-1/xxxxxxxxxxxx/DPM/dpSendTransitionEvent:
sending 0xFFFFFFFF event
*Dec 24 04:18:42.867: %SYS-5-CONFIG_I: Configured from console by console
siteb#
siteb#
siteb#sh run int s0/2/0:23
Building configuration…
hth,
Pushkar Bhatkoti
Sydney
Pushkar,
My PRI’s show registered as well but could not dial because without the bind command, there’s no way to make a call without IP PBX directing the call.
Thanx man for this info. I’ve solved my problem thanx to you! Cheers!
Ditto - I just ran into this exact problem and your solution (the only one Google finds) fixed it. I can’t thank you enough - you just saved me quite a bit of time troubleshooting and, likely, a TAC case. You rock!
Yoyo,
You correct, the bind command is a must. If you have SRST it removes it during srst because CCM is not reacheble (if you are following the CCIE voice lab).
There is another bind command, for binding MGCP media and signaling on interface or loopback.
don’t mixup this with the one you talking about (DURING SRST).
I have also seen without SRST folks triying to get MGCP work to CCM but the TE channel status in “show ISDN status” doesn’t show “Frames-eastablished”. Whats wrong with that?
If you do show ccm-manager , it will show you that its registerd to pub/sub. also in CCM you will see that the gateway is registered.
The life saving commands for srst router/mgcp router are:
1. Debug mgcp events ( look for send message and received messnage, also make sure that failed message counters are “0″). If you keep seeing the failed message, look for the hostname/domainname , upper/lower case of mgcp gw.
in 99% cases, it is because of your router is configured for “ip domain-name ccievoice.com” and your hostname is SiteBrouter. So if you had to add it to the CCM, make sure that you write SiteBrouter.ccievoice.com and not sitebrouter.ccievoice.com or SiteBrouter (its very important). I have seen many people do this mistake.
2. make sure framing and linecode matches to whats configured on the pstn SimuLATOR.
you must see “Multiple-frames ESTABLISHED” in ‘ show isdn status’ output.
3. ’show mgcp command’
many time folks try to do ‘mgcp’ , ‘no mgcp’ but not able to register the gateway. Most of the time its either my point#1 above or media and signaling is not bind to the loopback or fastethernet. look for this command mgcp bind media/signaling….
try shut, no shut on binded interface… e.g. if you’ve binded singnaling/media to loop0
go to
config t
int loop0
shut
no shut
then issue
show mgcp and look for media and signaling, they should be up and not down.
HTH,
Pushkar Bhatkoti
SYDNEY
Man WHAT A LIFE SAVER. Thank you i got an impressive 5 hours of sleep tonight after “fixing” the PRI issue according to your post. Thank you.
Many thanks for your information ! i
Thank you! I’ve solved my problem =)
Thank You, Thank you, Thank You! Fix my problem too.
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.
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
Thank you! This solved my problem as well!
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.
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!
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.
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
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!
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!