Solved Yealink T42U as a Router Phone auto-provisioning

Status
Not open for further replies.
My 3CX mobile app still seems to be functioning normally, but I was wondering if this is causing the issue with the desk phone? It provisiones fine but displays no service which if I understand correctly, would be SIP service on 5060 on the server.
First of all, is the corresponding SBC for the phone green in Admin/Voice & Chat?
 
First of all, is the corresponding SBC for the phone green in Admin/Voice & Chat?
Router phone is red and it still appears as a new unprovisioned phone in Phones section of the management console. That is why I assumed that the it had to be port related.
 
Go to the Event Log, enter your MAC into Search field. You should see something like this:
- Provisioning file for MAC xxx of user yyy requested by zzz was successfully generated.
- RPS request for Yealink (MAC:xxx) IP Phone of yyy delivered successfully.
 
@Riddle There is no port forwarding on the phone’s network.

SIP ALG must be disabled at the 3CX server router.

Ensure the router phone is set to use itself as its SBC. I ran into that once, where it was not set to anything but other phones worked through it.

You might try powering off the ISP router on the phone’s network.
 
Go to the Event Log, enter your MAC into Search field. You should see something like this:
- Provisioning file for MAC xxx of user yyy requested by zzz was successfully generated.
- RPS request for Yealink (MAC:xxx) IP Phone of yyy delivered successfully.
Making some progress. I did the factory reset on the phone and rebooted both the server and router.
I was able to provision the phone as a router phone. I checked the log and it states that it was successfully generated and delivered.
Furthermore, the log also states that Trunk SBC Yealink U42U has changed status to Up. When I go to Voice&Chat it is listed there as a Router Phone with a green dot.

On the phone itself, I can browse through the directory, but it still says No Service.
I logged into the phone's web server and went to Account --> Register and there is Account 1 with correct extension, Line Active is on but the status says "disabled".

On the SIP Server 1 section there is my FQDN with port 5060 which is where I ran into a problem. On 3CX Server Firewall Check it says Mapping does not match 5060. Mapping is 20003.
I confirmed that the SIP ALG is off and that 5060 on the firewall is mapped to 5060 on 3CX server.
I scanned the server and the firewall for port, 5060 and I received Status: 200 OK.
I also checked for port 20003 on server and the feedback was Port Closed.
SIP port used by PBX in network settings is 5060, so I am not entirely sure where the issue is.

@Riddle There is no port forwarding on the phone’s network.

SIP ALG must be disabled at the 3CX server router.

Ensure the router phone is set to use itself as its SBC. I ran into that once, where it was not set to anything but other phones worked through it.

You might try powering off the ISP router on the phone’s network.

Thank you for confirming that there is no port forwarding on router phone side.
I checked the phone settings on extension. It is using itself for the SBC and the option to change it is grayed out.

At this point I believe it's the issue port 5060 mapping. I believe it is forwarded correctly, I tried a bunch of online tools to make sure it is open on the firewall, ALG is off but the 3CX Firewall checker just doesn't want to see it.

The other port that has Mapping does not match error is 5090. It is confirmed opened on the firewall, but 3CX checker says it's on 20004. The rest of them are opened on firewall and 3CX detects them fine.

I have both open on firewall to allow TCP and UDP traffic.

Is there anything that can be done in the console to force mapping back to 5060 and 5090 or is my only option reinstalling the server?
 
Last edited:
SIP traffic in case of SBC/Router phone goes through tunnel connection directly, so port mapping is of no relevance.
Since now router is connected as a transport, could you try setting up another phone via this Yealink device?
 
Thanks for the tip.

I resolve it. My thing was that I didn't know on our network every device needed to login to the firewall.
So add the phone MAC address and make a rule to bypass the login rule.

Hope this is helpful for someone.
 
  • Like
Reactions: TheodorosG_3CX
Glad to know this is resolved ;)
 
Status
Not open for further replies.

Members Online Now

No members online now.

Forum statistics

Threads
111,831
Messages
589,277
Members
164,660
Latest member
RJenkinsROCK