Nice! Although I'll be waiting for the next RC before I'll start using it.
Thanks! Bert -----Original Message----- From: Stefan Sayer [mailto:[email protected]] Sent: dinsdag 10 februari 2009 16:36 To: Bert Fraterman Cc: [email protected] Subject: Re: [Sems] AmSipDispatcher 'could not dispatch reply' error Hello, o Bert Fraterman [02/10/09 16:19]: > I have tried the patch just now, but calls aren't closed down properly. > > Since I'm calling the setStopped() from a different thread, it looks > like I'm stuck with sending a bogus event, which is ok for workaround, > but it would be nice to have it documented. If I figure out how to send > in a patch I might write something in the doxygen comments about it. that would be great. > > Developer FAQ might be nice, it could be added to the main documentation > page. I have added the optional parameter to the setStopped function now (r1266). Stefan > > Thanks for your help, > Bert > > -----Original Message----- > From: Stefan Sayer [mailto:[email protected]] > Sent: dinsdag 10 februari 2009 15:59 > To: Bert Fraterman > Cc: [email protected] > Subject: Re: [Sems] AmSipDispatcher 'could not dispatch reply' error > > > o Bert Fraterman [02/10/09 14:32]: >> Hi Stefan, >> >> thanks for your comments, I'm starting to get a better insight into > the >> internals of SEMS. >> >> I did some more tracing and found that the session gets stuck on the >> 'waitForEvent();' line in the AmSession main loop. > btw have you tried the other fix that I sent with the mail (i.e. going > into Disconnecting instead of Disconnected state when doing bye())? > > Stefan -- Stefan Sayer VoIP Services [email protected] www.iptego.com IPTEGO GmbH Wittenbergplatz 1 10789 Berlin Germany Amtsgericht Charlottenburg, HRB 101010 Geschaeftsfuehrer: Alexander Hoffmann _______________________________________________ Sems mailing list [email protected] http://lists.iptel.org/mailman/listinfo/sems
