In the current RLS architecture, we have a cache of "resource URIs", in that if several users' BLF lists contain the same URI, the machinery notices this, and obtains and composes that URI's status only one, which it then sends to each of the users. This avoids having more than one subscription to a phone just because several users specify that phone's user in their BLF lists.
When I was testing the RLS with the new phone identification system, I noticed that the RLS was sending three subscriptions to one phone. It turns out that this is because there were these three URIs in BLF lists: sip:[email protected] sip:[email protected] sip:~~in~203/[email protected] all of which have as a contact the URI for the appearance of 203 on phone 00405a187c1a: sip:[email protected] The code in the RLS does not check to see if two resource URIs share a contact URI because without the phone identification feature, that rarely happens: resource URIs are AORs, and two different AORs do not share a contact URI (because that would make it impossible to subscribe to their statuses separately). Since phones tend to support a limited number of dialog subscriptions, it looks like we should add another cache in the RLS, to allow two resource URIs that share a contact URI to be supported by only one subscription to that URI. Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
