[cisco-voip] strange shared line behavior on 88XX phones

Wed Sep 30 17:27:06 EDT 2015

Also, if you’re not sure of which 200 final response belongs to the INVITE vs CANCEL, check out the CSeq header of the 200 message body. Typical call flow should be:

::Call is placed to phone::

cucm --> INVITE --> phoneA
cucm --> INVITE --> phoneB
cucm --> INVITE --> phoneC
cucm <-- 100 <-- phoneA&B&C     (one response per phone)
cucm <-- 180 <-- phoneA&B&C     (one response per phone)

::Call is answered::

cucm <-- 200 with CSeq: 101 INVITE <-- phoneA
cucm --> ACK --> phoneA
^^^^ this exchange can occur before or after the CANCEL requests. Dependent on how quickly CUCM can collect and exchange media information between calling/called phones.

::Call is cancelled on remaining phones::

cucm --> CANCEL --> phoneB
cucm --> CANCEL --> phoneC
cucm <-- 200 with CSeq: 101 CANCEL <-- phoneB&C               (one response per phone)
cucm <-- 487 with CSeq: 101 INVITE <-- phoneB&C          (one response per phone)
cucm --> ACK --> phoneB
cucm --> ACK --> phoneC

Hope this helps. I’m pretty interested in knowing what you or TAC finds.

- Dan

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Daniel Pagan
Sent: Wednesday, September 30, 2015 5:09 PM
To: Erick Wellnitz <ewellnitzvoip at gmail.com>; Lelio Fulgenzi <lelio at uoguelph.ca>
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] strange shared line behavior on 88XX phones

Interesting… Out of curiosity, there should first be a CANCEL to the IP phones where the call wasn’t answered. The phones should then 200 that CANCEL request, and then send the 487 final response to the original INVITE for the call. Do you see the 487 final response six seconds after the CANCEL/200 exchange? I ask only because this should help you determine where the delay is coming from - the phone or CUCM.

- Dan

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Erick Wellnitz
Sent: Wednesday, September 30, 2015 3:51 PM
To: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] strange shared line behavior on 88XX phones

Finally had the behavior repeat.

Found in the console logs and the CM traces that a couple of the phones are, for some reason, delaying their 487 - Request Cancelled response for up to 6 seconds from when the call is answered.

Sent to TAC to see what they have to say.

On Wed, Sep 30, 2015 at 11:09 AM, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:
turns out it is written.

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/7_1_2/ccmsys/accm-712-cm/a03dn.html#wp1100362

Shared Line Restrictions

The following restrictions apply to shared lines:

<snip>
•Do not configure shared-line appearances on the primary lines of the phones; for example, if two phones have a shared-line appearance, only one of the phones should have the primary line configured as shared (the other phone should have the secondary line configured as shared).
<snip>

In version 10 it becomes a suggestion though. Interesting.

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/10_0_1/ccmsys/CUCM_BK_SE5FCFB6_00_cucm-system-guide-100/CUCM_BK_SE5FCFB6_00_cucm-system-guide-100_chapter_010001.html#CUCM_RF_S05975F9_00

Shared Line Suggestions
Do not configure shared line appearances on primary lines as certain feature interactions are impacted. Settings of the primary line are applicable to the shared line. For example: if two phones have a shared-line appearance, only one phone should have the primary line configured as shared to avoid unexplained post configuration behavior.

---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph

519‐824‐4120 Ext 56354<tel:519%E2%80%90824%E2%80%904120%20Ext%2056354>
lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

________________________________
From: "Erick Wellnitz" <ewellnitzvoip at gmail.com<mailto:ewellnitzvoip at gmail.com>>
To: "Lelio Fulgenzi" <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Sent: Wednesday, September 30, 2015 12:20:51 PM
Subject: Re: [cisco-voip] strange shared line behavior on 88XX phones

It is on a fair number of them.  They didn't have the issue on 8.6.2 with the same firmware.

We're waiting on the next occurrence to gather traces.

On Wed, Sep 30, 2015 at 10:04 AM, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:

I recall there being an (un)written rule where shared lines should not be the primary line. It could cause issues.

Are the shared lines the first DN on the phone?

Lelio

---
Lelio Fulgenzi, B.A.
Senior Analyst, Network Infrastructure
Computing and Communications Services (CCS)
University of Guelph

519‐824‐4120 Ext 56354<tel:519%E2%80%90824%E2%80%904120%20Ext%2056354>
lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>
www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs>
Room 037, Animal Science and Nutrition Building
Guelph, Ontario, N1G 2W1

________________________________
From: "Erick Wellnitz" <ewellnitzvoip at gmail.com<mailto:ewellnitzvoip at gmail.com>>
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Sent: Wednesday, September 30, 2015 12:00:20 PM
Subject: [cisco-voip] strange shared line behavior on 88XX phones

anyone seen issues with the 88xx phones on firmware 10.3(1) and CUCM 10.5.2 SU1 where the line starts ringing on some phones right away and some start ringing up to 15 seconds later.  Some also experience ringing after the call is answered up to 15 seconds after answered.

88xx phones are the only ones exhibiting this behavior.  Another consideration is that this shared line is on 17 devices.

Thanks for any insight!

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto: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/20150930/33e32fda/attachment.html>