BLF Subscribe

[RaymondG]

I know that is might be a sore topic to bring up, but I feel like I'm so close to a solution I can taste it...

This project is for a Church, we picked up a large pile of Cisco 7965 and Cisco 7961 phones. I have all of the phones converted to SIP. And the phones all register correctly with 3CX using TCP for transport, no problems. Except the darn BLF buttons. From my reading these phones will support the subscribe function that 3CX uses to show all endpoints with a BLF if the owner of that endpoint is on the phone. There are a couple of prerequisites, like TCP instead of UDP audio. I've configured this on the phones and can tell that everything is almost there... This is suppose to work with Asterisk, so i figured there wasn't a reason why it wouldn't work with 3CX too.
https://www.voip-info.org/asterisk-presence-for-cisco-79x1-phones/

I need help with the 3CX logs. I'm trying to understand what 3CX is trying to tell me. Is it telling me 3CX doesn't know who to update? Or maybe 3CX doesn't know how to respond? Or is it telling me the phone isn't providing enough information. I believe this is listed as error CM505001

In my lab the 3CX server is 192.168.222.19. The phone end points are in the 192.168.1.x range. I've tried setting up the phones with different provisioning profiles. I'm not really sure what else 3CX does internally with this info aside building configurations that I can't use with Cisco 796x. I've tried Cisco 7961s, Cisco SPA525G as well as no profile and manually specifying TCP for transport. These extensions are two digits (ie extension 10 and extension 12 (I didn't pick the extension numbers).
Here are a few log excerpts.


03/10/2020 5:50:34 PM - Currently active calls - 1: [1]

03/10/2020 5:50:13 PM - [CM503007]: Call(C:1): Extn:12 has joined, contact <sip[email protected]:12545/tcp>

03/10/2020 5:50:13 PM - [CM503007]: Call(C:1): Extn:10 has joined, contact <sip:[email protected]:50973/tcp>

03/10/2020 5:50:13 PM - L:1.2[Extn:12] has joined to L:1.1[Extn:10]

03/10/2020 5:50:12 PM - [CM505001]: Endpoint Extn:12: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Cisco-CP7965G/8.5.3] PBX contact: [sip:[email protected]:5060;transport=TCP]

03/10/2020 5:50:12 PM - [CM503002]: Call(C:1): Alerting Extn:12 by contact <sip[email protected]:12545/tcp>

03/10/2020 5:50:12 PM - [CM503025]: Call(C:1): Calling T:Extn:12@[Dev:sip[email protected]:12545;transport=tcp] for L:1.1[Extn:10]

03/10/2020 5:50:12 PM - [CM503027]: Call(C:1): From: Extn:10 ("Phone10" <sip:[email protected]:0>) to T:Extn:12@[Dev:sip[email protected]:12545;transport=tcp]

03/10/2020 5:50:12 PM - [CM503004]: Call(C:1): Route 1: from L:1.1[Extn:10] to T:Extn:12@[Dev:sip[email protected]:12545;transport=tcp]

03/10/2020 5:50:12 PM - [Flow] No office hours set, office hours assumed

03/10/2020 5:50:12 PM - [Flow] Call(C:1): has built target endpoint: Extn:12 for call from L:1.1[Extn:10]

03/10/2020 5:50:12 PM - [Flow] Target endpoint for 12 is Extn:12

03/10/2020 5:50:12 PM - [CM503010]: Call(C:1): Making route(s) from Extn:10 to <sip:[email protected]:0/UDP>

03/10/2020 5:50:12 PM - [CM505001]: Endpoint Extn:10: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Cisco-CP7965G/9.4.2] PBX contact: [sip:[email protected]:5060;transport=TCP]

