According to the new frontpage on dev.openwengo.com and also some mails I've
seen NG is targeted towards being "operator agnostic" or "provider independent",
at the same time implying that Classic is not so much. OTOH, Classic too has a
white label option, which could be used to rename the application to something
else than Wengo.
I would be interested to know more about this. If I wanted to use Classic with
my own SIP Proxy, what obstacles would I need to overcome?
1) The inside content of WengoPhoneClassic is in fact a page on Wengo's portal,
need to replace that.
2) The server end of the http-tunnel functionality is not available. Need to
live without it or make my own.
3) Even with the SIP Profile tab enabled at build time, it is reset to the Wengo
values at each restart of the phone. This should be easily corrected.
4) There could be more bugs like the one above, because Classic has not been
thorougly tested other than as a part of the Wengo service. The question is
then, how many such bugs should one expect to stumble upon?
5) The developers paid for by Wengo do not prioritize fixing such bugs and might
be reluctant to incorporate patches. Need to fix such bugs myself.
I guess another means to the same end is to ask
a) How long until WengoPhoneNG is in a usable state?
henrik
--
[EMAIL PROTECTED]
+358-40-5697354
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
