Actions

Route Parameters and Call Routing

Revision as of 12:35, 29 March 2024 by Allyntree (talk | contribs) (Created page with "{{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" |100px | You can add dynamic r...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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]
You can add dynamic route attributes using the Web Portal. These attributes can be referenced by their name.

For example:

  • priority
  • weight




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).

More information can be found here about the way to control the priority of "dynamic" vs "static" routes.

More information can be found here about using routing scripts to access registered users information during call routing.