Call direction settings can be implemented at either end of a trunk route.
You can check a route on the Meridian 1 by following these steps:
- Print out the route data block RDB using overlay LD 21:
ROUT Route number to be printed or carriage return to print data for all routes.
ACOD Access code for the route. Used only if the ACOD is known and not the route number or carriage return.
- Find the prompt ICOG (Incoming and/or Outgoing).
One of the following values will be set for this prompt.
- IAO Incoming and Outgoing.
- ICT Incoming only Trunk.
- OGT Outgoing only Trunk.
Here are a few other checks to make to determine the direction of traffic:
- Although the route could be set to incoming and outgoing (both-way), the Route List indexes may not direct an outgoing call to a particular route. It would, in effect, be an incoming route.
- The TGAR/TARG settings may also affect outgoing access to a particular route.
- Sometimes the serving exchange or distant PBX in the case of a network-connected switch may place restrictions on the direction of traffic. These may have priority over the Meridian setting. The direction of traffic flow needs to be determined for both ends.
- A Direct Dialling In route implies by definition, that it is an incoming only route. This is not always the case. It carries incoming traffic directly to the console and extension users but if traffic conditions allow, it makes economic sense to use it for outgoing calls.
Only trained system administrators can make these changes:
learn how to get trained