On Thu, Sep 4, 2014 at 1:57 PM, Daniel-Constantin Mierla
wrote:
>
> On 04/09/14 09:19, aft wrote:
>>
>> On Wed, Sep 3, 2014 at 11:36 PM, Daniel-Constantin Mierla
>> wrote:
>>>
>>> Hello,
>>>
>>> The $si is the source ip of the sip packet. Bu in a rtimer route there is
>>> no
>>> packet received f
On 04/09/14 09:19, aft wrote:
On Wed, Sep 3, 2014 at 11:36 PM, Daniel-Constantin Mierla
wrote:
Hello,
The $si is the source ip of the sip packet. Bu in a rtimer route there is no
packet received from the network.
So your config is not going to work for what you want to do.
You can try to us
On Wed, Sep 3, 2014 at 11:36 PM, Daniel-Constantin Mierla
wrote:
> Hello,
>
> The $si is the source ip of the sip packet. Bu in a rtimer route there is no
> packet received from the network.
>
> So your config is not going to work for what you want to do.
>
> You can try to use mqueue to push sql
Hello,
The $si is the source ip of the sip packet. Bu in a rtimer route there is
no packet received from the network.
So your config is not going to work for what you want to do.
You can try to use mqueue to push sql queries from sip worker to rtimer as
you need to write something to database.
I'm trying to configure HOMER sip capture server to do some accounting
of the cases when "503 Service Unavailable" message arrives from
capture agents.
I've implemented the following to record the source IPs from which 503
message originates.
onreply_route {
..
