[cisco-voip] Calls dropping

Erick Wellnitz ewellnitzvoip at gmail.com
Wed Jun 26 11:25:45 EDT 2013


Are you able to swap the cable?  Besides a bad cable, the cause of PCV and
LoF is usually a carrier equipment issue in my experience.


On Wed, Jun 26, 2013 at 10:13 AM, costas georgiou <ckos1976 at hotmail.com>wrote:

> Hi,
>
> I have that already.  I am also seeing these errors
>
> E1 0/0/0 is up.
>   Applique type is Channelized E1 - balanced
>   No alarms detected.
>   alarm-trigger is not set
>   Version info FPGA Rev: 08121917, FPGA Type: PRK1
>   Framing is CRC4, Line Code is HDB3, Clock Source is Line.
>   International Bit: 1, National Bits: 11111
>   Data in current interval (78 seconds elapsed):
>      0 Line Code Violations, 6 Path Code Violations
>      0 Slip Secs, 1 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
>      1 Errored Secs, 0 Bursty Err Secs, 1 Severely Err Secs, 0 Unavail Secs
>   Total Data (last 24 hours)
>      0 Line Code Violations, 103098 Path Code Violations,
>      0 Slip Secs, 4328 Fr Loss Secs, 0 Line Err Secs, 1 Degraded Mins,
>      11923 Errored Secs, 7477 Bursty Err Secs, 3933 Severely Err Secs,
> 1035 Unavail Secs
> WPLUKROTVGW0001#
>
> ------------------------------
> Date: Wed, 26 Jun 2013 10:11:23 -0500
> Subject: Re: [cisco-voip] Calls dropping
> From: ewellnitzvoip at gmail.com
> To: ckos1976 at hotmail.com
> CC: cisco-voip at puck.nether.net
>
> I've seen something like this.  I solved it by issuing the
> 'network-clock-select' command.
>
>
> On Wed, Jun 26, 2013 at 10:03 AM, costas georgiou <ckos1976 at hotmail.com>wrote:
>
> Hi All,
>
> We have a CME gateway running at one of our sites.  Apparently calls have
> been dropping today.  I had a look at the logs and I could see the
> following:
>
> Jun 26 07:33:57.786: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for
> Controller E1 0/0/0
> Jun 26 07:33:59.622: %LINK-3-UPDOWN: Interface Serial0/0/0:15, changed
> state to down
> Jun 26 07:34:01.622: %LINK-3-UPDOWN: Interface Serial0/0/0:15, changed
> state to up
> Jun 26 07:34:02.038: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for
> Controller E1 0/0/0
> Jun 26 07:35:21.786: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for
> Controller E1 0/0/0
> Jun 26 07:35:25.038: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for
> Controller E1 0/0/0
> Jun 26 09:06:06.857: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for
> Controller E1 0/0/0
> Jun 26 09:06:10.109: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for
> Controller E1 0/0/0
> Jun 26 10:25:55.761: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for
> Controller E1 0/0/0
> Jun 26 10:25:59.013: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for
> Controller E1 0/0/0
> Jun 26 10:29:28.761: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for
> Controller E1 0/0/0
> Jun 26 10:29:32.013: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for
> Controller E1 0/0/0
> Jun 26 10:32:28.761: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for
> Controller E1 0/0/0
> Jun 26 10:32:32.013: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for
> Controller E1 0/0/0
> Jun 26 13:53:51.652: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for
> Controller E1 0/0/0
> Jun 26 13:53:54.904: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for
> Controller E1 0/0/0
> Jun 26 13:54:10.652: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for
> Controller E1 0/0/0
> Jun 26 13:54:13.904: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for
> Controller E1 0/0/0
> Jun 26 13:54:37.652: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for
> Controller E1 0/0/0
> Jun 26 13:54:40.904: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for
> Controller E1 0/0/0
> Jun 26 13:56:11.652: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for
> Controller E1 0/0/0
> Jun 26 13:56:14.904: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for
> Controller E1 0/0/0
> Jun 26 13:58:12.652: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for
> Controller E1 0/0/0
> Jun 26 13:58:15.904: %MARS_NETCLK-3-HOLDOVER: Exiting Holdover for
> Controller E1 0/0/0
> Jun 26 13:59:17.716: %MARS_NETCLK-3-HOLDOVER: Entering Holdover for
> Controller E1 0/0/0
>
> I am quite sure this is a Carrier issue, I have raised it with them and
> they say the line is clean.  Anyone come across this befor?
>
> Regards
>
> Cos
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130626/c1c832be/attachment.html>


More information about the cisco-voip mailing list