Auto provision half failed - not registered on 3CX - Yealink T54W

[BushInn]

I'm working now. I disconnected all phones and didn't log in for atleast 36hrs (over the 24hrs) went into the management console, deleted the router phone and IP phone and then added them. Worked straight away on phone reboot

Same here with a Snom D715 and 3CX Cloud free.
Provision ok but not registration because of Block WAN requests is ON and event ID12291. After several mins even the admin console got blacklisted.

There's no option to show white\blacklist on console

 

[BushInn]

I'm working now. I disconnected all phones and didn't log in for atleast 36hrs (over the 24hrs) went into the management console, deleted the router phone and IP phone and then added them. Worked straight away on phone reboot

That appeared to unblock all IP. Just leave it all including admin console for 36hrs

 

[franz.ciesko]

I'm working now. I disconnected all phones and didn't log in for atleast 36hrs (over the 24hrs) went into the management console, deleted the router phone and IP phone and then added them. Worked straight away on phone reboot

Thanks for your fast reply.
The questions is why I'm not able to see blacklist and whitelist on my console. Is it a 3CX cloud free limit?

 

[BushInn]

Yes mate sadly. I have the same problem. Working fine now tho.
Do the above and provision the router phone first - make sure firmware is upto date too. Follow the provisioning instructions for your phone as per 3CX Config guides.
Good luck

Thanks for your fast reply.
The questions is why I'm not able to see blacklist and whitelist on my console. Is it a 3CX cloud free limit?

 

[Csut12]

Recently ran into this with new Yealink T54W:

• Came with Firmware 96.86.0.70 - this was latest per MFG
• Deployed in field office, no local SBC.
• Configured as Router Phone: Selected T54w, typed in MAC Address, Selected 'Direct Connect'
• Rebooted phone and confirmed phone would successfully received provisioning information but unable to register/"No Service" message. SBC page showed Router Phone added but was red status/No local IP listed.
• Confirmed 3CX instance allowing 5060/UDP inbound
• No Error Messages in 3CX Logs.
• Deleted 3CX phone provisioning. Reset the phone. Tried again, same result.
• Logged into the Yealink T54w web console and validated the device status [register failed] as well as configuration looking as expected. Nothing too out of the ordinary found -- proxy was set to enabled, but disabling it and saving didn't resolve the issue.

Resolution: A newer firmware was available from 3CX (https://www.3cx.com/docs/phone-firmwares/), version 96.86.0.77. Once I updated the phone firmware (via the Phone web console) with latest from 3CX the phone successfully registered.

It appears that the current Manufacturer firmware 96.86.0.70 doesn't completely work as expected. Not sure why, but sharing incase anyone else has ran into this issue.

 

[TheodorosG_3CX]

@Csut12 Note that the latest firmware will allow the phone to be provisioned as router phone and not get blacklisted.

 

[WagTheDog]

I'm having exactly the same issue

Yealink SIP-T30P
Reset to factory settings
Installed firmware update v 124.86.0.40 (most recent on 3XC firmware list)

Using 3CX Free (cloud hosted)
Followed 3CX auto provision instructions to add IP phone to User from the admin portal
Restarted phone, which auto provisioned to 3CX.

3CX Log immediately showing Warning; "SIP request (REGISTER) from ... rejected. Reason: Block WAN request is ON.

Very shortly after this, IP address is blacklisted for both phone and admin portal computer.

Any solutions?

 

[SteveITS]

I'm having exactly the same issue

Yealink SIP-T30P
Reset to factory settings
Installed firmware update v 124.86.0.40 (most recent on 3XC firmware list)

Using 3CX Free (cloud hosted)
Followed 3CX auto provision instructions to add IP phone to User from the admin portal
Restarted phone, which auto provisioned to 3CX.

3CX Log immediately showing Warning; "SIP request (REGISTER) from ... rejected. Reason: Block WAN request is ON.

Very shortly after this, IP address is blacklisted for both phone and admin portal computer.

Any solutions?

Is your SBC connected OK? The 3 series can’t be a router phone.

 

[WagTheDog]

Is your SBC connected OK? The 3 series can’t be a router phone.

Thanks for your reply and yes, I just figured this out!
Have ordered a T4U series - expecting that will resolve the issue.

 

[TheodorosG_3CX]

Good to know. Always keep in mind the list in the documentation with the models that can be router phones: https://www.3cx.com/sip-phones/yealink-t4-series/

Let us know the outcome.