Route Optimization
Print View
by: Chris McAndrew
Total views: 10
Word Count: 782
Description
Route optimization will automatically take place whenever a call transfer is not using an optimal route. Users will probably not even be aware that route optimization is taking place.
Conditions
The following conditions apply to route optimization:
· MSDN/DPNSS Voice I (or MSAN/DPNSS) and MSDN/DPNSS Voice IV feature packages must be enabled
· Route optimization applies only to voice calls.
· Route optimization does not apply to calls that have been forwarded or to calls that have been rerouted from a set.
· The network must be programmed with a uniform numbering plan.
· Automatic route selection (ARS) programming on all nodes should reflect the optimal network routing.
· As route optimization involves conferencing, the number of available conference circuits will determine the number of concurrent route optimizations and real conferences possible.
· Maximum Trunks in Conference field on the System Options Assignment form must be greater than 0.
· The call will be dropped if a main controller activity switch occurs during the conference phase of a route optimization attempt.
· Neither party can activate any features during a route optimization attempt.
· If the answering party attempts to activate a feature during the route optimization attempt, the attempt is ignored.
· If the calling PABX receives an intrusion notification in response to the route optimization request, the route optimization attempt is aborted.
Programming
Programming the route optimization feature involves five fields on the System Options Assignment form:
· Route Optimization Establishment Timer (10s - 120s)
· Route Optimization Attempts per call (0 - 3)
· Route Optimization Network ID (max 7 digits)
· Route Optimization Trailing Digit
Note: As Route optimization makes use of conferencing, the “Maximum Trunks in Conference field on the System Options Assignment form must be set to a value greater than one.
(a) Route Optimization Establishment Timer: Sets the time allowed to establish an optimum route call. The default is 10 seconds. This value should be extended as the size of the network increases.
(b) Route Optimization Attempts per call: Sets the number of route optimization attempts to be made for each call. The default is 3 attempts. A value of zero disables route optimization.
(c) Route Optimization Network ID: Identifies the PABX for network routing. The primary node ID should be used if one exists. If no primary node ID exists, use the ARS value that will cause calls to be routed to this PABX.
(d) Route Optimization Trailing Digits: Enter the number of digits that will follow the Network ID in the dialing string. This should match the uniform numbering plan in use in the network.
Operation
No user action is required to activate route optimization once it is installed on the system. The only noticeable effect is that the caller is not permitted to use a feature involving DPNSS signaling during a route optimization attempt.
Route optimization involves the following system actions:
1. Thirty seconds after a voice call has been established, the calling PABX sends a route optimization request to the answering PABX. The delay allows a user to activate a feature (most likely attendant transfer).
2. The Route Optimization Establishment Timer starts. The timer allows a CDE programmed amount of time for successful establishment of a new, optimal call (default 10 seconds). Timer expiry is treated as a rejection.
3. A route optimization request may be rejected for a number of reasons (see Conditions, above). If rejected, the calling PABX will try again in 60 seconds. The number of retries is programmable in CDE, up to a maximum of 3.
4. If the request is not rejected, the answering PABX selects a free and optimal DPNSS channel, and establishes a call to the original calling party. Only the first ARS routing is accepted.
5. The original calling PABX conferences the new incoming call with the original call, and sends a message to the answering PABX indicating that the optimization can be completed.
6. The answering PABX transfers the original channel to the new channel, and sends a message back to confirm that this has been done. The original calling PABX then drops the original channel, and route optimization is complete.
Route Optimization Flag in SMDR Reports
An SMDR call record will be generated for both the pre-optimized and post-optimized trunks. The pre-optimized trunk is designated by a lower case r and the post-optimized trunk by an upper case R, in column 85 or 96 (with the SMDR option Extended Digit Length enabled) of the SMDR call record.
|
|
