Outbound Caller ID issue in Massachusetts only (?) 2

[edmhtel]

I'm running a shared-tenant environment in Boston, and would like my Nortel switch to send each client's name and number over the PSTN, but the ILEC won't let me. They claim that unless I were to register as a service re-seller, they MUST send a name themselves, and the only one they can send is the name on the bills (my company). Disabling outbound caller ID is apparently not an option, either. The situation is not acceptable to my clients. The ILEC is citing some MA privacy law, but has been unable to produce a copy of the law or ruling. I believe they have us confused with telemarketer rulings. Other carriers are willing to do it my way. Has anyone run across this before? Any info. or insight would be appreciated!

 

[PERRYPJ]

I TOOK CARE OF A SHARED TENANT BUILDING IN MIAMI FLA, I KNOW IN FLORIDA YOU HAVE TO REGISTER IN ORDER TO BE A TRUE SHARED TENANT BUILDING.

OLD ROLMEN WORKING ON NORTELS

 

[jgideon]

In the US, you can't SEND a name anyway... regardless of what you program in a PBX. Caller ID Name is retrieved by a database dip from the far end by the receiving telco, assuming they have billing arrangements set up with the provider of the DID range. (As an example, Verizon and SBC aren't playing nice, so I don't receive most SBC 'name's on my 'Verizon' callerID)

The only way I know to change what name displays is to have the LEC or CLEC change the name in the LIDB database, and if they told you they won't do it, then I think you're stuck.

 

[edmhtel]

Becoming a reseller isn't really a viable option for us. We are talking to a CLEC about porting our DID's to them and building my client names into their CNAM database on a per-number basis. I'm assuming that's the equivalent of the LIDB list you mention because it is the source of info for the terminating carrier's dbase dip.
When we do adds or deletes on site, we'll have to manage the CNAM list going forward, but that looks like a small price to pay to keep my client's identities intact!
Thank you both - your insight has helped clear this foggy area!
Ed

 

[jgideon]

edmhtl--sounds to me like you're on the right track, if your CLEC is willing to let you do that. Good luck, and let us know how it turns out!

 

[Ghostin]

A bit of warning. Some CLEC's will promise you the world to get your business, but not deliver. Get it all in writing, and preferralby test it, if possible, before porting. JGideon makes a good point, you can't "send" name across a cicruit, it comes from the phone company. If you new CLEC is going to register your customers with thier own "number" you can do it then. Beware, if you change customers alot, you may have to make a lot of changes, and they may charge you to do so.

 

[ISDNman]

Are you on PRI? If so you can send the number in the Called Party Number Information Element IE) in the call SETUP message. Chances are the PBX should do this routinely.

There are ways to do this using ANI on other types of trunks, but it gets much messier

You may also be able to set the screened bit, but I doubt most PBX's allow you to set that. If you can hack the PBX into sending it and marking it "screened" perhaps the CO switch will pass it as is.

If you do have PRI you may want to have a look wiht a protocol analyzer and verify the CPN IE is present. If not you'll need to solve that first and hope that the LEC just doesn't know what they are talking about.

I do know that many CO's will pass any number sent by a ISDN PBX on PRI (but not BRI). But I don't know for sure all do.