[asterisk-bugs] [JIRA] (ASTERISK-27930) res_pjsip: PJSIP TCP Segfault.

[Richard Mudgett (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-27930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Mudgett updated ASTERISK-27930:
---------------------------------------

    Assignee: Anna  (was: Unassigned)
      Status: Waiting for Feedback  (was: Open)

Have there been any crashes concerning this issue since the upgrade to 13.22.0?

Leave it in Wait-For-Feedback if there haven't been any.  The issue will automatically close in two weeks.  If any happen after that, the issue will automatically reopen if you comment on the issue.  We'll need new backtraces for the new Asterisk version if it happens.

> res_pjsip: PJSIP TCP Segfault.
> ------------------------------
>
>                 Key: ASTERISK-27930
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27930
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: 13.19.0, 13.19.1, 13.19.2, 13.20.0, 13.21.1, 13.21.0
>         Environment: Virtual box on VMWare
> CentOS Linux release 7.4.1708 (Core) 
> Linux  3.10.0-693.5.2.el7.x86_64
> CPU: 4 cores, Intel(R) Xeon(R) CPU E5-2637 v2 @ 3.50GHz
> RAM: 6GB
>            Reporter: Anna
>            Assignee: Anna
>              Labels: pjsip
>         Attachments: core-2018-06-21T08-28-01+0300-brief.txt, core-2018-06-21T08-28-01+0300-full.txt, core-2018-06-21T08-28-01+0300-locks.txt, core-2018-06-21T08-28-01+0300-thread1.txt, full_log.txt, pjsip.conf, pjsip_users.conf
>
>
> Hello,
> I experience random segfault crashes on Asterisk 13 setup with pjsip. Crashes happen for no apparent reason, it can be twice a day, can be once in 2 weeks. I have 2 servers with the same configuration and they both segfault from time to time. I can't reproduce this crash and don't know what is the reason. Also all endpoints that were registered before crash don't come back and register, i need to manually reboot/re-register all phones.
> I created a topic on Asterisk community and was advised to update my version since there is some issue with PJSIP using TCP protocol and if that won't help then i need to submit issue here.
> https://community.asterisk.org/t/segmentation-fault-asterisk-13-19-0/74289/9
> My asterisk is build from source with these options:
> PBX Core settings
> -----------------
>   Version:                     13.21.0
>   Build Options:               DONT_OPTIMIZE, DEBUG_THREADS, BETTER_BACKTRACES, BUILD_NATIVE, OPTIONAL_API
>   Maximum calls:               10000 (Current 4)
>   Maximum open file handles:   10000
>   Root console verbosity:      4
>   Current console verbosity:   4
>   Debug level:                 0
>   Maximum load average:        10.000000
>   Minimum free memory:         0 MB
>   Startup time:                08:28:10
>   Last reload time:            08:28:10
>   System:                      Linux/3.10.0-693.5.2.el7.x86_64 built by root on x86_64 2018-05-31 11:24:50 UTC
>   System name:                 
>   Entity ID:                   MY_MAC
>   PBX UUID:                    592b015e-a035-4b57-9bbe-8d8f785d663d
>   Default language:            en
>   Language prefix:             Enabled
>   User name and group:         asterisk/asterisk
>   Executable includes:         Disabled
>   Transcode via SLIN:          Enabled
>   Transmit silence during rec: Disabled
>   Generic PLC:                 Enabled
>   Generic PLC on equal codecs: Disabled
>   Min DTMF duration::          80
>   Cache media frames:          Enabled
>   RTP dynamic payload types:   96-127
> * Subsystems
>   -------------
>   Manager (AMI):               Enabled
>   Web Manager (AMI/HTTP):      Disabled
>   Call data records:           Enabled
>   Realtime Architecture (ARA): Enabled
> I have about 125 endpoints with static and dynamic AORs, i attached my pjsip config files. I have endpoints using TCP transport and trunks using UDP.
> I also attached backtraces from the core dump created on crash.



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