Yealink phone get configuration but does not register to 3CX

[Matteo Nexim]

Hello everyone,

I am going crazy with a Yealink phone.

Initially I was trying a T42S (FW version 66.86.0.15), then thinking it was the device I tried a T31G (FW version 124.86.0.77) and the problem is the same.

I configure the MAC address inside phone extension 1004 with the exact model of the telephones.
I see from the logs that the RPS request is generated correctly.
I reboot the phone.
From the logs I see that the configuration of extension 1004 with the correct MAC address is generated.
The phone downloads the configuration (trivially, the credentials are not admin-admin), but I do not see the phone appear among those registered.
Accessing the phone's WEB page I see that the extension [email protected] is in “register failed” status.

I download the phone logs and see that it remains stuck with “wrong SIP passwd” error.
I reset the SIP parameters manually on the phone but the situation does not change.
I try registering any VoIP client, for example Zoiper, on the same extension and it works on the first one.

I reset the Yealink. I configure the VoIP parameters by hand. Same error: “wrong SIP passwd.”

On the same PBX I have registered, without problems, other Yealink devices. As a precaution, I ran the firewall test from the 3CX Dash, with success.

Does anyone have any suggestions?

 

[Alphabetic]

Have you checked for blacklisted IP?

Also, is port 5060 blocked on the firewall where the phone is.

 

[Matteo Nexim]

Have you checked for blacklisted IP?

Also, is port 5060 blocked on the firewall where the phone is.

yes, I checked the blacklist and the IP is not there.
The “client” firewall does not block anything outgoing, as already mentioned I have other devices on the same LAN registered to the same PBX.

 

[Alphabetic]

If you try another extension does it work?

 

[Matteo Nexim]

If you try another extension does it work?

No extension works on these devices (t42s and t31g).

If I try extension 1004 on one of the already registered and working phones, it works.

 

[NicholasP_3CX]

Are these phones on the same network as the PBX or remote?

If remote, how did you configure them on the PBX? Through an SBC or to connect directly?

The phones will pick up the configuration through HTTPS so this would load on the phone, but the authentication will depend on where the phones are.

If the device is trying to connect directly, the PBX would not allow this, as these devices do not have SBC capabilities.

 

[Matteo Nexim]

Are these phones on the same network as the PBX or remote?

If remote, how did you configure them on the PBX? Through an SBC or to connect directly?

The phones will pick up the configuration through HTTPS so this would load on the phone, but the authentication will depend on where the phones are.

If the device is trying to connect directly, the PBX would not allow this, as these devices do not have SBC capabilities.

these phone are connect directy to the remote PBX. But other 3 phone on the same LAN of these 2 yealink works correctly.

 

[JohnS_3CX]

Remote phones = SBC is needed.

Otherwise they will provision but never register.
https://www.3cx.com/docs/3cx-tunnel-session-border-controller/

 

[AWS2P]

did you checked in extension 1004 options /options if connections out of tunnel are allowed?

but for sure SBC is a simplest way or router phones