Routing Script Tutorial: ENUM Query - Revision history

Allyntree: /* Add dynamic routes */

2024-04-03T15:17:53Z

Add dynamic routes

← Older revision		Revision as of 11:17, 3 April 2024
Line 102:		Line 102:
	</blockquote>		</blockquote>

	[[Image:BackToMain.png\|thumb\|center\|~~4000px~~\|link=https://docs.telcobridges.com/Routing_script_tutorial:Mini_Development_Guide]]		[[Image:BackToMain.png\|thumb\|center\|400px\|link=https://docs.telcobridges.com/Routing_script_tutorial:Mini_Development_Guide]]

Allyntree: /* Add dynamic routes */

2024-04-03T15:17:35Z

Add dynamic routes

← Older revision		Revision as of 11:17, 3 April 2024
Line 102:		Line 102:
	</blockquote>		</blockquote>

	[[Image:BackToMain.png\|thumb\|center\|~~250px~~\|link=https://docs.telcobridges.com/Routing_script_tutorial:Mini_Development_Guide]]		[[Image:BackToMain.png\|thumb\|center\|4000px\|link=https://docs.telcobridges.com/Routing_script_tutorial:Mini_Development_Guide]]

Allyntree: /* Add dynamic routes */

2024-04-03T15:17:16Z

Add dynamic routes

← Older revision		Revision as of 11:17, 3 April 2024
Line 102:		Line 102:
	</blockquote>		</blockquote>

	[[Image:BackToMain.png\|thumb\|center\|~~100px~~\|link=https://docs.telcobridges.com/Routing_script_tutorial:Mini_Development_Guide]]		[[Image:BackToMain.png\|thumb\|center\|250px\|link=https://docs.telcobridges.com/Routing_script_tutorial:Mini_Development_Guide]]

Allyntree: /* Add dynamic routes */

2024-04-03T15:16:56Z

Add dynamic routes

← Older revision		Revision as of 11:16, 3 April 2024
Line 102:		Line 102:
	</blockquote>		</blockquote>

	[[Image:BackToMain.png\|~~frame~~\|center\|100px\|link=https://docs.telcobridges.com/Routing_script_tutorial:Mini_Development_Guide]]		[[Image:BackToMain.png\|thumb\|center\|100px\|link=https://docs.telcobridges.com/Routing_script_tutorial:Mini_Development_Guide]]

Allyntree: /* Add dynamic routes */

2024-04-03T15:16:36Z

Add dynamic routes

← Older revision		Revision as of 11:16, 3 April 2024
Line 102:		Line 102:
	</blockquote>		</blockquote>

	[[Image:BackToMain.png\|frame\|center\|~~250px~~\|link=https://docs.telcobridges.com/Routing_script_tutorial:Mini_Development_Guide]]		[[Image:BackToMain.png\|frame\|center\|100px\|link=https://docs.telcobridges.com/Routing_script_tutorial:Mini_Development_Guide]]

Allyntree: /* Add dynamic routes */

2024-04-03T15:16:08Z

Add dynamic routes

← Older revision		Revision as of 11:16, 3 April 2024
Line 102:		Line 102:
	</blockquote>		</blockquote>

	[[Image:BackToMain.png\|center\|250px\|link=https://docs.telcobridges.com/Routing_script_tutorial:Mini_Development_Guide]]		[[Image:BackToMain.png\|frame\|center\|250px\|link=https://docs.telcobridges.com/Routing_script_tutorial:Mini_Development_Guide]]

Allyntree: /* Add dynamic routes */

2024-04-03T15:14:34Z

Add dynamic routes

← Older revision		Revision as of 11:14, 3 April 2024
Line 102:		Line 102:
	</blockquote>		</blockquote>

	[[Image:BackToMain.png\|250px\|link=https://docs.telcobridges.com/Routing_script_tutorial:Mini_Development_Guide]]		[[Image:BackToMain.png\|center\|250px\|link=https://docs.telcobridges.com/Routing_script_tutorial:Mini_Development_Guide]]

Allyntree: /* Add dynamic routes */

2024-04-03T15:12:33Z

Add dynamic routes

← Older revision		Revision as of 11:12, 3 April 2024
Line 102:		Line 102:
	</blockquote>		</blockquote>

	[[Image:BackToMain.png\|250px\|link=~~MediaWiki~~]]		[[Image:BackToMain.png\|250px\|link=https://docs.telcobridges.com/Routing_script_tutorial:Mini_Development_Guide]]

Allyntree at 15:11, 3 April 2024

2024-04-03T15:11:28Z

← Older revision		Revision as of 11:11, 3 April 2024
Line 101:		Line 101:
	----		----
	</blockquote>		</blockquote>

			[[Image:BackToMain.png\|250px\|link=MediaWiki]]

Allyntree at 14:56, 3 April 2024

2024-04-03T14:56:36Z

← Older revision		Revision as of 10:56, 3 April 2024
Line 21:		Line 21:
	Example:		Example:

	< ~~code~~>		----
			<blockquote>
	params[:enum_query][:responses_list]		params[:enum_query][:responses_list]
	[{:order=>"200", :preference=>"10", :uri=>"!^03111.*$!sip:123456782@example-2.com!"},		[{:order=>"200", :preference=>"10", :uri=>"!^03111.*$!sip:123456782@example-2.com!"},
	{:order=>"100", :preference=>"1", :uri=>"!^03222.*$!sip:123456782@example-3.com!"},		{:order=>"100", :preference=>"1", :uri=>"!^03222.*$!sip:123456782@example-3.com!"},
	{:order=>"200", :preference=>"1", :uri=>"!^03111.*$!sip:123456782@example-1.com!"}]		{:order=>"200", :preference=>"1", :uri=>"!^03111.*$!sip:123456782@example-1.com!"}]
	< /~~code~~>		</blockquote>
			----

	Using enum_called_remap.rb before filter script allows handling of ENUM query requests/responses. The match and replace regular expression from ENUM query responses are applied to params[:call][:called] to get "new called". This script allows update of the call parameters according to "new called" value. Refer to enum_called_remap.rb before filter script to get instructions on how to integrate this script into the main routing script (i.e. simple_routing_sbc.rb):		Using enum_called_remap.rb before filter script allows handling of ENUM query requests/responses. The match and replace regular expression from ENUM query responses are applied to params[:call][:called] to get "new called". This script allows update of the call parameters according to "new called" value. Refer to enum_called_remap.rb before filter script to get instructions on how to integrate this script into the main routing script (i.e. simple_routing_sbc.rb):

	< ~~code~~>		----
			<blockquote>
	...		...
	require 'enum_called_remap' unless defined?(EnumCalledRemap)		require 'enum_called_remap' unless defined?(EnumCalledRemap)
Line 39:		Line 41:
	before_filter :method => :enum_called_remap		before_filter :method => :enum_called_remap
	...		...
	< /~~code~~>		</blockquote>
			----

	== Resolve ENUM Query down to type A records ==		== Resolve ENUM Query down to type A records ==
Line 45:		Line 48:
	The ENUM query could also resolve uri from responses and get matching outgoing NAP, NAP proxy IP and port through a sequence of DNS queries (i.e. NAPTR, SRV down to type A records). This behavior could be requested using "dns_query" parameter:		The ENUM query could also resolve uri from responses and get matching outgoing NAP, NAP proxy IP and port through a sequence of DNS queries (i.e. NAPTR, SRV down to type A records). This behavior could be requested using "dns_query" parameter:

			----
	< ~~code~~>		<blockquote>
	params[:enum_query][:dns_query] = true		params[:enum_query][:dns_query] = true
	< /~~code~~>		</blockquote>
			----

	When ENUM and DNS Queries complete, the routing script is called again with the results. The params[:enum_query] and params[:dns_query] objects will be filled with the ENUM Query and the DNS Query attributes from the responses. The DNS query responses are available through params[:dns_query][:responses_list] call parameters:		When ENUM and DNS Queries complete, the routing script is called again with the results. The params[:enum_query] and params[:dns_query] objects will be filled with the ENUM Query and the DNS Query attributes from the responses. The DNS query responses are available through params[:dns_query][:responses_list] call parameters:

	< ~~code~~>		----
			<blockquote>
	params[:dns_query][:responses_list]		params[:dns_query][:responses_list]
	[{:nap=>"NAP_UDP", :nap_proxy_ip=>"10.3.14.191", :nap_proxy_port=>"8080", :transport=>"UDP", :order=>"100",		[{:nap=>"NAP_UDP", :nap_proxy_ip=>"10.3.14.191", :nap_proxy_port=>"8080", :transport=>"UDP", :order=>"100",
Line 58:		Line 63:
	{:nap=>"NAP_TCP", :nap_proxy_ip=>"10.3.14.192", :nap_proxy_port=>"8081", :transport=>"TCP", :order=>"100",		{:nap=>"NAP_TCP", :nap_proxy_ip=>"10.3.14.192", :nap_proxy_port=>"8081", :transport=>"TCP", :order=>"100",
	:preference=>"2", :priority=>"1", :weight=>"10"}]		:preference=>"2", :priority=>"1", :weight=>"10"}]
	< /~~code~~>		</blockquote>
			----

	== Add dynamic routes ==		== Add dynamic routes ==
Line 65:		Line 70:
	The ENUM query could also add dynamic routes base on DNS query responses. This could be requested using the "add_dynamic_routes" call parameter:		The ENUM query could also add dynamic routes base on DNS query responses. This could be requested using the "add_dynamic_routes" call parameter:

	< ~~code~~>		----
			<blockquote>
	params[:enum_query][:dns_query] = true		params[:enum_query][:dns_query] = true
	params[:enum_query][:add_dynamic_routes] = true		params[:enum_query][:add_dynamic_routes] = true
	< /~~code~~>		</blockquote>
			----

	Note that it is mandatary to send DNS query to add dynamic routes.		Note that it is mandatary to send DNS query to add dynamic routes.
Line 80:		Line 86:


	< ~~code~~>		<blockquote>
	...
			---- ...
	# This will select the outgoing NAP for this call according to the "remapped_nap" route parameter		# This will select the outgoing NAP for this call according to the "remapped_nap" route parameter
	route_remap :call_field_name => :nap, :route_field_name => :remapped_nap		route_remap :call_field_name => :nap, :route_field_name => :remapped_nap
Line 92:		Line 99:
	...		...

	< /~~code~~>		----
			</blockquote>