Solved Yealink W70B with DECT CP935W-Base Hangs up

[sneffets]

Hello,
Running into an issue with the W70B with a CP935W-Base via DECT...running through an onsite SBC (Debian v18). When I make a call from OR to the CP935W-Base when I pickup the call on another external/internal/3CX mobile app...you get a quick busy signal and it hangs up. The Conference phone is ext861 and I was calling to ext842 (v65 Router Phone). When calling from another v65 behind the same Linux SBC, the calls work great, same thing from the v65 router phone (ext842)...so I am pretty sure the W70B needs something "tweaked", but I could be wrong. I have been searching and trying some adjustments, but I get the same thing. Using Skyetel SIP trunks.

It looks like the call is setup "correctly"...but I do see the call "hang up":

03/13/2023 11:26:21 PM - SendMsg from "Family Conference Room" <sip:[email protected]:5060>;tag=c027d719 to <sip:[email protected]>;tag=4109921909
03/13/2023 11:26:21 PM - [CM503008]: Call(C:18): Call is terminated
03/13/2023 11:26:21 PM - Blocking refers for the Call(C:18)
03/13/2023 11:26:21 PM - Call(C:18) is terminated
03/13/2023 11:26:21 PM - Leg L:18.1[Extn:861] is terminated: Cause: BYE from 127.0.0.1:5080
03/13/2023 11:26:21 PM - L:18.1[Extn:861] got Terminated Recv Req BYE from 127.0.0.1:5080 tid=656440068 Call-ID=[email protected]:
BYE sip:[email protected]:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-524287-2---656440068;rport=5080
Via: SIP/2.0/UDP [::ffff:23.117.52.10]:42019;branch=z9hG4bK-524287-1---tunneltid;rport;tnlid=sbc.aeb3ab34
Via: SIP/2.0/UDP 172.17.2.173:5060;branch=z9hG4bK656440068
Max-Forwards: 68
Record-Route: <sip:[email protected]:5080;user=proxy;uri=sbc.aeb3ab34>
Record-Route: <sip:[email protected]:5060;user=proxy;tnlid=sbc.aeb3ab34>
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]:5060>;tag=9e69b22a
From: "Conference Room"<sip:[email protected]:5060>;tag=656084506
Call-ID: [email protected]
CSeq: 3 BYE
Proxy-Authorization: Digest username="As9x1yf4Cj",realm="3CXPhoneSystem",nonce="414d5359640fe95978:9e8339bce670e2ea70168679dbb0ac69",uri="sip:[email protected]:5060;user=proxy;tnlid=sbc.aeb3ab34",response="fe6b0bc2231109a1c259c1c9d2c15dab",algorithm=MD5
User-Agent: Yealink W70B 146.85.0.40
Content-Length: 0

03/13/2023 11:26:21 PM - Terminated from "Conference Room"<sip:[email protected]:5060>;tag=656084506 to <sip:[email protected]:5060>;tag=9e69b22a; reason: RemoteBye
03/13/2023 11:26:21 PM - L:18.1[Extn:861] Sending: OnSendResp Send 200/BYE from 0.0.0.0:0 tid=656440068 Call-ID=[email protected]:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-524287-2---656440068;rport=5080
Via: SIP/2.0/UDP [::ffff:23.117.52.10]:42019;branch=z9hG4bK-524287-1---tunneltid;rport;tnlid=sbc.aeb3ab34
Via: SIP/2.0/UDP 172.17.2.173:5060;branch=z9hG4bK656440068
Record-Route: <sip:[email protected]:5080;user=proxy;uri=sbc.aeb3ab34>
Record-Route: <sip:[email protected]:5060;user=proxy;tnlid=sbc.aeb3ab34>
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]:5060>;tag=9e69b22a
From: "Conference Room"<sip:[email protected]:5060>;tag=656084506
Call-ID: [email protected]
CSeq: 3 BYE
Content-Length: 0

03/13/2023 11:26:21 PM - SendMsg from <sip:[email protected]:5060>;tag=9e69b22a to "Conference Room"<sip:[email protected]:5060>;tag=656084506
03/13/2023 11:26:20 PM - Currently active calls - 1: [18]
03/13/2023 11:26:20 PM - L:18.1[Extn:861] got Confirmed Recv Req ACK from 127.0.0.1:5080 tid=656408138 Call-ID=[email protected]:
ACK sip:[email protected]:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-524287-2---656408138;rport=5080
Via: SIP/2.0/UDP [::ffff:23.117.52.10]:42019;branch=z9hG4bK-524287-1---tunneltid;rport;tnlid=sbc.aeb3ab34
Via: SIP/2.0/UDP 172.17.2.173:5060;branch=z9hG4bK656408138
Max-Forwards: 68
Record-Route: <sip:[email protected]:5080;user=proxy;uri=sbc.aeb3ab34>
Record-Route: <sip:[email protected]:5060;user=proxy;tnlid=sbc.aeb3ab34>
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]:5060>;tag=9e69b22a
From: "Conference Room"<sip:[email protected]:5060>;tag=656084506
Call-ID: [email protected]
CSeq: 2 ACK
Proxy-Authorization: Digest username="As9x1yf4Cj", realm="3CXPhoneSystem", nonce="414d5359640fe95978:9e8339bce670e2ea70168679dbb0ac69", uri="sip:[email protected]:5060", response="c1462062c38197000bbe30c1a27e1b9f", algorithm=MD5
User-Agent: Yealink W70B 146.85.0.40
Content-Length: 0

 

[JohnS_3CX]

Hi,

While we do support the Yealink W70B, we do not support nor have ever tested the CP935W.

In theory it should work fine, but I would suggest the following test to remove all unknowns from the troubleshooting procedure:

1. Do no involve trunks, just make extension to extension calls
2. Factory reset the W70B and provision it with a single extension using the 3CX provisioning URL. Do not change any of the settings in the base, leave the factory defaults as is to keep the test neutral.
3. Instead of the CP935W, try to use a supported handset with the base (if you have one available for testing)

you get a quick busy signal and it hangs up

This is a bit unusual, I don't think 3CX would be playing this signal, unless you mean the single tone the Fanvil V65 plays along with the screen message "Pls hang up" when someone ends its active call from the other end.

Either way if the base is sending a BYE signal first as soon as the call is picked up, then clearly it is hanging up the call. And most likely this is due to the CP935W. Trying to test with a supported DECT handset should give some insight.

 

[sneffets]

Update…thank you for the information, swamped with installs…but I will be testing this soon, and I will post back.

 

[sneffets]

Ok good news...I factory reset the W70B and followed the Guide using the Auto-provision and boom...working like a champ! Thank you!!!