Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

Callmanager Caller ID issue after a call foward

So the pstn service providers seem to be upgrading their internal switches. They are now blocking outbound calls from their system that do not have the correct external mask on it. For example, if the PRI at the site has 408-555-XXXX block, the mask must match or the call gets rejected.

when the phone is set to call forward all to say a cell phone, CUCM is putting the calling number as the mask... so this is not good. Call gets rejected.

Im trying to figure out which setting I could us to fix this on the call forward settings.

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Callmanager Caller ID issue after a call foward

Well, you may be in luck in the future with TPAC. I got this email and it looks like there is a Broadsoft upgrade that fixes this issue that they plan to apply-

MARKETING FLASH SmartVoice PRI Service Outbound Calling Line ID and Name

Outbound Calling Line ID and Name Works Differently on SmartVoice

Why? SIP works differently than traditional TDM PSTN (voice) networks with regard to outbound Caller ID.

With SmartVoice, the customer's telephone number is used to authenticate and authorize access to the TelePacific SIP network.

-Because the customer's telephone number is used in this way, all telephone numbers sent by the customer's equipment to the TelePacific SIP network must be assigned to the customer's account on the SIP network.

-If the customer's equipment sends a telephone number that is not assigned to their account the call will fail.

-So... unlike traditional voice services, the customer's PBX does not fully control Caller ID and name for outbound calls.

There are two options available -

1. The customer can use a single billing telephone number (BTN) as the Caller ID for all outbound calls.

2. Or they can use all the local TelePacific telephone numbers assigned to their account as the outbound caller ID

Only one name per trunk group is supported for either option.

How does this impact Call Forwarding on SmartVoice PRI Services?

If the PBX forwards a call to our network with the Caller ID of the original PSTN caller that telephone number is not assigned to the customer's SmartVoice PRI trunk and the call fails.

Is there a work around?

Yes; there are three ways to support forwarding calls from the PSTN with a SmartVoice PRI.

What if none of these three options meet the customer's requirements?

Please recommend another TelePacific PRI service.

Will SmartVoice PRI ever work more like a traditional PRI with regard to outbound Caller ID?

Yes; TelePacific is scheduled to apply Broadsoft Service Pack 9 (SP9) late 3Q 2009.

Click here <http://rs6.net/tn.jsp?et=1102588239141&s=63&e=001Ogj4nVI5wdHBHk30w8ME5G0MHQzXcOpiVFm3niENJp7phkqXYvTRotTdeCNrvrw-Tta56wytIJ1XS_Rq7EQj4z5ScY5tleTVAcKH2VInntchKwj8gjy3BvqoOMz1zLDEBqnchOzwOWX7kgKWlE548RcXObjelVIUCyf6oQLC2D9gLYldJinWrs_j_Ln3tTyo> for details.

Click here <http://rs6.net/tn.jsp?et=1102588239141&s=63&e=001Ogj4nVI5wdHHFcgpobQsOnxp-cEZ-XyW5wLOmWw1awmCba-gvxmvdEtvZFHpvCTknO8XecAtknXP4hrA29zH5yTkmv43AMBlKYpimCEGz8g4oA6JQN7QHg2alXzopkI15sxkF0qs0EPreL-RNR8wTCRoO5O9vLXM> , if you missed a past Telepartner Marketing Flash.

Telepartner Team TelePacific Communications

877-GO-AGENT

-- please remember to rate and mark answered helpful posts --
10 REPLIES

Re: Callmanager Caller ID issue after a call foward

I'd say there is about a 99% chance this is a Broadsoft based softswitch behind whatever PSTN service you have. I can't understand why Broadsoft wont fix this or more CLECs figure out a way around it.

Sorry, I don't know if this can be addressed in CM. In most cases you can tell the CLEC to push the main# for all caller ID to work around this, but it is not a very nice work around since you lose caller ID per DID and can't see who is call forwarded to you.

For what it is worth, there is one CLEC I have come across that uses Broadsoft, but doesn't have this problem: Cbeyond.

Their engineers won't talk about how they implement it though and I don;t blame them.

Some CLECs I know that do have this problem- Telepacific's Smartvoice product, XO, Fastmetrics. Lastly, any provider that uses Sonus or Syllantro soft switches don't seem to have this issue either.

-- please remember to rate and mark answered helpful posts --

Re: Callmanager Caller ID issue after a call foward

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.

Re: Callmanager Caller ID issue after a call foward

Well, you may be in luck in the future with TPAC. I got this email and it looks like there is a Broadsoft upgrade that fixes this issue that they plan to apply-

MARKETING FLASH SmartVoice PRI Service Outbound Calling Line ID and Name

Outbound Calling Line ID and Name Works Differently on SmartVoice

Why? SIP works differently than traditional TDM PSTN (voice) networks with regard to outbound Caller ID.

With SmartVoice, the customer's telephone number is used to authenticate and authorize access to the TelePacific SIP network.

-Because the customer's telephone number is used in this way, all telephone numbers sent by the customer's equipment to the TelePacific SIP network must be assigned to the customer's account on the SIP network.

-If the customer's equipment sends a telephone number that is not assigned to their account the call will fail.

-So... unlike traditional voice services, the customer's PBX does not fully control Caller ID and name for outbound calls.

There are two options available -

1. The customer can use a single billing telephone number (BTN) as the Caller ID for all outbound calls.

2. Or they can use all the local TelePacific telephone numbers assigned to their account as the outbound caller ID

Only one name per trunk group is supported for either option.

How does this impact Call Forwarding on SmartVoice PRI Services?

If the PBX forwards a call to our network with the Caller ID of the original PSTN caller that telephone number is not assigned to the customer's SmartVoice PRI trunk and the call fails.

Is there a work around?

Yes; there are three ways to support forwarding calls from the PSTN with a SmartVoice PRI.

What if none of these three options meet the customer's requirements?

Please recommend another TelePacific PRI service.

Will SmartVoice PRI ever work more like a traditional PRI with regard to outbound Caller ID?

Yes; TelePacific is scheduled to apply Broadsoft Service Pack 9 (SP9) late 3Q 2009.

Click here <http://rs6.net/tn.jsp?et=1102588239141&s=63&e=001Ogj4nVI5wdHBHk30w8ME5G0MHQzXcOpiVFm3niENJp7phkqXYvTRotTdeCNrvrw-Tta56wytIJ1XS_Rq7EQj4z5ScY5tleTVAcKH2VInntchKwj8gjy3BvqoOMz1zLDEBqnchOzwOWX7kgKWlE548RcXObjelVIUCyf6oQLC2D9gLYldJinWrs_j_Ln3tTyo> for details.

Click here <http://rs6.net/tn.jsp?et=1102588239141&s=63&e=001Ogj4nVI5wdHHFcgpobQsOnxp-cEZ-XyW5wLOmWw1awmCba-gvxmvdEtvZFHpvCTknO8XecAtknXP4hrA29zH5yTkmv43AMBlKYpimCEGz8g4oA6JQN7QHg2alXzopkI15sxkF0qs0EPreL-RNR8wTCRoO5O9vLXM> , if you missed a past Telepartner Marketing Flash.

Telepartner Team TelePacific Communications

877-GO-AGENT

-- please remember to rate and mark answered helpful posts --

Re: Callmanager Caller ID issue after a call foward

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!

Hall of Fame Super Gold

Re: Callmanager Caller ID issue after a call foward

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.

Re: Callmanager Caller ID issue after a call foward

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..

-- please remember to rate and mark answered helpful posts --

Re: Callmanager Caller ID issue after a call foward

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.

Hall of Fame Super Gold

Re: Callmanager Caller ID issue after a call foward

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.

Re: Callmanager Caller ID issue after a call foward

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.

Hall of Fame Super Gold

Re: Callmanager Caller ID issue after a call foward

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.

547
Views
0
Helpful
10
Replies
CreatePlease login to create content