I've commited changes to Voicemail2: * Handle properly when being left a message while checking VM -- this should fix the "saving to your inbox" issue too, at least in principle. And to DISA: * Properly handle extensions with multiple matches and "dots" Please let me know on or off list about any feedback you have regarding these changes. Mark
mmh, there's still an error when compiling voicemail2 with mysql support : gcc -pipe -Wall -Wmissing-prototypes -Wmissing-declarations -O6 -g -Iinclude -I../include -DUSEMYSQLVM=\"1\" -D_REENTRANT -D_GNU_SOURCE -march=i686 -DASTERISK_VERSION=\"CVS-07/21/02-14:49:14\" -DDO_CRASH -DDEBUG_THREADS -c -o app_voicemail2.o app_voicemail2.c app_voicemail2.c: In function `find_user': app_voicemail2.c:221: invalid type argument of `unary *' app_voicemail2.c: In function `load_config': app_voicemail2.c:2464: warning: unused variable `var' app_voicemail2.c:2463: warning: unused variable `cat' app_voicemail2.c: At top level: app_voicemail2.c:2425: warning: `append_mailbox' defined but not used make[1]: *** [app_voicemail2.o] Error 1 make[1]: Leaving directory `/root/phony/asterisk/apps' make: *** [subdirs] Error 1 [root@dhcp-3 asterisk]# I think that line 221 *retval->attach=-1; must be retval->attach=-1; Matteo. Il dom, 2003-06-15 alle 13:34, Mark Spencer ha scritto:> I've commited changes to Voicemail2: > > * Handle properly when being left a message while checking VM -- > this should fix the "saving to your inbox" issue too, at least in > principle. > > And to DISA: > > * Properly handle extensions with multiple matches and "dots" > > Please let me know on or off list about any feedback you have regarding > these changes. > > Mark > > > _______________________________________________ > Asterisk-Users mailing list > Asterisk-Users@lists.digium.com > http://lists.digium.com/mailman/listinfo/asterisk-users
>[snip] >And to DISA: > > * Properly handle extensions with multiple matches and "dots" > >Please let me know on or off list about any feedback you have regarding >these changes. > >MarkOK, this patch seems to work after some tests. DISA no longer "jumps" to wildcarded strings that might match in the called context, which is very handy for those of us that use the "broken" behavior of SIP dialing batches to do things like set variables, etc. before the meat of the dial sequence is executed. A quick and uneducated look at the source shows a 10-second timeout now on DTMF dialed sequences before the sequence is executed into the context. This means that upon hearing a DISA dialtone, this happens: (1) - you type the first digit of your password, dialtone stops. You must hit a key every 20 seconds, and you must end the password sequence by typing "#". You get a second dialtone. Proceed to (2) OR - proceed to (2) if "no-password" is set as the password (2) You type the first digit of the number to be dialed, and dialtone stops. You must press a digit before ~10 seconds have elapsed, or the number to that point will be dialed. To have the number dialed in the context you have specified, merely wait 10 seconds for the timeout. Dialing a "#" key will be appended to the end of the number, so it is NOT required to complete a DISA dialing sequence except for password sequences. Do I have this right? If so, it would appear that it would be possible to reduce the 10 second timeout to something smaller by changing this like in app_disa.c: static int digittimeout = 10000; /* 10 seconds subsequent digit timeout */ JT
It would be really nice if the DISA allowed one to make follow-on calls by pressing some key sequence (say, press * three times in a row within one second). This especially helps when you are at a hotel that charges for each call. We put our DISA on a toll-free number, and as long as it supports follow-on calls, you can make calls all night for that $1 they charge per call.