Daniel-Constantin Mierla writes:
> the bt is from custom timer process, which doesn't handle sip requests
> from the network.
ok, that just happened to be the one that according to 'top' used most
cpu time.
> Do a 'kamctl ps' and the select one of the sip workers to grab the back
> with gdb.
Hello,
you should enable core dumping - that should be via running 'ulimit -c
unlimited' before you start rtpproxy.
If you get the coredump, then grab the backtrace with gdb, it should
show where rtpproxy crashed. With that info, maybe we can spot a fix for it.
Hopefully rtpproxy package is
Hello,
the bt is from custom timer process, which doesn't handle sip requests
from the network.
Do a 'kamctl ps' and the select one of the sip workers to grab the back
with gdb.
Cheers,
Daniel
On 20/12/13 15:22, Juha Heinanen wrote:
once in a while kamailio 4.0 presence server becomes unr
Hi All,
root@sip-router3-ve206:/etc/kamailio# kamailio -V
version: kamailio 4.1.0 (x86_64/linux) 350d2e
Doing some testing, can't seem to get rtpproxy to not segfault. I've
loaded version from deb-squeeze pkg, from source
http://b2bua.org/chrome/site/rtpproxy-1.2.1.tar.gz and from git://
sippy.g
Hello,
Kamailio SIP Server v4.0.5 stable release is out.
This is a maintenance release of the stable branch 4.0, that includes
fixes since release of v4.0.4. There is no change to database schema or
configuration language structure that you have to do on installations of
v4.0.x. Deployments r
Hugh,
Thank you for the response, however, now neither the callee or the caller
are getting a feed. I am not sure if the nat requires symmetric RTP. If
there is a way to determine that, please let me know.
Summery, even with Hugh's possible solution, this still does not work.
Thank you again,
b
Hello,
About fix_nated_contact () problem has been resolved.
Thanks for your help.
The reason is that when k2 sent to k1 200 ok, k1 should not do
fix_nated_contact to ua1.
k2 received ack signal must be ua2 uri address
k2 debug:
DEBUG: [parser/msg_parser.c:624]: SIP Request:
DEBUG: [parser
Hey all,
I have kamailio set up behind a nat(port restricted, with firewall rules to
allow sip transactions and allowing rtpproxy packet handling if needed) on
Amazon EC2. I can register and calls complete, however, the Caller(the one
initiating the transaction) receives no rtp media feed. I am ru
Yes; such a request will have either a Contact with an ;expires=0
attribute, or an Expires: 0 header, e.g.
if($ct =~ ";expires=0")
or
if(is_present_hf("Expires") && $hdr(Expires) == "0")
-- Alex
On 12/20/2013 11:44 AM, Henry Fernandes wrote:
Is there a Kamailio module/function to de
Is there a Kamailio module/function to detect if a REGISTER request is for
unregistering?
-H
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/
Hi Ben,
Some NATs require symmetric RTP, so that source and destination ports
are the same for incoming and outgoing media streams. This can be
configured using the 'w' flag to rtpproxy_manage in the NATDETECT route.
rtpproxy_manage("cow");
Regards,
Hugh
On 20/12/2013 16:13, Benjamin Trent
Hey all,
**I apologize if this is a duplicate, I received a bounce back on my first
email.
I have kamailio set up behind a nat(port restricted, with firewall rules to
allow sip transactions and allowing rtpproxy packet handling if needed) on
Amazon EC2. I can register and calls complete, however,
Hello Carsten!
I was wondering if I can be of any service with preparing the vbox image?
Best regards,
Bruno C.
De: sr-users-boun...@lists.sip-router.org
[sr-users-boun...@lists.sip-router.org] em nome de Carsten Bock
[cars...@ng-voice.com]
Enviado: seg
once in a while kamailio 4.0 presence server becomes unresponsive, i.e.,
does not process any requests. below is bt full of a process that at
that time takes most of the cpu time. rls_notifier_processes is not
set, i.e., it defaults to 1.
does the bt give any clue why kamailio is unresponsive?
Hello,
the log errors don't seem related to rtp proxying.
Can you paste here what you have in kamailio.cfg at line 943?
The other error in syslog is related to a duplicate key, most probably
in cdrs table or some other table you populate with sql_query() from
kamailio.cfg -- the conflict is o
Hello,
here is a quick reminder for those willing to push patches to branch 4.0
before release of 4.0.5.
Cheers,
Daniel
On 18/12/13 09:42, Daniel-Constantin Mierla wrote:
Hello,
I am considering to release a new version out of branch 4.0 (previous
stable branch) before Christmas holidays.
Hello,
in failure route is given the SIP message as it was at the moment of
transaction (e.g., the headers added/removed in request_route will be
still kept there, but not those added in branch_route or other
failure_route blocks).
It would be good to get access to the attributes of the bran
17 matches
Mail list logo
