Least Cost Routing and Outgoing Caller ID

[gotrojans]

With least cost routing enabled, is it possible to display the caller ID from the originating 3300 ICP? For example, I make a call from the LA ICP (area code 213) to a Irvine number (area code 949). Because of LCR, the call is made local since we have a Irvine ICP. But the caller ID being displayed is from the LA ICP.

Is is possible to have the originating caller ID passed instead of the end point ICP in a LCR environment?

Thanks

Ron

 

[jgideon]

I'll be curious to see what the equpment-specific response it, but the other issue you will face is if the local dialtone provider at the LCR end allows a Calling Party Number that is not on the account that services that location. Most (but not all) LEC's and CLEC's have pretty strict screening on what CPN they allow to be transmitted. If you have the same LEC in both locations it might be easier to get them to change that setting.

 

[MitelInMyBlood]

Assuming you have non-conflicting digit strings between the two PBXs, then you CAN do this using PRI trunks to the LEC in conjunction with the CPN substitution table (accessed via IMAT).

However, as jgideon mentioned, you may have a fight on your hands with the LEC at the far end. We've done this exact thing with calls from our Canadian offices traversing our internal corporate network, but had to use one of the CLECs (Broadwing Communications) to send the calls out to the PSTN. The Incumbent LEC (AT&T) refused, citing some PUC regulatory malarkey.

 

[gotrojans]

Oops! I realized that I made a mistake when I stated "the caller ID being displayed is from the LA ICP." It is the Irvine ICP. I'm assuming that you guys knew that.

It seems like a almost 'yes' that it can be done. With the exception of two offices (Verizon), SBC is our main carrier. If SBC allowed CPN at the LCR end, we might be able to do it with our 3300 ICP's.

MitelInMyBlood, what did you mean by "non-conflicting digits between the two PBXs?" If Irvine was 949.456.1nnn and LA was 213.654.2nnn, then no digit conflict. Yes?

Sorry for newbie questions.

Thanks

Ron

 

[gotrojans]

Based on the early response from our carrier (AT&T/SBC), they do not prevent CPN from being passed from one region to another.

MitelInMyBlood, I'll provide your suggestion to our business partner.

Thanks

Ron

 

[MitelInMyBlood]

SBC = AT&T since the recent merger so your mileage may vary. AT&T said no to us in Texas. Broadwing said yes.

Can you pls clarify, are you wishing to allow ON-PBX users on one ICP in city "A" to use LCR to place external (outside) calls to the other city or are you trying to do complete toll bypass and allow outside callers (from the PSTN) in one locale to dial through your private PBX network (i.e., via DISA) to place external (outside) calls to the PSTN in another distant city?

Both are legal, though the second method may not be if the users are not your employees and are in any way paying for the service. In the second scenario you become a "Common Carrier", the FCC and state regulators get involved and a whole new set of rules apply.

 

[gotrojans]

Yes. We are looking at implementing LCR just for our internal users making outside long distance calls.

No to your second question.

BTW, business partner has started implementing your suggestion on a CPN substitution table. It is working.

Thanks

Ron