Routing Script Tutorial: DNS Query - Revision history

Allyntree at 15:23, 3 April 2024

2024-04-03T15:23:53Z

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

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

Allyntree: /* Add dynamic routes */

2024-04-03T14:53:41Z

Add dynamic routes

← Older revision		Revision as of 10:53, 3 April 2024
Line 20:		Line 20:
	Similarly to ENUM Query, the DNS query could also create dynamic routes base on DNS query responses. This could be requested using the "add_dynamic_routes" call parameter:		Similarly to ENUM Query, the DNS query could also create dynamic routes base on DNS query responses. This could be requested using the "add_dynamic_routes" call parameter:

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

	The "base_routing.rb" script version should be greater then 1.37 in order to allow dynamic routes creation base on DNS query responses.		The "base_routing.rb" script version should be greater then 1.37 in order to allow dynamic routes creation base on DNS query responses.

Allyntree: /* Add dynamic routes */

2024-04-03T14:53:21Z

Add dynamic routes

← Older revision		Revision as of 10:53, 3 April 2024
Line 30:		Line 30:
	It is required to modify main routing script (i.e. simple_routing_sbc.rb) to forward IP/port values from params[:routes] to params[:call] like we are doing for NAP. See following example:		It is required to modify main routing script (i.e. simple_routing_sbc.rb) to forward IP/port values from params[:routes] to params[:call] like we are doing for NAP. See following example:

			----
	<blockquote>		<blockquote>
	...		...
Line 42:		Line 43:
	...		...
	</blockquote>		</blockquote>
			----

Allyntree at 14:52, 3 April 2024

2024-04-03T14:52:55Z

← Older revision		Revision as of 10:52, 3 April 2024
Line 5:		Line 5:

	When DNS Query completes, the routing script is called again with the result. The params[:dns_query] object will be filled with the DNS Query attributes from the responses. The DNS query responses are available through params[:dns_query][:responses_list] call parameters:		When DNS Query completes, the routing script is called again with the result. The params[:dns_query] object will be filled with the DNS Query attributes from the responses. The DNS query responses are available through params[:dns_query][:responses_list] call parameters:
			----

	<blockquote>		<blockquote>
Line 13:		Line 14:
	:preference=>"2", :priority=>"1", :weight=>"10"}]		:preference=>"2", :priority=>"1", :weight=>"10"}]
	</blockquote>		</blockquote>
			----

	== Add dynamic routes ==		== Add dynamic routes ==

Allyntree at 14:52, 3 April 2024

2024-04-03T14:52:20Z

← Older revision		Revision as of 10:52, 3 April 2024
Line 18:		Line 18:
	Similarly to ENUM Query, the DNS query could also create dynamic routes base on DNS query responses. This could be requested using the "add_dynamic_routes" call parameter:		Similarly to ENUM Query, the DNS query could also create dynamic routes base on DNS query responses. This could be requested using the "add_dynamic_routes" call parameter:

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

	The "base_routing.rb" script version should be greater then 1.37 in order to allow dynamic routes creation base on DNS query responses.		The "base_routing.rb" script version should be greater then 1.37 in order to allow dynamic routes creation base on DNS query responses.
Line 28:		Line 28:
	It is required to modify main routing script (i.e. simple_routing_sbc.rb) to forward IP/port values from params[:routes] to params[:call] like we are doing for NAP. See following example:		It is required to modify main routing script (i.e. simple_routing_sbc.rb) to forward IP/port values from params[:routes] to params[:call] like we are doing for NAP. See following example:

	<~~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
Line 39:		Line 39:
	route_remap :call_field_name => :nap_proxy_port, :route_field_name => :remapped_nap_proxy_port		route_remap :call_field_name => :nap_proxy_port, :route_field_name => :remapped_nap_proxy_port
	...		...
	</~~code~~>		</blockquote>

Allyntree: /* Introduction */

2024-04-03T14:50:54Z

Introduction

