I'm trying to use a private work SIP account with my OBi110. With the work account, the registration server uses SIP, but the proxy servers uses SIPS. The proxy server requires TLS transport.
Using OBI, if the transport changes to:
"ProxyServerTransport" = TLS
When switching to TLS, the Registration server and registration URI change to sips:
REGISTER sips:10.1.1.68 SIP/2
From: <sips:matt.h@XX.com>
To: <sips:matt.h@XX.com>
Via: SIP/2.0/TLS 192.168.1.118:5743;branch=XXX
And result in: Register Failed: 416 Unsupported URI Scheme
I've got this to work correctly on a few Android Apps (CSipSimple).
You can specify:
The registration URI:
sip:10.1.1.68
The account URI:
<sip:matt.h@XX.com>
The Proxy URI:
sips:10.1.1.68:5061
Transport=TLS
The result is:
REGISTER sip:10.1.1.68 SIP/2
From: <sip:matt.h@XX.com>
To: <sip:matt.h@XX.com>
Via: SIP/2.0/TLS 192.168.1.118:5743;branch=XXX
Route: <sips:10.1.1.68:5061;transport=tls;lr>
This registers properly (and phone calls in/out work). The feature request is to either:
1) Allow registration of SIP URI using TLS via radio button selection
OR:
2) If registration fails due to "416 Unsupported URI Scheme", and using "sips" scheme, attempt to try using "sip" URI scheme.
+1