Iñaki,
IMO you should not use CSeq this way, for a variety of reasons:
- its a "layer violation". The cseq values are pertinent at the
dialog layer. The content of the NOTIFYs is at the application
layer.
- if perchance the dialog is being used for something else
(e.g. an INVITE) as well as the subscription, then there can be
other messages in the dialog that consume CSeq values.
- you might find SBCs doing funny things as in-dialog messages
cross them.
I know you can make a case that the latter two are weird things that
won't happen, but you are asking for trouble. But they are examples of
why to heed the layer separation.
If the sequencing is important to your application, then you should put
the sequence numbers into the payload.
BTW, don't forget to take into account the rate limiting stuff.
Thanks,
Paul
Iñaki Baz Castillo wrote:
> Hi, I'm doing a custom specification in which NOTIFY's contain just
> changes rather than the whole document (as there is no concept of
> "document" at all). In this case I need that the watcher receives
> always a NOTIFY with CSeq incremented in eactly one. If last received
> NOTIFY had CSeq=12 and the watcher receives a NOTIFY with CSeq=14 it
> means that it has lost some change, which is not suitable for my
> specification.
>
> So, how can achieve it? I wouldn't like to rely on a "version"
> parameter into the notification body as there is no concept of
> "version" at all (since there is no concept of "document").
>
> Any suggestion please? Thanks a lot.
>
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
