Hi
I'm trying to determine the simplest way to enable users to register an endpoint over a 3rd party SIP phone on any internet connection...
The problems I'm aware I have to tackle are:
1) NAT at the Registration end
2) Security for SIP authentication
3) NAT at the endpoint end
We have an NEC SV9500 sitting behind a Sonus SBC1k, which is using a non-natted public IP. So NAT at the SIP registration end is taken care of (there is none).
I've decided to test with 2 forms of authentication - a TLS certificate generated by the SBC and acquired via GoDaddy against a FQDN, along with an endpoint account name and 12 character passcode.
So I feel I'm left with one last problem which I don't know how to manage. The endpoint and it's NAT.... Or am I simply barking up the wrong tree trying to use SIP for this problem?
Thanks
ProAction Networks
NEC Phone System Forums:
I'm trying to determine the simplest way to enable users to register an endpoint over a 3rd party SIP phone on any internet connection...
The problems I'm aware I have to tackle are:
1) NAT at the Registration end
2) Security for SIP authentication
3) NAT at the endpoint end
We have an NEC SV9500 sitting behind a Sonus SBC1k, which is using a non-natted public IP. So NAT at the SIP registration end is taken care of (there is none).
I've decided to test with 2 forms of authentication - a TLS certificate generated by the SBC and acquired via GoDaddy against a FQDN, along with an endpoint account name and 12 character passcode.
So I feel I'm left with one last problem which I don't know how to manage. The endpoint and it's NAT.... Or am I simply barking up the wrong tree trying to use SIP for this problem?
Thanks
ProAction Networks
NEC Phone System Forums: