|
From: Dylan W. <dyl...@ho...> - 2003-07-31 06:22:54
|
The C++ source isn't really ready for post as yet. I've done all the
basic framework such as the code to receive packets, parse them, etc. If
real life hadn't interrupted me I'd probably be finishing up the code to
handle the Registrar side of things, I have most of it done I just need to
add code to drop duplicate packets from a transaction. Also the code that
generates the reply packet needs a bit of work, I missed a section in the
RFC when I was skimming over it. And I really need to edit out some of the
more "interesting" diagnostic messages I put in there while debugging late
at night. Useful comments would probably help to, at the moment they are
just in there to jog my memory and tend to be a tad cryptic.
But sure, once I get my act together the more help on this the merrier.
:) Do you have any particular specialties when it comes to coding Szabolcs?
- Dylan.
----- Original Message -----
From: <sar...@li...>
To: <sar...@li...>
Sent: Thursday, July 31, 2003 1:27 PM
Subject: Sarp-users digest, Vol 1 #5 - 1 msg
> Send Sarp-users mailing list submissions to
> sar...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/sarp-users
> or, via email, send a message with subject or body 'help' to
> sar...@li...
>
> You can reach the person managing the list at
> sar...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Sarp-users digest..."
>
>
> Today's Topics:
>
> 1. Re: SIP NAT traversal (contribution) (Andrew Radke)
>
> --__--__--
>
> Message: 1
> Date: Wed, 30 Jul 2003 14:18:14 +1000
> From: Andrew Radke <an...@ra...>
> To: Szabolcs Szasz <sz...@sz...>
> Cc: sar...@li...
> Subject: [Sarp-users] Re: SIP NAT traversal (contribution)
>
> Hi,
>
> Thanks for the offer. I'm not doing any of the work on the C++ version
> except providing information on how things are working for me on the
> Perl version. Unfortunately I'm not a programmer :-(. I will forward
> your offer to Dylan who is doing this work though. (about time he let
> the rest of us see some of his code anyway :-).
>
> So to your original questions: firewall changes will NOT be required for
> outgoing calls so long as any outgoing traffic from the SaRP server is
> allowed. Incoming calls will require the SIP port (5060 by default) to
> be accessible on the SaRP server. If the SaRP server has a real world IP
> then this just means allowing that traffic through or if it uses a
> private IP then forwarding anything on port 5060 to it. As for the RTP
> traffic this should be fine so long as any traffic from the server is
> allowed out or otherwise follow the same procedure for the ports listed
> in your config file as for port 5060.
>
> As for IPFreedom, I am not familiar with them so I can't comment. Could
> you provide more information?
>
> And lastly, as far as communication is concerned the best place to get
> in touch would probably be simply using the SaRP mailing lists. I'll
> have to add links to them directly on the homepage, but for now use the
> Sourceforge pages. (email me directly if you have problems)
>
> Regards,
>
> Andrew Radke
>
>
> On Tue, Jul 29, 2003 at 02:06:58PM +0200, Szabolcs Szasz wrote:
> > Oops, I forgot to tell, that there is some fair chance I could
> > contribute to the C++ version sometime in the near future.
> >
> > BTW, do you happen to know of any commercial alternatives
> > to IPFreedom?
> >
> > Cheers,
> > Sz.
> >
> > ----- Original Message -----
> > From: "Szabolcs Szasz" <sz...@sz...>
> > To: <an...@ra...>
> > Sent: Tuesday, July 29, 2003 1:59 PM
> > Subject: Fw: SIP NAT traversal
> >
> >
> > > Just in case, I forward this to your other mail address
> > > (found in the SARP copyright notice).
> > >
> > > Later,
> > > Sz.
> > >
> > > ----- Original Message -----
> > > From: "Szabolcs Szasz" <sz...@sz...>
> > > To: <ar...@us...>
> > > Sent: Tuesday, July 29, 2003 1:56 PM
> > > Subject: SIP NAT traversal
> > >
> > >
> > > > Hi,
> > > >
> > > > Just found your project! Very cool that someone really
> > > > started doing it. In fact, I also found myself in a situation
> > > > just now, where I need some solution to this problem.
> > > >
> > > > As I understand, your stuff requires firewall reconfiguration
> > > > (however minimal). Is that indeed the case?
> > > >
> > > > I'm investigating a solution that is more like the IPFreedom
> > > > client-server model. How close/far is your architecture
> > > > to/from theirs?
> > > >
> > > > (What would be the preferred way of keeping contact?
> > > > Is this your mail address OK for this purpose?)
> > > >
> > > > Thanks,
> > > > Szabolcs
> > > >
> > >
> >
>
>
>
> --__--__--
>
> _______________________________________________
> Sarp-users mailing list
> Sar...@li...
> https://lists.sourceforge.net/lists/listinfo/sarp-users
>
>
> End of Sarp-users Digest
>
|