CISCO VCS exresspress

Hi Team,
From India we are trying to reach our client who is in US.In Video conference tangberg device.we unable to reach from here.
Please find the logs and provide me solution.
2015-01-26T10:32:53-05:00
tvcs: Event="Outbound TLS Negotiation Error" Service="SIP" Src-ip="159.108.120.5" Src-port="25585" Dst-ip="159.108.1.120" Dst-port="7001" Detail="Timeout" Protocol="TLS" Level="1" UTCTime="2015-01-26 15:32:53,365"
I can able to ping and tracert from the client pc I'm unable to reach the web access of the gateway in client side.(159.108.1.120 - VCS expressway)
Let me know wht will the issue

Looking at the basics of that error message - there's been a timeout when trying to establish a TLS connection. Are you able to check your firewalls to see whether you've got all the required ports open?
You don't mention which VCS software version you're using, but you can find the firewall traversal guides for all the different versions at: http://www.cisco.com/c/en/us/support/unified-communications/telepresence-video-communication-server-vcs/products-installation-and-configuration-guides-list.html
Note: Your question would be better placed in the TelePresence section of the forums where these devices are more actively discussed than in the Video Over IP section you've posted in - I'd suggest, if the above hasn't answered your query, that you move your discussion over there.
Wayne
Please remember to rate responses and to mark your question as answered if appropriate.

Similar Messages

Decode Error in Cisco VCS for a call from Jabber to telyHD

Hi,
We have the following setup:
Cisco Jabber <---> Cisco VCS <---> telyHD (Our Video Product)
Now, the call works well when the call is intiated from telyHD to Cisco Jabber.
But, the call fails when the Cisco Jabber initiates the call towards telyHD.
The packet capture on VCS shows that there is a syslog message from VCS to Jabber indicating the following when 180 Ringing is received from telyHD:
Message [truncated]: tvcs: Event="Decode Error" Service="SIP" Src-ip="10.1.1.19" Src-port="5060" Dst-ip="10.1.11.11" Dst-port="25331" Detail="(User-Agent) Single header User-Agent appeared twice in message" Protocol="TCP" Level="1" UTCTime
Can you please help in troubleshooting this issue. I don't see multiple "User-Agent" headers in the 180 Ringing sent by telyHD.
I have attached the packet capture on VCS.

I am also having the same issue. Can someone please respond? Thanks.

Attaching Second Pool to Trusted Application for Cisco VCS

I have completed the Cisco VCS to Lync 2013 integration found here but needless to say, the guide
is very much lacking in clarity on the Lync end and doesn't take larger deployments into consideration; or I'm just missing something.
Most of the document thinks of Lync as a single pool entity but in my case, we have two pools on campus. My question is as follows:
Can I use DNS to trick the Lync topology builder into thinking there is an alternate device that can be assigned to a trusted application?

Integration and communication between Lync 2013 and Cisco Voice Communication Server, in conjunction with Cisco Tandberg room units.
I wasn't aware of the change taking place site wide and assumed that since the application lists and only accepts my Pool1 as a next hop that the static line between the two could only travel server to server (pool).
Video initiation works from Pool1 to Cisco and vice versa. Video integration between Pool2 and Cisco will only initialize if started by the Cisco endpoint dialing said Lync client. Presence information (provided by Jabber) works for users in
Lync Pool1 but not in Pool2.

Cisco VCS Starter Pack Express

Hi,
I would like to ask if "dual network interface" option key is needed for a Movi Client to register to VCS Starter Pack Express via public or internet?
Details:
VCS Starter Pack Express is installed as part of DMZ.
Able to ping and access VCS via public or internet.
Movi Client was able to register via internal network.
Movi Client was not able to register via public or internet. Same account used in internal network.
Regards,
Arvie

I disagree with your 100%.
The initial question was, can I run Movi with just the VCS Starter Pack Express with out an TMS.
Any yes, you can.
Yes, Movi requires provisioning to run. In general its:
* TMS + VCS + Licenses
In this model the License management for Movi is indeed handled by TMS
btw, you also need a "Device Provisioning Key" on the VCS, not only movi Licenses on the TMS
* VCS Starter Pack Express
Which gives you up to 50 registrations, limited findme and 5 (default) up to 25 (additional purchase) call licenses.
Here a info from the deployment guide: (found in the cisco vcs doc section)

Cisco VCS X7.1 RFC 4480 support (Rich Presence)

Hi all,
This is regarding Cisco VCS-C X7.1 or 7.2.
We’re trying to implement Rich Presence (RFC 4480) which is stated as supported in this document (page 34):
http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/release_note/Cisco_VCS_Release_Note_X7-1.pdf
However, the VCS returns “Online” indication even if the system in question is in a call. There’s no “busy” status for some reason. I’m referring to the SIP PUA which gives an option for using the presence even with H.323 endpoints, given their registration in a form of URI.
Is the Rich Presence supported for Jabber only?
Thanks!

Rich Presence isn't available for the normal endpoints, only the SIP SIMPLE status generated by the Presence User Agent (PUA). From the on-line help:
Endpoints that do not support presence can have status published on their behalf by the VCS. The service that publishes this information is called the Presence User Agent (PUA).
The PUA takes information from the local registration database and the call manager and determines, for each endpoint that is currently locally registered, whether or not it is currently in a call. The PUA then provides this status information via a PUBLISH message.
For the PUA to successfully provide presence information about a locally registered endpoint:
The endpoint must be registered with an alias in the form of a URI.
The domain part of the URI must be able to be routed to a SIP registrar that has a presence server enabled. (This could be either the local Presence Server, if enabled, or another Presence Server on a remote system.)
When enabled, the PUA generates presence information for all endpoints registered to the VCS, including those which already support presence. The status information provided by the PUA is either:
online (registered but not in a call)
in call (registered and currently in a call)
The PUA will update and publish presence information on receipt of:
a registration request (for new registrations)
a registration refresh (for existing registrations)
a deregistration request
call setup and cleardown information
Wayne
Please remember to rate responses and to mark your question as answered if appropriate.

Cisco VCS Microsoft Office 365 interop

As I understand this in order to connect Cisco Telepresence endpoints to the MS Lync client a VCS gateway is required.
This is supported for the on premises version of MS Lync. However I cannot find anything that details support or a road map
of the support of MS Lync within MS Office 365.
Does anyone have a road map or information on when support for Lync MS Office 365 may be forthcoming?
Thanks
Mark

Ah, but is SIP a "standard"? There are multiple RFCs outlining the protocol, but it isn't a standard per se, not in the way that H.323 is a "standard".
Yes, I'm splitting hairs, however, I agree with you and when companies bastardise SIP for their own nefarious purposes, they should at the very minimum provide an open interoperable gateway so that they can communicate will "normal" SIP based product that do comply to the RFCs. An example of a way that it could be done is through the StarLeaf (ex Codian) products. They use their own propitiatory SIP stack, yet their backend allows for full interoperability with H.323 , 'normal' SIP, and Lync - I must admit that I do like what they offer. The only ironic thing is that they don't negotiate AAC audio when hooked up to the Codian MCUs due to there product not being "white-listed"!. As Cisco now own Codian, we did forward a request to Cisco to add the StartLeaf product to the whitelist for these MCUs - we will have to see what happens....
Nevertheless, the last I read about this was that MS were looking to bring such a development to Lync, probably in 2015. I can't remember where I read it, but I think it may have come out of the last Lync Conference. My guess is that it will be rolled into a part of the next evolution of the product such as Lync 2015/16?

Cisco vcs 7.2.2 on vmware

Hello friends,
that is the question.
is it available to install the vcs 7.2.2. to my laptop's vmware?
According to some document, this version can be installed to vmware only UCS series.
thank you.

Hi Onur,
VCS can be installed only on UCS or 3rd party specs based on Intel Xeon. Please check the following link
http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_TelePresence_Video_Communications_Server
Let us know if this answers your query.
Manish

Cisco VCS

Hi,
I am new on the Cisco Telepresence and we will be getting Cisco Telepresence VCS to installed on our Campus and what to know:
1. Is this appliance support any dynamic routing "ospf, ..."
2. How many ethernet port this appliance has ? I would like to connect one port to FW and one port to Server Farm switch, is this OK as design ?
3. How about QoS, Is autoQoS enough to do in the access layer switches or need more ?
4. Any design recommendation or tips will be appreciated.
Thanks

Looking at the basics of that error message - there's been a timeout when trying to establish a TLS connection. Are you able to check your firewalls to see whether you've got all the required ports open?
You don't mention which VCS software version you're using, but you can find the firewall traversal guides for all the different versions at: http://www.cisco.com/c/en/us/support/unified-communications/telepresence-video-communication-server-vcs/products-installation-and-configuration-guides-list.html
Note: Your question would be better placed in the TelePresence section of the forums where these devices are more actively discussed than in the Video Over IP section you've posted in - I'd suggest, if the above hasn't answered your query, that you move your discussion over there.
Wayne
Please remember to rate responses and to mark your question as answered if appropriate.

Cisco VCS/Codian MCU and Lync 2013 integration

Hi,
I would like to know if Lync 2013 is supported to work with:
- Cisco Tandberg VCS version x6.1
- Cisco Codian 4.1 (comp. 6.16)
Is it necessary to update both devices to be supported/homologated/qualified?
Thanks

Hi, Kent ... From what I'm seeing so far the challenges of integrating Cisco/Tandberg equipment and Lync 2013 are the same as what you may have already encountered with Lync 2010. Since the Cisco endpoints and MCU cannot register directly to Lync 2010
or 2013, you will need to leverage the VCS systems as your SIP gateway between them and Lync clients. In Lync 2010 there were limitations as to the interoperability of the H.263/264 codec used by Cisco gear and the RTV codec that Lync was restricted
to, and we often experienced frozen video feeds from Lync clients or an inability to connect to individual Cisco endpoints or conferences hosted by the Codian MCU. Even though Lync 2013 will use H.264 as a codec for the video stream, I anticipate there
will still be challenges interconnecting through the VCS as well as providing content between Lync and Cisco endpoints. However, I expect an increase in the video quality since Lync 2013 supports higher resolutions and also uses a non-proprietary codec.
I expect content to still be unreliable for the Lync participant, even when using a Codian MCU.
You will still need to setup your VCS with a separate Neighbor zone for the Lync 2013 server just as you did for Lync 2010. I wouldn't hold my breath for Cisco to update the VCS software to accomodate the specific needs of Lync 2013, but at least the
VCS will get the correct video codec and connect your call. I don't know about you but I had to put my Cisco units and MCU into a separate SIP domain from the Lync pool, and then create a static route for the Cisco SIP domain on the Lync 2010 front-end
server. I expect to do the same in Lync 2013.
Ideally, Microsoft and Cisco would agree that SIP is SIP, and whether an endpoint registers with VCS, UCM or Lync shouldn't be relevant. Alas, it'll be a long, long time before that is true, certainly not as long as Microsoft and Polycom have
such a tight bond. I plan on implementing Lync 2013 in the next few months and will gladly post any progress here. At this point my plan is to simply mirror the static route and configuration I have with Lync 2010. My VCS and Codian units
are running software versions just a little ahead of yours and work fine.
Good luck!

Cisco vcs "ghost" or fake URIs dialing attempts

A customer reported that there was many call attempts from non-registered or "fake" URIs in their VCS Control and VCS expressway, the consecuence is the saturation of the customer internet bandwidth due the numerous requests.

This has been discussed before in these forums. Have a look at some of the following threads:
nuisance-h323-calls-sx20
ghost-calls-tandberg-e20
sourceh323idcisco-incomingcalls
vcs-sip-abuse-reported
Wayne
Please remember to rate responses and to mark your question as answered if appriopriate.

Cisco VCS Starter Pack Express (VCSSPE) Resilience

I have to deploy two VCS Starter Pack Express on two different sites. The VCSSPE-1 (192.168.1.1) on main site is always be a Active and VCSSPE-2 (10.1.1.1) on backup site is always be a Standby.
I know the VCSSPE is not support the Cluster .... Must be upgrade as VCS-C & VCS-E?
Can I use DNS resilience? Must DNS A-Record resilience is Round Robin?
Make the TP endpoints reg. on the "vcs.abc.com"
DNS A-Record "vcs.abc.com" point to two IP addresses "192.168.1.1" and "10.1.1.1". Default is 30 sec timeout? lookup 192.168.1.1 1st > 30 sec timeout > lookup 10.1.1.1
Must upgrade?
DNS must be RR?

Hi Chad,
You don't need TMS to get Jabber Video for Telepresence (Movi) working. You just need the VCS. I have a VCS Starter Pack X6.1 and I use Jabber Video for Telepresence v4.4 :-)
Hope to help, please remember to rate the post if it does.
Kind regards,
- Adrian.

Cisco VCS versus GK+CUBE

Is it possible to get VCS to query a remote (directory) gatekeeper in order to setup an off-premise H.323<>H.323 call, or do remote zones have to be running VCS clusters too? I have achieved something similar running GK+CUBE on a single IOS device, but the emphasis now appears to be on VCS for video call control (with SIP integration into CUCM as required). The CUBE also handled the address hiding for H.323<>H.323 calls; can VCS do this or is VCS ExpressWay a requirement for this?
Cheers,
Matt

Hi,
We are doing an integration between two companies that have CUBE and VCS control. I saw that your question is old... Did you eventually this integration?, Could you give me some feedback?, please.
Thanks

PCM - Consumption of Call Licenses - Cisco VCS

Hi,
I am interested to find out if PCM can look at the consumption of call licenses and flag when these when they reach a capacity threshold (i.e 75%) Looking at our current configuration I see an alarm enabled for "High Utilisation" but this does not tell me what threshold the high utilisation is set up at.
Would it be possible to tell me what threshold the high utlisation is set at?
Secondly, I suspect I know the answer to this but can PCM project when these thresholds might be met by looking at historical call data? For exmaple if PCM sees an overall growth in call volume?
Thanks

Hi,
Can anyone assist?

Cisco UCM 8.0 and new Tandberg VCS/ MCU

I can find a lot of quite old interoperability documents on Tandberg and Cisco.
But if a customer already had Tandberg H.323 endpoints and wanted to add a Tandberg VCS and MCU for VC bridging, what is the best way to get the Cisco phones to be able to join a multi-party video call on the MCU?
I'm thinking the MCU could run as an end point to Call Manager (phones running SCCP)?
Or, can you have SIP trunk(s)from CUCM 8.0 to the VCS and use traversal calls?
Or even if the phones were running SIP, can they talk to the VCS via the CUCM. Do they even need to - I can't imagine they can act as SIP endpoints registered to the VCS while their "day job" is being registered to CUCM.
Any help appreciated....Even if it means telling my questions don't make sense - as long as you tell me why!
Regards

Gordon,
The latest deployment guide for Cisco VCS and Unified Communications Manager (UCM) is available here:
http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Cisco_Unified_Communications_Manager_Deployment_Guide_CUCM_6-1_7_8_and_X6.pdf
Based on your post, I'd think you want to go this route:
1. Build a SIP trunk between VCS and CUCM. You have to make some decisions as to how you are going to do this:
- Security: Are you going to use TLS for setup? SRTP for media? If yes, then you will need to look at getting certificates aligned on both systems. The best approach is to use an internal CA to generate server certs for both clusters and then configured CUCM and VCS with the appropriate CA trust list. There are several docs for both products that cover this.
- Call failover and/or load balancing: If load balancing is required, you will need to leverage DNS SRV records that point to your CUCM cluster and a separate set of DNS SRV records for your VCS cluster. The pros: you can get away with one SIP trunk on CUCM and a single DNS neighbor zone on VCS. The cons: Some folks get squeamish with DNS SRV. An alternate approach is detailed in the deployment guide reference above. You would createa "neighbor zone" on the VCS. One per CUCM call processing node. On the CUCM you would create a separate SIP trunk for each VCS (or, if using CUCM 8.6 you can get away with one trunk, multiple peers).
- SIP profiles: This is easy. The deployment guide lays it out for you and the VCS includes a pre-canned profile so it knows how to talk to CUCM.
2. Dial plan. You will want to configure your dial plan so that you avoid overlaps/conflicts/call routing loops. As a simple example, assume you program all 7xxxx extensions to be video. Done. Tell CUCM to send all 7xxxx extensions to VCS. Tell VCS to send CUCM extensions to CUCM. Tricky parts come in when you want to enable features like SnR. Both products have a facility for this. You have to learn both and pick one as an authority. There is more to it. But no need to get too fancy at this point.
3. SIP/H323 interworking. The VCS Control can support up to 100 concurrent, interworked calls. So, the VCS can handle SIP to H323 interworking for you. It is good like that.
- MCU: You can avoid interworking for your MCU if it supports SIP natively. If your MCU is one of the Codian boxes then it can do H323 and SIP simultaneously. A discussion on this can get quite involved. The basic idea is that you configure a SIP Neighbor Zone for the MCU. You configure membership rules on the VCS to put MCU SIP URI registrations into this neighbor zone. Finally, you configure search rules on the VCS so that H323 and SIP dial patterns for a MCU resource are given the same search priority. Say, you use 100 as your H323 prefix. Then you would have a "100\d*" H.323 rule and a "100\d*@mcu.uri.com" SIP rule. The first rule points to Local Zone and the 2nd points to the MCU SIP Neighbor Zone. They are given equal priority and are searched at the same time. VCS will prefer SIP if the original caller is SIP. If this is too much info for you, just do the interworking until you get comfy and can optimize your design.
- VCS registered endpoints: VCS registered endpoints that support SIP and H.323 should have both protocol stacks enabled. This will minimize interworking when you call from VCS-to-CUCM. For CUCM-to-VCS you will probably still deal with interworking since your SIP URis probably are something more useful than an e164 number@yourdomain.
Phones on the CUCM can stay on the CUCM. Their calls will route via CUCM to VCS over the SIP trunk. You may need to dork around with CODECs, regions, and locations to ensure transcoding isn't needed. The bottom line is that if a phone is registered to CUCM, it doesn't need to have a separate registration for VCS:
phone-->CUCM-->VCS-->endpoint/mcu/etc.
Get things configured right, then you can think of this solution as a single system with multiple components rather than individual systems spliced together.
HTH.
Regards,
Bill
Please rate helpful posts.

VCS X8.5.1 SIP TLS to CUCM 8.6.2

I'm having problems enabling TLS on my SIP trunk from the VCS to CUCM.
The SIP trunk shows active on the VCS, but I can't make calls from VCS to CUCM or from CUCM to VCS.
Before configuring TLS, I was able to make these calls.
With TLS enabled, the VCS search for calls from VCS to CUCM show the call rejected and give the reason "Forbidden"
Calls from CUCM to VCS get fast busy and I do not see anything in the search history on the VCS.
I've restarted the trunk and call manager service on the CUCM servers, but no change.
I'm not really sure where to go from here.
I followed the following guide for configuring the SIP trunk. http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/config_guide/X8-5/Cisco-VCS-SIP-Trunk-to-Unified-CM-Deployment-Guide-CUCM-8-9-10-and-X8-5.pdf
Any help is appreciated.
Thanks,
Joe

I have again checked these and identical to what I set up, We have a multiple TX9000's on the CUCM in Secure mode working perfect and can make Encrypted calls to the TPS server via a TPS TCP Trunk.
but any calls to the VCS just fail on a VCS To CUCM Trunk using TLS with a fast busy signal. and the VCS doesn't even show a search history for it.
In the eyes of the VCS and the CUCM there is no Issues with the TLS SIP Trunk it seems to be working, but It seems SIP TLS packets don't even leave the CUCM. I have tried almost every resource known, and thought it was me just having some random issue until I saw Josef post the same issue.
Tomorrow I will check the X.509 names on the CUCM SIP Security Profile as this is the only thing I can think of that might cause the SIP trunk to be OK up but not route correctly maybe?

CISCO VCS exresspress

Similar Messages

Maybe you are looking for