AD authentication environment VCSe, VCSC and TMS

Similar Questions

• How to take backup for VCSC, VCSE, MCU and TMS. I'm new in the world of video. A brief step by step would be appreciated

  How to take backup for VCSC, VCSE, MCU and TMS. I'm new in the world of video. A brief step by step would be appreciated.

  You can back up each server by following these steps:

  For VCS, see "Backup and recovery of data from VCS" section in the Cisco VCS Administrator Guide X8.5, page 340.

  For MCU, see "upgrade and save the MCU" section in the Cisco Telepresence MCU series online help 4.5, page 212.

  For MSDS, see back up and restore SQL Server databases you will back up the database of TMS 'tmsng' of the SQL Server itself.  It could either be hosted locally on the TMS server if you have installed TMS with the default settings, or an external user provided SQL server.

• VCSC and VCSe

  I'm very confused on the VCSC and VCSe licenses and right. I need to launch a VCSe but I can't figure out how. Do I need an option key to activate the VCSC to VCSe? If so, what is the reference for this key?

  Thanks for your help!

  Installing VCS database (common to both), but when you order order you usually like a VCS - C or VCS-E.

  Reference to a VCS-E VM is R-VMVCS-EXPWY-K9.  This will give you the keys of the option to turn your basic VCS install in a VCS-E license.

  All references to products of VCS can be found here: http://www.cisco.com/c/en/us/products/collateral/unified-communications/telepresence-video-communication-server-vcs/data_sheet_c78-626491.html

• 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

