Caller ID

[DataSource7]

So besides at the line level and router pattern is there anywhere else CUCM controls the caller ID number being sent?  When I run a debug on the gateway I see the DN being sent as the calling party but the number shows up externally as the billing number.  I think Telco is masking the calls but they claim they are not.

All help is appreciated!

[Roger Kallberg]

If you see that you're passing the calling number as per the requirement of your Telco, but you still see something else, like the billing number it is most definitely being masked by your Telco.

Telcos are known for being clueless on this, and many other things IMHO. I would recommend you to capture the data of what your sending to them and share that with the engineer that your in contact with to have him/her verify that your sending the expected information, down to number format, number type and isdn plan. If you do and there is still other things seen as the calling number it’s on the service provider side and they need to work the problem.

[Nithin Eluvathingal]

Almost all telco will translate the calling information to your Pilot number or They drop the call if you send calling information other than your DID range.

If its an internal extension range which you are sending to Isp as calling number they will translate this to you pilot. use translation or make user of external phone number mask to make suer you send the right info to your ISP as they expect.

2.12.0.0

[Dmytro Benda]

Besides External Phone Number Mask and Route Pattern CUCM can modify Calling or Called numbers at Route List\Route Group level and also at Gateway\Trunk level (with Transformation CSS and Transformation Patterns). If you use an H323\SIP gateway, then voice translation rules and profiles can be used in the gateway itself (in the voice port or in the outbound dial-peer). 

My Cisco Unified Communications Blog

[Maren Mahoney]

The Directory Number (calling party) and the number dialed (called party) on the device are "original information".

If a Route Pattern is the target of the dialed number, then the route pattern will perform its calling- and called-party transformations and send the call to the next call routing step, the Route List/Route Group. Note that both the "original information" and the transformed information is send to this next step.

If, when the Route Group is added to the Route List, there is digit manipulation configured then the Route Group will discard whatever the Route Pattern has done for that component (calling- and/or called-party) and perform its digit manipulation on the "original information" for that component. Then the Route Group sends the call to the next call routing step which would be a trunk or gateway. Note, again, that the Route Group sends both the "original information" and any transformed information to the trunk or gateway.

If the trunk or gateway has digit manipulation configured in the form of outbound calling- or called-party transformations (assigned via a calling party CSS and/or called party CSS) then the trunk or gateway will discard any manipulation from earlier steps and perform its transformations on the "original information". This is the final digit-manipulation step in CUCM prior to signaling out to the Trunk or Gateway. (In some rare cases, for calling party the trunk and gateway configuration pages have a pair of fields where all outbound calls are assigned a specific calling party name and number which overrides anything else.)

The common exception to the above digit manipulation process is Translation Patterns. If the "original information" (original DN and original dialed number) targets a Translation Pattern first before matching a Route Pattern, then the Translation Pattern will do its digit manipulation and the output of the Translation Pattern is now the "original information" (replacing the original DN and original dialed number as "original"). Call processing and digit manipulation continues as above with this new "original information". (This is why with Globalized Call Routing the first call routing step is usually Translation Patterns so that numbers are Globalized (into E.164 format) and can then be 'sent' anywhere.)

Lastly, the gateway/CUBE itself can set calling party information in the form of Voice Translation Profiles or CLID commands on dial-peers.

Hopefully this helps clarify digit manipulation in CUCM for outbound calls. Let me/us know if you have questions.

Maren