“SIP Domain Configuration”的版本间的差异
| 第13行： | 第13行： | ||
;;;SIP Domain Configuration | ;;;SIP Domain Configuration | ||
Add a SIP domain by going to “Configuration -> Signaling -> Domains” | Add a SIP domain by going to “Configuration -> Signaling -> Domains” | ||
| + | http://manula.s3.amazonaws.com/user/1885/img/nsc-domain-add2.png | ||
Sangoma SBC Domain Add | Sangoma SBC Domain Add | ||
| 第19行： | 第20行： | ||
The system will then prompt you to select whether you want to enable “Forward Registration / Authentication”. If you want NSC to handle authentication of SIP requests (ie REGISTER, INVITE) using the local user database, you must choose “Disable”. If you plan to forward authentication to a third-party server (ie a registrar server or PBX) you must select “Enable” and provide the information of the third-party server that will handle authentication of those SIP requests. | The system will then prompt you to select whether you want to enable “Forward Registration / Authentication”. If you want NSC to handle authentication of SIP requests (ie REGISTER, INVITE) using the local user database, you must choose “Disable”. If you plan to forward authentication to a third-party server (ie a registrar server or PBX) you must select “Enable” and provide the information of the third-party server that will handle authentication of those SIP requests. | ||
| + | http://manula.s3.amazonaws.com/user/1885/img/nsc-domain-forward-info1.png | ||
| − | |||
If you wish to create SIP accounts (users) you can click the “Add” button in the domain edit page. | If you wish to create SIP accounts (users) you can click the “Add” button in the domain edit page. | ||
| + | http://manula.s3.amazonaws.com/user/1885/img/nsc-domain-add-user.png | ||
| − | |||
| − | You can create as many domains as you want. | + | *You can create as many domains as you want. |
| − | Later you can “Bind” a domain to one or more SIP profiles. | + | *Later you can “Bind” a domain to one or more SIP profiles. |
| − | See the SIP profile configuration for details. | + | *See the SIP profile configuration for details. |
| − | !Note that the directory of users for that domain will only be valid when using a SIP profile that is bound to that domain. | + | !Note that the directory of users for that domain will only be valid when using a SIP profile that is bound to that domain. |
2016年1月22日 (五) 11:47的版本
- SIP Domain Overview
Domains are also known as “Realms” within SIP networks.
A domain, or a SIP realm, is a component within SIP which is used to authenticate users within the SIP registration process. Domain profiles are used to define the way users will authenticate with the SBC.
- Local authentication is used when users will register with the SBC.
- Upper registration is used when users will register to a softswitch or a IP-PBX through a SBC.
This enables topology hiding so that no one outside of the corporate network knows about the equipment sitting behind the SBC.
Domains are not strictly needed. If you are not using SIP registrations or are using IP authentication, you will not require a domain profile.
- SIP Domain Configuration
Add a SIP domain by going to “Configuration -> Signaling -> Domains”
Sangoma SBC Domain Add
All you need to provide to add a domain is the domain name, which should be a FQDN string (ie mycompany.com).
The system will then prompt you to select whether you want to enable “Forward Registration / Authentication”. If you want NSC to handle authentication of SIP requests (ie REGISTER, INVITE) using the local user database, you must choose “Disable”. If you plan to forward authentication to a third-party server (ie a registrar server or PBX) you must select “Enable” and provide the information of the third-party server that will handle authentication of those SIP requests.
If you wish to create SIP accounts (users) you can click the “Add” button in the domain edit page.
- You can create as many domains as you want.
- Later you can “Bind” a domain to one or more SIP profiles.
- See the SIP profile configuration for details.
!Note that the directory of users for that domain will only be valid when using a SIP profile that is bound to that domain.
