Summary:	ASTERISK-27628: Asterisk stops processing events from the network
Reporter:	Private Name (falves11)	Labels:	pjsip
Date Opened:	2018-01-26 22:58:45.000-0600	Date Closed:	2018-02-01 06:41:37.000-0600
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_pjsip
Versions:	14.7.5	Frequency of Occurrence	Frequent
Related Issues:
Environment:	Centos 7	Attachments:
Description:	[Jan 26 23:19:53] NOTICE[10731]: res_pjsip_sdp_rtp.c:164 rtp_check_timeout: Disconnecting channel 'PJSIP/ulaw-3210-0000050f' for lack of RTP activity in 60 seconds [Jan 26 23:20:26] NOTICE[10731]: res_pjsip_sdp_rtp.c:164 rtp_check_timeout: Disconnecting channel 'PJSIP/ulaw-3210-0000052f' for lack of RTP activity in 60 seconds [Jan 27 01:25:33] ERROR[10731]: stasis_message.c:124 stasis_message_create_full: Excessive refcount 100000 reached on ao2 object 0xb88b28 [Jan 27 01:25:33] ERROR[10731]: stasis_message.c:124 stasis_message_create_full: FRACK!, Failed assertion Excessive refcount 100000 reached on ao2 object 0xb88b28 (0) Got 13 backtrace records #0: [0x45e9b9] main/astobj2.c:552 __ao2_ref() (0x45e810+1A9) #1: [0x5e6ed5] main/stasis_message.c:125 stasis_message_create_full() (0x5e6e40+95) #2: [0x5aa1be] main/rtp_engine.c:3148 ast_rtp_publish_rtcp_message() (0x5aa100+BE) #3: [0x7fe118a4497f] res/res_rtp_asterisk.c:3797 ast_rtcp_write_report() #4: [0x7fe118a44d19] res/res_rtp_asterisk.c:3825 ast_rtcp_write() #5: [0x5cb958] main/sched.c:784 ast_sched_runq() (0x5cb860+F8) #6: [0x5cbc38] main/sched.c:139 sched_run() #7: [0x605d5a] main/utils.c:1235 dummy_start() siptrunks*CLI>
Comments:	By: Asterisk Team (asteriskteam) 2018-01-26 22:58:47.277-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: George Joseph (gjoseph) 2018-01-29 07:10:33.904-0600 It appears the bug you have submitted is against a rather old version of a supported branch of Asterisk. There have been many issues fixed between the version you are using and the current version of your branch. Please test with the latest version in your Asterisk branch and report whether the issue persists. Please see the Asterisk Versions [1] wiki page for info on which versions of Asterisk are supported. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions By: Private Name (falves11) 2018-01-29 08:25:51.491-0600 It is the current release of version 14. 14.7.5 how can it be an old version? I was using the current 13.X verison with pjsip and it froze after a day, everyday. It did not happen before the latest update. But I have not time to debug it, I am in production. I have 36 Ip addresses in the box and was instantiating several transports, one per IP. My peers use a different transport each, for business reasons. I use registration. By: Joshua C. Colp (jcolp) 2018-01-29 08:33:27.986-0600 Asterisk 14 only receives security fixes. The current supported versions for bugs and security fixes are Asterisk 13 and Asterisk 15. By: Joshua C. Colp (jcolp) 2018-02-01 06:41:37.904-0600 If you can reproduce this in a currently supported version of Asterisk then feel free to reopen.