• Problem recording movi to VCSe (VCSC work)

  Hello

  for some reason any Jabber client video are not able to log on to VCSe. If they are in the office and connect to the VCSC his work.

  Deployment:

  VCS: 7.2.2

  TMSPE: 14.2

  VCSC is joined to the domain, so people should be able to login with LDAP credentials. Since a few days we have changed an OU for users in AD. I resynced the TMS users. In VCSC my thought is that I have nothing to do, right? I do not know its function, change OR cause the customer movi is not som uch in use.

  I started track of debugging on VCSe registration go external with movi (IP addresses and names have been changed):

  SIPMSG:

  | SIP SUBSCRIBE:@domain.comSIP/2.0

  Via: SIP/2.0/TLS 192.168.100.10:3157; branch = z9hG4bK06fbfdf1d928fdea44551eb01444f279.1; received = 78.51.4.182; = 45938 rport

  Call ID: [email protected]/ * /.

  CSeq: 201 SUBSCRIBE

  Contact: <> @192.168.100.10:3157; transport = tls >

  From: <> @domain.com >; tag = ff9e0e9142437b34

  To: <> [email protected] / * />

  Max-Forwards: 70

  Directions:

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

  Expires: 300

  Event: ua-profile;model=movi;vendor=tandberg.com;profile-type=user;version=4.5.7.16762;clientid="S-1-5-21-176747291-1711663684-1688638919";connectivity=1

  Accept: application/pidf + xml

  Content-Length: 0

  SIPMSG:

  | SIP/2.0 404 not found

  Via: SIP/2.0/TLS 192.168.100.10:3157; branch = z9hG4bK06fbfdf1d928fdea44551eb01444f279.1; received = 78.51.4.182; rport = 45938; DefaultZone = ingress-box

  Call ID: [email protected]/ * /.

  CSeq: 201 SUBSCRIBE

  From: <> @domain.com >; tag = ff9e0e9142437b34

  To: <> [email protected] / * />; tag = a9bdf7d526c0cb56

  Server: TANDBERG/4120 (X7.2.2)

  WARNING: 79.34.34.123:5061 399 'political response '.

  Content-Length: 0

  So we have a 404 not found error, but why and what is not found, the user who tried to connect? For some reason, it seems that demand is not going through VCSe VCSC, it is my feeling?

  Auth area is as follows:

  VCSe:

  DZ: do not check the credentials

  TZ: do not check the credentials, accept records submitted by proxy: refuse

  DSZ: do not check the credentials, registration: refuse

  VCSC:

  DZ: verify the credentials

  TZ: verify the credentials, accept records sent by proxy: enable

  DSZ: verify the credentials, registration: enable

  I also implemented a CPL on VCSe (not on the VCSC) but I have disabled also the policy tried it unsuccessfully with so this should not be the problem.

  I tested a few other constelattion without success. :-( Maybe someone has an idea of what I can test. What is a firewall issue?

  Concerning

  Thorsten

  Hello

  Could check you if the 'Record SIP proxy Mode' setting is on "Known Proxy" only on Hwy VCS? You will find this SIP configuration setting.

  This is a required parameter for allow VCSe work as a proxy SIP for registration. It is not enough to define 'Recording proxy Acept' control VCS. In general, you should have this record transmitted by proxy configuration:

  

  If you don't want to use the proxy record but jabbers on the internet for you sign up directly for VCSe, you must disable the Save proxy functionality and create the SIP domain in VCS Expressway. It would be something like this:

  

  Try this.

  Paulo Souza

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

• Integration of CUCM, CTS and TMS

  We currently have a 8.6/CTS-Man/CTMS CUCM environment for our telepresence system.  All systems are CTS only.  Currently, connect us to a Tandberg system via Server CUBE/VCS/telepresence.

  We are looking at the possibility of integrating the two systems together.  This would involve decommissioning our CTS-man and using their existing planning TMS.  Networks would be open to each other so that they didn't cross highway of CUBE/VCS.

  Can someone tell me please to some documents on the integration of the TMS with our CUCM for planning?

  Furthermore, is it possible to have a single MSDS to perform the planning on the two CUCM registered CTS and saved VCS Tandberg endpoints end points, as well as to perform planning tasks for Community trade marks and MSE8000/telepresence Server?

  Thank you

  Hi Nick

  It is a very good question, and the bellows are drawn from the responses on the features that each product can provide you (CTS - Man and TMS) however as we know the TP Cisco world is changing and moving quickly if the bellows has been updated / changed and can someone comment on this topic will be great for us

  Meetings 1-booking

  TMS:

  -adhoc and meetings,

  -3rd-party endpoints reservation.

  -Ms Exchange, Domino, and API

  CTS - Man:

  -mainly used for endpoints STC booking

  -You can book and include cisco webex

  -Ms Exchange, domino and API

  2 features

  TMS:

  -End suppliers Multi points

  -Telephone directories

  -planning of conf

  -management endpoints (monitoring, Reporting, strong alerts... etc)

  -commissioning

  -integration with 3rd party such as Ms exchange

  -"There is no button to push" for the endpoints of CTS (you can add CTS alis for TMS rooms and book it or add the E164 of the external endpoint CTS as a participant and not these means are a button to push the meeting!

  CTS-MAN

  -integration of calendar

  -Midware between CTS, CUCM system and society of calendaring system

  -provide 'a button to push' scheduled meetings

  -provide interoperability simplified such planning via Cisco MXE

  -Live English option and CTMS geographical selection

  for each of them can provide you with options and features and its depends on the needs of your business, you could keep both or just go with one, if you have endpoints of VCS I would say for sure to the TMS

  HTH

  Marwan

• I was looking in my information system; software environment; system drivers and I noticed that many have stopped status. How can I determine which are to be started? How can I start them?

  I was looking in my information system; software environment; system drivers and I noticed that many have stopped status.  How can I determine which are to be started?  How can I start them?

  Hello

  · Do you see a problem with your computer?

  You can check the links which has more information on the information system: Description of Windows XP system information (Msinfo32.exe) tool: http://support.microsoft.com/kb/308549

• Question about commissioning of the E20s - CUCM and TMS

  If we now run software CUCM 8.6.2 and 4.1 E20.  I played with CUCM and TMS supply by and a few questions.

  It seems that there are some features that can be set via the TMS models that cannot be resolved via CUCM (MTU, custom, etc commands).  Is it possible to apply these settings through TMS while having the unit registered in CUCM?

  Essentially, I want my call recording platform CUCM and control, but want to keep the granularity that TMS offers in terms of commissioning etc..  I expect the same problems with C-series, etc.

  Am I right in saying that, in order to get the E20 to join CUCM, I need to define the external Manager to "CUCM", and thus eliminate any possibility of TMS to manage? Otherwise, what is I could have managed by TMS and then set the SIP of the E20 to point to CUCM via templates in TMS?

  Any tips on that?

  Hello

  Having both TMS and CUCM to manage endpoints is not a good idea (yet). TMS and CUCM will return to each of the other toes with unpredictable results.

  With TMS 13.2, I understand that you should be able to import the CUCM in TMS and then find all systems registered to it and import these into TMS, however in this case TMS plan only systems conferences and will manage them not active (you can see status of the call as well).  13.2 TMS is not yet released, so that's what I said must be in this version.

  So basically now if you use CUCM, use CUCM provisioning and don't use TMS.  We focus on interactions with systems registered with CUCM TMS and it will be more developed on this in the future.  I recommend you check out the TMS13.2 release notes released to see if it is mentioned.

  Thank you

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

• Import and export directory for CUCM and TMS

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

  tms_not_supported.PNG

  

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

• VCSC and without VPN VCSe Jabber

  Can these two devices cause the same domain configured?

  Thank you

  Alex

  Yes, its possible.

• VCSE-VCSC-TMSPE-AD, always get 404 not found for connection movi

  Hi, Experts.

  Location:

  VCS-control: X7.2.1

  VCS-Expressway: X7.2.1

  TMSPE: 13.2.1

  RE: Windows 2K 3

  By VPN, movi user can connect to VCS-C(which integrated with AD, so user authentication in AD), but without a VPN, by VCS - E, movi user cannot connect.

  VCS - E a static NAT to a public IP address with all the necessary ports open.

  VCS - E have minimum configuration to factory default as below:

  1. name, IP address, DNS, NTP

  2. create the SIP domain, enable SIP

  3. create VCS - c TraversalZone, and h.323 and SIP connection was estalished, shown as green indicator

  4. create the link bandwidth needed across all areas

  5. create a rule to search for courses, the target value for any alias traversalzone

  6 political authentication of all areas the value "do not check references" defaultZone, defaultsubzone, traversalzone

  See below for logging I capture VCS Expressway, she always get back with 404 not found error message:

  2012 11-28 T 17: 22:00 + 08:00 vcse tvcs: elements UTCTime = "2012-11-28 09:22, 448" Module ="network.sip" Level = "INFO": Src - ip = "172.16.50.3" Src-port = "25000" detail = "receive the Request OPTIONS = method, Request-URI = sip: 172.16.5.10:7001; "transport = tls, [email protected]/ * / '.

  2012 11-28 T 17: 22:00 + 08:00 vcse tvcs: elements UTCTime = "2012-11-28 09:22, 448" Module ="network.sip" Level = "DEBUG": ip - Src = "172.16.50.3" Src-port "25000" = "

  SIPMSG:

  | Sip OPTIONS: 172.16.5.10:7001; transport = tls SIP/2.0

  Via: SIP/2.0/TLS 172.16.50.3:5061; branch = z9hG4bK560062cbd420650fbdcd1423acc049d649; received = 172.16.50.3; rport = 25000

  Call ID: [email protected]/ * /.

  CSeq: 34143 OPTIONS

  Starting at: ; tag = 0c3b86c51458f605

  TO:

  Max-Forwards: 0

  User-Agent: TANDBERG/4120 (X7.2.1)

  Support: com.tandberg.vcs.resourceusage

  Content-Type: text/xml

  Content-Length: 250

  25075025000|

  "2012 11-28 T 17: 22:00 + 08:00 vcse tvcs: elements UTCTime ="2012-11-28 09:22, 448"Module =" network.sip"Level ="INFO": Dst - ip ="172.16.50.3"Dst-port ="25000"detail =" send = 401, method = OPTIONS, To = sip response Code: 172.16.5.10:7001, [email protected]/ * / '.

  2012 11-28 T 17: 22:00 + 08:00 vcse tvcs: elements UTCTime = "2012-11-28 09:22, 449" Module ="network.sip" Level = "DEBUG": Dst - ip = "172.16.50.3" = "25000" Dst-port "

  SIPMSG:

  | SIP/2.0 401 Unauthorized

  Via: SIP/2.0/TLS 172.16.50.3:5061; branch = z9hG4bK560062cbd420650fbdcd1423acc049d649; received = 172.16.50.3; rport = 25000

  Call ID: [email protected]/ * /.

  CSeq: 34143 OPTIONS

  Starting at: ; tag = 0c3b86c51458f605

  To: ; tag = 7ea25e18118002bd

  Server: TANDBERG/4120 (X7.2.1)

  WWW-Authenticate: Digest realm = "TraversalZone", nonce = "b1863670c75e193fed666bb5e0b381b7081bccfd4f029bc392157553d58d", opaque = "AQAAAM/lI9sgrVIOAlyA49AKb1XNNSQG", stale = FALSE, algorithm = MD5, qop = "auth".

  Content-Length: 0

  |

  2012 11-28 T 17: 22:00 + 08:00 vcse tvcs: elements UTCTime = "2012-11-28 09:22, 452" Module ="network.sip" Level = "INFO": Src - ip = "172.16.50.3" Src-port = "25000" detail = "receive the Request OPTIONS = method, Request-URI = sip: 172.16.5.10:7001; "transport = tls, [email protected]/ * / '.

  2012 11-28 T 17: 22:00 + 08:00 vcse tvcs: elements UTCTime = "2012-11-28 09:22, 452" Module ="network.sip" Level = "DEBUG": ip - Src = "172.16.50.3" Src-port "25000" = "

  SIPMSG:

  | Sip OPTIONS: 172.16.5.10:7001; transport = tls SIP/2.0

  Via: SIP/2.0/TLS 172.16.50.3:5061; branch = z9hG4bK0543f31f3f612b0be1752d6785832d1a50; received = 172.16.50.3; rport = 25000

  Call ID: [email protected]/ * /.

  CSeq: 34144 OPTIONS

  Starting at: ; tag = 0c3b86c51458f605

  TO:

  Max-Forwards: 0

  User-Agent: TANDBERG/4120 (X7.2.1)

  Authorization: Digest nonce = "b1863670c75e193fed666bb5e0b381b7081bccfd4f029bc392157553d58d", realm = "TraversalZone", opaque = "AQAAAM/lI9sgrVIOAlyA49AKb1XNNSQG", algorithm = MD5, uri = "sip: 172.16.5.10:7001;" transport = tls", name of user ="exampleauth", response ="5424b23056e3408bb7c5057ca8921cba", qop is auth, cnonce ="32d6888de492c717c771f89e4b9931e3a4dd3090380a925b76349acf62b7", nc = 00000001

  Support: com.tandberg.vcs.resourceusage

  Content-Type: text/xml

  Content-Length: 250

  25075025000|

  2012 11-28 T 17: 22:00 + 08:00 vcse tvcs: elements UTCTime = "2012-11-28 09:22, 453" Module ="network.http" Level = "DEBUG": Message = "Request" method = "POST", URL ="http://127.0.0.1:9998 / identification/name/exampleauth information" Ref = "0x460b500".

  "2012 11-28 T 17: 22:00 + 08:00 vcse tvcs: elements UTCTime ="2012-11-28 09:22, 456"Module =" network.http"Level ="DEBUG": Message = 'Response' Src - ip ="127.0.0.1"Src-port ="9998"Dst - ip ="127.0.0.1"Dst-port = '45146' response =" 200 OK "ResponseTime ="0.003486"Ref ="0x460b500 ".

  "2012 11-28 T 17: 22:00 + 08:00 vcse tvcs: elements UTCTime ="2012-11-28 09:22, 456"Module =" network.ldap"Level ="INFO": detail =" credentials for authentication in identity directory: exampleauth.

  "2012 11-28 T 17: 22:00 + 08:00 vcse tvcs: elements UTCTime ="2012-11-28 09:22, 458"Module =" network.sip"Level ="INFO": Dst - ip ="172.16.50.3"Dst-port ="25000"detail =" send = 200, method = OPTIONS, To = sip response Code: 172.16.5.10:7001, [email protected]/ * / '.

  2012 11-28 T 17: 22:00 + 08:00 vcse tvcs: elements UTCTime = "2012-11-28 09:22, 458" Module ="network.sip" Level = "DEBUG": Dst - ip = "172.16.50.3" = "25000" Dst-port "

  SIPMSG:

  | SIP/2.0 200 OK

  Via: SIP/2.0/TLS 172.16.50.3:5061; branch = z9hG4bK0543f31f3f612b0be1752d6785832d1a50; received = 172.16.50.3; rport = 25000

  Call ID: [email protected]/ * /.

  CSeq: 34144 OPTIONS

  Starting at: ; tag = 0c3b86c51458f605

  To: ; tag = 2f5366fe32e2f0ee

  Server: TANDBERG/4120 (X7.2.1)

  Support: com.tandberg.vcs.resourceusage, path, outbound, gruu

  Content-Type: text/xml

  Content-Length: 250

  25075025000|

  "2012 11-28 T 17: 22:02 + 08:00 vcse tvcs: elements UTCTime =" 2012-11-28 09:22:02, 195"Module =" network.tcp "Level ="DEBUG": ip - Src ="101.85.21.125"Src-port ="51161"Dst - ip ="172.16.5.10"Dst-port ="5061"detail ="TCP connection ".

  2012 11-28 T 17: 22:02 + 08:00 vcse tvcs: elements UTCTime = "2012-11-28 09:22:02, 196" Module ="network.tcp" Level = "DEBUG": ip - Src = "101.85.21.125" Src-port = "51161" Dst - ip = "172.16.5.10" = "5061" detail = "TCP connection" Dst-port "

  "2012 11-28 T 17: 22:02 + 08:00 vcse tvcs: elements UTCTime ="2012-11-28 09:22:02, 277"Module =" network.sip"Level ="INFO": Src - ip ="101.85.21.125"Src-port = detail"51161"=" receive the = SUBSCRIBE Request method, Request-URI = sip:[email protected] / * /, [email protected]/ * / '.

  2012 11-28 T 17: 22:02 + 08:00 vcse tvcs: elements UTCTime = "2012-11-28 09:22:02, 277" Module ="network.sip" Level = "DEBUG": ip - Src = "101.85.21.125" Src-port "51161" = "

  SIPMSG:

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

  Via: SIP/2.0/TLS 192.168.1.3:51161; branch = z9hG4bKf60920d0f72bbac899bfab5b8e5e30c9.1; received = 101.85.21.125; rport = 51161

  Call ID: [email protected]/ * /.

  CSeq: 201 SUBSCRIBE

  Contact: <> [email protected]/ * /: 51161; transport = tls >

  From: <> [email protected] / * />; tag = c9331fde9f056be2

  To: <> [email protected] / * />

  Max-Forwards: 70

  Directions:

  User-Agent: TANDBERG/774 (MCX 4.5.7.16762) - Mac OS X

  Expires: 300

  Event: ua-profile;model=movi;vendor=tandberg.com;profile-type=user;version=4.5.7.16762;clientid="7B26CD64-18E7-5443-982A-DD2E496560D2";connectivity=1

  Accept: application/pidf + xml

  Content-Length: 0

  |

  "2012 11-28 T 17: 22:02 + 08:00 vcse tvcs: elements UTCTime ="2012-11-28 09:22:02, 282"Module =" network.sip"Level ="INFO": Dst - ip ="101.85.21.125"Dst-port ="51161"detail =" send = 404, method = SUBSCRIBE, To = sip response Code:[email protected] / * /, [email protected]/ * / '.

  2012 11-28 T 17: 22:02 + 08:00 vcse tvcs: elements UTCTime = "2012-11-28 09:22:02, 282" Module ="network.sip" Level = "DEBUG": Dst - ip = "101.85.21.125" Dst-port "51161" = "

  SIPMSG:

  | SIP/2.0 404 not found

  Via: SIP/2.0/TLS 192.168.1.3:51161; branch = z9hG4bKf60920d0f72bbac899bfab5b8e5e30c9.1; received = 101.85.21.125; rport = 51161; DefaultZone = ingress-box

  Call ID: [email protected]/ * /.

  CSeq: 201 SUBSCRIBE

  From: <> [email protected] / * />; tag = c9331fde9f056be2

  To: <> [email protected] / * />; tag = 709c4dfeda5f3666

  Server: TANDBERG/4120 (X7.2.1)

  WARNING: 172.16.5.10:5061 399 'political response '.

  Content-Length: 0

  |

  2012 11-28 T 17: 22:02 + 08:00 vcse tvcs: elements UTCTime = "2012-11-28 09:22:02, 295" Module ="network.tcp" Level = "DEBUG": ip - Src = "101.85.21.125" Src-port = "51161" Dst - ip = "172.16.5.10" Dst-port = '5061' = "TCP connection is closed" detail "

  Hello

  you mention that the VCS-E is behind a static NAT. The VCS-E has the option of two Network Interfaces key installed, and if this is the case, do you have properly enabled and configured the static NAT configuration on the VCS itself, on the system > IP page in the web interface of VCS?

  This option key is required when you deploy the VCS E behind a NAT, you can find more information on this in Appendix 4 of the following document:

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

• 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

• Environment of VB and its programme launch

  After a few months of correct behavior, an executable developed with Visual Basic version 6 (Windows XP SP 3 compatible) refuses the lauch, same thing for the environment Visual Basic itself. Restore the system to an earlier date has solved the problem (VB application works again, and the VB itself), BUT I'm back to the same problem after the first reboot!

  Thanks in advance for any advice!

  Hello Christine,.

  Thanks for posting your question on the Microsoft community.

  This question fits better to the developers on MSDN forums.

  I suggest you to ask your question on the MSDN forums.

  MSDN forum
  https://social.msdn.Microsoft.com/forums/en-us/home?Forum=vbgeneral

  Thank you

• Windows 7 was authentic until you restart and now it's not!

  I bought windows 7 not for long and put the product key and everything works perfectly fine... Until one day, my computer has been acting weird so I had to restart. and now it says that my windows 7 is not genuine. I tried to enter the key again but it tells me its not authentic.

  Guidelines-Microsoft North American Retail product refund:

  http://www.Microsoft.com/Mac/trial

  J W Stuart: http://www.pagestart.com