RFQ: New Voxalot Failover Implemention

[martin]

We have made some changes to Voxalot to further improve our fail over capabilities. Please read and comment on this fail over strategy. It is important to note that this fail over strategy will ONLY work for you if you configure your device to use SRV lookups. So please do so:

SRV record - Wikipedia, the free encyclopedia

The following is a breakdown of the new UDP SRV setup for Voxalot. The TCP setup is identical.

AU Service

host -t srv _sip._udp.au.voxalot.com

_sip._udp.au.voxalot.com has SRV record 10 100 5060 proxy01.au1.voxalot.com.
_sip._udp.au.voxalot.com has SRV record 20 50 5060 proxy01.us1.voxalot.com.
_sip._udp.au.voxalot.com has SRV record 20 50 5060 proxy02.us1.voxalot.com.
_sip._udp.au.voxalot.com has SRV record 30 100 5060 proxy02.eu1.voxalot.com.

Direct 100% of traffic to proxy01.au1.voxalot.com

1st Failover:

Direct 50% of traffic to proxy01.us1.voxalot.com
Direct 50% of traffic to proxy02.us1.voxalot.com

2nd Failover:

Direct 100% of traffic to proxy02.eu1.voxalot.com


EU Service

host -t srv _sip._udp.eu.voxalot.com

_sip._udp.us.voxalot.com has SRV record 10 60 5060 proxy01.eu1.voxalot.com.
_sip._udp.us.voxalot.com has SRV record 10 40 5060 proxy02.eu1.voxalot.com.
_sip._udp.eu.voxalot.com has SRV record 20 100 5060 proxy02.us1.voxalot.com.
_sip._udp.eu.voxalot.com has SRV record 30 100 5060 proxy01.au1.voxalot.com.

Direct 60% of traffic to proxy01.eu1.voxalot.com
Direct 40% of traffic to proxy02.eu1.voxalot.com

1st Failover:

Direct 100% of traffic to proxy02.us1.voxalot.com

2nd Failover:

Direct 100% of traffic to proxy01.au1.voxalot.com

US Service

host -t srv _sip._udp.us.voxalot.com

_sip._udp.us.voxalot.com has SRV record 10 60 5060 proxy01.us1.voxalot.com.
_sip._udp.us.voxalot.com has SRV record 10 40 5060 proxy02.us1.voxalot.com.
_sip._udp.us.voxalot.com has SRV record 20 100 5060 proxy02.eu1.voxalot.com.
_sip._udp.us.voxalot.com has SRV record 30 100 5060 proxy01.au1.voxalot.com.

Direct 60% of traffic to proxy01.us1.voxalot.com
Direct 40% of traffic to proxy02.us1.voxalot.com

1st Failover:

Direct 100% of traffic to proxy02.eu1.voxalot.com

2nd Failover:

Direct 100% of traffic to proxy01.au1.voxalot.com

[majo]

Hi,
As far as i understand, this SRV should be supported by client hardware or software. User does not need to change any thing. Luckily my fritz box support this. I have verified SRV under windows & linux, works both.

By the way what will be way to override this failover mechanisem, if by chance any failover server does not work better for any user. May be direct IP address of preffered server or may be there should be seperate DNS without SRV records.
Ok found!!! proxy01.eu1.voxalot.com will always connect to EU server without failover support.

This SRV failover mechanisem will work for WebCallBack, callforwarding & registered servers or not? Or user will need to change preffered cluster in member detail page manually?

More info.
DNS SRV - voip-info.org
SRV implementations - voip-info.org

I have tested eyeBeam 1.1 3007n stamp 17816, tried eu, us & au proxy server but it always connect to AU proxy[Eyebeam Bad client wrt SRV]
Fritzbox connect as expected.

Regards.

majo

[gotalkvoip]

for some un known reason couldn't get failover mechanisem to work for my spa3102, well I've followed instructions provided by another member but still doesn't register well this is what I've down have i missed something?

