[Home]

Summary:ASTERISK-15825: dtmf logging to console not working
Reporter:Brian J. Murrell (brian_j_murrell)Labels:
Date Opened:2010-03-16 15:27:02Date Closed:2011-06-07 14:05:19
Priority:MinorRegression?No
Status:Closed/CompleteComponents:General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:I have my logger.conf set to log DTMF to the console:

console => notice,warning,error,dtmf

and the console reflects that:

linux*CLI> logger show channels
Channel                        Type     Status    Configuration
-------                        ----     ------    -------------
/var/log/asterisk/messages     File     Enabled    - Warning Notice Error
                              Console  Enabled    - DTMF Warning Notice Error
/var/log/asterisk/debug        File     Enabled    - Debug Notice

However, when I make a call (from a SIP extension) either directly to Asterisk itself and enter DTMF, say, to input a voicemail password or get bridged to an outside line and enter a DTMF, say, to choose an option at a remote IVR I don't see the DTMF debug on the console as I did with 1.4.x.

I know the DTMF is working since the results I receive in response to the DTMF that I send are expected.

****** ADDITIONAL INFORMATION ******

I am using 1.6.2.2.  Using a newer version is not terribly easy as I am installing from a distro and not undertaking the considerable task of building from source.
Comments:By: Leif Madsen (lmadsen) 2010-03-16 18:39:27

Have you done 'core set debug 5' ?  I have a feeling that is your problem.
By: Brian J. Murrell (brian_j_murrell) 2010-03-16 21:02:09

Well, this would seem to be "new" since 1.4.17ish if it were the case, but it seems it's not:

linux*CLI> core set debug 5
Core debug was 0 and is now 5
 == Using SIP RTP CoS mark 5
   -- Executing [*112000@internal-sip:1] NoOp("SIP/1011002206-0000006d", "") in new stack
   -- Executing [*112000@internal-sip:2] Set("SIP/1011002206-0000006d", "CDR(accountcode)="internal"") in new stack
   -- Executing [*112000@internal-sip:3] Answer("SIP/1011002206-0000006d", "") in new stack
   -- Executing [*112000@internal-sip:4] Wait("SIP/1011002206-0000006d", "1") in new stack
   -- Executing [*112000@internal-sip:5] VoiceMailMain("SIP/1011002206-0000006d", "2000") in new stack
   -- <SIP/1011002206-0000006d> Playing 'vm-password.gsm' (language 'en')
[Mar 16 21:58:40] WARNING[8881]: app_voicemail_imap.c:2492 mm_log: IMAP Warning: Bad quota root list for vmINBOX
[Mar 16 21:58:40] WARNING[8881]: app_voicemail_imap.c:2492 mm_log: IMAP Warning: Bad quota root list for vmINBOX
   -- <SIP/1011002206-0000006d> Playing 'vm-youhave.gsm' (language 'en')
   -- <SIP/1011002206-0000006d> Playing 'vm-no.gsm' (language 'en')
   -- <SIP/1011002206-0000006d> Playing 'vm-messages.gsm' (language 'en')
   -- <SIP/1011002206-0000006d> Playing 'vm-opts.gsm' (language 'en')
   -- <SIP/1011002206-0000006d> Playing 'vm-helpexit.gsm' (language 'en')
   -- <SIP/1011002206-0000006d> Playing 'vm-options.gsm' (language 'en')
   -- <SIP/1011002206-0000006d> Playing 'vm-options.gsm' (language 'en')
   -- <SIP/1011002206-0000006d> Playing 'vm-options.gsm' (language 'en')

There was a mailbox password required to access that voice mail.  As you can see, the DTMF to give the password was not displayed.
By: Brian J. Murrell (brian_j_murrell) 2010-03-23 06:01:39

Any update?  I answered your question about having 'core set debug 5' set and it didn't help.

At least please change the status so that it's not reflecting that I have not provided feedback.


By: Leif Madsen (lmadsen) 2010-03-24 10:42:42

No idea, because I haven't had an issue with that for any of the boxes I've been testing on. Not sure what to tell you.
By: Leif Madsen (lmadsen) 2010-03-24 10:43:19

I'd suggest getting on the asterisk-users mailing list and see if anyone else has the same issue who can report back some information to allow us to reproduce this.
By: Paul Belanger (pabelanger) 2010-04-28 15:27:03

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.

Further information can be found at http://www.asterisk.org/developers/bug-guidelines