LIM CONFIGURATIONS FOR PRIVATE NETWORK CONNECTIONS LBI-39039B
61
7. LIM CONFIGURATIONS FOR PRIVATE NETWORK CONNECTIONS
The Private Network is considered to be another PBX to which the MD110 connects, as well as a true Private Network
the customer may own or lease. When connecting to another PBX, number conflicts may occur. The following codes are
recommended for directing calls out of the MD110. If "8" is used for access to the PBX for outbound calls and the basic
configuration script is followed, then the "7" for EDACS inbound calls is not necessary and direct dialing of the LID after
DISA dial tone can still be used.
LCR
Number
EDACS 7
Private Network 8
Public Network 9
•• Tie lines are used between the MD110 and the other PBX, not CO type trunks or lines.
•• If the other PBX allows connection to lines without line clearing, the information below should be considered.
7.1. NORTH AMERICA T1 TIE LINES
With Line Clearing and Without B-Answer
The following information is not in the basic script file and must be added if used. Please refer to section 2.2 for a
discussion of line clearing and B-answer supervision.
7.1.1. Route Class
ROCAI
ROU 2X This information must be added to the script
file. X will be 0-9. Make the first Private
Network route 20.
SEL
DID characteristics 0 No intercept
Incoming calls 1 Allowed
Outgoing trunk selection 1 Even load distribution
Terminal route characteristics
(outgoing)
0 Normal route
Alternate Route Selection (incoming) 0 Permitted
Customer affiliation 00 No tenant group
Virtual network calls 1 No
Malicious call tracing 0 No
Default FRL category 0 Lowest level
Default CSI category 0 Normal extension
Receipt of FRL 0 No TCM received
TRM
Transmission Category 5 Digital Tie trunk
To Next Page
Loading...
