Hi Joao,
is quite impossible to tell what's the problem only based on the cfgs.
please extract the backtrace from the core file in order to help you -
see my previous email about how to do it.
regards,
bogdan
Joao Pereira wrote:
Hello
I compiled openser myself.
Now I tried openser with a simpler configuration and it worked...
I had an openser.cfg that uses RTPproxy and TLS.... and the seg fault
happened when I used that file.
Now with a simpler openser.cfg (like the sample) just with TLS,
openser started :)
I will try to find the problem in the openser_rtpproxy_tls
configuration file... both files are in attachment
Thank you very much for the help
Joao
Bogdan-Andrei Iancu wrote:
> Hi Joao,
>
> do you compiled openser by yourself or you installed the binaries?
> to be able to get info from core is essential to have the correct
> binary.
>
> so, to simplify the thinks, please extract the backtrace from the
> core by yourself:
> 1) enter gdb: gdb openser_binar_file core_file
> 2) get backtrace : bt
>
> send me all the output of gdb from the beginning.
>
> thanks,
> bogdan
>
> Joao Pereira wrote:
>
>> I already did it, I deleted the file
>> /usr/local/sbin/openser
>> and all modules in:
>> /usr/local/lib/openser/modules/
>>
>> I installed again openser 1.0.1-tls and the problem persists.
>>
>> The core file has 34 Mb, so I putted it in:
>> sip.startel.pt/core/
>>
>> Thanks for the help.
>> Joao Pereira
>