As stated in the SIP Trunk introduction from the authentication point of view there's no difference between encrypted or unencrypted SIP Trunks. We can have authenticated unencrypted trunks as well as encrypted unauthenticated ones. In figure 1. Detail of the SIP Trunk form about the registration you have a magnification of the SIP Trunk form that shows the registration fields. Usually in order to perform the authentication you have two ways, depending on the authentication type exposed by your peer PBX:
- SIP Account: you must insert username and password and set the Register option on
- IP based: you can leave the username and password fields blank but you have to enable the Qualify option. The HOST parameter is the authentication token.
2.3.1 SIP Account authentication
If your PBX peer on the other end of the Trunk has given to you a SIP Account to be used for the Authentication, then you need to insert login and password in Username and Password fields. Plus you should enable the Register option (check figure 1. Detail of the SIP Trunk form about the registration). The Register option force PrivateServer to act like a VoIP client and thus operate an explicit registration to the other end as soon as the internal Asterisk has been restarted.
Typically this configuration is used by external SIP provider as Messagenet.
2.3.2 IP Address Authentication
If
sdgsdg