[OpenSIPS-Users] how to debug new opensips setup

[erik.buelens at telenet.be]

Hello Brett, 

Thanks for you quick reply, 

I did check the binding with netstat -nlp, this is correct. 
I did not find a firewall. 
Hard to tell is opensips is running, I see no action what so ever. I only knnow the process is there. 
there is section in the main route to handle the register message: 
" 
route{ 

if (!mf_process_maxfwd_header("10")) { 
sl_send_reply("483","Too Many Hops"); 
exit; 
} 

if (is_method("REGISTER")) 
{ 
xlog("L_ERR","received an register"); 
sl_send_reply("200","OK"); 

exit; 
} 

} 
" 
I attached the start-up log, after this nothing happens any more, debug=9 
I dont have the packages you suggested to trace, but I'm sure of the output of tcpdump 
"tcpdump -i eth0 -X -s 2048 port 5060" 

I'm lost and I know there is too little info to help, i looks like or opensips is not running or it does not receive 
anything. Is there any way to have a little log info on the udp_server? On a solaris machine I would use dtrace 
to see what it happening but for. The linux version of it systemtap seems a bit too complex. 

Any suggestions on how i could proceed? 



Kind regards, 

Erik Buelens 


----- Original Message ----- 
From: Brett Nemeroff 
To: OpenSIPS users mailling list 
Sent: Tuesday, August 10, 2010 4:30 PM 
Subject: Re: [OpenSIPS-Users] how to debug new opensips setup 

On Tue, Aug 10, 2010 at 9:23 AM, < erik.buelens at telenet.be > wrote: 






Hello, 

I'm new to opensips, i've sip experience but little programming skills. 

I've installed the opensips module on a virtual machine running centos. 

I've not seen compiler errors. Port 5060 is listend. 

When I'm sending a register message, which also arrives on the interface, verified with tcpdump 
I don't see any respons. 

I tought when i would compile with mode=debug i would get some logging but neither in the terminal nor on in 
the syslog i get any info. 


Couple of comments: 
To turn on debug, set: 
debug=3 (or higher) 
in opensips.cfg, then restart (opensipsctl restart) 


instead of using tcpdump, try using a tool like ngrep or tshark: 
ngrep -qW byline port 5060 
tshark -i any port 5060 


It's hard to diagnose the problem you are having without more information. I guess what you need to check on: 
1. Is opensips listening on the same interface you are receiving the message? (netstat -nlp) 
2. Is there a firewall blocking the traffic? 
3. Is opensips actually running (seriously!) 
4. Does your opensips.cfg actually handle REGISTERs? if you have a bunch of if (is_method("INVITE")) but nothing for REGISTER, it might end up just ignoring it altogether. 


normal "debugging" for the transactions isn't something you need to set during compile, it's a configuration parameter. 


Ultimately, that should help out. The opensips debug log will point you in the right direction, but honestly, I think while learning opensips, that debug log might be a little intimidating for this sort of problem. I'd check the other points first. :) 


-Brett 






_______________________________________________ 
Users mailing list 
Users at lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20100810/1b703fde/attachment.htm 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: opensips_start_ebue10082010_1.txt
Url: http://lists.opensips.org/pipermail/users/attachments/20100810/1b703fde/attachment.txt