<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"></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>And another issue…</div><div><br></div><div>With a call that went to a carrier that does support sst, I see they refreshed the call at 15 seconds into it. Or, 15 seconds before the session expired. You can look at it either way. They included the following in their refresher INVITE:</div><div><div> Session-Expires: 90;refresher=uac</div><div> Min-SE: 90</div></div><div><br></div><div>So they've bumped the timer to 90 seconds from my 30. Cool. It seems the sst module doesn't see this refresh, and the dialog module still doinks the call at 30 seconds into it. Bummer. Is this normal?</div><div><br></div><div>On the initial INVITE I create the dialog with create_dialog() then set the flag for the sst module. </div><div><br></div><div><br></div><div><br></div><div>- Jeff</div><div><br></div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Jeff Pyle <<a href="mailto:jpyle@fidelityvoice.com">jpyle@fidelityvoice.com</a>><br><span style="font-weight:bold">Reply-To: </span> OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br><span style="font-weight:bold">Date: </span> Thu, 27 Jan 2011 13:49:44 -0500<br><span style="font-weight:bold">To: </span> OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br><span style="font-weight:bold">Subject: </span> [OpenSIPS-Users] sst module killing calls<br></div><div><br></div><div><div 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></div></div></span></body></html>