[asterisk-bugs] [Asterisk 0011910]: [patch] VoiceMail d([context]) option does not set extension, priority

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11910 
====================================================================== 
Reported By:                nic_bellamy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11910
Category:                   Applications/app_voicemail
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 102060 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             02-02-2008 18:23 CST
Last Modified:              02-03-2008 00:02 CST
====================================================================== 
Summary:                    [patch] VoiceMail d([context]) option does not set
extension, priority
Description: 
The VoiceMail() 'd' option is supposed to allow you to dial a single digit
extension during the playback of the initial prompt.

This doesn't work, but is easily fixed.

Using the following very simple example extensions.conf (assume voicemail
box is all happy):

[default]
exten => 200,1,VoiceMail(200,ud(vmexit))

[vmexit]
exten => _X,1,SayDigits(${EXTEN})
exten => _X,n,DumpChan()
exten => _X,n,Goto(default,200,1)

Now, when you start voicemail and enter a digit, it should jump to that
digit in the vmexit context.

It doesn't - it tries to jump to the original extension in the vmexit
context, ie.:

[Feb  3 13:01:26] WARNING[22057]: pbx.c:3358 __ast_pbx_run: Channel
'SIP/200-081ee6b8' sent into invalid extension '200' in context 'vmexit',
but no invalid handler

====================================================================== 

---------------------------------------------------------------------- 
 nic_bellamy - 02-03-08 00:02  
---------------------------------------------------------------------- 
Please put a hold on committing this for the moment.

A bit more playing around has found that although this does fix a valid
bug, there's still some behavior that's a bit unpredictable around the
functioning of 'a' / '*' and 'o' extensions when you're using the d(ctx)
flag.

I'll come up with something saner and update the patch. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-03-08 00:02  nic_bellamy    Note Added: 0081609                          
======================================================================