Thanks Ovidiu,<br> <br>I'll be going over the RFC's till I find my answer.<br><br>Kurtis <br><br><div class="gmail_quote">On Tue, Apr 5, 2011 at 3:00 AM, <span dir="ltr"><<a href="mailto:users-request@lists.opensips.org">users-request@lists.opensips.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Send Users mailing list submissions to<br>
<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<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>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:users-request@lists.opensips.org">users-request@lists.opensips.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:users-owner@lists.opensips.org">users-owner@lists.opensips.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Far end byes are not being routed back to UAE (Ovidiu Sas)<br>
2. Memory Issues because of AVPs? (<a href="mailto:duane.larson@gmail.com">duane.larson@gmail.com</a>)<br>
3. Re: t_relay behavior with 477 send failed (Amit Sharma)<br>
4. Re: Memory Issues because of AVPs? (Bogdan-Andrei Iancu)<br>
5. Re: Asynchronous DB queries in OpenSIPS 1.x (Bogdan-Andrei Iancu)<br>
6. Re: Asynchronous DB queries in OpenSIPS 1.x (Bogdan-Andrei Iancu)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 4 Apr 2011 22:20:55 -0400<br>
From: Ovidiu Sas <<a href="mailto:osas@voipembedded.com">osas@voipembedded.com</a>><br>
Subject: Re: [OpenSIPS-Users] Far end byes are not being routed back<br>
to UAE<br>
To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
Cc: Kurtis vel <<a href="mailto:kurtisvelarde@gmail.com">kurtisvelarde@gmail.com</a>><br>
Message-ID: <<a href="mailto:BANLkTimKVEB4RrcUvJDDC8GbdXH_WhThJQ@mail.gmail.com">BANLkTimKVEB4RrcUvJDDC8GbdXH_WhThJQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
The BYE is not properly formated: the RURI is bogus.<br>
It should be:<br>
BYE <a href="http://sip:1000@172.16.113.63:10090" target="_blank">sip:1000@172.16.113.63:10090</a> SIP/2.0<br>
instead of:<br>
BYE <a href="http://sip:1000@50.56.106.41:5060" target="_blank">sip:1000@50.56.106.41:5060</a> SIP/2.0<br>
<br>
The RURI in BYE should be identical to the URI in the Contact header of ACK:<br>
Contact: <<a href="http://sip:1000@172.16.113.63:10090" target="_blank">sip:1000@172.16.113.63:10090</a>><br>
<br>
For more details, check the loose routing section in on the SIP rfc.<br>
<br>
<br>
Regards,<br>
Ovidiu Sas<br>
<br>
On Mon, Apr 4, 2011 at 8:20 PM, Kurtis vel <<a href="mailto:kurtisvelarde@gmail.com">kurtisvelarde@gmail.com</a>> wrote:<br>
> Hi Everyone,<br>
><br>
> I'm a new user and am having an issue routing byes from the called recipient<br>
> back to the origin UAE.<br>
><br>
> With `opensipsctl online` I can see that the device is registered. When the<br>
> recipient hangs up, opensips returns a 404 to the bye sent from my provider.<br>
> Attached is a sip trace and most or the opensips.cfg routing script. It is<br>
> marked where the 404 is being sent in both files.<br>
><br>
> Tried adding -<br>
> ? ? ? ? ? ? ? ? ? ? ?? if (uri==myself){<br>
> ??????????????????????????????? route(1);<br>
> ??????????????????????? }<br>
><br>
> In front of the 404 reply but a 483 To Many Hops is revived from the remote<br>
> network.<br>
><br>
> Any help would be appreciated.<br>
><br>
> Thanks<br>
><br>
> Kurtis<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>
><br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 05 Apr 2011 03:54:14 +0000<br>
From: <a href="mailto:duane.larson@gmail.com">duane.larson@gmail.com</a><br>
Subject: [OpenSIPS-Users] Memory Issues because of AVPs?<br>
To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
Message-ID: <<a href="mailto:20cf3054ac035fdb5004a023d492@google.com">20cf3054ac035fdb5004a023d492@google.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed";<br>
DelSp="yes"<br>
<br>
A while back I had posted on here thinking that i might have a memory leak<br>
<a href="http://opensips-open-sip-server.1449251.n2.nabble.com/Memory-leak-td5942660.html#a5949293" target="_blank">http://opensips-open-sip-server.1449251.n2.nabble.com/Memory-leak-td5942660.html#a5949293</a><br>
<br>
I've had to fix my SIPP scripts but also I had to change some stuff in my<br>
opensips.cfg file. In my script I commented out all of the times I set an<br>
AVP variable.<br>
<br>
So my question is<br>
<br>
Every time you load an AVP it gets put into memory correct? So in order for<br>
the memory not to get overloaded you need to do "avp_delete" correct? What<br>
about the AVPs that are declared in modparam's and that are set in the<br>
script? How do you make sure those are not overloading memory? What else<br>
could cause my opensips processes to gradually eat up the memory before<br>
opensips just starts erroring out because of no memory?<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensips.org/pipermail/users/attachments/20110405/be5a10e0/attachment-0001.htm" target="_blank">http://lists.opensips.org/pipermail/users/attachments/20110405/be5a10e0/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 5 Apr 2011 12:01:09 +0530<br>
From: Amit Sharma <<a href="mailto:asharma@3clogic.com">asharma@3clogic.com</a>><br>
Subject: Re: [OpenSIPS-Users] t_relay behavior with 477 send failed<br>
To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
Message-ID: <BANLkTikoRTGFWg-2wZG5h5DAkExKyZvU=<a href="mailto:g@mail.gmail.com">g@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1<br>
<br>
Bogdan,<br>
I set the flag with t_relay and it resolved the issue. I am able<br>
to handle failure from t_relay now.<br>
<br>
Thanks,<br>
Amit<br>
<br>
On Mon, Mar 21, 2011 at 10:33 PM, Bogdan-Andrei Iancu<br>
<<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>> wrote:<br>
> Hi Amit,<br>
><br>
> have you set the 0x02 flag for t_relay ? See:<br>
> ? ? ?<a href="http://www.opensips.org/html/docs/modules/1.6.x/tm.html#id293378" target="_blank">http://www.opensips.org/html/docs/modules/1.6.x/tm.html#id293378</a><br>
><br>
> This flag will prevent the t_relay() function do internally deal with errors<br>
> (by sending back a negative reply).<br>
><br>
> Regards,<br>
> Bogdan<br>
><br>
> Amit Sharma wrote:<br>
>><br>
>> I tried the fix from the 1.6 branch. The issue I still face is that now<br>
>> t_relay returns with a value of 1 even when the relaying has failed.<br>
>><br>
>> How do you figure out if t_relay has failed (!t_relay()) does not work in<br>
>> this case? Does a return value 1 also signify an error?<br>
>> ?-Amit<br>
>><br>
>> On Tue, Mar 15, 2011 at 3:51 PM, Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a><br>
>> <mailto:<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>>> wrote:<br>
>><br>
>> ? ?Hi Amit,<br>
>><br>
>> ? ?Following your report, Anca did a fix on SVN - see:<br>
>> ? ? ?<a href="http://lists.opensips.org/pipermail/devel/2011-March/007893.html" target="_blank">http://lists.opensips.org/pipermail/devel/2011-March/007893.html</a><br>
>><br>
>> ? ?Please update from SVN and try again.<br>
>><br>
>> ? ?Regards,<br>
>> ? ?Bogdan<br>
>><br>
>> ? ?Amit Sharma wrote:<br>
>><br>
>> ? ? ? ?I am facing an issue similiar to the one outlined in the thread<br>
>><br>
>> ? ? ? ?<a href="http://lists.opensips.org/pipermail/users/2010-April/011783.html" target="_blank">http://lists.opensips.org/pipermail/users/2010-April/011783.html</a><br>
>><br>
>><br>
>> ? ? ? ? I am using the latest stable version of opensips (1.6.4) and<br>
>> ? ? ? ?tried the solution outlined in the thread above.<br>
>> ? ? ? ?The issue I have observed is that t_relay function doesn't<br>
>> ? ? ? ?return control to the script in case of a send failure (e.g<br>
>> ? ? ? ?inability to establish TCP connection etc) ?and I recieve a<br>
>> ? ? ? ?477 send failure on the client.<br>
>><br>
>> ? ? ? ?This is the relevant and simplified route block that I am using<br>
>><br>
>> ? ? ? ? route{<br>
>> ? ? ? ? ? ? ? ? ? lookup();<br>
>> ? ? ? ? ? ? ? ? serialize_branches(1);<br>
>> ? ? ? ? ? ? ? ? next_branches();<br>
>> ? ? ? ? ? ? ? ? route(1);<br>
>> ? ? ? ? }<br>
>><br>
>> ? ? ? ?route[1]{<br>
>> ? ? ? ? ? ? ? ?xlog("L_ERR", "Before t_relay");<br>
>> ? ? ? ? ? ? ? ?t_relay();<br>
>> ? ? ? ? ? ? ? ?xlog("L_ERR", "After t_relay");<br>
>><br>
>> ? ? ? ?}<br>
>><br>
>> ? ? ? ? ?The log statement after the call to t_relay doesn't get<br>
>> ? ? ? ?printed in case the highest priority contact (TCP) ?is<br>
>> ? ? ? ?unreachable.<br>
>> ? ? ? ? ?In essence any failover logic written on the return value of<br>
>> ? ? ? ?t_relay doesn't execute.<br>
>><br>
>> ? ? ? ?Thanks,<br>
>> ? ? ? ?Amit<br>
>><br>
>><br>
>><br>
>> ?------------------------------------------------------------------------<br>
>><br>
>> ? ? ? ?_______________________________________________<br>
>> ? ? ? ?Users mailing list<br>
>> ? ? ? ?<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a> <mailto:<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>
>><br>
>><br>
>><br>
>> ? ?-- ? ? Bogdan-Andrei Iancu<br>
>> ? ?OpenSIPS eBootcamp - 28th February 2011<br>
>> ? ?OpenSIPS solutions and "know-how"<br>
>><br>
>><br>
>> ? ?_______________________________________________<br>
>> ? ?Users mailing list<br>
>> ? ?<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a> <mailto:<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>
>><br>
>><br>
><br>
><br>
> --<br>
> Bogdan-Andrei Iancu<br>
> OpenSIPS eBootcamp - 28th February 2011<br>
> OpenSIPS solutions and "know-how"<br>
><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>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 05 Apr 2011 12:31:44 +0300<br>
From: Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>><br>
Subject: Re: [OpenSIPS-Users] Memory Issues because of AVPs?<br>
To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
Message-ID: <<a href="mailto:4D9AE180.7010307@opensips.org">4D9AE180.7010307@opensips.org</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Hi Duane,<br>
<br>
On 04/05/2011 06:54 AM, <a href="mailto:duane.larson@gmail.com">duane.larson@gmail.com</a> wrote:<br>
> A while back I had posted on here thinking that i might have a memory<br>
> leak<br>
> <a href="http://opensips-open-sip-server.1449251.n2.nabble.com/Memory-leak-td5942660.html#a5949293" target="_blank">http://opensips-open-sip-server.1449251.n2.nabble.com/Memory-leak-td5942660.html#a5949293</a><br>
><br>
><br>
> I've had to fix my SIPP scripts but also I had to change some stuff in<br>
> my opensips.cfg file. In my script I commented out all of the times I<br>
> set an AVP variable.<br>
><br>
> So my question is<br>
><br>
> Every time you load an AVP it gets put into memory correct?<br>
yes, in shared memory, to be more specific.<br>
> So in order for the memory not to get overloaded you need to do<br>
> "avp_delete" correct?<br>
not necessarily - you use the function only only if you want to delete<br>
the AVPs at some specific point in script. AVPs are transaction/message<br>
persistent , and they are automatically deleted when the transaction /<br>
message is deleted (AVPs are part of transaction/message)<br>
> What about the AVPs that are declared in modparam's and that are set<br>
> in the script?<br>
those are just names of AVPs, not instances of AVPs<br>
> How do you make sure those are not overloading memory? What else could<br>
> cause my opensips processes to gradually eat up the memory before<br>
> opensips just starts erroring out because of no memory?<br>
As said, AVPs cannot cumulate in memory as they are attached to<br>
structures (transactions/messages) that are deleted.<br>
<br>
If you get errors on on running out of memory, please read and follow:<br>
<a href="http://www.opensips.org/Resources/DocsTsMem" target="_blank">http://www.opensips.org/Resources/DocsTsMem</a><br>
<br>
Regards,<br>
Bogdan<br>
<br>
<br>
--<br>
Bogdan-Andrei Iancu<br>
OpenSIPS eBootcamp - 2nd of May 2011<br>
OpenSIPS solutions and "know-how"<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Tue, 05 Apr 2011 12:35:56 +0300<br>
From: Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>><br>
Subject: Re: [OpenSIPS-Users] Asynchronous DB queries in OpenSIPS 1.x<br>
To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
Cc: OpenSIPS devel mailling list <<a href="mailto:devel@lists.opensips.org">devel@lists.opensips.org</a>><br>
Message-ID: <<a href="mailto:4D9AE27C.3060406@opensips.org">4D9AE27C.3060406@opensips.org</a>><br>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"<br>
<br>
Hi Brett,<br>
<br>
On 03/16/2011 07:32 PM, Brett Nemeroff wrote:<br>
><br>
> On Wed, Mar 16, 2011 at 12:18 PM, Vlad Paiu <<a href="mailto:vladpaiu@opensips.org">vladpaiu@opensips.org</a><br>
> <mailto:<a href="mailto:vladpaiu@opensips.org">vladpaiu@opensips.org</a>>> wrote:<br>
><br>
> Hello all,<br>
><br>
> Problem :<br>
> 1) Extend the OpenSIPS DB core. Add extra core processes that<br>
> would only handle queries that return no results.<br>
> For example : The accounting module need to insert an entry in<br>
> the DB. The module calls the insert() function. Behind the scene,<br>
> this triggers passing all the arguments to the new core processes,<br>
> via IPC mechanisms. The insert() then exists and the SIP children<br>
> continues execution as if the entry has been inserted in the DB.<br>
> Meanwhile, the DB core processes receive the new parameters, build<br>
> and send the query, blocking if necessary.<br>
><br>
><br>
> Maybe I'm just saying the same thing another way, but what about an<br>
> async execution queue. So you basically add to the queue messages to<br>
> be executed to the database and on some sort of timer loop process<br>
> them. To the script, we just assume everything is 100% successful.<br>
yes, it is the same what Vlad said, but in other words :)<br>
><br>
> Is IPC really necessary for this? The goal here is really just to<br>
> offload the processing elsewhere so that the DB slowness doesn't<br>
> adversely affect opensips core performance. right?<br>
IPC is a really generic way of saying - the idea is that you need to<br>
"move" the query from the process handling the SIP message to another<br>
process (DB related only)<br>
<br>
><br>
> I thin it's also important that there is a async execute and a sync<br>
> execute and people (users?) need to know that in the async execute,<br>
> you won't know if the execute succeeded in the script logic *ever*<br>
<br>
this support will be mainly be used from the other SIP modules (by the<br>
internal code) and not from script, so for "users", this will be<br>
transparent.<br>
<br>
Regards,<br>
Bogdan<br>
<br>
--<br>
Bogdan-Andrei Iancu<br>
OpenSIPS eBootcamp - 2nd of May 2011<br>
OpenSIPS solutions and "know-how"<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.opensips.org/pipermail/users/attachments/20110405/d65238ac/attachment-0001.htm" target="_blank">http://lists.opensips.org/pipermail/users/attachments/20110405/d65238ac/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Tue, 05 Apr 2011 12:42:38 +0300<br>
From: Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>><br>
Subject: Re: [OpenSIPS-Users] Asynchronous DB queries in OpenSIPS 1.x<br>
To: OpenSIPS users mailling list <<a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a>><br>
Cc: OpenSIPS devel mailling list <<a href="mailto:devel@lists.opensips.org">devel@lists.opensips.org</a>><br>
Message-ID: <<a href="mailto:4D9AE40E.2030704@opensips.org">4D9AE40E.2030704@opensips.org</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Hi Dave,<br>
<br>
We decided to put the async support in core (the mechanism for "moving"<br>
a query from current process to a DB process) - each DB module will<br>
choose to use or not this async support (like for db_text makes not<br>
sense, db_postgres may have a buitin one, etc)<br>
<br>
Regards,<br>
Bogdan<br>
<br>
On 03/16/2011 11:26 PM, Dave Singer wrote:<br>
> Vlad,<br>
> Would it be possible extend DB_VITRUAL kind of a combination of your<br>
> two options and Brett's suggestion.<br>
> I'm just guessing how things might work and possibilities. So for what<br>
> it is worth...<br>
> Since it is a middle layer, it could either use the async capabilities<br>
> of the native driver or put it in a queue to be handled by a special<br>
> db queue process that could also be threaded potentially (if<br>
> beneficial). The IPC would only need to pass the query that is needed.<br>
> To take advantage of the async the user would only need to use the<br>
> DB_VIRTUAL module.<br>
> Probably would want a module param to enable/disable async<br>
> (async_db_updates) in case it is important and maybe a bit flag option<br>
> as well that would reverse the async_db_updates option when flag set<br>
> for case by case basis.<br>
> Potentially with a separate queue process updates like registrations<br>
> could be combined into a single update.<br>
><br>
> Dave<br>
><br>
><br>
> On Wed, Mar 16, 2011 at 10:32 AM, Brett Nemeroff<<a href="mailto:brett@nemeroff.com">brett@nemeroff.com</a>> wrote:<br>
>><br>
>><br>
>><br>
>> On Wed, Mar 16, 2011 at 12:18 PM, Vlad Paiu<<a href="mailto:vladpaiu@opensips.org">vladpaiu@opensips.org</a>> wrote:<br>
>>> Hello all,<br>
>>><br>
>>> Problem :<br>
>>> 1) Extend the OpenSIPS DB core. Add extra core processes that would only<br>
>>> handle queries that return no results.<br>
>>> For example : The accounting module need to insert an entry in the DB.<br>
>>> The module calls the insert() function. Behind the scene, this triggers<br>
>>> passing all the arguments to the new core processes, via IPC mechanisms. The<br>
>>> insert() then exists and the SIP children continues execution as if the<br>
>>> entry has been inserted in the DB. Meanwhile, the DB core processes receive<br>
>>> the new parameters, build and send the query, blocking if necessary.<br>
>>><br>
>> Maybe I'm just saying the same thing another way, but what about an async<br>
>> execution queue. So you basically add to the queue messages to be executed<br>
>> to the database and on some sort of timer loop process them. To the script,<br>
>> we just assume everything is 100% successful.<br>
>> Is IPC really necessary for this? The goal here is really just to offload<br>
>> the processing elsewhere so that the DB slowness doesn't adversely affect<br>
>> opensips core performance. right?<br>
>><br>
>> I thin it's also important that there is a async execute and a sync execute<br>
>> and people (users?) need to know that in the async execute, you won't know<br>
>> if the execute succeeded in the script logic *ever*<br>
>> -Brett<br>
<br>
<br>
--<br>
Bogdan-Andrei Iancu<br>
OpenSIPS eBootcamp - 2nd of May 2011<br>
OpenSIPS solutions and "know-how"<br>
<br>
<br>
<br>
<br>
------------------------------<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>
<br>
<br>
End of Users Digest, Vol 33, Issue 11<br>
*************************************<br>
</blockquote></div><br>