Yealink T46U - Not Provisioning For User

[mygeeknc]

Hello all! I have a bit of a problem with a T46U. We have an office with roughly 10 extensions that work fine with an SBC device but the owner wants a phone at their home as well. So, if I understand correctly, a T46U is a router phone and should be capable of acting as a standalone phone. So I've gone through the process of using the correct firmware, I've logged into dashboard and added the phone with the correct MAC address and created the phone profile for it. Then I pasted the provisioning URL into the phone and hit auto provision. The phone then reboots a couple of times and then just says "No Service". I see the phone show up under my dashboard as a SBC Router Phone and is green, see below.

However, what I don't see is the phone under users, it's just red. Am I missing a step here? Thanks!

 

[bitn2]

Have you checked your firewall? Is the phone free to use? What firmware exactly do you have installed?

 

[JohnS_3CX]

Hi,

Is the phone on WiFi or ethernet currently?

Also is it behind a very strict firewall or just a run of the mill home modem?

 

[paulodagraca]

Hello all! I have a bit of a problem with a T46U. We have an office with roughly 10 extensions that work fine with an SBC device but the owner wants a phone at their home as well. So, if I understand correctly, a T46U is a router phone and should be capable of acting as a standalone phone. So I've gone through the process of using the correct firmware, I've logged into dashboard and added the phone with the correct MAC address and created the phone profile for it. Then I pasted the provisioning URL into the phone and hit auto provision. The phone then reboots a couple of times and then just says "No Service". I see the phone show up under my dashboard as a SBC Router Phone and is green, see below.

However, what I don't see is the phone under users, it's just red. Am I missing a step here? Thanks!

View attachment 49713

View attachment 49714

Hello mygeeknc,

Please try to use another internal extenson number, other than "112"
Not sure in what country you are located, but this does not seem to be good for Europe.

Paulo

 

[mygeeknc]

Have you checked your firewall? Is the phone free to use? What firmware exactly do you have installed?

1. The firewall doesn't block anything outbound.
2. I'm not sure what you mean by free to use?

3. 108.87.0.16

   
   
   

 

[mygeeknc]

Hi,

Is the phone on WiFi or ethernet currently?

Also is it behind a very strict firewall or just a run of the mill home modem?

It is ethernet, and it's just a home grade run of the mill modem/router combo.

 

[paulodagraca]

Hello mygeeknc,

Okay, let´s get back to basic.
To get a routerphone working we need the following things:

The tunnel Port 5090 (if not changed) on TCP and UDP to get the communication going.
To start the communication we need the configuration as wel on https Port 443 or 5001 (if not changed) on TCP only.
The HTTPS can only work if the Time is set correctly, IP Phone needs to contact an NTP server on UDP port 123
Also the DNS needs to be working good for the FQDN to be found on IPv4.

Actually, if you use a smartphone at the same location, the smartphone will need the same things to communicate.
So, if possible you could try to SCAN a QR code and try a smartphone on location to check this.
Noting that the smartphone already has the correct time, less depending on the NTP server to be working perfect.
Also you could turn WIFI on/off on the smartphone to check internet connection versus 4G/5G Cell connection.

If all is perfect it MUST work, so it is key to find the small details not working as expected.

Paulo

 

[mygeeknc]

Hello mygeeknc,

Okay, let´s get back to basic.
To get a routerphone working we need the following things:

The tunnel Port 5090 (if not changed) on TCP and UDP to get the communication going.
To start the communication we need the configuration as wel on https Port 443 or 5001 (if not changed) on TCP only.
The HTTPS can only work if the Time is set correctly, IP Phone needs to contact an NTP server on UDP port 123
Also the DNS needs to be working good for the FQDN to be found on IPv4.

Actually, if you use a smartphone at the same location, the smartphone will need the same things to communicate.
So, if possible you could try to SCAN a QR code and try a smartphone on location to check this.
Noting that the smartphone already has the correct time, less depending on the NTP server to be working perfect.
Also you could turn WIFI on/off on the smartphone to check internet connection versus 4G/5G Cell connection.

If all is perfect it MUST work, so it is key to find the small details not working as expected.

Paulo

The user has the 3CX app working just fine on the same network. So I truly do not believe this is a firewall issue but a configuration issue. Thanks for your input though.