[cisco-voip] cisco 8851 problematic

Thu Feb 9 17:37:47 EST 2017

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.

On Thu, Feb 9, 2017 at 3:12 PM, cisco.voip <cisco.voip at verizon.net> wrote:

> Yes, the Cisco tac is saying the Ok, cancel message gets to the phone and
> doesn't reply.
> Using the latest 11.7 firmware. CUCM v10.5.2 su3.
>
> 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.
>
> Network path is clean.
>
> Does the phone have a builtin Firewall?
>
>
> Send cisco-voip mailing list submissions to
> 	cisco-voip at puck.nether.net
>
> 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
> 	cisco-voip-request at puck.nether.net
>
> You can reach the person managing the list at
> 	cisco-voip-owner at puck.nether.net
>
> 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)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 09 Feb 2017 02:52:23 -0500
> From: "cisco.voip" <cisco.voip at verizon.net> <cisco.voip at verizon.net>
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] cisco 8851 problematic
> Message-ID: <815e0308-ece5-9f7d-1e98-ab322d27e058 at verizon.net> <815e0308-ece5-9f7d-1e98-ab322d27e058 at verizon.net>
> 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 <bamick at HumanArc.com> <bamick at HumanArc.com>
> To: cisco.voip <cisco.voip at verizon.net> <cisco.voip at verizon.net>, "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
> 	<cisco-voip at puck.nether.net> <cisco-voip at puck.nether.net>
> Subject: Re: [cisco-voip] cisco 8851 problematic
> Message-ID:
> 	<820C24BFE55F434C97807C60D4647ACE2FE984C9 at E2k10-MB-HT1.humanarc.com> <820C24BFE55F434C97807C60D4647ACE2FE984C9 at E2k10-MB-HT1.humanarc.com>
> 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 [mailto:cisco-voip-bounces at puck.nether.net <cisco-voip-bounces at puck.nether.net>] On Behalf Of cisco.voip
> Sent: Thursday, February 09, 2017 2:52 AM
> To: cisco-voip at puck.nether.net
> 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
>
>
> _______________________________________________
> cisco-voip mailing listcisco-voip at puck.nether.nethttp://cp.mcafee.com/d/1jWVIp6hAe4zqb3PzyrwVMQsCXCQkmnSkNMV4QsCQkmnSkNPPX9J55BZVYsY-Urhhsd79EVLuWdPp3lpmawECSHIdzrBPpdJnor6TbCQk7kr6zBV_HYCUMMCDRXBQSjhOPP3BNOrfkhjmKCHtdfBgY-F6lK1FJ4SyrLRQkhPz0WXVEVdTdAVPmEBCbdSaY3ivNU6U9GX33VkDa3JsJaBGBPdpb6XiFqFsPmiNsxlK5LE2BCX5u1FfUY3jqpEVd79EVdCBKQGmGncRAIqnjh1qlbld43PPW9EwmzkwvWKPBoSO-rb0Eh0RZM
>
>
> 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 <bmeade90 at vt.edu> <bmeade90 at vt.edu>
> To: "cisco.voip" <cisco.voip at verizon.net> <cisco.voip at verizon.net>
> Cc: "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net> <cisco-voip at puck.nether.net> <cisco-voip at puck.nether.net>
> Subject: Re: [cisco-voip] cisco 8851 problematic
> Message-ID:
> 	<CAGcuYh3s4S1YMoMR=gVqO9oKcEH-utjB506CtKn_skwG0GRsLg at mail.gmail.com> <CAGcuYh3s4S1YMoMR=gVqO9oKcEH-utjB506CtKn_skwG0GRsLg at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> There's an issue where some phones don't ring-https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuz56811
>
> 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 <cisco.voip at verizon.net> <cisco.voip at verizon.net> wrote:
>
>
> 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
>
>
> _______________________________________________
> cisco-voip mailing listcisco-voip at puck.nether.nethttps://puck.nether.net/mailman/listinfo/cisco-voip
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170209/d5b189ea/attachment-0001.html> <https://puck.nether.net/pipermail/cisco-voip/attachments/20170209/d5b189ea/attachment-0001.html>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 9 Feb 2017 15:28:23 +0000
> From: Daniel Pagan <dpagan at fidelus.com> <dpagan at fidelus.com>
> To: cisco.voip <cisco.voip at verizon.net> <cisco.voip at verizon.net>, "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
> 	<cisco-voip at puck.nether.net> <cisco-voip at puck.nether.net>
> Subject: Re: [cisco-voip] cisco 8851 problematic
> Message-ID:
> 	<0b0000c3fe034e0e94c4e0df0803a693 at NYC-EX2K13-MB.fidelus.com> <0b0000c3fe034e0e94c4e0df0803a693 at NYC-EX2K13-MB.fidelus.com>
> 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.
>
>
> INVITE
>
> <<< 100 Trying
> <<< 180 Ringing
> [[ Answered on other phone ]]
>
> CANCEL
>
> <<< 200 OK CSeq Cancel
> <<< 487 Request Terminated CSeq INVITE
>
> ACK
>
> 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 [mailto:cisco-voip-bounces at puck.nether.net <cisco-voip-bounces at puck.nether.net>] On Behalf Of cisco.voip
> Sent: Thursday, February 09, 2017 2:52 AM
> To: cisco-voip at puck.nether.net
> 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
>
>
> _______________________________________________
> cisco-voip mailing listcisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net> <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/20170209/75a01234/attachment-0001.html> <https://puck.nether.net/pipermail/cisco-voip/attachments/20170209/75a01234/attachment-0001.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> cisco-voip mailing listcisco-voip at puck.nether.nethttps://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> ------------------------------
>
> End of cisco-voip Digest, Vol 160, Issue 9
> ******************************************
>
>
>
>
> _______________________________________________
> 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/20170209/2ed43167/attachment.html>