o Juha Heinanen on 11/22/2011 12:19 PM:
stafan,
thanks for thorough explanation on sems session timers. i defined in my
sbc profile
## session timer:
enable_session_timer=yes
session_expires=300
minimum_timer=120
#session_refresh_method=UPDATE_FALLBACK_INVITE
#accept_501_reply=yes
and made a test call between two sip UAs. then i killed the other one
with kill -KILL.
at time 12:17:57 sems sent re-invite to both UAs and got reply only from
the alive one. at 12:18:05 my sip proxy responded with 408 Request
timeout to sems regarding the re-invite to the dead UA.
for some reason sems didn't react to that at that time, but waited until
12:20:25 before it sent byes to both parties.
why the wait of more than two minutes after 408 before sending the byes?
SEMS is trying the refresh at half of the timer value (at 150s if
proxy or other end didn't lower the value), and ending the call when
the session expires, i.e. at the timer of 300s.
I think you are right that it could already end the call before - when
it detects that the refresh is failed. Another possibility would be to
retry the refresh once more and then end the call.
Stefan
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
