[OpenSIPS-Users] Opensips 3.1Debian constantly crashing

[Mario San Vicente]

Hello Bogdan-Andrei,

I ran some traffic without rtpengine and with the codec operations, i did
not got any core files.  I will take care of not combining those commands.


Thanks and regards.
Mario

On Thu, Oct 21, 2021 at 7:26 AM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi Mario,
>
> So you do both rtpengine ops and codecs ops in your cfg. This is a bit of
> a receipt for disaster (as both are independently changing the SDP), still
> not for a crash.
>
> Could you try to run both codec ops, but without rtpengine, just to see if
> ok ?
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS eBootcamp 2021
>   https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>
> On 10/19/21 7:20 PM, Mario San Vicente wrote:
>
> Hello Bogdan-Andrei,
>
> I removed the following lines and it is working fine now.  Not sure if the
> issue was one or the combination of those 2 lines that made opensips crash.
>
>               #codec_delete_re("PCMA|PCMU");
>               #codec_delete_except_re("speex");
>
> The reason for using those lines was that opensips was doing transcoding
> and after a while it stops doing the transcode, it just was bypassing the
> original codec offer.   This is also solved, the problem is that
> the rtpengine_offer was not closing properly and then i ran out of ports.
>    The solution was to add rtpengine_delete(); at the failure route.
>
>
> Thank you all for your help!
>
> Regards.
> Mario
>
> On Tue, Oct 19, 2021 at 2:01 AM Bogdan-Andrei Iancu <bogdan at opensips.org>
> wrote:
>
>> Hi Mario,
>>
>> What is the codec relate operation you do from the script? As it looks it
>> is crashing there.
>>
>> Regards,
>>
>> Bogdan-Andrei Iancu
>>
>> OpenSIPS Founder and Developer
>>   https://www.opensips-solutions.com
>> OpenSIPS eBootcamp 2021
>>   https://opensips.org/training/OpenSIPS_eBootcamp_2021/
>>
>> On 10/19/21 12:15 AM, Mario San Vicente wrote:
>>
>> Thank you Giovany .
>>
>> I got some info, but I'm not sure how to proceed....  Looks like an issue
>> assigning core vars..  Here the whole info in a txt file.
>>
>>
>> {rs = {s = 0x6dc2d4a3fa5df100 <error: Cannot access memory at address
>> 0x6dc2d4a3fa5df100>,
>> sval = {s = 0x100000002 <error: Cannot access memory at address
>> 0x100000002>, len = -1510612476}
>>
>> Thank your comments.
>>
>> On Mon, Oct 18, 2021 at 12:39 PM Giovanni Maruzzelli <gmaruzz at gmail.com>
>> wrote:
>>
>>> On Mon, Oct 18, 2021 at 7:01 PM Mario San Vicente <
>>> mrsanvicente at gmail.com> wrote:
>>>
>>>> Hello Ovidiu,
>>>>
>>>> That works for getting the core files.  Then i run the command bt full
>>>> and got the following:
>>>>
>>>>
>>> You must install the opensips-dbg debian package, it contains the
>>> symbols, then restart opensips, then retake the core and you'll see info in
>>> it.
>>>
>>> -giovanni
>>>
>>> --
>>> Sincerely,
>>>
>>> Giovanni Maruzzelli
>>> OpenTelecom.IT
>>> cell: +39 347 266 56 18
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>
>>
>> --
>> Mario San Vicente
>> Cheers!
>>
>> _______________________________________________
>> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>>
>
> --
> Mario San Vicente
> Cheers!
>
>
>

-- 
Mario San Vicente
Cheers!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20211021/37eaba99/attachment.html>