ld 16 new rdb trunk type did.. after that switch interface type and start arangements you have to get from your vendor.. then ld 14 new 8 type did, except for tn and route/member and cls dtn, those are default
This may help, comes from a training outline I created for my team:
1. Where you go
a. LD 16 – create route data block
b. LD 14 – create trunks
c. LD 17 – create D-channels
d. LD 21 – print trunks
e. LD 22 – print D-channels
2. Identifying trunk groups
a. LTM
b. PRT RDB
c. MUS, DID, TIE, RAN, COT
d. Renaming designations
3. Universal Trunk card
a. 8 ports, 0 – 7
b. Punched on every other port
4. Create CO trunk group
a. Get number for ACOD
b. Create RDB in LD 16
i. TYPE – RDB
ii. ROUT – XX number for group
iii. DES – name for group
iv. TKTP – type of route (COT)
v. DTRK – digital trunk? (NO)
vi. ISDN – ISDN route? (NO)
vii. ICOG – incoming or outgoing route? (IAO) for incoming and outgoing
viii. ACOD– XXXX access code number for group
ix. CDR – call detail recording? (YES)
1. INC – CDR on incoming calls? (YES)
2. LAST – CDR on redirected calls? (YES)
3. QREC – CDR on queue calls? (YES)
4. OAL – CDR on outgoing calls? (YES)
5. AIA – Answered calls identification allowed (YES)
6. OAN – CDR timing starts on answer supervision? (NO)
7. OPD – outpulsed digits? (YES)
8. CDRX – CDR on multiple call transfer (YES)
x. MUS – music route? (YES)
xi. MRT – XX Music route number
c. Create trunk members in LD 14
i. TYPE – type of trunk (COT)
ii. TN – XXX X XX XX – TN of trunk
iii. DES – Name for trunk
iv. CUST – 0
v. NCOS – network class of service if trunk could make trunk-trunk call
vi. RTMB – Route and member – RR MM
vii. SIGL – Signaling type (will usually be GRD)
viii. CLS – class of service (UNR DTN)\
ix. TKID – Trunk ID – optional identifier for trunk
you will not need a dch of course or ld 17 21 96 or 60.. build the route, and one trunk, take the default if the switch will let you and you don't know the prompt.. then post questions as they come up. i could post a did route and trunk but without the start type, interface type etc it would be worse then default
yeah, should've deleted section 1. was part of a training document I created for my team on building all kinds of trunks. There were other parts that spoke to building T-1's and d-channels.
COT and analog DID trunks will only be using LD14, LD16, and LD 21
True, but analog comes in handy for backup and we always use them for 911 and for modem dial in. Nothing worse than a T1 going down and your only access to the switch is through that T1.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.