Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

VCS Expressway redundancy

Hi All,

I am trying to check redundancy operation between my two VCS-Es version x8.1. The following is my scenario:

2x CUCM ----- 2x VCS-C ----- 2x VCS-E

I am connecting through VCS-E to register EX endpoint to CUCM (9.1.2) servers. Registration works fine. I have tried to test redundancy, but I could not see this working as expected.

When my endpoint is registered to primary VCS expressway, and I disconnect network cable of primary expressway, endpoint goes to unregistered. Even if I change the PROXY to point to the second VCS expressway, endpoint stays unregistered. When I plugin the network card of the primary expressway, the endpoint registered to the secondary or primary VCSE. Why is this so. This is not redundant. If the first goes down, I am expecting that the second will take over everything... Any ideas?

8 REPLIES

VCS Expressway redundancy

Hi Sebastian,

on the Ex have you enabled SIP outbound ?

regards

Alok

New Member

VCS Expressway redundancy

Hi Alok,

No. I use DNS SRV records for redundancy. Even If I set endpoint to use secondary VCS-E, when primary is down. It will not register. If I enable primary back, and leave the setting to register to secondary, the registration is accepted.

BR,S.K.

VCS Expressway redundancy

Sebastian,

so you mean to say you forcefully remove the cable from first VCS-E and then go to endpoint and modify the proxy 1 address to point to secondary peer, correct?

did you tried taking the logs when you have primary VCS down.

regards

Alok

New Member

VCS Expressway redundancy

I am removing the cable from primary VCS, and in the same time i am investigating what is going on on the endpoint. After couple of seconds, the endpoint unregisters. So the normal scenario should be, that the endpoint changes the SIP proxy to another A host provided in the SRV record. Probably it does, but it cannot register to secondary VCS. If I change the PROXY to secondary VCS-E, the endpoint stays unregistered. If I plug the primary VCS back, it will register if I provide primary or secondary VCS-E. Both scenarios works. Even if primary is down, then no registration in successfull.

No logs for now. Where will I see the apropriate logs?

New Member

VCS Expressway redundancy

Anyone has a comment to this discussion. The situation is still the same...

VIP Purple

VCS Expressway redundancy

Can you show us your DNS SRV records for the Expressways?

New Member

VCS Expressway redundancy

> set type=SRV


> _sip._udp.phone.telekom.si

Non-authoritative answer:
_sip._udp.phone.telekom.si      SRV service location:
          priority       = 1
          weight         = 0
          port           = 5060
          svr hostname   = vcsemb.phone.telekom.si
_sip._udp.phone.telekom.si      SRV service location:
          priority       = 1
          weight         = 0
          port           = 5060
          svr hostname   = vcselj.phone.telekom.si

telekom.si      nameserver = taurus-2.siol.net
telekom.si      nameserver = taurus-1.siol.net
taurus-1.siol.net       internet address = 193.189.160.11
taurus-1.siol.net       AAAA IPv6 address = 2a00:ee0:d::11
taurus-2.siol.net       internet address = 193.189.160.12
taurus-2.siol.net       AAAA IPv6 address = 2a00:ee0:d::12


> _sip._tcp.phone.telekom.si


Non-authoritative answer:
_sip._tcp.phone.telekom.si      SRV service location:
          priority       = 1
          weight         = 0
          port           = 5060
          svr hostname   = vcsemb.phone.telekom.si
_sip._tcp.phone.telekom.si      SRV service location:
          priority       = 1
          weight         = 0
          port           = 5060
          svr hostname   = vcselj.phone.telekom.si

telekom.si      nameserver = taurus-2.siol.net
telekom.si      nameserver = taurus-1.siol.net
taurus-1.siol.net       internet address = 193.189.160.11
taurus-1.siol.net       AAAA IPv6 address = 2a00:ee0:d::11
taurus-2.siol.net       internet address = 193.189.160.12
taurus-2.siol.net       AAAA IPv6 address = 2a00:ee0:d::12


> _sips._tcp.phone.telekom.si


Non-authoritative answer:
_sips._tcp.phone.telekom.si     SRV service location:
          priority       = 1
          weight         = 0
          port           = 5061
          svr hostname   = vcsemb.phone.telekom.si
_sips._tcp.phone.telekom.si     SRV service location:
          priority       = 1
          weight         = 0
          port           = 5061
          svr hostname   = vcselj.phone.telekom.si

telekom.si      nameserver = taurus-2.siol.net
telekom.si      nameserver = taurus-1.siol.net
taurus-1.siol.net       internet address = 193.189.160.11
taurus-1.siol.net       AAAA IPv6 address = 2a00:ee0:d::11
taurus-2.siol.net       internet address = 193.189.160.12
taurus-2.siol.net       AAAA IPv6 address = 2a00:ee0:d::12
>
>
> _collab-edge._tls.phone.telekom.si

Non-authoritative answer:
_collab-edge._tls.phone.telekom.si      SRV service location:
          priority       = 10
          weight         = 10
          port           = 8443
          svr hostname   = sb-cvcse-lj.phone.telekom.si
_collab-edge._tls.phone.telekom.si      SRV service location:
          priority       = 10
          weight         = 10
          port           = 8443
          svr hostname   = sb-cvcse-mb.phone.telekom.si

telekom.si      nameserver = taurus-2.siol.net
telekom.si      nameserver = taurus-1.siol.net
sb-cvcse-lj.phone.telekom.si    internet address = 89.143.228.90
sb-cvcse-mb.phone.telekom.si    internet address = 89.143.228.91
taurus-1.siol.net       internet address = 193.189.160.11
taurus-1.siol.net       AAAA IPv6 address = 2a00:ee0:d::11
taurus-2.siol.net       internet address = 193.189.160.12
taurus-2.siol.net       AAAA IPv6 address = 2a00:ee0:d::12
>
>
>

VIP Purple

VCS Expressway redundancy

Everything looks good, I was thinking the SRV records priority/weight might have been a factor, but doesn't look like it.

724
Views
0
Helpful
8
Replies
CreatePlease login to create content