T57W as a router phone not able too Register

[Guillaume Bourgeois]

In your file what do you have for
#Specify the IP address or domain name of the outbound proxy server.
account.1.outbound_proxy.1.address =
?

The local IP address of the phone

 

[SteveITS]

If using wireless, in my experience Yealinks would not provision as a router phone over wireless, but could be changed to wireless after. Officially wireless isn’t supported so I guess that makes sense.

There have been a few reports of the .76 firmware not working for a router phone. It has been fine for me but some have posted they had to install .74 firmware. (Change the number on the 3CX download URL)

 

[Guillaume Bourgeois]

If using wireless, in my experience Yealinks would not provision as a router phone over wireless, but could be changed to wireless after. Officially wireless isn’t supported so I guess that makes sense.

There have been a few reports of the .76 firmware not working for a router phone. It has been fine for me but some have posted they had to install .74 firmware. (Change the number on the 3CX download URL)

The wireless connection have a different MAC address, but when the correct MAC address as per the interface is entered, it does work, although I've never been a big fan of wireless.

It's possible that the "router phone" feature might not be compatible with wireless connections.

However, I fail to see how this would explain why the outbound proxy field is empty in the configuration file downloaded from the PBX through the provisioning link.

 

[SystemsMD.net]

It's not wireless and even more I have a device in the PC port, it's an ATA and that is working as it should show registered with the SIP and can make in and out calls and the port is set to bridge.

 

[SystemsMD.net]

I think its empty as the phone never reported the LAN address to the cloud PBX and we pulled the file I'm trying to manually put it in there but what scares me now it says it's not registering because it disabled is it because I'm manually pushing the config template?

 

[SteveITS]

Try .74. I found this thread, there have been a few others in recent months.
https://www.3cx.com/community/threads/t-57w-router-phone-which-firmware.122679/

 

[SystemsMD.net]

Downgraded to .74 and now it went from disabled to Register Failed
but at least this time it came up on the screen and tried to do it. Also, after a reboot it comes up as config update and then config skipped. also manually putting in local ip for proxy didn't help.

 

[SteveITS]

Downgraded to .74 and now it went from disabled to Register Failed
but at least this time it came up on the screen and tried to do it. Also, after a reboot it comes up as config update and then config skipped. also manually putting in local ip for proxy didn't help.

If you didn't also factory reset it again, try that.

It is usually easy if the right firmware is on the phone. Just add as a router phone via MAC address, and restart it.

 

[Guillaume Bourgeois]

It's not wireless and even more I have a device in the PC port, it's an ATA and that is working as it should show registered with the SIP and can make in and out calls and the port is set to bridge.

Is the ATA working without a phone router?

This is not normal! Every SMB-type system requires that phones be configured through a Phone Router or an SBC. I'm puzzled as to how you managed to get your ATA working without this.

Remove the phone from your 3CX, and also remove it from your Yealink RPS account (If it's in your RPS account) ; 3CX will handle it on its own.
Unplug all others SIP devices on same network (for now)…

Also, verify your MAC address. Be careful, there are 2 MAC addresses, one for the wireless network interface and the other for the wired interface. Ensure you're using the correct one, confirm the information in your DHCP...

Re-add the phone into the 3CX PBX. Perform a Factory Reset on phone; it should auto-provision.

If it doesn't work, generate the info package, open the ZIP file, and review the log files.

 

[JohnS_3CX]

@SystemsMD.net Is your internet connection over IPv6 by any chance?

It will provision, but the SBC does not work on IPv6, so it will never register, hence the phone's Proxy field will not get filled in, and as a result the phone will not attempt to register until this is resolved.

 

[SystemsMD.net]

Today it's working after the reboot. Thank you for that suggestion!

 

[SystemsMD.net]

@SystemsMD.net Is your internet connection over IPv6 by any chance?

It will provision, but the SBC does not work on IPv6, so it will never register, hence the phone's Proxy field will not get filled in, and as a result the phone will not attempt to register until this is resolved.

It is ipv6 but today after the reboot it's working on the older firmware. So, what would be the solution to disable ipv6? Because we have both enabled just in case something does not support ipv6 but wan in most cases show up as ipv6 but other services do get ipv4 as well.

 

[SystemsMD.net]

Is the ATA working without a phone router?

This is not normal! Every SMB-type system requires that phones be configured through a Phone Router or an SBC. I'm puzzled as to how you managed to get your ATA working without this.

Remove the phone from your 3CX, and also remove it from your Yealink RPS account (If it's in your RPS account) ; 3CX will handle it on its own.
Unplug all others SIP devices on same network (for now)…

Also, verify your MAC address. Be careful, there are 2 MAC addresses, one for the wireless network interface and the other for the wired interface. Ensure you're using the correct one, confirm the information in your DHCP...

Re-add the phone into the 3CX PBX. Perform a Factory Reset on phone; it should auto-provision.

If it doesn't work, generate the info package, open the ZIP file, and review the log files.

It was ipv6 and older FW that did the trick but i never changed the ipv6 but it does make since what John is saying. Thank you for jumping on this and trying to help! Sorry I should have sad ATA is not on 3cx pbx it's a direct connect to SIP.

 

[JohnS_3CX]

If it goes out via IPv4 it will be OK. Not sure if it was going through IPv6 earlier causing the issue.

It's also possible you hooked up the phone before upgrading to our supported firmware (which contains the SBC), causing the phone to register directly and get blacklisted (anything lower than 96.86.0.74)