Cisco Unified Communications Manager

More documents

Recommendations

Info

Appendix 10 – Connecting VCS to CUCM using TLS (rather than TCP)Update the VCS neighbor zone to CUCM to use TLSNote: VCS will report that the CUCM zone is active even while it is communicating with CUCM overTCP. The changes below are necessary to allow communications to happen over TLS.On VCS:1. On the Edit zone page (VCS configuration > Zones, then select the zone to CUCM).2. Configure the following fields:SIP sectionPort 5061TransportTLSTLS verify modeOffAuthentication trust mode OffLeave other parameters as previously configured.3. Click Save.Verify that the TLS connection is operationalTo verify correct TLS operation, check that the VCS zone reports its status as active and then makesome test calls:1. Check the VCS zone is active:a. Go to VCS configuration > Zones.b. Check the Status of the zone.If the zone is not active, try resetting or restarting the trunk again on CUCM.2. Make a test call from a VCS registered endpoint to a CUCM phone.3. Make a test call from a CUCM phone to a VCS registered endpoint.Note: CUCM 8.0.2 and earlier do not handle received crypto tags properly; the receipt of them maycause CUCM to clear the call. If this occurs, configure endpoints with Encryption = Off.TANDBERG Deployment Guide: CUCM v6.1, 7 and 8 with VCS X5.1 using a SIP trunk Page 42 of 43
Disclaimers and noticesDisclaimers and noticesThe objective of this documentation is to provide the reader with assistance in using and configuring the product. Thecapabilities of TANDBERG products and other manufacturers' products change over time and so the required configuration maybe different from that indicated here. If you have any suggestions for changes to this document, please feed them back toTANDBERG through your TANDBERG Authorized Service Representative.If you need technical support, please contact your TANDBERG Authorized Service Representative.The specifications for the product and the information in this Guide are subject to change at any time, without notice, byTANDBERG. Every effort has been made to supply complete and accurate information in this Guide; however, TANDBERGassumes no responsibility or liability for any errors or inaccuracies that may appear in this document.TANDBERG® is a registered trademark belonging to Tandberg ASA. Other trademarks used in this document are the propertyof their respective holders.This Guide may be reproduced in its entirety, including all copyright and intellectual property notices, in limited quantities inconnection with the use of this product. Except for the limited exception set forth in the previous sentence, no part of this Guidemay be reproduced, stored in a retrieval system, or transmitted, in any form, or by any means, electronically, mechanically, byphotocopying, or otherwise, without the prior written permission of TANDBERG.www.tandberg.com© 2010 TANDBERGTANDBERG is now part of <strong>Cisco</strong>TANDBERG Deployment Guide: CUCM v6.1, 7 and 8 with VCS X5.1 using a SIP trunk Page 43 of 43
Page 1 and 2: Cisco UnifiedCommunications Manager
Page 3 and 4: ContentsLook at “Call history”
Page 5 and 6: IntroductionIntroductionObjectives
Page 7 and 8: Enabling calls between endpoints re
Page 15 and 16: Enabling endpoints registered on th
Page 23 and 24: Enabling endpoints registered on CU
Page 25 and 26: Enabling endpoints registered on CU
Page 27 and 28: Appendix 1 - TroubleshootingLook at
Page 29 and 30: Appendix 1 - TroubleshootingVCS Rep
Page 31 and 32: Appendix 2 - Known interworking cap
Page 33 and 34: Appendix 4 - Allow dialing to VCS d
Page 35 and 36: Appendix 5 - Connecting CUCM to a c
Page 37 and 38: Appendix 7 - Endpoint specific conf
Page 39 and 40: Appendix 9 - CUCM 5 incompatibility
Page 41: Appendix 10 - Connecting VCS to CUC

Cisco Unified Communications Manager

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?