Hi all,
as announced quite a while ago, I finally checked in code that allows to
produce CDRs (Call Data Records) directly from SIP-Router and generate
logs accordingly.
The main code portion resides in modules_k/acc and provides a switch to
enable basic CDR generation including start time, end
Hello Daniel,
Yes ,it works now .
Thanks.
Hala
From: Daniel-Constantin Mierla mico...@gmail.com
To: hala alramli doreme202...@yahoo.com; SIP Router - Kamailio (OpenSER) and
SIP Express Router (SER) - Users Mailing List sr-users@lists.sip-router.org
Sent:
Hi Sebastian,
thanks for reporting back the results. On a second thought I updated the
patch a bit to use a local variable for backup in order to allow nested
execution of event_route[tm:local-request] which can be triggered by
sending local generated requests. The commit was:
Hello,
I committed a patch to master branch in order to skip setting the
dst_uri to next hop address for branch route, link to commit:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=fb4ecbf986f4af366e5be9cbad26ceba924c77fd
It would be great if you can give it a try and
i have 8 children specified in default file and in cfg file i have:
listen=192.98.101.10:5060;
listen=udp:127.0.0.1:5070;
listen=udp:127.0.0.1:5070;
listen=tcp:127.0.0.1:5070;
listen=udp:127.0.0.1:5080;
listen=tcp:127.0.0.1:5080;
listen=tcp:127.0.0.1:6060;
that results in 8 tcp receiver
On Thursday 04 August 2011, Juha Heinanen wrote:
i have 8 children specified in default file and in cfg file i have:
listen=192.98.101.10:5060;
listen=udp:127.0.0.1:5070;
listen=udp:127.0.0.1:5070;
listen=tcp:127.0.0.1:5070;
listen=udp:127.0.0.1:5080;
listen=tcp:127.0.0.1:5080;
Hi, I remember that in Kamailio 1.5.X t_on_branch and t_on_failure
still remain after rouning failure_route[XX], and I think there was
a way to reset them.
In 3.X it seems that t_on_branch and t_on_failure must be set again in
failure_route to take effect in next t_relay() call, am I right?
Hello,
On 8/4/11 2:59 PM, Iñaki Baz Castillo wrote:
Hi, I remember that in Kamailio 1.5.X t_on_branch and t_on_failure
still remain after rouning failure_route[XX], and I think there was
a way to reset them.
In 3.X it seems that t_on_branch and t_on_failure must be set again in
failure_route
2011/8/4 Daniel-Constantin Mierla mico...@gmail.com:
To reset, just use the parameter 0 or for t_on_xyz().
Thanks a lot.
--
Iñaki Baz Castillo
i...@aliax.net
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
That 480 reply is generated by FreeSWITCH. You should run it in debug
mode to see the reason of why 480 was generated.
Also, since the communication between Kamailio and fs is on loopback
interface, be sure you capture the SIP traffic on it with 'ngrep -d any
...' or 'ngrep -d lo ...'
Thank you!
And isn't there an impact on the line
modparam(pcscf,ipv4_for_signaling,192.168.106.162)
las well?How do I add my second IP?
Thank you.
RR
El 3 de agosto de 2011 00:23, Daniel-Constantin Mierla
mico...@gmail.comescribió:
Hello,
On 8/2/11 11:19 PM, Rocío Ruz wrote:
Hello,
And this one too : modparam(pcscf,gg_ip,192.168.106.162)
Thank you.
RR
2011/8/4 Rocío Ruz rocio...@gmail.com
Thank you!
And isn't there an impact on the line
modparam(pcscf,ipv4_for_signaling,192.168.106.162)
las well?How do I add my second IP?
Thank you.
RR
El 3 de agosto de
Hello sr-users,
I would like to present a new project called Homer.
What is Homer ?
Homer is a capture solution for SIP logging.
How does it work?
Homer has 4 components:
1. Capture Agent
2. Capture Node
4. Capture DB
3. Web GUI.
The capture agent takes your local SIP traffic and sends it to
Hi Alexandr,
thanks for this project. We will review the patches to kamailio and get
them in the repository.
Collecting 5 000 000 SIP packets/hour is quite some traffic, I would
say!!! If the average size of sip packet is like 0.5 to 1KB, then the
traffic stored per hour is like 2.5 to 5
8/4/2011 7:23 PM, Daniel-Constantin Mierla ?:
Hi Alexandr,
Hello Daniel,
thanks for this project. We will review the patches to kamailio and
get them in the repository.
Collecting 5 000 000 SIP packets/hour is quite some traffic, I would
say!!! If the average size of sip packet is
15 matches
Mail list logo
