[SR-Users] Cannot run Kamailio on public IP

[spamasbl at gmail.com]

Hi,

I have tried to sniff SIP packets, and maybe someone could check my results
?
http://pastebin.com/6EY5VYeP

Now I am getting Too Many Hops (483)

77.YY.YY.YY = IP from which client trying to register
77.XX.XX.XX = My Public IP
192.168.1.137 = Kamailio

Thanks for all!



2011/4/7 federico cabiddu <federico.cabiddu at gmail.com>

> Hi,
> try to sniff the traffic on your Kamailio server to see if SIP packets
> are reaching the server or not and where, eventually, Kamailio is
> sending the replies.
>
> Regards,
>
> Federico
>
> 2011/4/7 spamasbl at gmail.com <spamasbl at gmail.com>:
> > Thank you, Klaus for your prompt reply.
> >
> > Now Kamailio listens on local IP (192.168.1.137)
> > I've added advertised_address line into my conf (I've added here my
> public
> > hostname)
> > Also I have configured RTPProxy on port 22222, and now Kamailio starts
> > without errors or
> > warnings:
> > Apr 7 04:58:37 sipbox kamailio[2465]: INFO: rtpproxy [rtpproxy.c:1403]:
> rtp
> > proxy <udp:127.0.0.1:22222> found, support for it enabled
> > But still the problem persists. I am not able to register with kamailio
> via
> > public IP.
> > DMZ is turned on, so I guess router should forward all ports to .137
> > address.
> > When trying to register, I am getting request timed out.
> >
> > Any ideas ?
> > Thanks
> > 2011/4/7 Klaus Darilion <klaus.mailinglists at pernau.at>
> >>
> >>
> >> Am 07.04.2011 09:10, schrieb spamasbl at gmail.com:
> >> > Hello all,
> >> >
> >> > I have installed latest Kamailio 3.1.3 on latest ubuntu server.
> >> > Everything seems to be working well
> >> > on my LAN. I can successfully register with local Kamailio IP address
> >> > (192.168.1.137).
> >> >
> >> > The issue is that I can not run Kamailio on my public IP:
> >> > listen=udp:77.XX.XX.XX:5060
> >> > listen=udp:192.168.1.137:5060
> >> > port=5060
> >>
> >> Kamailio can only listen to local IP addresses. The public IP address is
> >> not on your server, but on the public interface of the NAT Router. I
> >> guess the NAT router just does a forwarding to 192.168.1.137.
> >>
> >> Having a SIP proxy behind NAT will give you lot of headache. Anyway,
> >> listen only to the local IP address (192.168.1.137) and try
> >> advertised_address:
> >>
> >>
> >>
> http://www.kamailio.org/dokuwiki/doku.php/core-cookbook:3.1.x#advertised_address
> >>
> >> klaus
> >>
> >>
> >>
> >> >
> >> >
> >> > Kamailio runs behind Linksys WRT54GL router with latest Linksys
> firmware
> >> > and DMZ is turned on (192.168.1.137).
> >> >
> >> > Here is the error I am getting when trying to run kamailio with my
> >> > public IP:
> >> >
> >> > Apr 7 02:57:40 sipbox kamailio[1050]: ERROR: <core>
> [udp_server.c:400]:
> >> > ERROR: udp_init: bind(7, 0x82cc6e4, 16) on 77.XX.XX.XX: Cannot assign
> >> > requested address
> >> >
> >> > Do you have any idea what I'm doing wrong ?
> >> >
> >> > Thanks !
> >> >
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
> list
> >> > sr-users at lists.sip-router.org
> >> > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
> >>
> >> _______________________________________________
> >> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> >> sr-users at lists.sip-router.org
> >> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
> >
> >
> > _______________________________________________
> > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> > sr-users at lists.sip-router.org
> > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
> >
> >
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20110407/df729cf0/attachment-0001.htm>