Configuring SIP Registration for regular NAP - Revision history

Serdar Civici at 15:26, 26 December 2023

2023-12-26T15:26:13Z

← Older revision		Revision as of 11:26, 26 December 2023
Line 76:		Line 76:
	[[Image:SIP_Server_NAP_Create_4.png]]		[[Image:SIP_Server_NAP_Create_4.png]]

	* '''Note:''' If you are using multiple registrations to the same destination with different ports, you must add the port number in the '''Address to register''' too. ~~For example, want to register to 1.2.3.4 from port 5060 and 1.2.3.4 from 5062. In this case NAPs '''Address to register''' parameters will be:~~		* '''Note:''' If you are using multiple registrations to the same destination with different ports, you must add the port number in the '''Address to register''' too.

	[[Image:different_port.png]]		[[Image:different_port.png]]

Serdar Civici at 15:25, 26 December 2023

2023-12-26T15:25:45Z

← Older revision		Revision as of 11:25, 26 December 2023
Line 76:		Line 76:
	[[Image:SIP_Server_NAP_Create_4.png]]		[[Image:SIP_Server_NAP_Create_4.png]]

	* '''Note:''' If you are using multiple registrations to the same destination with different ports, you must add the port number in the Address to ~~Register~~ too. For example, want to register to 1.2.3.4 from port 5060 and 1.2.3.4 from 5062. In this case NAPs Address to ~~Register~~ parameters will be:		* '''Note:''' If you are using multiple registrations to the same destination with different ports, you must add the port number in the '''Address to register''' too. For example, want to register to 1.2.3.4 from port 5060 and 1.2.3.4 from 5062. In this case NAPs '''Address to register''' parameters will be:

	[[Image:different_port.png]]		[[Image:different_port.png]]

Serdar Civici at 15:23, 26 December 2023

2023-12-26T15:23:32Z

← Older revision		Revision as of 11:23, 26 December 2023
Line 76:		Line 76:
	[[Image:SIP_Server_NAP_Create_4.png]]		[[Image:SIP_Server_NAP_Create_4.png]]

	* Note: If you are using multiple registrations to the same destination with different ports, you must add the port number in the Address to Register too. For example, want to register to 1.2.3.4 from port 5060 and 1.2.3.4 from 5062. In this case NAPs Address to Register parameters will be:		* '''Note:''' If you are using multiple registrations to the same destination with different ports, you must add the port number in the Address to Register too. For example, want to register to 1.2.3.4 from port 5060 and 1.2.3.4 from 5062. In this case NAPs Address to Register parameters will be:

	[[Image:different_port.png]]		[[Image:different_port.png]]

Serdar Civici at 15:22, 26 December 2023

2023-12-26T15:22:51Z

← Older revision		Revision as of 11:22, 26 December 2023
Line 75:		Line 75:

	[[Image:SIP_Server_NAP_Create_4.png]]		[[Image:SIP_Server_NAP_Create_4.png]]

			* Note: If you are using multiple registrations to the same destination with different ports, you must add the port number in the Address to Register too. For example, want to register to 1.2.3.4 from port 5060 and 1.2.3.4 from 5062. In this case NAPs Address to Register parameters will be:

			[[Image:different_port.png]]

Allyntree at 14:02, 12 September 2022

2022-09-12T14:02:59Z

← Older revision		Revision as of 10:02, 12 September 2022
Line 1:		Line 1:
	~~=== '''''Applies to version(s): v3.0''''' ===~~
	{{DISPLAYTITLE:Configuring SIP Registration for regular NAP}}		{{DISPLAYTITLE:Configuring SIP Registration for regular NAP}}

Allyntree at 14:02, 12 September 2022

2022-09-12T14:02:47Z