03/10/2020 5:50:12 PM - [CM500002]: Call(C:1): Info on incoming INVITE from Extn:10: Invite-IN Recv Req INVITE from 192.168.1.129:50973 tid=430ad25f [email protected]: INVITE sip:[email protected];user=phone SIP/2.0 Via: SIP/2.0/TCP 192.168.1.129:50973;branch=z9hG4bK430ad25f Max-Forwards: 70 Contact: <sip:[email protected]:50973;transport=tcp> To: <sip:[email protected]> From: "Phone10"<sip:[email protected]>;tag=a0554f8c6a8802914289da99-79346ea7 Call-ID: [email protected] CSeq: 102 INVITE Expires: 180 Accept: application/sdp Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, UPDATE, SUBSCRIBE, INFO Content-Disposition: session;handling=optional Content-Type: application/sdp Date: Tue, 10 Mar 2020 22:50:12 GMT Proxy-Authorization: Digest username="Phone10",realm="3CXPhoneSystem",uri="sip:[email protected];user=phone",response="461605817a74ccec3d3a8cdf4ce0ac24",nonce="414d535c1478aaa427:d79dc24df243b19ae53309298a5f3bf3",algorithm=MD5 Supported: replaces, join, sdp-anat, norefersub, resource-priority, extended-refer, X-cisco-callinfo, X-cisco-serviceuri, X-cisco-escapecodes, X-cisco-service-control, X-cisco-srtp-fallback, X-cisco-monrec, X-cisco-config, X-cisco-sis-6.0.0, X-cisco-xsi-8.5.1 User-Agent: Cisco-CP7965G/9.4.2 Allow-Events: kpml, dialog Content-Length: 352 v=0 o=Cisco-SIPUA 24831 0 IN IP4 192.168.1.129 s=SIP Call t=0 0 m=audio 26218 RTP/AVP 0 8 18 102 116 101 c=IN IP4 192.168.1.129 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:102 L16/16000 a=rtpmap:116 iLBC/8000 a=fmtp:116 mode=20 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv
03/10/2020 5:50:12 PM - [CM503001]: Call(C:1): Incoming call from Extn:10 to <sip:[email protected]:0>

03/10/2020 5:50:04 PM - Currently active calls [none]

 

[YiannisH_3CX]

Hi @RaymondG

Not sure why you chose these specific phones or why you are using TCP instead of UDP as an additional challenge but i guess you like a challenge
What i can tell you is from the logs you shared, not a single one has something to do with BLFs.

Do you actually see the BLFs configured on the phones and those just do not work or are you having trouble pushing the config on the phones?
What you should be looking for is SUBSCRIBE and NOTIFY messages using wireshark. The phones should subscribe to the BLFs. If the PBX receives these SUBSCRIBE messages and likes the message it will respond with a 200 OK message.
Then when that extension is involved in a call the PBX will send a NOTIFY message to the phone.

If i remember correctly Cisco 79xx series never worked had working BLF keys with 3CX. SPA 525G phones did work though so i would first try on that. We do have a configuration guide for SPA phones
https://www.3cx.com/Sip-Phones/Cisco-SPA/

 

[RaymondG]

Hello YiannisH,

I appreciate your response. Sorry it took me so long to get back into the weeds on this.

On these Cisco 79x1 phones I have:
2 lines configured for regular inbound line appearances with <featureID>9</featureID>
3 lines configured for BLF/Speed dials with <featureID>21</featureID>
1 line configured for BLF/Shared Parking with <featureID>22</featureID>

After the phone boots it has an apperance though I would expect it to have. If I press the 3 lines configured for Speed dials, the intended phone does ring.
The last line that's configured for BLF/Shared Parking doesn't seem to do anything. The phone seems to know it's not communicating correctly with the PBX. If I push the button on the phone it illuminates, then goes out.

FYI, we're using 2 digit extensions in this environment (I didn't pick the extension length).

Using Wireshark I do hear the phone successfully register (and calls to/from all phones work correctly). I also see the phone attempt to update the SUBSCRIBE for the BLF and Shared Parks. But the response from 3CX is Proxy Authentication Required... I think I have something configured incorrectly. Here's an example of the Wireshark:
Request: SUBSCRIBE sip:[email protected]
Status: 407 Proxy Authentication Required
Request: SUBSCRIBE sip:[email protected]
Status: 407 Proxy Authentication Required
Request: SUBSCRIBE sip:[email protected]
Status: 407 Proxy Authentication Required
Request: SUBSCRIBE sip:[email protected]
Status: 407 Proxy Authentication Required
Status: 487 Event Package Not Supported
Status: 487 Event Package Not Supported
Status: 487 Event Package Not Supported
Status: 487 Event Package Not Supported

The documentation that I am following can be found here:
http://usecallmanager.nz/line-keys-xml.html#BLF Speed Dial

Any thoughts?

 

[RaymondG]

Bump...