[asterisk-bugs] [JIRA] (ASTERISK-21014) logger.c Call_ID 'bound' or 'removed' DEBUG messages spammed during a feature code attended transfer

[Matt Jordan (JIRA)]

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

Matt Jordan updated ASTERISK-21014:
-----------------------------------

    Target Release Version/s: 11.4.0
    
> logger.c Call_ID 'bound' or 'removed' DEBUG messages spammed during a feature code attended transfer
> ----------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21014
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21014
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/General, Features
>    Affects Versions: SVN
>         Environment: Asterisk SVN-branch-11-r380043 built by root @ ubuntu on a x86_64 running Linux on 2013-01-26 23:28:17 UTC
>            Reporter: Rusty Newton
>            Severity: Trivial
>      Target Release: 11.4.0
>
>         Attachments: full_log.txt
>
>
> Happens during SIP to SIP call with feature code attended transfer.
> full_log attached.
> * 6001 dials 6002
> * 6002 answers
> * 6002 dials "*2" waits a few seconds and then hangs up.
> During "waits a few seconds" the full log will show 80-100 of the follow DEBUG messages per second.
> {noformat}
> [Jan 30 10:29:23] DEBUG[12222][C-00000005] logger.c: CALL_ID [C-00000005] bound to thread.
> [Jan 30 10:29:23] DEBUG[12222][C-00000005] logger.c: Call_ID [C-00000005] being removed from thread.
> {noformat}
> The issue also occurs if and while 6002 dials the transfer destination. The messages stop spamming after dialing a transfer destination or the channels hang up.
> No noticeable effect on a single call, but may be indicative of something happening that shouldn't be.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira