VCS FindMe vs TMS FindMe

Similar Questions

• Do we need to purchase the license to upgrade the VCS, VCSe and TMS?

  Hello

  We need to get a new license when upgraded version of VCS, VCSe and TMS?

  Hi Kelvin,

  xxx. OVA files are package files to deploy the VCS on virtualize platforms.

  Release key are required to upgrade the VCS for major updates. for p. ex. upgrade of x 6 x 7 software version worm.

  However for improvements minor as x7.2 to x7.2.2 these are the released hotfix version or bux fixes release and you don't need a license for this upgrade.

  in any case if you your devices are less covered by valid contract you can get the license key anytime just contact cisco license team on "[email protected] / * /" and they should be able to provide the necessary license.

  Rgds

  Alok

• Cannot add VCS Expressway to TMS

  I'm trying to add the VCS Highway to TMS.  When I add, TMS tries to connect via different protocols.  Then it errors and the screen refreshes quickly enough, and I don't see what happened.

  Where should I go to try to determine what happened?

  Suggestions to solve this problem?

  Thank you

  Ron

  Is this a new deployment? The SNMP on VCS is disabled by default.

  Check the setting of SNMP on the CV:

  System > SNMP

  SNMP mode: v3 more TMS support

  Try to add the VCS on MSDS once again and if you could share the screenshot on everything that happens when you add to the system.

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

• Cisco Telepresence Server/Cisco Telepresence driver/Cisco VCS - C / Cisco TMS license

  A big problem with the fact that I'm stuck is licensing. Really, I have tried many things to find the solution for it, but could not.

  I have actually made all of these servers (mentioned in the title) in my lab in preparation for the CCNP Collaboration certification at home.

  I am not able to complete some laboratories due to license issue (I guess). Y at - it an option to get the demo license for all these servers?

  I would be really greatfull if someone can suggest me the solution and/or the licenses required to complete all the stuff for my CCNP Collab tag.

  Best regards

  Dipak Singh

  TMS and VCS - C when installed without licenses, are automatically set mode of demonstration/test with some availability of license to test with. If needing a VCS-E, you will need to do to your account manager and they should be able to get you the time limited licenses good because I think that 90 days.

  Conductor Essentials is free, which means that you can install and get full functionality without the need of all licenses, but you are limited to 1 conference bridge and no grouping is allowed.

  TelePresence Server require licenses to function, once again, reaching out to your account manager for this.

  At the end of the day, you should reach to your account manager for all of this, as they should be able to help get timed license if you need.

• VCS upgrade through TMS to X7.1

  Hi outhere.

  With 'Software Manager' in article 13.2 of TMS, it seems to be a problem. Download S42700x7_1_0.tar.gz does not work.

  Is there a known problem?

  How can I upgrade without TMS VCS?

  I hope someone can help

  Martin

  You can upgrade the VCS directly by logging into the web page of VCS and will interview--> update and download the new file.

• Problems with VCS - C, VCS - E and TMS

  I hope someone can help me because I nearly pulled my hair with this problem.

  We have a VCS - C and VCS-E the two X7.2 running.  Our TMS runs 13.2.1.  We used it for several months with the 'transfer', which worked well.  Recently, I am currently having of Movi/Jabber clients authenticate via LDAP/AD, in addition to using local accounts (we have some vendors and partners who register through our infrastructure).

  I have gone through all the documentation and think I have it configured correctly, however, things work behind what I need them for.  Currently, a client who is on our internal network can sign up by using the credentials of the AD, but may NOT use local credentials.  Customers who are outside our network can register using the information of local identification, but NOT using their AD information.

  My configuration on the devices of VCS is:

  VCS - C

  Credentials of the default TextBox control

  Course credentials Check box

  By default, subarea treat as authenticated

  VCS-E

  Course credentials Check box

  SIP Proxy record tried Off and known Proxy Proxy at all.  Currently set to Off

  What I'm missing here as I'm more on the side things CTS and just try to learn the VCS Cisco Tandberg product?

  Thank you

  Allen

  Allen,

  When you enable the NTLM protocol challenges on your VCS - C, this means that only NTLM authentication will be used for devices that support NTLM, namely Movi 4.2 and later, video Jabber 4.3 and more more Jabber for iPad. Other devices that do not support NTLM authentication will use either the local database or LDAP authentication, depending on what you have set up on your VCS.

  Is there a particular reason why you want to use Digest authentication and NTLM for video devices Jabber?

  -Andreas

• VCS 7.2 + TMS 13.2.1 + version TMSPE Movi/Jabber compatibility

  Hi, if I switch to 7.2 VCS + TMS 13.2.1 + TMSPE.

  Jabber/Movi will work with version 4.1 and 4.2?

  This is essential information as Jabber (4.4) update is not possible right now on all PCs.

  Tom br.

  Yes.

  We have everything from 4.0.1 to 4.5 Movi on the system we use in the office, I work in and run with TMS 13.2.1 X7.2

• TMS does not COR of VCS Control collect

  Hi all

  Our TMS does not collect call Record of VCS control detail.

  (Reports > call detail record > Gatekeeper and VCS)

  He collected CDR properly until 2 August.

  But it does not collect no COR from 3 August until today even if many calls are housed.

  We have not changed configurations of MSDS and the VCS.

  What should I check on TMS and VCS?

  Any advice is welcome

  Best regards

  Kotaro Hashimoto

  As mentioned in Magnus, is a known issue with X7.2 for CDR.

  Symptom:

  TMS will not to CDR data type 'Gatekeeper and VCS' and the journal-web - public.txt in TMS log file will contain entries that are similar to the:

  ---> Tandberg.TMS.SystemAPI.OakPine.InvalidStateException: expected to find, but on the other hand find.

  at Tandberg.TMS.SystemAPI.OakPine.XMLFeedbackReader.AssumePositionedAtTag (XmlReader, String tag player)

  at Tandberg.TMS.SystemAPI.OakPine.XMLFeedbackReader.ProcessCall (XmlReader reader)

  at Tandberg.TMS.SystemAPI.OakPine.HttpFeedback.ProcessCallDisconnected (IXMLDoc txasDoc, RoutableSystem system)

  -End of the exception stack trace internal-

  TMS Version 13.2.1

  Background:

  Due to a change in the feedback XML VCS sends to TMS for events related to calls connection / disconnection, TMS is not able to correctly interpret the XML data provided by the VCS. For this reason, TMS is not capable of generating records CDR based on feedback data provided by the VCS.

  Workaround:

  Currently, there is no workaround known workaround for this issue when executing software X7.2 on VCS. X7.1 and earlier versions of the VCs are not affected by this problem.

  This will be fix with the next maintenance release, X7.2.1.

• TMS server and control the VCS

  Hello

  We have a customer's request if they can change the usename (admin) of control VCS in the TMS server. They don't want to purge the VCS of TMS server control, because they still need all the TMS Server historical reports. Basiaclly, they won't use the username: admin more to managing TMS server. They can create another account in the control of VCS with admnin rights, but how they change in the SMT server without purge from the TMS server.

  In the server of TMS, the VCS control connections tab, there is a place to change the password. but no place the username change.

  TMS software version: 13.1.2

  VCS Control version: 7.0.1

  Note: I noticed that this option is available on the server SMT version 14.2.

  Thank you

  Kind regards

  Chris

  Hello

  Using a different name that 'admin' to manage the VCS was introduced in TMS 14.1 (CSCuc88048). Not even bleed and add will help them, I'm afraid!

  Your client is upgraded if they want to use a different user name.

  Kind regards

  Kjetil

• Cisco VCS does not show the user account option

  Hi team,

  We have 7.2 VCS server control, I'm not able to see the option of user account under maintenance-Login accounts. Please advise.

  We don't have find me and TMS provisioing Extension service license, don't you think that's the reason.

  I just started my first deployment of VCS, MCU and TMS and I must add customer movie, cisco Jabber video for Ipad and integrtaion with CUCM. CUCM has some end points of polycom and C40 and C60.

  You precious advice will give me comfort during this deployment.

  Irfan

  BR

  Hello

  It's probably because that VCS runs in TMS PE commissioning mode, in which FindMe is managed by the portal user in TMS, meaning there is no need to set up the maintenance > logins on the VCS.

  Edit: You added information that you do not have the keys option Device Provisioning and FindMe. Because user names relate directly to FindMe, the absence of an option key FindMe would explain also unable to see maintenance > login accounts > user accounts.

  -Andreas

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

