[cisco-voip] D channel errors - carrier or us?

[Lelio Fulgenzi]

k, thanks for the hint. i'll have to push them to help resolve this intermittent issue. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 


----- Original Message -----
From: "Matthew Loraditch" <MLoraditch at heliontechnologies.com> 
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>, "Cisco VOIP" <cisco-voip at puck.nether.net> 
Sent: Friday, July 13, 2012 10:24:32 AM 
Subject: RE: [cisco-voip] D channel errors - carrier or us? 




Those errors from the router in my experience are 99/100 times a carrier issue. Occasionally it can be your extended demarks or patch cables, and on that 100 th time it could be hardware but I’d go with the carrier as a first look 






Matthew G. Loraditch – CCNP-Voice, CCNA, CCDA 

1965 Greenspring Drive 
Timonium, MD 21093 

voice. 410.252.8830 
fax. 410.252.9284 

Twitter | Facebook | Website | Email Support 







From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi 
Sent: Friday, July 13, 2012 10:20 AM 
To: Cisco VOIP 
Subject: [cisco-voip] D channel errors - carrier or us? 





Over the last few months, I've had sporadic D channel errors. Am I correct in suspecting carrier issues? Typically, if it's a problem on our end, we'd see other errors like unregistered gateways, etc. 


Jul 13 04 :34:46 iptccm105.cs.uoguelph.ca 2274: : : 842: Jul 13 08 :34:46.717 UTC : %CCM_RTMT-RTMT-2-RTMT-ERROR-ALERT: RTMT Alert Name:MgcpDChannelOutOfService Detail: MGCP DChannel is out-of-service. D-Channel-Out-Of-Service status in gateway device(s): S0/DS1-0 at sda0002fce0933c, S0/DS1-0 at sda0002fce09322, S0/DS1-0 at sda000164165b07, S0/DS1-0 at sda000164165b04, S0/DS1-0 at sda0002fce09321, S0/DS1-0 at sda0002fce0933a, S0/DS1-0 at sda0002fce09339, S0/DS1-0 at sda0002fce09324 App ID:Cisco AMC Service Cluster ID: Node ID:iptccm105 


I don't have any more log details from the 6608 ports, but the one port on our 3945 had this information in the logs at the time: 


Jul 13 2012 04:33:58.335: %CONTROLLER-5-UPDOWN: Controller T1 0/0/0, changed state to down (AIS detected) 
Jul 13 2012 04:33:58.391: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for Controller T1 0/0/0 
Jul 13 2012 04:34:00.335: %LINK-3-UPDOWN: Interface Serial0/0/0:23, changed state to down 
Jul 13 2012 04:34:08.643: %MARS_NETCLK-3-HOLDOVER_TRANS: Holdover timer exceeded for Controller T1 0/0/0 
Jul 13 2012 04:34:08.643: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 1 to priority 10 
Jul 13 2012 04:35:07.332: %CONTROLLER-5-UPDOWN: Controller T1 0/0/0, changed state to up 
Jul 13 2012 04:35:09.332: %LINK-3-UPDOWN: Interface Serial0/0/0:23, changed state to up 
Jul 13 2012 04:35:17.644: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1 

Should I be looking in CallManager logs for more information at this time? 


--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120713/3a23e1ac/attachment.html>