Hi Bogdan,<div><br></div><div>I get a very similar behavior as what Jeff gets. I can see the re-INVITE coming and I'm sure that it goes through loose_route block. I can also see the "Update by a REQUEST" log. Here's a snippet of the logs after getting the re-INVITE:</div>
<div><br></div><div><div>DBG:dialog:dlg_onroute: route param is '04e.1dc98a86' (len=12)</div><div>DBG:dialog:lookup_dlg: ref dlg 0x780a4fe0 with 1 -> 3</div><div>DBG:dialog:lookup_dlg: dialog id=1755880657 found on entry 3648</div>
<div>DBG:core:parse_headers: flags=48</div><div>DBG:core:parse_to_param: tag=9979</div><div>DBG:core:parse_to: end of header reached, state=29</div><div>DBG:core:parse_to: display={}, ruri={sip:NXXNXXXXXX@OPENSIPS.IP:5060}</div>
<div>DBG:dialog:next_state_dlg: dialog 0x780a4fe0 changed from state 4 to state 4, due event 8</div><div>DBG:dialog:dlg_onroute: sequential request successfully processed (dst_leg=0)</div><div>DBG:dialog:get_dlg_timeout: invalid AVP value, use default timeout</div>
<div>DBG:dialog:dlg_update_cseq: dlg 0x780a4fe0[0]: cseq is 1</div><div>DBG:dialog:run_dlg_callbacks: dialog=0x780a4fe0, type=16</div><div>DBG:sst:sst_dialog_request_within_CB: Update by a REQUEST. INVITE</div><div>DBG:core:parse_headers: flags=ffffffffffffffff</div>
<div>7fcf80a53e41f75c431e5b7d0300c238@OPENSIPS.IP: entering loose_route block..</div></div><div><br></div><div>Dialogs still expire after the timeout set by sst module. What else can I check to see where might probably be wrong?</div>
<div><br></div><div>Thanks!</div><div><br></div><div>Regards,</div><div>Ronald</div><div><br><div class="gmail_quote">On Thu, Feb 3, 2011 at 6:23 AM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi Jeff,<br>
<br>
are you sure your re-INVITE is going through loose_route() and attached to the dialog context (to update it) ?<br>
<br>
if running in debug mode, at re-INVITE time you could see a log from SST module like "Update by a REQUEST..."<br>
<br>
Regards,<br>
bogdan<br>
<br>
Jeff Pyle wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
And another issue…<br>
<br>
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:<br>
Session-Expires: 90;refresher=uac<br>
Min-SE: 90<br>
<br>
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?<br>
<br>
On the initial INVITE I create the dialog with create_dialog() then set the flag for the sst module.<br>
<br>
<br>
<br>
- Jeff<br>
<br>
<br></div>
From: Jeff Pyle <<a href="mailto:jpyle@fidelityvoice.com" target="_blank">jpyle@fidelityvoice.com</a> <mailto:<a href="mailto:jpyle@fidelityvoice.com" target="_blank">jpyle@fidelityvoice.com</a>>><br>
Reply-To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org" target="_blank">users@lists.opensips.org</a> <mailto:<a href="mailto:users@lists.opensips.org" target="_blank">users@lists.opensips.org</a>>><div class="im">
<br>
Date: Thu, 27 Jan 2011 13:49:44 -0500<br></div>
To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org" target="_blank">users@lists.opensips.org</a> <mailto:<a href="mailto:users@lists.opensips.org" target="_blank">users@lists.opensips.org</a>>><div class="im">
<br>
Subject: [OpenSIPS-Users] sst module killing calls<br>
<br>
Hello,<br>
<br>
I'm experimenting with the sst module once again. It's configured as follows:<br>
<br>
modparam("dialog|sst", "timeout_avp", "$avp(s:dialog_timeout)")<br>
modparam("sst", "sst_flag", 6)<br>
modparam("sst", "min_se", 30)<br>
<br>
Dialogs are set for all calls.<br>
<br>
Calls I sent contain the following header:<br>
Session-Expires: 30<br>
<br>
So far, so good. When I get a 200 OK from a carrier that supports sst, I see the following headers:<br>
Supported: timer<br>
Session-Expires: 30;refresher=uas<br>
<br>
(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.<br>
<br>
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.<br>
<br>
<br>
- Jeff<br>
<br></div><div class="im">
------------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
</div></blockquote><div><div></div><div class="h5">
<br>
<br>
-- <br>
Bogdan-Andrei Iancu<br>
OpenSIPS Event - expo, conf, social, bootcamp<br>
2 - 4 February 2011, ITExpo, Miami, USA<br>
OpenSIPS solutions and "know-how"<br>
<br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div>