Summary: | ASTERISK-15999: contexts and voicemail | ||
Reporter: | Juan Settecase (juanctkc) | Labels: | |
Date Opened: | 2010-04-22 10:27:07 | Date Closed: | 2010-04-22 11:10:41 |
Priority: | Trivial | Regression? | No |
Status: | Closed/Complete | Components: | Applications/app_voicemail |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ( 0) voicemail.conf | |
Description: | Hi, I have an problem with voicemail and contexts. I'm define a mailbox in mgcp.conf or sip.conf and voicemail dont recieve that value. ¿? Ex. mgcp.conf [0011aecc4516.mta] host=0011aecc4516.mta dtmfmode=rfc2833 ncs=1 mailbox=3885426000@base wcardep=aaln/* context=base ; callerid = "3885426000" <3885426000> line => aaln/1 nat=yes transfer=yes cancallforward=yes ; log extract full.log [Apr 22 12:18:18] DEBUG[14365] res_config_mysql.c: MySQL RealTime: Retrieve SQL: SELECT * FROM voicemail WHERE mailbox = 'aaln/1' AND context = '0011aecc4516.mta@' [Apr 22 12:18:18] WARNING[14365] app_voicemail.c: No entry in voicemail config file for 'aaln/1' It seems to recieve another vm context and mailbox. extensions.conf exten => s,1,Dial(${ARG2},60) ; Ring the interface, 20 seconds maximum exten => s,2,Goto(s-${DIALSTATUS},1) ; Jump based on status (NOANSWER,BUSY,CHANUNAVAIL,CONGESTION,ANSWER) exten => s-NOANSWER,1,Voicemail(${ARG1},u) ; If unavailable, send to voicemail w/ unavail announce ;exten => s-NOANSWER,2,Goto(default,s,1) ; If they press #, return to start exten => s-NOANSWER,n,Hangup() exten => s-BUSY,1,Voicemail(${ARG1},b) ; If busy, send to voicemail w/ busy announce ;exten => s-BUSY,2,Goto(default,s,1) ; If they press #, return to start exten => s-BUSY,n,Hangup() exten => _s-.,1,Goto(s-NOANSWER,1) ; Treat anything else as no answer exten => a,1,VoicemailMain(${ARG1}) ; If they press *, send the user into VoicemailMain voicemail.conf attached Any ideas? How ever you need, ask me. | ||
Comments: | By: Paul Belanger (pabelanger) 2010-04-22 11:10:19 Thanks for your comments. This does not appear to be a bug report and we are closing it. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker, http://www.asterisk.org/support |