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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

OPT 11 to Cisco don't have QSIG 1

Status
Not open for further replies.

sarakodi

Technical User
Mar 29, 2006
38
0
0
US
Trying to set up PRI between Nortel Opt11 and Cisco
Set up is NI2 trunk type is DID can call back and forth but unable to call out from Cisco and Cisco can't recieve external call from Nortel, calls revert to operator
I don't have QSIG

Thanks in advance
Mike

TYPE adan dch 6

ADAN DCH 6
CTYP MSDL
CARD 03
PORT 1
DES CISCO
USR PRI
DCHL 3
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC NI2
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE USR
CNEG 1
RLS ID **
RCAP COLP
MBGA NO
T310 120
T200 3
T203 10
N200 3
N201 260
K 7




TYPE RDB
CUST 00
DMOD
ROUT 9
DES CISCO
TKTP DID
SAT NO
RCLS EXT
DTRK YES
DGTP PRI
ISDN YES
MODE PRA
IFC NI2
CBCR NO
SBN NO
NCNA YES
NCRD YES
CHTY BCH
CPFXS YES
BCOT 0
INTC NO
DSEL VOD
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
RANX NO
SRCH RRB
TRMB YES
STEP
ACOD 4000
TCPP NO
PII NO
TARG 01
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
FLH 510
GRD 896
SFB 3
NBS 2048
NBL 4096
TFD 0
DRNG NO
CDR NO
MUS NO
MR 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
TTBL 0
PLEV 2
MCTS NO
ALRM NO
ART 0
SGRP 0
AACR NO


TN 003 01
TYPE DID
CDEN SD
CUST 0
NCOS 0
RTMB 9 1
B-CHANNEL SIGNALING
NITE
STRI/STRO OWK OWK
NO
IAPG 0
CLS UNR DTN WTA LPR APN THFD HKD
P10 VNL
TKID
DATE 28 OCT 2011
 
Take a look at the NTP feature guide for Direct Inward Dialing to Tie Connection under operating paremeters. I had this problem on a CS1000 to ASCOM wireless box. The CS1000 DID trunks are on a 1.5 T1. I set up a Analog DID route with one trunk member and using a Butt set I could dial the four digits and it worked fine. Try setting up analog test DID trunk to see if it's the same issue.
 




I am told from TAC that when you want to have 2 PRIs share a D channel, one being a primary and the other a secondary that configuration is considered NFAS.



NFAS will not work with MGCP as you can see from the below email from the TAC agent. It will however work with a H-323 configuration on the gateway. He will be available to talk tomorrow at 12 noon tomorrow, if anyone has any questions.



Also attached is a link to a document that discusses the differences between a H-323 gateway and MGCP. To summerise it:



H-323 :

QOS is not guaranteed
H-323 gateway handles all call processing
· Non-Facility Associated Signaling (NFAS) support—Support for NFAS allows the H.323 Gateway to control more ISDN PRI lines with one D channel.

· Much more configuration intensive and more complex



MGCP:

Call Manager handles QOS
Call Manager processes all call routing
Does not work with NFAS
Less configuration easier to manage
Much more features and functionality


Sarakodi I'm just posting this so that you have a little more knowledge of the UCM.
 
That is how you have to do it. But he just has one with one d-channel. Should work the way he has it built and I think he has tried tie too.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top