[AusNOG] SIP trunking DR diversion

[Sean K. Finn]

www.netsip.com.au<http://www.netsip.com.au> has a portal where you can manually forward your trunk / range to a different server or IP, but I guess in a short timeframe this

I think it’s even configurable in a failover fashion? Not sure?

It depends on how much time you have on your hands, and what your provider supports.



From: ausnog-bounces at lists.ausnog.net [mailto:ausnog-bounces at lists.ausnog.net] On Behalf Of Coleman, Patrick
Sent: Tuesday, December 11, 2012 2:24 PM
To: Ed Hallett; ausnog
Subject: Re: [AusNOG] SIP trunking DR diversion

Sure, Telstra (for example) does this with their SIP Connect product, though I’m not sure it’s exactly what you want. Basically you can nominate a number that all inbound trunk calls get diverted to when the trunk registration isn’t up which works quite well.

It sounds like you don’t want to divert the trunk, though, you want to forward all internal extensions out to user softphones so you can retain the hunt group and other internal logic and your users can work remotely. This depends on the PABX system you’re using; Cisco’s CUCM has a softphone that registers like any other phone (and works ok over a VPN), and you would assign the user’s desktop DN to it so both the desk phone and the softphone ring simultaneously and either can be answered. I’d imagine most other VOIP systems could do the same thing.

So basically, it depends on what you have deployed. At the least I’d expect you would need some sort of site-to-site VPN between head office and the remote location, and whichever softphone your internal PABX system supports to register over the VPN. Your VPN endpoint could then do QoS as appropriate.

Cheers,

Patrick


From: ausnog-bounces at lists.ausnog.net<mailto:ausnog-bounces at lists.ausnog.net> [mailto:ausnog-bounces at lists.ausnog.net] On Behalf Of Ed Hallett
Sent: Tuesday, 11 December 2012 11:58 AM
To: ausnog
Subject: [AusNOG] SIP trunking DR diversion

Afternoon Noggers,
More of a “is this possible” scenario:
Can a SIP trunk be diverted in a Disaster Recovery situation, including indials?

More info (as much as I have at this stage):
A client with multiple remote offices is sponsoring a company wide event at a remote location which has a large pipe, and is afraid of what will happen if the staff are trapped at the remote location for a few extra days. They have asked for a method to divert all SIP trunks to their sites to the single remote location, where staff can likely use softphones on their laptop.
The tricky bit as I can see it is the indial 1300 numbers which goes to a group, as well as QOS for up to 20 concurrent inbound/outbound phonecalls.

Does anyone have DR / High Availability experience with SIP trunking and could spare some wisdom? 6 days into the new job and I get this one .
Replies off-list are fine, but feel free to reply online – this may of interest to others.
Kind regards,
Ed – TelTech – 1300 81 55 66 | 0413 233 303


This email, together with any attachments, is intended for the

addressee only. It may contain confidential or privileged information.

If you are not the intended recipient of this email, please notify

the sender, delete the email and attachments from your system and

destroy any copies you may have taken of the email and its attachments.

Duplication or further distribution by hardcopy, by electronic means

or verbally is not permitted without permission.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20121211/a841aa0d/attachment.html>