RPS Provisioned Phone Intermittent Unregister

[oguruma1218]

• 3CX Version, Professional 16.0.5.612
• Server OS, Debian (from 3CX iso) on a KVM
• Is the 3CX Server Hosted and where? KVM box in a DMZ
• IP Phone Make/Model/Firmware Yealink T42S 66.85.0.05/66.84.0.125
• Provisioning Method: RPS
• Trunk Provider or Gateway Make/Model Flowroute
• Has the Firewall Checker passed: Yes
• Are custom Phone Templates being used: No

I set up my 3CX server in a DMZ using a PfSense Router. I provisioned the phone via RPS. Test calls were successful. I unplugged the phone, and when it booted back up, it did not re-register.

I started from scratch, reset the phone to factory defaults, deleted it in the 3CX and reprovisioned with the same method.

Test calls successful. But this time, I left it plugged in, checked back in an hour and it was unregistered (Warning no service on the phone and "Extension 0000 is unregistered" in the Dashboard, but also "RPS request sent successful").

So, for some reason the phone after successfully being registered via RPS, is unregistering....

I've tried the most recent phone firmware and the one before that.

As a test, I set up an SBC and the extension has not any issues when connected via SBC.

 

[Saqqara]

rps stun is not the way to go, as you will have to give each phone different sip / rtp ports, fixed ip address and firewall port forwarding

use of of these options

1. Use a SBC server

2. create firewall rule to allow your phone network access to the 3cx server in the dmz. Use DHCP option 66 to provision the phones after adding the phone details into 3cx as local

 

[oguruma1218]

rps stun is not the way to go, as you will have to give each phone different sip / rtp ports, fixed ip address and firewall port forwarding

use of of these options

1. Use a SBC server

2. create firewall rule to allow your phone network access to the 3cx server in the dmz. Use DHCP option 66 to provision the phones after adding the phone details into 3cx as local

All traffic can pass from the LAN to the 3CX server, and all traffic can pass from the 3CX server to the phone.

What confuses me is why the phone gets successfully provisioned, then decides to unregister...

SBC seems like the most straightforward way to go, however it does create another point of failure...

 

[cobaltit]

Sounds like a firewall issue. RPS is one and done meaning once the phone successfully retrieves the configuration info it doesn't touch RPS again unless you factory reset it. Focus your efforts on figuring out why your firewall doesn't like passing the traffic to the PBX or from the PBX to the phone.

 

[oguruma1218]

Sounds like a firewall issue. RPS is one and done meaning once the phone successfully retrieves the configuration info it doesn't touch RPS again unless you factory reset it. Focus your efforts on figuring out why your firewall doesn't like passing the traffic to the PBX or from the PBX to the phone.

That makes sense, except that I successfully made test calls... I can't fathom why it would work intermittently....

 

[Saqqara]

All traffic can pass from the LAN to the 3CX server, and all traffic can pass from the 3CX server to the phone.

setup the phones the supported way, for your network setup

As the two network are connected, setup your phones within the management console using local lan https://www.3cx.com/sip-phones/yealink-t4-series/

configure DHCP option 66 on the phone lan https://www.3cx.com/sip-phones/DHCP-option-66/ so the phones pickup the configuration.

if this does not work, then you need to investigate your firewall rules / rounting