Call Routing Server FAQ
The following topics are covered in this
FAQ:
|
Routing Server Logic Flow
What is the logical flow of routing that occurs with Routing
Server Manager?
-
When a route request arrives, it has the following information:
- EndpointId / GatewayId (name in GW)
- TrunkGroupType
- TrunkGroupId / PassThruId (name in GW)
- DNIS (Called Number)
- ANI (Calling Number)
- Remote IP (in case of IP call)
The Routing Server tries to match the EndpointId and the TrunkGroupId,
and tries to determine if there is an attached Ingress Group. If you
have any of the items misconfigured, you will see the error:
"NO INGRESS GROUP ATTACHED"
-
Once the Ingress Group attached to that TrunkGroup is found, the
Routing Server looks for a Blocked number in the attached Blocked
number directory.
-
If it is an IP call, the Routing Server also looks for a Remote IP
in the AccessControl directory. (There is an optional step here if
a Subscriber/Subscriber Directory is used.)
-
If there is any matching pattern found in the Ingress Translation
Group, the Routing Server tries to translate the number, and if the
number is translated it will be treated as a new DNIS.
Note: This is done prior to routing.
-
The Routing Server then tries to find all possible Egress Groups
attached to that Ingress Group.
-
From all possible Egress Groups, the Routing Server finds all possible
attached Egress Trunks.
-
The Routing Server tries to match the DNIS for all attached Egress
Trunks, and filters out Egress Trunks.
-
The Routing Server then applies all the criteria in the order configured
in the Ingress Group, and sorts the possible EgressTrunks.
Note: The criteria only help sort the results, not
restrict them.
-
The first 3 routes are chosen from the sorted list, and the rest
of the routes are dumped.
-
The Routing Server looks for an attached Egress Translation table
for each of the 3 Egress Trunks, and tries to translate the number
separately for each route.
-
Now the Routing Server knows the Egress Trunk, Egress Endpoint IP,
and the attached Egress TrunkGroup profile. The Routing Server sends
a route response to the Gateway with the first route.
-
If the first route fails, then the Routing Server sends the second,
and then sends the third.
|
Copy Configuration from Primary to Secondary Database
I have two Routing Servers, how do I copy/replicate the database?
- On the Primary/Master box, issue the following command:
RouteServer> slave add <IP address of slave>
- On the Secondary/Slave box, issue the following command:
RouteServer> sync-master <IP address of master>
-
To confirm, type "Yes" (Note that the Y is upper case.)
This will do a one-time copy from Master to Slave. The data on the
Slave will be erased/overwritten.
|
Restrict Route Visibility to a Particular Ingress Call
Source
I want to restrict a particular call source's route visibility.
How do I achieve it?
All you need to do is create a new Ingress Group for that call source,
create a new Egress Group, attach the TrunkGroups to the newly created
Egress Group, and finally attach the Ingress Group and Egress Group.
This can be achieved by the following steps.
-
Create an Egress Group. Add a new name for the Egress Group, and
add visible TrunkGroups in that Egress Group.
-
Create a New Ingress Group for that particular Ingress Source..
Add the Ingress Group Name. Optionally, change the Routing Criteria
.
-
Go to the Advanced tab and remove the "default" Egress
Group, then move the newly created Egress Group from the "available
Egress Group" to the "selected Egress Group."
-
Assign a new Ingress group to the call source. Go to the Ingress
TrunkGroup or particular Subscriber, and change the associated Ingress
Group.
-
Submit everything and test using the Action > Testroute
utility.
|
Create Multiple IPRGs under a Single Object
The TrunkGroupId for IPRG Type TrunkGroups must be "0."
How do I support multiple IPRGs? I need to treat incoming calls differently
depending on their IP address or ANI.
To support multiple IPRGs, you do not need to create multiple TrunkGroups.
Instead, you create multiple Subscribers. Follow these steps.
-
Create a Subscriber. Add the Subscriber Name and, under the ID tab,
add either ANI or IP/SubnetMask. Optionally, under the Association
tab, you can assign the proper Ingress group. (It is OK to leave the
default Ingress Group.)
-
Create a Subscriber Directory. Add the Subscriber Directory Name,
and move the newly created Subscriber from the "Available Subscribers"
to the "Selected Subscribers" column.
-
Go to the TrunkGroup under Endpoint, and select the IPRG where you
want to support multiple incoming Subscribers. Go to the Ingress Tab,
and set the"subscriber lookup type" to either ANI or IP,
depending on what you added in step 1. Go to the Advanced Tab, and
select the newly created Subcriber Directory.
-
Activate your changes. To treat the newly created Subscriber differently,
create a new "Ingress Group," then select different routing
criteria. Assign the new Ingress Group to that Subscriber in the Subscriber
> Association tab.
|
No Ingress ServiceGroup Attached
I am getting the error message "No Ingress ServiceGroup
Attached" ( I checked, and I have the default Ingress Group attached.)
Check the following things.
-
First, make sure that on your Gateway/CallRelay that the Gateway
ID set in the RadiusInfo-RoutingServer prompt is the same as the EndpointId
set in the Endpoint window in the Routing Server Manager.
-
Check that the TrunkGroup Type is properly set.
- For IPRG H323 calls, you want to set it to IPRG-ARQ.
- For SIP calls, you might want to set it to IPRG-SIP.
-
The TrunkGroupId in the TrunkGroup window MUST match the "PassThruId"
under the TCRG or LCRG. For IPRGs, the TrunkGroupId MUST be 0.
-
The TrunkGroupId value must be between 0 to 999. The same applies
to the PassThruId when used with the Routing Server.
-
If the Ingress Group is set to something other than "default,"
make sure that there is an Egress Group attached to that Ingress group,
and at least one TrunkGroup is assigned in the EgressGroup.
|
| |
|
