CLID Issues with Tandem calls through Meridian

[bubbaphone]

I have read almost every post on the CLID issues with Meridian, and still haven't been able to get my situation worked out. Perhaps I overlooked something.

I have a Meridian with PRI to CO, and another PRI to a different (non-Meridian) PBX. All connections are 5ESS, and I use CDP from Meridian to PBX-B. Here's the problem.

PBX-B calls Meridian desk phone, CLID shows Hxxxx. We can live with that, no problem. PBX-B calls 9+phone number (tandems through Meridian), outgoing CLID to PSTN = xxxx, not NPA-NXX-XXXX.

Meridian desk calls 9+phone number, outgoing CLID is correct (NPA-NXX-XXXX) using CLID tables, but also shows the same when Meridian calls PBX-B using CDP (PBX-B sees 10d CLID).

How can I make the calls from PBX-B show Hxxxx to Meridian Desk phone, but still get 10d CLID for calls that tandem through Meridian to PSTN, while allowing Meridian to PBX-B to show xxxx, and Meridian to PSTN show 10d CLID?

It this possible? I have changed CTYP, IDC, DGT, CLID, CLEN, etc., etc., and no luck.

Any guidance or insight would be greatly appreciated.

 

[mluckie1]

For calls from the Meridian to PBX 'B' is it programmed as a DSC? Please prt the code and rli.

 

[bubbaphone]

Here's the printouts:

CDP:
DSC 46
FLEN 4
DSP LSC
RLI 2
NPA
NXX

RLB:
RLI 2
ENTR 0
LTER NO
ROUT 2
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
CNV NO
EXP NO
FRL 0
DMI 0
FCI 0
FSNI 0
SBOC NRR
OHQ NO
CBQ NO
ISET 0
NALT 5
MFRL 0
OVLL 0


DMI:
DMI 2
DEL 0
CTYP CDP

RDB:
TYPE RDB
CUST 00
DMOD
ROUT 2
DES LABESS5
TKTP TIE
NPID_TBL_NUM 0
ESN NO
CNVT NO
SAT NO
RCLS INT
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC ESS5
SBN NO
PNI 00000
SRVC NNSF
NCNA YES
NCRD NO
CHTY BCH
CTYP UKWN
INAC NO
ISAR NO
CPUB ON
DAPC NO
BCOT 0
DSEL 3VCE
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH RRB
TRMB NO
STEP
ACOD 8002
TCPP NO
PII 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
TFD 0
DRNG NO
CDR 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
PLEV 2
ALRM NO
ART 0
SGRP 0
AACR NO

DCH:
ADAN DCH 20
CTYP TMDI
CARD 02
PORT 1
DES LABESS5
USR PRI
DCHL 2
OTBF 32
PARM RS232 DTE
DRAT 64KC
CLOK EXT
IFC ESS5
SIDE USR
CNEG 1
RLS ID **
RCAP
MBGA NO
OVLR NO
OVLS NO
T200 3
T203 10
N200 3
N201 260
K 7

Net Data:
TYPE NET_DATA
CUST 00
OPT RTD
AC2
FNP YES
ISDN YES
PNI 0
PINX_DN
MBG 0
BSGC 65535
PFX1
PFX2
HLOC 919
LSC
RCNT 5
PSTN NO
TNDM 15
PCMC 15
SATD 1
OCLI NO
TRNX NO
EXTT NO
FTOP FRES
VNR NO
NIT 8
FOPT 14


CLID:
INTL 1

ENTRY 0
HNTN
ESA_HLCL
ESA_INHN NO
ESA_APDN YES
HLCL
DIDN YES
HLOC
LSC
CLASS_FMT DN

ENTRY 1
HNTN 919
ESA_HLCL
ESA_INHN NO
ESA_APDN NO
HLCL 4
DIDN YES
HLOC
LSC
CLASS_FMT DN

 

[mluckie1]

Meridian will send 10 digits because of the ess5 dchannel. To make it look like another Meridian you will need to set it up as QSIg for the point to point. Could try and put RCAP as ND3 before making the change also RLS ID 1. RLI 2 would need the DMI assigned to it for the labeling to work but try the dchannel setting first. Your CLID table looks like it could be adjusted as well. CLID table 0 is the default for all DN's when none is assigned.

 

[johnpoole]

without qsig the 4 digit clid will not be sent through the pstn, i can send clid via t1 or pri point to point on a merridian to mirridian t1, pni not only needs to match on each end but must be entered in the cdb on each end. i'll bet even without qsig, if you match pni and enter the same pni in each cdb, you can see the 4 digit dn on the far end. qsig would clean it up in a minute but i have only used qsig as a translator to a 3rd party switch, can you get the co to reconfig qsig? if so it's clean.. i do know merridian to avaya to ccm works with dn and names and mwi's due to qsig, so it's doable, the problem is getting the central office people to match your desire to get it done

john poole
bellsouth business
columbia,sc

 

[SL1User]

To get rid of the H in front of every number display just enable plugin #14

See text:

PI: Patch to suppress "H" in the display for MCDN calls.
(FIXED AS PLUGIN 14 FROM 25.15 S/W)

Problem:

Setup:
======

Two systems are connected via MCDN (node A and B).
A set with digit display is connected at each system.

Action:
=======

Establish a network call from node A to node B.

Problem:
========

The display of the set connected to node B shows a "H"
in front of the originators DN to indicate that this is
a network call.
The request from the customer is to make this "H" in the
display optional. It could be an option in the CDB.
The customer BASF for example doesn't want to have the
"H" in the display.