Incoming Call Route Form
Additional configuration information
For additional information on the Tag setting, see Call Tagging.
Default Blank Call Routes
Incoming call routes are used to match call received with destinations. Routes can be based on the incoming line group, the type of call, incoming digits or the caller's ICLID.
If a range of MSN/DID numbers has been issued, this form can be populated using the MSN Configuration tool. In Manager, see .
By default the configuration contains two incoming calls routes; one set for Any Voice calls (including analog modem) and one for Any Data calls. While the destination of these default routes can be changed, it is strongly recommended that the default routes are not deleted.
Deleting the default call routes, may cause busy tone to be returned to any incoming external call that does not match any incoming call route.
Setting any route to a blank destination field, may cause the incoming number to be checked against system short codes for a match.
This may lead to the call being rerouted off-switch.
Calls received on IP, S0 and QSIG trunks do not use incoming call routes. Routing for these is based on incoming number received as if dialed on-switch. Line short codes on those trunks can be used to modify the incoming digits.
If there is no matching incoming call route for a call, matching is attempted against system short codes and finally against voicemail nodes before the call is dropped.
For SIP calls, the following fields are used for call matching:
Line Group ID This field is matched against the Incoming Group settings of the SIP URI (Line | SIP URI).
This must be an exact match.
Incoming Number This field can be used to match the called details (TO) in the SIP header of incoming calls. It can contain a number, SIP URI or Tel URI.
For SIP URI's the domain part of the URI is removed before matching by incoming call routing occurs. For example, for the SIP URI [email protected] , only the user part of the URI, ie. mysip, is used for matching.
The Call Routing Method setting of the SIP line can be used to select whether the value used for incoming number matching is taken from the To Header or the Request URI information provided with incoming calls on that line.
Incoming CLI This field can be used to match the calling details (FROM) in the SDP header of incoming SIP calls.
It can contain a number, SIP URI, Tel URI or IP address received with SIP calls. For all types of incoming CLI except IP addresses a partial record can be used to achieve the match, records being read from left to right. For IP addresses only full record matching is supported.
These settings can be edited online. Changes to these settings do not require a reboot of the system.
For a Server Edition network, these settings can be configured at the network level and are then automatically replicated in the configuration of all systems in the network.
How to create a new DDI or DID number
They can only be seen and edited at the individual system configuration level if record consolidation is switched off.
Incoming Call Matching Fields
The following fields are used to determine if the Incoming Call Route is a potential match for the incoming call.
By default the fields are used for matching in the order shown starting with Bearer Capability.
Call Setting Fields
For calls routed using this Incoming Call Route, the settings of the following fields are applied to the call regardless of the destination.
In cases where a particular Incoming Number is routed to a specific individual user, the system will attempt to use that Incoming Number as the user's caller ID when they make outgoing calls if no other number is specified.
This requires that the Incoming Number is a full number suitable for user as outgoing caller ID and acceptable to the line provider.
When this is the case, the character i can also be added to the Incoming Number field. This character does not affect the incoming call routing.
Setting up outbound route filtering in BGP
However when the same Incoming Number is used for an outgoing caller ID, the calling party number plan is set to ISDN and the type is set to National. This option may be required by some network providers.
For internal calls being forwarded or twinned, if multiple incoming call route entries match the extension number used as caller ID, the first entry created is used.
This entry should start with a “-” character (meaning fixed length) and provide the full national number. These entries do not support wildcards.
If additional entries are required for incoming call routing, they should be created after the entry required for reverse lookup.