Creating a new Route between Opt 61c, Opt 11c, and a PRI Gateway

[NateRD25]

Ok...Here is my problem. I have 2 locations one running CS1K and an Opt 61c connected through a signaling server for 4 digit dialing. I also have a PRI Gateway that is physically connected to the CS1K for our VoIP offices. Here is the routing information at the main location

ld 21
REQ: prt
TYPE: rdb
CUST 0
ROUT 62

TYPE RDB
CUST 00
ROUT 62
DES ZITO
TKTP TIE
M911P NO
ESN NO
CNVT NO
SAT NO
RCLS EXT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC ESS5
SBN NO
PNI 00000
SRVC NNSF
NCNA YES
NCRD YES
CHTY BCH
CTYP UKWN
INAC NO
ISAR NO
CPUB OFF
DAPC NO
BCOT 0
MBXR NO
DSEL VOD
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 7962
TCPP NO
PII NO
AUXP NO
TARG
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
ANTK
SIGO STD
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640


PAGE 002

GRD 896
SFB 3
NBS 2048
NBL 4096

IENB 5
TFD 0
VSS 0
VGD 6
DRNG NO
CDR NO
VRAT NO
MUS NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
CBQ NO
AUTH NO
TDET NO
TTBL 0
ATAN NO
PLEV 2
ALRM NO
ART 0
SGRP 0
ARDN NO
AACR NO

ld 86
RLI 18
ENTR 0
LTER NO
ROUT 62
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
VNS NO
CNV NO
EXP NO
FRL 0
DMI 0
FCI 0
FSNI 0
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO

ISET 0
NALT 5
MFRL 0
OVLL 0

REQ: ltm
CUST 0
ROUT 62

ld 21
TYPE TLST
TKTP TIE
ROUT 62
DES ZITO
TN 029 01 MBER 1 ZITTO
TN 029 02 MBER 2 ZITTO
TN 029 03 MBER 3 ZITTO
TN 029 04 MBER 4 ZITTO
TN 029 05 MBER 5 ZITTO
TN 029 06 MBER 6 ZITTO
TN 029 07 MBER 7 ZITTO
TN 029 08 MBER 8 ZITTO
TN 029 09 MBER 9 ZITTO
TN 029 10 MBER 10 ZITTO
TN 029 11 MBER 11 ZITTO
TN 029 12 MBER 12 ZITTO
TN 029 13 MBER 13 ZITTO
TN 029 14 MBER 14 ZITTO
TN 029 15 MBER 15 ZITTO
TN 029 16 MBER 16 ZITTO
TN 029 17 MBER 17 ZITTO
TN 029 18 MBER 18 ZITTO
TN 029 19 MBER 19 ZITTO
TN 029 20 MBER 20 ZITTO
TN 029 21 MBER 21 ZITTO
TN 029 22 MBER 22 ZITTO
TN 029 23 MBER 23 ZITTO

This route works at our main location. The issue is the remote location that is attached through the signaling server. I need the other location to be able to dial 4-digits and get to those extensions at our remote offices.

I started building the route but my issue now is trying to build a trunk to be a member of the route so that the call as path to get to the PRI Gateway.

 

[KCFLHRC]

So do you not know how to build the trunks? They are built in LD 14. Then you will have to create CDP entries for your 4 digit dialing.

 

[NateRD25]

I dont know what type of trunk to build in ld 14. I have read up on a bunch of different forums. I am just stuck I get errors(depending on TN I use) SCH3959 A non-PRI loop number was specified in the TN, but the route member is PRA mode. Or SCH5270 That is an invalid trunk type for XCOT, XDID, or XFEM. Valid trunk types are listed here: XCOT = CO trunks; XDID = DID trunks; XFEM = MUS, PAG, RAN, and TIE trunks. My new route looks exactly like the one I posted.

 

[KCFLHRC]

Your route determines how the trunks are built. In your case the route and trunks would be TIE. You have to make sure your loop is defined as PRI in the CEQU and not defined as a TRK.

 

[KCFLHRC]

What is your new PRI Loop #

 

[NateRD25]

Where can I find that?

 

[NateRD25]

The new Route I created is 62. Here is the new one I built at our remote location

>ld 21
PT1000

REQ: prt
TYPE: rdb
CUST 0
ROUT 62

TYPE RDB
CUST 00
ROUT 62
DES ZITO
TKTP TIE
M911P NO
ESN NO
CNVT NO
SAT NO
RCLS EXT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC ESS5
SBN NO
PNI 00000
SRVC NNSF
NCNA YES
NCRD NO
CHTY BCH
CTYP UKWN
INAC NO
ISAR NO
CPUB OFF
DAPC NO
BCOT 0
MBXR NO
DSEL VOD
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 7752
TCPP NO
PII NO
AUXP NO
TARG 01
CLEN 1
BILN NO
OABS
INST
ANTK
SIGO STD
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
GRD 896
SFB 3
NBS 2048
NBL 4096


PAGE 002


IENB 5
TFD 0
VSS 0
VGD 6
DRNG NO
CDR NO
VRAT NO
MUS NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
CBQ NO
AUTH NO
TDET NO
TTBL 0
ATAN NO
PLEV 2
ALRM NO
ART 0
SGRP 0
ARDN NO
AACR NO

 

[KCFLHRC]

Things have to happen in a logical sequence when programming a new PRI.

