Send cisco-voip mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/cisco-voip
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."
Today's Topics:
1. Re: Cisco Federated Link & Jabber implementation (Kenneth Hayes)
2. Re: Outgoing cLI (Adewale2)
3. Re: Cisco Federated Link & Jabber implementation (Thomas LeMay)
4. Re: Cisco Federated Link & Jabber implementation (Kenneth Hayes)
5. Re: UCCX IVR Campaign with SIP GW (shary shary)
6. Re: Need help in installing Cisco WFM and AQM (Muneeb khan)
7. Calls dropping (costas georgiou)
8. Re: Calls dropping (Erick Wellnitz)
9. Re: Calls dropping (costas georgiou)
10. Re: Calls dropping (Jason Faraone)
11. Re: Calls dropping (Erick Wellnitz)
12. Re: Calls dropping (costas georgiou)
----------------------------------------------------------------------
Message: 1
Date: Tue, 25 Jun 2013 05:45:49 -0400
From: Kenneth Hayes <[email protected]>
To: "[email protected]" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Cisco Federated Link & Jabber implementation
Message-ID: <-5098584404765277950@unknownmsgid>
Content-Type: text/plain; charset="iso-8859-1"
I've done this type of deployment and feel like its worth it. I had to do
some firewall configurations on the ASA but besides that it fit my business
needs.
Sent from my iPhone
On Jun 24, 2013, at 9:43 PM, Thomas LeMay <[email protected]> wrote:
Hi,
I am trying to help out a colleague and get some information and pros\cons
from anyone who has implemented or designed a Cisco Federated Link jabber
integration. Any links or information would be greatly appreciated.
Thanks in advance,
Tom
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130625/0629b2f6/attachment-0001.html>
------------------------------
Message: 2
Date: Tue, 25 Jun 2013 18:19:44 +0100 (BST)
From: Adewale2 <[email protected]>
To: Costas Georgiou <[email protected]>, Ryan Ratliff
<[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Outgoing cLI
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
okay, thanks
?
Heaven is Real try your best to be there, and in all your getting get
understanding
God's Own
Addy
________________________________
From: Costas Georgiou <[email protected]>
To: Ryan Ratliff <[email protected]>
Cc: "[email protected]" <[email protected]>
Sent: Tuesday, June 25, 2013 11:42 AM
Subject: Re: [cisco-voip] Outgoing cLI
Hi all,
Just to let you know, the issue was with the route patterns, the "use calling
parties external number mask" was not ticked.
Thanks for your help.
Regards
Cos
Sent from my iPhone
On 21 Jun 2013, at 15:44, Ryan Ratliff <[email protected]> wrote:
In the first two the calling numbers are different, are either of those your
main number, or are they the number you expected to be sent?
>
>
>-Ryan
>
>On Jun 21, 2013, at 5:12 AM, costas georgiou <[email protected]> wrote:
>
>The first two debugs are from an MGCP gateway which is only passing the main
>number not the individual extension.? The last one is passing the correct
>digits.? They are both outgoing,? all extensions are 7 digits.
>?
>un 21 08:27:26.254: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8? callref = 0x1B5C
>??????? Sending Complete
>??????? Bearer Capability i = 0x8090A3
>??????????????? Standard = CCITT
>??????????????? Transfer Capability = Speech
>??????????????? Transfer Mode = Circuit
>??????????????? Transfer Rate = 64 kbit/s
>??????? Channel ID i = 0xA9839F
>??????????????? Exclusive, Channel 31
>??????? Calling Party Number i = 0x0081, '02082696700'
>??????????????? Plan:Unknown, Type:Unknown
>??????? Called Party Number i = 0x80, '01212548185'
>??????????????? Plan:Unknown, Type:Unknown
>Jun 21 08:27:26.438: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8? callref =
>0x9B5C
>??????? Channel ID i = 0xA9839F
>?
>
>un 21 08:34:17.500: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8? callref = 0x1B62
>??????? Sending Complete
>??????? Bearer Capability i = 0x8090A3
>??????????????? Standard = CCITT
>??????????????? Transfer Capability = Speech
>??????????????? Transfer Mode = Circuit
>??????????????? Transfer Rate = 64 kbit/s
>??????? Channel ID i = 0xA9839C
>??????????????? Exclusive, Channel 28
>??????? Calling Party Number i = 0x0081, '2036132'
>??????????????? Plan:Unknown, Type:Unknown
>??????? Called Party Number i = 0x80, '07825015577'
>??????????????? Plan:Unknown, Type:Unknown
>Jun 21 08:34:17.704: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8? callref =
>0x9B62
>??????? Channel ID i = 0xA9839C
>??????????????? Exclusive, Channel 28
>Jun 21 08:34:19.580: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8? callref = 0x1B63
>
>***********************************************************************
>?Working
>*Jun 21 09:19:09.201: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8? callref =
>0x00CD
>??????? Sending Complete
>??????? Bearer Capability i = 0x8090A3
>??????????????? Standard = CCITT
>??????????????? Transfer Capability = Speech
>??????????????? Transfer Mode = Circuit
>??????????????? Transfer Rate = 64 kbit/s
>??????? Channel ID i = 0xA9839F
>??????????????? Exclusive, Channel 31
>??????? Calling Party Number i = 0x0081, '02078223798'
>??????????????? Plan:Unknown, Type:Unknown
>??????? Called Party Number i = 0x80, '07976596466'
>??????????????? Plan:Unknown, Type:Unknown
>*Jun 21 09:19:09.401: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8? callref =
>0x80CD
>??????? Channel ID i = 0xA9839F
>??????????????? Exclusive, Channel 31
>?
>
>> From:[email protected]
>> Date: Thu, 20 Jun 2013 09:19:33 -0500
>> Subject: Re: [cisco-voip] Outgoing cLI
>> To:[email protected]
>> CC:[email protected]
>>?
>> On Thu, Jun 20, 2013 at 7:29 AM, costas georgiou <[email protected]>
>> wrote:
>> > Hi All,
>> >
>> > I have an MGCP and a H323 gateway and I am trying to send out the correct
>> > number. When a call is made it sends out the main number i.e. receptions
>> > number rather than the users extension. CLI is enabled by the provider.
>> > The outbound call Calling party presentation is set to default and so is
>> > the
>> > Route group. I have even amended that to Allow but still not sending the
>> > correct digits.
>>?
>> You said that you have both MGCP and H.323. Which gateway are your
>> outbound calls using?
>>?
>> Do a "debug isdn q931" and then a "term mon" and capture the output of
>> an outbound call.
>_______________________________________________
>cisco-voip mailing list
>[email protected]
>https://puck.nether.net/mailman/listinfo/cisco-voip
>
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130625/50dd27c7/attachment-0001.html>
------------------------------
Message: 3
Date: Tue, 25 Jun 2013 14:55:40 -0400
From: "Thomas LeMay" <[email protected]>
To: "'Kenneth Hayes'" <[email protected]>
Cc: [email protected]
Subject: Re: [cisco-voip] Cisco Federated Link & Jabber implementation
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Hi, Kenneth,
Thank you for responding. Are there any additional specifics that you could
include like pros and cons concerning the implementation or performance of
the applications? What documents did you consult to carry out the
implementation?
Thank you,
Tom
From: Kenneth Hayes [mailto:[email protected]]
Sent: Tuesday, June 25, 2013 5:46 AM
To: [email protected]
Cc: [email protected]
Subject: Re: [cisco-voip] Cisco Federated Link & Jabber implementation
I've done this type of deployment and feel like its worth it. I had to do
some firewall configurations on the ASA but besides that it fit my business
needs.
Sent from my iPhone
On Jun 24, 2013, at 9:43 PM, Thomas LeMay <[email protected]> wrote:
Hi,
I am trying to help out a colleague and get some information and pros\cons
from anyone who has implemented or designed a Cisco Federated Link jabber
integration. Any links or information would be greatly appreciated.
Thanks in advance,
Tom
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130625/47eed50f/attachment-0001.html>
------------------------------
Message: 4
Date: Tue, 25 Jun 2013 15:05:12 -0400
From: Kenneth Hayes <[email protected]>
To: "<[email protected]>" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Cisco Federated Link & Jabber implementation
Message-ID: <8543324818665520751@unknownmsgid>
Content-Type: text/plain; charset="iso-8859-1"
I actually created my own documentation.. Basically opened ports for XMPP
and SIP. I configured the domains in the XMPP config settings and made
changes in my external DNS provider and that was it.
Sent from my iPhone
On Jun 25, 2013, at 2:55 PM, Thomas LeMay <[email protected]> wrote:
Hi, Kenneth,
Thank you for responding. Are there any additional specifics that you
could include like pros and cons concerning the implementation or
performance of the applications? What documents did you consult to carry
out the implementation?
Thank you,
Tom
*From:* Kenneth Hayes [mailto:[email protected]<[email protected]>]
*Sent:* Tuesday, June 25, 2013 5:46 AM
*To:* [email protected]
*Cc:* [email protected]
*Subject:* Re: [cisco-voip] Cisco Federated Link & Jabber implementation
I've done this type of deployment and feel like its worth it. I had to do
some firewall configurations on the ASA but besides that it fit my business
needs.
Sent from my iPhone
On Jun 24, 2013, at 9:43 PM, Thomas LeMay <[email protected]> wrote:
Hi,
I am trying to help out a colleague and get some information and pros\cons
from anyone who has implemented or designed a Cisco Federated Link jabber
integration. Any links or information would be greatly appreciated.
Thanks in advance,
Tom
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130625/42db8ebc/attachment-0001.html>
------------------------------
Message: 5
Date: Tue, 25 Jun 2013 20:01:01 +0000
From: shary shary <[email protected]>
To: "Ryan LaFountain (rlafount)" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] UCCX IVR Campaign with SIP GW
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
thnx for your response. Therefore it means first UCCX dialer will not use CUCM
to make outbound call but send the call directly to Gateway and then using Dial
peer VG will dial out to customer.
In this case we can not use QSIG trunk between CUCM and Nortel.
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [cisco-voip] UCCX IVR Campaign with SIP GW
Date: Mon, 17 Jun 2013 10:00:39 +0000
Hi,
SIP is only required between UCCX and the gateway (and between the GW and CUCM
later in the call flow). This feature requires TDM on the other side to do CPA,
until CUBE supports CPA over IP in a later release. So it is for you:
PSTN -- E1 -- GW -- SIP -- UCCX/CUCM
Thank you,
Ryan LaFountain
Unified Contact Center
Cisco Services
+1 919 392 9898
Sent from my iPhone
On Jun 15, 2013, at 7:09 AM, "shary shary" <[email protected]> wrote:
Hi Folks,
I have to implement the UCCX IVR based outbound campaign and as per the UCCX
admin guide it says we need SIP Gateway to make it run. Customer does not have
SIP trunk but E1 and FXO port. Therefore, the question is, is SIP GW
configuration require only
between UCCX and GW or we need SIP Trunk as well between Service Provider and
voice GW.
Thanks in advance.
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130625/62226e0b/attachment-0001.html>
------------------------------
Message: 6
Date: Wed, 26 Jun 2013 10:09:48 +0500
From: Muneeb khan <[email protected]>
To: Dustin S Fowler <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Need help in installing Cisco WFM and AQM
Message-ID:
<caoivckb9vg3heujgyk6+1bsj6hmczwmnlawvocanjw0ft1l...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Dear Dustin,
I had configured UCCX and CUCM but got stuck in installing AQM and WFM as
they required SQL database, and it need some fields to be inserted for
installing AQM/WFM.
So i need help in installing and configuring them.
Regards
On Mon, Jun 24, 2013 at 7:16 PM, Dustin S Fowler
<[email protected]>wrote:
> Muneeb,
>
> Yes, do you have specific questions?
>
> Dustin S Fowler
>
>
>
> On Jun 23, 2013, at 8:02 AM, Muneeb khan <[email protected]> wrote:
>
> Dear,
>
> Can anyone has an idea about installing and configuring Cisco WFM and AQM,
> integration with UCCX 8.5 and CUCM 8.6?
>
> Regards
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> 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/2a4bc6a2/attachment-0001.html>
------------------------------
Message: 7
Date: Wed, 26 Jun 2013 15:03:46 +0000
From: costas georgiou <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [cisco-voip] Calls dropping
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130626/4f97a693/attachment-0001.html>
------------------------------
Message: 8
Date: Wed, 26 Jun 2013 10:11:23 -0500
From: Erick Wellnitz <[email protected]>
To: costas georgiou <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Calls dropping
Message-ID:
<cak0wosbk16jhqfhqx5uyfawygwvmsz2bz-aszs+bzorsh6t...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
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 <[email protected]>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
> [email protected]
> 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/e025022e/attachment-0001.html>
------------------------------
Message: 9
Date: Wed, 26 Jun 2013 15:13:45 +0000
From: costas georgiou <[email protected]>
To: Erick Wellnitz <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Calls dropping
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
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: [email protected]
To: [email protected]
CC: [email protected]
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 <[email protected]> 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
[email protected]
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/67f0ad3d/attachment-0001.html>
------------------------------
Message: 10
Date: Wed, 26 Jun 2013 15:18:22 +0000
From: Jason Faraone <[email protected]>
To: "'costas georgiou'" <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Calls dropping
Message-ID:
<fb0beb07ca11e54a83b331ad1c263ed665d07...@chq-mdf-mbx-02.paulo.com>
Content-Type: text/plain; charset="us-ascii"
When running "show controller e1" you should see a number of interface errors;
line code violations, path code violations, errored seconds... that sort of
thing. These generally indicate equipment or cabling failure. In my experience,
carriers are notorious for not getting involved unless you really pressure
them, and this includes the passive threat that "if it isn't our problem, we'll
send you a bill", etc. If you see "slipped seconds", this generally indicates a
timing issue. I saw this a lot with the 1st gen dual port VWIC cards, but it
can happen anytime there is a misconfiguration (ie: should pull timing from
carrier, but pulling it internally).
I haven't fully read this, but it looks like a decent start if you need to
troubleshoot cabling to your dmarc - The idea is to use a E1 loop and run ping
tests against the interface itself using a variety of data patterns and
datagram sizes.
http://www.cisco-help.org/2011/05/youre-having-intermittent-issue-with.html
To create the loop, use these instructions:
http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a008010059a.shtml#topic1
At any rate, if you can run a handful of extensive ping tests without
incrementing any of the E1 counter errors, that's usually enough to get the
carrier looking into it. Don't forget to clear counters before testing.
From: cisco-voip [mailto:[email protected]] On Behalf Of
costas georgiou
Sent: Wednesday, June 26, 2013 10:04 AM
To: [email protected]
Subject: [cisco-voip] Calls dropping
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130626/b9332e55/attachment-0001.html>
------------------------------
Message: 11
Date: Wed, 26 Jun 2013 10:25:45 -0500
From: Erick Wellnitz <[email protected]>
To: costas georgiou <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Calls dropping
Message-ID:
<cak0wosbck+-b_sebjusiiagunmd3lvp48aitri4y3ufdtmp...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
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 <[email protected]>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: [email protected]
> To: [email protected]
> CC: [email protected]
>
> 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 <[email protected]>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
> [email protected]
> 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-0001.html>
------------------------------
Message: 12
Date: Wed, 26 Jun 2013 15:39:23 +0000
From: costas georgiou <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Calls dropping
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
Hi,
On the phone to the carrier at the moment, apparently, and I was not told this
20 mins ago when I raised the call, that there seems to be an issue with the
exchange.
The gateway is at another location. I will let you know the outcome.
Thanks again for your quick responses.
Regards
Cos
Date: Wed, 26 Jun 2013 10:25:45 -0500
Subject: Re: [cisco-voip] Calls dropping
From: [email protected]
To: [email protected]
CC: [email protected]
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 <[email protected]> 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: [email protected]
To: [email protected]
CC: [email protected]
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 <[email protected]> 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
[email protected]
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/c3614e99/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
------------------------------
End of cisco-voip Digest, Vol 116, Issue 25
*******************************************
