I have sipsorcery local listening on port 8060 instead of 5060. I am having problems receiving incoming calls via registered providers.
If I have a public address of mydomain.example.org and port 8060 forwarded by nat to the sipsorcery machine listening on 10.x.x.x port 8060
1. Should the sip domain in sipdomains.xml and sipaccounts.xml be mydomain.example.org:8060 or just mydomain.example.org ?
2. Should the contact header or register contact in sipproviders.xml and sipproviderbindings.xml include the port number ie. 1234@mydomain.example.org:8060 or just 1234@mydomain.example.org ?
contact header for port other than 5060
Re: contact header for port other than 5060
1. The domain should be mydomain.example.org and in the alias list you should have something like the string below. The alias list should hold a semi-colon separated list of every permutation on the host name that you're expecting your sipsorcery instance to recognise as being the same as mydomain.example.org.
2. If you leave the port off than SIP devices will treat that as meaning port 5060 should be used. If you want your SIP providers to send incoming calls to your IP address on a specific port then you definitely need to include it in the URI so the answer would be 1234@mydomain.example.org:8060.
Code: Select all
mydomain.example.org:5060;mydomain.example.org:8060;10.1.1.1:5060;10.1.1.1:8060;
Re: contact header for port other than 5060
Seems some providers (specifically ipcomms.net) ignore the port number in the contact header (I am using port 8060) and still send INVITE requests to 5060 (:
Re: contact header for port other than 5060
In those cases you need to get the Proxy at your end to send the REGISTER request from port 8060 rather than 5060. You can do that by adding a custom SIP header to your provider entry of "Route: <sip:ipaddress:8060;lr>" where IP address is the IP address of your local machine.