Brett Tate wrote:
>> From: "Vikram Chhibber" <[EMAIL PROTECTED]>
>>
>> Yes, I agree now. There is no standard that mentions about
>> accepting unsolicited NOTIFY. The RFC 3265 mentions establishing
>> subscription using non SIP mechanism, the NOTIFY should always be
>> received in an existing dialog.
>
> Yes; that is what the definition section mentions. However it obviously
> isn't complete since notifies can create the dialog (i.e. forking
> situations).
The cases where NOTIFY can create a dialog are somewhat constrained. The
callid will match a callid originated by the recipient, and the to-tag
of the NOTIFY should match the from-tag of a SUBSCRIBE (or REFER) sent
with the same callid.
In the case of a truly unsolicited NOTIFY, the callid will be generated
by the sender, and there will be no to-tag. In this case I don't think
the recipient should be establishing a dialog.
Paul
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
