Hello,

Klaus Darilion wrote:

But to make it even more attractive, openwengo ng should:

- being buildable on Windows with free software. That means free qt4 + mingw. I've tried several times but never suceeded. Open source software which can't be built without commercial products are useless for most developers.

I agree, and this is something being worked on. Feel free to come on #openwengo on IRC or to post a message on this mailing list to share the difficulties you had in trying to use mingw.We could work on improving the existing documentation from your comments.

- being independent of wengo. Probably this is against your/wengo's business case, but a configuration option (not a compile option) which tells openwengo the http URL to download the provisiong data, or an option to allow direct configuration of the SIP configuration is necessary.

It is one of the goals that we want to achieve for NG. Provider independency will be at the root of NG.

- calling outside the home domain. I do not know if this is doable with ng, but I tried classic and it did not worked to dial any SIP URI outside the local domain just by entering the SIP URI, eg. sip:[EMAIL PROTECTED] Also the buddy list and presence should be open to all SIP domains.

If your SIP provider allow this, i don't see any reason why you couldn't call any SIP URI outside the local domain. As for the buddy list and presence, i don't think it is something that we have decided yet, any suggestion is welcome.

Thank you very much for your suggestions and comments.

All the best,

--
Julien Gilli
.

_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel

Reply via email to