From a previous thread (which led me to buy some hardware and give up on 
putting the thing on the firewall in the short term, I do intend to make this 
work longer term but I need to actually get this deployed in any form sooner 
rather than later before all interest in SIP vs analog PBX is lost here):

From Eric Varsanyi:
> The immediate problem is that the freeswitch configuration sets the
> sip listen IP to freeswitches guess at our IP (which it gets by trying
> to open a connection to 82.45.148.209 then looking at the resulting
> source IP address in the socket -- in the case of this firewall that
> chooses one of the external routes and return the address on one of
> the external interfaces). I can fix this various ways by hacking
> the .vm files used to build the freeswitch configuration but I'm
> wondering if there are deeper issues.
> 
> Does anyone know of a successful deployment on a multi-homed platform?
> (or is this known to not work for reasons bigger than freeswitch)
From: "Scott Lawrence" <scottlawr...@xxxxxxxxx>
Date: Tue, 19 Jan 2010 12:10:28 -0500

There are a number of similar issues.

At present, the sipXecs distribution is designed to work only on systems
with a single IP address.

-----

Dale Worley wrote:

Nortel sells such a combination:

http://www.nortel.com/products/01/secure_router/collateral/nn124201.pdf

        Nortel Secure Router 4134 with Software Communication System
        (SCS)
        
Dale
------

This all led me to think that Nortel worked through the various issues for 
their commercial offering leaving the open source codebase without the fixes.

Thread starts here: http://list.sipfoundry.org/archive/sipx-users/msg20703.html

-Eric

On Jan 27, 2010, at 6:11 AM, Scott Lawrence wrote:

> On Wed, 2010-01-27 at 01:24 -0800, Mark Eissler wrote:
>> 
>> While the devs might not like the criticism... I think if it's true
>> that 
>> Nortel resolved the issue for SCS500 then I'm not the only one that 
>> thinks this is a design flaw.
> 
> There is no difference between SCS and sipXecs in this respect.
> 
> _______________________________________________
> sipx-users mailing list [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users
> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
> sipXecs IP PBX -- http://www.sipfoundry.org/

_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to