Frankly, i cannot remember why i added that warning. And i must add that i do not pay that much attention to most of the debug log messages. But if you feel like SEMS is telling something wrong in that place, then please remove it. We definitly do not want to lead application developer to some wrong conclusions ;-)
Cheers Raphael. Stefan Sayer wrote: > Hello, > > I get this advice from SEMS: > "Dialog should have been terminated by the app !!!" > when in b2bua callee leg with relayed invite a negative FR is received, > e.g. failed call for auth_b2b application. When callee leg FR comes in, > caller leg does bye() in Pending state (onOtherReply(), terminateLeg()), > but has INVITE as UAS transaction. The thing is, I think it is correct > to call bye() from B2BSession regardless of the dialog state, as it is > not possible to determine whether the INVITE is UAS or UAC transaction, > at least without looking at uac/uas transaction list. > > the case I can imagine where this situation hints to an application > error is INVITE UAS transaction and the dialog pending (i.e. early > media), and the app calling bye() instead of sending FR bye itself. > > So I would remove that error message and just do nothing in that > situation; the application developer would notice anyway if the dialog > is not ended, this is not an error that occurs in an unforeseen situation. > > Is that correct? Or did I miss something? > > Stefan > > _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
