[OpenSIPS-Users] how to debug new opensips setup

Brett Nemeroff brett at nemeroff.com
Tue Aug 10 16:30:17 CEST 2010


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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20100810/7154b66a/attachment-0001.htm 


More information about the Users mailing list