You are correct. It's Telepacific. I also had the problem with XO. I had to switch their gateways to h323 and put in dial-peers to over-ride everything to their main number.... that fixed it, which sucks because there is nothing we can do in CUCM.

Im not sure what to do about this one. I hate to tell them that it's their main number overide everything and not have their own caller ID, but ..... it's a little hard to strong arm a CLEC to say fix it.

Some Telepacific engineer mention TN masking, but not sure what that would be equal to in CUCM, if anything.

ho-hum.

You are the man. Man..... What timing.... I was ready to raise heck in Monday AM with telepacific.

If I could give you a 100 points, I would. but here is 5. Love the forums just for this knowledge sharing.

Cheers!

Wow, much fuss for something that is absolutely routine in the rest of

the world:

If the calling number does not fall in the assigned range, it is overwritten with a "main" number. No call ever falls.

Real ancient people will remember that it the same with X.25 networks.

But, the US telcos wanted to give PRI user the privilege of presenting the calling number they wanted... from here everything started.

True, this is likely only a problem in the US or N. America, but not because the way PRI works or the ability to control caller ID as much as the most prevalent soft switch provider, Broadsoft, that is used by the majority of CLECs in the US is so slow in responding to issues like this.. X.25 is little before my time, but I believe your example ;)

So in other parts of the world on BRI/PRI you cannot choose your outbound caller ID via your PBX? What if you are a company with 5 toll free numbers, for example? The TF numbers aren't normally provided by the CLECs here so how would you be able to send correct, chosen caller ID when making calls? Another example I get a lot is a block of DID numbers where some users want to show their DID while others prefer to show the main company number..

Hello,

Basically you would just configure at the route group/route list level in CCM the main number you would like to send out as caller-id. On the route pattern, leave the "use external calling party mask" unchecked. And place this route pattern in a partition that is visible to the calling search space of the users in which you would like to send the main number on caller id, and point the route pattern to the applicable route list.

For the users that want to send their DID, make another route pattern and check the "use external mask" box, and point this to another route list that doesnt change the caller id. Place this route pattern in a partition that is visible to the calling search space of the users who would like to have their DID sent out.

Hope that made sense, if so please rate.

Yes, you can choose your outbound caller ID as long it falls within you assigned DID range.

I never seen any company calling with a toll free number CLID. In these cases they usually restrict CLID presentation altogether.

It's a catch 22 on this one those. yes, you can have the LEC overide your outbound caller ID with anything in your block. Say my block is 555-8900 to 8999. I want the LEC to overide my caller id I send from my pbx with 555-8900 for all outbound calls.

Sure, easy. But if the customer wants to have their DID show up as caller ID on outbound calls, it works fine. But as soon as they put their phone on Call Forward, the call will fail because the Calling Number is now the originating caller on the outbound, which then fails because of the crappy software on the broadcom switch.

As mentioned before. Configuring so that calling number is the forwarder phone is a single click operation, so not really much of a problem.

I agree that calls should never fail due to whatever calling number is sent, just overwritten.

From overly permissive to excessively restrictive, one can tell that Americans never took ISDN for serious.