TMS directory - contacts AD

I've recently upgraded to 14.1 and tmspe. During the upgrade, I've migrated my entries inherited TMS in the new solution highlights. The transmission of data contained in 5 groups with the users in each group. When I log in MOVI as legacy user and find the directory entries, everything works as expected.

The problem I have is this - I created a new group and imported my Active Directory users. I can connect to MOVI as a user of Active Directory however when I try and search for users/end points in MOVI nothing appears.

I checked for the provisioning directory ticks next to all my other access control entries in the phone book.

All the world and ideas?

Thank you

Stem

Hi Rod

The first thing that comes to mind is the configuration information. If you have created a new group you also assigned to this group a provisioning model right? This model is different from other groups? Because other users directories work what is the difference between these users and the users AD?

Users of AD have the configuration of the directory [email protected] / * /?

/ Magnus

Tags: Cisco Support

Similar Questions

  • Check if the TMS directory is accessible from codec

    Hi all

    I'm starting a new configuration of telepresence. I have problems with directories. Seems that codec are not even trying to search the TMS directory.

    How can I check if the codec is configured to query the directory TMS?

    In "Advanced-> directory server 1 Configuration" ID has the default value, type MSD and URL to http:///tms/public/external/phonebook/phonebookservice.asmx

    When users press the directory key in remote control no shows, only my Contacts.

    Thank you

    Concerning

    Thanks for the update - the question is usually a proxy or a firewall - your endpoints need to have direct access to port 80 on the box of TMS on the subnet, they are on.

    Wayne
    --
    Remember the frequency responses and mark your question as answered as appropriate.

  • TMS directory failed in the endpoints of series C after the migration of the device to the virtual computer

    Hi all

    We have migrated the 12.8 TMS from the device to the TMS 13.0 on the VM platform. There is no matching TMSPE and mainly used for management and directory service.

    Once the migration is complete on the platform of the VM, we found that endpoint C-series could not receive phonebook of TMS (while 95 MXP endpoints works very well with the TMS directory).

    The end point of series C, we check the Configuration-> directory server 1: URL. The link is converted from http:// /tms/public/external/phonebook/phonebookservice.asmx http:// tms/public/external/phonebook/phonebookservice.asmx.

    (In addition, we check the authorization of the two phone book page, and there is no IIS issue).

    In the 95 MXP endpoint, it can receive the telephone directory unit VM MSD and MSD.

    Best regards

    Ben

    Hi Ben,

    As confirmed by the curl command - you don't have access to the web page as an anonymous user.  You have to fix your permissions.  One of the fastest ways to do would be to try to reinstall the MSDS on the server again - this should reconfigure the IIS settings required for TMS.

    Wayne
    --
    Remember the frequency responses and mark your question as answered as appropriate.

  • Synch TMS directory phone book Local Codec

    Hi all

    I was wondering, is it possible to synchronize the TMS (server) directory to the Codec (C20, 40, 60) Local Directory?

    I checked on the guides of the admin and also on this forum, but without success.

    Thanks in advance

    See you soon
    Hugh

    Hi, unfortunately, this is not possible with the c series that it does not support the download directories. The MXP in comparison does not support this.

    / Magnus

    Sent by Cisco Support technique iPhone App

  • TMS Directory link ISDN paired devices

    Hello world

    I currently have a problem trying to get a directory TMS containing details of ISDN on a SX20 with an ISDN connection.

    I created a manual list directory in TMS that contains details whether H323 or ISDN for various parameters.  The directory is detected by the SX20 and it shows all the details of H323, but none of the ISDN are listed.  The same directory, when it is applied to an edge 95, displays all the entries.

    I tried to create a directory containing only the ISDN numbers, and assigning that to the SX20 and then nothing is indicated.

    My first impressions are that that TMS has information as an 'ISDN' entry, and as SX20 has similar directory information stored in the form "H320", that the two are not compatible / correcftly - translation and so it's a TMS bug and/or TC software.

    In addition to the telephone directory, all the other functionality works as expected.

    Versions:

    TMS: 14.1.1

    SX20:TC7.0.1

    ISDN link: IL1.1.0

    Edit: I tried to push the same directory for a C60 and who was not either - TC6.3 - only the H323 entered were seen running - ISDN those lacking, is not purely a matter of SX20.

    Wayne
    --
    Remember the frequency responses and mark your question as answered as appropriate.

    Hello

    There is no link to the SFT ISDN support. When 'route telephone directories' is set to Yes, TMS removes the entries she wants not the point endpoint to deal, that is what is happening here. TMS knowledge, SX20s cannot dial numbers H320.

    ? Kjetil

    Sent by Cisco Support technique iPhone App

  • TMS directory system endpoints source folder

    Hello

    I came across a rather baffling problem with a few cases of TMS and I can't for the life in me know as to why this is happening.

    I get the following.

    in the option for creating source directory Cisco TMS, I create a new directory and link with the MSDS files and select the folder where all the end points, this creates the entries in the phone book for me as I expect with one exception, I will detail below.

    H.323 = [email protected] / * /

    H.323 = [email protected] / * /< this="" is="" where="" the="" issue="">

    IP = IP address

    I find that on some systems (this doesn't happen to all systems) in the second entry of H.323, the H.323 entry where I expect to see the directory (also known as E.164 number) number I see a URI where a field has been added at the end of the number, I'll give you a few examples below.

    DN = 1234

    set field = @video.net

    random field = @newdomain.com

    IP = 10.10.10.1

    I expect to see the following.

    H323 = [email protected] / * /

    H323 = 1234

    IP 10.10.10.1

    but I don't actually see

    H323 = [email protected] / * /

    H323 [email protected] / * /

    IP 10.10.10.1

    I have purged the TMS systems and added, I searched through the xconfig for the NouveauDomaine which is invalid and I can't find anything anywhere other than on the list of areas configured SIP VCS parameters in the second area, endpoints have disabled by default SIP and in both cases I expect to see that under a SIP entry not an H.323 entry

    This is the origin of the problem of when a user tries to call via the Directory site remote also responds to busy VCS is unable to find the appropriate directory number because the location request contains the domain as well as the DN.

    I worked around this by adding a transform to the VCS who sees the patter of specific numbering and the bands of the area, so the calls work, but I still need to understand as to what is causing this behavior.

    If I had to create the directory entries by importing information from the record of the VCS seem to be correct, its only when I try to import the entries of the endpoint via the system folder in TMS (or more exactly to import the information stored in the file on the endpoint system) I see the problem.

    a very popular Adviser.

    See you soon

    Dave

    Hello

    Picked up that the case with David and it seemed that at least on the systems the international denomination on the mxp MXP has been configured. The area of intellectual property also has a configured domain uri that has caused the other symptoms. We where able to erase the questions but still yet to see if the client is actually affected by the same configuration "mistakes".

    / Magnus

    Sent by Cisco Support technique iPhone App

  • TMS directory

    Hey Cisco user community.

    I work with TMS 13.x and need to import a .csv file to add to my repertoire. It does not appear when I search the file.

    Is there some settings, the data must be in allowing TMS accept the file?

    The file contains a list of contact for Vidyo users data.

    Any help would be appreciated, and I am also happy to provide you with more information.

    Thank you

    Nick

    Network management may not be good community CSC to meet telepresence related research. You can republish or forward this question to the community MSDS here:

    https://supportforums.Cisco.com/community/5886/Telepresence

    I would like to get the attention of right from members of the community and experts.

    -Thank you

    Vinod

  • TMS directory against LDAP directory

    Morning,

    We intend to use a real directory like Phonebooksource.

    To connect through the AD, it's no problem, but the LDAP user has a different format.

    AD : >\>

    LDAP: CN = videoUnit, CN = Abo, CN is accounts, CN = System, CN = Apps, O = company, C = OF

    In this format, I tried a lot of.

    But nothing seems to work, does anyone know the problem?

    Greetings

    Jens

    No, not really, I'm afraid, I just need to know more precisely the type of LDAP you are trying to connect, if it's not AD... And what kind of Source of PB in TMS you try to use when you try to connect to the Directory LDAP AD, H350, H350 user directory?

    And if I understand you correctly, you are saying that you can connect successfully to say AD but not this particular LDAP that is not AD but something else... OK?

  • GSM numbers in the TMS directory

    Hello

    I have AD facility as a source of the telephone directory in TMS for video settings. I'm having a problem where the GSM numbers for users on endpoints TP are appearing as H320 and so the calls fail. I have a VCS/TMS connected to CUCM and want to route mobile calls to CUCM and then get out. Is this possible.

    Thank you!

    Then I was watching your definitions of zone again.

    • TMS needs to know that the endpoint can make H.323/SIP
    • The permissions for the system in the browser from should not be the call blocking options (settings down to change the planning parameters)
    • The endpoint must be associated with a zone of intellectual property with a defined gateway prefix
    • The area of intellectual property must be associated with a correctly configured ISDN zone
    • Route of the directories = yes

    If all this is in place, TMS will be able to deliver to an end point unique h323 call entered ISDN or telephone through the gateway prefixes defined in the area.

    If the entries are not displayed, TMS does not believe he can do a call from the bridge... the lack of supported protocols or failure of registration status.

    You can test this by creating a simple dummy directory with just the vocal entries in it.  Then associate this directory to your endpoint.  If it's an MXP, you can use the web interface of the endpoint to display the directory of the business directory provided by TMS.

    If you can not make it work again, I'd recommend appellant TAC where they can walk through your configuration with you.

  • Installation failed once again. Says bond impossible to extract to the temp directory, contact support (EX11)...?

    Hello! I am trying to install a trial version of InDesign.

    Teeenaj, this means that your current user account is unable to write to the Temp directory or that there is insufficient disk space.

  • Directory of TMS on the endpoints registered CUCM TC

    Since 14.4.0 TMS version, it is possible get endpoint CUCM registered directory server to point to the TMS directory instead of the CUCM directory.

    I tried to set up, but I still can't get it to work.

    On the endpoint of TC (version TC7.1.3), in Configuration > System Configuration > Server from the phonebook,

    I set the server type MSD and the URL as http://TMSserverFQDN/tms/public/external/phonebook/phonebookservice.asmx

    When I SSH to the endpoint TC I ping the TMS serverFQDN so DNS resolution on the endpoint is apparently works.

    When I open this URL in my browser, I get a page called "PhoneBookService" with GetPhonebooks links, ResolveSystem and research

    But on the preview endpoint it works everything simply. This shows just "no directory.

    How can I solve this problem?

    A few quick questions that jump to mind are:

    1. Endpoints defined in TMS?
    2. A TMS directory is published at the endpiont in MSDS?
    3. The directory TMS has a source valid and entered in it?

    Wayne
    --
    Remember the frequency responses and mark your question as answered as appropriate

  • Import and export directory for CUCM and TMS

    How can I configure TMS and CUCM use of TMS directory for an endpoint registered to CUCM? I've added to TMS but and TMS can shoot CUCM Phonebook, but how does he see the directory for other infrastructure in TMS to fill in the directory of CUCM CUCM?

    If the endpoint of telepresence is running TC7.0 or later, you can configure in CUCM using TMS as a source of spare phone book, there are also TMS 14.4.  Refer to the Administration of the TC on CUCM 10.5.1 endpoints (TC7.2) on page 24 for more information.

  • Managing local Contacts on endpoints TC7

    I have a few points of termination of TC with local Contacts to 100s. I wish I had a way to remove at once by command line.

    I tried to use the command xcommand directory Contact remove ContactId: possible in different ways, but I am still unable to get a combination of delete all existing at once. The only way I see right now is to delete one by one.

    someone has already tried before? is there a way to completely erase the local favorites list quickly?

    Put the bottom in a text file and import it into endpoint under Configuration > local Contacts management.  The import will replace anything on endpoint with everything that is in the file.

        

    Another way, which is what I did to test this, is to export the current telephone directory and delete all contact entries in the export, then re-import the file modified in the endpoint with no contacts.

  • Questions of FindMe Provisioning/user between TMS &amp; VCS

    Hello

    I have what seems to be a problem in service between TMS and VCS.

    Using TMS to import users from AD (from 2 domains of x), everything seems to work, and can see the users in the provisioning of TMS directory. MOVI users use AD authentication which connect properly.

    User login also works very well on the VCS (with connection LDAP AD). However when to call the findme users address VCS does not recognize the configured users? If you navigate in user accounts, the user is not displayed, if you run a search on VCS (users account address name or findme) findme VCS find the user. Once the user has been found and open if you click on save button (without changing details), the user will then appear in the VCS user accounts section and findme works correctly.

    We use the TMS 13.1.1 and VCS x7.0.2 (Cluster).

    I would like to know if you have solved your problems or you are still having problems? Any suggestions for help would be appreciated.

    Thank you

    Matt

    Hi Matthew.

    Findme users must fill in the "user accounts".

    But you must make sure that the VCS 'Cluster name' matches the 'SIP server address' in TMS.

    TMS:

    VCS:

    I hope this helps.

    / Magnus

  • Migration of TMS/VCS to CUCM

    Hello

    I was wondering if anyone can help please. I had a customer who uses VCS? TMS. Every endpoint registered in VCS - C.

    I need migrat ethem to cucm 10.5.

    What will be the best way to go, any suggestions will be appreciated.

    Thakns

    Of TMS directory are what kind you referring?

    You can use TMS to a source of the telephone directory with the telepresence endpoints registered to CUCM, see pg 24 in the guide I linked to in my first answer.

Maybe you are looking for