[Users] ACK and re-INVITE ordering

[Bogdan-Andrei Iancu]

HI Jerome,

Jerome Martin wrote:

>>yes please - open a feature request to have it in mind for the next release.
>>Just to be sure - the enhancement I was referring at is not about adding 
>>additional information about the dialog state as RR param, but just a 
>>function to access the internal dialog state.
>>    
>>
>
>Does it mean transaction information is kept in-memory as part of dialog
>state, and I could check if last ACK was processed ? I can't really see
>how this state information would be structured/what it contains.
>  
>
see in modules/dialog/dlg_hash.h the dlg_cell structure, state field. 
There is no state yet saying if ACK was received or not, but I guess can 
be added without problems

>  
>
>>>- I was really wondering what those functions would do that RR
>>> module's add_rr_param and check_route_param don't.
>>> Could anyone help me to understand this ?
>>> 
>>>      
>>>
>>see above; the dialog module puts a dialog id in as RR param just for a 
>>fast dialog matching - the information about the dialog parameters, its 
>>state and so on are kept in memory by the dialog module.
>>    
>>
>
>Thanks, I misunderstood how it works. Now it makes sense :-)
>Do you plan to add an avp access to store/access arbitrary per-dialog
>information in-memory ? Like declaring avps to be dialog-specific as
>dialog module parameter, than just using avp the usual way ?
>  
>

the dialog module will export a new PV containing the dialog state.

Regards,
bogdan