Deployment of VCS - E

Similar Questions

• Ask for help for deploying Cisco VCS EX60

  Hello

  First of all, I have a knowledge in voice and the field of video networks, I have a Cisco video conference server and a Cisco EX60 device, can someone guide me on how to successfully deploy over the internet? Basically what I do is video conference from one site to another site. I enjoy gladly of help from someone ~ I need to understand the basics so ~ thank you very much!

  Hello

  Manual of the bellows short and very good for people with a limited knowledge of telepresence.

  short links > cisco.com/go/cvd

  For you:

  http://www.Cisco.com/c/dam/en/us/TD/docs/solutions/CVD/Aug2013/CVD-H323VideoInterworkingUsingVCSDesignGuide-AUG13.PDF

  http://www.Cisco.com/c/dam/en/us/TD/docs/solutions/PA/Midmarket/video.PDF

  Another way > use the search in this community

  BR Oleksandr

• DNS records in the VCS - ARM deployment

  Hello team cisco,

  Regarding a deployment on VCS (control and Highway) - Mobile and remote access, I saw in the guides from cisco that there is some DNS records it should be implemented in your public DNS host and private, however, he is considered by our team work, this step may be omitted if we put the IP address directly. It would be posible or necesarely I have to configure DNS records?

  Respect of

  Bill

  Hi Jose,

  as I said in my previous comment, you must advertise the documents.

  Yes, you will need to announced records and SRV deployment of the e-highway.

  Thank you

• Question about the design of VCS-C/VCS-E

  Hello

  Customer has no DMZ. So, what are my options to configure a deployment of VCS-C/VCS-E?

  How is it I could reach the goal that VCSC and VCSe contact area of neighbor?

  Do I need to assign an internal IP address (without static nat) and LAN2 in also an IP address in-house with NAT static external IP LAN1.

  Prerequisite for which is 'Dual touch Option NIC', no?

  At the moment I have no double key Option of NIC, then the only way in my deployment is the DMZ preffered way, right? Or make me another option?

  Concerning

  Thorsten

  Well, in this case, you can have the VCS-E in public, VCS - C behind the firewall and an area between the two.

  You can increase the security nat'ing and with who use dual NICs on the VCS-E option.

  I also either turn off or at least to block SSH on VCS-E to the public.

  Deployment Guide:

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

  /Jens

• Understand the flow of appeal through VCS c/e

  Hey Geeks,

  I write this to understand "how to work things. Here's the design.

  I have a VCSC configured with the name of the domain example.com SIP (we have internal DNS server to resolve)

  I have a VCSe configured with the name of the cisco.com SIP domain (we have external DNS server to make globally routable)

  I create a link bw VCSC and VCSe course.

  How the call will flow between the Ep A and B Ep

  Scenario a.

  My Ep A is [email protected] / * / dials Ep B Jabber client (user) recorded on VCSe [email protected] / * /

  How call flows; I understand that the flow of the beginning IE Ex 90 will send a register message to VCSC etc etc.

  Scenario B:

  If Ep A [email protected] / * / call a 3rd party (distinct) = (inter appeal cases) End point ie [email protected] / * /

  How runs the call.

  Please excuse me for asking layman explanation:

  Thanks in advance

  Vikram

  Hi Vikram,

  First thing to note is in most of the customer scenario prefer same sip domain on highways and control so that they can avoid transform and simplify the numbering plan.

  Happens to your scenario.

  Scenario a.

  EP A VCS-contrl<--traversal-->VCS - Ex <--SIP--><--sip-->Ep B (points of termination assumptions made using the SIP protocol)

  EP began with the sending of a guest for VCS-cntrol SIP message, which gets transmitted to VCS - by VCS-cntrl exp, hope you're installation rules research properly on vcs control.

  VCS - exp send this appeal to Ep B and call connect. You can google for SIP call flow, so nothing different happens in this case.

  Scenario B

  EP A VCS-cntrl<--traversal-->VCS - Exp<-->public cloud<--SIP--><-->Ep B (dell.com)

  A DNS zone, which uses the dns configured on exp do query srv records to the external field like "dell.com" is now required to apply for external part VCS - exp

  in this scenario again Ep began with the sending of a message to the VCS-cntrl invitation gets sent to the SCV - exp rules-based research. VCS - exp begins looking for new address based on the rule of the research and since it does not find the URI ending with exp and "dell.com" starts to send query record srv for the domain "dell.com". DNS configured on exp in the SRV company A sends question and get an answer for this domain with the company B VCS - exp - ip address, and then vcs - exp in company A starting configuration of the call to the remote ip address.

  now in the present, you can have several scenarios and I recommend you consult the guide deployment for VCS-control and traversal solution VCS - exp.

  Rgds,

  Alok

• VCS Cisco control / Core Expressway interoperability

  Hello

  I have the fate of unmanageable endpoints on the internal network, functioning as a H323 IP address directly.
  In fact, we had regular meetings as the auto numbering unmanageable endpoint by H323 IP address directly.
  Unmanageable end points would not be registered in the VCS / CUCM.

  1. can I adjust the composition of Cisco driver auto & GST to endpoints VC not saved by its IP address (regular meeting VC > Auto call the IP address internal VC endpoints directly)?

  2. or should I deploy VCS / Expressway to consume the traversal lic. / RMS lic. from autodial URI translate be IP call? Can I just deploy the VCS - C / E motorway in order to reduce the lic. costs?

  You don't need a VCS-E for this.

  Just go to the plan of numbering - Setup and call to unknown IP addresses as Direct. The alternative would be to create a subzone with a membership rule with the IP of your endpoint. Depends on if you want to only allow the call to this particular or to any endpoint IP on your network endpoint.

• VCS Starter Pack in a datacenter (fixed Behinde NAT)

  Hi guys,.

  We have a server express telepresence VCS starter pack and it worked very well in our dataline E2 Office but now after moving to a data center there is a problem with saving a customer Movi of VCS on the Internet.

  The server installation is now this: VCS Starter pack firewall/Touter - Internet - Movi

  The VCS is connected to the local network (internal data center network with an interface and static is using a NAT to the Internet with a router)

  all ports are open in the firewall (incoming and outgoing)

  And here are the settings in the VCs:

  Default credentials - authentication - Check policy

  By default, subzone - authentication policy - threat as authenticated

  Also, here is the log of the attempt to save Movi from the public network (Internet):

  26 Dec 14:11:21	"" "" "" TVCS: event = "Message sent" Service ="SIP" Src - ip = "10.29.10.43" Src-port ="5061" Dst - ip = "41.130.193.41" Dst-port ="59519" Protocol = "TLS" Num-bytes ="426" Level = "4" elements UTCTime = '2011-12-26 12:11:21, 714"
  26 Dec 14:11:21	"" "" "TVCS: event ="responded"Service ="SIP"Src - ip ="10.29.10.43"Src-port ="5061"Dst - ip ="41.130.193.41"Dst-port ="59519"Protocol ="TLS"method ="FOLLOW"to ="sip: [email protected] / * /"code-response ="404"Level ="3"elements UTCTime ='2011-12-26 12:11:21, 714"
  26 Dec 14:11:21

  "" "" "TVCS: event ="application received"Service ="SIP"Src - ip ="41.130.193.41"Src-port ="59519"Dst - ip ="10.29.10.43"Dst-port ="5061"Protocol ="TLS"method ="SUBSCRIBE"Request-URI = 'sip: [email protected] / * /" Level = "3" elements UTCTime ='2011-12-26 12:11:21, 712"

  26 Dec 14:11:21

  "" "" "" TVCS: event = "Message received" Service ="SIP" Src - ip = "41.130.193.41" Src-port ="59519" Dst - ip = "10.29.10.43" Dst-port ="5061" Protocol = "TLS" Num-bytes ="998" Level = "4" elements UTCTime = '2011-12-26 12:11:21, 712"

  26 Dec 14:11:21

  "" "" "" TVCS: event = "Message sent" Service ="SIP" Src - ip = "10.29.10.43" Src-port ="5061" Dst - ip = "41.130.193.41" Dst-port ="59519" Protocol = "TLS" Num-bytes ="587" Level = "4" elements UTCTime = '2011-12-26 12:11:21, 643"

  26 Dec 14:11:21

  "" "" "TVCS: event ="responded"Service ="SIP"Src - ip ="10.29.10.43"Src-port ="5061"Dst - ip ="41.130.193.41"Dst-port ="59519"Protocol ="TLS"method ="FOLLOW"to ="sip: [email protected] / * /"code-response ="407"Level ="3"elements UTCTime ='2011-12-26 12:11:21, 643"

  26 Dec 14:11:21

  "" "" "TVCS: event ="application received"Service ="SIP"Src - ip ="41.130.193.41"Src-port ="59519"Dst - ip ="10.29.10.43"Dst-port ="5061"Protocol ="TLS"method ="SUBSCRIBE"Request-URI = 'sip: [email protected] / * /" Level = "3" elements UTCTime ='2011-12-26 12:11:21, 642"

  26 Dec 14:11:21

  "" "" "" TVCS: event = "Message received" Service ="SIP" Src - ip = "41.130.193.41" Src-port ="59519" Dst - ip = "10.29.10.43" Dst-port ="5061" Protocol = "TLS" Num-bytes ="661" Level = "4" elements UTCTime = '2011-12-26 12:11:21, 642"

  Can someone help me understand why this happens?

  Hi houari,.

  There are several threads on this forum which explains the requirements for the deployment of a VCS in a private DMZ, you can find by searching for "VCS static NAT".

  In short, when you deploy the VCS-E in a statically NAT'ed environment, it is necessary to have the option "Dual network interfaces" key on the VCS - E, this key unlocks the static NAT functionality of the VCS-E.

  You can also find more information in the guide of the VCS for X7.0 Administrator.

  Concerning

  Andreas

• 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

• 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

• VCS - C <>= VCS - C vs VCS - C <>= VCS-E

  Case 1: VCS - C<==[Firewall]==>VCS - C<====>Internet

  Case 2: VCS - C VCS-E<====><==[Firewall]==>Internet

  In both cases, there are hints of options: encryption, interoperability of calls, Traversal, Non-Traversal.

  I have 3 questions, and I hope that someone please respond:

  Q1. In which case the supported encryption on all calls? If yes then what are the requirements to ensure that all calls are encrypted?

  Q2. How to call signal and call road traffic of media in each case, while internal endpoint connects to the remote endpoint?

  Q3. What are different between the covered area and / vs nearby area? I'm looking for pro and con.

  In short, an area of neigbor is appropriate if the media can flow directly without NAT or a firewall blocking somehow.

  A properly configured firewall is in general no problem, but h323 and rtp/media use a lot

  ports and you never really know what are the ports of the remote site will use so you end up having to open it

  high all ports for customers anyway...

  As 'internet' is mentioned, there is also that the components are on public ip addresses (do not forget

  No NAT allowed) and that these higher ports are open between all systems video (including video Jabber) and all (= 'Internet'), not sure if you want that,...

  Its more likely that some calls works perfectly with the deployment of 1 but many other calls will fail.

  so no, this isn't the way to go.

  Remember also, firewall/nat handling is as important on the internet, so if you expect from remote devices

  be behind NAT or a firewall (for example, a JabberVideo user or endpoint to a Home Office) you would

  also need to NAT traversal.

  Unless you have a mutation very very special needs very very specific VCS-E is the device

  you need to deal with the interest to link media.

  Q1. In which case the supported encryption on all calls? If yes then what are the requirements to ensure that all calls are encrypted?

  Endpoint also plays a vital role cordially encryption

  VCS with X7.2 can also supports encryption on the client's behalf, as

  CLIENT1 > (unencrypted) > VCS > (encrypted) > Client2

  Therefore, no problem.

  Q2. How to call signal and call road traffic of media in each case, while internal endpoint connects to the remote endpoint?

  If non-traversal calls (as in the deployment of VCS-C/VCS-C) and Neighborzones are used media will go directly between the endpoints, in the case of failure to sign will stick to the VCS unless you use the optimal call routing

  in some cases can release a VCS from the stream of calls. VCS where endpoint is saved forever

  involved in the call signaling.

  Q3. What are different between the covered area and / vs nearby area? I'm looking for pro and con.

  The area of route is used when you need to limit the number of ports and link media to

  a specific path (between the VCS).

