Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Asterisk to CS1000E via TMDI PRI 2

Status
Not open for further replies.

AnthonyHardy

IS-IT--Management
May 9, 2008
56
US
OK guys, I've had a tech on the phone with me on and off for two days. I'm trying REALLY hard to get this setup and functional, but not having any luck.

We originally setup the TMDI PRI as NI2 (same on the asterisk side) and DID the PRI came up great. I could place calls from the Nortel to the asterisk server with no problems. When I attempted to go from asterisk to Nortel, the Nortel was sending "Channel unavailable, cause 44" according to dch messaging on both sides.

The tech seemed to think that the DID setting was the cause of this so we changed to 5ESS on both sides and now I can't place a call either way (CALL BARRED on Asterisk->Nortel . .maybe Channel Unavailable for Nortel->Asterisk, I'm not positive on that last one).

I would prefer to go back to NI2, but the tech seemed certain that it was the DID setting that was the issue and you can't do TIE on NI2. Thoughts?
 
Just for a test have you tried setting the IFC to ESIG and CO_type to STD on both sides? It should allow tie trunks to be configured.I had to use this IFC to connect a Mitel to a Nortel. I also saw this post, don't know if it will help as I am Asterisk challenged. thread798-1455378.
 
look like a perfect place for qsig.. lacking that, are you using any did trunks now? if so the astrick will have to send the same number of digits as your did provider.. the number of digits is a customer wide setting... we are now getting 4 tone from our provider, our dictation people wanted to send 7 tone from there server.. that meant i had to use tie for that app.. then build an idc to strip 3..

the server team could have sent 4 IF they knew their job..

your running pri's so you have a lot of flexability.. be sure that any change (tie to did), you dis msdl x, enl msdl x fdl.. that writes changes to the msdl.. without that command all bets are off..

john poole
bellsouth business
columbia,sc
 
I'll bet it was that we were sending 4 digit extensions instead of 7 digits, which is what was expected because of the other existing PRI that receives 7 digits.

Bingo. Now, to get my tech back on the phone so we can go back to NI2 and get this thing functional. I would try to change back to NI2 from 5ESS, but I am having a hard time trying to figure out how.
 
OK. . I think I've managed to setup for NI2 again and have the capability to call from Nortel->Asterisk fine.

Still getting fast busy when calling Asterisk->Nortel. Here are the dch messages. I tried changing it so the asterisk server sends 7 digits, just like the dch messages showed for the existing PRI, but still no luck:(.


DCH 5 UIPE_IMSG CC_SETUP_IND REF 00000200 TOD 10:29:42 CK 6F26B24A
CALLED #:8091531 NUM PLAN: UNKNOWN TON: UNKNOWN
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:1707 NUM PLAN: UNKNOWN TON: UNKNOWN

BUG1369
BUG1369 : 00000005 0000001A
BUG1369 + 106B66C4 10A3862A 10A38488 10EA3B48 10EA2ED0
BUG1369 + 10EA27E4 10EA22F2 21E0D73A 10E8338A 21D77C10
BUG1369 + 10EAB412 10EAB166 10EA90F8 10EA902C 108D85DC
BUG1369 + 108D5364 108D4F7C 10F26FC0 10F20986

DCH 5 UIPE_OMSG CC_REJECT_REQ REF 00008200 CH 0 TOD 10:29:42 CK 6F26B252
CAUSE: #44 - REQ CIRC/CHAN NOT AVAILABLE

DCH 5 UIPE_OMSG CC_REJECT_REQ REF 00008200 CH 0 TOD 10:29:42 CK 6F26B257
CAUSE: #34 - NO CHANNEL/CIRC AVAIL

DCH 5 UIPE_IMSG CC_RESTART_IND REF 00000000 TOD 10:29:42 CK 6F26B303
TYPE: INDICATED CHANNEL

BUG1369
BUG1369 : 00000005 0000001A
BUG1369 + 106B66C4 10A3862A 10A38488 21D34E22 10EF0754
BUG1369 + 10EF06F0 10EEFAC0 10EE8690 10EE859C 21D77BD2
BUG1369 + 10EAB412 10EAB166 10EA90F8 10EA902C 108D85DC
BUG1369 + 108D5364 108D4F7C 10F26FC0 10F20986

DCH 5 UIPE_OMSG CC_RESTART_REJ REF 00000000 CH 0 TOD 10:29:42 CK 6F26B30F



Any ideas?
 
OK guys, I'm completely stumped here. Anyone know a tech I can hire to help me with this? I don't want to open a $600 ticket with Nortel for something that I have a sinking feeling will be a 15 minute fix from someone who has seen this issue before:( . .
 
how many digits are in your ldn 0? set the astrick to that number of digits.. not the clid as seen in your dch msgs.. your msgi shows calling number, not the same as rec digits..

unless your using 7 digit ext numbers, your box does not have a clue as to what to do with 7 digits.. does your did have idc translation for each did?.. if not your getting the same number of digits as your ext dn's

john poole
bellsouth business
columbia,sc
 
step one. remove the targ from the route.. targ x1.. what is the ncos on the trunks?

the switch treats a trunk the same as it treats an analog station.. make sure the trunks are dtn

john poole
bellsouth business
columbia,sc
 
Doing one thing at a time (sorry, not a native nortel guy here and I have to look up instructions on most things outside of normal MACs):

LDNs are:

REQ: prt
TYPE: ldn
TYPE LDN_DATA
CUST 0

TYPE LDN_DATA
CUST 00
OPT XLDN
DLDN YES
LDN0 1700
LDA0 ALL
LDN1
LDA1
LDN2
LDA2
LDN3
LDA3
LDN4
LDA4
LDN5
LDA5
LDBZ
ICI 00 LD0
ICI 01
ICI 02 INT
ICI 03 RLL
ICI 04 DL0
ICI 05
ICI 06
ICI 07
ICI 08
ICI 09

Not sure what 1700 means? Trying to find documentation.
ncos on the trunks is 5 (my phone is 3)
targ on the route is 01
trunks have dtn in their cls.
 
Just FYI, for anyone who finds this issue, the reason Asterisk wouldn't send was the trunkgroups option in chan_dahdi.conf. I removed that and Asterisk starting requesting the proper channels from the Opt11 and I'm almost good. Now just to get external calling working properly, which is probably just a result of my playing with ncos and tgar too much.

Thanks to EVERYONE for all of their help.
 
Another question, so I don't beat my head too long (I think this one "might" be easy?). . .

normal extension calls are going through fine (even calls to our remote sites over H323 trunks), but calls going out other trunks (to the pstn, for example) are routed to the operator.

Any ideas?
 
OK . worked out my last issues . .posting for posterity.

DID's were not allowed out. NI2 cannot be setup as TIE, only DID. THe calls could come in, but not exit another DID line (security in the Nortel we didn't want to break).

We changed to QSIG on both ends and then changed to TIE trunks and everything is functional:).

THanks to everyone here for their help!
 
I'm glad to see someone else attempting this. We have been using an ESS5 IFC for a year now but users want name and number.

Are you getting name and/or number when calls flow from Nortel to Asterisk?

Thanks
 
We are. Had to make sure facilityenable=yes was set in asterisk and RCAP had to have NDI on the dch.


Here's my setup, for posterity:


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


PAGE 002

NBL 4096

IENB 5
TFD 0
VSS 0
VGD 6
DRNG NO
CDR NO
VRAT NO
MUS NO
EQAR 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
TTBL 0
ATAN NO
PLEV 2
ALRM NO
ART 0
SGRP 0
AACR NO

==============================================

REQ: prt
TYPE: tn
TYPE TNB
TN 5 1
DATE
PAGE
DES

DES ASTERIX
TN 005 01
TYPE TIE
CDEN SD
CUST 0
TRK PRI
PDCA 1
PCML MU
NCOS 3
RTMB 11 1
B-CHANNEL SIGNALING
TGAR 1
AST NO
IAPG 0
CLS CTD DTN WTA LPR APN THFD HKD
P10 VNL
TKID
AACR NO
DATE 20 JUL 2009


======================================================

ADAN DCH 5
CTYP TMDI
CARD 05
PORT 1
DES ASTERIX
USR PRI
DCHL 5
OTBF 32
PARM RS232 DTE
DRAT 64KC
CLOK EXT
IFC ISGF
PINX_CUST 0
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE USR
CNEG 1
RLS ID **
RCAP COLP NDI
MBGA NO
OVLR NO
OVLS NO



PAGE 002

T310 120
T200 3
T203 10
N200 3
N201 260
K 7
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top