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!

Caller ID funkiness

Status
Not open for further replies.

robust57

IS-IT--Management
Apr 14, 2005
65
0
0
US
I want the outbound caller ID to be the same for every phone. Therefore I only have one CLID entry. That CLID is assigned to every phone. The odd part is that when I make an outbound call from an analog line I get the correct 10 digit caller ID, when I call outbound from a digital phone I get the 3 digit extension of that phone. What am I missing, thanks in advance?

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


Analog that has correct caller ID
DES UNITY
TN 009 0 00 12
TYPE 2616
CDEN 8D
CUST 0
AOM 0
FDN 751
TGAR 1
LDN NO
NCOS 4
SGRP 0
RNPG 0
SCI 0
SSU
XLST
CLS CTD FBD WTA LPR MTD FND HTA ADD HFD
MWA LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1
POD DSX VMD CMSD SLKD CCSD SWD LND CNDA
CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTU
GPUD DPUD DNDD CFXD ARHD FITD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD AHD
DDGA NAMA
DRDD EXR0
USRD ULAD RTDD RBDD RBHD PGND FLXD FTTC MCBN

CPND_LANG ENG
RCO 0
HUNT 751
LHK 0
PLEV 02
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
DNDR 0
KEY 00 SCR 298 0 MARP
01
02
03
04
05
06
07
08
09
10
11
12
13 MIK
14 MCK
15 TRN
DATE 11 JUN 2010

Digital phone that has incorrect caller ID
DES 229
TN 004 0 00 01
TYPE 3904
CDEN 8D
CUST 0
FDN 298
TGAR 1
LD
N NO
NCOS 4
SGRP 0
RNPG 0
SCI 0
SSU
LNRS 16
XLST
CLS CTD FBD WTA HPR MTD FNA HTA TDD HFA GRLD CRPD STSD
MWA LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1
POD DSX VMD CMSD SLKD CCSD SWD LNA CNDA
CFTD SFA MRD DDV CNIA CDCA MSID DAPD BFED RCBD
ICDD CDMD LLCN MCTD CLBD AUTU
GPUD DPUD DNDA CFXD ARHA FITD CLTD ASCD
CPFA CPTA ABDD CFHD FICD NAID BUZZ AGRD MOAD AHD
DDGA NAMA
DRDD EXR0
USRD ULAD RTDD RBDD RBHD PGND FLXD FTTC MCBN

CPND_LANG ENG
RCO 0
HUNT 298
LHK 1
PLEV 02
AST
IAPG 0
AACS NO
ITNA NO
DGRP
MLWU_LANG 0
MLNG ENG
DNDR 0
KEY 00 SCR 229 0 MARP
CPND
NAME XXXXXXXX
XPLN 27
DISPLAY_FMT FIRST,LAST
01 SCR 329 0 MARP
CPND
NAME XXXXXXXX
XPLN 27
DISPLAY_FMT FIRST,LAST
02 MSB
03 ADL 16
04 ADL 16
05 ADL 16
06 ADL 16
07 ADL 16
08 ADL 24
09
10
11
12
13
14
15
16 MWK 298
17 TRN
18 AO6
19 CFW 4 200
20 RGA
21 PRK
22 RNP
23
24 PRS
25 CHG
26 CPN
27
28
29
30
31
DATE 21 MAR 2007
 
For a test, try a CLID table like this example. I used the main number for Microsoft just to keep the original customer's privacy. Put your 10 and 7 digit number in these positions and leave blanks where I have left them. Prompts I did not show do not need to be changed from yours:

[tt]
HNTN
ESA_HLCL 4258828080
ESA_INHN NO
ESA_APDN NO
HLCL 4258828080
DIDN NO
HLOC 8828080
[/tt]

--
GHTROUT.com - Help for Nortel Meridian/CS1000 System Administrators
--
 
I made those changes. Analog line still comes up correctly. Digital line now comes up with HLOC number and extension number. So for you given example of the CLID the caller ID is showing at 8828080xxx, where xxx is the extension of the calling number.
 
You are referring to an analog TN, but have not yet posted an analog TN. So I am wondering if there is some other issue here. What is the CLID of the analog TN?

of robust57 said:
Analog that has correct caller ID
DES UNITY
TN 009 0 00 12
TYPE 2616 <-------- Digital TN type, not analog)

--
GHTROUT.com - Help for Nortel Meridian/CS1000 System Administrators
--
 
Doh, those lines use to be analog, now are digital. So scrap the analog and digital difference. The rest of the information holds true.

Sorrya about that mix u
 
OK. One difference I see between the two TNs is:

CLS CNIA on 004 0 00 01

CLS CNID on 009 0 00 12

See how that relates. In other words, change it and see if that is the factor that is causing the difference.

--
GHTROUT.com - Help for Nortel Meridian/CS1000 System Administrators
--
 
The whole story changes now, I hate not being on site for this specific reason.

The dialing method is what is causing the major difference. I had no idea the users were using this other dialing method so all testing done was under a false assumption. We have one of the dumbest things setup that replaced TIE lines. Basically I've set up BARS/NARS (don't know which one) where AC2 is accessed by dialing a 6. Then there's a set of SPN translations. All they are is basically a speed dial that allows variable input. Here's a sample of this setup.


FEAT esn


MXLC 10
MXSD 300
MXIX 0
MXDM 75
MXRL 75
MXFC 10
MXFS 10
MXSC 0
NCDP 0
AC1 9
AC2 6
DLTN YES
ERWT NO
TODS 0 00 00 23 59
RTCL DIS



SPN 10
FLEN 0
RLI 10
SDRR NONE
ITEI NONE




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



DMI 10
DEL 2
INST 1303295
CTYP SPN


So the difference now is that when somone uses this BARS/NARS method of dialing via AC2 the caller ID shows their extension, when dialing full 10 digits on AC1 the caller ID is correct.

BAH sorry for not understanding my issue fully before posting.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top