Hello,   I've noticed that firmware 11.2.1 (I haven't tested for older versions) violates SIP specifications in an embarrassing way when sending a re-SUBSCRIBE within an existing dialog. More specifically, the phone (a 8851 in this case) doesn't use the previously received URI from the Contact header. Instead, it re-uses the R-URI from the initial SUBSCRIBE.   Please find below the cadence of SIP messages demonstrating the problem:   SUBSCRIBE sip:402@my-sip-proxy.net SIP/2.0 Via: SIP/2.0/UDP 2.2.2.2:5064;branch=z9hG4bK-e33ba6a1 From: "johntest-405" <sip:johntest-405@my-sip-proxy.net>;tag=c7976ef9660b6c8c To: <sip:402@my-sip-proxy.net> Call-ID: 14d1519-a9d4fd4d@172.17.173.14 CSeq: 60735 SUBSCRIBE Max-Forwards: 70 Proxy-Authorization: Digest username="johntest-405",realm="my-sip-proxy.net",nonce="W+21WFvttCwi3gqyVA9svGyun5Faqj6X",uri="sip:402@modcom- c",algorithm=MD5,response="aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa" Contact: "johntest-405" <sip:johntest-405@2.2.2.2:5064> Accept: application/dialog-info+xml Expires: 120 Event: dialog User-Agent: Cisco-CP-8851-3PCC/11.2.1 Content-Length: 0 SIP/2.0 200 OK From: <sip:johntest-405@my-sip-proxy.net>;tag=c7976ef9660b6c8c To: <sip:402@my-sip-proxy.net>;tag=as74e10ebb Call-ID: 14d1519-a9d4fd4d@172.17.173.14 CSeq: 60735 SUBSCRIBE Server: modCOM v2 SIP Server Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Expires: 120 Content-Length: 0 Via: SIP/2.0/UDP 2.2.2.2:5064;rport=5064;branch=z9hG4bK-e33ba6a1 Contact: <sip:atpsh-5bed8859-3719-2@3.3.3.3> The URI from the response's Contact: header should be used for all subsequent in-dialog requests from the phone. Instead: SUBSCRIBE sip:402@my-sip-proxy.net SIP/2.0 Via: SIP/2.0/UDP 2.2.2.2:5064;branch=z9hG4bK-81b84571 From: "johntest-405" <sip:johntest-405@my-sip-proxy.net>;tag=c7976ef9660b6c8c To: <sip:402@my-sip-proxy.net>;tag=as74e10ebb Call-ID: 14d1519-a9d4fd4d@172.17.173.14 CSeq: 60736 SUBSCRIBE Max-Forwards: 70 Proxy-Authorization: Digest username="johntest-405",realm="my-sip-proxy.net",nonce="W+21WFvttCwi3gqyVA9svGyun5Faqj6X",uri="sip:402@modcom- c",algorithm=MD5,response="aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa" Contact: "johntest-405" <sip:johntest-405@2.2.2.2:5064> Accept: application/dialog-info+xml Expires: 120 Event: dialog User-Agent: Cisco-CP-8851-3PCC/11.2.1 Content-Length: 0   Public IPs, hostnames and challenge responses have been edited for privacy/seccurity reasons.   BR, George ... View more

Hello all, I've been having the following issue with firmware versions 11.x.x for Cisco 8851 3PCC IP Phone. I can pair my bluetooth headset just fine with the 8851, but after a few days the pairing is lost, and I'm unable to reconnect. More specifically, these are the steps I've taken to no avail: Navigate to the bluetooth menu --> Devices and then highlight the entry for my headset and select "Connect", in order to enforce a manual attempt at re-connecting: After "Connect" is depressed, the labels in the context-sensitive area of the display are cleared, and a single "Cancel" entry is now visible for the last context-sensitive key After a while, the previous labels are restored (namely Option, Scan, Connect), which means that the "Connect" key pressed was registered correctly, but the phone hit some sort of timeout when trying to reconnect with the headset via Bluetooth In another attempt, I deleted the aforementioned entry for my headset from the "Devices" list and then initiated a scan for bluetooth devices to start from scratch. The headset does appear along with other detected bluetooth devices, but after highlighting its entry and selecting "Connect", pairing fails, in a similar fashion as before. The only solution I have found so far is to reset 8851 phone to factory defaults. In that case, I am able to pair with the headset again, until the issue manifests after a few days. I haven't been able to determine what triggers this, but the last time it happened I was on a call which I disconnected using controls on the phone, not on the headset. Almost immediately after hanging up I heard a disconnect tone through the headset. I'm not sure if this in anyway triggered the issue, but I thought I'd mention it anyway, with reservations. Needless to say this behaviour is not encountered when using the headset with other devices, e.g. mobile phone and laptop, both of which connect via bluetooth as well. I also have an issue with the mute function not syncing between phone and headset, but I think I'll start a new thread for that issue. My headset model is Jabra Evolve 75+ UC. Cisco 8851 is listed as supported by Jabra in their support pages, and Cisco lists several Jabra models as supported as well, although I haven't been able to find such a list specifically for 8851 3PCC. This is becoming really annoying, can I expect a fix in a future firmware release? I'd be glad to provide any further information if needed. Thank you.   BR, George ... View more