[SIPForum-discussion] SIP privacy header and how to break-out to PSTN

[Yolanda Ruiz]

Hello Dilip,

Thanks for your answer about question 2.

So it´s better to remove the Remote-Party-ID and change it for the P-asserted-Id, inside the domain SP+VPNclient, and breaking out to PSTN with privacy=off, it should be forwarded with the From URI user number, but if I get a privacy=on, instead of stripping it out completely, so no-CLI sent to PSTN, I should "create" a dummy #A to be sent to the PSTN.
How about question 1 and unavailable+ restricted?
From: "Unavailable" <sip:Restricted at 1.1.1.1:5060;cpc=ordinary>;tag=gK0672bb18
                    Contact: <sip:Restricted at 1.1.1.1:5060<http://sip:Restricted@1.1.1.1:5060>>

Thanks in advance
Yolanda
________________________________
De: Dilip Kumar [dondilip at gmail.com]
Enviado el: lunes, 10 de agosto de 2009 15:07
Para: Yolanda Ruiz
CC: discussion at sipforum.org
Asunto: Re: [SIPForum-discussion] SIP privacy header and how to break-out to PSTN

Hi Yolanda,

It depends upon whether you can deliver the blank CLI to the Far end PSTN operator..On the VOIP switch you can override these parameters..Instead of Remote-Party-id, Use P-Asserted-Identity which is more flexible..This has to be a configuration from the client side.

privacy=on which will restrict the CLI delivery at far end..In your voip switch you should be able to override these parameters and put a put Carrier Code with dummy CLI and set to the far end pstn operator.

With Regards,
D. Dilip Kumar

On Thu, Aug 6, 2009 at 11:19 PM, Yolanda Ruiz <yolanda.ruiz at telefonica.com<mailto:yolanda.ruiz at telefonica.com>> wrote:
Hello,

I have read the document "SIPConnect v.14" and I have some doubts about these messages I got from my interconnection partner.
The background is:
There is a client/IPPBXs enviroment connected to one Service Provider and sending this traffic to a transit network through a SIP interconnection, this last carrier should break-out to PSTN.

I would like to know your recommendation about how to map in an appropiate and standard way all the different headers received:

1  - From: Unavailable and restricted? - I didn´t see this option in the "SIPConnect v.14".
Is it a valid one?

1.1- Should the PBX from the client should send this message? should it change something?
1. 2 - Should a transit network received this type of message?
1 .3 - How should be it translated to the PSTN? ( no CLI?)
                    To: <sip:7114759392506087 at 2.2.2.1:5060<http://sip:7114759392506087@2.2.2.1:5060>>
                    From: "Unavailable" <sip:Restricted at 1.1.1.1:5060;cpc=ordinary>;tag=gK0672bb18
                    Contact: <sip:Restricted at 1.1.1.1:5060<http://sip:Restricted@1.1.1.1:5060>>



2 - The break-out to PSTN, receiving this header: From, To, Contact with righ SIP URIs + Remote-party-id

                    Remote-Party-ID: <sip:+4444444 at 5.5.5.5:5060<http://sip:+4444444@5.5.5.5:5060>>; privacy=off



2.1- Should the SP when receiving this header, strip it off before sending it to the next IP carrier?

2.2- How should be it translated to the PSTN? In case, privacy=on -> No CLI should be sent to the PSTN?





And I apologize for the long mail..!!



Yolanda




_______________________________________________
This is the SIP Forum discussion mailing list
TO UNSUBSCRIBE, or edit your delivery options, please visit http://sipforum.org/mailman/listinfo/discussion
Post to the list at discussion at sipforum.org<mailto:discussion at sipforum.org>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20090810/5325509b/attachment-0002.html>