________________________________________ From: [email protected] [[email protected]] On Behalf Of Jean-Hugues Royer [[email protected]]
When you subscribe to the RLS for the first time you get a fullstate (RFC4662) of the list which is good, but for each resource you get the last notification received which can be a partial state (RFC4235). So it is impossible to know the full state of the extensions whom the last notification was a partial state. To overcome this problem the RLS server at sipXecs should not only remember the last notification of every resources in the list but also construct a full state out of it to give it in the first RLS subscription. _______________________________________________ This is true if you subscribe to the "full state" URI, ~~rl~F~[user]. But if you subscribe to the "consolidated" URI, ~~rl~C~[user], the various dialog events that the RLS receives are folded together into one synthetic dialog event, and a new subscription to that URI will return the full state in the first NOTIFY. It's not entirely clear from RFC 4662 whether a resource list subscription *should* integrate the notifications that it receives. But for practical reasons, the RLS provides URIs that do, so we haven't attacked that problem. Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
