Configuring a Router phone behind a network router with 3CX port forwarding active

[erling]

Probably obvious to most, but if you try to put a Router phone on a network with 3CX port forwarding active, the Router phone will provision, but normal phones won't.

You have to disable all the 3CX port forwarding on the on-premise router, to allow the normal phones to see, and connect, to the SBC Router phone..

We like to configure customer phones in the office before we deploy them. and we experienced this issue.

The error in the event log is "extension XX is behind SBC Yealink T53 (XX) which has no known local IP yet!"

After the phone are setup, you can re-activate the port forwarding for your on premise server.

Just FYI

 

[JohnS_3CX]

We like to configure customer phones in the office before we deploy them. and we experienced this issue.

You don't necessarily have to - auto provisioning now works over RPS for both normal and router phones.

I can suggest the following workflow:

1. Manually upgrade the firmware on the phones and factory reset them afterwards.
2. Unplug all the phones, and prepare them to go to the customer.
3. Setup your router phone via the web client admin first, and the normal phones after. You now have 14 days from this moment to plug them in at the customer's location.
4. Visit the customer and plug in the router phone first - wait for it to come online and verify that the SBC in your admin console lit up. You can quickly check that via your mobile phone browser if needed, and afterwards make a quick test call to voicemail.
5. As a very last step, you can now plug in the normal phones and give them a couple of minutes to come up.

The error in the event log is "extension XX is behind SBC Yealink T53 (XX) which has no known local IP yet!"

This error you were getting was because something was done out of order. This 100% means that when you plugged in the normal phone, the router phone was not up yet - with the correct firmware in place and the SBC lit up as connected.

None of what you mentioned above would be down to the firewall settings. The phones would never be hitting your own office firewall ports because the customer's FQDN points to some other IP outside your network.