JM,<div>I'm not sure if I'm reading too little into what you are saying, but just adding entries into the LCR table isn't going to do anything. OpenSIPs is largely a toolkit. Like asterisk, it doesn't do anything until you set the configuration to perform a certain way. So out of the box, the example configs are pretty useless and only show basic functionality. It certainly doesn't use drouting or LCR to do anything.</div>
<div><br></div><div>It's possible that with some minimal reconfiguration of opensips.cfg example you can achieve what you want. But there is limitless opportunity for complexity. :)</div><div><br></div><div>BTW, don't bother working with the LCR module. Go ahead and go for the drouting module.</div>
<div><br></div><div>-Brett</div><div><br></div><div><br></div><div><br><div class="gmail_quote">On Thu, Sep 17, 2009 at 1:00 PM, J M <span dir="ltr"><<a href="mailto:gspdjosh@gmail.com">gspdjosh@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hello,<br>
<br>
I'm pretty new to OpenSIPS. I've lurked on this list a bit and read<br>
anything I could find, but I'm struggling with figuring things out.<br>
It feels like there is a steep learning curve. Right now I have been<br>
able to register SIP devices to the proxy and place calls between<br>
them, but that's about it. I'm going to start off saying if I missed<br>
some very basic documentation or a nice walk-through, please point me<br>
in the right direction and I'll be on my way. I'll also be happy to<br>
create a nice tutorial when I get my setup working. I think what I'm<br>
trying to do should be very simple, but maybe not.<br>
<br>
Currently, I have a group of Asterisk servers. In front of the<br>
Asterisk servers is a basic payware SIP proxy (I want to replace it as<br>
it would be good having a database backend to make adding many routes<br>
a lot easier. The payware solution only has a web-based interface.).<br>
The SIP proxy only has a handful of routing rules currently. For<br>
example:<br>
<br>
Any SIP traffic to an extension matching 555XXXX routes to Asterisk<br>
server1, anything matching 444XXXX routes to Asterisk server2, and so<br>
on.<br>
<br>
Right now I just want to replicate this configuration and from that<br>
point, I would hope I could use that knowledge to add a large number<br>
of specific routes - preferably being held in a SQL table. I have<br>
played around a bit with trying to add a lcr gateway and route (didn't<br>
seem to do anything), and I've also seen mention of using dispatcher<br>
or drouting, but I can't make heads or tails of how (I've seen the<br>
"cookbook" but so far I haven't had any bit of success).<br>
<br>
Even if I don't get a specific how-to, anything to point me in the<br>
right direction would be greatly appreciated.<br>
<br>
Regards,<br>
<br>
Josh<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote></div><br></div>