1.5 Administrator's Guide

  1. Home
  2. Docs
  3. 1.5 Administrator’s Guide
  4. Commissioning the unit
  5. FlexPaths
  6. FlexPath Fundamentals

FlexPath Fundamentals

Every SIP or FXS Extension Port, FXO, BRI or PRI Trunk and VoIP Provider Trunk is a candidate for FlexPath routing.

In the FlexPath configuration panel, all these ports are displayed in a tree structure in the right hand column of the screen, along with the selected routing path for each port. By default, no FlexPaths are defined and every port is displayed with the “default” path.

A port configured in the “default” context will route as follows:

  • FXS, SIP phone port – routed as internal extensions, i.e. access to internal destinations and Outbound routes.

  • FXO, BRI, PRI, VoIP trunks – routed as inbound, i.e. access to Inbound routes and DID mapped extensions only

In order to change the default routing, one or more FlexPaths are created, and one or more extension ports or trunks are “placed into” the FlexPath. A port that is mapped to a FlexPath is indicated in the tree on the right as <port name> -> <FlexPath name> instead of <port name> -> default. Right clicking on the port text allows selection of default or any of the configured FlexPaths.

An extensions port or trunk assigned to a particular FlexPath follows the routing rules of that FlexPath instead of the default routing as described above.

FlexPaths are also available as destinations for Inbound routes (on the Inbound panel) – i.e. custom FlexPath routing can be applied after initial Inbound routing. In this case, the trunk port will typically be assigned to the default routing context to enable normal Inbound handling.

Each FlexPath has the following:

  • A name and description

  • A number of configuration parameters

  • One or more FlexPath Routes

Types of FlexPath Routes available are as follows:

  • Include – the selected routing set is simply included (routing sets include Inbound, Internal, other FlexPaths and Outbound routes)

  • Match – a pattern for matching dialled number/DID and/or CID is configured, along with a destination route set as above and an optional transform to the dialled number. In this case, only matching numbers are routed.

  • Start – a route set is selected for calls with no dialled number information.