CS-1000M-MG Succession 4.5 PRI ----> Asterisk Switch

We had to do a DID trunk setup on ours. We swapped out a 61c to an Asterisk system. Their was a limitation, we had to use phantom ext's to forward dialing to sets as they were replaced to the Asterisk system. Some suggest QSIG or a Control route setup to get proper 2 way trunking. EXT to EXT worked good but we relied on the Asterisk to do the outside trunking for the new system and the 61c for those still on the 61c. We split the T-1's as they had 5.


Avaya/Nortel/NEC/Asterisk/Access Control/CCTV/DSX/Acti

After wrestling with every possible combination of settings I've managed to get all the channels active and the dch to be est confirmed instead of awaiting establishment using QSIG tie trunks. It does not, however, make calls.

When I brink the circuit up this is what I get on the Nortel side (which is set as NET)

.enll 31

PRI000 31 15

PRI000 31 15

DTA023 31

OK
.

stat 31

PRI* TRK LOOP 31 - ENBL
FFMT/LCMT/YALMT: ESF/B8Z/FDL
SERVICE RESTORE: YES
YEL ALM PROCESS: YES
ALARM STATUS : NO ALARM
CH 01 - MBSY TIE VOD * CH 02 - MBSY TIE VOD *
CH 03 - MBSY TIE VOD * CH 04 - MBSY TIE VOD *
CH 05 - MBSY TIE VOD * CH 06 - MBSY TIE VOD *
CH 07 - MBSY TIE VOD * CH 08 - MBSY TIE VOD *
CH 09 - MBSY TIE VOD * CH 10 - MBSY TIE VOD *
CH 11 - MBSY TIE VOD * CH 12 - MBSY TIE VOD *
CH 13 - MBSY TIE VOD * CH 14 - MBSY TIE VOD *
CH 15 - MBSY TIE VOD * CH 16 - MBSY TIE VOD *
CH 17 - MBSY TIE VOD * CH 18 - MBSY TIE VOD *
CH 19 - MBSY TIE VOD * CH 20 - MBSY TIE VOD *
CH 21 - MBSY TIE VOD * CH 22 - MBSY TIE VOD *
CH 23 - MBSY TIE VOD * CH 24 - DCH 31
.
DCH: 31 EST REMOTE TIME: 15:05:40 30/04/2013

DCH 31 UIPE_OMSG CC_RESTART_REQ REF 00000000 CH 0 TOD 15:05:40 CK 9AA4F024
TYPE: ALL CHANNEL

stat
DCH: 31 RLS NO RESPONSE TIME: 15:05:46 30/04/2013
31

PRI* TRK LOOP 31 - ENBL
FFMT/LCMT/YALMT: ESF/B8Z/FDL
SERVICE RESTORE: YES
YEL ALM PROCESS: YES
ALARM STATUS : NO ALARM
CH 01 - MBSY TIE VOD * CH 02 - MBSY TIE VOD *
CH 03 - MBSY TIE VOD * CH 04 - MBSY TIE VOD *
CH 05 - MBSY TIE VOD * CH 06 - MBSY TIE VOD *
CH 07 - MBSY TIE VOD * CH 08 - MBSY TIE VOD *
CH 09 - MBSY TIE VOD * CH 10 - MBSY TIE VOD *
CH 11 - MBSY TIE VOD * CH 12 - MBSY TIE VOD *
CH 13 - MBSY TIE VOD * CH 14 - MBSY TIE VOD *
CH 15 - MBSY TIE VOD * CH 16 - MBSY TIE VOD *
CH 17 - MBSY TIE VOD * CH 18 - MBSY TIE VOD *
CH 19 - MBSY TIE VOD * CH 20 - MBSY TIE VOD *
CH 21 - MBSY TIE VOD * CH 22 - MBSY TIE VOD *
CH 23 - MBSY TIE VOD * CH 24 - DCH 31
DTA005 31

.sta
DTA007 31
t 31

PRI* TRK LOOP 31 - ENBL
FFMT/LCMT/YALMT: ESF/B8Z/FDL
SERVICE RESTORE: YES
YEL ALM PROCESS: YES
ALARM STATUS : NO ALARM
CH 01 - MBSY TIE VOD * CH 02 - MBSY TIE VOD *
CH 03 - MBSY TIE VOD * CH 04 - MBSY TIE VOD *
CH 05 - MBSY TIE VOD * CH 06 - MBSY TIE VOD *
CH 07 - MBSY TIE VOD * CH 08 - MBSY TIE VOD *
CH 09 - MBSY TIE VOD * CH 10 - MBSY TIE VOD *
CH 11 - MBSY TIE VOD * CH 12 - MBSY TIE VOD *
CH 13 - MBSY TIE VOD * CH 14 - MBSY TIE VOD *
CH 15 - MBSY TIE VOD * CH 16 - MBSY TIE VOD *
CH 17 - MBSY TIE VOD * CH 18 - MBSY TIE VOD *
CH 19 - MBSY TIE VOD * CH 20 - MBSY TIE VOD *
CH 21 - MBSY TIE VOD * CH 22 - MBSY TIE VOD *
CH 23 - MBSY TIE VOD * CH 24 - DCH 31
.
****
OVL000
>ld 96
DCH000
.stat 31
.
DCH010

