Aastra OpenCom X320 User Guide - Page 140
Prefix for dest. call, number at incoming internal, Legend, PBX Networking, Technical Details
View all Aastra OpenCom X320 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 140 highlights
PBX Networking Technical Details Some of the features possible in Q.SIG are not supported by OpenCom X320 with all their options, for example callback on busy within the Q.SIG network. The call categories defined in Q.SIG (e.g. Emergency Call, Operator, Normal) and the Q.SIG name transmission feature ("user names") are fully supported. The code digits to be used for seizing a route with open numbering are not transmitted to the destination PBX and thus cannot be evaluated by it. To reseize a route (for example for a callback), you must set the appropriate digit prefixes in the trunk group configuration for the routes to be reseized. Tip: If, for example, you are configuring a route which can be seized using routing code "5" and have selected one or more bundles for this route, change the Prefix for dest. call number at incoming internal setting to "5" for this bundle in order to enable the route to be reseized. Due to their hardware properties, not all S0 ports of the OpenCom X320 can be fully used for TK system networking. Depending on the type of system, some ports can only be operated in the L1-Master mode or the L1-Slave mode. The external S0 ports can be set according to the following table. OpenCom X320 S0 1 S0 2 S M/S Legend S = Slave M/S = Master/Slave M = Master Note: The S0 ports on extension cards can be operated in both the L1-Master mode as well as the L1-Slave mode. 138