TMS Agent Legacy migration

Similar Questions

• How to check the MSDS 13.2 running MSD Agent (legacy mode) or TMS provisioning or extension of TMS provisioning services.

  Hello

  How to check the MSDS 13.2 running MSD Agent (legacy mode) or TMS provisioning or extension of TMS provisioning services.

  Kind regards

  Siva

  My TMS is strictly using Extension of Provisioning, because I am running 14.3.2 TMSPE is the only option for me, so I can't provide a screenshot.

  However check you by going to: administrative tools > Configuration > General settings, look for the commissioning Mode.

  That said, I suggest that you consider migrating to TMSPE if you have not already, that the recent version of TMS have removed TMS Agent legacy mode.  If you want to use the latest versions of TMS and take advantage of the features it provides, you will need to perform the migration, if not already done.

• Removing VCS of TMS and TMSPE migration problem

  We prepare to start using TMSPE, however it must first disable replication on all VCS via MSD MSD Agent.  There is a VCS that have failed has been deleted afterwards, but we cannot delete TMS because TMS Agent replication is enabled.  We cannot have the Agent MSDS tab to disable the replication because the VCS is offline (i.e. it was removed) - it just goes to the 'Connection' tab whenever I try.

  So, how can we migrate to TMSPE if TMS don't delete us the VCS in offline mode or at least turn Replication Agent MSDS for it?

  Hey Nick

  Try to run this SQL query:

  USE TMSNG

  UPDATE field_SystemField SET BolValue = 0 WHERE field_Field_Id = 1072

  UPDATE Cluster SET EnforceTMSAgentDataReplication = 0

  This should clear the replication on all VCs added to the TMS (even the zombie ones like the one you have), once it is executed, you can try to purge the VCS.

  / Magnus

• Error TMS agent Portal

  Hi all

  I have exactly the same problem as described in this discussion: tmspe-tms-aent-page.  If I try to connect to http://TMS/tmsagent/tmsportal (or https).  I get the error message "an error has occurred. ' Reload the page and try again.  See the attached file.

  With TMS 14.6.1 and TMSPE 1.4 installed on Windows 2008 R2 server standard edition server.

  TMS is running for a couple of months with this version very well. Recently, I've implemented CMR after conductor and new mm410v has been added to you video below. A model was created and applied to a group of users. This group has the authorization requested to the meeting of the book.

  I got the same error message when I click on the button "Edit CMR in the portal".

  If I try as http://tmsipaddress/api/v0/version suggested link I get a page not found error.

  Default Web site also has an HTTPS binding.

  I'm stuck because I am not able to solve problems more.

  Cisco TAC after webex session ask me follow up with Microsoft!

  Any suggestion or advice is welcome.

  Thanks in advance.

  Ahmed

  TMSPE working before trying to add CMR, or is this a new installation?

  Java has been updated recently? TMSPE 1.4 requires Java 7 update 51, I know that's not far from the version you use, but it is worth it to try the version that offers the deployment guide.

  It could also be that Windows is missing a required service pack, see tms-agent-ui - error message.

• Warning in VCS and TMS (inherited from TMS Agent mode)

  Hello.

  I have this massage in TMS and VCS system, how this fix?

  in TMS: #2057 - Configuration Warning - The VCS is running in a mode inherited from the officer of TMS; It is recommended to switch your system to use another mode.

  in VCS: the VCS is running in a mode inherited from the officer of TMS; It is recommended to switch your system to use another mode

  How to switch different mode?

  Thank you

  If you are not Provisioning - remove the key to implementation of the VCS.

  In the web interface, go to the maintenance, options keys, select the configuration key and press delete.

  (it might be helpful to take note of the key first, where you decide in the future that you want to install it again - but it can be retrieved otherwise if you lose, IE from the Cisco Licensing Portal).

  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

• TMSPE Dial Plan Configuration in TMS

  I work on the migration of TMS Agent legacy at TMSPE, and I noticed the following in the commissioning of TMS options:

  Note: Video Address Pattern and Device Address Pattern must be configured for  provisioning and FindMe to function properly.
  

  I am use to the legacy fill method only in the device URI to create the video address SIP that we use.  However, how can I go of this unique method of configuration to the new address TMSPE, and that each of the new address types are if they were separate or the same?

  Thank you

  Address of the video is the FindMe address, the address of device model is, well, just the address of the device; that is the address of JabberVideo (Movi) users. The address of video template is used only if you use FindMe, otherwise not.

  See: https://supportforums.cisco.com/thread/2179099?tstart=120

  /Jens

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

• Problema con el modo TMS provisioning Extension

  Hola, No tengo soporte por lo than no puedo open el contrato a caso en tac

  Tengo los back following problems:

  1 uando yo activo el modo TMS provisioning, me dejan funcionar las llamadas sip, estos his los erroresque me appears:

  VCS-E cuando el are the llamada desde Internet toward the Red international.

  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"

  In el VCS - C the llamada cuando es desde red Interna toward 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"

  Cuando el mod TMS Agent activated todo works correctamente esta

  2 Cuando cambio al modo TMS Provisioning yo puedo provisionar equipos desde red interna pero desde internet. Y lo mas than me floor are el jabber video, este are el error q appears:

  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

  Este are el modelo authenticacion as uso y por tanto esa manera config:

  

  Config en 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

  No tengo appeal policy

  Por favor ayudenem a worm as me falta?

  Gracias

  Hi, I do not read Spanish, but I read the newspapers.

  Why don't you use the domain "domain.com"? Could you change this to your own domain name?

  You call H323 to SIP? If you call of H323 and don't add not the domain (if you call SIP), you will not achieve this SIP unit, except if you add a search (or transformation) rule to add the field.

  Additionally, make sure that you have the possibility of the installed key (116341G 00) interoperability, and the interoperability that you allow users ("Registered only" or "On") on your VCS.

  Hope this helps,

  Arne

• Upgradeing TMS using TMSPE

  What is the process of upgrading of TMS which currently uses the TMSPE?  I know with TMS Agent Legacy, you had to Devil replication with VCS, but I'm not familiar with TMSPE at the moment and how to upgrade of MSDS.

  Simply upgrade the tms regularly according to the documentation. No need to turn off the mark.

  / Magnus

  Sent by Cisco Support technique iPhone App

• Interval synchronization and TMSPE

  The fact that the LDAP/time synchronization interval is static, TMS causes a lot of headaches for organizations that deploy quickly end points configured to their user base.  Only they that must wait for the nightly synchronization or manually connect to TMS and this kickoff, which does not fit well when dealing with many wish someday and strong demand.

  In the TMS Agent model there was formerly a SQL, stored procedure, you can use to trigger synchronization, is there a similar way to trigger by LDAP Sync program under the TMSPE model?

  Hi, Frédéric

  I asked about this and was told that is not possible in TMSPE that the interval is embedded in the code. I know that it was possible for the TMS Agent Legacy.

  I guess a feature request is the way to go in order to get this configurable setting.

  / Magnus

• PC VMware fusion migration agent: can I migrate to an external drive

  I'm evaluating merger 7 and try to migrate existing PC. Is there a way I can create a vmware file which I can move in a HARD drive rather than perform the migration on the network?

  Thank you

  Ravi

  ravi123201110141 wrote: he talks about the installation and use of "Vmware fusion migration Agent" to perform the migration. Is this different from "VMWare VCenter converter"

  While the two results in a P2V and share some code/software between then, however, they are different products.  The Agent of Migration of VMware Fusion is a limited subset of what VMware vCenter Converter Standalone is able to do.  You said in your OP ""is there a way I can create a vmware file that I can move in a HARD drive rather than perform the migration on the network?". VMware vCenter Converter Standalone is the way to go if that's what you want to do.  Personally I would never, under any circumstances use the Agent of Migration of VMware Fusion and instead use other disk imaging software then manually create a Virtual Machine VMware vCenter Converter Standalone is the way to go otherwise.

• TMSPE migration failed with "deny access".

  Hello.  Im running into the problem using the TMSPE migration tool.  IM receiving "Unable to export data from OpenDS.

  Here's what I see from the windows of command:

  at java.lang.Thread.run (Unknown Source) [na: 1.7.0_06]
  Caused by: com.cisco.ts.mgmt.migrationtool.exception.LdifExportFailedException:
  LDIF export failed: access denied.
  Access is denied.
  Access is denied.
  Access is denied.
  Access is denied.
  Access is denied.
  Access is denied.
  Access is denied.

  to com.cisco.ts.mgmt.migrationtool.ldif.LdifExporterImpl$ 1.call (LdifExpo
  ~[migration-tool-1.0.159.jar:na rterImpl.java:121)]
  to com.cisco.ts.mgmt.migrationtool.ldif.LdifExporterImpl$ 1.call (LdifExpo
  ~[migration-tool-1.0.159.jar:na rterImpl.java:93)]
  to java.util.concurrent.FutureTask$ Sync.innerRun (Unknown Source) [na: 1.7]
  .0_06]
  at java.util.concurrent.FutureTask.run (Unknown Source) [na: 1.7.0_06]
  ... 3 omitted common frameworks
  August 30, 2012 13:32:29 - impossible Migration

  The documentation says when meet this error msg, follow these steps:

  Corrective actions:

  1 see the log for more details

  2. check that sufficient memory for the parameters exportconnection OpenDS.

  3. check that the connection details for Cisco Agent Cisco TMS Legacy TMS are correct.

  4 re-run the migration tool.

  My question is what it means in the number of corrective actions 2 and 3?
  I re - run the migration tool multiple times without a bit of luck.  In addition, the legacy of Agent TMS works very well.

  Thank you in advance for any advice.

  Hello

  Open the command line as an administrator (as run as administrator).

  CD to the Directory migration tool. C:\Program files\tandberg\tms\provisioning extension\migration tool

  Run the migration tool.bat of the cmd as administrator. Should solve the problem.

  / Magnus

  Sent by Cisco Support technique iPhone App

• Error #1684957 connection error found in the TMSPE TMS

  Hi all

  In our system of VC network, there are several VCS with different software version, for example,

  VCS - A with s.w 7.1 formed a TMSPE with TMS s.w 13.2

  VCS - B with s.w 5.2 run the TMS with TMS agent mode.

  The problem is, for all the endpoints registered with VCS - B, there is an error (report

  Connection of the #1684957 TMS error error). Amounts confrimed have not change the endpoint configuration, and this error affects a type different from VC endpoint, included MXP, series C and series EX.

  In the TMSPE release notes, we are unable to find relatively to this error notice, what anyone face the same problem as well?

  Best regards

  Ben

  Hi Lai

  

  What is the ticket that you see on the systems? I do not understand what TMSPE has to do with this error mostly on MXP systems as you also experience this problem. Usually, when this error is raised there is a connection problem between the endpoint and the TMS, response point No. HTTP or answer No. SNMP or something like that. The system has the 'Idle' connection status when you see this post set on the system?

  As Jens says that you cannot run TMSPE with 5.2 (you can also not run simultaneously TMSPE and TMSAgent on the TMS even legacy).

  Please check the status of the connection of the endpoints affected, it could not have something to do with the configuration but rather something on the network that prevents the TMS to achieve systems.

  Please let me know if I am wrong here, but it seems to me that there is a connection problem and nothing to do with TMSPE. I might have misunderstood you so if I have, please provide more details, perhaps a screenshot?

  / Magnus

• TMS Provisioning question

  Hello

  My TMS version is 13.2, new facility.

  I tried to enable the agent TMS under administration-> configuration-> General-> tms tools enable agents. After all, I do not see any process under the status of the activity.

  "If I connect to VCS, under systems > Navigator, selecting the agent VCS and TMS tab, I see"

  Successfully connected to the TMS agent running on the VCS. "" but there is an error message "

  Unable to connect to the agent running locally on this server MSDS MSDS. »

  Any idea on this issue? Thank you

  Hi Curtis

  Since this is a new installation and you are running 13.2 I recommend you to install the tms extension provisioning. The tmsagent is the old model of provisioning.

  https://supportforums.Cisco.com/thread/2145898

  Follow this thread for the document and download links.

  / Magnus

  Sent by Cisco Support technique iPhone App