[Serusers] Sipsak Question

[Nils Ohlmeier]

Hi,

sometimes requests can push some things forward :-) :

I just released a new sipsak version 0.8.7, which uses one port for sending 
and receiving and thus should work from hosts which are behind [N|P]AT.

It works for me with iptel.org. Please test it and report errors/bugs to me 
directly.

Greets
  Nils

On Tuesday 30 December 2003 21:27, Nils Ohlmeier wrote:
> On Tuesday 30 December 2003 09:52, Jiri Kuthan wrote:
> > I think that should be definitely done and it is already on Nils's
> > to-do list.
>
> Yes, i know that sipsak does not work behind [N|P]AT, because of the usage
> of two different ports/sockets. And it is on the ToDo list (public viewable
> on the website) to use only one port.
> But on the other side what sipsak does is completly SIP compliant. The
> problem is more that SIP was not NAT compliant designed :-)
>
>   Nils
>
> > -jiri
> >
> > At 05:39 AM 12/30/2003, Wasik, Paul wrote:
> > >Hi all,
> > >
> > >I'm having a little trouble with Sipsak when the Sipsak host is
> > > separated from the SER proxy by a SIP aware PIX firewall using PAT. I'm
> > > running it on a Windows XP machine with cygwin.
> > >
> > >I'm using "sipsak-0.8.6.exe -T -s sip:960 at 192.168.100.10".
> > >
> > >Everything works fine if I bypass the firewall. The problem I seem to
> > > have is I think with the UDP port that Sipsak listens for a response
> > > on. For instance it sends from a UDP source port of for example 1055 to
> > > the SIP destination port of 5060. But it seems that Sipsak is listening
> > > on UDP port 1054 (source port -1) for the reply. I'm running Ethereal
> > > on the same PC as Sipsak and I see the replies coming back correctly on
> > > port 1055. But since Sipsak seems to be listening on port 1054 the
> > > application does not see the replies from my SIP proxy.
> > >
> > >Is there any way to control the port that sipsak listens for replies on
> > > and is it actually listening on UDP send port -1 for replies?
> > >
> > >Thanks,
> > >
> > >Paul
> > >
> > >
> > >
> > >DISCLAIMER
> > >
> > >The information in this e-mail and its attachments may be confidential.
> > >If you are not the intended recipient, you must not read, use or
> > > disseminate that information. If you have recieved this e-mail in
> > > error, please notify us and destroy it immediately.
> > >
> > >Whilst we try to eliminate any viruses or other harmful code or device
> > > from our emails or attachments, it is your responsibility to protect
> > > your system and we do not accept responsibility for any that may
> > > remain. We may monitor or access any e-mails sent to us.
> > >
> > >_______________________________________________
> > >Serusers mailing list
> > >serusers at lists.iptel.org
> > >http://lists.iptel.org/mailman/listinfo/serusers
> >
> > --
> > Jiri Kuthan            http://iptel.org/~jiri/
> >
> > _______________________________________________
> > Serusers mailing list
> > serusers at lists.iptel.org
> > http://lists.iptel.org/mailman/listinfo/serusers
>
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers