[OpenSIPS-Users] Matching dialog IDs

[Răzvan Crainea]

Hi, Kingsley!

Just open an issue on OpenSIPS github page[1], it would be easier for us 
to keep track of them. You will find the procedure there.
I think the feature is to also provide the dialog id in the event.

[1] https://github.com/OpenSIPS/opensips/issues

Thanks,

Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com

On 4/9/21 1:58 PM, Kingsley Tart wrote:
> What would you like me to specifically request, and how do I submit a
> feature request for OpenSIPS?
> 
> Cheers,
> Kingsley.
> 
> On Fri, 2021-04-09 at 11:01 +0300, Răzvan Crainea wrote:
>> Hi, Kingsley!
>>
>> I am afraid your approach is the correct one, and currently there's no
>> other workaround, rather than the one you already did :(.
>> Last year I've reworked the did and dlg_id in a few places to have a
>> more consistent value, but somehow I missed the event's one. Ideally, we
>> should have only two formats: the hex one (the one in Record-Route,
>> dlg_list and $DLG_did), and the db_id one (the integer in DB).
>> I will try to rework this in the master branch, any chance you could
>> open a feature request for it?
>>
>> Best regards,
>>
>> Răzvan Crainea
>> OpenSIPS Core Developer
>> http://www.opensips-solutions.com
>>
>> On 4/9/21 2:04 AM, Kingsley Tart wrote:
>>> Hi,
>>>
>>> With OpenSIPS 3.1, on one example call I noted that:
>>>
>>>    * did in Record-Route header was 5af.b5c82a2
>>>    * dlg_id in DB table was 17201388227675
>>>    * event_route[E_DLG_STATE_CHANGED] got hash_entry=4005 (param 1) and
>>>      hash_id=44207195 (param 2)
>>>
>>> I see these 3 sets of values are all essentially the same thing but in
>>> a different format.
>>>
>>> In a way it feels wrong to ask this but, is this guaranteed behaviour?
>>>
>>>
>>> eg in the event route, this expression:
>>>
>>> 	$(param(1){s.dec2hex}{s.reverse}{s.tolower}) + "." +
>>> $(param(2){s.dec2hex}{s.reverse}{s.tolower});
>>>
>>> evaluates to "5af.b5c82a2", ie the did in the Record-Route header, and
>>> that in MySQL I could derive the dlg_id value in the DB table (which
>>> was 17201388227675) by doing XXXX*POW(2,32)+YYYYYYY where XXXX is the
>>> value of $param(1) and YYYYYYY is the value of $param(2).
>>>
>>> There may be a better way to do all this, but I'm trying to figure out
>>> ways I can update the DB with some additional info at BYE time and
>>> haven't currently found out how to do this more properly.
>>>
>>> (again, this feels the wrong way to do it, but I have not yet found a
>>> better way).
>>>
>>> Cheers,
>>> Kingsley.
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> 
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>