← Older revision		Revision as of 10:02, 12 September 2022
Line 1:		Line 1:
	=== '''''Applies to version(s): v3.0''''' ===		=== '''''Applies to version(s): v3.0''''' ===
	{{DISPLAYTITLE:Configuring SIP Registration for regular NAP}}		{{DISPLAYTITLE:Configuring SIP Registration for regular NAP}}
	A regular NAP is a NAP with specific Proxy address (either IP address or FQDN from 3.1 onward). Configuring SIP Registration for regular NAP requires no extra ~~step from using~~ steps ~~for configuring a regular NAP~~. A NAP that ~~accepting~~ SIP registration must be a Registrar. Registrar accepts SIP registration ~~request~~ from ProSBC after ProSBC ~~receiving this~~ request from remote SIP end point ~~whom it~~ wants to register ~~to this~~ registrar.
	You must configure SIP Registration Domain(s) for your regular NAP and associate them ~~to this~~ regular NAP (Registrar).		{\| class="wikitable"
			\|-
			\|rowspan="2"\|This article applies to:
			\|'''Product'''
			\|'''Version'''
			\|-
			\|SBC
			\|3.0
			\|}

			A regular NAP is a NAP with a specific Proxy address (either IP address or FQDN from 3.1 onward). Configuring SIP Registration for a regular NAP requires no extra steps. A NAP that accepts SIP registration must be a Registrar. A Registrar accepts SIP registration requests from ProSBC after ProSBC receives the request from a remote SIP end point that wants to register on the registrar.

			You must configure SIP Registration Domain(s) for your regular NAP and associate them with the regular NAP (Registrar).

	To create a new NAP:		To create a new NAP:

William Wong: /* Create routes for registered users */

2019-11-19T09:22:39Z

Create routes for registered users

← Older revision		Revision as of 05:22, 19 November 2019
Line 64:		Line 64:

	[[Image:SIP_Server_NAP_Create_4.png]]		[[Image:SIP_Server_NAP_Create_4.png]]

	~~== Create routes for registered users ==~~
	~~In most cases, TBSC will be required to route SIP calls (SIP Invite) to registered users. That's done by [[Sip_registration_forwarding#SIP_Calls_routing\|creating appropriate routes]].~~

William Wong: /* Applies to version(s): v3.0 */

2019-11-19T09:22:23Z

Applies to version(s): v3.0

← Older revision		Revision as of 05:22, 19 November 2019
Line 1:		Line 1:
	=== '''''Applies to version(s): v3.0''''' ===		=== '''''Applies to version(s): v3.0''''' ===
	{{DISPLAYTITLE:Configuring SIP Registration for regular NAP}}		{{DISPLAYTITLE:Configuring SIP Registration for regular NAP}}
	A ~~SIP domain represents~~ a ~~grouping of devices~~ (or ~~users~~) that ~~can communicate with one another~~.		A regular NAP is a NAP with specific Proxy address (either IP address or FQDN from 3.1 onward). Configuring SIP Registration for regular NAP requires no extra step from using steps for configuring a regular NAP. A NAP that accepting SIP registration must be a Registrar. Registrar accepts SIP registration request from ProSBC after ProSBC receiving this request from remote SIP end point whom it wants to register to this registrar.
	You must configure SIP Registration Domain for your ~~system~~. ~~The first step in doing so is to create a SIP Domain:~~		You must configure SIP Registration Domain(s) for your regular NAP and associate them to this regular NAP (Registrar).

			To create a new NAP:

			1- Click '''NAPs''' in the navigation panel

	~~1- Click '''SIP Domain''' in the navigation panel~~		[[Image:NAP_NavigationMenu.png]]

	~~[[Image:SIP_Domain_NavigationMenu.png]]~~

			2- Click '''Create New NAP'''

	~~2- Click '''Create New Domain'''~~		[[Image:Create_New_NAP_SIP.png]]

	~~[[Image:Create_SIP_Domain.png]]~~

			3- Create the new NAP:

	3- ~~Create~~ the ~~new Domain:~~		* Enter a '''name''' for the NAP
			* Click '''Create'''

			[[Image:SIP_Server_NAP_Create.png]]


			4- Verify that the '''NAP was successfully created''' message appears

	* Enter a configuration '''Name''' for this domain.		[[Image:Create_New_NAP_SIP2.png]]
	* Enter a ~~'''Domain Name''' for the~~ SIP ~~Registration Domain (domain can be a FQDN or an IP address)~~
	* Set the ~~number '''Maximum Registered Users''' for this domain~~		5- Associate a SIP transport server with the new NAP:
	* Set the Expires value used by SBC when the remote device doesn't supply one ('''Default Contact Expire''')
	* Select '''~~Routing Method~~''' the ~~system will use to route calls to registered users (if enabled in routing scripts).~~		* Select a '''SIP Transport Server''' from the '''Available''' list
	** '''~~Register source~~'''~~: Sends SIP Invite to the registering source IP address.~~		* Click '''"<<"''' to associate the '''LAN_SIP_TS''' with the NAP
	** '''~~Contact~~'''~~: Sends SIP Invite~~ to ~~the 'contact' from the Register message.~~
	* Set the '''~~Default Contact Expiration~~'''~~, this value will be used when no ''Expires'' value is supplied by~~ the ~~user agent.~~		[[Image:SIP_Server_NAP_Create_1.png]]
	* Set the '''Minimum Contact Expiration''', this is the minimum ''Expires'' value that can be supplied by a user agent. Lower values will be rejected with a 423 'Interval too brief' response.
	* Set the '''Maximum Contact Expiration''', this is the maximum ''Expires'' value that can be supplied by a user agent. Higher value are replaced by this parameter.		6- Enter SIP Server proxy address:
	* Forwarding Parameters:
	** Select the Registration '''Forwarding Mode''' to the registrar:		[[Image:SIP_Server_NAP_Create_2.png]]
	*** '''Contact Remapping''': ~~Changes the user and the IP address~~.
	*** '''Contact Passthrough''': Doesn't change anything. Enables devices to be contacted directly without going through the SBC.		7- Associate a Port range with the new NAP:
	** Set '''Minimum Registrar Expiration''', this is the minimum ''Expires'' value sent by the SBC to the registrar. If a ~~user agent 'Expires' value is greater than this parameter, the SBC will do rate adaptation between the user agent and the Registrar.~~
	** Set '''Maximum Pending Register Forward''', the maximum number of simultaneous pending register requests allowed for this domain. New REGISTER request are being refused passed this threshold.
	** Set '''Maximum Simultaneous Register Forward''', the maximum number of simultaneous active register requests allowed for this domain. New REGISTER request are being refused passed this threshold.
	** Select the Registration '''Registrar Selection Mode''' to the registrar:
	*** '''Active/Standby''': The active registrar is the one with ~~status up and the lowest priority (automatic fallback).~~
	** Enable the ~~'''Forward After Switchover'''~~: ~~After a switchover, the first register refresh request from each user will be forwarded to the active registrar.~~
	* Click '''Create'''

	~~[[Image~~:~~Create_SIP_Domain1.png]]~~		* Select a '''port range''' from the '''Available''' list
			* Click '''"<<"''' to associate '''LAN_Vlan:0''' Port range with the NAP

			[[Image:SIP_Server_NAP_Create_3.png]]

	4- ~~Verify that~~ the ~~'''Sip registration~~ domain ~~was successfully created''' message appears~~		8- Associate a SIP Domain with the new NAP. If you have more then 1 registrar domain using the same registrar you can associate all of them with the NAP:

	~~[[Image:Create_SIP_Domain2.png]]~~		* Select a '''sip domain''' from the '''Available''' list
	<~~br>~~<~~br>~~		* Click '''"<<"''' to associate the SIP Domain with the NAP
	~~[[Image:Create_SIP_Domain3.png]]~~

	~~5- Add the domain to one or multiple NAPs from which users are allowed to register for this domain~~		[[Image:Open_NAP_Create_3.png]]
	* Click '''NAPs''' in the navigation panel
	* Click on a NAP to bind the SIP Domain to
	* Add the SIP Domain to the NAP (bottom of the page):
	[[Image:~~bind_domain_to_nap~~.png]]


	6- ~~Multiple registrars (registration redundancy)~~		9- Configure settings for the following parameter groups as required:
	~~Multiple registrars can be created per domain, for redundancy.~~		*Registration Parameters
	* ~~Registrars are ordered by priority~~		*Authentication Parameters
	* ~~Users' registration requests are forwarded to the available registrar with the highest priority in the list~~		*Network Address Translation
	* SIP ~~'options' polling is used to determine which registrars are available or not~~		*SIP-I Parameters
			*Advanced Parameters

	~~[[Image:multiple_registrars.png]]~~		*Click '''Save'''

			[[Image:SIP_Server_NAP_Create_4.png]]

	== Create routes for registered users ==		== Create routes for registered users ==
	In most cases, TBSC will be required to route SIP calls (SIP Invite) to registered users. That's done by [[Sip_registration_forwarding#SIP_Calls_routing\|creating appropriate routes]].		In most cases, TBSC will be required to route SIP calls (SIP Invite) to registered users. That's done by [[Sip_registration_forwarding#SIP_Calls_routing\|creating appropriate routes]].

William Wong at 08:36, 19 November 2019

2019-11-19T08:36:06Z

← Older revision		Revision as of 04:36, 19 November 2019
Line 1:		Line 1:
	=== '''''Applies to version(s): v3.0''''' ===		=== '''''Applies to version(s): v3.0''''' ===
	{{DISPLAYTITLE:~~Creating a~~ SIP ~~Domain~~}}		{{DISPLAYTITLE:Configuring SIP Registration for regular NAP}}
	A SIP domain represents a grouping of devices (or users) that can communicate with one another.		A SIP domain represents a grouping of devices (or users) that can communicate with one another.
	You must configure SIP Registration Domain for your system. The first step in doing so is to create a SIP Domain:		You must configure SIP Registration Domain for your system. The first step in doing so is to create a SIP Domain:

William Wong: Created page with "=== '''''Applies to version(s): v3.0''''' === {{DISPLAYTITLE:Creating a SIP Domain}} A SIP domain represents a grouping of devices (or users) that can communicate with one ano..."

2019-11-19T08:30:29Z

Created page with "=== '''''Applies to version(s): v3.0''''' === {{DISPLAYTITLE:Creating a SIP Domain}} A SIP domain represents a grouping of devices (or users) that can communicate with one ano..."

New page

=== '''''Applies to version(s): v3.0''''' ===
{{DISPLAYTITLE:Creating a SIP Domain}}
A SIP domain represents a grouping of devices (or users) that can communicate with one another.
You must configure SIP Registration Domain for your system. The first step in doing so is to create a SIP Domain:

1- Click '''SIP Domain''' in the navigation panel

[[Image:SIP_Domain_NavigationMenu.png]]

2- Click '''Create New Domain'''

[[Image:Create_SIP_Domain.png]]

3- Create the new Domain:

* Enter a configuration '''Name''' for this domain.
* Enter a '''Domain Name''' for the SIP Registration Domain (domain can be a FQDN or an IP address)
* Set the number '''Maximum Registered Users''' for this domain
* Set the Expires value used by SBC when the remote device doesn't supply one ('''Default Contact Expire''')
* Select '''Routing Method''' the system will use to route calls to registered users (if enabled in routing scripts).
** '''Register source''': Sends SIP Invite to the registering source IP address.
** '''Contact''': Sends SIP Invite to the 'contact' from the Register message.
* Set the '''Default Contact Expiration''', this value will be used when no ''Expires'' value is supplied by the user agent.
* Set the '''Minimum Contact Expiration''', this is the minimum ''Expires'' value that can be supplied by a user agent. Lower values will be rejected with a 423 'Interval too brief' response.
* Set the '''Maximum Contact Expiration''', this is the maximum ''Expires'' value that can be supplied by a user agent. Higher value are replaced by this parameter.
* Forwarding Parameters:
** Select the Registration '''Forwarding Mode''' to the registrar:
*** '''Contact Remapping''': Changes the user and the IP address.
*** '''Contact Passthrough''': Doesn't change anything. Enables devices to be contacted directly without going through the SBC.
** Set '''Minimum Registrar Expiration''', this is the minimum ''Expires'' value sent by the SBC to the registrar. If a user agent 'Expires' value is greater than this parameter, the SBC will do rate adaptation between the user agent and the Registrar.
** Set '''Maximum Pending Register Forward''', the maximum number of simultaneous pending register requests allowed for this domain. New REGISTER request are being refused passed this threshold.
** Set '''Maximum Simultaneous Register Forward''', the maximum number of simultaneous active register requests allowed for this domain. New REGISTER request are being refused passed this threshold.
** Select the Registration '''Registrar Selection Mode''' to the registrar:
*** '''Active/Standby''': The active registrar is the one with status up and the lowest priority (automatic fallback).
** Enable the '''Forward After Switchover''': After a switchover, the first register refresh request from each user will be forwarded to the active registrar.
* Click '''Create'''

[[Image:Create_SIP_Domain1.png]]

4- Verify that the '''Sip registration domain was successfully created''' message appears

[[Image:Create_SIP_Domain2.png]]
<br><br>
[[Image:Create_SIP_Domain3.png]]

5- Add the domain to one or multiple NAPs from which users are allowed to register for this domain
* Click '''NAPs''' in the navigation panel
* Click on a NAP to bind the SIP Domain to
* Add the SIP Domain to the NAP (bottom of the page):
[[Image:bind_domain_to_nap.png]]

6- Multiple registrars (registration redundancy)
Multiple registrars can be created per domain, for redundancy.
* Registrars are ordered by priority
* Users' registration requests are forwarded to the available registrar with the highest priority in the list
* SIP 'options' polling is used to determine which registrars are available or not

[[Image:multiple_registrars.png]]

== Create routes for registered users ==
In most cases, TBSC will be required to route SIP calls (SIP Invite) to registered users. That's done by [[Sip_registration_forwarding#SIP_Calls_routing|creating appropriate routes]].