Calling / Connected Number Manipulation Cisco Jabber

[franknienhaus1]

Hi,

we used a virtual CUBE for the SIP Connection to our provider. The provider need the call in a format like this: 0049XXXX but we are using an E.164 Dial Plan on the CUCM - +49XXXX.

The call works fine and inbound call are presenting right – the complete E.164 number.

The “problem” of the outbound calls is that the CUCM transform all Calls (Local, National, International) to the E.164 Format and send this to the CUBE.

At this moment the Jabber show +49XX. The Dial-Peer on the cube for the external connection transform the number to the format 0049 and the Jabber displaying this updated number, now. We want to see the updated number but in the correct format.

Is it possible, to manipulate the outgoing connected number for outbound calls?

Call Flow:

Cisco Jabber (+49XX) --> CUBE --> Dial-Peer-to-Provider (transform to 0049) --> Provider

I have tested the following options:

• Called / Calling / Connected Party Transformation on the Trunk
• Calling Party Transformation CSS on a phone
• Route Pattern to CUBE

Thanks for help,

Frank Nienhaus

[Daniele Giordano]

Try this on cube:

conf t

voice translation-rule 10

 rule 1 /^+49/ /0049/ 

voice translation-profile XLATE_OUTGOING_CLI

 translate calling 10

dial-peer voice XXX voip  (must be your outgoing dial-peer to your provider)

 translation-profile outgoing XLATE_OUTGOING_CLI

Let me know the result.

If necessary add the output of debug ccsip messages.

Regards.

[franknienhaus1]

Hi,

thanks for the response. This is my translation rule:

rule 1 /^\+49/ /0049/

I attached the configuration and the log file.

+49 2542 8772 210 calls +49 157 11111111 (I change my mobile number)

I will recheck the cube translation pattern, if I find a solution I will post it.

Thanks,

Frank

[Daniele Giordano]

Yes, for + you must use escape code \+ in translation rule.

Sorry for my mistake.

In your trace I see the right format number:

invite received from cube:

INVITE sip:+4915711111111@10.4.0.30:5060 SIP/2.0
Via: SIP/2.0/TCP 10.4.0.11:5060;branch=z9hG4bK2fd3ae61039fcc
From: <sip:+4925428772210@10.4.0.11>;tag=14387304~ad5a55d4-56b2-4c86-b01f-c4d117c9a460-26425693
To: <sip:+4915711111111@10.4.0.30>

inviste sent from cube:

INVITE sip:004915711111111@versatel.sip:5060 SIP/2.0
Via: SIP/2.0/UDP 10.4.200.5:5060;branch=z9hG4bK1C5E46E
Remote-Party-ID: <sip:004925428772210@10.4.200.5>;party=calling;screen=yes;privacy=off
From: <sip:004925428772210@versatel.sip>;tag=281CB916-7A
To: <sip:004915711111111@versatel.sip>

What is the issue now?

Regards.

[franknienhaus1]

Sorry for my explanation...

The call works fine, my problem is the number presentation in the Jabber Client. I attached two Screenshots of a Jabber Call.

The number presentation is confused when the call is connected because our users can’t dial 0049 to reach someone outside. In Germany you must call 0 00 49 (Outside 0) + (0049 Company Code). The call history display the +49 number correct.

I want to manipulate the connected number that is shown in the Jabber Client to the shortest version or to the full E.164 Format.

Thanks a lot!

[franknienhaus1]

If someone has the same issue - I solved it by adding the following lines to the SIP-Profile for the incoming dial peer from the CUCM to the CUBE for Outgoing Calls.

 response 200 sip-header Remote-Party-ID modify "<sip:00(.*)@10.4.0.30>" "<sip:+\1@10.4.0.30>"
 response 180 sip-header Remote-Party-ID modify "<sip:00(.*)@10.4.0.30>" "<sip:+\1@10.4.0.30>"
 response 183 sip-header Remote-Party-ID modify "<sip:00(.*)@10.4.0.30>" "<sip:+\1@10.4.0.30>"

Now all the time the complete E.164 Number is shown.

Thanks for help...