I've recently got TMSPE working with VCS X7.1, TMS 13.2 and Jabber 4.4. Provisioning, calls etc all work OK but I can't seem to get phone books working.
The phone book folders and entries show up in VCS, I've assigned the phonebooks to the relevant user folders from TMS, mase the phonebook URI "firstname.lastname@example.org but every time I search from within Jabber it says "No exact match found" and returns no results.
Is this a new installation or did you upgrade from the legacy TMS Agent?
While TMS Agent was running previously, I didn't actually have any provisioning data in there. Essentially it's a new installation.
None of the phone book entries appeared on VCS until I got everthing set up - it seems like the provisioning side of things is working well betwenn VCS and TMS.
Do the folders from the provisioning groups have access to see the phone books - this is set up from the phone book menu. Also note that the access doesn't flow down the folders - if you tick access for a top level folder, folders under that folder won't get access unless you tick them too
On the VCS you can check phone book access go to -
Status - Applications - TMS Provisioning Extension services - Phone book - User access
And check the user has the list of phone books you expect
Sent from Cisco Technical Support iPad App
I had a similar problem after upgrade from TMS 13.1.2 to TMS 13.2 and TMSPE. The Phonebook folder was shown on endpoints, but if I searched on a Jabber client, the Phonebooks were not available. I tried to set permissions for Provisioning Users and TMS says "Permissions updated.", but after refreshing the web page the permissions are gone.
These Phonebook folders also do not appear on VCS.
I recreated the folder structure and now the permissions work fine.
It looks like it's a user access issue - whenever I try to grant access to the user groups in TMS > Phone Books > Manage Phone Books, it gives an error saying "cannot communicate with TMS provisioning extension services - see web-log.txt for details".
When I read the log file, it reports "Internal server error". I've tried restarting both VCS and TMS but no luck.
All other provisioning is working OK - the users and the phone books themselves populate correctly between VCS and TMS, it's just the phone book access that't the problem.
I should add that when I checked log-web.txt on TMS, it has the following error:
"WARN ASP.tandberg_tms_ui_phonebook_phonebooksetonuser_ascx - POST http://localhost:8788/pb/phonebooks/id/0c8b7cea-0855-4929-a278-2c2c54d8998e/acls failed: The remote server returned an error: (500) Internal Server Error."
The phone book shows no errors when going to “Systems > Navigator > VCS > Provisioning” , but under “Provisioning Extension Services” it shows a critical alarm for the phone books, telling me to check the TMS connection settings.
Under “TMS Provisioning Extension Settings > Cisco TMS Connection Settings”, it doesn’t seem to accept the username and password, saying “Connection Refused”. I have double checked the username and password and can use the same credentials to log into TMS. The user is a site administrator.
Question as to my above post - am I right to assume that if it says "Connection Refused" it's not a problem with the username and password, but the connection is being refused before authentication is checked? As the connection is just to the localhost I wouldn't have thought it would be an issue...
What are the Provisioning Extension Diagnostics telling you? I'm assuming your seeing a red status on the Phone Book but can you confirm that. If this is the case, then I'm fairly certain this is the root of your problem, i.e. internal issue on the TMS server between the TMS and TMSPE.
On the Provisioning Extension Settings page > Cisco TMS Connection, and assuming your TMS and user is on the domain, are you entering the username as "domain\username" and I assume password is correct and the user isn't disabled or locked?
And I believe you did confirm that this user is part of the TMS Site Admin group...correct?
What PB and PB source are you utilizing for your Jabber users, i.e. Provisioning PB and Provisioning Source?
And the TMS/TMSPE installed in redundanct setup or is just a single TMS/TMSPE?
We ended up getting this working (thanks to TAC) by a full reinstallation of TMSPE.
Apparently, after TMSPE installation you can't change the username/password of the TMS connection or you have to re-install!
Sounds like the kind of thing you would document, but apparently not........... would have saved me a week!
Appreciate that you found a solution here. However, this doesn't sound right to me. For example, I assume your talking about the username and password on the Provisioning Extension Settings page? If so, then it should be possible to change this username and password, as long as the user your changing it to belongs to the Site Admin group in TMS. Was that true in this case? And if so, can you please provide me with the TAC engineer you worked this case with. I'd like to find out more about this since again, this should be possible to do.
I currently have exactly the same issue. At this point I am checking to see if the site admin account I created (user: tmspe) exists in the phone book user access page as per your suggestion. tmspe is not there, all the Jabber accounts are there.