<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div>Hello,</div><div><br></div><div>I'm experimenting with the sst module once again. It's configured as follows:</div><div><br></div><div> modparam("dialog|sst", "timeout_avp", "$avp(s:dialog_timeout)")</div><div><div> modparam("sst", "sst_flag", 6)</div><div> modparam("sst", "min_se", 30)</div></div><div><br></div><div>Dialogs are set for all calls.</div><div><br></div><div>Calls I sent contain the following header:</div><div> Session-Expires: 30</div><div><br></div><div>So far, so good. When I get a 200 OK from a carrier that supports sst, I see the following headers:</div><div><div> Supported: timer</div><div> Session-Expires: 30;refresher=uas</div></div><div><br></div><div>(The 30 second expiration is an experimentally low value.) When I get a 200 OK from a carrier that doesn't support sst, I don't see those two headers. In this case it seems the sst module still sets the dialog expiration to 30 seconds, after which the call goes poof.</div><div><br></div><div>Is that correct behavior? If neither end advertise support for sst, and neither side is going to refresh it, it seems a bit strange the sst module would still cause the dialog to expire at the expiration time.</div><div><br></div><div><br></div><div>- Jeff</div><div><br></div></body></html>