I¹ll second that. I¹m fairly new to Opensips, but not to SIP and definitely not to Asterisk. As I started to realize the limitations of Asterisk I looked for something a bit more powerful and flexible. I started reading some of the module documentation to get an idea what Opensips (Openser at the time) was capable of. It referenced a lot of things I didn¹t understand. So, I ended up at RFC3261. It was invaluable to me to understand exactly what a proxy, uas, uac, and a few other key terms meant. And what their specific functions were in a SIP environment. I¹m far from an expert but I¹ve learned a lot. It has really helped me understand what a proxy¹s role is, and also what a proxy¹s role isn¹t. Opensips is a proxy, after all.
- Jeff On 7/9/09 1:53 PM, "Brett Nemeroff" <[email protected]> wrote: > I know this may sound like a pretty lame answer, but you'll get a lot of > benefit from reading the definition of a SIP PROXY from RFC3261. > > You can't do much with OpenSIPS (properly) if you dont' know the underlying > RFC. This is very different from other SIP software packages, like Asterisk > where you pretty much can't break RFC compliance on purpose (hah, it may just > already be broken).. > > > -Brett > > > > 2009/7/9 Raúl Alexis Betancor Santana <[email protected]> >> >> ---------- Forwarded message ---------- >> From: "Raúl Alexis Betancor Santana" <[email protected]> >> To: [email protected] >> Date: Tue, 7 Jul 2009 20:47:01 +0100 >> Subject: Re: [OpenSIPS-Users] Is opensips a front end to asterisk? >> On Tuesday 07 July 2009 20:15:01 [email protected] wrote: >>> > On Tue, 7 Jul 2009 14:02:11 -0400, Alex Balashov wrote: >>>> > > Specific and well-parameterised questions really are the key. >>> > >>> > I'll certainly do that, once I start understanding the product but for >>> now, >>> > I'm just trying to get a handle on basics, not deep in depth >>> > understandings, just enough to formulate a plan. >> >> You should go into deep knowleadge, it's a MUST to work with a sip proxy. You >> could begin reading the "Getting starting gide" and so. >> >>> > One was asking about the viability of using opensips on ESXi. Because of >>> > how easy it is to use snapshots, backup and so on, this would be the best >>> > working environment. So my question was, does opensips have any hardware >>> > timing requirement issues such as asterisk does. If timing is not >>> critical, >>> > as a voip server is, then opensips must run nicely in a virtual manner. >> >> Yes, you could use it into a VM, no timming issues like Asterisk. Talking >> about backup and so ... you only need to do a backup of the .cfg file and the >> database backend you use, so you will not get any real advantage of running >> inside a VM from backup point of view. >> >>> > I don't have any numbers to work with, which is why I say scalable. I'm >>> > looking for something which can help me to scale a voip based application >>> > to many users. So let's say hundreds of users so that we have a number. I >>> > know many of you are running many thousands so this should be a good >>> > starting point. >> >> It depends on lot of variables, like available mem, CPU power, network (the >> most important part), but also how complex is your .cfg about request >> proccessing, how do you handle database request, etc. >> So there is not a magic formula, but there are sip-proxies around the world >> working with Million of users. >> >>> > This is how I would have approached this, until I started looking for a >>> sip >>> > gateway/load balancer. >> >> That's a setup, not direcly related with the software you use. >> >>> > This should be pretty straight forward to those who have pro setups and >>> > want as much reliability as possible. I want to have two separate >>> locations >>> > so that I can fail over, simple as that really. >> >> There are not "simple" scenarios in SIP world and faiolver is very-complex >> one. >> >>>> > >-From what I can tell, opensips could act as a pbx on it's own but it >>>> can >>>> > > act as a proxy/load >balancer/gateway to asterisk systems as well. >>> > >>> > This is what I asked about in this thread a couple of times now. It's not >>> > fully clear to me, even after reading. It sometimes sounds like opensips >>> > can be a voip server though it does not provide other media services such >>> > as voice mail and so on. I get that it is a gateway but I'm trying to get a >>> > better understanding of FROM that point on. >> >> That's because Opensips it's a proxy, not a PBX, not a B2BUA, etc., it >> doesn't >> manage media, so you need some "complements" to have a "full-featured VoIP >> system" >> >> -- >> Raúl Alexis Betancor Santana >> Dimensión Virtual >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
