Hi Pratik,

RFC 3265 Section '3.2.4 Subscriber NOTIFY Behavior' states following

*"Upon receiving a NOTIFY request, the subscriber should check that it
matches at least one of its outstanding subscriptions; if not, it MUST
return a "481 Subscription does not exist" response unless another 400- or
500-class response is more appropriate"*

So as per RFC, subscriber SIP client must reject such out of dialog NOTIFY
with 481 response.

I have encountered some servers which sends NOTIFY message without client
subscribes for.
Such proxies considers user registration as a subscription for the service.

So, it depends on the SIP client implementation that it wants to follow the
RFC or to make itself inter-operable with such servers.


​Regards,

Mohit Soni


On Tue, Jul 26, 2016 at 9:42 AM, pratik patel <pratik.b.pa...@elitecore.com>
wrote:

> Hi,
>
> Is it possible to send Non-dialog NOTIFY for SUBSCRIPTION request with
> "Event:presence"?
>
> i.e 1) Let a SIP client(3001) SUBSCRIBE to get "presence" status of SIP
> client(3002) with call-id="1234" and cseq="1 SUBSCRIBE".
>
>      2) SIP client(3002) PUBLISH it's presence status, so presence server
> send NOTIFY request to SIP client(3001).
>
> So here Is it possible to send NOTIFY with different call-id and cseq?
> Will SIP client(3001) accept the NOTIFY request with different call-id and
> cseq?
>
>
> Regards,
>
> Pratik
>
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to