[asterisk-bugs] [JIRA] (ASTERISK-25504) Asterisk with pjsip driver crashes codec related?

[Rusty Newton (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-25504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=228442#comment-228442 ] 

Rusty Newton commented on ASTERISK-25504:
-----------------------------------------

Let's not confuse this issue. The high CPU issue sounds different enough to split it out. Perhaps sometimes the high CPU leads to a crash.. but that is yet to be seen.

For now, if the crash occurs again report back on this issue. Otherwise please create a new issue for the high CPU problem and attach all relevant debug to that new issue. Most preferably any details that may lead to reproduction of the issue.

> Asterisk with pjsip driver crashes codec related?
> -------------------------------------------------
>
>                 Key: ASTERISK-25504
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25504
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.5.0
>         Environment: Asterisk Realtime 13.5 PJSIP Driver 
> mysql Ver 14.14 
> pjproject 2.3 
> spandsp 0.0.6 
> jansson 2.7 
> CentOS 6.6 64 bits on Vmware 
> Number of endpoints : > 700 
> Numbers of calls : 3000/day 
> Our Hardware: 
> Phones : Cisco SPA514G FW: 7.5.7 
> ATA : Audiocodes MP124 
> T1 : Mediatrix 3532 ISDN to SIP gateway 
> CPU : Quadcore Intel(R) Xeon(R) CPU E5-2650 
> RAM : 3 GB
>            Reporter: Carl Fortin
>            Assignee: Unassigned
>         Attachments: backtrace_2.txt, backtrace.txt, Endpoint_detail.txt, High_CPU.txt, My_debug_log.txt
>
>
> We are running asterisk 13.5 pjsip in a production environment and I had 2 crashes yesterday.  It happened shortly after enabling the g722 codec to a couples of phones in our ps_endpoints database. I'm not sure if the problem is coming from this modification but the same phone with the g722 codec made asterisk crashed 2 times.
> Can someone look and my backtrace and my full debug log to see if it could be related to a codec negotiation?



--
This message was sent by Atlassian JIRA
(v6.2#6252)