<div dir="ltr">To see if CUCM is overwhelmed, you just need a capture to see if all the Cancel messages were sent in a timely manner on the wire. I'd look at the phone console logs and a packet capture from the phone side to see if the phone is actually receiving the Cancel quickly and just not responding to it.</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 9, 2017 at 3:12 PM, cisco.voip <span dir="ltr"><<a href="mailto:cisco.voip@verizon.net" target="_blank">cisco.voip@verizon.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Yes, the Cisco tac is saying the Ok, cancel message gets to the
phone and doesn't reply.<br>
Using the latest 11.7 firmware. CUCM v10.5.2 su3.<br>
<br>
<pre>I've seen this before and it was caused by network issues where the other
phones didn't receive the Cancel.Theay are getting it.
How many phones have the shared line on it? It could be that CUCM node is
getting overwhelmed. 12 phones and how can I tell if the Sub in overwhelmed.</pre>
Network path is clean.<br>
<br>
Does the phone have a builtin Firewall?<br>
<br>
<br>
<div class="m_-6948062561398698079moz-text-plain" style="font-family:-moz-fixed;font-size:14px" lang="x-western">
<pre>Send cisco-voip mailing list submissions to
<a class="m_-6948062561398698079moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
To subscribe or unsubscribe via the World Wide Web, visit
<a class="m_-6948062561398698079moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/<wbr>mailman/listinfo/cisco-voip</a>
or, via email, send a message with subject or body 'help' to
<a class="m_-6948062561398698079moz-txt-link-abbreviated" href="mailto:cisco-voip-request@puck.nether.net" target="_blank">cisco-voip-request@puck.<wbr>nether.net</a>
You can reach the person managing the list at
<a class="m_-6948062561398698079moz-txt-link-abbreviated" href="mailto:cisco-voip-owner@puck.nether.net" target="_blank">cisco-voip-owner@puck.nether.<wbr>net</a>
When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."
Today's Topics:
1. cisco 8851 problematic (cisco.voip)
2. Re: cisco 8851 problematic (Ben Amick)
3. Re: cisco 8851 problematic (Brian Meade)
4. Re: cisco 8851 problematic (Daniel Pagan)
------------------------------<wbr>------------------------------<wbr>----------
Message: 1
Date: Thu, 09 Feb 2017 02:52:23 -0500
From: "cisco.voip" <a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="mailto:cisco.voip@verizon.net" target="_blank"><cisco.voip@verizon.net></a>
To: <a class="m_-6948062561398698079moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
Subject: [cisco-voip] cisco 8851 problematic
Message-ID: <a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="mailto:815e0308-ece5-9f7d-1e98-ab322d27e058@verizon.net" target="_blank"><815e0308-ece5-9f7d-1e98-<wbr>ab322d27e058@verizon.net></a>
Content-Type: text/plain; charset=utf-8; format=flowed
All, i'm on CucM 10.5.2 using cisco 8851 and 8861.
When several phones share the same number, when that line is picked up
by one of the phones - all the other phones continue ringing.
Anyone experience this, or have a tshoot method that works,
Thanks,
Ciscovoip
------------------------------
Message: 2
Date: Thu, 9 Feb 2017 14:58:29 +0000
From: Ben Amick <a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="mailto:bamick@HumanArc.com" target="_blank"><bamick@HumanArc.com></a>
To: cisco.voip <a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="mailto:cisco.voip@verizon.net" target="_blank"><cisco.voip@verizon.net></a>, <a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck.nether.net" target="_blank">"cisco-voip@puck.nether.net"</a>
<a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck.nether.net" target="_blank"><cisco-voip@puck.nether.net></a>
Subject: Re: [cisco-voip] cisco 8851 problematic
Message-ID:
<a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="mailto:820C24BFE55F434C97807C60D4647ACE2FE984C9@E2k10-MB-HT1.humanarc.com" target="_blank"><<wbr>820C24BFE55F434C97807C60D4647A<wbr>CE2FE984C9@E2k10-MB-HT1.<wbr>humanarc.com></a>
Content-Type: text/plain; charset="us-ascii"
Not saying it's the issue, but I know there was a few really messed up bugs with 10.5 with the firmware that was bundled in. This might be one of those bugs. I'd personally try updating your firmware for 88XX and see if it resolves the issue.
Ben Amick
Telecom Analyst
-----Original Message-----
From: cisco-voip [<a class="m_-6948062561398698079moz-txt-link-freetext" href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">mailto:cisco-voip-bounces@<wbr>puck.nether.net</a>] On Behalf Of cisco.voip
Sent: Thursday, February 09, 2017 2:52 AM
To: <a class="m_-6948062561398698079moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><span class="">
Subject: [cisco-voip] cisco 8851 problematic
All, i'm on CucM 10.5.2 using cisco 8851 and 8861.
When several phones share the same number, when that line is picked up by one of the phones - all the other phones continue ringing.
Anyone experience this, or have a tshoot method that works,
Thanks,
Ciscovoip
______________________________<wbr>_________________
cisco-voip mailing list
<a class="m_-6948062561398698079moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
</span><a class="m_-6948062561398698079moz-txt-link-freetext" href="http://cp.mcafee.com/d/1jWVIp6hAe4zqb3PzyrwVMQsCXCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCQk7kr6zBV_HYCUMMCDRXBQSjhOPP3BNOrfkhjmKCHtdfBgY-F6lK1FJ4SyrLRQkhPz0WXVEVdTdAVPmEBCbdSaY3ivNU6U9GX33VkDa3JsJaBGBPdpb6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jqpEVd79EVdCBKQGmGncRAIqnjh1qlbld43PPW9EwmzkwvWKPBoSO-rb0Eh0RZM" target="_blank">http://cp.mcafee.com/d/<wbr>1jWVIp6hAe4zqb3PzyrwVMQsCXCQkm<wbr>nSkNMV4QsCQkmnSkNPPX9J55BZVYsY<wbr>-<wbr>Urhhsd79EVLuWdPp3lpmawECSHIdzr<wbr>BPpdJnor6TbCQk7kr6zBV_<wbr>HYCUMMCDRXBQSjhOPP3BNOrfkhjmKC<wbr>HtdfBgY-<wbr>F6lK1FJ4SyrLRQkhPz0WXVEVdTdAVP<wbr>mEBCbdSaY3ivNU6U9GX33VkDa3JsJa<wbr>BGBPdpb6XiFqFsPmiNsxlK5LE2BCX5<wbr>u1FfUY3jqpEVd79EVdCBKQGmGncRAI<wbr>qnjh1qlbld43PPW9EwmzkwvWKPBoSO<wbr>-rb0Eh0RZM</a>
Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you
------------------------------
Message: 3
Date: Thu, 9 Feb 2017 10:18:53 -0500
From: Brian Meade <a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="mailto:bmeade90@vt.edu" target="_blank"><bmeade90@vt.edu></a>
To: "cisco.voip" <a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="mailto:cisco.voip@verizon.net" target="_blank"><cisco.voip@verizon.net></a>
Cc: <a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck.nether.net" target="_blank">"cisco-voip@puck.nether.net"</a> <a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck.nether.net" target="_blank"><cisco-voip@puck.nether.net></a>
Subject: Re: [cisco-voip] cisco 8851 problematic
Message-ID:
<a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="mailto:CAGcuYh3s4S1YMoMR=gVqO9oKcEH-utjB506CtKn_skwG0GRsLg@mail.gmail.com" target="_blank"><CAGcuYh3s4S1YMoMR=gVqO9oKcEH-<wbr>utjB506CtKn_skwG0GRsLg@mail.<wbr>gmail.com></a>
Content-Type: text/plain; charset="utf-8"
There's an issue where some phones don't ring-
<span class=""><a class="m_-6948062561398698079moz-txt-link-freetext" href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuz56811" target="_blank">https://bst.cloudapps.cisco.<wbr>com/bugsearch/bug/CSCuz56811</a>
For your issue, I'd do some packet captures at CUCM and the phones
ideally. CallManager traces/Console logs may be a good start if you can't
get captures.
I've seen this before and it was caused by network issues where the other
phones didn't receive the Cancel.
How many phones have the shared line on it? It could be that CUCM node is
getting overwhelmed.
On Thu, Feb 9, 2017 at 2:52 AM, cisco.voip <a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="mailto:cisco.voip@verizon.net" target="_blank"><cisco.voip@verizon.net></a> wrote:
</span></pre><span class="">
<blockquote type="cite" style="color:#000000">
<pre>All, i'm on CucM 10.5.2 using cisco 8851 and 8861.
When several phones share the same number, when that line is picked up by
one of the phones - all the other phones continue ringing.
Anyone experience this, or have a tshoot method that works,
Thanks,
Ciscovoip
______________________________<wbr>_________________
cisco-voip mailing list
<a class="m_-6948062561398698079moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a class="m_-6948062561398698079moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/<wbr>mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
</span><pre>-------------- next part --------------
An HTML attachment was scrubbed...
URL: <a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="https://puck.nether.net/pipermail/cisco-voip/attachments/20170209/d5b189ea/attachment-0001.html" target="_blank"><https://puck.nether.net/<wbr>pipermail/cisco-voip/<wbr>attachments/20170209/d5b189ea/<wbr>attachment-0001.html></a>
------------------------------
Message: 4
Date: Thu, 9 Feb 2017 15:28:23 +0000
From: Daniel Pagan <a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="mailto:dpagan@fidelus.com" target="_blank"><dpagan@fidelus.com></a>
To: cisco.voip <a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="mailto:cisco.voip@verizon.net" target="_blank"><cisco.voip@verizon.net></a>, <a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck.nether.net" target="_blank">"cisco-voip@puck.nether.net"</a>
<a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck.nether.net" target="_blank"><cisco-voip@puck.nether.net></a>
Subject: Re: [cisco-voip] cisco 8851 problematic
Message-ID:
<a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="mailto:0b0000c3fe034e0e94c4e0df0803a693@NYC-EX2K13-MB.fidelus.com" target="_blank"><<wbr>0b0000c3fe034e0e94c4e0df0803a6<wbr>93@NYC-EX2K13-MB.fidelus.com></a>
Content-Type: text/plain; charset="windows-1252"
I have heard of this but have yet to see it from a trace perspective. For troubleshooting, my first step would be to determine if the problem is CUCM or the IP Phones that don't stop ringing. The call is sent to an 8851/61 using INVITE, which means CUCM should force them to stop ringing on CANCEL.
</pre><span class="">
<blockquote type="cite" style="color:#000000">
<blockquote type="cite" style="color:#000000">
<blockquote type="cite" style="color:#000000">
<pre>INVITE
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre><<< 100 Trying
<<< 180 Ringing
[[ Answered on other phone ]]
</pre>
<blockquote type="cite" style="color:#000000">
<blockquote type="cite" style="color:#000000">
<blockquote type="cite" style="color:#000000">
<pre>CANCEL
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre><<< 200 OK CSeq Cancel
<<< 487 Request Terminated CSeq INVITE
</pre>
<blockquote type="cite" style="color:#000000">
<blockquote type="cite" style="color:#000000">
<blockquote type="cite" style="color:#000000">
<pre>ACK
</pre>
</blockquote>
</blockquote>
</blockquote>
</span><pre><span class="">If this transaction occurs without issues, the problem is likely the IP phone and not CUCM, but digging in further would likely require review of console logs off the phone to determine if the CANCEL was received and handled properly. If this transaction does not occur, then further review into SDL signaling would be needed depending on where the transaction broke.
Basic way to find SIP signaling to an 88XX is searching CCM SDL traces for "TCP message to <ip_addr_of_phone> on port" or "TCP message from <ip_addr_of_phone> on port". Console logs would contain signaling info too and might be easier, but SDL of course is not written there.
Curious... what version of firmware are you running?
-----Original Message-----
From: cisco-voip [<a class="m_-6948062561398698079moz-txt-link-freetext" href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">mailto:cisco-voip-bounces@<wbr>puck.nether.net</a>] On Behalf Of cisco.voip
Sent: Thursday, February 09, 2017 2:52 AM
To: <a class="m_-6948062561398698079moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
Subject: [cisco-voip] cisco 8851 problematic
All, i'm on CucM 10.5.2 using cisco 8851 and 8861.
When several phones share the same number, when that line is picked up by one of the phones - all the other phones continue ringing.
Anyone experience this, or have a tshoot method that works,
Thanks,
Ciscovoip
______________________________<wbr>_________________
cisco-voip mailing list
</span><a class="m_-6948062561398698079moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck.nether.net" target="_blank"><<wbr>mailto:cisco-voip@puck.nether.<wbr>net></a>
<a class="m_-6948062561398698079moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/<wbr>mailman/listinfo/cisco-voip</a>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <a class="m_-6948062561398698079moz-txt-link-rfc2396E" href="https://puck.nether.net/pipermail/cisco-voip/attachments/20170209/75a01234/attachment-0001.html" target="_blank"><https://puck.nether.net/<wbr>pipermail/cisco-voip/<wbr>attachments/20170209/75a01234/<wbr>attachment-0001.html></a>
------------------------------
Subject: Digest Footer
______________________________<wbr>_________________
cisco-voip mailing list
<a class="m_-6948062561398698079moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a class="m_-6948062561398698079moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/<wbr>mailman/listinfo/cisco-voip</a>
------------------------------
End of cisco-voip Digest, Vol 160, Issue 9
******************************<wbr>************
</pre>
</div>
<br>
</div>
<br>______________________________<wbr>_________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/<wbr>mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>