Outbound caller ID

[Alliance Collections]

We are having troubles with our carrier and outbound caller ID. Our call center maintains calls for 5+ clients. We are working on sending out a number with outbound calls so the caller ID will flag as the client and not as blocked which we use by default. We have already worked with the our provider of the PRI and I am able to make test calls using my phone and seperate CSS. I haven't found any information about how to setup a similar system with our dialer. The dialer is all T1's. We use MGCP to get them to callmanager, what it appears to me is that the outbound number is being lost in the transfer. The dialer vendor has verified in thier logs that the outbound number is being sent properly and should be handed off to callmanager. Version 5.1.1.3000-5 by the way. From there as I mentioned I am getting lost in the steps we have called support for this and one person says to use the route pattern and another says translation pattern. So in summary we are looking for the best way to take the caller id number that is passed from our dialer and make sure that it is only applied to the calls as needed, direct dials and manual dials from inside the building still need to be caller id blocked since one person may call on behalf of multiple clients. I will try to provide any information anyone needs in helping and appreciate any help anyone can give. This has been a long drawn out process for over 3 months now. Thanks again in advance.

[mchin345]

Route pattern is the best way to best way to take the caller id number that is passed from our dialer.

Configuration for calling party transformations settings that are used in route lists occurs in the individual route groups that comprise the list. The calling party transformations settings that are assigned to the route groups in a route list override any calling party transformations settings that are assigned to a route pattern that is associated with that route list.

For further information click this link.

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/5_1_3/ccmsys/a03rp.html#wp1044110

[Alliance Collections]

This gets a little tricky for me we have 2 different route patterns i can find that may match to the calls we are making. there is an area inside call manger that lists the 25xx which is what we use as DNIS for our dialer. 2501 as an example would be client A. There is also a mask for 7.207XXXX which is a local number. This is also copied and listing 2 different partitions. One specifically named dialer. Both patterns use the same Route List. This again is an area i am not too familiar with in callmanager and appreciate the help so far. I will take the document home and read through to see where it gets me. From what i have skimmed over, correct me if i am wrong please, i would want to copy the route list we are currently using and create a new list for the client that allows the passing of the transform mask. Then its just a matter of making sure callmanager passes the information along which i am a little unclear of how esactly to go about.

[jbarcena]

I strongly recommend you to take a CCM detailed trace to see exactly which Route Pattern are you matching. If you do not know how to read traces perhaps you could use the Dialed Number Analyzer that is a plugin that you can download from the CCMAdmin webpage.

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.