[asterisk-bugs] [JIRA] (ASTERISK-26836) res_pjsip: Memory corruption of endpoint

[Daniel Journo (JIRA)]

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

Daniel Journo commented on ASTERISK-26836:
------------------------------------------

What is the environment? 
Centos 6.8

Are you strictly using .conf files?
For pjsip config, I'm using static files only.

Are you using realtime at all?
Yes, for queues, queue members, queue logs, voicemail and musiconhold.

What's the configuration?
Attached is my pjsip transports and an example of how my endpoints are all defined. They are identical apart from the username/password and mailbox.

What's the usage patterns (are there lots of calls going on at the same time)?
Average usage at the time. Peak usage is around 40 calls. When this last one occurred, there were about 10 calls.
I can't spot an obvious way to repeat the issue but it does repeat.


> res_pjsip: Memory corruption of endpoint
> ----------------------------------------
>
>                 Key: ASTERISK-26836
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26836
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 13.11.2, 13.14.0
>         Environment: Centos 6, PJSIP 2.4.5
>            Reporter: Daniel Journo
>            Assignee: Unassigned
>         Attachments: cli.txt, pjsipconfig.txt
>
>
> This is a recurring issue on all my production servers. When it happens, Asterisk stops serving SIP clients properly.
> It reads to me as a memory leak as it's just one character incrementing.
> The latest time, it occurred shortly (but not immediately) after I issued a 'pjsip reload', but it may have just been a coincidence. I've included the timing in the CLI log.
> Seems to happen every 4 or 5 days requiring a 'killall -9 asterisk' and 'database deltree registrar' in order to get working again. I can't remember, but the first time it happened, Asterisk would not respond to 'core stop now' or 'core restart now' so I had to do killall. But I havent tried 'core stop now' during subsequent issues.
> This issue stops all endpoints from communicating with Asterisk. Even ones that have already registered.



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