Calling party transformation issue for Call Forwarding

[nicolas.coursant]

Hello,

I have an issue to use Calling party transformation rules for call forwarding.

I work on CUCM 8.6.2.20000-2 and I have a SIP trunk configured like this:
- Outbound - Called Party Transformation CSS: "CSS_CUBE_Outbound_Called"
- Outbound - Use Device Pool Called Party Transformation CSS : unchecked
- Outbound - Called Party Transformation CSS: "CSS_CUBE_Outbound_Calling"
- Outbound - Use Device Pool Calling Party Transformation CSS : unchecked
- Outbound - Redirecting Party Transformation CSS: "CSS_CUBE_Outbound_Calling"
- Outbound - Use Device Pool Redirecting Party Transformation CSS : unchecked
I don't put any calling/called party transformation parameters inside route pattern (because this will not be applied when I use transformation CSS on my SIP trunk)

My PSTN provider control that outbound call are made with authorized DID. Then I configure the SIP trunk like this:
- Outbound - Redirecting Diversion Header Delivery : unchecked
- Outbound - Calling Party Selection : Last Redirect Number

I use an internal dial plan in 8XXXXXXXXX and I translate these number in +E164 thanks to Transformation CSS "CSS_CUBE_Outbound_Calling" on SIP trunk. Everything works fine for standard call, calling-party is transformed to +E164.

My issue comes for call forwarding: The CUCM send the outbound call with the calling party in 8XXXXXXXXX instead of +E164.
So, CUCM apply the setting "Last Redirect Number" but then, don't apply the transformation CSS.

Is it a bug ? Is it a feature ? Or do I miss configured something ?

Thanks in advance for your help
Nicolas

[Carlo Poggiarelli · Accepted solution]

Hi Nicolas.

Please flag Redirecting Diversion Header Delivery - Outbound option.

Uncheck Use Device Pool Redirecting Party Transformation CSS

Use  CSS_CUBE_Outbound_Calling  as Redirecting Party Transformation CSS.

This should behave as you espect.

HTH

Regards

Carlo

[Ayodeji Okanlawon · Accepted solution]

Nicola,

My experience with diversion header is that you need to use some form of sip profiles to authenticate with your provider..There may be another way but the only way I have got it work is using sip profiles

voice class sip-profiles 1

request INVITE sip-header Diversion modify "<.>" ""

where XXXXX is a valid DDI number you want to authenticate with and 10.10.10.10 is the ip address of your gateway/CUBE

You then need to apply the sip profile to the outbound dial-peer facing your ITSP

dial-peer voice xx voip

voice-class sip profiles 1

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[nicolas.coursant]

Hi Carlo and aokanlawon,

I solved my issue by merging your solution.

Here is the change I made:
- Outbound - Calling Party Selection : Last Redirect Number
- Outbound - Redirecting Diversion Header Delivery : checked
- Outbound - Redirecting Party Transformation CSS: "CSS_CUBE_Outbound_Calling"
- Outbound - Use Device Pool Redirecting Party Transformation CSS : unchecked

-> After this change the calling party is correctly normalized, but the diversion header is now sent to my CUBE.
Because I don't want to send the diversion header to the provider (this cause some issue), I made these change on my CUBE:

voice class sip-profiles 1
request INVITE sip-header Diversion remove

dial-peer voice 101 voip
...
destination-pattern +T
voice-class sip profiles 1
...

Thanks for your help.
Nicolas