sounds like good improvement. Please file an issue in tracker.sipfoundry.org
On Sun, Oct 31, 2010 at 6:52 AM, Justin Menga <[email protected]> wrote: > Hi > I have a problem with the Phonebook API - basically the full Phonebook call > (/my/phonebook) returns a list of all contacts in the user's personal > phonebook in an XML format, but there is no "unique" identifier provided > with each entry. > Now the API supports interrogating a specific Phonebook "entry" - e.g. > calling /my/phonebook/entry/1 - which is fine, however the entry ID has > absolutely no correlation to the full phonebook list called by > /my/phonebook. I was expecting in the absence of an "entry" ID in the full > list that the entries would at least maintain the same order in the list > (i.e. entry ID 1 would come first, entry ID 2 would come second and so on), > however that doesn't appear to the case. > Also closely related is when you issue a search query - e.g. calling > /my/search/phonebook?query={search-query} - you don't get back the entry ID > in the response. > The lack of a unique Identifier makes it very difficult to delete a contact > using the APIs, as you need to reference an entry ID when you delete. The > only way I can see to do this currently is to get the full list, get a count > of phonebook entries, and then iterate from 1 up to the count to determine > the entry ID for each entry - not ideal at all! > Regards > Justin > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
