SIP Registration - Revision history

William Wong: /* Configuration */

2019-11-21T09:48:29Z

Configuration

← Older revision		Revision as of 05:48, 21 November 2019
Line 58:		Line 58:
	*[[Toolpack:Allocating a SIP Network Access Point (NAP) B\|Allocating a SIP NAP Configuration v2.6]]		*[[Toolpack:Allocating a SIP Network Access Point (NAP) B\|Allocating a SIP NAP Configuration v2.6]]
	*[[Toolpack:Allocating a SIP Network Access Point (NAP) A\|Allocating a SIP NAP Configuration v2.5]]		*[[Toolpack:Allocating a SIP Network Access Point (NAP) A\|Allocating a SIP NAP Configuration v2.5]]
			</div>
	*[[Configuring SIP Registration to SIP Proxy\|Configuring SIP Registration to SIP Proxy]]		*[[Configuring SIP Registration to SIP Proxy\|Configuring SIP Registration to SIP Proxy]]
	~~</div>~~

	== References ==		== References ==

William Wong: /* Configuration */

2019-11-21T09:47:11Z

Configuration

← Older revision		Revision as of 05:47, 21 November 2019
Line 58:		Line 58:
	*[[Toolpack:Allocating a SIP Network Access Point (NAP) B\|Allocating a SIP NAP Configuration v2.6]]		*[[Toolpack:Allocating a SIP Network Access Point (NAP) B\|Allocating a SIP NAP Configuration v2.6]]
	*[[Toolpack:Allocating a SIP Network Access Point (NAP) A\|Allocating a SIP NAP Configuration v2.5]]		*[[Toolpack:Allocating a SIP Network Access Point (NAP) A\|Allocating a SIP NAP Configuration v2.5]]
			*[[Configuring SIP Registration to SIP Proxy\|Configuring SIP Registration to SIP Proxy]]
	</div>		</div>

Luc Morissette: /* Configuration */

2018-06-18T12:53:49Z

Configuration

← Older revision		Revision as of 08:53, 18 June 2018
Line 50:		Line 50:
	== Configuration ==		== Configuration ==

			*[[Toolpack:Allocating a SIP Network Access Point (NAP) F\|Allocating a SIP NAP Configuration v3.0]]
			*[[Toolpack:Allocating a SIP Network Access Point (NAP) E\|Allocating a SIP NAP Configuration v2.10]]
	*[[Toolpack:Allocating a SIP Network Access Point (NAP) D\|Allocating a SIP NAP Configuration v2.9]]		*[[Toolpack:Allocating a SIP Network Access Point (NAP) D\|Allocating a SIP NAP Configuration v2.9]]
	*[[Toolpack:Allocating a SIP Network Access Point (NAP) C\|Allocating a SIP NAP Configuration v2.8]]		*[[Toolpack:Allocating a SIP Network Access Point (NAP) C\|Allocating a SIP NAP Configuration v2.8]]
			<div class="mw-collapsible mw-collapsed" data-collapsetext="other versions" data-expandtext="Click here for other versions" style="width: 400px;">
	*[[Toolpack:Allocating a SIP Network Access Point (NAP) B\|Allocating a SIP NAP Configuration v2.7]]		*[[Toolpack:Allocating a SIP Network Access Point (NAP) B\|Allocating a SIP NAP Configuration v2.7]]
	*[[Toolpack:Allocating a SIP Network Access Point (NAP) B\|Allocating a SIP NAP Configuration v2.6]]		*[[Toolpack:Allocating a SIP Network Access Point (NAP) B\|Allocating a SIP NAP Configuration v2.6]]
	*[[Toolpack:Allocating a SIP Network Access Point (NAP) A\|Allocating a SIP NAP Configuration v2.5]]		*[[Toolpack:Allocating a SIP Network Access Point (NAP) A\|Allocating a SIP NAP Configuration v2.5]]
			</div>

	== References ==		== References ==

Abrassard at 10:56, 18 June 2018

2018-06-18T10:56:01Z

