2008/10/31 Juha Heinanen <[EMAIL PROTECTED]>:
> Elwell, John writes:
>
> > > I support draft-kuthan-sip-derive-00, and hope the WG can devote
> > > time and energy to improving and standardizing it to work well
> > > across a variety of networks.
> > [JRE] I agree. This must include networks that contain B2BUAs/SBCs.
>
> i strongly disagree. b2bua is just an ua. if you you build or deploy
> such boxes, it is your headache, not sip wg's. it is enough that this
> work is based on rfc3261 components.
I agree. If a B2BUA is capable of sending requests with a specific
From it's becomes in fact an UA responsible for that AoR in the From,
so it should be capable of handle incoming SUBSCRIBE for that AoR.
The most problematic case could be the following, in which the
outbound proxy Proxy responsible for domain.org forwards the request
to a B2BUA but at the same time this proxy is the resolution (RFC3263)
for domain.org, so acts also as inbound proxy. In this case
[EMAIL PROTECTED] will know nothing about the dialog data received in the
SUBSCRIBE.
[EMAIL PROTECTED] ---- Proxy (domain.org) ---- B2BUA ---- [EMAIL
PROTECTED]
INVITE ---------------------->
INVITE ---------------------->
INVITE ---------------------->
<------------------------------------------------ SUBSCRIBE
<--------------------- SUBSCRIBE
But, how much common is this scenario? However there is a solution:
There are two dialogs now:
1) UA [EMAIL PROTECTED] <-----> B2BUA
2) B2BUA [EMAIL PROTECTED] <----> [EMAIL PROTECTED]
So clearly alice must verify the dialog with B2BUA, so the SUBSCRIBE
must arrive to B2BUA. In order to get it, Proxy (domain.org) could
forward the SUBSCRIBE to B2BUA which will match the specified dialog
and reply 200 OK. Proxy would decide to forward this SUBSCRIBE to
B2BUA upon the presence of a "Event: dialog;call-id=xxx,to-tag=xxx"
header.
--
Iñaki Baz Castillo
<[EMAIL PROTECTED]>
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
