<div dir="ltr"><div>Hi <span name="Răzvan Crainea">Răzvan,</span></div><div><span name="Răzvan Crainea"><br>It seems none of the download links on the page you linked work for me (the video or the source). I know the website has been moved around a bit recently, do you have updated links for these resources?<br>
<br>Thanks!</span></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 24, 2013 at 3:16 AM, Răzvan Crainea <span dir="ltr"><<a href="mailto:razvan@opensips.org" target="_blank">razvan@opensips.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi, Bobby!<br>
<br>
I'm glad you're interested in enhancing OpenSIPS with extra features for the Event Interface, and I am eager to help you with this.<br>
The pvar interface in OpenSIPS is quite simple. Each variable consists of a spec and a value, which can be string or integer. Reading or writing a variable can be easily done using the generic pseudo-variable interface. I think the best way to start this is to watch the devel tutorial we prepared for the PVAR interface[1].<br>
<br>
[1] <a href="http://www.opensips.org/Documentation/Tutorials-DevelSession04" target="_blank">http://www.opensips.org/<u></u>Documentation/Tutorials-<u></u>DevelSession04</a><br>
<br>
PS: probably this discussion should be continued on the devel list.<br>
<br>
Best regards,<br>
<br>
Razvan Crainea<br>
OpenSIPS Core Developer<br>
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.<u></u>com</a><div><div class="h5"><br>
<br>
On 05/24/2013 08:21 AM, Bobby Smith wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid"><div><div class="h5">
Greetings list,<br>
I'd like to be able to use a pvar in the subscribe function for the<br>
event interface like so:<br>
subscribe("$avp(event_name)", "$avp(rabbit_url)")<br>
Where event_name would be like E_CUSTOM_SUBSCRIBE and url would be<br>
"rabbitmq:localhost/$fU"<br>
I know this is not supported yet and I'd be interested in implementing<br>
it, but understanding how pvars work is kinda tough without<br>
documentation. Also, it seems like you have to have a sip_msg in<br>
context for the function to translate a pvar into it's data type, but in<br>
the event interface it's not passed in.<br>
Any thoughts? I'd prefer not to use an infinite case statement: my use<br>
case is having a 1.9.x route block with param() calls that pass in the<br>
event name and the pvar for the queue name to subscribe to.<br>
<br>
Thanks list!<br>
<br>
<br></div></div>
______________________________<u></u>_________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-<u></u>bin/mailman/listinfo/users</a><br>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-<u></u>bin/mailman/listinfo/users</a><br>
</blockquote></div><br></div>