← Older revision		Revision as of 06:56, 18 June 2018
Line 9:		Line 9:
	* The Tmedia forwards per-user registration requests from users		* The Tmedia forwards per-user registration requests from users
	** [[Sip_registration_forwarding\|Explanation of Tmedia's registration forwarding]]		** [[Sip_registration_forwarding\|Explanation of Tmedia's registration forwarding]]
	** [[Toolpack:Creating_a_SIP_Domain_SBC_A\|Configuration of Tmedia's registration forwarding]]* The Tmedia registers itself to the SIP Proxy (~~per NAP)~~		** [[Toolpack:Creating_a_SIP_Domain_SBC_A\|Configuration of Tmedia's registration forwarding]]
	* Registration per SIP NAP (explained in current page)		* The Tmedia registers itself to the SIP Proxy (per SIP NAP, as explained below in current page)

	== Registration per SIP NAP ==		== Registration per SIP NAP ==

Abrassard at 10:55, 18 June 2018

2018-06-18T10:55:22Z

← Older revision		Revision as of 06:55, 18 June 2018
Line 7:		Line 7:

	Tmedia supports two modes for SIP Registration:		Tmedia supports two modes for SIP Registration:
	* The Tmedia forwards per-user registration requests from users ([[Sip_registration_forwarding\|~~Sip Registration Forwarding~~]])		* The Tmedia forwards per-user registration requests from users
	* The Tmedia registers itself to the SIP Proxy (per NAP)		** [[Sip_registration_forwarding\|Explanation of Tmedia's registration forwarding]]
			** [[Toolpack:Creating_a_SIP_Domain_SBC_A\|Configuration of Tmedia's registration forwarding]]* The Tmedia registers itself to the SIP Proxy (per NAP)
			* Registration per SIP NAP (explained in current page)

	~~== Registration forwarding ==~~		== Registration per SIP NAP ==
	~~The Tmedia supports forwarding registration requests from individual users. Documentation is found here:~~
	* [[Sip_registration_forwarding\|Explanation of Tmedia's registration forwarding]]
	* [[Toolpack:Creating_a_SIP_Domain_SBC_A\|Configuration of Tmedia's registration forwarding]]

	== Registration per NAP ==
	The Tmedia supports to register a SIP [[NAP]] to a SIP proxy. Registration, can be used, for example, to authenticate the Tmedia Gateway IP address to a SIP provider proxy or SBC and allow the SIP traffic from the Tmedia to that SIP provider.		The Tmedia supports to register a SIP [[NAP]] to a SIP proxy. Registration, can be used, for example, to authenticate the Tmedia Gateway IP address to a SIP provider proxy or SBC and allow the SIP traffic from the Tmedia to that SIP provider.
	* Registration is when Tmedia sends a SIP REGISTER to a Registrar, and gets a response which could be accepted (200 OK) or refused (4xx reason code). Upon refusal, the registration is not stopped and is retried after 5 seconds.		* Registration is when Tmedia sends a SIP REGISTER to a Registrar, and gets a response which could be accepted (200 OK) or refused (4xx reason code). Upon refusal, the registration is not stopped and is retried after 5 seconds.

Abrassard at 10:54, 18 June 2018

2018-06-18T10:54:02Z

← Older revision		Revision as of 06:54, 18 June 2018
Line 6:		Line 6:
	[[Image:SIP Registration Process.jpg\|400px]]		[[Image:SIP Registration Process.jpg\|400px]]

	Tmedia ~~does not provide registrar functionality, therefore, a~~ SIP ~~client cannot register to a~~ Tmedia~~. If a SIP clients communicate to another SIP clients~~ (~~B2BUA~~) ~~in point-~~to~~-point fashion and not through a SIP proxy, REGISTER is usually not required. In that case,~~ the SIP ~~clients are required to know the IP addresses or DNS of all the other clients they wish to communicate with.~~		Tmedia supports two modes for SIP Registration:
			* The Tmedia forwards per-user registration requests from users ([[Sip_registration_forwarding\|Sip Registration Forwarding]])
			* The Tmedia registers itself to the SIP Proxy (per NAP)

	== Registration ==		== Registration forwarding ==
			The Tmedia supports forwarding registration requests from individual users. Documentation is found here:
			* [[Sip_registration_forwarding\|Explanation of Tmedia's registration forwarding]]
			* [[Toolpack:Creating_a_SIP_Domain_SBC_A\|Configuration of Tmedia's registration forwarding]]

			== Registration per NAP ==
	The Tmedia supports to register a SIP [[NAP]] to a SIP proxy. Registration, can be used, for example, to authenticate the Tmedia Gateway IP address to a SIP provider proxy or SBC and allow the SIP traffic from the Tmedia to that SIP provider.		The Tmedia supports to register a SIP [[NAP]] to a SIP proxy. Registration, can be used, for example, to authenticate the Tmedia Gateway IP address to a SIP provider proxy or SBC and allow the SIP traffic from the Tmedia to that SIP provider.
	* Registration is when Tmedia sends a SIP REGISTER to a Registrar, and gets a response which could be accepted (200 OK) or refused (4xx reason code). Upon refusal, the registration is not stopped and is retried after 5 seconds.		* Registration is when Tmedia sends a SIP REGISTER to a Registrar, and gets a response which could be accepted (200 OK) or refused (4xx reason code). Upon refusal, the registration is not stopped and is retried after 5 seconds.

Lucas Trottier at 14:12, 23 June 2016

2016-06-23T14:12:12Z

← Older revision		Revision as of 10:12, 23 June 2016
Line 10:		Line 10:
	== Registration ==		== Registration ==
	The Tmedia supports to register a SIP [[NAP]] to a SIP proxy. Registration, can be used, for example, to authenticate the Tmedia Gateway IP address to a SIP provider proxy or SBC and allow the SIP traffic from the Tmedia to that SIP provider.		The Tmedia supports to register a SIP [[NAP]] to a SIP proxy. Registration, can be used, for example, to authenticate the Tmedia Gateway IP address to a SIP provider proxy or SBC and allow the SIP traffic from the Tmedia to that SIP provider.

	* Registration is when Tmedia sends a SIP REGISTER to a Registrar, and gets a response which could be accepted (200 OK) or refused (4xx reason code). Upon refusal, the registration is not stopped and is retried after 5 seconds.		* Registration is when Tmedia sends a SIP REGISTER to a Registrar, and gets a response which could be accepted (200 OK) or refused (4xx reason code). Upon refusal, the registration is not stopped and is retried after 5 seconds.
	* If Authentication is required, the Registrar returns a 401 Unauthorized response with a WWW-Authenticate header
	* The WWW-Authenticate header contains nonce to encrypt user’s communications password, user then sends a second REGISTER containing an Authorization header with the user's encrypted password
	* Even if there is no call on the system, Tmedia will send SIP REGISTER		* Even if there is no call on the system, Tmedia will send SIP REGISTER
	* If it is not registered already, the Tmedia will send SIP REGISTER at 5 seconds interval, otherwise it is at the half of the minimum registration negotiated with the remote proxy (endpoint)
	* The SIP REGISTER is "valid" for 3600 seconds
	* Tmedia will send a new REGISTER (to refresh a registration) after half of the minimum registration negotiated, general use will be at 1800 seconds (3600/2)
	* Sending SIP REGISTER will happen when the option [[Parameter:_Register_to_Proxy\|"Register to Proxy?"]] is selected for a specific SIP [[NAP]]		* Sending SIP REGISTER will happen when the option [[Parameter:_Register_to_Proxy\|"Register to Proxy?"]] is selected for a specific SIP [[NAP]]
	* If you apply a new configuration and the option [[Parameter:_Register_to_Proxy\|"Register to Proxy?"]] is present it will start sending SIP REGISTER		* If you apply a new configuration and the option [[Parameter:_Register_to_Proxy\|"Register to Proxy?"]] is present it will start sending SIP REGISTER


	===Register with negotiation (contact ~~expire)~~===		===Register with no answer from registrar ===
			If it is not registered already, the Tmedia will send a new SIP REGISTER every 32 + 5 seconds interval until it receive a response from the Registrar
			*Over UDP (shown it the message flow bellow), the REGISTER request is retransmitted for 32 seconds before the request transaction timeout, then a new SIP REGISTER is sent after 5 seconds.
			*Over TCP, if the SIP registrar does not listen on the TCP port, a new TCP connection is retried every 5 seconds. If the TCP connection is established but no SIP responses returned by the Registrar, the transaction timeout after 32s and then a new SIP REGISTER is sent after 5 seconds.
			[[Image:SIP_Register_no_answers.png\|500px]]

			===Register expire negotiation ===
			The REGISTER request negotiate the contact binding expiration by adding "expires=3600" parameter to the contact header. The value is hardcoded to 3600 seconds.
			If the REGISTER response from the Registrar does not change the "expires" parameter:
			* The SIP REGISTER will be "valid" for 3600 seconds
			* Tmedia will send a new REGISTER (to refresh the registration) after half of the minimum registration negotiated, general use will be at 1800 seconds (3600/2)

			The Registrar can change the "expires" contact parameter or the Expires header as shown in the two example below to negotiate a value different from 3600 seconds.
			==== Negotiation uses case 1: contact expires header ====
			In the example below, the Registrar changes the "expires" contact parameter.

	[[Image:SIP_Register_negotiated_expire_time_example_1.png\|700px]]		[[Image:SIP_Register_negotiated_expire_time_example_1.png\|700px]]

			==== Negotiation uses case 2: no contact expires parameter; Expires header ====
	===~~Register with negotiation (~~contact ~~expire not provided, default~~ Expires header)===		In the example below, the Registrar removes the "expires" contact parameter and set the Expires header.

	[[Image:SIP Register negotiated expire time example 2.png\|650px]]		[[Image:SIP Register negotiated expire time example 2.png\|650px]]


	===Register Authentication===		===Register Authentication===
			* If Authentication is required, the Registrar returns a 401 Unauthorized response with a WWW-Authenticate header
			* The WWW-Authenticate header contains nonce to encrypt user’s communications password, user then sends a second REGISTER containing an Authorization header with the user's encrypted password
	[[Image:SIP_Register_401_authentication_example.png\|1100px]]		[[Image:SIP_Register_401_authentication_example.png\|1100px]]


	~~===Register with no answer from registrar ===~~
	The message flow below shows the retransmission of SIP REGISTER '''over UDP'''. The request is retransmitted for 32 seconds before the request transaction timeout, then a new SIP REGISTER is sent after 5 seconds.
	Over TCP, if the SIP registrar does not listen on the TCP port, a new TCP connection is retried every 5 seconds. If the TCP connection is established but no SIP responses returned by the Registrar, the transaction timeout after 32s and then a new SIP REGISTER is sent after 5 seconds.
	~~[[Image:SIP_Register_no_answers.png\|500px]]~~

	~~== [[NAP\|Network Access Point (NAP)]] Availability ==~~
	~~If [[Parameter:_Poll_Remote_Proxy\|"Poll Remote Proxy?"]] and [[Parameter:_Register_to_Proxy\|"Register to Proxy?"]] are both checked, only the SIP OPTIONS answers will affect the [[NAP]] availability.~~



	== Configuration ==		== Configuration ==

Lucas Trottier: /* Registration */

2016-06-23T13:50:24Z

Registration

← Older revision		Revision as of 09:50, 23 June 2016
Line 11:		Line 11:
	The Tmedia supports to register a SIP [[NAP]] to a SIP proxy. Registration, can be used, for example, to authenticate the Tmedia Gateway IP address to a SIP provider proxy or SBC and allow the SIP traffic from the Tmedia to that SIP provider.		The Tmedia supports to register a SIP [[NAP]] to a SIP proxy. Registration, can be used, for example, to authenticate the Tmedia Gateway IP address to a SIP provider proxy or SBC and allow the SIP traffic from the Tmedia to that SIP provider.

	* Registration is when Tmedia sends a SIP REGISTER to a Registrar, and gets a response which could be accepted (200 OK) or refused (~~anything else~~) ~~that may require further action~~		* Registration is when Tmedia sends a SIP REGISTER to a Registrar, and gets a response which could be accepted (200 OK) or refused (4xx reason code). Upon refusal, the registration is not stopped and is retried after 5 seconds.
	* If Authentication is required, the Registrar returns a 401 Unauthorized response with a WWW-Authenticate header		* If Authentication is required, the Registrar returns a 401 Unauthorized response with a WWW-Authenticate header
	* The WWW-Authenticate header contains nonce to encrypt user’s communications password, user then sends a second REGISTER containing an Authorization header with the user's encrypted password		* The WWW-Authenticate header contains nonce to encrypt user’s communications password, user then sends a second REGISTER containing an Authorization header with the user's encrypted password

Lucas Trottier: /* Register with no answer from registrar */

2016-06-23T13:47:01Z

← Older revision		Revision as of 09:47, 23 June 2016
Line 38:		Line 38:

	===Register with no answer from registrar ===		===Register with no answer from registrar ===
	~~This example~~ shows the retransmission of SIP REGISTER over UDP. The request is retransmitted for 32 seconds before the request transaction timeout, then a new SIP REGISTER is sent after 5 seconds. Over TCP, a new ~~request would be transmitted~~ every 5 seconds.		The message flow below shows the retransmission of SIP REGISTER '''over UDP'''. The request is retransmitted for 32 seconds before the request transaction timeout, then a new SIP REGISTER is sent after 5 seconds.
			Over TCP, if the SIP registrar does not listen on the TCP port, a new TCP connection is retried every 5 seconds. If the TCP connection is established but no SIP responses returned by the Registrar, the transaction timeout after 32s and then a new SIP REGISTER is sent after 5 seconds.
	[[Image:SIP_Register_no_answers.png\|500px]]		[[Image:SIP_Register_no_answers.png\|500px]]

Lucas Trottier: /* Register with no answer from registrar */

2016-06-23T13:09:43Z

← Older revision		Revision as of 09:09, 23 June 2016
Line 38:		Line 38:

	===Register with no answer from registrar ===		===Register with no answer from registrar ===
	This example shows the retransmission of SIP REGISTER over UDP. The request is retransmitted for 32 seconds before the request transaction timeout, then a new SIP REGISTER is sent after 5 seconds.		This example shows the retransmission of SIP REGISTER over UDP. The request is retransmitted for 32 seconds before the request transaction timeout, then a new SIP REGISTER is sent after 5 seconds. Over TCP, a new request would be transmitted every 5 seconds.
	[[Image:SIP_Register_no_answers.png\|500px]]		[[Image:SIP_Register_no_answers.png\|500px]]

← Older revision		Revision as of 08:53, 18 June 2018
Line 50:		Line 50:
	== Configuration ==		== Configuration ==

			*[[Toolpack:Allocating a SIP Network Access Point (NAP) F\|Allocating a SIP NAP Configuration v3.0]]
			*[[Toolpack:Allocating a SIP Network Access Point (NAP) E\|Allocating a SIP NAP Configuration v2.10]]
	*[[Toolpack:Allocating a SIP Network Access Point (NAP) D\|Allocating a SIP NAP Configuration v2.9]]		*[[Toolpack:Allocating a SIP Network Access Point (NAP) D\|Allocating a SIP NAP Configuration v2.9]]
	*[[Toolpack:Allocating a SIP Network Access Point (NAP) C\|Allocating a SIP NAP Configuration v2.8]]		*[[Toolpack:Allocating a SIP Network Access Point (NAP) C\|Allocating a SIP NAP Configuration v2.8]]
			<div class="mw-collapsible mw-collapsed" data-collapsetext="other versions" data-expandtext="Click here for other versions" style="width: 400px;">
	*[[Toolpack:Allocating a SIP Network Access Point (NAP) B\|Allocating a SIP NAP Configuration v2.7]]		*[[Toolpack:Allocating a SIP Network Access Point (NAP) B\|Allocating a SIP NAP Configuration v2.7]]
	*[[Toolpack:Allocating a SIP Network Access Point (NAP) B\|Allocating a SIP NAP Configuration v2.6]]		*[[Toolpack:Allocating a SIP Network Access Point (NAP) B\|Allocating a SIP NAP Configuration v2.6]]
	*[[Toolpack:Allocating a SIP Network Access Point (NAP) A\|Allocating a SIP NAP Configuration v2.5]]		*[[Toolpack:Allocating a SIP Network Access Point (NAP) A\|Allocating a SIP NAP Configuration v2.5]]
			</div>

	== References ==		== References ==