Re: [reSIProcate] Feature list of open source proxy
I was thinking about this a bit more and Sparks was mentioning that the
response context is one of the biggest chunks of work. I wonder if a good
way to do the first version would be to make a proxy that was not stateless
but one that did not fork. Any time a fork would normally be done, it would
302 instead.
On 11/20/04 8:14 AM, "Cullen Jennings" <fluffy@xxxxxxxxx> wrote:
>
> I thought I would just start an email thread on thins that would be nice in
> an open source proxy.
>
> The key thing is the out of box experience, you can go from nothing to
> having a running proxy that allows phone A to call phone B in 15 minutes.
>
> The key property of it is that it provides what is needed for secure phone
> calls with devices behind a NAT.
>
> It is a single executable, you download it, run it and it is running. It
> includes an embedded web server that you can use to configure it. It
> includes an embedded data base that it uses to store configuration data and
> subscriber info. The DB has a well known scheme that other apps can write
> to.
>
> It has some of the flowing properties:
>
> Identity
> TLS
> Can be a Cert Store
> GRUU
> Outbound Connection
> ENUM
> Can do simple routing based on number
> output to syslog
>
> Has a few types of forwarding
> - per user forward all calls unconditionally
> - per user call forward no answer
> - per user call forward when no devices are registered
>
> Can be configured in a master/slave mode where the slave gets all it's
> configuration from master and slave and master synchronize the registration
> table.
>
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel