[cisco-voip] Modify calling number in SIP invite on CUCM 11

Fri Jul 1 17:05:33 EDT 2016

Do you have use external phone number mask on the route group inside the route list?

If I remember correctly, the call to the SIP recorder is just another call, with the specific CSS, so you should be able to use DNA to see what step is changing the calling part number.

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Deepak Maggo
Sent: Friday, July 01, 2016 1:24 PM
To: Brian Meade <bmeade90 at vt.edu>
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Modify calling number in SIP invite on CUCM 11

In earlier versions of CUCM we used to get extension number as SIP address for external calls, but after upgrading the CUCM to v11.0 we are getting external phone number mask.

If anyone can help me with SIP normalisation script where I can replace the external phone number mask with extension number in SIP INVITE, which I can apply on SIP trunk to my call recorder coz I want external phone number mask to be displayed on PSTN calls.

Appreciate all help in this.

Thanks & Regards,
Deepak Maggo

On 1 Jul 2016 14:47, "Brian Meade" <bmeade90 at vt.edu <mailto:bmeade90 at vt.edu> > wrote:

It's got the extension in there too in a few fields.  I think it does the Invite this way so the recorder can match up the call from the CTI messages.

On Fri, Jul 1, 2016 at 2:30 PM, Deepak Maggo <dmaggo at ipcelerate.com <mailto:dmaggo at ipcelerate.com> > wrote:

Here is the SIP Invite from extension number "1102" with External Phone Number Mask "8889184192 <tel:8889184192> ", when I dial the internal extension I do receive the extension number in SIP invite:

Jul 01 07:30:24.631 [INFO] JSIPListerner: processRequest() requestType (INVITE) = INVITE

Jul 01 07:30:24.631 [INFO] JSIPListerner: processSIPInvite() callIDHeader = f89b3e00-77619055-42-6e08210a at 10.33.8.110 <mailto:f89b3e00-77619055-42-6e08210a at 10.33.8.110> 

Jul 01 07:30:24.631 [INFO] JSIPListerner: processSIPInvite() sipFromHeader = "1102" <sip:8889184192 at 10.33.8.110 <mailto:sip%3A8889184192 at 10.33.8.110> ;x-nearend;x-refci=29335531;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP1CE85DC824AC;x-nearendaddr=1102;x-farendrefci=29335532;x-farendclusterid=StandAloneCluster;x-farenddevice=10.31.8.1;x-farendaddr=917325797456>

Jul 01 07:30:24.631 [INFO] JSIPListerner: checkHalfCall() sipFromHeader = "1102" <sip:8889184192 at 10.33.8.110 <mailto:sip%3A8889184192 at 10.33.8.110> ;x-nearend;x-refci=29335531;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP1CE85DC824AC;x-nearendaddr=1102;x-farendrefci=29335532;x-farendclusterid=StandAloneCluster;x-farenddevice=10.31.8.1;x-farendaddr=917325797456>

Jul 01 07:30:24.631 [INFO] JSIPListerner: processSIPInvite() First sipFromHeader = "1102" <sip:8889184192 at 10.33.8.110 <mailto:sip%3A8889184192 at 10.33.8.110> ;x-nearend;x-refci=29335531;x-nearendclusterid=StandAloneCluster;x-nearenddevice=SEP1CE85DC824AC;x-nearendaddr=1102;x-farendrefci=29335532;x-farendclusterid=StandAloneCluster;x-farenddevice=10.31.8.1;x-farendaddr=917325797456>

Thanks & Regards,

Deepak Maggo

On Fri, Jul 1, 2016 at 2:16 PM, Brian Meade <bmeade90 at vt.edu <mailto:bmeade90 at vt.edu> > wrote:

What does the Invite actually look like?  I wouldn't expect this setup to show the external number mask to the recorder.

On Fri, Jul 1, 2016 at 1:33 PM, Deepak Maggo <dmaggo at ipcelerate.com <mailto:dmaggo at ipcelerate.com> > wrote:

No, I am not using any CSS Transformations.

Thanks & Regards,
Deepak Maggo

On 1 Jul 2016 13:29, "Brian Meade" <bmeade90 at vt.edu <mailto:bmeade90 at vt.edu> > wrote:

Do you have a calling party transform CSS on the SIP trunk?

On Fri, Jul 1, 2016 at 11:09 AM, Deepak Maggo <dmaggo at ipcelerate.com <mailto:dmaggo at ipcelerate.com> > wrote:

Hi Florian,

I verified my trunk as well and it is also selected as "OnNet":

Thanks & Regards,

Deepak Maggo

On Fri, Jul 1, 2016 at 10:56 AM, Deepak Maggo <dmaggo at ipcelerate.com <mailto:dmaggo at ipcelerate.com> > wrote:

Florian,

Thanks for the response. My route pattern is set to OnNet only:

Thanks & Regards,

Deepak Maggo

On Fri, Jul 1, 2016 at 10:50 AM, Florian Kroessbacher <florian.kroessbacher at gmail.com <mailto:florian.kroessbacher at gmail.com> > wrote:

Maybe your trunk to the Recorder is set to Offnet, try to set it Onnet

Am 1. Juli 2016, 15:47 +0200 schrieb Deepak Maggo <dmaggo at ipcelerate.com <mailto:dmaggo at ipcelerate.com> >:

Hi, 

The problem I have is that we have active recording system which communicates with the CUCM cluster using a SIP trunk and uses Built-in-bridge configuration.

The invites that CUCM sends via the SIP trunk show the "External Phone Number Mask" rather than the four digit extension when make PSTN calls which will not work according to  the recording system. We need the External Phone Number Mask on phones to display the correct Caller ID.

Can anyone suggest a way to fix this?

Ideally I need a way to modify the number in the SIP invite but I cannot find any example of how to do this.

Any suggestions are welcome.

Thanks

Thanks & Regards,

Deepak Maggo

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net> 
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net <mailto:cisco-voip at puck.nether.net> 
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160701/e9ae5970/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 83594 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160701/e9ae5970/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 81425 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160701/e9ae5970/attachment-0001.png>