Solved Phone not provisioned via SBC

[Goran Cvijanovic]

I have 2 phones with same firmware and one of them is connected to 3CX via SBC, and other isn't. I will upgrade phones after hours, but I would like to know if there is something else I should do to avoid this. I have checked, and both phones are configured to use SBC, so it's not a error in configuration.
Thanks

 

[YiannisH_3CX]

Hello @Goran Cvijanovic

From the provided screenshot it looks like both phones are connected to the PBX. Are you referring to a different phone?
Also these are not the same phones and will require different firmware to update them.

 

[Goran Cvijanovic]

Hey, yes I saw it's not the same model, but it actually doesn't matter because I'm having issues with extension 105 which is connected to 3CX, but not via SBC like second phone, which is strange because I have same settings configured for both of them.
Regards.

 

[YiannisH_3CX]

Is the phone located to a remote site? Did you configure the phones through PnP or manually?

 

[Goran Cvijanovic]

Phone was provisioned using provisioning URL via option 66. When I open phone directly, I can see that phone have "Outbound Proxy" configured with IP 192.168.1.189, which was received via provisioning URL, but phone is actually connected directly to the 3CX which is VM in the cloud.
I assume that because I don't see this part ... via SBC 192.168.1.189:5060, under extension 105.
My theory is that this phone is having issues to communicate with other SIP phones because there is no port forwarding configured for any of the phones, and reason for that is because we use SBC. So when extension 105 dials something via SIP trunk, session is initiaded, but when SIP provider provides public IP of both parties to each other, so they can start RTP communication, extension 105 doesn't hear anything because there is no port forwarding rules in place.
Does this makes sense to you?

 

[YiannisH_3CX]

The phone shows up in the management console with its local IP which makes me believe that is coming from the SBC it is just not configured correctly.
I would recommend removing option 66 and factory resetting the phone. Once it appears in the management console as new assign it to extension via PnP amd see if that works.
Also make sure that you are on the latest version of the PBX and you are using the latest SBC

 

[Goran Cvijanovic]

Thanks, this actually helped me a lot. Phones are up to date, SBC also, and everything is provisioned via PnP like you suggested.
You can close this thread.
Thanks!

 

[YiannisH_3CX]

Glad i could help