09-06-2013
06:08 AM
- last edited on
03-25-2019
08:25 PM
by
ciscomoderator
Hello,
I need to configure CUBE (sip-to-sip gw) passing through FROM header values from incoming to outgoing INVITE, when CLIR is applied from UAC by display name = Anonymous.
.
Current situation:
incoming INVITE headers:
INVITE sip:42190711111@195.X.X.X:5060;transport=udp SIP/2.0
From: "Anonymous" <sip:421233322222@sip.domain.com>;tag=7D55465C-5229CC240005D353-4FDFD700
Privacy: id
P-Asserted-Identity: <sip:0233322222@sip.domain.com>
outgoing INVITE headers:
INVITE sip:0907111111@195.X.Y.Y:5060 SIP/2.0
From: "anonymous" <sip:anonymous@195.X.X.X>;tag=BCCCF08-1AE8
Contact: <sip:anonymous@195.X.X.X:5060>
Desireable situation:
outgoing INVITE headers:
INVITE sip:090711111@195.X.Y.Y:5060 SIP/2.0
From: "Anonymous" <sip:0233322222@195.X.X.X>;tag=BCCCF08-1AE8
Contact: <sip:0233322222@195.X.X.X:5060>
Can you please point me to the right direction?
Thanks a lot.
Mike
09-06-2013 06:52 AM
You can use sip profiles for that.
09-06-2013 08:57 AM
HI,
Yes, it would be possible to change that with SIP profiles but the incoming INVITE contains:
Privacy: id
That means according to RFC 3325:
"The presence of this privacy type in a Privacy header field indicates that the user would like the Network Asserted Identity to be kept private with respect to SIP entities outside the Trust Domain with which the user authenticated."
So you're not honouring the user's request by revealing his/her identity ...
Kind regards,
Jan
09-06-2013 11:15 AM
jbollen wrote:
So you're not honouring the user's request by revealing his/her identity ...
How do you know that, for example that is not OP own call, or that he is not authorized by usesr or by the company he works for? This is a technical forum, the question is valid, please leave judgments aside.
09-09-2013 01:05 AM
Thanks. But lets say that both (incoming/outgoing) domains are trusted for me.
I need to achieve Privacy: Id (and From: Anonymous <) and also callilng party number.
Calling Party Number will be removed on another device in topology.
For you imagination - this is call-flow:
Caller--->CUBE--->PSTN-GW--->TDM-SWITCH--->Calle
Caller calls Calle. The identity of Caller is removed by CUBE (current behavior).
Problem is that my billing system is based on CDRs generated by TDM-SWITCH.
As you see, I need to force my setup to the behavior, in which will PSTN-GW know Caller identity, send it to TDM-SWITCH, which will hide identity of caller, but TDM-SWITCH will insert CallerPartyNumber into the CDR for billing purposes.
Lets say that CUBE, PSTN-GW and TDM-SWITCH are under my control, so this components are trusted for me.
09-09-2013 03:00 AM
Hi.
You can use calling-info sip-to-pstn name set 123456 and calling-info sip-to-pstn number set 123456
to have an invite similar to the following
INVITE sip:800100100@sip.isp.com:5060 SIP/2.0
Via: SIP/2.0/UDP 10.100.101.2:5060;branch=z9hG4bK431E71AAB
Remote-Party-ID: "123456" <1100>;party=calling;screen=yes;privacy=off1100>
From: "123456" <123456>;tag=9E93DC2C-C0123456>
To: <>>800100100@sip.isp.com,>
In this case the only number and name that would be showed is 12345
HTH
Regards
Carlo
Please rate all helpful posts
"The more you help the more you learn"
09-09-2013 05:16 AM
Carlo: Is this working in sip-to-sip scenario too?
Anyway.. I don't think this will be solution for me.
I have plenty of Callers with different numbers and I need to pass these numbers (set by callers) through CUBE to PSTN-GW (see schema above).
Understand that my CUBE is something like sip-to-sip gateway/interface between two ITSP, not between COMPANY and ITSP.
Rewriting all calls with CLIR by the same CalledPartyNumber is not solution :-(
09-09-2013 06:21 AM
Again as above: sip-profile is to be used.
09-09-2013 10:31 AM
Ok. I give up :-(
I've read a lot of examples and documents regarding sip-profiles and tried to force sip-profile to modify From header by replacing Anynonymous string for something else - simple:
input: From: "Anonymous"
output: From: "999999"
----------------cut---------------
!
voice service voip
sip
sip-profiles 100
!
!
voice class sip-profiles 100
request ANY sip-header From modify "Anonymous" "999999"
!
----------------cut---------------
But it doesn't work :-(.
I still have output From: "Anonymous"
What am i missing?
09-09-2013 11:02 AM
To begin with, that should be
request INVITE
Then I would apply the sip-profile on the necessary dial-peer only, not globally.
09-09-2013 11:22 AM
!
voice class sip-profiles 100
request INVITE sip-header From modify "Anonymous" "999999"
!
No change...
Output:
From: "anonymous"
Btw debug ccsip all shows that sip-profile is matched:
//-1/224338828701/SIP/Info/ccsipUpdateIncomingCallParams: ccCallInfo: Calling name Anonymous, number 421233322222, Calling oct3 0x00, oct_3a 0xA0, Called number 42190711111
//-1/xxxxxxxxxxxx/SIP/Info/sipSPIGetCallConfig: voice class SIP Profiles tag is set : 100
09-09-2013 12:06 PM
You should write "anonymous" all lower case.
09-09-2013 10:41 AM
Did you tryed what i suggested?
Carlo
Sent from Cisco Technical Support iPhone App
09-09-2013 11:07 AM
Yes Carlo. I tried to modify sip-to-pstn calling-info name and number and it works.
I modified calling number of sip-ua, this number was set (by CUBE) on output.
config:
ip2ip-gw1(config-sip-ua)# calling-info sip-to-pstn name set 99999999
ip2ip-gw1(config-sip-ua)# calling-info sip-to-pstn number set 88888888
output:
From: "99999999" <0088888888>0088888888>
config:
ip2ip-gw1(config-sip-ua)# calling-info sip-to-pstn number set 88888888
ip2ip-gw1(config-sip-ua)# no calling-info sip-to-pstn name set
output:
From: "Anonymous" <0088888888>0088888888>
That seems to be so close to my needs :-)
With this command, I'm able to set the same CallingNumber to all my users with CLIR, but as i wrote before...
This is not solution for me, because my billing is not correct.
I have many users and they are billed separately (see my Reply to Your first answer).
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide