View source for Routing Script Tutorial: Route Parameters and Call Routing

{{DISPLAYTITLE:Route Parameters and Call Routing}}
== Route parameters  ==

All call routes may have these parameters: 

*calling 
*called 
*nap 
*remapped_calling 
*remapped_called 
*remapped_nap 
*remapped_destination_leg_profile (called remapped_profile prior to Toolpack 2.9)
*remapped_source_leg_profile (called remapped_incoming_profile prior to Toolpack 2.9)


Example:

  route[:remapped_nap]



{| class="wikitable"

|[[File:NoteIcon.png|100px]]
| You can add dynamic route attributes using the Web Portal. These attributes can be referenced by their name.

For example:

*priority
*weight
|}
<br><br>


== Routing calls toward registered users ==
Static routes normally choose an outbound NAP to forward the call to. It is also possible to create routes from which the outbound NAP is dynamically chosen by matching a registered user (when using [[Sip_registration_forwarding|SIP registration forwarding]]).

More information can be found [[Sip_registration_forwarding#SIP_Calls_routing|here]] about the way to control the [[Sip_registration_forwarding#SIP_Calls_routing|priority of "dynamic" vs "static" routes]].

More information can be found [[#Registered_Users_Information|here]] about using routing scripts to access registered users information during call routing.

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