telecom116

You have to set up your CLID tables in LD 15

CHG
NET
...
CLID? YES
...

Here's an example of part of my CLID table. I have multiple entries for various reasons (see below entries):

LD 15
REQ: prt
TYPE: clid
CUST 0
SIZE 256
RNGE 0 11

INTL

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

ENTRY 1
HNTN 913
ESA_HLCL 555
ESA_INHN YES
ESA_APDN YES
HLCL 5553911
DIDN NO
HLOC
LSC
CLASS_FMT DN

ENTRY 2
HNTN 913
ESA_HLCL 5553911
ESA_INHN YES
ESA_APDN NO
HLCL 5553911
DIDN NO
HLOC
LSC
CLASS_FMT DN

ENTRY 10
HNTN 913
ESA_HLCL 555
ESA_INHN YES
ESA_APDN YES
HLCL
DIDN NO
HLOC
LSC
CLASS_FMT DN

ENTRY 11
HNTN 913
ESA_HLCL 555
ESA_INHN YES
ESA_APDN YES
HLCL 555
DIDN YES
HLOC
LSC
CLASS_FMT DN

Which table is used by a DN is set by the number at the end of the key definition. By default it is 0. Look in the Emergency Services NTP since I think (I don't have my MERL right now) it has the most CLID setup info.

Some of my table entries include:
0 - Default CLID table - send out customer service center phone number, both CLID and ESA (i.e., 911 calls); My goal is to not have any entries using the default table
1 - Send administrative switchboard number as CLID for DID numbers, but send DID number for ESA; used for execs that don't want number sent
2 - Non-DID numbers - send switchboard number for everything
10 - DID numbers - send Customer service center number (default number ANAT/ANLD), but send DID number for ESA
11 - DID numbers - send DID for both CLID and ESA

Hopefully this makes some sense.

Fletch

I commend you on a well planned implementation of CLID. I hope many will take careful notes of your examples and implement them accordingly. This is a terric example of the power behind The Meridian CLID capabilities, and is a feature many other manufacturers can't hold a candle to.

Great response.

Fletch

glehman

That was an excellent explanation of what do to with the CLIDs...

I had started another topic, which I think I got mired in my own ineptitude. I tried to shorten the infomation...

Here is the gist of things, basically my LD company uses the ANI to determine whether or not a call being placed requires a code or not. Right now we are using 2 different routes out of 2 different COs, so the ANIs are different. If everything is going out over 1 route, can we send 2 different ANIs?

Here is my other post:
"From my discussion with the LD carrier, they determine if a call placed requires an LD code based on the ANI.

We have built 2 separate CLID tables, I will make fax dns:
key 0 scr 5555 1
where 1=769-4044
769 4044 is set with the LD carrier to NOT REQUIRE an LD code.

phone dns:
key 0 scr 5555 0
where 0=769-4884
769-4884 is set with the LD carrier to REQUIRE an LD code.

ANI_DATA is set to 769 4044.

Is there anyway to make the ANI sent out the same as the CLID sent?
How do long distance carriers usually distiguish whether or not the call requires a LD code or not? Mine says they look at the ANI, but I have people within the same LD company telling me different things, is there a standard?

Thanks for any help. You folks have been wonderful with assistance, and I appreciate any experience can you share with me to help me save navigate this obstacle. "

I hope my lack of experience with this switch isn't making things harder to explain than they should be.

Thanks in advance for any help you may provide.
Gene

telecom116

You may have to just experiment to see how your phone company handles the CLID info sent.

When I started changing my CLID tables, for calls to 1411 (the only LD that goes out over the PRI) the telco bill shows the individual CLID as if it was the ANI of the phone making the LD call. So now I have a individual breakdown by CLID of all of these calls.

Anonymous

telecom116----

Thanks for the response.

I added the CLID entries as you stated, but calls are still going out with my main number only.

DID Range (22 386-7000 thru 7999

CLID ENTRIES:

REQ: prt
TYPE: clid
CUST 0
SIZE 256
RNGE

INTL

ENTRY 0
HNTN 228
ESA_HLCL 228
ESA_INHN YES
ESA_APDN YES
HLCL 3867111
DIDN NO
HLOC 7111
LSC

ENTRY 1
HNTN 386
ESA_HLCL 386
ESA_INHN NO
ESA_APDN YES
HLCL
DIDN YES
HLOC 386
LSC

ENTRY 11
HNTN 228
ESA_HLCL 386
ESA_INHN YES
ESA_APDN YES
HLCL 386
DIDN YES
HLOC
LSC

ENTRY 12
HNTN 228
ESA_HLCL 3867111
ESA_INHN YES
ESA_APDN YES
HLCL 3867111
DIDN NO
HLOC
LSC

ENTRY 13
HNTN 228
ESA_HLCL 386
ESA_INHN YES
ESA_APDN YES
HLCL
DIDN NO
HLOC
LSC

TEST SET....

DES TEST
TN 084 1 04 13
TYPE 2008
CDEN 8D
CUST 0
FDN 7111
TGAR 1
LDN NO
NCOS 5
SGRP 0
RNPG 0
SCI 0
SSU
LNRS 16
XLST 0
SCPW
CLS CTD FBD WTA LPR MTD FNA HTA ADD HFD
MWD AAD IMD XHD IRA NID OLA VCE DRG1
POD DSX VMD CMSD CCSD SWD LNA CNDA
CFTD SFD MRD DDV CNID CDCA
ICDD CDMD MCTD CLBD AUTU
GPUD DPUD DNDA CFXD ARHD FITD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID
DDGA NAMA
USRD ULAD RTDD PGND OCBD FLXD FTTC
CPND_LANG ENG
RCO 0
HUNT 000
LHK 0
LPK 0
PLEV 02
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
DNDR 0
KEY 00 SCR 7030 11 MARP
CPND
NAME TEST SET
XPLN 27
DISPLAY_FMT FIRST,LAST
01
02
03
04
05
06
07
DATE 5 OCT 2003

When i dial another business set in my office I'm hoping to see 2283867030 but I always see 2283867111.....

Any Ideas.........

telecom116

Do a trace in load 80 of the outgoing PRI channel to isolate whether the M1 is sending out the correct CLID, or if your carrier is not passing on the CLID correctly.

Anonymous

telecom....

With CLID = 11

Trac:
---- ISDN PRA CALL (TERM) ----
CALL REF # = 141
BEARER CAP = VOICE
CALL STATE = 3 OUTGOING
CALLING NO = 2867030
CALLED NO = 3480671

With CLID = 0

Trac:
---- ISDN PRA CALL (TERM) ----
CALL REF # = 141
BEARER CAP = VOICE
CALL STATE = 3 OUTGOING
CALLING NO = 3867111
CALLED NO = 3480671

So it look as though the M1 is sending the correct CLID but that Bell South is inserting the ANI?

What's my next step.....

telecom116

A call to Bell South is in order. It may take a while but you need to find someone who knows ISDN and the switch to check things out.

glehman

Good Luck finding someone at BellSouth who knows anything.

Been batted around for the last couple of weeks with those people and can never speak to someone who knows. They all profess to know, but none of them have touched the switch. Good luck!

telco--
So, if I have 2 CLID tables, and get my carrier to get their hands off what I send, will I still send ANI info? That may seem like an odd question, but I am not sure how to phrase it.

We have BellSouth as well.. Our phone vendor thinks that by changing the CLID we should be fine. I assume that is because if no ANI is found, that the CLID was be used for ANI, if needed? God, I need a BARS/NARS class... I'm just mr. MAC.

Thanks for the help!
Gene