[Home]

Summary:ASTERISK-21152: if pressed * the user menu is not working
Reporter:Daniel Knoll (kenji)Labels:
Date Opened:2013-02-22 10:29:08.000-0600Date Closed:2013-03-15 15:06:07
Priority:MajorRegression?Yes
Status:Closed/CompleteComponents:Applications/app_meetme
Versions:1.8.21.0 Frequency of
Occurrence
Constant
Related
Issues:
Environment:Asterisk 1.8.21.0-rc1 built by root @ asterisk on a x86_64 running Linux on 2013-02-01 20:48:28 UTC Linux asterisk 2.6.26-2-amd64 #1 SMP Wed Sep 21 03:36:44 UTC 2011 x86_64 GNU/Linux Debian Version: 5.0.9Attachments:( 0) rtp-debug_usermenu_not-working.log
( 1) rtp-debug-asterisk.1.8.17_usermenu_working.log
( 2) usermenu-not-working.log
Description:If you're in a Conference Room With MeetMe(123,MsX) and press the * key to get the user menu, it is not working and not playing "conf-usermenu"
Comments:By: Matt Jordan (mjordan) 2013-02-22 13:25:25.207-0600

Can you provide the same DEBUG log illustrating the problem, only with 'rtp set debug on' enabled? If other DTMF keys are working, please provide an example where a DTMF key press works and one where it does not work.

By: Daniel Knoll (kenji) 2013-02-22 16:17:15.797-0600

Hi, ok here the logs, 1 with usermenu not working and 1 with a working sample of another asterisk, but i can't see the differences. Sorry. Hope that may be help.

By: Rusty Newton (rnewton) 2013-02-27 16:02:08.806-0600

Thanks for the logs. Looks like you removed DEBUG from them, and may have also cut out some important parts.

For both working and non working, can you provide the log covering from the beginning of that call to end (just to be sure we have everything in between).

Make sure to include VERBOSE, DEBUG, DTMF message types and the output of 'rtp set debug on'. Be sure that VERBOSE and DEBUG levels are turned up to at least 5.

As far as the current logs go , it looks like in both cases the * digit is being detected, I just can't see what else happens other than that since nothing else is included in the logs. Be sure you don't have another feature or application in use on those channels set to use the * digit. I've seen interaction before with configuration in agents.conf and features.conf where a * set for functionality in both caused unexpected behavior.



By: Matt Jordan (mjordan) 2013-03-15 15:06:02.474-0500

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