«
»

Service records and ports, VCS Express

19/08/2009, 13:26

Here are the service records needed to use the Tandberg VCS:

_h323ls._udp.company.com      srv     1 0 1719 vcs-e.company.com.
_h323cs._tcp.company.com      srv     1 0 1720 vcs-e.company.com.
_sip._udp.company.com              srv     0 0 5060 vcs-e.company.com.
_sip._tcp.company.com               srv     0 0 5060 vcs-e.company.com.
_sip._tls.company.com                 srv     0 0 5061 vcs-e.company.com.
_sips._tls.company.com               srv     0 0 5061 vcs-e.company.com.
_sips._tcp.company.com             srv     0 0 5061 vcs-e.company.com.

There should also be an a-record pointing to the vcs express. (in this example, vcs-e.company.com)

Also, should anyone ever need it, here are the ports that an endpoint needs opened outbound if it is registering directly to a VCS express:

TCP/2776 (Q931/H245 for external traversal endpoints)
UDP/2776 (RTP Media from external traversal endpoints)
UDP/2777 (RTCP Media control traffic from external traversal endpoints)
UDP/1719 (H323 RAS signaling from gatekeepers/VCSes and traversal endpoints)
TCP/1720 (Q931/H.225 call connect signaling)

UDP/5060 (SIP signaling)
TCP/5060 (SIP signaling)
TLS/5061 (Encrypted SIP signaling)

Tags: , , , , ,
Category: video conferencing  |  Comment (RSS)  |  Trackback

8 Comments

  1. Jason says:
    18/04/2011 at 12:15

    For clustering, does a new entry needs to be added on the DNS or can one of the above be used? Thanks!

  2. tom says:
    29/04/2011 at 08:40

    Hi

    For clustering, you can either create an SRV record with equal priority and weight and target each of the peers in the cluster, or you can set up the A record to the VCS cluster as a Round robin list of ip addresses.

    see more in the cluster creation guide:

    http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Cluster_Creation_and_Maintenance_Deployment_Guide_X6-1.pdf

    Tom

  3. Kuhuna says:
    09/05/2011 at 22:31

    Can SRV Records be used for subdomains?

    i.e.,

    _sip._tcp.subdomain.company.com srv 0 0 5060 vcs-e.subdomain.company.com.

    TIA!

  4. tom says:
    10/05/2011 at 08:52

    Hi!

    Yes they can.

    The domain in the SRV record needs to correspond to the domain used in the SIP/H323 URI though, so if your endpoint has address something@subdomain.company.com your example can be used.

    I use this a lot when integrating with other systems, eg. MS Lync. The Lync SIP domain is normally company.com, while the Cisco/Tandberg domain would be video.company.com to ease the routing between the to systems.

  5. Mads says:
    18/07/2011 at 14:27

    Is it best practise to use different SIP domains when integrating Tandberg VCS with Lync?

    We have a small installation with a VCS Control and a VCS Expressway and the VCS Control is also acting as Lync Gateway.

    Can you recommend any good resources about Tandberg and Lync integration – apart from the official deployment guide?

    Thanks!

  6. tom says:
    19/07/2011 at 14:24

    It’s not only best practice, it’s more or less required. There are always problems in the installations i’ve seen when the same sipdomain is used.

    I’ve never used anything other guides than the official ones, so unfortunately I can’t recommend anything else other than the internet :/

  7. mek says:
    22/07/2011 at 11:49

    Hei Tom,

    to put it in different words, the single domain setup requires an additional (internal) domain
    for internal devices and mapping via findme/ocs relay. But it works fine :-)

    What is the reason that you list:
    _sip._tls.company.com srv 0 0 5061 vcs-e.company.com.
    _sips._tls.company.com srv 0 0 5061 vcs-e.company.com.

    Also
    _h323cs._tcp.company.com srv 1 0 1720 vcs-e.company.com.
    _sip._udp.company.com srv 0 0 5060 vcs-e.company.com.
    are not really “needed” and can be seen as optional.

    If you have a vcs-e its even worth thinking about disabling 5060udp completly
    as this is way fewer used for video conferening then for voip scans :-)

    In addition I would recomed a weight and priority of 10, the A/AAAA record
    “should” not only be there it MUST (not even CNAME), as it is required for SRV (see RFC2782)

  8. tom says:
    29/07/2011 at 09:42

    Hi mek

    Thanks for the additions!

Leave a Reply