1. You have to define the loop in LD 17
2. You have to define the D-channel in LD 17
3. You have to build the Route in LD 16
4. You have to build the Trunks in LD 14
5. You have to build an RLI in LD 86 for your CDP entries to point to
6. You have to build your CDP entries in LD 87

 

[NateRD25]

What load can I print out what is programmed in DCH.

 

[KCFLHRC]

Print the d-channel in LD 22

REQ PRT
TYPE ADAN DCH XX where XX is your d-channel #

 

[NateRD25]

I found where to printout my loops, I think...The question now is can I use a loop that is already created? Or do I need to create a new one
TYPE adan
ADAN HIST
SIZE 30000
USER MTC SCH BUG CSC OSN
ADAN TTY 0
CTYP CPSI
DNUM 0
PORT 0
DES terminal
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC SCH BUG OSN
TTYLOG 0
BANR YES
ADAN TTY 1
CTYP PTY
DNUM 1
PORT 0
DES
FLOW NO
USER MTC SCH BUG
TTYLOG 0
BANR YES
ADAN TTY 2
CTYP MGC
IPMG 0 0
DNUM 2
PORT 2
DES CDR
BPS 1200
BITL 8
STOP 1
PARY NONE
FLOW NO
USER CTY
ADAN TTY 3
CTYP MGC
IPMG 0 0
DNUM 3
PORT 0
DES maint
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC SCH BUG
TTYLOG 0
BANR YES



PAGE 001

ADAN TTY 6
CTYP MGC
IPMG 0 1
DNUM 6
PORT 1
DES tty
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC SCH BUG OSN
TTYLOG 0
BANR YES
ADAN TTY 7
CTYP MGC
IPMG 0 1
DNUM 7
PORT 2
DES tty
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC SCH BUG
TTYLOG 0
BANR YES
ADAN TTY 8
CTYP MGC
IPMG 0 0
DNUM 8
PORT 1
DES tty
BPS 9600
BITL 8
STOP 1
PARY NONE
FLOW NO
USER MTC SCH BUG
TTYLOG 0
BANR YES
ADAN TTY 12
CTYP PTY
DNUM 12
PORT 12
DES PTY12
FLOW NO
USER MTC SCH BUG
TTYLOG 0
BANR YES
ADAN TTY 13
CTYP PTY
DNUM 13
PORT 13
DES PTY13
FLOW NO
USER MTC SCH BUG
TTYLOG 0
BANR YES
ADAN TTY 14



PAGE 002

CTYP PTY
DNUM 14
PORT 0
DES pty14
FLOW NO
USER MTC SCH BUG OSN
TTYLOG 0
BANR YES
ADAN TTY 15
CTYP PTY
DNUM 15
PORT 1
DES pty15
FLOW NO
USER MTC SCH BUG OSN
TTYLOG 0
BANR YES
ADAN DCH 16
CTYP DCIP
DES vdch
USR ISLD
ISLM 4000
SSRC 1800
OTBF 32
NASA NO
IFC SL1
CNEG 1
RLS ID 36
RCAP ND2 MWI TAT
MBGA NO
H323
OVLR NO
OVLS NO
ADAN DCH 17
CTYP MSDL
MG_CARD 000 1 01
PORT 1
DES FUTUREUSE
USR PRI
DCHL 52
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
NASA NO
IFC SL1
SIDE USR
CNEG 1
RLS ID **
RCAP ND2 MWI
MBGA NO
OVLR NO
OVLS NO
T200 3
T203 10
N200 3
N201 260
K 7

 

[NateRD25]

I have 2 DCH one with a DES of FUTUREUSE. Would I use that?

 

[NateRD25]

A bit easier to read.

REQ prt
TYPE adan dch

ADAN DCH 16
CTYP DCIP
DES vdch
USR ISLD
ISLM 4000
SSRC 1800
OTBF 32
NASA NO
IFC SL1
CNEG 1
RLS ID 36
RCAP ND2 MWI TAT
MBGA NO
H323
OVLR NO
OVLS NO
ADAN DCH 17
CTYP MSDL
MG_CARD 000 1 01
PORT 1
DES FUTUREUSE
USR PRI
DCHL 52
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
NASA NO
IFC SL1
SIDE USR
CNEG 1
RLS ID **
RCAP ND2 MWI
MBGA NO
OVLR NO
OVLS NO
T200 3
T203 10
N200 3
N201 260
K 7

 

[NateRD25]

Here is the DCH for the main site with the routing that is working correctly. I am thinking I should just mirror this.

ADAN DCH 10
CTYP MSDL
DNUM 11
PORT 1
DES zito
USR PRI
DCHL 29
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC ESS5

 

[KCFLHRC]

If that one works then yes, I would program the new one like that.

 

[NateRD25]

Ok, what would my type be in ld 17 to chg?

 

[NateRD25]

Im getting there. I have my Nortel books

 

[KCFLHRC]

You need to build the new D-channel on a spare MSDL port and wire it accordingly. It would be some thing like this

REQ CHG
Type ADAN
ADAN New DCH XX
CTYP MSDL
Port X


and so on

 

[NateRD25]

Here is what I have now.

ADAN DCH 17
CTYP MSDL
MG_CARD 000 1 01
PORT 1
DES ZITO
USR PRI
DCHL 52
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC ESS5
SIDE USR
CNEG 1
RLS ID **
RCAP ND2 MWI
MBGA NO
OVLR NO
OVLS NO
T200 3
T203 10
N200 3
N201 260
K 7