← Older revision		Revision as of 10:50, 3 April 2024
Line 6:		Line 6:
	When DNS Query completes, the routing script is called again with the result. The params[:dns_query] object will be filled with the DNS Query attributes from the responses. The DNS query responses are available through params[:dns_query][:responses_list] call parameters:		When DNS Query completes, the routing script is called again with the result. The params[:dns_query] object will be filled with 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 12:		Line 12:
	{: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 ==

Allyntree: /* Add dynamic routes */

2024-04-01T13:23:36Z

Add dynamic routes

← Older revision		Revision as of 09:23, 1 April 2024
Line 28:		Line 28:
	It is required to modify main routing script (i.e. simple_routing_sbc.rb) to forward IP/port values from params[:routes] to params[:call] like we are doing for NAP. See following example:		It is required to modify main routing script (i.e. simple_routing_sbc.rb) to forward IP/port values from params[:routes] to params[:call] like we are doing for NAP. See following example:

	< code>		<code>
	...		...
	# 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
Line 39:		Line 39:
	route_remap :call_field_name => :nap_proxy_port, :route_field_name => :remapped_nap_proxy_port		route_remap :call_field_name => :nap_proxy_port, :route_field_name => :remapped_nap_proxy_port
	...		...
	< /code>		</code>

Allyntree at 13:23, 1 April 2024

2024-04-01T13:23:13Z

← Older revision		Revision as of 09:23, 1 April 2024
Line 6:		Line 6:
	When DNS Query completes, the routing script is called again with the result. The params[:dns_query] object will be filled with the DNS Query attributes from the responses. The DNS query responses are available through params[:dns_query][:responses_list] call parameters:		When DNS Query completes, the routing script is called again with the result. The params[:dns_query] object will be filled with the DNS Query attributes from the responses. The DNS query responses are available through params[:dns_query][:responses_list] call parameters:

	< code>		<code>
	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 12:		Line 12:
	{: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>		</code>

	== Add dynamic routes ==		== Add dynamic routes ==
Line 18:		Line 18:
	Similarly to ENUM Query, the DNS query could also create dynamic routes base on DNS query responses. This could be requested using the "add_dynamic_routes" call parameter:		Similarly to ENUM Query, the DNS query could also create dynamic routes base on DNS query responses. This could be requested using the "add_dynamic_routes" call parameter:

	< code>		<code>
	params[:dns_query][:add_dynamic_routes] = true		params[:dns_query][:add_dynamic_routes] = true
	< /code>		</code>

	The "base_routing.rb" script version should be greater then 1.37 in order to allow dynamic routes creation base on DNS query responses.		The "base_routing.rb" script version should be greater then 1.37 in order to allow dynamic routes creation base on DNS query responses.

Allyntree: Created page with "{{DISPLAYTITLE:DNS Query}} == Introduction == Similarly to ENUM query, starting with release 3.1, it is possible to issue DNS Query requests to DNS servers from routing scripts. This could be used to skip the ENUM Query part when the called uri is already known but still need to get the matching outgoing NAP, NAP proxy IP and port. To do so, the params[:dns_query] object must be filled with the required DNS Query attributes params[:dns_query][:fqdn] and #Refuse|an exc..."

2024-03-29T18:06:52Z

Created page with "{{DISPLAYTITLE:DNS Query}} == Introduction == Similarly to ENUM query, starting with release 3.1, it is possible to issue DNS Query requests to DNS servers from routing scripts. This could be used to skip the ENUM Query part when the called uri is already known but still need to get the matching outgoing NAP, NAP proxy IP and port. To do so, the params[:dns_query] object must be filled with the required DNS Query attributes params[:dns_query][:fqdn] and #Refuse|an exc..."

New page

{{DISPLAYTITLE:DNS Query}}

== Introduction ==
Similarly to ENUM query, starting with release 3.1, it is possible to issue DNS Query requests to DNS servers from routing scripts. This could be used to skip the ENUM Query part when the called uri is already known but still need to get the matching outgoing NAP, NAP proxy IP and port. To do so, the params[:dns_query] object must be filled with the required DNS Query attributes params[:dns_query][:fqdn] and [[#Refuse|an exception must be raised]] with reason :dns_query_required.

When DNS Query completes, the routing script is called again with the result. The params[:dns_query] object will be filled with the DNS Query attributes from the responses. The DNS query responses are available through params[:dns_query][:responses_list] call parameters:

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

== Add dynamic routes ==

Similarly to ENUM Query, the DNS query could also create dynamic routes base on DNS query responses. This could be requested using the "add_dynamic_routes" call parameter:

< code>
params[:dns_query][:add_dynamic_routes] = true
< /code>

The "base_routing.rb" script version should be greater then 1.37 in order to allow dynamic routes creation base on DNS query responses.

When requesting to add_dynamic_routes, the dns_query responses are used to create routes. Make sure that your configuration include a route with remapped_nap = "Registered or DNS users". A route will be created for each DNS query responses. The routes "remapped_nap" takes NAP value from DNS query responses.

It is required to modify main routing script (i.e. simple_routing_sbc.rb) to forward IP/port values from params[:routes] to params[:call] like we are doing for NAP. See following example:

< code>
...
# 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

# This will select the outgoing NAP proxy ip address for this call according to the "remapped_nap_proxy_ip" route parameter
route_remap :call_field_name => :nap_proxy_ip, :route_field_name => :remapped_nap_proxy_ip

# This will select the outgoing NAP proxy port for this call according to the "remapped_nap_proxy_port" route parameter
route_remap :call_field_name => :nap_proxy_port, :route_field_name => :remapped_nap_proxy_port
...
< /code>