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
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
Bogdan,
How about an event route that lets you use script logic to modify the event
prior to emitting it?
Sent from my iPhone
On May 18, 2015, at 4:57 AM, Bogdan-Andrei Iancu bog...@opensips.org wrote:
Hi Dan,
I will do the backport to 1.2.0 - thank you for testing.
Now, on your
Hey Brett,
For your info, I have tried a similar thing, raising another event out
of the E_DLG_STATE_CHANGED route however for some reason I could not
access the avps in there, so not much more info than the original event had.
DanB
On 18.05.2015 15:23, Brett Nemeroff wrote:
Bogdan,
How
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
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
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
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:
Hi Ben,
Can u please give me an example?
Ta,
DanB
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
OK, let's move this on the #504 issue.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 11.05.2015 15:11, DanB wrote:
For now no emergency since we went back to using Accounting Start/Stop
over EVI. Works like a charm.
Would be interesting if we
The usage of $dlg_val is described in the module documentation [1]. You set and
read them just like any other pseudo-variable:
$dlg_val(foo) = “bar”;
The only thing I don’t know is whether these variables can be accessed from the
E_DLG_STATE_CHANGED event route, as it is not clear whether the
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
You can add variables to the Dialog using $dlg_var.
Ben Newlin
From: DanB
Reply-To: OpenSIPS users mailling list
Date: Monday, May 11, 2015 at 8:11 AM
To: Bogdan-Andrei Iancu, OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Dialog start event over EVI
For now no emergency since we
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 :
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
For now no emergency since we went back to using Accounting Start/Stop
over EVI. Works like a charm.
Would be interesting if we could add pseudovariables to
E_DLG_STATE_CHANGED so we can load more useful info inside.
Thanks,
DanB
On 11.05.2015 14:08, Bogdan-Andrei Iancu wrote:
Right good one
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
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,
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
19 matches
Mail list logo
