Andreas - comments inline.
Paul
Andreas Byström wrote:
Hi!
Question about P-Asserted-Id header.
If subscriber A, B and C "belongs" to domain X, and proxy1 (P1) and
ApplicationServer1 (AS1) are both in the trusted domain of X, what would you
say should be in the P-Asserted-Id header in the following case:
- A calls B, request goes to P1
- P1 authenticates A and send the message to AS1 to trigger B's terminating
services. Since AS1 is in the trusted domain of X, P1 will include A in the
P-Asserted-Id header
- ASr1 is a B2BUA and receives the invite from P1. B has a terminating
service to forward all calls to C. So AS1 now have to place a call to C (B
should be billed for the call to C, A should be billed for the call to B)
- When AS1 sends the invite to C it sends it via P1.
In this INVITE going from AS1 to P1, what do you think should be in the
P-Asserted-Id header.
* A that actually placed the call to B, or
* B that is logically calling C
Lets first consider the case where AS1 is a proxy, and than consider the
B2BUA case later.
With AS1 a proxy, it seems clear that the caller is A. B may play the
role of "payer of the B-C segment of the call", but is not the caller.
So I think the P-Asserted-ID should contain A.
Now consider AS1 as a B2BUA. It certainly has the possibility of
asserting B for the leg it initiates. It is an interesting question
whether it is permitted to pass on the assertion for A. If it is, then
can it also assert anything it pleases?
Practically speaking, it probably wants to *appear* as a proxy, and so
it probably wants to retain the assertion of A, because it probably
wants C to receive and present A as the "callerid". It *might* want to
include History-Info so that C can view the entire history of how the
call reached it - in particular that it came via B.
Paul
Thanks in advance!
Regards,
// Andreas
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
