[OpenSIPS-Users] Killing confirmed no-ack dialogs

[Ovidiu Sas]

forgot to cc the list ...

On Wed, Mar 30, 2011 at 4:15 PM, Ovidiu Sas <osas at voipembedded.com> wrote:
> On Wed, Mar 30, 2011 at 3:09 PM, Brett Nemeroff <brett at nemeroff.com> wrote:
>>
>>
>> On Wed, Mar 30, 2011 at 1:47 PM, Ovidiu Sas
>>>
>>> This should be done by the dialog itself (nothing to do from the
>>> script).  It's a bug.
>>>
>>> As for the other question, I haven't followed closely the latest fixes
>>> and additions to the dialog module.
>>> You could try to set the dialog timeout avp to a small value in the
>>> beginning and set it back to a higher value when an ACK is received,
>>> but I haven't checked the code if this will work.
>>>
>>>
>>
>> Where are you saying the bug is? In the UA or opensips?  Obviously I'm
>> dealing with crappy UAs that are broken. But borked UAs shouldn't leave
>> dialogs hanging.
>
> That is correct.  The fix should be made in the dialog module.
>
>
>> So I was thinking about doing the dialog timeout bit like you mentioned, but
>> will that work for an ACK? Wasn't sure if it was really considered a
>> request. Also, don't I need to check something else in the ACK to be sure
>> it's really the right message to trigger the dialog timeout change. Wasn't
>> sure where in the code the state changes when an ACK is received.
>
> Take a look at this sample:
> http://www.opensips.org/html/docs/modules/devel/dialog.html#id293460
> You can validate your dialog and check the status of it.
> But again, I'm not sure that the avp will be re-read on subsequent
> in-dialog messages.
> You can give it a try.
>
>
>> Thanks,
>> Brett
>>
>>
>