Ralf Schlatterbeck wrote:
I'm using wengo in the following as a placeholder for a future name... Now that Wengophone is no longer supported by a single company I'd propose the following changes to the branding configuration, my goal here is to make wengophone better interoperable with other SIP infrastructures, e.g. FWD or ekiga.net or commercial SIP-to-PSTN gateway providers.- Remove special-casing from code, make Wengo just another SIP-client (possibly the preferred-one by default but user-changeable) - Put some of the Backend-Services configuration-variables which are currently wengo-specific into the SIP-Server configuration, namely: - Testcall Audio/Video This might fall back to a generic service (preconfigured like currently the testcall for wengo) if no testcall service is available with the chosen infrastructure - Forum (!) but of course the link to the wengo forum should also be in teh client - FAQ (same as for forum there should be a client-specific faq but many infrastructures have their own faq) - Phone-Books/Directory (both internal and external) (e.g. ekiga.net does have it's own phonebook) - Account Creation/Maintenance/Phone Number/Lost Password/Selfcare What do others think? Ralf
Great proposals IMO. Please submit patches for review Thanks Vadim _______________________________________________ Wengophone-devel mailing list [email protected] http://dev.openwengo.com/mailman/listinfo/wengophone-devel
