Blocking callers using *67 1

[techmeridian]

81c, succession 3.0, ISDN PRI, and symposium in use and we can block vulgar callers by CLID but they can get around it by *67. What's worse is that we can still pull CDR against ANI and both calls will show up in report. AT&T is not very helpful. Has anyone run into this problem and solved it?

 

[johnpoole]

only option is to also block callers without a clid and at&t has there hands tied by regulations.. if the problem persist, file a police report or tell your agents to transfer to 911.. that tends to stop that type of call very quickly

john poole
bellsouth business
columbia,sc

 

[techmeridian]

Does anyone know what is different about what AT&T delivers on a *67 call? Maybe there's something unique there that I can use to deny the caller.

 

[johnpoole]

you can see the diff with a ld 96 msgi x but i don't think that field is read by symposium

john poole
bellsouth business
columbia,sc

 

[GHTROUT]

What if... you Call forwarded the TN (the DN is DID on a PRI) to a Toll Free Number that terminated on the same PRI?

Would your Toll Free vendor show the calling party or would they show the DN that was forwarded, on the billing record?

Point is, you cannot block your number from appearing on the bill when calling a Toll Free Number











~

http://www.GHTROUT.com/

 

[TAnselm]

I ran into this at one of my other sites and I wrote down the solution but I don't have it here at work.

However, I believe that if you turn on MSGI and make a *67 call you will most likely see the number string in the call setup message. The information is there but the switch can't see it becasue of a calling privacy flag. In the Route Data Block there is a prompt for CCP (calling party privacy) Change response to "YES" to override the privacy flag.

I'll look when I get home and if there is more to it, I'll send it later.

 

[TAnselm]

OOOPS, one more thing... Also in the Route Data Block...
Go down to the PII prompt (Privacy Indicator Ignored) and answer "YES" to that one also.

 

[GHTROUT]

TAnselm, it thought those entries were for calls origonated by your PBX, rather than recieved from the PSTN.

Are you saying an incoming caller that blocked CID becomes "visible"? when CPP=YES and PII=YES ?











~

http://www.GHTROUT.com/

 

[TAnselm]

I'm not sure about the CPP that may be for out going. But yes if the incoming caller used *67 to block the incoming digit what that does is put a privacy flag in the data stream which the nortel switch will honor by not displaying digits. By changing PII to yes you are telling the switch to ignore that flag.

This of course is assuming that the digits are present in the incoming data stream. You can check that by turning on MSGI for that trunk. If you see the digits but they are not being display on the phones then simply change PII to YES.

If in fact the digits are not in the data stream then you have to contact your carrier to have them turn on privacy override at their end. This will put the digits into the data stream coming to your switch. As stated above the digits will be there with a privacy flag. So although they can be displayed using MSGI they will not appear on the phone until your answer YES to PII.