as
.
DCH009

stat dch 31
DCH 031 : OPER AEST AUTO
DES : ASTERISK
.
DCH: 31 EST CONFIRM TIME: 15:06:26 30/04/2013

DCH 31 UIPE_OMSG CC_RESTART_REQ REF 00000000 CH 0 TOD 15:06:26 CK 9AA658CB
TYPE: ALL CHANNEL

DCH: 31 RLS NO RESPONSE TIME: 15:06:38 30/04/2013

DCH: 31 EST CONFIRM TIME: 15:06:42 30/04/2013

DCH 31 UIPE_OMSG CC_RESTART_REQ REF 00000000 CH 0 TOD 15:06:42 CK 9AA6DBAC
TYPE: ALL CHANNEL

DCH: 31 EST REMOTE TIME: 15:06:42 30/04/2013
stat****
OVL000
>ld 60

.stat 31

PRI* TRK LOOP 31 - ENBL
FFMT/LCMT/YALMT: ESF/B8Z/FDL
SERVICE RESTORE: YES
YEL ALM PROCESS: YES
ALARM STATUS : NO ALARM
CH 01 - MBSY TIE VOD * CH 02 - MBSY TIE VOD *
CH 03 - MBSY TIE VOD * CH 04 - MBSY TIE VOD *
CH 05 - MBSY TIE VOD * CH 06 - MBSY TIE VOD *
CH 07 - MBSY TIE VOD * CH 08 - MBSY TIE VOD *
CH 09 - MBSY TIE VOD * CH 10 - MBSY TIE VOD *
CH 11 - MBSY TIE VOD * CH 12 - MBSY TIE VOD *
CH 13 - MBSY TIE VOD * CH 14 - MBSY TIE VOD *
CH 15 - MBSY TIE VOD * CH 16 - MBSY TIE VOD *
CH 17 - MBSY TIE VOD * CH 18 - MBSY TIE VOD *
CH 19 - MBSY TIE VOD * CH 20 - MBSY TIE VOD *
CH 21 - MBSY TIE VOD * CH 22 - MBSY TIE VOD *
CH 23 - MBSY TIE VOD * CH 24 - DCH 31
.

DCH: 31 EST REMOTE TIME: 15:08:44 30/04/2013
stat 31

PRI* TRK LOOP 31 - ENBL
FFMT/LCMT/YALMT: ESF/B8Z/FDL
SERVICE RESTORE: YES
YEL ALM PROCESS: YES
ALARM STATUS : NO ALARM
CH 01 - MBSY TIE VOD * CH 02 - MBSY TIE VOD *
CH 03 - MBSY TIE VOD * CH 04 - MBSY TIE VOD *
CH 05 - MBSY TIE VOD * CH 06 - MBSY TIE VOD *
CH 07 - MBSY TIE VOD * CH 08 - MBSY TIE VOD *
CH 09 - MBSY TIE VOD * CH 10 - MBSY TIE VOD *
CH 11 - MBSY TIE VOD * CH 12 - MBSY TIE VOD *
CH 13 - MBSY TIE VOD * CH 14 - MBSY TIE VOD *
CH 15 - MBSY TIE VOD * CH 16 - MBSY TIE VOD *
CH 17 - MBSY TIE VOD * CH 18 - MBSY TIE VOD *
CH 19 - MBSY TIE VOD * CH 20 - MBSY TIE VOD *
CH 21 - MBSY TIE VOD * CH 22 - MBSY TIE VOD *
CH 23 - MBSY TIE VOD * CH 24 - DCH 31
.

DCH: 31 MAINT INDICATION TIME: 15:12:02
COUNTER VALUE
2 255
3 16
25 1


TIM000 15:15 30/4/2013 CPU 0
stat 31


PRI* TRK LOOP 31 - ENBL
FFMT/LCMT/YALMT: ESF/B8Z/FDL
SERVICE RESTORE: YES
YEL ALM PROCESS: YES
ALARM STATUS : NO ALARM
CH 01 - IDLE TIE VOD * CH 02 - IDLE TIE VOD *
CH 03 - IDLE TIE VOD * CH 04 - IDLE TIE VOD *
CH 05 - IDLE TIE VOD * CH 06 - IDLE TIE VOD *
CH 07 - IDLE TIE VOD * CH 08 - IDLE TIE VOD *
CH 09 - IDLE TIE VOD * CH 10 - IDLE TIE VOD *
CH 11 - IDLE TIE VOD * CH 12 - IDLE TIE VOD *
CH 13 - IDLE TIE VOD * CH 14 - IDLE TIE VOD *
CH 15 - IDLE TIE VOD * CH 16 - IDLE TIE VOD *
CH 17 - IDLE TIE VOD * CH 18 - IDLE TIE VOD *
CH 19 - IDLE TIE VOD * CH 20 - IDLE TIE VOD *
CH 21 - IDLE TIE VOD * CH 22 - IDLE TIE VOD *
CH 23 - IDLE TIE VOD * CH 24 - DCH 31

.****
OVL000
>ld 96
DCH000
.stat dch 31
DCH 031 : OPER EST ACTV AUTO
DES : ASTERISK


So as you can see it finally seems to come up and the dchannel is active. However, when I make a call using direct trunk access this is what I get.

DCH 31 UIPE_OMSG CC_SETUP_REQ REF 0000000A CH 31 23 TOD 15:20:30 CK 9AC01951
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:4997 NUM PLAN: PRIVATE TON: UNKNOWN
CALLED #:7000 NUM PLAN: PRIVATE TON: UNKNOWN

DCH: 31 EST REMOTE TIME: 15:20:30 30/04/2013

DCH 31 UIPE_OMSG CC_DISC_REQ REF 0000000A CH 31 23 TOD 15:20:30 CK 9AC01D8F
CAUSE: #41 - NTWK TEMP FAIL

DCH 31 UIPE_IMSG CC_RELEASE_CONF REF 0000000A CH 31 23 TOD 15:20:30 CK 9AC01DAC

DCH: 31 EST REMOTE TIME: 15:20:32 30/04/2013






Here's my config.

REQ: prt
TYPE: rdb
CUST 0
ROUT 31

TYPE RDB
CUST 00
ROUT 31
DES TIE ASTERISK
TKTP TIE
NPID_TBL_NUM 0
ESN NO
CNVT NO
SAT NO
RCLS INT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC ISGF
SBN NO
PNI 00000
NCNA NO
NCRD NO
CHTY BCH
CTYP UKWN
INAC NO
ISAR NO
CPFXS YES
DAPC NO
INTC NO
DSEL VOD
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 1831
TCPP 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

IENB 5
TFD 0
VSS 0


PAGE 002

VGD 6
DRNG NO
CDR NO
VRAT NO
MUS NO
RACD NO
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

REQ:

REQ: prt
TYPE: tie
TN 31 1
DATE
PAGE

DES ASTERISK
TN 031 01
TYPE TIE
CDEN SD
CUST 0
TRK PRI
PDCA 1
PCML MU
NCOS 0
RTMB 31 1
B-CHANNEL SIGNALING
TGAR 1
AST NO
IAPG 0
CLS CTD DIP WTA LPR APN THFD HKD
P10 VNL
TKID
AACR NO
DATE 30 APR 2013

****

>ld 22
PT2000

REQ prt
TYPE adan dch 31

ADAN DCH 31
CTYP MSDL
GRP 0
DNUM 10
PORT 1
DES ASTERISK
USR PRI
DCHL 31
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC ISGF
PINX_CUST 0
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE NET
CNEG 1
RLS ID 1
RCAP COLP NDI CCBI CCNI PRI DV3I CTI QMWI
PR_TRIGS DIV 2 3
CNG 2 3
PR_RTN NO
MBGA NO
OVLR NO
OVLS NO
T310 120
T200 3
T203 10
N200 3
N201 260
K 7

****

DLOP NUM DCH FRM TMDI LCMT YALM TRSH
TRK 014 24 ESF NO B8S FDL 00
PRI 015 23 ESF NO B8S FDL 00
030 23 ESF NO B8S FDL 00
031 23 ESF NO B8S FDL 00
050 23 ESF NO B8S FDL 00
051 23 ESF NO B8S FDL 00
082 23 ESF NO B8S FDL 00
083 23 ESF NO B8S FDL 00



Any Ideas?

The only differences that I have for an example are RDB - RCLS EXT, TN - Cls unr dtn, DCH RCAP - QMWI as well.


Avaya/Nortel/NEC/Asterisk/Access Control/CCTV/DSX/Acti/UCx

Well, I made those changes and I'm still getting HDLC Bad FCS messages and HDLC Aborts flooding my Asterisk CLI.

Would you mind if I had a look at both sides of your config? I'm pulling my hair out on this one and I've been at it for a month or so on and off... I wouldn't mind using Phantom DN if that's what it takes, I was hoping to just have some sort of vacant number routing to send it out one of the TIE and have asterisk clean up whatever it sends me but I can't even get that far...

Also, what did you use for connectivity between the two switches? Did you use a CSU or did you cable direct? I've built cables, used nortel cables, figured out crossover pinouts and I don't think cablinb is my problem but I'm not yet ruling it out...

We had a cross over from a 61 to Asterisk. The pri was set as a did pri. We set the 61 as the user. It was a std DID pri with rcap - colp,nds on the dch, IFC - ni2. I'm soory I don't have a print out of the RDB, but it was pretty much just a standard DID route and channels. TN cls of unr,dtn.


Avaya/Nortel/NEC/Asterisk/Access Control/CCTV/DSX/Acti/UCx

So does your 61 have an RJ-45 as the interface or was it DB-15 on the nortel side and RJ45 on the Asterisk side? I was having trouble verifying what the pinout should be going from DB15 (out of my NT5D12 Dual PRI) to the RJ on the other end to Asterisk. I'm pretty sure I've got it right, but I wanted to verify if possible. I'll try the setup you've described next and cross my fingers!

I still used the RJ-45 adapter to the DB-15 cable to the 61 and the Asterisk was straight to the PRI port. Just make sure one of the systems is the user and the other the NET.


Avaya/Nortel/NEC/Asterisk/Access Control/CCTV/DSX/Acti/UCx

by the way, your signature sounds like me...
I do Nortel, Asterisk, CCTV, Access Control, 2 Way Radios, Pagers (yes we still use them), Cell Phones, and... the ever present... "other duties as assigned

still no joy. This shouldn't be that difficult...

Another customer of ours the just put in an Asterisk based system just had us connect to them with a std TIE pri with D100. Are you just trying to get EXT to Ext at his point?


Avaya/Nortel/NEC/Asterisk/Access Control/CCTV/DSX/Acti/UCx

Yes, I'm just trying to get a call, any call, to go over the trunk successfully. At the moment I can't even see traffic on the asterisk side if I call from Nortel. Once when I was setting up a regular "super trunk" as ATT calls it (full 24 channel T1 with no dch) I could see some junk coming across the CLI on the asterisk side when I made a call but nothing of use. I can't get anything with a dch to be happy enough to connect any call.

for the record I've been able to get two asterisk systems to talk to eachother using the ni-2 DID tie trunk, just not Nortel/asterisk

if you don't really need the Dch, try just a std DTI tie trunk. I don't know what else to try at this point. Hopefully one of the others have some suggestions.


Avaya/Nortel/NEC/Asterisk/Access Control/CCTV/DSX/Acti/UCx

How is you routing set up? ie.... dsc's & ect. RLI restrictions?


Avaya/Nortel/NEC/Asterisk/Access Control/CCTV/DSX/Acti/UCx

Had no idea something like this existed... buying one now to test! That will take about 4 variables out of the picture!

I have set up one RLI for testing right now and pointed an unused nxx at it. Throughout a couple of these trials and errors I've been able to make a channel go busy for a second using a maint set and ld 36 but never complete a call

is there no way to edit a post on this forum??

Ok,
The latest is that i'm still having issues establishing a connection between the two systems. I believe I've figured out what's going on at least.

On the Asterisk side(between the HDLC Abort mesages that I've been paying too much attention to) I see

PRI Span: 2 TEI=0 MDL-ERROR (G): T200 expired N200 times sending SABME in state 5(Awaiting establishment)
PRI Span: 2 Changing from state 5(Awaiting establishment) to 4(TEI assigned)
PRI Span: 2 TEI=0 DL event: Q931_DL_EVENT_DL_RELEASE_IND(3)

over and over again like the Asterisk system is trying to do an initial setup of the dch.

On Nortel side I see this:


DCH054 DCH: 31 EST REMOTE TIME: 9:33:40 5/08/2013

DCH054 DCH: 31 EST REMOTE TIME: 9:33:40 5/08/2013

DCH054 DCH: 31 EST REMOTE TIME: 9:33:42 5/08/2013

DCH054 DCH: 31 EST REMOTE TIME: 9:33:44 5/08/2013



and eventually get this

DCH: 31 MAINT CONFIRM TIME: 9:34:46
COUNTER VALUE
2 255

Count of peer initiated re-establishment link

Which means it filled up the counter and started over.

What could cause the Asterisk system to keep resetting the link? I'm using ESS5 right now but I was trying with NI2 a minute ago and it looked almost like it was doing the same thing in reverse. Instead of counter 2 going up I was getting counter 3 which is:
03 = Count of unsuccessful retransmit N200 of SABME as if the Nortel side was retransmitting SABME over and over again... Any ideas?