under LINE 1 tab:
Use DNS SRV:yes
DNS SRV Auto Prefix: yes
Proxy Fallback Intvl: 900
Proxy Redundancy Method:Based on SRV Port

under SIP tab:
Substitute VIA Addr:yes
Send Resp To Src Port: yes
STUN Enable:yes
STUN Test Enable: yes
STUN Server:stun.voxalot.com:3478
EXT IP:
EXT RTP Port Min:
NAT Keep Alive Intvl: 15

for my proxy i use: au.voxalot.com:5060
(for some reason au.voxalot.com doesn't work)

Also do i need to switch NAT on in spa3102 as it never works for me so I haven't touched it

appreciate anyones help

[ptruman]

Ditto that, it's not working for me either.

I'm using STUN (stun.voxalot.com), I was configured for eu.voxalot.com, "Send Resp To Src Port" is yes, all VIA flags are set to NO and fallback is set to based on SRV port, and NAT is enabled.

No failover for me...

Does anyone have failover working with an SPA3102? (I'm on BIOS 5.1.10(GW))

[g00fy]

Is this automatically handled by ATA's? I see nowhere in my device I can set this SRV stuff.

By the way, I use a Zyxel 2602H-63 modem.

[amroe]

Thanks Martin , but iam not an expert what i have to do with my sip ATA to get this feture active and thanks .

[Steve]

Also tried the failover witha 3102 with no luck

[sleek]

I'm using Grandstream HT-502 and the latest firmware includes failover SIP server field so SRV records or not I do have secondary option in case of disaster.

What I'm really digging is the fact that SRV records work vice versa. For example if my primary server fails and devices register to one of the alternatives, I have to log in and change the SIP server on record with IPKall to reflect on the sip proxy switch. Now, regardless of which server my registration goes to, or which server IPKall have on record, URIs are always forwarded to me so that is downright perfect! Bravo! No more missed calls in that regard.

Hey Martin, perhaps you should create SRV records for voxalot.com or sip.voxalot.com for forwarding reasons. Since the eu., us., and au. SRV only matters from geographical stand point, otherwise it's irrelevant when URI forwarding is implemented to either of Voxalot's users. Not that it really matters, though certain clarity will be established for users who have DIDs or have other VSPs forwarded TO Voxalot.

[boatman]

Originally Posted by Steve

Also tried the failover with a 3102 with no luck

DNS SRV failover works with Linksys ATAs such as PAP2 and SPA3102. To use DNS SRV failover set 'Proxy' and 'Outbound Proxy' to the desired Voxalot proxy such as us.voxalot.com (not us.voxalot.com:5060). When using DNS SRV one cannot specify any port number after the proxies used in 'Proxy' and 'Outbound Proxy'. A port number should be included with any SIP addresses used in the Dial Plan or Speed Dial Settings (example; echo@proxy01.sipphone.com:5060)

Also set the following:
Use DNS SRV: yes
DNS SRV Auto Prefix: yes

After making these changes all Voxalot proxies will be available for use automatically. The order in which the proxies are used will vary depending on which proxy name you have entered in 'Proxy' and 'Outbound Proxy' (us.voxalot.com, eu.voxalot.com, or au.voxalot.com) and of course which proxies are on/off line.

Edit: Be sure to direct inbound calls to your_number@voxalot.com. Do not use the regional proxy names (au.voxalot.com, eu.voxalot.com, us.voxalot.com) for inbound calls from outside Voxalot's network such as DIDs from ipkall.com.

[137383]

Originally Posted by boatman

Edit: Be sure to direct inbound calls to your_number@voxalot.com. Do not use the regional proxy names (au.voxalot.com, eu.voxalot.com, us.voxalot.com) for inbound calls from outside Voxalot's network such as DIDs from ipkall.com.

I have no problem with my DID fowarded number to 123456@voxalot.com i receive a bussy signal whith the "registered sip did-number" when i call to this number from pstn see here

ps: i can make calls without problem.

What i need do? to fix the problem.