a user complained that un-subscribing a pending subscription is also pending, i.e., kamailio responds with 202 instead of 200. i verified the behavior.
now the question is, what do the relevant RFCs say about it? it appears logical to me that if a user gives up waiting to get his/her subscription confirmed, he/she should be able to forget the whole thing by sending an un-subscribe.
any comments on this?
-- juha
I've checked RFC 3265 but could not find a description. Probably you should ask at the sip-implementors list
klaus
Juha Heinanen schrieb:
a user complained that un-subscribing a pending subscription is also pending, i.e., kamailio responds with 202 instead of 200. i verified the behavior.
now the question is, what do the relevant RFCs say about it? it appears logical to me that if a user gives up waiting to get his/her subscription confirmed, he/she should be able to forget the whole thing by sending an un-subscribe.
any comments on this?
-- juha
Users mailing list Users@lists.kamailio.org http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
Klaus Darilion writes:
I've checked RFC 3265 but could not find a description. Probably you should ask at the sip-implementors list.
i looked at rfc 3265 and found this in section 3.3.6:
Note that the NOTIFY messages triggered by SUBSCRIBE messages with "Expires" headers of 0 will contain a "Subscription-State" value of "terminated", and a "reason" parameter of "timeout".
wireshark dump reveals that notify request is not generated at all when ua un-subscribes a bending subscription. there is just 202 followed by nothing.
-- juha
-
jh＠tutpro.com -
Klaus Darilion