TMS Phone book Update Type: Search Only

[Patrick Sparkman]

We currently have two phone books that we "Import to TMS" from their phone book source, but are looking to change that settings to "Search Only" due to the length of this particular phone book.  I know instead of showing all the phone book entries in one huge list like it does when it's set to import, one has to search to pull up the entry they want.  In what way, if any will changing this setting have any affect on scheduled conferences that utilize that particular phone book whether it is set to import or search?

Thanks!

[Zac Colton · Accepted solution]

If the phone book is set for "Search Only", you will not be able to use those contacts in scheduled conterences.

- Zac

*UPDATE*

You will be able to add the contact to the confereces, but TMS will display "Deleted Phone Book Entry" for the contact when go back to view the conferece. TMS will also display a warning if you view the connection tab for the call routing details of the conference. I have confirmed this today, and I have filled a defect in regards to this. CSCui45154 The defect is new, so it will not yet be publicly viewable.

[Patrick Sparkman]

Thanks Zac, I figured that weither it was Import or Search wouldn't affect scheduling via that phone book, but only how you access and display entries.  Since import makes all the entries avaliable right there, and with search you have to of course simply search for the entry you want.  From a TMS standpoint, it shouldn't matter, the phone book is still fully avaliable in either method, just displayed differently.

Are you able to post the specifics of the BUG Id?

[Zac Colton]

The specifics of the bug are more or less as I described them:

When using a phonebook set to "Search Only", you can successfully add a particioant to a scheduled conferece. However, if you go back to view the save conferece, the participant list will show "Deleted PhoneBook Entry" instead of the contact display name. If you select the connection tab to view the call routing, TMS will display an error ar the top of the page. This has been test in the latest code for TMS. 13.X will behave differently, reguarding scheduled participants that are considered deleted phone book entries.

Conferences should launch fine with the connection details that are save at the time of the booking. The issue appears to be more of a cosmetic issue. Since all ramificaitions of this issue are still an unknwon, I strongly recommend either setting the phone book to "import to TMS", or not using that phone book for scheduling purposes.

[Patrick Sparkman]

I can add to the "Deleted Phone Book Entry" issue, is if you want to update a conference that contains an entry of that nature, you have removed/re-add that entry.  I could potentially be cumbersome if the scheduler has to always keep going through the drop/add process for this particular participant over and over if all they want to do is update the participants list or conference.  I should know, I'm facing that issue now.. and it's not related to a search only phone book, but a phone book that was deleted however recreated, though the video address hasn't changed.

EDIT:  We won't move to "Search Only" until later this year when we enable AD import for our provisioning directory.  Since scrolling through the provisioning phone book would take a forever long time to find the specific user, and it seems kind of rhetorical to give access to ALL those users in a list type phone book.  So I'm contemplating changing it to search instead of import when we get there later this fall.

[Zac Colton]

I am also aware of the aiisue. I have opened a couple of different defects regarding deleted phone book enries.

Here is a defect I opened a while ago: CSCuf90606

I believe that one is viewable