Registration MXP300 G2 in TMS

Similar Questions

• Purge schedule on the TMS/TMSXE

  TMS is 14.3.0

  TMSXE is 3.1.2

  We gave up on the recording of our telepresence on the CUCM, we work to keep away them from the CUCM and their inclusion in the VCS - C (see here). But when you remove the CUCM non-registrant endpoints off the TMS and add it as registered endpoint C - VCS, TMS causing problems on all scheduled meetings.

  After the now the rebinding VCS - C saved telepresence endpoints for room calendar changes in the TMSXE, it

  1. Add the 'new' (actually modified) end for the calendar of meetings
  2. maintains endpoint (previously saved CUCM) former listed as a "shadow" unknown endpoint
  3. clear the multipoint resource MCU/TP server allocated meeting
  4. send an email to the host of the meeting, saying: "information your administrator is migrating to a new system of conferencing reservations." During the migration, your conference was made. Cautions due to limited resources of routing, automatic routing could not be set up for your conference. A participant dial-in/out external added to the call is not connected. To ensure that the Conference will connect and the delivery of resources are available, contact your administrator to videoconferencing. Road is not valid.

  But all meetings are internal, and there are many resources available on the telepresence Server

  I wonder if there is a way to solve this problem and what we should do. Is there a way to purge all the TMS meetings so that the TMSXE re - synchronize all the information meeting of the TMSXE.

  Hello

  There is unfortunately no history of migration in TMS between a CUCM-centric and a deployment centered on VCS. If you make a change like that, you essentially need to manually update all future bookings.

  Kind regards

  Kjetil

• TC cannot connect to TMS on demand conference

  Hello community,

  I sent TCS in our video conference infrastructure and SIP Trunk to CUCM.

  I can do by opening a web session of the TCS for manual registration and dial points endpoint or lectures on the conductor using SIP.

  But if I do the Conference planning on recording of the Conference, the TCS and TMS don't auto connect to the Conference. Registration (SIP URI) alias are configured on TCS.

  I see on the connection of conference TMS setting the driver calls the CHT by using the h.323 protocol but TCS is not registered with the h.323 Gatekeeper. It's using a SIP trunk to CUCM. Is this a limitation if the TCS uses SIP trunk?

  tcs_error.jpg

  

  Thank you.

  ACCOUNT that is configured with CUCM planning only is not supported yet in TMS using the recording during a conference booking. See cisco-tms-cant-schedule-sip-recordings-tcs for more details, the solution is to add the alias to record with a participating entry model or the phone book.

• Registration for authentication and crossing area of Jabber

  Hello

  I used TMS 13.1.2 as authentication source LDAP for VCS-control and VCS Expressway, but noticed, that not all passwords are synchronized correctly in the LDAP H.350 MSDS database, because the user is recorded in two entries. I went to the local authentication, including the database configuration on VCS - C and the local database with the transmission by proxy SIP VSC-E to the VCS - C records. It works fine and I am able to make calls.

  I created the search on VCS highway rules to replace all aliases MCU to an auto attendant external special. Stored locally on the VCS-E endpoint points are allowed to call internal aliases. I tried to do the same for the Jabber Clients, which is recorded in the crossing area of the VCS - C. This works as expected, because the Jabber Clients are not enrolled in a local area and SIP GUEST is not in dispute.

  I expect that all the Jabber client message will be challenged by the VCSE, but this isn't the case. Accordingly, the guest of the SIP protocol is treated as an external user and not an intern.

  May 9 10:11:28     tvcs: UTCTime="2012-05-09 08:11:28,425" Module="network.search" Level="INFO": Detail="Search rule 'my.domain proxy registrations' did not match destination alias [email protected]/* */'"
May 9 10:11:28     tvcs: UTCTime="2012-05-09 08:11:28,423" Module="network.sip" Level="INFO": Dst-ip="84.113.206.194" Dst-port="62503" Detail="Sending Response Code=100, Method=INVITE, To=sip:[email protected]/* */, [email protected]/* */"
May 9 10:11:28     tvcs: UTCTime="2012-05-09 08:11:28,419" Module="network.sip" Level="INFO": Src-ip="84.113.206.194" Src-port="62503" Detail="Receive Request Method=INVITE, Request-URI=sip:[email protected]/* */, [email protected]/* */"

  These are the rules of research that I was talking about:

  110     Enabled     "local registered to Traversal"     LocalZone      No      Alias pattern match      Regex      ^(.*)@my.domain$      Leave      Continue      TraverselZone
115     Enabled     "authenticated to internal"     Any      Yes      Alias pattern match      Regex      ^(.*)@my.domain$      Leave      Continue      TraverselZone
120     Enabled     "mcu all to 899"     Any      No      Alias pattern match      Regex      ^(900\d*|conference)@nts\.eu$      Replace      Stop      TraverselZone

  Is it possible to allow the Jabber Clients to be authenticated on the VCS-E, so a search rule can aply?

  Thanks for your help!

  You get the 'Preparation device' key for your VCS-E so its free.

  It may require a valid service contract.

  I have the provisioning again running on a cluster of VCS - E in my lab, works very well.

  In ancient times that the deployment has not officially supported, it was running great in any case :-)

  Did not check if its now a deployment with support.

  I don't know enough about your deployment to say what would be the best for you.

  There will be some scenarios where not all features can be deployed together for some reason any.

  Maybe someone can help you by looking at how implementation could be done better.

  If you have authentication and integration of ads, that you need to connect

  the VCS-E announced as well. Endpoints (at least for now) is not auth via AD, but you could

  use a database of h.350 (could also be hosted with AD) or the local authentication database.

  Now, which is also spread by TMS, could be an answer to your question as well.

• Service contract for codec status listed as unknown in TMS

  Hi all

  We have a Cisco MX200 we recently installed and we bought 3 years maintenance contract to the unit by our partner Cisco.  TMS currently appears the contract status of maintenance/service as unknown codec.  We checked the codec with Cisco via the Cisco partner, they are registered and we have also received the contract number for the unit.  However the TMS still shows unknown status.

  The partner said that they have rerequested the registration of the contract of maintenance/maintenance with Cisco, but still do not get any update on MSDS.  All other registered codecs are their contract maintenance/maintenance OK status.  Advice please on how to get this problem is resolved.

  Thank you very much

  Concerning

  David

  Hi David,

  Open a TAC case and provide the serial number of the device to the TAC and they will be successively illuminate the case with Cisco HIM who is responsible for these type questions. The registration database for this device must be updated.

  Best regards, Ahmad

• VCS VCS - E, TMS, TMSPE, Jabber/Movi authentication

  Just trying to figure the best way to approach this.

  I have read the documentation and the best approach seems to get to the VCS VCS-E to Active Directory and the synchronization of the TMS with AD for user account creation. This would avoid the need to records movi proxy for control of VCS and would ensure that all (SIP and H323) registration for the VCS-E would be authenticated.

  I don't think that my client will allow the VCS-E talk to AD.

  So, what are my options?

  If I SIP proxy of VCS-E records the VCS control, how are they managing H323? I don't want just any point endpoint h323 register with the VCS-E. I need to authenticate them. The customer has exernal h323 endpoints that they would like to sign up for VCS - E. I know I could put registration rules to restrict only some URI SIP, H323 IDs etc but it's really just security by obscurity.

  The local on VCS and VCS-E database can be used for authentication Movi/SIP and H323 records? I know that I would have to duplicate accounts and passwords on both.

  What books commissioning and address through registration to the VCS-E? Would it still work?

  Any suggestions on the best way to handle this in the safest way possible without breaking things?

  If I go with the control of VCS and VCS Expressway with authentication Active Directory (directly) on the control method of the VCS as described in the guide of authentication devices, I'm looking for the reality that I will not be able to restrict who can register for the VCS-E? At this time should I just seek to restrict the search for rules to only authenticated users?

  Thank you

  Jon

  Hey Jon,

  MOVI/Jabber you won't have to worry about authenticating H323. With your endpoints however you can just use the database local to authenticate or H350 (more can be read about in the guide of the Provisioning device referred to as Tomo). You can create a different generic for all your endpoints (less secure if which is discovered). But by combining this feature with a political appeal will ensure better security.

  I highly doubt that your client will allow you to leave the talk VCSE in AD. For movi/jabber users, you can create another subfield and use a regex pattern for point movi/jabber users to authenticate it as. * (\.movi)@domain.com. In addition, you can refer to this fragment and others have used in the past.

  In a secure design, the VCS (control and Highway) would require identification for registration information.

  The Control of VCS would have Active Directory Service active and joins the Active Directory domain. For VCS authenticate the credentials of Movi/Jabber on Active Directory before the SUBSCRIPTION for the supply is sent to the service of commissioning, the default Zone would be set to verify the credentials. For requests for SUBSCRIPTION from the highway, the area on the VCS control would also to verify the credentials. It handles authentication for the provision.

  The next part is the record of the Movi/Jabber client. The subzone to which the customer will register must also be set to verify the credentials. Here's everything you need for internal records (registration to the VCS control).

  For the Highway, things get a little more complicated. For commissioning subscription, the SUBSCRIPTION is forwarded to the VCS control. With the area on the VCS game to check the credentials, you're all set. Now on registration to the highway. The subzone to which the customer will register to must be defined to check credentials. From the motorway VCS don't have direct access to Active Directory, we use local credentials on the highway. A set of credentials should be configured in VCS Configuration > authentication > devices > local database. You will create a single name and password all Movi/Jabber clients will use. The end user has NO need to know these credentials. The username and password is provided to the Movi/Jabber client via configuration data it has received. To set up these data, MSDS, you must configure a SIP of authentication user name and password for SIP authentication in the configuration of the commissioning. For these options to be available, you must ensure that you have downloaded the configuration template xml for the Movi/Jabber version you are using. The xml file is included in the zip package full of the client which can be downloaded on www.cisco.com. So, who will be recording from the highway. Now, this creates an interesting situation with VCS control. The internal Movi/Jabber client will receive the same provisioning configuration and will attempt to use those same credentials when you register for the control of VCS. The VCS control is already set to authenticate against Active Directory and Active Directory ONLY registration.

  You will need to create an account in Active Directory corresponding to these credentials. The Active Directory account didn't need special access. It is used only for authentication purposes. A few things to keep in mind: SIP authentication user name and password for SIP authentication are stored in clear text configuration configuration. This means that the data is sent in clear text. To be sure that these data are not compromised on the wire, do not forget that you are using for your communication SIP Movi/Jabber TLS.

  With this directories will always work as jabber should be authenticated in order to receive directories. Your physical endpoint points will work differently with how they receive books and whether or not they are able to communicate with MSDS (unless you choose to configure endpoints also if those you are capable).

  It is in no way the design as safe as possible. It is to you to ensure that your environment is as secure as possible and therefore tested. The best way to fix everything is a well-defined appeal policy designed with your specific needs.

  The foregoing is in no way a recommendation but just a little more information to chew while looking to choose and implement what is best for you.

  Adam

• Remove the video of TCS in the layout when flow on demand through TMS ' record'

  System information:

  TMS v13.2.2

  TCS v5.2 (configured as a terminal)

  4510 Codian MCU v4.4

  The TCS and the MCU are registered at TMS.  I work on the management of all our calls more centrally by TMS and struggled to integrate the CHT in conferences.  I don't want the black screen of the "registration...". "appears as a participant at the disposal of the participants.  I know these can be configured manually to rule out it, but I want to automate it as much as possible.

  On the MCU, aliases are configured to not send the video to the MCU by default; It silently records in the background.  All conferences configured directly on the MCU without the "help" of TMS call out to all the endpoints - including the alias TCS - and only the video settings are visible.  The content is saved properly.

  When conferences are planned through TMS, however, the TCS alias is composed in just like before, but it also sends a video feed to the MCU - a black screen with "Recording" on this subject.  I tried to call from the system directory and what makes an "external" call, but both give me the same result.  I guess that's because the MCU and TMS do not share the same phone book.  What is the reason?  When this happens, the MCU is not the ability to cut the flow of the CS during the video content.

  Currently, my plan is to have every endpoint called via TMS scheduling and then have my technicians dial to the CS manually after that trial is over.  Automation is my aim, however

  Any help would be great.

  Hello Luke.

  You can very easily cut the video and/or audio from the TCS in your conference.  When you create the reservation in MSD and have your MCU added, go into 'Connection settings' and it should be two boxes on the right-hand side where you can trim the video/audio.

  Try it and let us know.

• AD authentication environment VCSe, VCSC and TMS

  Hello

  We have VCSe, VCSC and TMS work with commissioning on the VCSC through TMS.

  VCS, Version 6.1, 13.1 TMS

  Movi (4.3) external Clients have registration with the VCSC. VCSe does proxy registration.

  Users have been configured on the MSDS. There is still no configured AD authentication.

  Everything works fine.

  We now want to configure AD authentication.

  There are several deployments to do, but for me, some of them are not so sure than others.

  I need a top secure deployment.

  I need ideas to make the deployment.

  Thank you

  Martin

  Hi Martin,

  I understand perfectly what you want, but I do not understand why. When you set a directory of provisioning in TMS to be integrated with AD, users are imported automatically according to the 'search string', that you are configuring. But passwords are not imported from AD, basic information only from users are imported. When any user try to connect, TMS challenge for authentication in real time.

  For me it is not a problem, because the MSDS do not save passwords in its own database. Is this a problem for you? Why?

  If you try to do it only because you want to limit which users are allowed to use the customer Movi, if your problem is the following, so you can solve it by using a 'search filter' in the configuration directory configuration, so that you afin que vous serez will be able to import only users who belong to a specific group, for example.

  Please, explain to me why you want to do.

  Paulo Souza

• Conductor XC2.2 and TMS 14.3 automatic connects

  Hello

  I've also seen a topic on current versions of beta XC2.2 conductor and TMS 14.3, so I'll post my question here.

  I use the conductor with VCS, CUCM, MCU 4505 and TS. I am able to create ad hoc via CUCM and VCS and regular calls through TMS conferences.

  If I create a conference with automatic connect and the conductor in the call I can see that the MCU or TS tries to achieve a participant, but not with the URI. To use my email address (findme ID) to call me, but instead, it uses strange URI identifiers: [email protected]/ * /: 5073

  1.1.1.1 is the IP address of the driver. On the front part @ I do not know where it comes from, but it looks like an internal identifier.

  These are the logs of the MCU for a test with a participant conference to be connected automatically:

  13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: "Videokonferenz 101" is 13307 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], numerische Favorites auf ID '88800010 '. 13308 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], pine Favorites auf "114". 13309 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], Gast-PIN options auf "114". 13310 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [101 Videokonferenz], busy 'public '. 13311 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101] content mode set to 'convert '. 13312 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101] Stummschaltung EIB participation [Audio = deaktiviert] 13313 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101] Stummschaltung EIB participation [video = deaktiviert] 13314 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [101 Videokonferenz], Layoutsteuerung uber FECC/DTMF "use FECC and relief to DTMF". 13315 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], maximum Dauer Favorites auf 'permanent '. 13316 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101], Ende Favorites auf "kein Enddatum. 13317 13:38:05 API admin /HTTP/TCP/1.1.1.1:38141 Info conferences: Conference [Videokonferenz 101] auto remove time limit set to "600 seconds". 13318 13:38:06 admin API /HTTP/TCP/1.1.1.1:38141 API-Endpunkt-Einstellungen Info: Endpunkt [e922d880ee1854c242ba94e69b113af: [email protected]/ * /: 5073] via API zu Conference "Videokonferenz 101" added 13319 13:38:06 admin API /HTTP/TCP/1.1.1.1:38141 Info API-Endpunkt-Einstellungen: Endpunkt [3805: [email protected]/ * /: 5073] via API Conference "Videokonferenz 101" added zu 13320 13:38:36 API admin /HTTP/TCP/1.1.1.1:38149 Info API-Endpunkt-Einstellungen: Endpunkt [3806: [email protected]/ * /: 5073] via API zu Conference "Videokonferenz 101" added

  Unfortunatetly newspapers are in German, but I think you can see that there are a few strange added URI.

  If I create a conference without a conductor the log shows the URI:

  13386 14:07:14 /HTTP/TCP/172.21.10.12:52001 Info API-Endpunkt-Einstellungen admin API: Endpunkt [Paul Woelfel: [email protected] / * /] via API zu Conference ' 1234 - Videokonferenz 07/08/2013 "added.

  1.1.1.1 is the IP of the conductor (of course not the real IP ;-))

  Someone at - test the latest versions as expirenced this question?

  Hi Paul,.

  You use the conductor and VCS B2BUA deployment? If so, this behavior is correct. MCU must not call endpoint directly, MCU must compose a unique URI of the driver, something like [email protected]/ * /, so Condcutor will take this URI and route the call to VCS replacing this strange URI of the right destination SIP URI according to what you have planned.

  But to make it work, MCU must not be registered for VCS, MCU should only be integrated with driver, without registration, SIP and H323 for VCS.

  Can you confirm what type of deployment you have? What integration between your MCU and conductor?

  Concerning

  Paulo Souza

  Please note the answers and mark it as "answered" as appropriate.

