Hi I?aki,
>From UAS core prespective of B2BUA, dialog state goes to *Trying* on reciept
of INVITE and if provisional response is sent by B2BUA with tag, dialog
state reaches to *Early*, that's what happening in your case (i believe that
B2BUA responds with provisional response with tag). Hence, this seems OK as
per RFC 4235.
However, it is up to the B2BUA implementation whether it maintain the
*dialog* (from NOTIFY perspective) state of its own UAS core OR actual UAS
viz Alice (from NOTIFY perspective). Your idea is perfectly OK if B2BUA
implementation is following the dialog state of Alice itself which is actual
called party instead maintaining the *dialog* (from NOTIFY perspective)
state of its own UAS core.
Best Regards,
Vivek Batra
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
