[OpenSIPS-Users] trying to understand the E_DLG_STATE_CHANGED

Khalil Khamlichi khamlichi.khalil at gmail.com
Fri Sep 15 15:46:16 EDT 2017


Hi everyone,

I am trying to understand dialog module eventing system.

I have added this route :


event_route[E_DLG_STATE_CHANGED] {

    fetch_event_params("$avp(a);$avp(b);$avp(c);$avp(d);$avp(e);$avp(f)");

    cache_raw_query("redis:0", "PUBLISH serv1
fetch_event_params=$avp(a),$avp(b),$avp(c),$avp(d),$avp(e),$avp(f)",
"$avp(res)");

}


so for each event I can watch an entry

1505503997.413642 [0 127.0.0.1:39734] "PUBLISH" "serv1"
"fetch_event_params=3917,339471624,1,3,<null>,<null>"
1505503997.524535 [0 127.0.0.1:39762] "PUBLISH" "serv1"
"fetch_event_params=3917,339471624,3,4,<null>,<null>"
1505504018.809746 [0 127.0.0.1:39840] "PUBLISH" "serv1"
"fetch_event_params=3917,339471624,4,5,<null>,<null>"


I understand that

a = hash_id of dialog
b= hash_entry of dialog
c = old_state
d = new_state
e & f = do not exist and here just to prove that they do not exist.

but I don't understand how to use the information of a & b to track dialogs
? if there a function that when fed those parameters gives us callid for
example ?

Thanks in advance.

Kkh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20170915/d193779c/attachment.html>


More information about the Users mailing list