J100 through SBCE

[jinxs]

Hi Everyone,

I have an IP Office Server edition with a Portwell Cad SBCE using the Remote Worker IX Workplace app. The app works great. My customer asked if we can connect hard phones to the system remotely. I was able to connect the phone to the FQDN, login with the extension credentials then the phone displayed Acquiring Service. I checked the settings on the phone. The SIP Server is the FQDN, the SIP Proxy is the SBC. The HTTPS server is the FQDN. What am I missing to make the J169/J179 work?

Thanks in advance,

AJ-

 

[janni78]

You should trace on the SBC and IPO to see if the request comes through, and if so what the answer is.

"Trying is the first step to failure..." - Homer

 

[John563]

Are you using TLS? You might try SET TLSSRVRID 0 to see if its having issues validating the certificate. tracesbc can trace TLS handshakes as well, which might give some clues.

If you browse to the 46xxsettings.txt file externally, does it contain the internal IP addresses or the proper FQDNs? It could be the phone starts with the right registrar, then the 46xxsettings.txt changes it to a non-routable IP.

If your cert is publicly signed, maybe SET ENABLE_PUBLIC_CA_CERTS 1?

Is there a subscriber flow to allow the j series?

Also don't forget your NoUser configuration. This wouldn't cause your issue though.
RW_SBC_REG=123.123.123.123 - ( External IP of ASBCE or if there is a firewall before ASBCE the external leg of Firewall )
RW_SBC_PROV=456.456.456.456 - ( Internal IP of ASBCE )
RW_SBC_TLS=5061 ( or any chosen port that is programmed on the system as the TLS signaling port )

 

[derfloh]

Do you have any specific settings within 46xxspecials.txt? While the Workplace App ignores that file the phone doesn't.

You have to check if the phone loads the WebRootCA.pem

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN