Scott Lawrence wrote: > On Fri, 2009-05-22 at 14:11 +0100, Damian Dowling wrote: > >> SipXconfig running on a single server I can understand, it makes >> everything a lot simpler from a programming point of view. Although it >> would be nice for load balancing reasons to allow users to access their >> accounts via different servers. > > That's a feature that's being looked at, but we don't have any firm > plans yet. >
We don't have "un-firm" plans either ;-) Load balancing of java servlets (which is what sipXconfig really is) has little to do with what sipXecs is now doing to load balance SIP services in HA environment. sipXconfig is using very standard technologies and protocols: it's really mostly a question of configuration and not a question of writing code differently. >> However, I find storing the phone profiles only on the primary server >> surprising. It would improve redundancy if the profiles were also stored >> on the secondary server. Is this planned for the future? > > At present, the way most phones retrieve configuration information is > too limited - there is no way to tell the phones "try one of the > following redundant locations". However, that is a feature of a new > Technical Recommendation on SIP User Agent Configuration that is being > worked on in the SIP Forum [1]. The latest draft documents for that > group are available [2]. > > I hope and believe that we will be able to include support for this new > standard in sipXecs 4.2 (we already support a significant fraction of > it). Whether or not users can leverage that depends on what phones > support it (ask your phone vendors). > > [1] http://www.sipforum.org/content/view/311/253 > [2] > http://www.sipforum.org/component/option,com_docman/task,cat_view/gid,66/Itemid,75/ > In addition to what Scott said: If you want it you can set up a provisioning server separate from a primary server even today (replicate provisioning directory, set-up FTP/TFTP/HTTP servers, set up DNS so that phones find the best provisioning server. I saw little demand for that though: when you actually configure your phones your provisioning server is up (otherwise you cannot configure the phones). Serving static files has negligible impact on primary server performance. And finally if sipXconfig is stopped other sipx services are still fully functional. Separating provisioning server is probably more important from "no-access behind firewall" perspective. D. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
