Solved Provisioning a Yealink W52P DECT Phone

[viridio]

Hello,

I followed the doc here https://www.3cx.com/sip-phones/yealink-dect-w52p/ but the issue is when setting it up in 3CX there is no option for normal phone. The only option I see for this phone in a drop down is when you are in the old admin area and setup a DECT from there. But doing it that way you can only set provision method as Local LAN and not the SBC. I have interface set to PUBLIC.FQDN.COM. I want to use an Raspberry Pi SBC and I set that up, set the W52P outbound proxy as the local SBC IP and can see the auth occur in the event logs but it errors out below. Running On Prem 3CX 18.0 (Build 23).

04/25/2024 4:15:07 PM - [CM102001]: Authentication failed for AuthFail Recv Req REGISTER from 127.0.0.1:5080 tid=663567006 Call-ID=[email protected]:
REGISTER sip:127.0.0.1:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK-524287-2---663567006;rport=5080
Via: SIP/2.0/UDP [::ffff:XX.XXX.XX.XX]:34771;branch=z9hG4bK-524287-1---tunneltid;rport;tnlid=sbc.ce2b1758
Via: SIP/2.0/UDP 192.168.0.230:5060;branch=z9hG4bK663567006
Max-Forwards: 68
Record-Route: <sip:[email protected]:5080;user=proxy;uri=sbc.ce2b1758>
Record-Route: <sip:[email protected]:5060;user=proxy;tnlid=sbc.ce2b1758>
Contact: <sip:[email protected]:5060>
To: "User Name"<sip:[email protected]:5060>
From: "User Name"<sip:[email protected]:5060>;tag=1588257650
Call-ID: [email protected]
CSeq: 2 REGISTER
Expires: 3600
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Proxy-Authorization: Digest username="tg*********",realm="3CXPhoneSystem",nonce="414d5359662ae3fa71:382827a51758bb6de1c7861d92d3eee8",uri="sipUBLIC.FQDN.COM:5060",response="d123a7a8d8e4882623a54193b93a0704",algorithm=MD5
User-Agent: Yealink W52P 25.81.0.30
Allow-Events: talk, hold, conference, refer, check-sync
Content-Length: 0

; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
04/25/2024 4:15:07 PM - [Auth] Provided response (d123a7a8d8e4882623a54193b93a0704 doesn't match calc. (ca3a901db100106452e0a22210ca3a2f)

How can I fix this?

 

[TheodorosG_3CX]

Have you added the phone for manually provisioning, got the credentials and copy in the interface of the Yealink device?

 

[OlegR_3CX]

Hi there.
Additionally, check and apply the newer firmware here, as it should be 26.81.0.40

 

[viridio]

Thanks, I grabbed the provisioning file cfg and copied the data out of it into the Line config per the doc, so that it matched the info. Then we had the latest firmware you reference here, and that still had the same error so we downgraded to the firmware listed in the doc on 3CX and still the same issue.

Ill try upgrading it to version you listed and let you know.

 

[viridio]

Hi there.
Additionally, check and apply the newer firmware here, as it should be 26.81.0.40

That link downloads a ROM for version 25.81.0.30, how do we get 26.81.0.40 ?

 

[SweetAction]

That link downloads a ROM for version 25.81.0.30, how do we get 26.81.0.40 ?

https://www.yealink.com/upfiles/products/201806/1529371451811.81.0.40.rom

 

[viridio]

Thanks, I just deleted the phone from the Admin -> Advanced -> FSX/DECT section and adjusted the number assignment on the phone and now its working via the RPi SBC at the users home. I can call them and they can call out. But oddly I have the phone listed twice under the Admin -> Phones section, the one that has the extension listed, I cant edit at all anywhere or delete it, and the one listed as new I cant edit or assign to an extension either. The one with the extension and IP 192.168.0.230, that IP is the local network IP of the SBC. So would this be normal and I just leave it?

 

[OlegR_3CX]

Hi there.
As this device is EOL, you will configure your device manually, and that is the reason you see UNPROVISIONED.
For the duplication and bold NEW device, it's a multicast message that was received by the 3CX System, so you could reject it.

 

[viridio]

Thanks for all the help and phone is working great, you can close this thread!