...
Pay special attention to the following fields:
SIP Profile Field | Description |
|---|---|
IP Address | This is the IP address where NSC will listen for calls |
Transport | Most implementations will want to leave the default “UDP+TCP”, this means SIP packets will be accepted in both UDP and TCP protocols. |
Port | Most of the time you will want to leave the default 5060 port. |
Authenticate Calls | This means any SIP calls (INVITE requests) will be accepted and not challenged. |
Routing Plan: | You have to choose the routing plan you created before () |
...
| Info |
|---|
Security Note: If you Disable Authenticate Calls in the SBC, take care that the remote SIP UA, eg: IP IPBX has |
...
authentication enabled. |
...
| Info |
|---|
Security Note: if you are exposing a SIP Profile to the public internet, you may want to change its Port to something different than default 5060, in order to reduce attach exposure. |
...
| Info |
|---|
The contextual help on each field will give you information about what each field in the SIP profile does. |
...
You can now proceed to optionally bind one or more domains to this SIP profile.
When you bind a domain to a SIP profile you are attaching all the user directory of each domain bound for this SIP profile to be able to accept registrations and/or perform authentication of SIP INVITE messages based on the user/password information stored in the domain user directory (or performed via authentication forwarded according to the domain configuration).*
| Info |
|---|
Note that in order to perform SIP authentication you have to set the “Authenticate Calls” parameter to “Enable”. |
To bind a domain to a SIP profile simply click “Bind” in the SIP profile modification page:
...