cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
7144
Views
67
Helpful
20
Replies

VCS Cluster DNS issues

ma.romero
Level 2
Level 2

Hi,

I have created a DNS SRV for configure in the FQDN of the VCS Cluster.

The problem is when the Devices try to register to the VCS Cluster; I put in the endpoints, in the part of Gatekeeper Registration the DNS or the IP of the DNS SRV but the always the endpoints never reach the  VCS CLuster.

I check the logs in DNS SRV and I don't see any request from devices.

I think that I have to create a virtual IP address with DNS with Load balancer, I mean: IP/DNS(FQDN) for Cluster with load balance and when the devices trying to connect to IP/DNS of the cluster this send the request to one IP or hostname of the one peer of the cluster.

DNS CLuster

23.1.0.201 (vcs.xxx)

Peer of the cluster:

23.1.0.32 (vcscontroltc.xxx) Master

23.1.0.33(vcscontrolvag.xxx) Slave

xxx--> domain

Is it correct?

Thanks in advance.

Best regards.

20 Replies 20

You will need a set of SRV records to support device registration to the cluster. Note, this isn't strictly required, just recommended. So, given your example you would need SRV records for the @vcsc.video.company.com. Your two VCS appliances will need DNS "A" (or host) records to resolve hostname to IP address.

If you are accepting ingress URI dialing, then you will need another set of SRV records (SIP and/or H.323, depending on what you want to support) for the @video.company.com domain. This is only necessary if you want external video endpoints (like the one at my desk) to call user@video.company.com.

HTH.

Regards,

Bill

http://ucguerrilla.com

HTH -Bill (b) http://ucguerrilla.com (t) @ucguerrilla

Please remember to rate helpful responses and identify

Thanks again Bill. Just to be completely clear:

" If you are accepting ingress URI dialing, then you will need another set of SRV records (SIP and/or H.323, depending on what you want to support) for the @video.company.com domain. This is only necessary if you want external video endpoints (like the one at my desk) to call

user@video.company.com "

This addtional set of SRV records will be configured under the Cluster DNS record, correct? The VCS appliances need "A" records only.

Thanks once more. I don't see the option to rate responses. Probably because I didn't started this thread?

In any case I rate you 5 stars.

Oscar

Hi Everyone,

We use Microsoft Windows 2003 server for DNS lookup, it seems you can only create SRV records on the domain level, for example we can create a VCS cluster SRV record of: _sips._tcp.company.com, but we can't find a way to create a SRV record of: _sips._tcp.vcscluster.company.com (note that vcscluster.company.com is the VCS cluster name), any suggestions?  Thanks in advance!

Regards,

Jie

When I was using Windows 2003 for DNS in my I had to create a new forward zone for the VCS cluster. I have also had customers do the same when they used Windows DNS. Basically, you create a new zone: vcscluster.company.com. Then you add the SRV records in that zone. It is OK if they point to host records in the parent zone (company.com).

HTH

-Bill (http://ucguerrilla.com)

HTH -Bill (b) http://ucguerrilla.com (t) @ucguerrilla

Please remember to rate helpful responses and identify

Hi Bill,

Thanks a lot!! I am forwarding your answer to our DNS admin, I think that's it!

Regards,

Jie

Hi Bill,

I have a follow-up question:

With the SRV records setup for VCS cluster: vcscluster.company.com, the C40 and Jabber clients we support seem to have no problem with it.  In the backend we also have the following devices:

1) 8510 MCU blades

2) 8321 ISDN GW

3) Conductor

4) TCS Content Server

Are the above devices "cluster aware" like the C40s?  If not, how should I configure them for the VCS cluster?

Thanks in advance!

Jie