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.

New Member

Caller ID on outbound calls issue

We are running CCM 4 and I have one phone's caller ID info configured to display correctly.

However when calls are made they are showing up on external phones as 655 prefix. CCM is configured for 720 prefiox. Also the name is wrong. When I debug a call on the outbound gateway it shows calling party as 655-xxxx.

Im at a loss why and where else I need to change it. Could it be something cached ?

7 REPLIES

Re: Caller ID on outbound calls issue

Make sure that you have configured the Caller ID and the Name correctly.

Please see below the places in callmanager administration where you can configure caller ID:

------------------------------------------------------

1) "Directory Number Configuration" page.

Scroll down to "External Phone Number Mask". Enter here the number that you want to send to the PSTN. Then click on "update" at the top of the page. You have to repeat this same procedure for the other extensions configured for this IP Phone (if you want to send those numbers also to the PSTN).

------------------------------------------------------

2) "Route Pattern Configuration" page.

Locate the route pattern that you are using for doing calls to the PSTN.

Scroll down to the "Calling Party Transformations" section.

- If you check the "Use Calling Party's External Phone Number Mask" checkbox, you will use the number that you configured in the "Directory Number Configuration" page as caller ID.

- If you uncheck that checkbox, then you can configure the "Calling Party Transform Mask". Just enter here a number like, as an example, 978858xxxx (callmanager will fill out the xxxx with phone's 4-digit extension).

------------------------------------------------------

3) "Route List Detail Configuration" page.

Go to the "Calling Party Transformations" section.

"Use Calling Party's External Phone Number Mask" > if you set it to "on", you will use the number that you configured in the "Directory Number Configuration" page as caller ID. If you set it to "off", then you need to configure the "Calling Party Transform Mask" (next line on this same page). The setting that you use here will override the settings that you configured in the "Route Pattern Configuration" page.

You configure the "Calling Party Transform Mask" here in the same way as explained for the "Route Pattern Configuration" page.

------------------------------------------------------

4) "Gateway Configuration" page.

Go to the Gateway and select the PRI that you are using for outgoing calls. Under 'Outbound Calls' you should see the Caller ID DN field. In here you can configure also the Caller ID.

------------------------------------------------------

In other words Caller ID works as follows:

- Gateway configuration overrides everything else.

- Route List configuration overrides the Route Pattern and the Directory Number Configuration.

- Route Pattern overrides only the Directory Number configuration.

New Member

Re: Caller ID on outbound calls issue

2) "Route Pattern Configuration" page.

Locate the route pattern that you are using for doing calls to the PSTN.

Scroll down to the "Calling Party Transformations" section.

- If you check the "Use Calling Party's External Phone Number Mask" checkbox, you will use the number that you configured in the "Directory Number Configuration" page as caller ID.

- If you uncheck that checkbox, then you can configure the "Calling Party Transform Mask". Just enter here a number like, as an example, 978858xxxx (callmanager will fill out the xxxx with phone's 4-digit extension).

I think this fixed it. When I went in there the Box was not checked.

New Member

Re: Caller ID on outbound calls issue

I spoke to soon, just got off the phone with the remote user and tested it. She still rings into my cell phone as 655. I wasnt logged into the system to debug teh gateway but Im assuming it will still show 655 too.

New Member

Re: Caller ID on outbound calls issue

Is the rest of the number correct or does it always show up as the same number (a billing or main number, for example)?

If the extension is showing up correctly and it's just the leading "exchange" digits, I would check the places the poster above mentioned to make that you set up a phone number mask at least in one of those places with "720xxxx" or whatever.

If it's a billing number, maybe you have multiple PRI's and it is just going out the wrong one, or you need to modify the call routing / outbound call parameters on the PRI (calling line ID presentation, calling numbering plan) until it works.

Just a thought.

New Member

Re: Caller ID on outbound calls issue

hi,

could you please run the debug on gateway & can paste the output...

New Member

Re: Caller ID on outbound calls issue

Hope you dont think I am hijacking the posting, but is there a guide to config how Gateway and callmanager communicate with LEC's? In another posting I have this posted:

Currently we have a calling plan that has the XXXXXXX for local calling and

[2-9]XXXXXXXXX for metro and 1[2-9]XXXXXXXXX for LD. Call are completing, but LD carrier says there are getting one number BTN (billing telephone #) for all DID's we are sending out, done as a calling mask per line/phone.

Since LEC said since they aren't recieving a BTN the are masking it on its PIC to LD carrier. Is there a way for me to control the BTN and the ANI (calling mask)?

Any idea's?

New Member

Re: Caller ID on outbound calls issue

I found and fixed my problem.

1) with the number coming up as 665 instead of 720. We have a route pattern setup for all " internal ". This phone fell into that. On the pattern it was setup to 716665XXXX. But we had the box checked that stated " use dn perference. I thought this would use what I had the DN setup for which was 716720.

Now if I removed the 716250 setting it worked fine. But most of the rooms only had the last 4 ext configured on it. So I created a new pattern to include the 716720 stuff and fixed it. The second problem with the name display was from the carrier. They were the ones sending that and got it corrected.

My thing was I thought with " Use Calling Party's External Phone number mask " was checked. It would first check there and see if its set and use it.

I think I answered my own question though from one of the first posts. It states

Gateway / route pattern / DN settings.

even if the box is checked?

173
Views
9
Helpful
7
Replies
CreatePlease login to create content