Need help with calling party transformation with SIP trunks

[voip7372]

I've been driving myself crazy trying to get this to work.  Just as soon as I think I have it working, I find another type of call that has incorrect calling party number.

Here's the details on the system, type of trunks and what I want to accomplish...

System = CUCM 10.5.2.  Trunks from PSTN = ISDN PRI connected to Cisco router.  Trunk between Cisco router and CUCM = SIP trunk.  Outside access code/route pattern in CUCM that users dial to reach PSTN numbers = 9.

First of all, I understand (according to the SRND document) that SIP trunks do not support the 'type of number' tag and all calls coming to CUCM via a SIP trunk would basically be tagged as 'unknown' type instead of National, Subscriber, etc like you can get from H323 or ISDN trunks.  

What I'm trying to accomplish seems very simple, but it's turned out to be rather complicated to make it work.  I simply want to make it so that users can call back to a missed call or received call in the call log by pressing the Call button without having to dial the 9 first.  By default, you would naturally only see the calling party number that came from the phone company, like 614-555-1212 for example.  Let's pretend for a moment that I'm using a phone in a device pool that's local to that 714 area code number I mentioned.  I would like to be able to make it so that number is dialed back from the call log as 9-614-555-1212 (a local 10 digit call, not long distance).  

I would also like to have it so any other calls arriving with a 10 digit calling party number from the phone company that is NOT area code 614 to dial back from the call log with 9-1-714-555-1212 for example (a long distance call since 714 is not in the local area where this phone happens to be).  

And of course, I want to make sure that direct dialed calls from the internal phones (dialing manually, not pressing 'Call' from the Recents/Call log) have the correct calling party number for the user making the call from our office.  

I'm just not sure of the exact combination of settings on the Device Pool, Phone, etc to make this happen.  I have the calling party number from our phones on CUCM working correctly when calling party transformation is not configured, but of course then the users don't have the convenience of pressing 'Call' from the Recents call log to dial back to a missed call without dialing 9 first.  

If you can explain the proper configuration for this type of setup, I'd greatly appreciate it!  I have a cut-over coming up next week and if I can get this function working before the cut-over, that would be great.   If I can't get it to work properly, I'll have to abandon that function for the time being.

[Dennis Mink]

I would apply this on the gateway itself as much as possible not on cucm.  This will allow SRST to have the same behaviour in case you use this.

so, put translation patterns on your gateway and apply them to the inbound dial peer.

for instance 

voice translation-rule 2
 rule 1 /\(.*\)/ /9\1/

voice translation-profile CLID
 translate calling 2

to add 9 to any incoming calling number

[voip7372]

I've been testing your idea combined with what I saw in this discussion:  https://supportforums.cisco.com/discussion/12470321/prefix-9-missedrecieved-calls-custom-requirement-cucm-105

After looking at that discussion, I realized they were talking about using a CSS/PT on the trunk incoming to CUCM to prefix something and then use another CSS/PT to mask the number you don't want to see on caller id (9 for example).  

So, I added a translation rule and inserted 91 for call calls leaving the gateway going to CUCM.  Once at CUCM, I see the 91 plus the rest of the number and I can use the calling party transformation pattern in a new CSS/PT on the incoming calling party settings section to strip 91 and insert just 9 if I know that area code calling me is local and we don't need to dial back to it with 91, but just 9.  Then I added another new calling party transform pattern in a different css/pt to mask the 9 so all i see is the local 10 digit number for the calling party ID.  

It all seems to work fine (I see what I expect and the call log shows the 9 to call back), with one exception (which may be the death of this idea).  When the call forwards to voice mail (Microsoft Unified Messaging), it still has the 9 for the calling party id and that breaks some functionality in voice mail that would normally see a calling party number and associate it with one of your contacts in Outlook or a known user in Exchange.  I know people would complain about this if it wasn't working, so if I can't get the voice mail part to work right, I won't be able to do this.  For example, don't present 9-714-555-1212 as the calling party number to voice mail, but just present 714-555-1212 as the person who called.

[Mohammed al Baqari]

Hi,

How are you integrating with the unified messaging. I am assuming it is SIP integration.

[voip7372]

Yes, SIP trunk.   I just realized I have MS UM (voice mail) in its own device pool.  When I applied the xform CSS I was using to mask the 9 from the caller-id, it does show up correctly now in MS UM also.   

My only concern at this point is, if I used this scenario, I'd have to apply that xform CSS I'm using to mask the 9 to every device pool or device that could possibly receive a call that started out with the 9 in front as the caller-id.  If I don't, the 9 appears in the calling party number on the display.   I'm a little worried about the implications of that down the road as we get more and more sites using CUCM.