[OpenSIPS-Users] Dialog start event over EVI

Bogdan-Andrei Iancu bogdan at opensips.org
Mon May 18 17:21:47 CEST 2015 

OK, let me know if it works for you (it should, with the current code).

Be happy (user),

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 18.05.2015 18:12, DanB wrote:
> Hey Bogdan,
>
> This one sounds good enough for my use case. I will need a bit of time 
> to test it but if it works with dialog vars then I am a happy user ;).
>
> Thanks for your efforts!
>
> DanB
>
> On 18.05.2015 17:05, Bogdan-Andrei Iancu wrote:
>> Dan, the biggest problem I see is how to get the extra information 
>> for that event. You can set a list of vars to be added to the event, 
>> but the question is - what context will be used to evaluated those 
>> vars ? The events do not have a context of themselves - no msg, so no 
>> vars, no script variable, no avps are present.
>>
>> What we should continue doing is to allow the code triggering the 
>> event (like the dialog module in this case) to "make available" a 
>> context with different info - like the "dialog related" variables in 
>> this case.
>> And as Razvan said, this already works - you can intercept the 
>> STATE_CHANGED event in script, use the dialog vars to collect more 
>> info ($dlg_val) and raise a new, more complex event.
>>
>> Regards,
>> Bogdan-Andrei Iancu
>> OpenSIPS Founder and Developer
>> http://www.opensips-solutions.com
>> On 18.05.2015 13:45, DanB wrote:
>>> Hey Bogdan,
>>>
>>> Thanks for your answer.
>>>
>>> I understand the part with custom things added to events. I was more 
>>> like looking for the long shot solution, to define what to put in 
>>> (maybe same way we do for raise_event).
>>>
>>> Regarding solution 2) - tried that but it appears that the avps are 
>>> not longer active in E_DLG_STATE_CHANGED route. Could that be the case?
>>>
>>> Dan
>>>
>>> On 18.05.2015 11:57, Bogdan-Andrei Iancu wrote:
>>>> Hi Dan,
>>>>
>>>> I will do the backport to 1.2.0 - thank you for testing.
>>>>
>>>> Now, on your comments: IMHO it is not wise to add more info to the 
>>>> event - the actual event should notify only on the change of state 
>>>> and that's it; You need extra A and B fields, somebody else C and 
>>>> D, etc... So there is no way to get a consents in term of what and 
>>>> how much additional info should be added.
>>>> The Options I see:
>>>> 1) extend support for events, so you can specify extra vars to be 
>>>> pushed into the event - this is a long shot.
>>>> 2) derive the event - capture the event and build on top of it 
>>>> another custom one, with the additional things you want
>>>> 3) get the original event, and using the dialog ID, make a dlg_list 
>>>> to get all the info from the dialog.
>>>>
>>>> Regards,
>>>> Bogdan-Andrei Iancu
>>>> OpenSIPS Founder and Developer
>>>> http://www.opensips-solutions.com
>>>> On 17.05.2015 14:58, DanB wrote:
>>>>> Hey Bogdan,
>>>>>
>>>>> Thanks for this.
>>>>>
>>>>> I can confirm that the hash_entry and hash_id are now attached to 
>>>>> the event:
>>>>> """
>>>>> #
>>>>> U 2015/05/17 13:55:45.632615 127.0.0.1:60380 -> 127.0.0.1:2020
>>>>> E_DLG_STATE_CHANGED
>>>>> hash_entry::1593
>>>>> hash_id::82596694
>>>>> old_state::4
>>>>> new_state::5
>>>>> """"
>>>>>
>>>>> As inquired in the ticket also, will it be possible here to add 
>>>>> some $avp or dialog variables maybe? From the billing perspective 
>>>>> we will need to know at least user and destination called to make 
>>>>> use of dialog_start event.
>>>>>
>>>>> Ta,
>>>>> DanB
>>>>>
>>>>> On 15.05.2015 17:02, Bogdan-Andrei Iancu wrote:
>>>>>> Hi Dan,
>>>>>>
>>>>>> Could you check the patch I did (see commit e461b65) to provide 
>>>>>> the hash_entry and hash_id for the event ? if ok, I will backport 
>>>>>> to 2.1 too
>>>>>>
>>>>>> Regards,
>>>>>> Bogdan-Andrei Iancu
>>>>>> OpenSIPS Founder and Developer
>>>>>> http://www.opensips-solutions.com
>>>>>> On 11.05.2015 15:08, Bogdan-Andrei Iancu wrote:
>>>>>>> Right good one :D..... We will patch it to include the DID too.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Bogdan-Andrei Iancu
>>>>>>> OpenSIPS Founder and Developer
>>>>>>> http://www.opensips-solutions.com
>>>>>>> On 11.05.2015 14:54, DanB wrote:
>>>>>>>> Hi Bogdan,
>>>>>>>>
>>>>>>>> That is a useful variable indeed (works perfect with 
>>>>>>>> Accounting). Unfortunately have no clue how to include/attach 
>>>>>>>> it to the E_DLG_STATE_CHANGED event.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> DanB
>>>>>>>>
>>>>>>>> On 11.05.2015 13:52, Bogdan-Andrei Iancu wrote:
>>>>>>>>> Hi Dan,
>>>>>>>>>
>>>>>>>>> Try the $DLG_did variable :
>>>>>>>>> http://www.opensips.org/html/docs/modules/1.11.x/dialog.html#id297237
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Bogdan-Andrei Iancu
>>>>>>>>> OpenSIPS Founder and Developer
>>>>>>>>> http://www.opensips-solutions.com
>>>>>>>>> On 09.05.2015 12:23, DanB wrote:
>>>>>>>>>> Hey Bogdan,
>>>>>>>>>>
>>>>>>>>>> Thank you for the tip. I am trying now to use as advised 
>>>>>>>>>> E_DLG_STATE_CHANGED.
>>>>>>>>>>
>>>>>>>>>> I get the following information in the event:
>>>>>>>>>> """
>>>>>>>>>> U 2015/05/09 11:19:59.018404 127.0.0.1:40817 -> 127.0.0.1:2020
>>>>>>>>>> E_DLG_STATE_CHANGED
>>>>>>>>>> old_state::1
>>>>>>>>>> new_state::5
>>>>>>>>>> """
>>>>>>>>>>
>>>>>>>>>> Can you advise me how to add some useful information inthere? 
>>>>>>>>>> I would need to know at least h_entry and h_id for the dialog 
>>>>>>>>>> (so I can kill it from outside) and some other $avps I need 
>>>>>>>>>> for prepaid at the start of the call.
>>>>>>>>>>
>>>>>>>>>> Thanks again!
>>>>>>>>>> DanB
>>>>>>>>>>
>>>>>>>>>> On 07.05.2015 18:42, Bogdan-Andrei Iancu wrote:
>>>>>>>>>>> Hi Dan,
>>>>>>>>>>>
>>>>>>>>>>> As in ACC you cannot do START/STOP and CDRs in the same 
>>>>>>>>>>> time, I suggest to use the CDR event for accounting purposes 
>>>>>>>>>>> and for monitoring the dialog status take a look at the 
>>>>>>>>>>> E_DLG_STATE_CHANGED event:
>>>>>>>>>>> http://www.opensips.org/html/docs/modules/2.1.x/dialog.html#id297207 
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>>
>>>>>>>>>>> Bogdan-Andrei Iancu
>>>>>>>>>>> OpenSIPS Founder and Developer
>>>>>>>>>>> http://www.opensips-solutions.com
>>>>>>>>>>>
>>>>>>>>>>> On 06.05.2015 13:39, DanB wrote:
>>>>>>>>>>>> Hey Guys,
>>>>>>>>>>>>
>>>>>>>>>>>> I am using EVI to generate CDRs out of OpenSIPS. The result 
>>>>>>>>>>>> is that I get one CDR record at the end of the dialog as 
>>>>>>>>>>>> E_ACC_CDR event.
>>>>>>>>>>>>
>>>>>>>>>>>> Now I would need to know also when dialog starts (eg: after 
>>>>>>>>>>>> INVITE is being OKed).
>>>>>>>>>>>>
>>>>>>>>>>>> What is the most recommended way to achieve that? I tried 
>>>>>>>>>>>> setting evi_flag but it appears that works only if I do not 
>>>>>>>>>>>> set cdr_flag. Am I right in that assumption? Are both 
>>>>>>>>>>>> evi_flag and evi_missed_flag options suppressed by cdr_flag?
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks in advance for your feedback!
>>>>>>>>>>>> DanB
>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> 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
>>>>>>
>>>>>
>>>>
>>>
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20150518/5820232e/attachment-0001.htm>

More information about the Users mailing list