DID Trunk to PSTN

[marcocho]

Hello,

I have succesfully connected my 3cx phone system to our meridian using a TMDI card / PRI / NI2 protocol / DID trunks. Everything is working fine except for 1 think. If on the 3cx side, the user dials an external number, ex 91234567890, it never gets out from the meridian and will ring forever. Our ac1 is 9 and all our PSTN lines (t1 from vendor) are connected to the 11c.

What can I do ? I tried configuring TIE trunks with NI2 but it's always asking me for CRBC and I don't know what to do with that.

Thanks for your help !

Marco

 

[KCFLHRC]

On the 3 cx side, are you inserting the "9" and sending that to the Opt.11? If you are then I would look at the NCOS on the PRI connecting the 3 cx and make sure it is a high enough NCOS to make the outbound call. Also turn on inbound d-channel messaging on the pri connecting the 3 cx and see what digits you see come across that PRI.

 

[marcocho]

My NCOS is the highest it can be ( I don't want to block anything outgoing ). I have turned on the trace and I see all the digits (I put the 9 on the 3cx side). I have found what is happening: my calls are going to the attendant extension instead of accessing bars. How can I change that ?

Thanks

Marco.

 

[KCFLHRC]

If you are sure about your NCOS setting then maybe make sure that there is no TARG entry on the route connecting the 3 cx. Remember by default TARG is a 1.

 

[KCFLHRC]

I also think these should be programmed as TIE, not DID. Where are you seeing the CRBC prompt?

 

[marcocho]

I see the CRBC prompt in ld 16 right after I put IFC = NI2 for a TIE trunk type.

I have no clue how to configure ISA routes.

Thank you.

 

[marcocho]

Sorry, it's CBCR not CRBC.

In the administration manual, it says: Service route indicator

Thanks.

 

[KCFLHRC]

The default for CBCR is no, just return past that prompt because it's not a service route.

 

[marcocho]

I get an error if I do that.

Marco

 

[KCFLHRC]

Problem is a TIE trunk probably shouldn't be NI2. Do you have the packages in the PBX for QSIG or do you know?

 

[marcocho]

How do I find out ?

 

[KCFLHRC]

Ld 22, Req PRT, Type PKG You will need all of these



Network Alternate Route Selection (NARS) package 58
- Coordinated Dialing Plan (CDP) package 59
- Flexible Numbering Plan (FNP) package 160
- QSIG Interface (QSIG) package 263
- QSIG-GF Transport (QSIGGF) package 305
- QSIG Supplementary Services (QSIG-SS) package 316
- Primary Rate Access (PRI) package 146
-
Multipurpose Serial Data Link (MSDL) package 222

 

[marcocho]

I have all of these. But what kind of interface I need to configure on the 3cx end ?

The options I have are: NI2 - DSS1 - NTT - DMS100.

The problem with DMS100 is that I cannot put it as "net" side on the 3cx and I can't put it on "net" side on the Meridian...

Thanks.

 

[KCFLHRC]

I don't know anything about the 3 cx or what it even is. I have no idea what DSS1 and NTT is either. Someone at 3 cx should be able to help you with the config on that side. Did you check the targ on the route?

 

[marcocho]

Targ is ok.

I have tried ISGF with tie trunks. I can dial outside now !

But I have 2 other problems: No more caller id on this route and when I dial from outside, i get to the automated attendant and when I trie to dial the extention on the 3cx side, the systems says that I cannot dial that number, please try another one. Is there a restriction on the Meridian Mail where it cannot transfer the call to my isgf trunk ?

Thanks.

 

[KCFLHRC]

Caller ID will be RCAP settings. The other is a Restriction Permission list in the Mer Mail

 

[marcocho]

I was able to finally configure everything properly. For future refence, here is my config to connect a meridian opt11c with a 3cx system using a patton smartnode 4970. I have used 3cx's provisionning to configure the patton.

Patton:

Modified the e1t1 config to this:

port type: t1
port type: short-haul
clock: slave
linecode b8zs
framing: esf
encapsulation: q921

Q.921 (isdn layer 2)
permanent activity: disabled
endpoint type: net
protocol: pp
encapsulation: q931

Q.931 (isdn layer 3)
signaling protocol: ni2
endpoint type: net
b-channel allocation: ascending
b-channel range: 0 to 23
Maximum calls: 23

dchannel settings:
ADAN DCH 10
CTYP TMDI
CARD 02
PORT 1
DES 3CX
USR PRI
DCHL 2
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 36
RCAP COLP NDI CCBI CCNI PRI DV3I CTI
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

Route setting
TYPE RDB
CUST 00
DMOD
ROUT 20
DES 3CX
TKTP TIE
NPID_TBL_NUM 0
ESN NO
CNVT NO
SAT NO
RCLS EXT
VTRK NO
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 3VCE
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD x (i have omitted the acod)
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
NBL 4096


PAGE 002


IENB 5
TFD 0
VSS 0
VGD 6
DRNG NO
CDR NO
VRAT NO
MUS NO
RACD 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

route members (just the first route as an example, have 23 in total)
DES 3CX
TN 002 01
TYPE TIE
CDEN SD
CUST 0
TRK PRI
PDCA 1
PCML MU
NCOS 6
RTMB 20 1
B-CHANNEL SIGNALING
TGAR 1
AST NO
IAPG 0
CLS UNR DTN WTA LPR APN THFD HKD
P10 VNL
TKID
DATE 3 DEC 2013

My RLI
RLI 20
ENTR 0
LTER NO
ROUT 20
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 DBA
IOHQ NO
OHQ NO
CBQ NO

ISET 1
NALT 5
MFRL 0
OVLL 0

Then I configure the extention on the 3cx side in the dsc (ld 87 feat cdp) to route to rli 20

On the 3cx side, I add a DID on the gateway for each extension I want to reach from the meridian.

Hope this helps someone !

My only problem right now is that I'm loosing clid info when an external caller goes thru my auto-attendant. I always get my meridian mail's extension when I call goes in that way. For my needs, it's not a problem.

Thanks.

 

[jamie2]

How are you physically connecting the Qsig circuit to you 3cx server?

 

[marcocho]

From the pbx, there's a cable that connects to the bottom of the card and ends by a db25 connector. On that connector, there's a db25 to rj45 adapter. I run an ordinary cat6e câble to a patch panel that goes to another one and from that one I go into the rj45 port on the back of the patton.

Thanks.

 

[marcocho]

Just to be more precise, I use a TMDI card in my cabinet for the t1. Under the cards, there are ports where cables run out. Since my card is in slot 2, I use the cable at the bottom of the cabinet that is connected on port 2. That's where the cable that ends with a db25 is connected.