Block outbound CLID per set 1

[MagnaRGP]

Good Day all.

I seem to be having a skull cramp today. Customer has a CS1ke 5.0 patched to current. They would like to block outbound CLID on certain sets. At a loss, I created a new CLID entry to display zero's for the number, however the customer reports that my change had no effect. Here is the CLID entry:

ENTRY 2
HNTN 416
ESA_HLCL abcdefg <--- number was left for ESA purposes
ESA_INHN NO
ESA_APDN NO
HLCL 0000000 <--- should be zeros, but still sending out
DIDN NO
HLOC
LSC
CLASS_FMT DN

I've assigned this entry to the MCR keys of the necessary sets. Is there a better way? Any reason why this isn't working?

TIA.

 

[phonz1]

just prt a tn and make sure it shows key 0 xxxx 2

 

[spunkysus]

You can block at set level in the class of services I beleive CLBA

Thanks

 

[MagnaRGP]

@ phonz1 -- as indicated I have changed the sets to reflect key 0 mcr xxx 2 and key 1 mcr xxxx 2 and this didn't work.

@ spunkysus -- I'll give that a try and see what happens.

I've just noticed an omission in my original post:

HLCL 0000000 <--- should be zeros, but still sending out

should read:

HLCL 0000000 <--- should be zeros, but still sending out 416abcdefg

I have other CLID entries assigned to sets where ESA_HLCL is 416abcdefg and HLCL is hijklmn. In this case I have tested ESA calls and they display 416abcdefg while a non-esa call from the same set shows 416hijklmn. This is why I left the ESA_HLCL in the entry.

I'll post back the cls result.

 

[phonz1]

Magna, was just making sure that your change took....

 

[MagnaRGP]

@ spunkysus

Good call. CLBA was the ticket. Have a star.

Thanks

 

[spunkysus]

Thanks, Magna glad we could assist

 

[sporty2]

Just a note on what I have found lately with the Telco's.
It seems that at the CO level they are now doing a DID screening table that is a sort of lookup for your outbound CLID. result is that if the CLID you are sending out is not in their screening table the main billing number assigned to the trunk group is sent.

sporty2

 

[roupe]

sporty2 is correct When our first pri with clid went in in 1990 the co would send whatever you sent from the switch. Every pri I have implemented for my customers in the past 10 years is screened by the CO so that an incorrect or someone else's number is not being sent. When the clid feature first came out on Nortel switches you could only send the ldn or the key 0 of the set. We sent out a lot of wrong numbers!
This being said how does a company on the net offer to send any name or number for your call if you pay their fee?