Hello, Ralf and osAlliance folks Ralf Schlatterbeck wrote:
Hello Vadim, I'm glad you take over coordination of the development of Wengo (or whatever the future name of it will be). I'm working with osAlliance, an alliance of open source companies in Austria, you have already had contact with Roland Alton-Scheidl. We have a project with a major mobile phone provider in Austria to provide them with a free sip client they want to use for a new service they will be launching. I'm coordinating this project technically. So far we've identified the following issues we want to tackle -- I'm giving you these details so that we may be able to join forces on some of them:
It'll be great iw we could join forces
- general stabilisation - SIP Peer-to-peer presence (rather high prio)
I'm working in this right now, you can see stuff comitted on http:://repo.mbdsys.com/openwengo/wengophone-2.2 I expect to finish low level stuff today (phapi and PhapiWrapper) and my collegue will do GUI stuff today and tomorrow... Maybe by Friday we'll have something testable
- IM even if no presence info is available or if other party is offline -- many IM architectures store messages in the infrastructure while a client is offline. So we need to be able to use IM even if no presence is available or presence indicates offline status. Some of this was quite easy to get going, but in the infrastructure we use for testing I'm still not able to send IM -- they have no presence infrastructure currently :-(
You mean the sfotphhone storing messages locally?
- Video-Codec bug in H.263 implementation that prevents interoperability with other SIP clients, e.g. Ekiga. This is documented on the ekiga page at http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F and is on the wengo bug-tracker at http://dev.openwengo.org/trac/openwengo/trac.cgi/ticket/747 might be not-so-high prio for us as getting IM and Presence going is higher on the list. We've not looked at Video so far and haven't confirmed this bug in our tests yet.
I remember some time ago somebody on ML propose patch revamplin ph_codec stuff to include rtp muxer/demuxer the bug also fixed H263 payload related issue. It would be nice to ressurect this patch
- Python integration -- I've seen that on the trunk there is a python wengo version. Is there something I can look at/read to further understand how to use the python integration? We will have to provide a connection to a provisioning infrastructure and parsing that config info in python would be easier for us...
Aurelien and Thomas form openwengo team know this stuff well, may be teil''l be kind enough to respond
Hope some of these are on your roadmap, too, so we can contribute to the project. I'll probably be posting some of these issues above as questions to the mailinglist. (I'm sending this mail to our internal voip-list we use to coordinate the project, feel free to cc the list (about 5 people) if you want to answer this mail) Best Regards, Ralf
Thanks Vadim P.S. Can i rpost this to wengophone-devel list? _______________________________________________ Wengophone-devel mailing list [email protected] http://dev.openwengo.com/mailman/listinfo/wengophone-devel
