[cisco-voip] MGCP D Channel out of service?

Wes Sisk wsisk at cisco.com
Mon Apr 3 11:17:01 EDT 2006


Either your MGCP gateway unregistered (IP connectivity between CM and 
the MGCP gateway?) or your d-channel really is flapping.

To check for IP connectivity issue:
 From this message:
CCM|MGCPHandler::processMGCPAuedRes parsing Package error (10.10.31.250)

Find the previous previous messages for this gateway:

12/27/2005 10:17:07.002 CCM|MGCPHandler send msg SUCCESSFULLY to:
10.10.31.250
AUEP 13561613 AALN/S2/0 at HQ-VG224-1stFlr MGCP 0.1
F: X
|<CLID::MFCU-CM-1-Cluster><NID::10.10.200.11><CT::2,100,66,1.23017448><IP::10.10.31.250><DEV::>

12/27/2005 10:17:07.002 CCM|MGCPHandler received msg from: 10.10.31.250
200 13561613
X: 2
|<CLID::MFCU-CM-1-Cluster><NID::10.10.200.11><CT::2,100,66,1.23017648><IP::10.10.31.250><DEV::>

This AUEP is not 'normal'.
F = RequestedInfo
X = RequestIdentifier
Normal AUEP requests much more information.


CM only sends this type of AUEP after 2 missed keepalives from the MGCP
gateway.

Normal keepalive exchange for an MGCP gateway on the CM side looks like
this every 15 seconds where 10.10.33.250 is the IP addr of the MGCP gateway:
12/27/2005 10:16:40.173 CCM|MGCPHandler received msg from: 10.10.33.250
NTFY 333382 *@HQ-VG224-3rdFlr MGCP 0.1
X: 0
O:
|<CLID::MFCU-CM-1-Cluster><NID::10.10.200.11><CT::2,100,66,1.23017474><IP::10.10.33.250><DEV::>
12/27/2005 10:16:40.173 CCM|MGCPHandler -
PktCapService::out(Protocol_MGCP,src=10.10.33.250,port=2427,desc=10.10.200.11,port=2427,0,0,msg,len=48,gateway=10.10.33.250)|<CLID::MFCU-CM-1-Cluster><NID::10.10.200.11><CT::2,100,66,1.23017474><IP::10.10.33.250><DEV::>
12/27/2005 10:16:40.173
CCM|<CLID::MFCU-CM-1-Cluster><NID::10.10.200.11><CT::2,100,66,1.23017474><MN::MGCPEndPoint><MV::*@HQ-VG224-3rdFlr><DEV::>
12/27/2005 10:16:40.173 CCM|MGCPHandler send msg SUCCESSFULLY to:
10.10.33.250
200 333382
|<CLID::MFCU-CM-1-Cluster><NID::10.10.200.11><CT::2,100,66,1.23017474><IP::10.10.33.250><DEV::>


Search back through the traces looking for keepalives from the offensive
gateway.  If no sign of NTFY, these are UDP packets that either never
originated from the gateway or dropped in the network.  MGCP does have a
builtin ACK mechanism (200 OK) that should attempt at least 3 retries.

/Wes


Rhodes, Geoff wrote:
>
> At 00:57:29 on 04/03/2006 on cluster StandAloneCluster.
>
> MGCP DChannel is out-of-service .
>
> There are currently 1 device(s) with D-Channel-Out-Of-Service status.
>
>  
>
> I am getting these every so often (3 times this weekend).  Do I have a 
> PRI circuit going bad?
>
>  
>
> Geoff Rhodes
> Director, Information Technology
> Robinson, Bradshaw & Hinson, P.A.
> 704 / 377-8188
> grhodes at rbh.com <mailto:grhodes at rbh.com>
>  
>
>  
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>   



More information about the cisco-voip mailing list