On Thu, Jan 6, 2011 at 6:47 PM, [email protected] <[email protected]> wrote:
> Just thinking out loud here but... why all of the integrations? Would it > not be way better to spend energy in other areas, not bloating the system up > with too many things? > Bloating? I don't consider sipx bloated, but everyone has an opinion (me too). > > For example, something I've wanted to see since I've started using sipx, a > truly distributed system, where there is no MAIN box that can fail, any > system can take over, any system can store/retrieve voicemail from one or > more voicemail servers, etc. > That is a work in progress. Whereas the dimdim integration was more likely a very minimal configuration issue because the dimdim meeting was hosted elsewhere. It's integrations like this that help to attract more people to the project and keep it robust. The current development show a lot of contributions being made by ezuce to forward that goal, but it will take months, not days to reach that kind of integration. Stop any other integration efforts in lieu or "not until this is done is not in the mantra of many software development firms. > > Secondly, even more important, running separate openfire or openmeeting or > other servers on their own isn't a big deal and is a better method anyhow, > letting the phone system do what it does best. > Not necessarily, because then a lot of other information would have to be transported and exposed in order to make IM integrate the way it does within sipx. That's not a real good example to have "separate or off somewhere else", openfire has to read a lot of time sensitive information from a secure location, which would be "inside sipx". > > Seems to me what would really make sipx kick butt is being able to > integrate it with other products by giving it the capabilities to seamlessly > tie into, bridge, with those various products. Getting LDAP working and > other such centralized authentication protocols would really help tie things > together but a bridge to openfire and what ever will replace dimdim for > example would rock and keep the system nice and clean, and lean. > > Why trust just to LDAP. As you have learned LDAP is one thing, but Active Directory is another. a SSO service would also be "kick butt", but what is it that people will get behind, test and work toward together? If so, which one? Is this before or after "truly distributed" is done? > > Mike > > > > > On Thu, 06 Jan 2011 18:19:16 -0500, Matt White wrote: > >>>> Tony Graziano 01/06/11 6:12 PM >>> > >>>> > >>>> Yes it seems like everyone with a dimdim account got the same email. > >>>> its no longer available to "anyone" except >>>subscribers, who won't > >>>> be able to renew it anymore. Sad, but it happens. The search begins! > >>>> > > Sometime ago we played with integrating openmeetings with sipx. The two > > ran on the same box without any glaring issues and a quick hack was > passing > > credentials. Openmeetings is actually quite capable. Might be > something > > to look t for version 5.+ > > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
