[OpenSIPS-Users] [OpenSIPS-Devel] [RFD] dialog expire event in dialog module

[Bogdan-Andrei Iancu]

Sounds like a plan for me :)..

Regards,
Bogdan

Ovidiu Sas wrote:
> For now, let's stick with the flags and we will build later on extra
> functionality if needed (like dropping BYEs and rearm timer).
>
> Regards,
> Ovidiu Sas
>
> On Thu, Oct 9, 2008 at 9:15 AM, Bogdan-Andrei Iancu
> <bogdan at voice-system.ro> wrote:
>   
>> Hi Ovidiu,
>>
>> To be honest I like also the idea of triggering a route when the timeout
>> happens, but the biggest problem is that all routes (and script functions)
>> are design to receive as parameter a SIP message - actually the whole script
>> is design to be triggered by messages.
>> In our case, there is no message.. (not even a transaction)....so, it is
>> really difficult to plug there a route for this event........
>>
>> Maybe we can do sending (internally) the BYE mandatory and use the
>> local_route() as timeout_route[] and allow to drop the BYE, etc....
>>
>> Regards,
>> Bogdan
>>
>> Ovidiu Sas wrote:
>>     
>>> I like the idea of having a timeout_route, but if this is to much of a
>>> headache, the flags will do it.
>>> The timeout_route can provide a more refined control over the dialog
>>> timeout handling.
>>>  - send BYE's,
>>>  - terminate the dialog without sending BYE's,
>>>  - re-arm the timer and keep the call going.
>>>
>>> With flags, there will be a script callback only when the dialog is
>>> terminated and BYEs are sent out (the local_route callback).  No
>>> script callback for silent dialog expiry.
>>>
>>>
>>> Regards,
>>> Ovidiu
>>>
>>> On Mon, Oct 6, 2008 at 6:29 AM, Bogdan-Andrei Iancu
>>> <bogdan at voice-system.ro> wrote:
>>>
>>>       
>>>> Hi everybody,
>>>>
>>>> I want to bring into discussion an older topic as we need to take a
>>>> decisions on this - it is what to do when a dialog gives timeout in
>>>> dialog module.
>>>>
>>>> Right now, nothing is done. The dialog module simply stops monitoring
>>>> the dialog without taking any action.
>>>>
>>>> There were several demanded actions to be done, as:
>>>>   - accounting (to be able to account hanged calls)
>>>>   - send BYE in both directions
>>>>   - etc.....
>>>>
>>>> Of course, we are looking for a mechanism to cover as many cases as
>>>> possible and not to hardcode one of them.
>>>>
>>>> So, I would like to get some feedback on:
>>>>   1) what are the actions that could be done when a dialog gives timeout
>>>>   2) how the implementation should look like?
>>>>
>>>> For 2), we already have some ideas:
>>>>   A) use bitmask flags to select the action to be done at dialog
>>>> timeout event.
>>>>   B) set a route to be called when the dialog timesout
>>>>
>>>>
>>>> So, ideas and comments are welcomed.
>>>>
>>>> REgards,
>>>> Bogdan
>>>>
>>>> _______________________________________________
>>>> Devel mailing list
>>>> Devel at lists.opensips.org
>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
>>>>
>>>>
>>>>         
>>>       
>>     
>
>