On 4/13/10 8:39 PM, Alex rsm wrote:
Hi,
My Kamailio server uses an external mysql database with perl script to
proxy traffic.
When mysql server is unreachable, Kamailio do not respond with 100
Trying and instead responses with 484 (Address Incomplete) to the
INVITE message.
Is this a
Hi
I need some guidelines to troubleshoot the following issue:
a) A is behind NAT
b) B is not behind NAT
c) A calls B, SIP INVITE is sent over TCP
d) A's firewall does NAT and changes the source port to let's say p1
e) B releases the call and sends BYE over UDP
f) Kamailio sends the BYE to
Klaus
I attached the ngrep you asked me to this email.
Regards,
Pascal
On Wed, Apr 14, 2010 at 12:21 PM, Klaus Darilion
klaus.mailingli...@pernau.at wrote:
The contact after fix_nated_contact() should also contain ;transport=tcp.
Thus, Kamailio should relay the BYE with TCP.
Can you
alexis heron wrote:
Hi,
I have a problem to routing with kamailio. When I restart kamailio I
have this error message :
0(710) : core [cfg.y:3328]: parse error in config file
/usr/local/etc/kamailio/kamailio.cfg, line 640, column 2-3: syntax error
0(710) : core [cfg.y:3328]: parse error in
On Wednesday 14 April 2010, Pratab Ali wrote:
I read the reply from Daniel and as he suggested I got kamailio 3.0.0
using GIT this morning. However, I don't know if I actually got (Commit:
3a25f8327c on 3.0). I am unfamiliar with GIT as I use CVS.
I will recheck to see if I got the branch
Pratab Ali wrote:
Hi,
Thanks, I just followed your git instructions and it shows that I have
Daniel's change.
I will try a clean rebuild and run again.
Thanks.
pratab
If a clean build doesn't solve can you add to modules/db_mysql/Makefile
a -lm (link the math library) to the LIBS
On Wednesday 14 April 2010, Pratab Ali wrote:
Your suggestion with regards to appending -lm after -lz worked. I no
longer get the undefined symbol: log error. Thanks!
However, now I have kamailio unable to connect to mysql because I've not
told it to use the correct port. This I can fix from
i call drop() in branch route and it is the only branch left. the
branch gets correctly dropped, i.e., the request is not send out, but
the reply to UAC is strange:
U 2010/04/14 21:03:43.750712 192.98.102.10:5060 - 192.98.103.2:5074
SIP/2.0 477 Unfortunately error on sending to next hop occurred
2010/4/14 Juha Heinanen j...@tutpro.com:
i call drop() in branch route and it is the only branch left. the
branch gets correctly dropped, i.e., the request is not send out, but
the reply to UAC is strange:
U 2010/04/14 21:03:43.750712 192.98.102.10:5060 - 192.98.103.2:5074
SIP/2.0 477