T46U autoprovisioning not working?

[Stijn_DC]

Hi all,

We deployed a 3CX yesterday and had a wierd issue with one of our T46Us.
It was the first phone for this install so we followed the 3CX Hosted V20 guide a the day before yesterday, just so we had it set up and ready to go

• updated the firmware (108.86.0.76 from https://www.3cx.com/docs/phone-firmwares/ )
• added the device as SBC/routerphone
• rebooted the phone

it then looks like it started to get the new config but it never restarted or updated its config completely.
After leaving it for some time, doing other stuff, we came back and saw that it still didn't get a new config or even rebooted.
rebooted the phone, no luck, looks like it never even got the config.
We of course checked the mac adres etc.
after that we just decided to take another phone from our stock, did exactly the same and it just booted up as an SBC without any issues.

We've checked the devices for any differences and the only real difference that stood out was the MAC adres.
All/most of our Yealink devices hav a MAC adres that starts with 80: however, this units started with 24:9A.

Is this a known issue, could this be an issue between Yealinks RPS and 3CX or are the units with 24:9A not integrated into 3CX's autoprovisioning in some way or form?
Just wanted to check if this could be possible as the unit does seem to be working as intended and we are able to register the device on diy instances.

Thanks!

 

[georgewillow]

Did you resolve this? I am having the same issue with the T46U on v20. They don't seem to be accepting the provisioning profile. They seem to work fine when provisioning via PNP when there is an existing SBC but I can't get them to provision as you described when it's added as a SBC/routerphone

I'm running 108.86.0.77 firmware

 

[georgewillow]

Never mind. My issue was the IP blacklist. Phones provision fine after clearing that of course.

 

[TheodorosG_3CX]

@georgewillow glad to know this is resolved

 

[Stijn_DC]

@georgewillow glad to hear the issue on your end has been resolved!
As a general rule of thumb, if a customer has a static IP adress assigned, we whitelist that IP to prevent accidental blacklisting.

As for our case, at this time we've not used this unit. We are going to be testing this in our NFR V20 demo environment and if it is still giving us issues, we will be opening a support case.

 

[OlegR_3CX]

@Stijn_DC
You normally should not have any issues.
Ensure that the firmware is up to date in advance and you are good to go.
Good luck with your demo!

 

[Stijn_DC]

Hello @OlegR_3CX,

We've tried to redeploy this device without succes.
When looking at the config and comparing to a working T46U we noticed two things:

1) This device was running a Lydis Dutch firmware 108.86.XX.7 (latest availabe)
2) When provisioning in a V20, we saw the following errors in the event logs: SIP request (REGISTER) from X.X.X.X was rejected. Reason: Block WAN requests is ON.

When checking the SIP account settings we found that the Outbound Proxy Server was set as the FQDN of the 3CX instance, while with a working config it should be the local IP of the router phone (in this case, the IP of that device)
We then changed the config of the Proxy server and retried the registration, without succes, we still received the same error in the logs.

We then tried to upgrade the firmware through Lydis but received an error. So after confirming with the customer, we flashed the device with the latest 3CX supported (English) firmware and reprovisioned the device. This worked instantly. So it seems that this was an issue related to the Dutch firmware installed.

Is alternative firmware still allowed in V20 instances?

 

[OlegR_3CX]

Hi there.
You must ensure you are using the latest firmware that is mentioned on our page, and not Lydis, as we are not testing it.