Hi,
As the $Ts pseudovariable gets the timestamp only in seconds, what is
the best way to get the value of the current Unix timestamp in
miliseconds in Kamailio?
Regards,
Dragos
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
non-SIP
entries (which would be absolutely fine for my use-case)?
Regards,
Peter
On 15/02/13 15:22, Dragos Dinu wrote:
Hi,
As far as I know, although making siptrace encapsulate different types
of messages is not something very difficult, the sipcapture module is
developed to write SIP message
Hi,
As far as I know, although making siptrace encapsulate different types
of messages is not something very difficult, the sipcapture module is
developed to write SIP messages into database.
Webhomer 3 reads SIP-related data from DB, so it displays only SIP.
Regards,
Dragos
On 02/15/2013 0
Hi Samuel,
Could you try to test again with the updated siptrace sources from 3.3
branch? I had a patch recently commited for a crash in siptrace, so I'm
pretty sure you have the same issue.
Please tell us if your problem was fixed.:)
Dragos
On 10/09/2012 12:00 PM, samuel wrote:
Hi folks,
What kind of traffic are you sending to sipcapture?
It should be HEP encoded.
Dragos
On 10/04/2012 06:11 PM, Juha Heinanen wrote:
after adding a few module params
modparam("sipcapture", "db_url", "MYSQL_SIP_PROXY_USAGE_URL")
modparam("sipcapture", "table_name", "sip_capture")
modparam("sipcap
Indeed, I have replicated the crash.
I'll commit a fix, but in the meantime, you should set the "table_name"
parameter : this is the name of the table (or tables) that are used to
insert the captured data.
You can write:
modparam("sipcapture", "table_name", "sip_capture");
Dragos
On 10/04/
Hi,
This module is not obsolete. Which version are you using?
I'll also take a look at the crash. Please give me the module parameters
that you used for sipcapture.
Here is the documentation for 3.4:
http://www.kamailio.org/docs/modules/3.4.x/modules/sipcapture.html
Dragos
On 10/04/2012 09:49
