It does not address how the proxy will glom onto all the interfaces in a system unless additional coding takes place. This will always create an issue, especially if the startup script fails to run as a result due to errors...
How the services glom onto an interface (no matter which services) still needs to be addressed. On Wed, Sep 29, 2010 at 9:00 AM, Nico (sipxecs) <[email protected]>wrote: > Oops the previous message was sent prematurely... > Hi Devs, > > On a system with multiple interfaces, freeswitch fails to "do the right > thing" w.r.t. interface choice. > > In SIPXECS the ip address is specified on the server page. Due to a > $${local_ip_v4} in the sofia config file it consistently chooses the wrong > address there. > The config file is allready generated to reconfigure the sip-port to > 15060. so this should be a fairly minor fix IMHO. > > The request is to insert the configured ip address in the configfile for > the sip-ip & rtp-ip tags. This makes the media-services work miracously in > a multi homed system. > instead of missing failing auto attendant, conferences & voicemail. > It does improve stability though by relying on explicit in stead of > implicit configuration of core functionality. > > Kind regards, > Nico > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
