You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
When using db_redis for dialog realtime storage, I've found every dialog entry is writing to a single hash with a null value:
1564282556.519166 [7 127.0.0.1:33838] "HMSET" "" "hash_entry" "2461" "hash_id" "4292" "callid" "39d9ba94b0e311e9b879c08c6015a900@10.0.0.2" "from_uri" "sip:61400123123@10.0.0.2:5060;user=phone" "from_tag" "1991956793-3910263728-2361424312-11081056" "to_uri" "sip:61399991234@5.5.5.5;user=phone" "to_tag" "vvFKcF789FU6S" "caller_sock" "udp:10.0.0.2:5060" "callee_sock" "udp:10.0.0.2:5060" "start_time" "1564282556" "state" "3" "timeout" "1486721673" "caller_cseq" "1" "callee_cseq" "0" "caller_contact" "sip:61400123123@10.0.0.2:5060;user=phone" "callee_contact" "sip:10.0.0.3:5060" "caller_route_set" "" "callee_route_set" "" "sflags" "0" "toroute_name" "" "req_uri" "sip:61399991234@kamailio.local" "xdata" "" "iflags" "0"
1564282561.716416 [7 127.0.0.1:33836] "HMSET" "" "hash_entry" "3657" "hash_id" "8250" "callid" "100c26fd-2b86-1238-048a-0cc47a18705a" "from_uri" "sip:61400123123@10.0.0.3:5060" "from_tag" "ye24F58F417BH" "to_uri" "sip:61400123123@kamalio.local" "to_tag" "as2bd0b9fb" "caller_sock" "udp:10.0.0.2:5060" "callee_sock" "udp:10.0.0.2:5060" "start_time" "1564282561" "state" "3" "timeout" "1486721672" "caller_cseq" "7587486" "callee_cseq" "0" "caller_contact" "sip:10.0.0.3:5060" "callee_contact" "sip:5.5.5.5;did=94e.d9ab66d6" "caller_route_set" "" "callee_route_set" "" "sflags" "0" "toroute_name" "" "req_uri" "sip:61400123123@5.5.5.5" "xdata" "" "iflags" "16"
Note that these are two seperate dialogs, however each runs HMSET "", meaning the hash known as "" has the value written.
modparam("dialog", "dlg_flag", 4)
modparam("dialog", "track_cseq_updates", 1)
modparam("dialog", "event_callback", "ksr_dialog_event")
modparam("dialog", "db_mode", 1) # Real time dump to DB
modparam("dialog", "db_url", "redis://127.0.0.1:6379/7")
5.3.0-dev4
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.