• The URI of the TMS device field

  I have a situation where a customer has an existing VCS C/E and MSDS to the United States. They added a new C/E VCS in Asia. American systems have the domain customer.com and new VCS in Asia for apac - vc.customer.com.

  In TMS, (they are still using TMS Agent, not PE) Movi/Jabber clients are all configured and use the device URI of [email protected] / * /.

  The only way I could get a Jabber client to register for VCS in Asia was to change this device URI to apac - vc.customer.com.

  Is it possible to add a secondary device URI in TMS? Or is it a translation that I can do in VCS to either allow all movi/Jabber accounts to register as. customer.com?

  Thank you

  SoC

  Hi Rob,

  You can create different subareas, save customers jabber based on their subnet ip addresses.

  Also according to what you have defined in the SIP domain VCS, you can register your jabber/Movi customers based on the SIP domains.

  You can use the CPL to change coming for registration domain names.

  BR, Ahmad

• Registration of telepresence

  We have our configuration of the recording and the work, but I'm looking for the place to change the screen on registration form.  Instead of him occupy little space and say record I want just display a red dot.  I saw a video like this, but I can't find where I can change this.  Any ideas?

  Cisco TelePresence Content Server v5.3 build 3316

  TMS - 13.2.1

  MCU - 5310

  I understand that, you want to hide the red dot with the video "Recording" that appears when it is connected and show only a red dot on the screen?  And I assume you are using a TCS?

  You can on your MCU, cut video of the TCS that will hide the splash video "Recording" from the server.  Then turn on your MCU the following setting make a red dot appear in the upper corner of the screen for everyone.

  Settings > superimposed icons > record indicator

  I would like to know if that's what you're looking for, or have something else in mind.

• Design of the telephone directory of TMS

  SALVATION of Netpro

  I have a VCS - C AND TMS located within a DMZ. The VCS-E is on the public internet.

  All internal clients are saved on the SCV - C and pull the telephone directories of TMS - OK.

  I would like to publish directories TMS to devices that are registered with the VCS-E

  Our compnay is a global organization and we have external companies with the internet only C20 end points which are registered in our E-VCS.

  My goal is this - I would like to have a global directory that all systems have access to via registration VCS /TMS

  Is the only way to achieve this goal to create two TMS servers who ask the same PB? A single server TMS on the DMZ with a NAT translation on a public address and a TMS server inside the network to all WAN / LAN clients?

  Or y at - it another way to reach my goal?

  Thank you

  Stem

  Well, the directory is transferred using http, which means that endpoint must join the tms on http or https in order to get it. An alternative would be to open port 80 or 443 so that MSDS are available on the public internet, which is what you eventually to do. If you use a double tms pointing to the same database where a single server is public you anyway compromising server tms to the public internet from the info you get would be the same no matter which tms server you connect to because of the shared db. The c20s must be added in tms as well (but not accessible by the MSDS if it is a system of soho) in order to obtain the authorization to access the directories that you set on the system. But there is no need to be very complex, as long as the endpoints can reach the tms of the internet server.

  / Magnus

  Sent by Cisco Support technique iPhone App

• 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.

• iTunes U registration does not work after last update Apple

  When I turn the key to the registration, he said still schooling off the power.  If I close iTunes you and reopen the course registration switch is off again.  This prevents the students to join and view the course.  It was working fine until the last Apple update.

  

  May have already checked this, but if you type 'Course settings', is your course session? If so, as the end date has passed, I suggest you move the end date for the future, and then try to change your registration again.

• Cost of iTunes on the credit card registration

  Hello

  You want to ask, while creating a new appleid on itunes, is it normal that it will charge $1.00 during registration because he says that will be done free of charge, but I got the message from my credit card that apple charged $1.00.

  Why? can someone please explain.

  Thank you

  See on the payment card's authorization in the iTunes Store - Apple Support. Some card companies to deal with these requests as a transaction complete only to remove it later.

  TT2