Hi all
I have recently setup a 3CX FREE 10 Users account with two extensions.
Our main phone (first extension) is a Yealink T46U which according to the 3CX documentation can be setup as the router phone (SBC). It is on firmware version: 108.86.119.2.
Our second phone (second extension) is also a Yealink T46U on the same firmware version.
In the 3CX Admin Console I setup both extensions to be auto provisioned using the provisioning link. I have then dropped that link onto the phones using the Yealink web UI.
When the T46U's boot up and attempt to register, they both fail resulting in the blocking of my public IP address for 24 hours. I have also attempted to configure them manually as well, with the same result.
Strangely I can register the two extensions on mobile phones (by scanning the QR codes). They work perfectly on a mobile connection (in my case EE in the UK).
Digging into the settings on the Yealink phones themselves, the hostname and port are all correct, as are the usernames and passwords etc.
Does anybody have any suggestions as to why the extensions register fine on mobile phones (connecting to https://****.3cx.cloud/) but not on the Yealink T46U's when on my broadband connection. Does the T46U acting as the SBC need to have NAT setup on the firewall? Should SIP ALG be enabled or disabled?
I was meant to have the system up and running by tomorrow morning so any assistance would be greatly appreciated.
Many thanks,
Graeme
I have recently setup a 3CX FREE 10 Users account with two extensions.
Our main phone (first extension) is a Yealink T46U which according to the 3CX documentation can be setup as the router phone (SBC). It is on firmware version: 108.86.119.2.
Our second phone (second extension) is also a Yealink T46U on the same firmware version.
In the 3CX Admin Console I setup both extensions to be auto provisioned using the provisioning link. I have then dropped that link onto the phones using the Yealink web UI.
When the T46U's boot up and attempt to register, they both fail resulting in the blocking of my public IP address for 24 hours. I have also attempted to configure them manually as well, with the same result.
Strangely I can register the two extensions on mobile phones (by scanning the QR codes). They work perfectly on a mobile connection (in my case EE in the UK).
Digging into the settings on the Yealink phones themselves, the hostname and port are all correct, as are the usernames and passwords etc.
Does anybody have any suggestions as to why the extensions register fine on mobile phones (connecting to https://****.3cx.cloud/) but not on the Yealink T46U's when on my broadband connection. Does the T46U acting as the SBC need to have NAT setup on the firewall? Should SIP ALG be enabled or disabled?
I was meant to have the system up and running by tomorrow morning so any assistance would be greatly appreciated.
Many thanks,
Graeme
Last edited:
