Meridian to Avaya tie trunk 1

[wiremantx]

We have an opt 61 with a T1 tie circuit connected to an Avaya communication manager 2.2(I believe)on the far end.

I have the ACOD built as 3013 ( I want to change to a single digit later) and I get a dial tone. Whenever I dial the Avaya's 4 digit extension, I get a fast busy.

Are there any protocols or anything that I need to check to be able to connect to the other switch?

 

[pbxn]

Are the Avaya's 4 digits built as cdp's pointing to your new route built in the meridian?

 

[Triton101]

TGAR and TARG?

 

[tnphoneman]

What type of tie trunk is this? PRI or just DTI? If it is PRI you may not be able to dial without putting a CDP steering code in. DO NOT make your ACOD 1 digit as it will take away from available numbers in your dialing plan and leaves a door partially open for hackers. Single digit easy to guess. If there is not a number conflict between the 2 switches just use CDP to steer the calls. Another reason is that if any of the numbers at the other site have a 0 or a 1 as the first or second digit you will have to make the set you are calling from UNR instead of CTD in the class of service. If you are anything other than UNR you can not dial a 0 or 1 as the first or second digit after dialing the route ACOD. This is from the old days when all the area codes had either a 0 or a 1 as the second digit. For example if you had CLS=CTD and you dialed the ACOD and the ext was x1xx, 1xxx, x0xx or 0xxx you would not be able to dial those numbers.

 

[johnpoole]

best bet is dsc's.. in ld 87 you build the cdp, add a dsc, point it to a rlb that hits the route.. that takes the acod out of the package...

john poole
bellsouth business
columbia,sc

 

[wiremantx]

Thi is what I have. This Route 13 used to be a tie circuit to a BCM at another location. The Avaya guys says the tie circuit was built by the Telco as an ISDN/PRI or clear channel circuit. I swung the new cable to the new smartjack from the old smartjack that used to go the old location. I haven't changed any settings in the Meridian so far. The CSU/DSU settings are the same also.


When I tested it before, I dialed the access code and it did ring a phone on the avaya side but when the called party picked up there was no connection, Avaya dropped the call.

ROUT 13

TYPE RDB
CUST 00
ROUT 13
DES TIE-SANTA ROSA
TKTP TIE
NPID_TBL_NUM 0
ESN NO
CNVT NO
SAT NO
RCLS EXT
DTRK YES
DGTP PRI
ISDN YES
MODE PRA
IFC SL1
PNI 00001
NCNA YES
NCRD YES
TRO YES
CHTY BCH
CTYP UKWN
INAC YES
ISAR NO
DAPC NO
DSEL 3VCE
PTYP PRI
AUTO NO
DNIS NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 3013
TCPP 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
GRD 896
SFB 3
NBS 2048
NBL 4096
TFD 0
DRNG NO
CDR NO
MUS NO
EQAR NO
FRL 0 0


PAGE 002

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
TTBL 0
ATAN NO
PLEV 2
ALRM NO
ART 0
SGRP 0
AACR NO

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

 

[Triton101]

IFC is set to SL1

I have seen other Avaya ties showing ISGF (ISO QSIG interface with GF platform)

 

[tnphoneman]

Your interface on the D-channel and route is SL1. You need to change it to something that the Avaya can talk to. SL1 is Nortel proprietary. Can't even use this to a DMS.

 

[wiremantx]

Thanks for the help! I will talk to the avaya tech and see if we can make these switches connect.

If anyone might have an example to show me let me know.

 

[wiremantx]

I did find one that John posted. We also found an Avaya whitepaper on the subject.

 

[wiremantx]

It won't let me use the ISGF for IFC. are there any other alternatives or do I have to add the necessary patches to get it to work.

IN-SERVICE PATCHES : 47
PAT# PRS PATCH REF # NAME DATE FILENAME
00 MP15566 ISS1:1OF1 CORE 00/00/00 p11061_1.cp4
01 BV81802 ISS1:1OF1 CORE 00/00/00 p11286_1.cp4
02 MP09988 ISS1:1OF1 CORE 00/00/00 p14186_1.cp4
03 MP14613 ISS1:1OF1 DECT 00/00/00 p15720_1.cp4
04 DEPLIST ISSA:1OF6 CORE 00/00/00 p16000aa.cp4
05 DEPLIST ISSA:2OF6 CORE 00/00/00 p16000ba.cp4
06 DEPLIST ISSA:3OF6 CORE 00/00/00 p16000ca.cp4
07 DEPLIST ISSA:4OF6 CORE 00/00/00 p16000da.cp4
08 DEPLIST ISSA:5OF6 CORE 00/00/00 p16000ea.cp4
09 DEPLIST ISSA:6OF6 CORE 00/00/00 p16000fa.cp4
10 DEPLIST ISSA:1OF3 SCCS 00/00/00 p16001aa.cp4
11 DEPLIST ISSA:2OF3 SCCS 00/00/00 p16001ba.cp4
12 DEPLIST ISSA:3OF3 SCCS 00/00/00 p16001ca.cp4
13 DEPLIST ISSA:1OF2 CALLPILOT 00/00/00 p16002aa.cp4
14 DEPLIST ISSA:2OF2 CALLPILOT 00/00/00 p16002ba.cp4
15 DEPLIST ISSA:1OF2 TERMINALS 00/00/00 p16003aa.cp4
16 DEPLIST ISSA:2OF2 TERMINALS 00/00/00 p16003ba.cp4
17 DEPLIST ISSA:1OF2 IP 00/00/00 p16004aa.cp4
18 DEPLIST ISSA:2OF2 IP 00/00/00 p16004ba.cp4
19 DEPLIST ISSA:1OF3 INTL 00/00/00 p16005aa.cp4
20 DEPLIST ISSA:2OF3 INTL 00/00/00 p16005ba.cp4
21 DEPLIST ISSA:3OF3 INTL 00/00/00 p16005ca.cp4
22 DEPLIST ISSA:1OF2 EURO 00/00/00 p16006aa.cp4
23 DEPLIST ISSA:2OF2 EURO 00/00/00 p16006ba.cp4
24 DEPLIST ISSA:1OF6 FEATURES 00/00/00 p16007aa.cp4
25 DEPLIST ISSA:2OF6 FEATURES 00/00/00 p16007ba.cp4
26 DEPLIST ISSA:3OF6 FEATURES 00/00/00 p16007ca.cp4
27 DEPLIST ISSA:4OF6 FEATURES 00/00/00 p16007da.cp4
28 DEPLIST ISSA:5OF6 FEATURES 00/00/00 p16007ea.cp4
29 DEPLIST ISSA:6OF6 FEATURES 00/00/00 p16007fa.cp4
30 DEPLIST ISSA:1OF1 CALLPILOT/SCCS 00/00/00 p16008aa.cp4
31 MP16609 ISS1:1OF1 Core 00/00/00 p16070_1.cp4
32 Q460828 ISS1:1OF1 EuroISDN 00/00/00 p16526_1.cp4
33 Q004857 ISS1:1OF2 CORE 00/00/00 p16628a1.cp4
34 Q004857 ISS1:2OF2 CORE 00/00/00 p16628b1.cp4
35 Q506239 ISS2:1OF1 CORE 00/00/00 p16678_2.cp4
36 MP16071 ISS1:1of1 qsig 00/00/00 p16744_1.cp4
37 Q005426 ISS2:1of1 QSIG 00/00/00 p16835_2.cp4
38 Q005328 ISS1:1OF1 CORE 00/00/00 p16923_1.cp4
39 Q005680 ISS1:1OF1 MCDN 00/00/00 p16960_1.cp4
40 Q006155 ISS1:1OF1 CCR/MLINK 00/00/00 p17159_1.cp4
41 Q006174 ISS2:1OF3 ACD/NACD 00/00/00 p17193a2.cp4
42 Q006174 ISS2:2OF3 ACD/NACD 00/00/00 p17193b2.cp4
43 Q006174 ISS2:3OF3 ACD/NACD 00/00/00 p17193c2.cp4
44 Q006604 ISS3:1OF1 CORE 00/00/00 p17499_3.cp4
45 Q007980 ISS1:1OF1 GF 00/00/00 p18163_1.cp4
46 Q009202 ISS2:1OF1 p18852_2 00/00/00 p18852_2.cp4

 

[bigindian65]

IFC eSS4

Mato' Was'aka

 

[drifter56]

Sounds like you're headed down the right path. Not sure what error you are getting when you try to setup the D-Channel for ISIG, but if the system is not letting you use this protocol then it will be a package issue, not a patch issue. Make sure you have all the needed packages to do QSIG. Also not sure what type of d channel card you are using but it must be a downloadable card to be able to program QSIG d channels, ex. MSDL. Also, do not just start using various protocols and hope something works. Both the Nortel and Avaya are CPE pieces of equipment and therefore when you put ESS5 or DMS into you IFC the switch thinks is going to be talking to that type of Central Office. As far as I know neither of the two pbx's can emulate a central office. The only protocol developed for inter-vendor PRI connection that I am aware of was QSIG. The nortel pbx only supports the full network protocol of either SL-1 or QSIG. I beleive you will find that true of the Avaya as well.

 

[wiremantx]

Well we got it work with Nortel ess4 and Avaya(Connect=PBx Interface=Network)

I am able to dial my access code and get through to the Avaya.

We need to change the display name from the old tie circuit which shows up on the Nortel phones display with the old name. A new circuit was installed to the
switch. I had changed the DES in the ADAN and in the 24 trunk tn's and they have the new name.