I think it's a good thing to think about but you could possibly use
sipXbridge as well as a third party SBC to do the same thing (or two third
party SBC's of course).

I'm just sayin, if the SIP trunks are that important off-board SBC's are a
good idea anyway.

Mike

On Mon, Jul 4, 2011 at 8:26 AM, Tony Graziano
<[email protected]>wrote:

> Does it make sense to look at being able to provide more than one IP
> in this field at some point in the future? Use case is as follows:
>
> Firewall with dual WAN. Sip trunk registers out each WAN, successfully
> registers and places, receives calls. One trunk can fail to the other
> trunk.
>
> Remote users successfully register, but cannot load balance or
> failover to second WAN since the server behind nat would have to be
> changed/services restarted in order to fully utilize dual wan's.
>
> It is very customary for us to use multiple providers in a small
> business setup. We simply find that putting up a second instance of
> sipx "only" for this is sometimes more involved than it should be.
>
> Server behind NAT: primary public IP 1.2.3.4, secondary public IP 2.3.4.5
>
> I might also suspect with mongo this could be shared/replicated as a
> pool between multiple servers.
>
> Does this make sense to discuss and look at an enhancement request to
> anyone besides me?
>
> --
> ======================
> Tony Graziano, Manager
> Telephone: 434.984.8430
> sip: [email protected]
> Fax: 434.326.5325
>
> Email: [email protected]
>
> LAN/Telephony/Security and Control Systems Helpdesk:
> Telephone: 434.984.8426
> sip: [email protected]
>
> Helpdesk Contract Customers:
> http://support.myitdepartment.net
> Blog:
> http://blog.myitdepartment.net
>
> Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
> _______________________________________________
> sipx-dev mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>



-- 
Michael Picher
eZuce
Director of Technical Services
O.978-296-1005 X2015
M.207-956-0262
@mpicher <http://twitter.com/mpicher>
www.ezuce.com
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to