01-28-2013 11:59 PM - edited 03-18-2019 12:30 AM
Hi Together,
we installed the new TMS PE with 14.1.1 Jabber ect.. with VCS X.7.2.1
So the Phonebooks from the Jabbers AD( Provisioning Source) works fine . But if i push the push the Phonebooks to a registerded Endpoint EX90 on the TMS and VCS-C, do not receives the Phonebooks like All System or Jabber Phonebook.
i disconenct the Sources and conencted again, i sync the provisioning, i create a new sourche und and new manage Phoebook but without access.
On the VCS-c the External Manager connection between the TMS and VCS- is also green.
No Firewalls between the TMS and VCS-C.
Again, on the Movi client, i see the Phonebook but not on the real Endpoint
What could be the problem?
THX
01-29-2013 12:13 AM
Hi Rasim
Did you make sure the public folder in IIS is set to Anonymous access?
/Magnus
01-29-2013 12:29 AM
Hi Magnus, not really,
could you please explane why and how ?
01-29-2013 12:35 AM
Hi Rasim
The endpoints get their phonebooks from the TMS in general when you push it to them. The jabber clients get their phonebooks from the VCS, this will also be the case if you provision the ex90 from the VCS.
But in this case where you grant the endpoints access to the phonebooks in TMS the endpoints will send a http request for the phonebook to the phonebook api in TMS. This api is in the public folder in IIS and since the request is not authenticated the public folder needs to be granted anonymous access.
In IIS just locate the public folder:
I am not saying this is the issue you are encountering but its pretty common.
The issue could be endpoint related as well but you are not telling me that there are other endpoints its working from. SO usually when all endpoints are missing their phonebooks the problem is on the TMS side, and most likely the public folder
/Magnus
01-29-2013 01:48 AM
Hi Magnus,
perfect, it works now great Magnus. It was disabled
01-29-2013 10:37 AM
BTW, what Magnus described to you is also found in the Troubleshooting section of the new TMS 14.1.1 Admin doc (page 311):
Always good to be familiar with documentation when troubleshooting issues
cheers,
Dale
02-14-2013 06:07 AM
Hi Magnus, Dale,
I have again the same problem, only that with certain devices groups didnt phonebooks are on the SX 20 Endpoints. IN the TMS are all the books in order but I don't see any on the SX20. On the EX90's all Phonebook fine.
I checked also all settings like this picture
I removed all Phonebook from the SX20 and pusit again, no success
I purge the Endpoint and added again, without success
i make the PE diagnostic and all led 's are green.
I perfomed PE Full sync but without success
Any Idea's
02-14-2013 06:22 AM
Hey Rasim
Can you tell me if the phonebook URL on the SX20 is IP address or FQDN?
/Magnus
02-14-2013 06:26 AM
Hey Magnus,
under Phonebook Server1-->URL--> http://tmsserver.company.com/tms/public/external/phonebook/phonebookservice.asmx
The FQDN is also pingable
02-14-2013 06:30 AM
Yea, but I just saw a similar case recently. Can you change it to IP and see if it works?
It might be a bug, but first see if the phonebooks appear if you change it to IP. Make sure phonebooks are SET on the System first since that the most basic thing that needs to be in order.
/Magnus
02-14-2013 06:39 AM
Could be DNS issue as well
/Magnus
02-14-2013 06:54 AM
Hi Magnus,
it doesnt help, tried wit the URL: http://10.10.10.10/tms/public/external/phonebook/phonebookservice.asmx
and only the IP in the URL Path but without success. That is strange. On the EX 90's we addet or remove phonebooks, everythin works fine, but not on the SX 20
02-14-2013 07:09 AM
Access the SX20 on via SSH as root and type: curl http://10.10.10.10/tms/public/external/phonebook/phonebookservice.asmx
Do you get a result?
A wireshark trace on the TMS server should tell you if the request is even coming into the TMS, if not I would check the network.
Another thing is to try to set the "route phonebook entries" to No in the General settings of TMS and see if that works (if the request is coming into the TMS that is).
/Magnus
02-14-2013 07:10 AM
And I am not sure what part TMSPE is playing here...? Endpoints <-> phonebooks are pure TMS <--> endpoint communications.
For provisioned devices it would be VCS <--> Endpoints in regards to the phonebook requests but as I understand they are not provisioned. SX20 is not supported for provisioning through VCS anyway.
/Magnus
02-14-2013 07:17 AM
The feedback fro mthe customer was, that the Phonebooks have works. The SX20 is a endpint and not a provisioning device.
The Phonebook should works, any other ideas? The TMS Version is 13.2.2 and the VCS is X.7.2.1
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide