I implenent a new TMS Server 13.1.2 (VMware ) and VCS-C x.7.0.3 and Movi 4.3. Everything works fine but only the Provisioning Phonebook doesnt work right.
The Problem is, that i've got only 2 of 8 created contact or user's on the Phonebook. But in the Phonebook Sources they show all 8 Movi users. But if you connected the Movi Folder and Endpoints Folder, i've see all Endpoint correctly but only 2 Movi users.
I tried all, disconnect and connect again, created new Users. But it doesnt help.
Maybee i must disabled the Provisioning and enabled again?
The default Configuration add. of the Movi 4.3 is:
Alok is on to something here as the movi user will only appear in the phonebook if it has a device. If you are logging in with different movi user on the same client (device) the device is just "moved" around . If you are logging in from different pc's and still see this issue, please let us know if they where imaged and if the image was properly sysprepped to assign a unique SID to each of the pc's. Ive seen this before
If you are logging in from different pc's and still see this issue, please let us know if they where imaged and if the image was properly sysprepped to assign a unique SID to each of the pc's. Ive seen this before :-)
The chance of this being the issue is low if you just tried with the same client on multiple users. But i have seen this before.
What I mean is : The Security identifier (SID) is a unique identifier generated by windows setup. This SID plays a part when the device id is generated for the movi client on the machine.
If the SID is duplicate the device id for jabber may be the same on multiple computers with the same SID. This is equivalent to one device logging in with multiple users just moving the device id around since this is unique.
The SID will be duplicate if the PC is imaged after installation without sysprepping it so the next pc the image is loaded on gets a unique SID.
However i would not worry to much about this for now.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...