Outbound Call Routing - Vertical Xcelerator IP Application Note

You can see that the data that was in route table no. 1 was moved to route table no. 2. and then
the extensions that reside in Scottsdale(150-175) where input on route table no. 1.
Route table no. 1 data is as follows:
From: 150
•
To: 175
•
Min: 3 (number of digits expected)
•
Max: 3 (number of digits expected)
•
Delete: 0 (number of digits to delete on leading edge)
•
Insert: N/A (number of digits to insert on the leading edge)
•
Destination: IG Expansion, with Scottsdale as the network link to use to establish the call.
•
The same entries need to be configured at the Scottsdale Xcelerator IP. Below is a screen shot of
what the Scottsdale Xcelerator IP Call Routing Table should look like.
With this configuration station calls between these 2 sites will route correctly. This configuration
will also allow incoming calls on either site to be transferred to an extension at the remote site.

OUTBOUND CALL ROUTING

In this section we will look at routing an outbound call across the network to access trunks on a
remote Xcelerator IP. The area code for phoenix is 602, and the area code for Scottsdale is 480.
In Phoenix if a user wanted to make a call to the 480 area code and wanted to use the trunks out
of Scottsdale the configuration would look like this in Phoenix:
6 July 2007