CLID on second DN

[Aspectus]

81c with succession 4.5. CLID shows up ok on primary DN but when hunting to second DN, CLID shows up as first DN. Can I get CLID to be passed when hunting to second DN on same phone?

 

[BkMesser]

Put a d after the dn on the second key....

ie... key 1 scr xxxx d

 

[sjm64]

If that doesn't work try to chg your cls=to dndd,icda.I just had the same problem in my switch. I made the cls= dndd.

 

[Aspectus]

Thanks guys...
1st. Correct me if I'm wrong...D parm searches down for first DN with outgoing CLID. All sets have a DID and non-DID. When I got here, they all had the same CLID, you can imagine the mess so I'm changing all that. Second DN has the D parm so it's getting it's CLID from the first DN, this is all fine.
2nd. As for the dndd and icda class, got to try that. I know about dndd (somewhat) but no clue as to icda. Got to look this up.

Thanks

 

[Nortellian]

cls dndd tdd
tdd is tandem digit display and will display who is calling you if you are on your first line. dndd is something about dn display on redirect and if it is dnda than second call will not display for whatever reason.

 

[Aspectus]

Nortellian, you're right, it has nothing to do with icda (allowed or denied result is same). It's dndd that does all, as for tdd all sets already have tandem, but also dnda, so guess some changes are to be made

Thanks to all for your input, I appreciate

 

[Johnthephoneguy]

ICDA wouldnt have anything to do with display, thats for call details! Internal Call Detail Allowed/Denied

You turn that on so your cdr data captures internal calls.

JohnThePhoneGuy

"If I can't fix it, it's not broke!

 

[johnpoole]

1st. Correct me if I'm wrong...D parm searches down for first DN with outgoing CLID

if i want key 4 to display the clid of the did on key 0, i enter the d after the dn.. if i want to it do display my main number i use the clid table for that.. in my case, default clid is the main number, very few users need the did to show.. your talking clid, but the above posts seem to address the inbound.. your key 1 is not sending or rec. clid?

john poole
bellsouth business
columbia,sc

 

[Aspectus]

to John Poole
everything is working fine now, and you're right - key 1 was not receiving clid but cpnd from key 0 and dndd did the trick

as for sending out did's, most people wanted that here but all they got was outing main # since clid table has main number in 0 and seems all sets were build (at some point) with default which would end up being 0. Just trying to get things straight in all this mess.

Question: i would guess that activating internal cdr (icda) for a set could mean buffer consuming - is this why this cls is on a set by set basis?

tks

 

[acewarlock]

Most company's don't care about Set to Set CDR and only use it for special cases.