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

Problems with OG CLID

Status
Not open for further replies.

rpneal44

MIS
Apr 1, 2003
97
US
I've been trying to assign outgoing CLIDs to several extensions at my site and am having limited success. These involve the "roll-over" line on ACD sets. Set type is 1140E. Below is an excerpt of the key programming:

KEY 00 ACD 1030 0 53441
AGN
01 NRD
02 MSB
03 SCR 2x41 0 MARP
CPND
NAME ECC Supervisor
XPLN 14
DISPLAY_FMT FIRST,LAST
04 SCR 52x41 10 MARP
CPND
NAME ECC Supervisor
XPLN 14
DISPLAY_FMT FIRST,LAST
05 DSP

The problem is that key 4 will not send out the CLID of key-3. Key 3 works fine, sending out the correct CLID info. All I get for OG caller ID on key 4 is the CO assigned number (which is not even the lead number in the DID group). I've tried using several different settings in the CLID programming (LD15, NET_DATA). Below is the current CLID 0 & 10 set-up:

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

ENTRY 10
HNTN
ESA_HLCL
ESA_INHN NO
ESA_APDN YES
HLCL 6xx360
DIDN SRCH
HLOC
LSC
CLASS_FMT DN

CLID = YES in LD17_PARMs. Is there something in the RDB I'm missing? Could the CO be restricting the OG CLID? (filters?) I have several other stations that would like to output their numbers located at another site (that are CFW to here). I suspect that these issues are all related, and if I could get one of them resolved the others would follow.

Suggestions please...

Phildo



Phil, the Phriendly Phone Man
 
G - Tried that already. No change.

Phil, the Phriendly Phone Man
 
Setting it to "D" will make it send out the CLID info of Key 0. Looks like a dilemma. Still thinking....

War Eagle!
Lions Baseball '09!
 
You could "hard code" HNTN and HLCL and DIDN no, unless that would be too many entries, sets to use a work around.

HNTN
ESA_HLCL
ESA_INHN NO
ESA_APDN YES
HLCL 6xx360
DIDN SRCH
HLOC
LSC
CLASS_FMT DN


Mato' Was'aka
 
BigIndian - Tried that, too, already. Still get the default CLID assigned by CO

Phil, the Phriendly Phone Man
 
That's the only way I can think to make it work. Every ACD set will have to have its own CLID table entry for the key 4 extension.

War Eagle!
Lions Baseball '09!
 
That's not right at all, I wonder if it isn't even your problem???

Mato' Was'aka
 
BigIndian - That was what I was thinking, but I wanted to pursue every other avenue before I turned it over to the CO as a trouble. I put it out here to get others' feedback on what I'd already done.

Still looking for ideas, tho.

Phil, the Phriendly Phone Man
 
The link to the CLID document includes some things that are not in all book sets. Just in case you had not opened it.

Not sure your answer is in there or not.

~~~
[small] [©] GHTROUT.com [⇔] A Variety of Free Resources for Nortel Meridian/CS1000 System Administrators [/small]
 
G - I've had a copy of your CLID docs for a while, and tried many of the combinations listed therein, before I posted.

Telebub - The DIDN = SRCH tells the entry to search for the first DID number on the phone. See GH's docs. Good stuff. He's put a lot of time into them over the years.

Phil, the Phriendly Phone Man
 
BI - The way I understand G's CLID docs is tht it would start its search at key 0 and look for the first DN with CLID DIDN entry=yes.

Phil, the Phriendly Phone Man
 
I might be up to speed (duh) I was thinking you wanted 3 to send 3 and 4 to send 4, sorry. have you tried taking srch out of the mix?

Mato' Was'aka
 
BI - I've tried DIDN = yes & no, as well as the current SRCH. No affect yet. Also, something I found strange, there is no OG CLID unless both NPA/NXX is programmed at the HLCL prompt. It was my understanding that the NPA should be programmed at the HNTN and NXX at the HLCL for it to work.

Phil, the Phriendly Phone Man
 
I had that problem w/ a toll free entry once, and had to put the whole string at hntn and hlcl to get it to fly.

Mato' Was'aka
 
Any particular reason why you are using 10 for key 4?
Have you tried using 0 on key 4? D entry should have worked, you use that for either key 1 on typical setup or key 4 for acd.
Always been my experience that most CO's want to see 10 digits npa-nxx-abcd. If they do not recv 10 digits, the default # will be sent instead
What shows up when you trace calls from these two keys?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top