Solved Some phones not working via SBC

[Moz]

Hi All,

I have been setting up a new system with a cloud based PBX and local SBC (I have other environments like this that work)

Upon connecting four phones today three of the would not provision but show in phones in the 3CX console as follows: phone_IP:5080 via SBC sbc_IP:5060. One phone does work as expected, I did not do anything differently however it shows as follows: phone_IP:5060 via SBC sbc_IP:5060

All devices were brand new, fresh out of the box. I just plugged them into the network with the SBC and attempted to assign an extension after they showed in in the 3CX console as normal.

I have tried updating the firmware, factory resets and reboots of all systems to no avail, after some pointers on what to try next.

Thanks

 

[JohnS_3CX]

Hi Moz,

What phone models and which specific 3CX version are you using ?

 

[Moz]

Hi John,

Using 3CX 15.5 and Grandstream GXP2140 with an up to date firmare version.

I have the same phones elsewhere with the same type of SBC setup and 3CX version all working fine.

Thanks,

 

[JohnS_3CX]

Hi Moz, I tested this phone model over SBC with latest firmware. The default port for this device is 5080 before you provision it for the first time, so this appears to be normal. Once provisioned it switched to 5060 but in any case this should not affect you since the port the phone listens to can be different from 5060 so long as the PBX is aware.

If the provisioning does not take place however please make sure that port 5001 is not blocked for some reason so the auto-provisioning can take place (assuming you did not change the HTTPS port during installation).

You can also check to see if you can open the provisioning link and ensure that your PBX provides a configuration file correctly by going to:

https://[your.domain.com]:5001/provisioning/[your provisioning folder]/cfg[phonemacaddress].xml

Tested and replicated this behavior with FW V1.0.9.102 and V1.0.9.127

 

[Moz]

Hi John,

That is most useful and thanks for confirming, at least I know why the ports differ.

I am running FW V1.0.9.102 currently so will go check the firewall and report back.

Thanks,

 

[Moz]

Hi John,

SIP ALG was the issue here.

Turned off on the firewall and all started working normally.

 

[JohnS_3CX]

Hi Moz, glad it was sorted. Thanks for updating the thread.