On Thu, Nov 13, 2008 at 02:46:28PM +0100, Vadim Lebedev wrote:

> We have a another phapi based sip stack:  Verona 
> (http://www.mbdsys.com/vopensource/verona)  where  correct behaviour is 
> implemented  so if somebody could rig a patch  proting  this to QuteCome
> we'd be happy to accept it.

Uh, my impression was that Verona *is* the sip part of qutecom?

We're seeing all sorts of hard-to-reproduce problems:
I'm adding the kvats issues on our tracker for reference. Vadim, you and
Laurent do have an account (write to me personally if you need to reset
the password). I hope to make the tracker public soon.
- instability on network loss
  http://tracker.kvats.net/kvats/issue101
  http://tracker.kvats.net/kvats/issue83
  and probably also
  http://tracker.kvats.net/kvats/issue116
- instability when using conferences (both audio and video):
  http://tracker.kvats.net/kvats/issue114
- very seldom problems when putting a call on hold:
  http://tracker.kvats.net/kvats/issue82
- Presence: Sometimes the presence infrastructure (we're using p2p
  presence) sends weird presence information with some default values.
  We've worked around this by sending presence info via an
  application-timer
- Other hard-to-reproduce problems
  http://tracker.kvats.net/kvats/issue94

Maybe many of these could be fixed by using Verona? Laurent seemed to be
very happy with Verona when I met him @ innovationdays. At that time I
thought that Verona *was* Qutecoms SIP part.

We're facing troubles due to the problems above. So I'd help to port
Verona to Qutecom -- but I'd certainly need help. Vadim could you
outline what needs to be done? Are there hopes to fix the problems above
by porting to Verona?

Ralf
-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  Fax:   +43/2243/26465-23
Reichergasse 131                        www:   http://www.runtux.com
A-3411 Weidling                         email: [EMAIL PROTECTED]
osAlliance member                       email: [EMAIL PROTECTED]
_______________________________________________
QuteCom-dev mailing list
[email protected]
http://lists.qutecom.org/mailman/listinfo/qutecom-dev

Reply via email to