• Route orders for Cisco VCS

  Hello

  We have deployed a VCS Expressway Starterpack with dual NIC

  We followed the deployment guide on how to deploy dual NIC and works very well.

  We find difficult on the way to show the roads that have been set up and also how to remove roads on the VCS.

  What are the specific commands for these?

  Thank you for your support in advance.

  Best regards

  Acevirgil Ocampo

  I checked and did not configure find a way to see what roads are currently, only the ability to add or delete, unless it is under a different command or user interface somewhere.

  xCommand RouteAdd

  «Add and configure a new IP route (also known as a static route).»
  Address (r): 'specifies an IP address that is used in conjunction with the prefix length to determine the network to which applies this road."
  PrefixLength (r): <1..128>'specifies the number of bits of the IP address that must match when determining the network for this route. Default: 32 "
  Gateway (r): 'specifies the IP address of the gateway for this route."
  Interface: "specifies the LAN interface to use for this route. Auto: VCS will select the interface most appropriate to use. "Default: Auto".

  xCommand RouteDelete

  "Deletes a route."
  RouteId (r): <1..50>"The index of the route to delete."

• Questions on the transmission by proxy VCS-E/C Media

  I'm trying to find a way to get the VCS-e to the media of proxy to a nearby area.  We currently use VCS - E to connect to others via areas of course VCS, however, a new organization wants to peer with us via a SBC instead.

  My understanding is that this should be a neighbouring area rather than a crossing area as the SBC support us H460, however it is a problem as long as the area nearby don't media proxy unless the call is interoperability or to another area of course.

  As we have a MCU and some other legacy systems is directly recorded or alongside the VCS-E, this would case calls to fail because the external firewall will obviously only allow traffic to and from the IP address of the VCS-E.

  So is there a way to get the VCS-e media proxy without a crossing area or forcing H323 to SIP Interworking?

  What type of deployment is behind this SBC?

  If you want to archive a behavior of crossing area, incl. sip and h323 especially you should stick with

  a model of VCS. If it is a pure CUCM installation Highway deployment model might be something to look into.

  If really desperate, they want a SBC but media and signaling they should deploy a VCS - C, have a

  area crossing for you and a neighbor through their SBC what they then.

  For a single area of SIP, you have a support of locking option as a command line parameter,

  This + put in routed to always for this area will force the media and stick to the signaling VCS.

  But it of only for SIP and requires Firewall bideirectional openings.

  Please remember useful frequency responses and identify useful or correct answers.

• The authentication of the client at the edge of Collaboration / MRA

  Hello

  Could someone help with the following question?

  When a Jabber client to get authenticated?

  My understanding is that when a Jabber Internet device accesses (to connect) the highway-E, only the server (Expressway-E) is authenticated (using the public certification authority in the operative part of Jabber).

  Is this correct? If so, the user of the device Jabber/get authenticated when the device attempts to save with the CUCM?

  Thanks in advance,

  / Bertin

  Dimension Data.

  In the case of deployment of Jabber/CUCM/Highway, during the initial connection between the Jabber client and server side of the highway, there is an exchange of key/cert/handshake that creates a secure between communication channel. At this point customer Jabber solidly passes the credentials to the edge of the highway and happening at the Expressway kernel, the kernel then provides the credentials to the server CUCM (that defies in turn compared to its local user database authentication or LDAP, if it is in use) then returns a message authenticated core Expressway , which sends it to the side of the highway, which tells in turn the Jabber client, it has successfully authenticated.

  This leaves out some deeper technical details, but does that answer your question?

  Also, above statements may be different for a deployment of VCS (not Expressway series) as there are has several authentication options. It would also be about endpoint and video Jabber for TelePresence and not 'normal' Jabber points.

• 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

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