• Client Jabber Viceo registry for VCS/MSDS

  Hello

  I am trying to record a video jabber VCS or TMS customer but his does not work. Whenever I was

  "Bad username, domain and/or password". Check spelling and caps lock.

  Do not know why. Should what I do to register a customer with username and password? VCSC and VCSe are configured for access from inside and outside VCSe.

  Is there a guide for video Jabber clients?

  Best regards

  Jason

  Hi Jason!

  You need a starter pack of VCS-highway or TMS (license + Movi licenses) and a VCS (with the option of commissioning key device).

  As you write VCSe and c its more likely that you do not have the starter pack.

  She has need of configuration and user creation, so it would work not just out of the box.

  The recommended method is the TMSPE, you will find here the deployment guide:

  http://www.Cisco.com/en/us/docs/Telepresence/infrastructure/tmspe/Install_Guide/Cisco_TMSPE_Deployment_Guide_1-0.PDF

  If you have older versions of TMS/VCS you will use it (but I recommend you upgrade and use TMSPE!):

  http://www.Cisco.com/en/us/docs/Telepresence/infrastructure/TMS/config_guide/Cisco_TMS_Provisioning_Deployment_Guide_13-0.PDF

  In addition to this documentation Cisco for TMS, VCS and JabberVideo control.

  TMS:

  http://www.Cisco.com/en/us/products/ps11338/tsd_products_support_series_home.html

  VCS:

  http://www.Cisco.com/en/us/products/ps11337/tsd_products_support_series_home.html

  JabberVideo:

  http://www.Cisco.com/en/us/products/ps11328/tsd_products_support_series_home.html

  Jason: Please note the validations and define the thread if it's an answer!

• Video Jabber for TelePresence, VCS-E connection problem

  Hello

  I recently configured control VCS, VCS Expressway and TMS. Two VCS servers are software X7.2 and TMS is on 14.1.1 commissioning is configured between the VCS control and TMS, everything works OK internally and users can log in their Jabber client of telepresence video.

  When you try to connect via the highway-VCS I get the following question: "connection refused by the server. Try to connect again later"

  Area authentication is configured like this:

  VCS-Highway

  Sub-area by default: do not check the credentials

  Area Sefault: Do not check the credentials

  Crossing area: Do not check the credentials

  VCS-control

  Default subfield: treat as authenticated

  Area by default: credentials check

  Subarea: Credentials Check {area which movi users register to regex function}

  Crossing area: Do not check the credentials

  Search the rules between the two VCS game [email protected] / * / OK.

  The only port of the restrictions in place here are between the VCS control and VCS Expressway, outgoing ports open to the highway of the SANCTION.

  It seems to me that there is a connection problem, as opposed to an authentication problem. also, do I need to configure a SIP domain local VCS-Highway even if I try to proxy, registration to the VCS control.

  Would be appreciated if someone can verify my authentication area also...

  Thank you

  Simon,

  to do this, you re normally the area on VCS - C as "check credentials.

  If you want to proxy of VCS VCS-C-E records, you should not add the SIP domain name to the VCS-E.

  "Rejected by the login server" sounds weird in this case, however, could you share what you use for this deployment, the SIP domain name so that we can verify that your DNS SRV records are fine?

  -Andreas

• VCS StarerPack + MSD - reports

  Hello

  Customer a VCS Starter Pack + TMS for the management.

  I know that VCS Starter Pack more than TMS does not support the report files. He don't suport. not all reports of type or kind of reports?

  Custome really want to get TMS reports, what can I do to fix this?

  Thank you

  I never tried to add a starter pack to TMS, just out of curiosity, have you tried it?

  I would say that it needs to be upgraded to a full VCS - E + Movi to do this.

  (at least the documentation given).

  If he has managed in TMS end points at least the call Info

  but you will not have the movi stats (which are not so good in the TMS standard reports in any case)

  and anything else related to the VCS-CDRs.