[Freeswitch-users] SIP Proxy - Kamailio/Opens* load-balancing - simple example please?

[Michael Jerris]

There is no way to make a sip user agent stateless.  recovery may be an option.

> On Feb 5, 2015, at 1:59 PM, Avi Marcus <avi at avimarcus.net> wrote:
> 
> Kristian: Indeed, that would be easier! 
> However, that doesn't seem to solve the ability to do maintenance on that box (I was planning to have opensips share with one of the FS instances).
> 
> Is recover call table from a shared sql DB reliable for that situation, or any other way to make it stateless...?
> 
> -Avi
> 
> On Thu, Feb 5, 2015 at 7:33 PM, Kristian Kielhofner <kris at kriskinc.com <mailto:kris at kriskinc.com>> wrote:
> Unless you're looking at extremely high scale (several hundred to
> thousands CPS) or tens - hundreds of thousands of call (yes, really)
> why not just use another FreeSWITCH instance in bypass_media? On
> decent hardware FreeSWITCH can easily manage a simple call routing
> config in bypass_media into hundreds of CPS and several thousands
> calls.
> 
> This can provide everything you've mentioned (and more) with many
> additional advantages including not needing to learn SIP in and out to
> make a SER-ish configuration useful.
> 
> On Mon, Feb 2, 2015 at 3:55 AM, Avi Marcus <avi at avimarcus.net <mailto:avi at avimarcus.net>> wrote:
> > Hi - I know this has come up several times and I see several examples even
> > on the old wiki - but I've never used a SIP proxy before, and I don't
> > understand most of the configuration in the examples.
> >
> > Here's what I believe is a fairly common use case:
> >
> > 1) I have inbound calls via various carriers. Some only support an IP
> > endpoint (so DNS won't work) and some don't support 302 redirects, so I
> > can't use a stateless FS endpoint either, so I need a sip proxy.
> >
> > 2) I need a SIP proxy that will route calls to various FreeSWITCH endpoints.
> > (Preferably, it should route registration too (or manage registration list
> > itself?))
> >
> > 3) I need the ability to pull freeswitch nodes out of the routing (waiting
> > for them to drain is fine, I don't need failover of live calls) to perform
> > maintenance, and then add them back to the routing.
> >
> > 4) I should be able to have this proxy on a floating IP that I can move this
> > too, without downtime, for maintenance work.
> >
> > I think this is mostly handled by the examples I found - but the opensips
> > configuration files are hundreds of lines that I don't understand. If it's
> > just routing calls to a backend, shouldn't that be possible in a small
> > numbers of lines that are more understandable?
> >
> > I imagine someone can probably just point me to a tutorial/working code that
> > I can use. Several have been shared but I don't recall any one being
> > particularly simple... Also, most of them tell you about compiling code. FS
> > has been released in packages - has opensips? That might cut off many steps
> > from an updated tutorial.
> >
> > 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20150205/d6295c68/attachment.html