VCS cluster SIP registrations

[petark]

Hello,

Can anyone explain the mechanism/difference behind endpoint registration on VCSc cluster FQDN, on ports 5060/5061?

e.g. We have 2 endpoints located in the same network(DNS SRV records are the same), running the same software version, having the same configuration, with the same SIP Proxy registration FQDN(cluster FQDN), same subzone...

Both endpoints are registered with the same cluster peer, but one of them over port 5060 and the other one over port 5061.

Any reason for this? Is there a way to force the registration over port 5061?

Regards,

Petar

[Alok Jaiswal]

It depends on your endpoint configuration. Under SIP protocol configuration check the "transport mode" it would either be UDP/TCP (uses port 5060). You can change that to use TLS which will be port 5061. 

Regards,

Alok

[Patrick Sparkman]

5060 is unencrypted, and 5061 is encrypted with TLS.

For the endpoints that are registering using 5061, check SIP Profile 1 DefaultTransport.  Default is Auto (order of protocols tried is TLS, TCP, UDP), but it could be set to TCP or UDP, recommend setting it to Auto unless you need to force it to TLS.

Here is a good document I used a few years ago when trying to understand SRV records for video conferencing: DNS SRV for TelePresence Video Communication Server.

[petark]

But if both endpoints have SIP Profile 1 DefaultTransport set to Auto, how come one is registered with 5060 and the other one with 5061?

[Patrick Sparkman]

Is SIP TlsVerify enabled? If so, than the CA of VCS certificate must be installed on the endpoint, without it, the endpoint will use 5060.

[petark]

SIP TlsVerify is set to "Off" on every endpoint, yet some of them are using 5060 and some 5061.

How is that happening?