[VoiceOps] Acme SBC geographic redundancy

[Jason L. Nesheim]

Right, that would impact existing established calls and subscriptions. However, larger problem is that in a failover condition endpoints would begin sending SIP Invites to a SBC (pair) that does not have a valid registration cached, and depending on the configuration, SIP port map. Depending on the re-registration interval, this could result in outbound call failures for anywhere for a couple minutes to an hour or more. In the reverse direction the inside SBC IP would be unique at each site. This would render the metaswitch unable to contact the endpoint for PSTN -> VoIP calls for the period of re-registration as well. 




-- 
Jason Nesheim 




----- Original Message ----- 
From: "Alex Balashov" <abalashov at evaristesys.com> 
To: "Jason L. Nesheim" <jnesheim at cytek.biz> 
Cc: "Brad Anouar" <Brad at broadcore.com>, voiceops at voiceops.org 
Sent: Sunday, September 6, 2009 5:39:46 PM 
Subject: Re: [VoiceOps] Acme SBC geographic redundancy 

Jason L. Nesheim wrote: 

> If you're going to use SRV records in an Access deployment with 
> registration caching on the Acme SBC one thing to keep in mind is that 
> non-HA SBCs (or two separate pairs) will not share their registration 
> and NAT databases. 

I would imagine they don't share transaction and dialog state either. 

-- 
Alex Balashov - Principal 
Evariste Systems 
Web : http://www.evaristesys.com/ 
Tel : (+1) (678) 954-0670 
Direct : (+1) (678) 954-0671 
Mobile : (+1) (678) 237-1775 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20090906/d5926723/attachment.html>