[cisco-voip] What's the best way to emulate "clid restrict" on a SIP trunk?

[Ryan Ratliff]

Does this help?
http://www.cisco.com/en/US/docs/ios/voice/cube/configuration/guide/vb_9397_ps5640_TSD_Products_Configuration_Guide_Chapter.html


-Ryan

On Apr 30, 2013, at 11:43 AM, Robert Kulagowski <rkulagow at gmail.com> wrote:

On Fri, Apr 26, 2013 at 2:50 PM, Robert Kulagowski <rkulagow at gmail.com> wrote:
> On Fri, Apr 26, 2013 at 11:26 AM, Andreas Sikkema <asikkema at unet.nl> wrote:
>> Hi,
>> 
>>> Is there some combination of privacy settings that I can enable on a
>>> dial peer so that
>>> 1- the calling number and name is sent to the provider, so that they
>>> can associate a calling and called number (and the cost of that call)
>>> 2- the upstream SIP provider _doesn't_ forward that information
>>> towards the called party? For some calls it's important that they get
>>> to the destination as "Unknown"
>> 
>> This depends on which relevant SIP headers your upstream provider
>> supports for CLID presentation.
>> 
>> Some use the Remote-Party-ID header, others can handle
>> P-Preferred_Identity and/or P-Asserted-Identity headers with the
>> associated Privacy header that does the real restricting bit.
> 
> "... bandwidth.com uses the FROM field to represent the Caller ID Name
> and Number & call rating. If a Remote-Party ID field (RPID) is
> included in the SIP INVITE message, the RPID will be used for caller
> ID and for call rating. The from field and the RPID must be in a
> 10-digit format."
> 
> OK, so in CUCM I set the Calling Line ID and Name Presentation to "Restricted".
> 
> In CUBE, I configured "privacy id" under voice service voip along with
> "privacy-policy passthru"
> 
> The call leg from CUCM is:
> 
> INVITE sip:1630xxxxxxx at 204.xxx.xxx.xxx:5060 SIP/2.0
> Date: Fri, 26 Apr 2013 19:33:42 GMT
> Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER,
> SUBSCRIBE, NOTIFY
> From: "Anonymous"
> <sip:anonymous at anonymous.invalid>;tag=d465acaa-c4d5-4a79-b7e9-2f1a79e6b2a6-39519923
> Allow-Events: presence
> P-Asserted-Identity: "Robert Kulagowski" <sip:223928 at 10.255.29.20>
> Supported: timer,resource-priority,replaces
> Supported: X-cisco-srtp-fallback
> Supported: Geolocation
> Min-SE:  1800
> Remote-Party-ID: "Robert Kulagowski"
> <sip:223928 at 10.255.29.20>;party=calling;screen=yes;privacy=full
> Content-Length: 0
> User-Agent: Cisco-CUCM7.1
> Privacy: id
> To: <sip:81630xxxxxxx at 204.xxx.xxx.xxx>
> Contact: <sip:223928 at 10.255.29.20:5060>
> Expires: 180
> Call-ID: 32807480-17a1d696-5-141dff0a at 10.255.29.20
> Via: SIP/2.0/UDP 10.255.29.20:5060;branch=z9hG4bK765b52845
> CSeq: 101 INVITE
> Session-Expires:  1800
> Max-Forwards: 70
> 
> And what was sent to the provider:
> 
> INVITE sip:+1630xxxxxxx at ot.bandwidth.com:5060 SIP/2.0
> Via: SIP/2.0/UDP 204.xx.xxx.xxx:5060;branch=z9hG4bK914FF
> From: "anonymous" <sip:anonymous at 204.xx.xxx.xxx>;tag=67C96C50-1048
> To: <sip:+1630xxxxxxx at ot.bandwidth.com>
> Date: Fri, 26 Apr 2013 19:33:42 GMT
> Call-ID: 9AB9FF1-ADDF11E2-86BFDAE7-AA8C8F4C at 204.xx.xxx.xxx
> Supported: 100rel,timer,resource-priority,replaces,sdp-anat
> Min-SE:  1800
> Cisco-Guid: 0162082489-2917077474-2260327143-2861338444
> User-Agent: Cisco-SIPGateway/IOS-12.x
> Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER,
> SUBSCRIBE, NOTIFY, INFO, REGISTER
> CSeq: 101 INVITE
> Timestamp: 1367004822
> Contact: <sip:anonymous at 204.xx.xxx.xxx:5060>
> Expires: 180
> Allow-Events: telephone-event
> Max-Forwards: 69
> Session-Expires:  1800
> Content-Type: application/sdp
> Content-Disposition: session;handling=required
> Content-Length: 253
> 
> Is there some combination of settings that will allow me to send the
> "223928" part to the provider so that it shows up in their billing
> system, but not send _anything_ to the person being called? I don't
> want the called party to see "223928" on their phone, because that's
> weird.

Any ideas on this? Is this even possible? I've been reading through
the CVOICE material and I may be missing something, or just not
understanding everything fully.
_______________________________________________
cisco-voip mailing list
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/20130430/12f30727/attachment.html>