CallManager 6.0 - Changing the Caller ID for outbound calls to reflect a different number

[dgarcia]

Hi Guys,

I really need help on this one...

I need to change the caller ID on a user's phone so that it reflects a differnet number when he places calls. The change is as follow:

From: 3059150544 to 3039453325

Right now, the user is able to make and received calls. But we have this user at home in his Denver office and we need to change his current 305xxxxxxx number (Miami area code) (this number is part of our pool of DIDs) to his forwared DID number 303xxxxxxx (Denver area code)

The cisco IP phone is connected to our CallManger 6.0 by using a static TFTP Server option for this remote user. The only problem is that when he makes calls the number that appears is his 305xxxxxxx and we want to change it because he is in another City.

Please any help would be appreciated.

Thanks...

P.S:   I have tried changing it in the "Directory Number Configuration" -- using the option "External Phone Number Mask", but no luck.

[Jaime Valencia]

Lets start with this, where are you doing the translation????

Route pattern??

route group??

gw??

Only if you're doing it on RP with the checkbox for the external phone number mask that change will take effect.

You might want to look into transformation patterns/translation patterns or create a separate group of route patterns for that user.

But you need to start by knowing where you're doing the translation right now.

HTH

java

If this helps, please rate

www.cisco.com/go/pdihelpdesk

[dgarcia]

If i enable "Use Calling Party's External Phone Number Mask" it will show the 305xxxxxxx caller ID.

Thanks,

[dgarcia]

java,

Thanks for the reply and input.

Im doing the translation using the option "Translation Pattern"

Please see below:

[Jason Bree]

Would it not be easier to just use the external phone number mask field on the DN settings?  Just put in the 10 digits you want outpulsed.

[dgarcia]

Jason,

Thank you for the update. I did that but still displays the 305xxxxxxx number when placing calls.

[yixiu0317]

First,please check with your local telco see if they support showing different area code number from your Miami gateway

Then have a calling party transformation pattern, the pattern is his Denver home number, have a new partition for this pattern, and add this partition in the Miami gateway CSS(on the top of the partition list), have 10 "X"  in the calling party transformation mask

[dgarcia]

Yiziu0317,

Thanks for your input. I actually spoke with the service provider at my local telco, and they said that 303 area codes could not be added to my local pool of numbers since they do not host them. This is why we had to go with another provider to purchase the DID number and forward it to our local pool of 305. numbers.

Dispite this issue, i created what you sugested but still no luck.

I don't know if there anything else I can try doing ? Any other suggestions?

Thank you all...

[Tracy Larson]

The way I get the caller ID to work with whatever I want it to show outbound is:

On your Route Pattern, under Calling Party Transformations, Check the box that says "Use Calling Party's External Phone Number Mask"

Where it says "Calling Party Transform Mask" put in ten X's and click save.

Now on the phones line appearance, put in the 10 digit number that you want to see outbound in the "External Phone Number Mask" field. Click save and try.

[dgarcia]

Tracy,

Thank you for the update and your help. I made the changes but still the 305. number comes out when placing calls.

Any other settings I have to check? or Does this change takes time to take effect?

NOTE: The 305 number that comes out it's always the main office number which is under our pool of registered DIDs.

Thank you all for your inputs,

Please advise.

[Tracy Larson]

Make sure you dont have anything specified on your gateway itself as well as far as the field for "Caller ID DN" under the Call Routing Information - Outbound Calls section goes.

Also, are your gateways MGCP or H323? You can also issue the commands of "debug isdn q93"1 then "term mon" to see what you are actually sending outbound to the Telco. If you are sending the full 10 digits to them and the caller ID still not showing what you want then they are not allowing you to send out what you are wanting to.

[dgarcia]

Please see attached for my gateway config.

Thanks again.

[dgarcia]

Tracy,

It looks like the gateway it's showing the correct CallerID when the calls is placed but somehow the called person still shows the 305xxxxxxxx number instead:

Jan 18 15:16:01.786 EST: ISDN Se0/0/0:23 Q931: pak_private_number: Invalid type/plan 0x0 0x0 may be overriden; sw-type 3

Jan 18 15:16:01.790 EST: ISDN Se0/0/0:23 Q931: Applying typeplan for sw-type 0x3 is 0x2 0x1, Calling num 3035544543

Jan 18 15:16:01.790 EST: ISDN Se0/0/0:23 Q931: Sending SETUP  callref = 0x3C46 callID = 0xBBC8 switch = primary-5ess interface = User

Jan 18 15:16:01.790 EST: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8  callref = 0x3C46

        Bearer Capability i = 0x8090A2

                Standard = CCITT

                Transfer Capability = Speech

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA9838A

                Exclusive, Channel 10

        Calling Party Number i = 0x2181, '3035544543'

                Plan:ISDN, Type:National

        Called Party Number i = 0xA1, '3057825241'

                Plan:ISDN, Type:National

Jan 18 15:16:02.150 EST: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8  callref = 0xBC46

        Channel ID i = 0xA9838A

                Exclusive, Channel 10

Jan 18 15:16:04.442 EST: ISDN Se0/0/0:23 Q931: RX <- ALERTING pd = 8  callref = 0xBC46

Jan 18 15:16:12.546 EST: ISDN Se0/0/0:23 Q931: RX <- CONNECT pd = 8  callref = 0xBC46

Jan 18 15:16:12.550 EST: ISDN Se0/0/0:23 Q931: TX -> CONNECT_ACK pd = 8  callref = 0x3C46

Jan 18 15:16:18.610 EST: ISDN Se0/0/0:23 Q931: RX <- DISCONNECT pd = 8  callref = 0xBC46

Jan 18 15:16:01.786 EST: ISDN Se0/0/0:23 Q931: pak_private_number: Invalid type/plan 0x0 0x0 may be overriden; sw-type 3

Jan 18 15:16:01.790 EST: ISDN Se0/0/0:23 Q931: Applying typeplan for sw-type 0x3 is 0x2 0x1, Calling num 3035544543

Jan 18 15:16:01.790 EST: ISDN Se0/0/0:23 Q931: Sending SETUP  callref = 0x3C46 callID = 0xBBC8 switch = primary-5ess interface = User

Jan 18 15:16:01.790 EST: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8  callref = 0x3C46

        Bearer Capability i = 0x8090A2

                Standard = CCITT

                Transfer Capability = Speech

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA9838A

                Exclusive, Channel 10

        Calling Party Number i = 0x2181, '3035544543'

                Plan:ISDN, Type:National

        Called Party Number i = 0xA1, '3057825241'

                Plan:ISDN, Type:National

Jan 18 15:16:02.150 EST: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8  callref = 0xBC46

        Channel ID i = 0xA9838A

                Exclusive, Channel 10

Jan 18 15:16:04.442 EST: ISDN Se0/0/0:23 Q931: RX <- ALERTING pd = 8  callref = 0xBC46

Jan 18 15:16:12.546 EST: ISDN Se0/0/0:23 Q931: RX <- CONNECT pd = 8  callref = 0xBC46

Jan 18 15:16:12.550 EST: ISDN Se0/0/0:23 Q931: TX -> CONNECT_ACK pd = 8  callref = 0x3C46

Jan 18 15:16:18.610 EST: ISDN Se0/0/0:23 Q931: RX <- DISCONNECT pd = 8  callref = 0xBC46

[Tracy Larson · Accepted solution]

If the gateway is showing outbound what you are wanting to see via the debug's but the called party is still not seeing what is being sent, then I would have a conversation with your telco as they dont seem to be passing it all the way through.

[dgarcia]

Thanks.

The problem was that our Telco provider could not pass non-registered caller ID. We had to be bind in to a different service contract in order to advertise our own caller ID.

We ended up using a SIP Trunk with outgoing/incoming calls usage with the ability to use our own caller ID.

Regards,