asterisk users - Jun 2018 - Questions about SIP From, P-Asserted-Id fields and Diversion headers ?

Hi,

After a long discussion with a friend, I would like to ask here:

1.According SIP RFCs, is possible/recommended to have different values
in
>From and P-Asserted-Id fields ?
For instance, From field showing 123456789 and P-Asserted-Id showing
987654321 (beside privacy considerations) ?

2. When Bob forwards to Cory a call coming from Alice, would expect
Diversion/History-Info header to include Alice's number ?

Best regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20180605/6aea01e0/attachment.html>

On Tue, Jun 05, 2018 at 11:34:51AM +0200, Olivier wrote:
> 1.According SIP RFCs, is possible/recommended to have different values in
> From and P-Asserted-Id fields ?
> For instance, From field showing 123456789 and P-Asserted-Id showing
> 987654321 (beside privacy considerations) ?
Yes, most obviuos need for PAI is a call where anonimity is desired by
caller. Set the From to anonymous at anonymous.invalid and PAI to a real
user if the destination is trusted, any proxy that handles this message
that doesn't trust a destination will strip PAI thus ensuring privacy.
 
> 2. When Bob forwards to Cory a call coming from Alice, would expect
> Diversion/History-Info header to include Alice's number ?
No, diversion/history should contain Bob.

On Tue, Jun 5, 2018 at 3:35 AM Olivier <oza.4h07 at gmail.com> wrote:
> Hi,
>
> After a long discussion with a friend, I would like to ask here:
>
> 1.According SIP RFCs, is possible/recommended to have different values in
> From and P-Asserted-Id fields ?
> For instance, From field showing 123456789 and P-Asserted-Id showing
> 987654321 (beside privacy considerations) ?
>
Possible? yes absolutely.  Recommended? who knows?  Implementations are all
over the place.  I've always thought of the From header as identifying the
user agent making the request which kinda agrees with RFC3261.   The PAI
header should contain the identity of the original caller.

>
> 2. When Bob forwards to Cory a call coming from Alice, would expect
> Diversion/History-Info header to include Alice's number ?
>
No.  The diversion header shows who the diverter is.
https://tools.ietf.org/html/rfc5806



>
> Best regards
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> Check out the new Asterisk community forum at:
> https://community.asterisk.org/
>
> New to Asterisk? Start here:
>       https://wiki.asterisk.org/wiki/display/AST/Getting+Started
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users


-- 
George Joseph
Digium, Inc. | Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
Check us out at: www.digium.com & www.asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20180605/be784c63/attachment.html>

2018-06-05 15:27 GMT+02:00 George Joseph <gjoseph at digium.com>:
Thank  you very much, George for replying.
>
>
> On Tue, Jun 5, 2018 at 3:35 AM Olivier <oza.4h07 at gmail.com> wrote:
>
>> Hi,
>>
>> After a long discussion with a friend, I would like to ask here:
>>
>> 1.According SIP RFCs, is possible/recommended to have different values
in
>> From and P-Asserted-Id fields ?
>> For instance, From field showing 123456789 and P-Asserted-Id showing
>> 987654321 (beside privacy considerations) ?
>>
>
> Possible? yes absolutely.
>
How would you then configure both headers, respectively ?
>From memory, in previous testings, whenever  CALLERID was set to WHATEVER,
P-Asserted-Id was also set to WHATEVER and vice versa, so that I inferred
from this that P-Asserted-Id was meant for Privacy considerations and
nothing else (see [1])


[1]
https://www.voip-info.org/p-asserted-identity-and-remote-party-id-header/

> Recommended? who knows?  Implementations are all over the place.  I've
> always thought of the From header as identifying the user agent making the
> request which kinda agrees with RFC3261.   The PAI header should contain
> the identity of the original caller.
>
>
>>
>> 2. When Bob forwards to Cory a call coming from Alice, would expect
>> Diversion/History-Info header to include Alice's number ?
>>
>
> No.  The diversion header shows who the diverter is.
> https://tools.ietf.org/html/rfc5806
>
>
>
>
>>
>> Best regards
>> --
>> _____________________________________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>
>> Check out the new Asterisk community forum at:
>> https://community.asterisk.org/
>>
>> New to Asterisk? Start here:
>>       https://wiki.asterisk.org/wiki/display/AST/Getting+Started
>>
>> asterisk-users mailing list
>> To UNSUBSCRIBE or update options visit:
>>    http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
>
> --
> George Joseph
> Digium, Inc. | Software Developer
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - US
> Check us out at: www.digium.com & www.asterisk.org
>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> Check out the new Asterisk community forum at:
> https://community.asterisk.org/
>
> New to Asterisk? Start here:
>       https://wiki.asterisk.org/wiki/display/AST/Getting+Started
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20180605/ea73d5ee/attachment.html>