I'm a little confused here. I haven't used SST before so I'm sure I'm missing some background here.. But if I enable SST module, and set an expires at say, 120 seconds, don't I get an invite refresh roughly every 120 seconds? then if I don't I send a BYE out both ways.
What part of that may be unsupported. Part I'd be worried about is if I tell the UAC "Session-expires: 120" and it simply doesn't care, doesn't send the refresh and then BYEs get sent out and the dialog is torn down.. ? -Brett On Thu, Mar 5, 2009 at 10:47 AM, Iñaki Baz Castillo <[email protected]> wrote: > 2009/3/5 Brett Nemeroff <[email protected]>: > > Question, do SST help the situation? Is it widely accepted enough in the > > protocol to provide some backup mechanism to maintaining dialog state in > the > > event of a lost BYE. > > Sure, but keep in mind that a proxy CANNOT generate in-dialog > requests, so SessionTimers must be suppoerted (and enabled) in caller > and/or callee. If no one of them supports/uses SST then the proxy can > do *nothing*. > For example, a B2BUA *can* use SST in both legs to check the dialog > state since a B2BUA behaves as a callee for the caller and as a caller > for the callee. This is never possible with a proxy. > > > > BTW, how is a BYE accounted for in ACC when generated locally because of > an > > expired dialog? > > Use local_route to account it as any other BYE. > > -- > Iñaki Baz Castillo > <[email protected]> > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
