CUCM Called Party Transformation

[Stoyan Stoitsev]

Hello,

I am using some called party transformation patterns on CUCM 8.6 to some destionations. However I need not to show the prefix on the calling line's display. I noticed that this works for CUCM-SIPtrunk-CUBE-SIPtrunk calls but it doesn't for CUCM-SIPtrunk-CUBE-ISDN calls.

Some examples:

CUCM-SIPtrunk-CUBE-SIPtrunk

1. Calling line dials 002123#
2. Transformation changes it to 100#002123# and this does NOT show on the display
3. When connected the called number chages to the connected number (after translations on the CUBE) which is 02123. So the internal caller sees 02123 on his display.

CUCM-SIPtrunk-CUBE-ISDN

1. Calling line dials 002123#
2. Transformation changes it to 100#002123# and this does show on the display
3. When connected the called number stays the same and does not reflect the translations on the CUBE.

What I want to know is if I can get the called number behaviour on the ISDN scenario behaving like in the SIP-SIP scenario.

Stoyan

[William Hennenlotter · Accepted solution]

Date Created: 27-MAR-2012 12:35 PM Created By: Hennenlotter, William L(WHENNENL,36926) Made the following changes to his IOS SIP gateway:

~~~~~~~~~~~~~~~

conf t

voice service voip

sip 

update-callerid

~~~~~~~~~~~~~~~

Conf t

Voice class sip-profiles 1

request UPDATE sip-header Remote-Party-ID modify "Remote-Party-ID: 

response 200 sip-header Remote-Party-ID modify

"Remote-Party-ID: 

~~~~~~~~~~~~~~~

Conf t

  dial-peer voice XXX voip

     voice-class sip profile 1

~~~~~~~~~~~~~~~

The update-callerid affected called party display before ringback.

The update affected called party display during ringback.

The 200 ok affected called party display after connected.

~~~~~~~~~~~~~~~