CICS Block Caller ID on all Outgoing Calls

[doughonea]

I need to block outgoing caller ID on all outgoing calls. We're a doctor's office, and unfortunately, we have a problem with the patient's returning calls to the number that shows on their Caller ID. Since CICS is programmed to use numbers from the bottom of the hunt group for outgoing calls, the patients are encountering frequent busy signals. Our Telco, Verizon, says the only way to show the main number on all lines is to use a PRI (not cost effective). They also say they cannot institute blocking of all outgoing caller ID on those lines (though no one seems to be able to explain why), but we can do per call blocking.

I found this suggestion in another post and it appears to me that it will accomplish my goal of blocking outbound caller ID.

Route 001 use Pool A, dial digits *67
Dest Code 9 told to use Route 001 (must remove 9 from Access/External/Pool Codes first)
Set dials 9 then number (when steady dial tone returned)

I can use the manuals to find instructions on programming the route function. How do I remove the '9' from the Access/External/Pool codes? Are there three separate places I have to make that change? I'm only using pool A, and only the first line of the hunt group appears on any phone (for those rare times we need to forward the main number to an answering service).

I appreciate any assistance. Total hand holding is not required here, but guidance is very much appreciated. I have installed four CICS systems in my practice's offices over the past couple of years, but since I do programming so rarely, I have to do a refresher every time I do something other than a very routine change.

Thank you.

 

[allworxguy]

Sounds to me like your telco is being lazy. The Caller Id of all POTS lines in a hunt group can made to display the pilot number of the group. BTW CICS does not support PRI anyway.


If the Telco won't cooperate, I would simply put a speed dial button on the phones that dials 9*67

You could set up a route that will insert *67. You will need to remove the pool code "9" and create a destination code 9 that access the route that inserts your Caller Id block code.

Remove poolA code SYSTEM PROGRAMMING > ACCESS CODES > POOL CODES > POOL-A



Marv ccna

http://www.telemarv.ca

 

[curlycord]

Also skip Line Pool Codes by pressing NEXT a couple more times until you see Extrnl Code....make it NONE

=----(((((((((()----=
curlycord

http://www.curlycord.com

Toronto Canada

http://www.telcopc.ca

 

[curlycord]

This may help for routing:

http://www.tek-tips.com/faqs.cfm?fid=2078

=----(((((((((()----=
curlycord

http://www.curlycord.com

Toronto Canada

http://www.telcopc.ca

 

[doughonea]

allworxguy: The Telco implied that they weren't allowed to line block (?by tarrif?). When I said I'd had it done before they replied, not by Verizon. Maybe the CLECs can do things the ILECs cannot do. For a PRI, I'd have to get an Adtran and a breakout box. Like I said, not cost effective.

I'm going to work on the route method. Thanks for the guidance, both allworxguy and curlycord!

 

[doughonea]

Anybody have any idea what effect, if any, this would have on a 911 call? I don't think 911 uses caller ID.

 

[allworxguy]

*67 does not block 911

I wasn't talking about block caller ID by the provider, but making caller ID the same for all lines in the hunt group. The pilot (published) number. Here you can pay an extra fee per line to have it made "private number".

Marv ccna

http://www.telemarv.ca

 

[doughonea]

I will call them back tomorrow and ask about that, but the one rep I spoke with today said I'd have to split off the hunt group to a separate account. Honestly, sometimes when you are talking to these guys, it's easier to just hang up and look for another way!

 

[exsmogger]

I'd also suggest inserting a pause after *67 if you decide to use a route.

Brian Cox
Georgia Telephone

http://Georgia-Telephone.com

http://www.linkedin.com/in/briancox1952

 

[curlycord]

Actually Marv the "Local Link" package from Bell Canada in Toronto always (at least used to) gives the main billing # as the caller ID.....a pain in our ass when we are trying to ANAC the lines during troubleshooting.
Local Link is years old now, seems Verizon is behind the times and it is always Verizon with the most issues.
I did a quick Google and AT&T seems to provide the same feature.

-When calling out it is always best to leave a message with your main # and not just hang up!!!

-If you have "Call Forward" feature on your lines from Verizon then forward lines 2 and up back to line #1

-Make sure receptionist says something to the caller when they get a call on a middle line with nobody on the above lines.
They should state the main number and mention "as advertised".

-or make sure not to answer the calls that come in the middle of the hunt group, just like a wrong # call.

-Threaten to get another carrier if they cannot complete the request or ask for a supervisor.

I personally think returning a call based on caller id just complete stupidity.
If the caller wanted you to call them back they would have left a message or call again later, otherwise pretend they never called you.... so plain and so simple.

-Hello
-Yes, somebody called me from your number
-Oh nice, aren't phones cool?
-You didn't call me?
-I don't know, you didn't say who you are or what phone number you are calling from.
-XXX-XXXX
-Nope, cant say that was me.
-Well somebody called from your number.
-Could be, we have 300 employee's and a hundred phone lines, should I ask who called you?.
-No....that's ok.
-all right, cya


















=----(((((((((()----=
curlycord

http://www.curlycord.com

Toronto Canada

http://www.telcopc.ca