[asterisk-bugs] [JIRA] (ASTERISK-26145) taskprocessor.c:887 taskprocessor_push: The 'subm:rtp_topic-000000de' task processor queue reached 500 scheduled tasks

Ross Beer (JIRA) noreply at issues.asterisk.org
Mon Jun 27 07:22:56 CDT 2016


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

Ross Beer commented on ASTERISK-26145:
--------------------------------------

Ok, Asterisk is on public IP addresses and not behind NAT. Therefore I have disabled this, on doing so I have reloaded 'res_rtp_asterisk.so' however, I am still seeing the following in the CLI:

STUN Debugging Enabled
STUN Packet, msg Binding Request (0001), length: 8
Found STUN Attribute Change Request (0003), length 4
Ignoring STUN attribute Change Request (0003), length 4
STUN Bind Request, username: <none>
STUN Packet, msg Binding Response (0101), length: 36
Found STUN Attribute Mapped Address (0001), length 8
Ignoring STUN attribute Mapped Address (0001), length 8
Found STUN Attribute Source Address (0004), length 8
Ignoring STUN attribute Source Address (0004), length 8
Found STUN Attribute Changed Address (0005), length 8
Ignoring STUN attribute Changed Address (0005), length 8
Dunno what to do with STUN message 0101 (Binding Response)

Does this module require a full restart to stop the STUN lookup?

Hopefully this will resolve the issue with the taskprocessor.


> taskprocessor.c:887 taskprocessor_push: The 'subm:rtp_topic-000000de' task processor queue reached 500 scheduled tasks
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26145
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26145
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_sdp_rtp
>    Affects Versions: 13.10.0-rc1
>         Environment: Fedora 23
>            Reporter: Ross Beer
>            Assignee: Unassigned
>         Attachments: backtrace-threads_20160627_CLEAN.txt, taskprocessor_CLEAN.txt, threads_CLEAN.txt
>
>
> Asterisk stops processing SIP packets due to the task processor exceeding 500 tasks.
> From the below, it looks like the RTP streams are not closing tasks related to RTP timeouts. 
> [2016-06-24 11:35:39] WARNING[313]: taskprocessor.c:887 taskprocessor_push: The 'subm:rtp_topic-000000de' task processor queue reached 500 scheduled tasks.
> [2016-06-24 11:36:08] NOTICE[313]: res_pjsip_sdp_rtp.c:165 rtp_check_timeout: Disconnecting channel 'PJSIP/<<Username>>-000040dd' for lack of RTP activity in 65 seconds
> No core dump is created as asterisk doesn't crash.



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



More information about the asterisk-bugs mailing list