|
The B2BUA would look like a proxy from outside.
So
similar rules apply. Its however capable of
carrying out
independent converstaions on either
leg.
The dest IP address of the INVITE is that of
the B2BUA.
The request URI in general would also be the
domain of
the B2BUA, but may not be, in the case where it
is operating
as an outbound proxy. The user parts of the
request uri,
from and to represent the usual infromation
(called, calling,
and ultimate dest)
----- Original Message -----
Sent: Tuesday, May 14, 2002 6:59 AM
Subject: [Sip-implementors] SIP INVITE
via B2BUA
Hello,
I would be grateful if you could help me with understanding
the SIP INVITE message that would be sent to a B2BUA which acts as a third
party call controller. I have read the Internet draft on third party
call control using SIP, but it does not answer my questions.
My questions in particular are:
If the originating party wished to INVITE the called party via
a B2BUA:
Which part(s) of the SIP header specify the address of the B2BUA?
Which parts
of the SIP header or body tell the B2BUA the address of the called party?
When the B2BUA forwards the INVITE:
Which part
of the SIP header contains the address (SIP) of the originating party?
Which part
contains the address (SIP)of the B2BUA
Are there any papers or documents which explain this behaviour
including the contents of header fields in more detail?
Any information you can provide would be most helpful.
Thanks,
Nick Wiltshire
| 