<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Hi Rudy,<br>
<br>
Events are send to the server/queue described when you subscribed
for an event (via the MI command -
<a class="moz-txt-link-freetext" href="http://www.opensips.org/Resources/DocsCoreMi18#toc15">http://www.opensips.org/Resources/DocsCoreMi18#toc15</a>). or ?<br>
<br>
Regarding ACC, the module itself does not generate events for acc
records, but you can do that from the script (see the
raise_event() core function -
<a class="moz-txt-link-freetext" href="http://www.opensips.org/Resources/DocsCoreFcn18#toc129">http://www.opensips.org/Resources/DocsCoreFcn18#toc129</a>)<br>
<br>
Regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
<br>
On 11/02/2012 10:49 PM, Rudy wrote:
<blockquote
cite="mid:CAA0TfghuqtgcPHLY9R_tBQjfGrHigUEznHV+2SNsN13g5qAMLw@mail.gmail.com"
type="cite">Bogdan,
<div><br>
</div>
<div> Its great to hear all these ideas for 1.9 from
the community. One thing that may also be useful, is some
enhancements to the rabbit_mq module. It would be great if this
module could also push/send events to a any rabbitmq queue or
exchange (maybe based on an avp) . Another thing that may be
worth exploring is being able to send ACC via a rabbitmq event.
What do you think?</div>
<div><br clear="all">
Regards,<br>
--Rudy<br>
Dynamic Packet<br>
Toll-Free: 888.929.VOIP ( 8647 )<br>
<br>
<br>
<div class="gmail_quote">On Fri, Nov 2, 2012 at 9:55 AM,
Bogdan-Andrei Iancu <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:bogdan@opensips.org"
target="_blank">bogdan@opensips.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div class="im"><br>
On 11/02/2012 02:17 PM, Iñaki Baz Castillo wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
2012/11/2 Bogdan-Andrei Iancu<<a
moz-do-not-send="true"
href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>>:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt
0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
Yes the patch is there, we need to review it. Also
Inaki sugested some<br>
tunings in the PATH module (to fully support
websocket).<br>
</blockquote>
Well, there is no special needs for the PATH module to
support<br>
WebSocket. In fact, nothing must be done if it already
works ok (but<br>
just increasing the path column size to be able to store
two URIs).<br>
<br>
</blockquote>
</div>
Yes, that's the kind of things I was referring at. Also
looking in the patch module code, there are several things
that can be improved there (how path is built, mem usag,
etc). There are still some faulty things also there - there
was recently a fix on TCP handling (proto changing) in PATH
hdr.<br>
<br>
Regards,<br>
Bogdan
<div class="HOEnZb">
<div class="h5"><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a moz-do-not-send="true"
href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
</body>
</html>