Can you spoof CID on Hicom 150?

[donb01]

Does anyone know how to change the CID information on a Hicom 150 with ISDN PRI as primary trunking? I support a medical network, and we often have situations where privacy is important. My "normal" equipment is 9006-based also on PRI, and for the physicians and nurses who typically call patients at home I change the subscriber ID sent out by the system to the main phone number of the clinic - that way when the customers think they are getting around the system they are really calling the number they should be.

In the case of the 150 it does not appear to be that flexible. I have the choice of sending out the correct phone number for the phone that is dialing out, or putting "none" for some of the parameters, which causes the circuit to default to its SPID number - which is also not the number I want the customers to call back. In this case my published number is the pilot of an ACD group, and I have the Optiset phones that belong to this group set to block CID, which sends out "Private". Customers who have privacy manager have these calls blocked by default, and my staff complains they cannot return customer calls from their phones. If I unblock the CID information the customers then dial direct to the phones and bypass the ACD group, which leaves the people in the ACD group on hold seemingly forever.

Anyway - Ideas for solutions are appreciated.

 

[ISDNman]

Is the 150 on PRI? From your description I think not.

If it is on BRI you might try entering your LDN for the "DN" on all of your BRI's.

Let us know if this works.

 

[donb01]

Yes it's on PRI.

 

[ISDNman]

There are no spids for PRI, which is why I am confused.

So just enter the number you want sent wherever these "spid numbers" are entered and that should do it.

Best of luck.

 

[donb01]

Thanks. I've not found a way yet where I can have a number come out per client other than the one assigned to each phone. I have DID on site. The PRI has an alternate number assigned for billing purposes that is not part of my dial plan, but it rings in if you dial it - They call this the SPI number on all the paperwork, and verbally refer to it as the SPID. If I configure the switch properly it will give out the station number of the phone making the call. If I misconfigure the switch (on purpose) it will send out every call with this SPI number. Problem is there are 4 different clinics in that building and the other clinics all WANT to give their numbers out to the patients. This is the only one that has a "phantom" number for dial-in to the UCD group. I can block caller ID on the phones in the UCD group so the customers do not get them, but then the caller-id comes up as "private" and this is causing problems for our customers that block calls that do not have a valid ID (and I would assume there must be some kind of emergency personnel phone override for that or it would never be allowed).

Oh well.... Maybe I'll contact AT&T and see if they have any bright ideas

 

[keyset6]

I'm not sure if this also applies to the 150, but in the 3000s you can just have CID send out the main number. According to my notes: In Lines/Networking, Routes, Select the trunk group. In PABX number-outgoing, if PABX number and Supress station number is selected only number in the PABX number field will be sent.

 

[donb01]

You're right, it does work that way. Problem is that I don't want the customers calling THAT number either. Basically I'm in a situation where I have a "multi-tenant" building, even though all the tenants are divisions of my own company. I need to be able to choose what number comes out by default for each tenant. I could designate certain trunks for this purpose but unfortunately I'm using ISDN PRI so everyone shares the same trunks - just the DID blocks are different.

I actually think I'm out of luck on this one. The problem is more with the way AT&T Privacy Manager blocks calls marked "Private". I can block the phones from sending their ID's, but then the privacy manager crap blocks our calls back to our customers.

 

[keyset6]

Ok I see what you mean, and yea that privacy manager should be called something else. Unfortunately the 150/3000 isn't quite as flexible as the 9006 where you could enter whatever you want in the PUBSCR field. I've played tricks with that over the years with that. I know a hospital that sent out a particular number with every call. If that number was called back a recording would state the caller has reached ABC hospital but the specific calling number cannot be displayed. I can see in a tenant situation that wouldn't apply.

 

[ISDNman]

Maybe break the PRI into multiple OB trunk groups with a different number for each? not efficient trunk wise though.

Maybe assign a few channels to each company with a trunk group and then have an overflow group with no ID?

This would at least reduce the problem.