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

Tags: Cisco Support

Similar Questions

  • Meeting scheduled for the TMS OBTP disconnect active calls

    Customers start ad-hoc calls because they cannot initially connect to a BBFRR meeting. The call is interrupted when the scheduled start time of hits. The client must then select the BBFRR to resume the session. I prevent the client to be disconnected?

    Sent by Cisco Support technique iPad App

    You cannot prevent MSDS disconnecting ad hoc calls regular calls start. Regular calls always have priority.

    Kind regards

    Kjetil

  • schedule meetings with the TMS and CTManager on the same endpoint

    Hello everyone

    I explain my problem, we have a CUCM with CTManager to plan meetings of the CTS, we have 2 VCS with a TMS to plan meetings of TC endpoints also.
    Our TC end points are saved in venture capital using H323, recorded in CUCM using SIP and exchange of email to can program using the CTManager. And TC endpoints are supplied by our TMS.

    As endpoints of TC may appeal to the endpoints CTS sometimes we have meetings planned between TC and CTS endpoints in the CTManager, but if schedule us a meeting by using the TMS, meetings of CTManager disappear and endpoint show TMS meetings, if we do a resynchronization of the electronic mail room in the CTManager We can see again in the meetings of CTManager in the touchscreen.

    We tried not to allow bookings for this endpoint of TC in the TMS, but later there is no way to schedule a meeting for this endpoint, even using the external call.

    You know any workaround solution to activate the two calendar options running on the same endpoint without removing the CTManager meetings? We don't need the BBFRR for the TMS meetings, only for meetings of the MLC.

    Best regards

    Hello

    Disabling power of the TMS write calendars 'Meetings' on managed systems is not supported. If an endpoint is added to the TMS, TMS assumed that endpoint is not used in another system of planning (such as CTS - man) and could replace any parameter that depends on the other system of planning.

    Kind regards
    Kjetil

  • Integration of TMS/TMSXE/conductor and Exchange

    Just installed new TMS/TMSXE/conductor for a customer and the initial test was OK but have a question.

    When TMSXE sends the notification to inviting him with the information that the meeting has been scheduled and information to others to call for the meeting, is there a way for TMSXE to also send information to people who have been invited as well?

    The client thinks it would be a pain to make the cut and past in humans invite you again

    If there is somewhere in the documentation that I missed, plase let me know.

    Thank you.

    TMS will not send e-mail confirmation of booking to anyone else that the person who at the request of the Conference.  By the TMSXE user's Guide, the Scheduler will send the e-mail confirmation for guests, or paste its content in the original meeting invitation.

  • Replace the TMS device

    Hi all

    I only appliance TMS with VCS and TMSagents (applications MOVI), then my TMS has error and had to be replaced by a new.

    is there any procedure to do this replacement for the TMS have TMSagents with VCS to ensure that replication will not be problem. Sorry, I just worriying on replication to be failed.

    because I have a large number of users MOVI.

    Thank you all

    Hello Kalinda

    What kind of error you see on the server of TMS? Maybe the ist possible to fix it?

    Before you replace your server TMS device, you need schedule downtime for maintenance.

    You should back up your sql database and the agent MSDS database. Then install the new TMS server with the corresponding version of the former and restore and backup agent MSDS database. You can then enable replication again.

    Keep in mind that the TMS appliance server is EOL and EOS, but also you can be able to take advantage of the Cisco migration program.

    Please visit this link:

    http://www.Cisco.com/en/us/prod/collateral/ps7060/ps11305/ps11316/ps11338/end_of_life_notice_c51-683062.html

    Concerning

    Rafal

  • Instant schedule in the version of the firmware change 8

    Since the 8.0.4, update I get the following emails every day at midnight that come from the table itself:

    ---

    event: 8.3.65
    time: Thu Sep 3 00:00:00 2015

    Free space is the threshold of 15% for pool HybridPool. Default snapshot schedule runs with max - keep set to 1.
    ---

    I have not any planning defined snapshot (do not have). Research in the eql newspapers, I see it says TI scanned X number of volumes and 0 photos.

    Is there a way to stop this new default calendar? I can't find what it defined anywhere or even place to stop these messages.

    Thank you

    Hello

    The default snapshot process runs on volumes with snapshot reserve, but have some snapshots.  So if you set the instant reservation on the volume to zero (0) it will not try to create a snapshot.

    Moreover, the CLI group, you can change the time, see the State or turn this feature off.

    GrpName > grpparams by default-snapshot-sched?

    Disable - disables the snapshot grid by default.

    Enable - enables the snapshot planning by default.

    Show - displays the current values for snapshot planning by default.

    start-time - value start time of the default schedule of the snapshot.

    If you use no clichés defining instant reserve to zero will also return the pool area.

    Kind regards

    Don

  • Adding the Polycom HDX to the TMS system

    How can I add a Polycom HDX system in TMS to manage?  What, if any configuration on the Polycom system must be made, or in the TMS?  Can't seem to find any documentation about it.

    http://www.Cisco.com/en/us/docs/Telepresence/infrastructure/TMS/interoperability/Cisco_TMS_Product_Support.PDF

  • Trying to link my VCS to my TMS, but I get no response VCs https in the TMS

    Hello

    I'm trying to get my MSD to talk to my VCS, but whenever I try to get the two to talk to each other. In my TMS, it said "no https response" of the VCS. I know that HTTPS is enabled in my VCS, what else could be the problem?

    Do you have a hostname on your VCS? DNS is able to resolve the domain your RESUME FULL name?

    Please, try the following on your TMS:

    (1) in the TMS Server RDP
    (2) open Administrative Tools > local security policy
    3) go to security settings > local policies > Security Options > System cryptography: Use FIPS compatible algorithms for encryption, hashing, and signing.
    If this option is enabled, please disable it and then repeat the test.

  • Problem with the commissioning of Web check-in and ASK when swicht to the TMS Provisioning extend mode

    Hi, I need help please, because I have no contract and I cannot open a TAC case.

    I have the following two issues:

    1. when I do the tms extension preparation mode switch as stop working sip calls, I get the following error of internal and internet scenarios for my internal network:

    VCS-e when the call is the Internet to the internal network

    2013-09 - 05T 11: 50:38 - 04:30

    "" "" "" "TVCS: event = 'Search is complete" reason ="authorization not valid - insufficient privilege" Service = "H323" type-aliases-Src ="E164" CBC-alias = '7449"Dst-alias-type ="H323"Dst-alias ="anthony_accardi"call-number ="1a069dfa-1647-11e3-86f9-0010f328943a"Tag ="1a069f44-1647-11e3-b22f-0010f328943a"detail ="found: fake, searchtype:ARQ"Level ="1"elements UTCTime = '2013-09-05 16:20:38, 670"

    VCS - c when the call is internal network to the Internet:

    2013-09 - 05T 11: 53:31 - 04:30

    "" "" "" "TVCS: event = 'Search is complete" reason ="prohibited" Service = "H323" type-aliases-Src ="E164" CBC-alias = '7429"Dst-alias-type ="H323"Dst-alias ="vianyfel_cordaro"call-number ="812a5198-1647-11e3-ba89-0010f325da04"Tag ="812a52e2-1647-11e3-93c9-0010f325da04"detail ="found: fake, searchtype:ARQ"Level ="1"elements UTCTime = '2013-09-05 16:23:31, 687"

    2013-09 - 05T 11: 53:31 - 04:30

    "" "" "TVCS: Event = 'research has attempted" Service ="H323" CBC-alias-type = "E164" CBC-alias ='7429"Dst-alias-type ="H323"Dst-alias ="vianyfel_cordaro"call-number ="812a5198-1647-11e3-ba89-0010f325da04"Tag ='812a52e2-1647-11e3-93c9-0010f325da04" detail = "searchtype:ARQ" Level = "1" elements UTCTime ='2013-09-05 16:23:31, 680"

    2013-09 - 05T 11: 53:23 - 04:30

    "" "" "" "TVCS: event = 'Search is complete" reason ="prohibited" Service = "H323" type-aliases-Src ="E164" CBC-alias = '7429"Dst-alias-type ="H323"Dst-alias ="vianyfel_cordaro"call-number ="7c9181c4-1647-11e3-bda8-0010f325da04"Tag ="7c918304-1647-11e3-865b-0010f325da04"detail ="found: fake, searchtype:ARQ"Level ="1"elements UTCTime = '2013-09-05 16:23:23, 974"

    BUT WHEN THE MODE IS AGENT LEGACY TMS ALL THE CALL WORKS FINE

    2 when I switch I can tms mode of preparation I can do internal network equipment supply but not from the outside and this worries me more is the jabber that being Internet I get the following error:

    013 09 - 05 T 11: 07:42 - 04:30

    "" "" TVCS: elements UTCTime = '2013-09-05 15:37:42, 263"Module ="network.sip"Level = 'INFO': Src - ip ="192.168.0.252"Src-port ="25084"detail = 'receive the Request OPTIONS = method, Request-URI = sip: 192.168.0.250:7001; transport = tls, [email protected] / * /"

    2013-09 - 05T 11: 07:42 - 04:30

    "" TVCS: elements UTCTime = '2013-09-05 15:37:42, 261"Module ="network.sip"Level ="DEBUG": Dst - ip ="192.168.0.252"Dst-port ="25084"
    SIPMSG:
    | SIP/2.0 401 Unauthorized
    Via: SIP/2.0/TLS 192.168.0.252:5061; branch = z9hG4bK4de281330ed1277914e57a4bb98ac81416134; received = 192.168.0.252; rport = 25084
    Call ID: [email protected]/ * /.
    CSeq: 38570 OPTIONS
    Starting at: ; tag = 21e96c96b3f9a439
    To: ; tag = ba0e03ca2f6b3957
    Server: TANDBERG/4120 (X7.2.1)
    WWW-Authenticate: Digest realm = "TraversalZone", nonce = "b40cb8278b4a11da992154324161d566d2b57bac3d83c5c518c4528c790d", opaque = "AQAAAN1NC9IHdFS3kNJ3Q6UX2JiBXhut", stale = FALSE, algorithm = MD5, qop = "auth".
    Content-Length: 0

    |

    2013-09 - 05T 11: 07:42 - 04:30

    "" "" TVCS: elements UTCTime = '2013-09-05 15:37:42, 261"Module ="network.sip"Level = 'INFO': Dst - ip ="192.168.0.252"Dst-port ="25084"detail ="sending = 401, method = OPTIONS, To = sip response Code: 192.168.0.250:7001, [email protected] / * /"

    2013-09 - 05T 11: 07:42 - 04:30

    "" TVCS: elements UTCTime = '2013-09-05 15:37:42, 261"Module ="network.sip"Level ="DEBUG": Src - ip ="192.168.0.252"Src-port ="25084"
    SIPMSG:
    | Sip OPTIONS: 192.168.0.250:7001; transport = tls SIP/2.0
    Via: SIP/2.0/TLS 192.168.0.252:5061; branch = z9hG4bK4de281330ed1277914e57a4bb98ac81416134; received = 192.168.0.252; rport = 25084
    Call ID: [email protected]/ * /.
    CSeq: 38570 OPTIONS
    Starting at: ; tag = 21e96c96b3f9a439
    TO:
    Max-Forwards: 0
    User-Agent: TANDBERG/4120 (X7.2.1)
    Support: com.tandberg.vcs.resourceusage
    Content-Type: text/xml
    Content-Length: 250

    25075024960|

    2013-09 - 05T 11: 07:42 - 04:30

    "" "" TVCS: elements UTCTime = '2013-09-05 15:37:42, 261"Module ="network.sip"Level = 'INFO': Src - ip ="192.168.0.252"Src-port ="25084"detail = 'receive the Request OPTIONS = method, Request-URI = sip: 192.168.0.250:7001; transport = tls, [email protected] / * /"

    2013-09 - 05T 11: 07:36 - 04:30

    "" "" "TVCS: elements UTCTime = '2013-09-05 15:37:36, 757" Module ="network.tcp" Level = "DEBUG": Src - ip = "10.10.10.1" Src-port ="10191" Dst - ip = "10.10.10.10" Dst-port ='5060"detail = 'TCP connection is closed"

    2013-09 - 05T 11: 07:36 - 04:30

    "" TVCS: elements UTCTime = '2013-09-05 15:37:36, 641"Module ="network.sip"Level ="DEBUG": Dst - ip ="10.10.10.1"Dst-port ="10191"
    SIPMSG:
    | SIP/2.0 404 not found
    Via: SIP/2.0/TCP 201.210.111.54:2379; branch = z9hG4bK5fc6a3c5021e3557216ef01c2434fb00.1; received = 10.10.10.1; rport = 10191; DefaultZone = ingress-box
    Call ID: [email protected]/ * /.
    CSeq: 301 SUBSCRIBE
    From: <> [email protected] / * />; tag = 2991aa56d191ede3
    To: <> [email protected] / * />; tag = c4114db76ace49d8
    Server: TANDBERG/4120 (X7.2.1)
    WARNING: 200.11.230.253:5060 399 'political response '.
    Content-Length: 0

    |

    2013-09 - 05T 11: 07:36 - 04:30

    "" "" TVCS: elements UTCTime = '2013-09-05 15:37:36, 641"Module ="network.sip"Level = 'INFO': Dst - ip ="10.10.10.1"Dst-port ="10191"detail = 'send = 404, method = SUBSCRIBE, To = sip response Code: [email protected] / * /, [email protected] / * /"

    2013-09 - 05T 11: 07:36 - 04:30

    "" TVCS: elements UTCTime = '2013-09-05 15:37:36, 638"Module ="network.sip"Level ="DEBUG": Src - ip ="10.10.10.1"Src-port ="10191"
    SIPMSG:
    | Sip SUBSCRIBE:[email protected] / * / SIP/2.0
    Via: SIP/2.0/TCP 201.210.111.54:2379; branch = z9hG4bK5fc6a3c5021e3557216ef01c2434fb00.1; received = 10.10.10.1; rport = 10191
    Call ID: [email protected]/ * /.
    CSeq: 301 SUBSCRIBE
    Contact: <> [email protected]/ * /: 2379; transport = tcp >
    From: <> [email protected] / * />; tag = 2991aa56d191ede3
    To: <> [email protected] / * />
    Max-Forwards: 70
    Directions:
    User-Agent: TANDBERG/774 (4.6.3.17194 PCS) - Windows
    Expires: 300
    Event: ua-profile;model=movi;vendor=tandberg.com;profile-type=user;version=4.6.3.17194;clientid="S-1-5-21-1078081533-484061587-725345543";connectivity=1
    Accept: application/pidf + xml
    Content-Length: 0

    The setup I have is:

    Configuration on VCS Expressway:

    TMS Agent Legacy mode

    Search rule:

    local area-no domain

    Any

    Any

    NO.

    Alias matching

    Regex

    (. +) @domain.com. *.

    Replace

    Continue

    LocalZone.GetDaylightChanges

    local area full URL

    Any

    Any

    NO.

    Alias matching

    Regex

    (. +) @domain.com. *.

    Leave

    Continue

    LocalZone.GetDaylightChanges

    Search of covered area rule

    Any

    Any

    NO.

    Any alias

    Continue

    TraversalZone

    Search for DNS zone rule

    Any

    AllZones

    NO.

    Alias matching

    Regex

    (?. *@%localdomains%.*$).*)

    Leave

    Continue

    DNSZone

    Transform

    Transform the alis destinations to URL

    ([^@]*)

    Regex

    Replace

    ------[email protected] / * /

    Presence PUA - on

    Presence server - off

    CONTROL VCS:

    TMS Extension commissioning of fashion

    Search rule

    local area-no domain

    Any

    Any

    NO.

    Alias matching

    Regex

    (. +) @domain.com. *.

    Replace

    Continue

    LocalZone.GetDaylightChanges

    local area full URL

    Any

    Any

    NO.

    Alias matching

    Regex

    (. +) @domain.com. *.

    Leave

    Continue

    LocalZone.GetDaylightChanges

    Search of covered area rule

    Any

    Any

    NO.

    Any alias

    Continue

    TraversalZone

    External IP address search rule

    Any

    Any

    NO.

    Any IP address

    Continue

    TraversalZone

    Transform

    Transform the alis destinations to URL

    ([^@]*)

    Regex

    Replace

    ------[email protected] / * /

    PUA - on

    presence server - on

    I do not have political appeal hace

    Please help me to see what I'm missing or what's wrong?

    Thankss

    Hello

    Ok. Are you saying that VCSe uses the IP address 10.10.10.10 in interface external, right? Of course, what the IP address of 200.x.x.x? It's your VCSe NAT IP address, right? What is this configured in VCSe?

    Well, reaally you have a problem of NAT. look at the SUBSCRIPTION message of jabber to VCSe:

    SIPMSG:

    | Sip SUBSCRIBE:[email protected] / * / SIP/2.0

    Via: SIP/2.0/TCP 201.210.116.201:3612; branch = z9hG4bK138dca6bf6cdd458588900dbaf7b45f4.1; received = 10.10.10.1; rport = 9368

    Call ID: [email protected]/ * /.

    CSeq: 301 SUBSCRIBE

    Contact:

    From: [email protected] / * />; tag = 1e82c817dc3224d5

    In: [email protected] / * />

    Max-Forwards: 70

    Directions:

    User-Agent: TANDBERG/774 (4.6.3.17194 PCS) - Windows

    Expires: 300

    Event: ua-profile;model=movi;vendor=tandberg.com;profile-type=user;version=4.6.3.17194;clientid="S-1-5-21-1078081533-484061587-725345543";connectivity=1

    Accept: application/pidf + xml

    Content-Length: 0

    Do you see? If the Red 192.168.41.205 IP address is the IP address of your router/nat, then you can come to the conclusion that your router is inspection/ALG, it puts its own IP address in the SIP headers. Your router/firewall device should not use any function ALG/inspection, otherwise you will have problems.

    I can say with great confidence, VCSe rejects the message SUBSCRIBE "404 not found" response because VCSE does not recognize this IP address in the field 'road', 192.168.41.205.

    In addition, the configuration of your NAT is not recommended. First, you use the port-based NAT (PAT), in fact, you must use a NAT. Second, when your NAT firewall allows VCSe, the source address is 10.10.10.1, which means that your firewall is NATing the source address and destination address not only. This type of NAT, it is not recommended for h.323/SIP applications.

    Well, don't be angry with me, I try to help, but I need to say, your deployment VCSe is almost completely false, there are a lot of blind spots.

    I suggest reviewing and reconfigure your deployment following this guide:

    http://www.Cisco.com/en/us/docs/Telepresence/infrastructure/VCs/config_guide/Cisco_VCS_Basic_Configuration_Control_with_Expressway_Deployment_Guide_X7-2.PDF

    I hope this helps.

    Concerning

    Paulo Souza

    My answer was helpful? Please note the useful answers and do not forget to mark questions resolved as "responded."

  • Allow outgoing SIP URI dial on the TMS system Type: room

    Hello

    I ve added a VC-end point unsupported to the TMS with system Type: room.

    If I check the planning parameters on MSDS for this endpoint, I see that I can only plan entering, but not outgoing calls.

    We´re with the help of BBFRR and if I book this endpoint in a Multipoint meeting, I get an error of TMS routing, because the outgoing call missing clearances characteristic.

    Is there a way to activate the planning coming out for this type of endpoint?

    Is it possible to configure the device manually type for example in the MXP880 to get the outbound features?

    Is there maybe a flag in the comic book, were I can define the type of device manually?

    Thank you

    Tino

    System of 'room' type is intended for endpoints that TMS does not support, but which can be saved to the guardian or register SIP (and therefore be composed by any other endpoints). MSD cannot control endpoint, it cannot force the end point to dial a number to someone, but logical routing TMS allows incoming calls, because it assumes that the doorman / SIP registrar can route calls to it.

    Makes sense?

  • Reports on the TMS - network packet loss

    Hello world

    I'm seeing packet loss reports in TMS, but there is no info here.

    My network is: VCS 7.0.2 movi, c20 and ex60 registered (SIP) as well as a TMS 13.1.2.

    The vcs is a starter pack and the TMS is the demo version. I first registered endpoint of the vcs and then added the TMS to the network. I have the endpoints addition and vcs to TMS. In TMS, I see the endpoints and the news on their topic, but unfortunately no information in the report of packet loss. I made a call between movi and c20 with packet loss, but no info has been shown in the report.

    I am very new to the TMS, and I wonder if there is something I should be doing in order to make endpoints send info packet loss to TMS.

    I sshed in endpoints and I can see the info on packet loss and jitter through the api.

    Described above is my test network on which I can make prety much all about. I also have the same problem (this time with EX60 endpoints, control VCS and TMS) on a network of clients and on this network that I really need this job.

    Any help would be appreciated. Form what I read end points to send this info by HTTP to MSDS. Am I wrong?

    Thank you for your help.

    Hello

    Endpoint to send your comments to tms on http Yes. I'm not at the office and this cannot be verified at the moment, but I don't know if devices running software like c-series and ex support tc this packetloss reports, I know the MXP legacy for this. If anyone can check it out that would be great. If this isn't the case, I will check it tomorrow.

    At least, you can check that endpoints send your comments to the tms at all looking at the system in the browser tab newspapers.

    Check the trap logs. If you see connect and disconnect traps here, feedback should work.

    /Magnus

    Sent by Cisco Support technique iPhone App

  • Provisioning of the TMS - the model schema question

    Hello

    I have read the deployment of TMSPE and tried to find the TMS Provisioning model for new Movi 4.4 schema, however, I could not find anything of cisco.com.

    Please help me where I can download the movi and schema of the model from the other end?

    Thank you

    Hello

    This model should be included in the bundle of jabber, when you download jabber 4.4.

    Sent by Cisco Support technique iPhone App

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

  • EX90 Point endpoint will not receive the TMS directories

    We have an EX90 which is implemented through TMS. Systems can be sent and the EX90 can be configured through TMS. However, the EX90 does not display the directories assigned in the Directory tab. When you view the config directory via the Web of EX90s interface server, all the information seems to be correctly put into service through TMS. Any help would be greatly appreciated.

    Thank you

    Kyle

    Is it maybe a firewall between endpoint and the TMS that stops at the request of endpoint and makes worse them TMS telephone directory?  Or it is set to 'https' when only "http" is available?

    You can do a quick test of connectivity connecting to CLI of the endpont as a 'root' via telnet/ssh and requesting the directory:

    curl /tms/public/external/phonebook/phonebookservice.asmx" rel="nofollow">http:///tms/public/external/phonebook/phonebookservice.asmx

    where is the IP address or the host name of your server TMS.

    You should receive some HTML if you have access, or a timeout / cannot connect error if you do not.

    Wayne

    --

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

  • TMS, VCS and Jabbber "impossible to connect to the TMS on the VCS agent".

    Dear,

    We have Cisco TMS, VCSC and jabber deployment, we did before commissioning the VCSC and TMS and jabber worked well, but after the upgrade the VCSC v7.2 to jabber version 8.2 has stopped working and I can not connect more and when I go to the TMS and connect to the VCS I get "unable to connect to the TMS on the VCS agent" Please notify

    What TMS version do you use?  And you are using Extension of provisioning of the TMS (TMSPE)?

    Looks like you are using TMS Agent Legacy, which has been supported in VCS X7.2 and has since been removed from X8.1.  You will need to migrate to TMSPE and very probably upgrade your server TMS as well if you do not meet the minimum version.

    Cisco TMSPE 1.0 Deployment Guide

    Here's the guide deployment for TMSPE 1.0, there are newer versions, but 1.0 is one that you want to migrate from legacy Agent TMS.  Once installed and migrate your data, you can then go to the most recent version, which is 1.4 (see below).

    Cisco TMSPE with VCS 1.4 Deployment Guide

Maybe you are looking for