Static Routes

Overview

9Line's Single Route engine provides Static Routing, a useful feature when other call-matching mechanisms do not provide the desired functionality.

Static Routes evaluate the user portion (user@domain.com) of the From header, and when a match is found, use the assigned Location.

Requirements

You must contact your 9Line Account Manager to add this feature to your service.
Static Routes are available only at the Parent Organization level.
- For Enterprise customers, this is your primary organization.
- BroadWorks carriers must ensure their Static Routes are installed at the Parent level and the Parent organization contains the SBC IP addresses sending static route calls to 9Line.
Your equipment must be configured to accept calls from 9Line with the exact same user@domain.com format as delivered to 9Line for purposes of emergency callback.
For example, if your "From" is [email protected] to 9Line, we will send calls "To" [email protected] when returning the call to your SBC.
A 9Line Location must exist before creating the route.
You can use the API or import feature to create static routes and locations simultaneously and in bulk.

Configuration

Login to the 9Line Portal
Ensure you are in the Parent organization by viewing the context name in the top left corner. Switch to your Parent organization if necessary, Management → Organizations.
Navigate to Management → Static Routes.
Click Create Static Route to create a new entry.
Complete the required fields:
- A descriptive name for the route;
- The user portion of the pattern to match, e.g. if the URI is [email protected] then you would enter "1234" without the quotes;
- Enter the 9Line Location should be used when this pattern is matched.

Operation

Once the Static Route feature is configured, any calls that match the pattern will be assigned a 9Line-managed telephone number, and the Location will be inserted into the call.

As a reminder, return calls from the PSAP will be returned to your SBC with the same [email protected] SIP URI.