I have been using the Voicemail ODBC Storage capability of Asterisk in v1.2.0 without any problems. When I upgraded to v1.2.1 and tried to leave a voicemail, I get a message on the CLI that it can not find that user configured. I do an ‘odbc show’ and see that Asterisk is successfully connected to the MySQL DSN (besides no config changes were made).
If I rollback to v1.2.0 all works well again. Has anyone else seen this? Please post if you have. Meanwhile, I will do more testing and report to the bug tracker if warranted.
As I test this and think it through, it is actually the Asterisk Realtime Architecture for Voicemail that appears to be at fault in v1.2.1. Extensions, SIP, IAX all work fine, just appears to be when it tries to find voicemail users in the ARA database.
[quote=“MuppetMaster”]As I test this and think it through, it is actually the Asterisk Realtime Architecture for Voicemail that appears to be at fault in v1.2.1. Extensions, SIP, IAX all work fine, just appears to be when it tries to find voicemail users in the ARA database.
Anyone else seen this in v1.2.1?[/quote]From another forum[quote]‘searchcontexts=yes’
added to my voicemail.conf file solved the problem.[/quote]Hope that does it.
That did the trick, thanks. You caught me mid-bug report on Mantis, so I cancelled that.
Looking at the changelog I do not see where this is specifically addressed:
[quote=“Changelog”]* apps/app_voicemail.c, configs/voicemail.conf.sample, UPGRADE.txt:
allow previous context-searching behavior to be used if desired
(issue #5899)
* apps/app_voicemail.c: Only look in 'default' context when no context defined to VoiceMailMain(). (issue #5887)[/quote]
Although, it looks like something was impacted in the above. May still be a bug? What do you think?
[quote=“MuppetMaster”]…
Although, it looks like something was impacted in the above. May still be a bug? What do you think?[/quote]If you look at the sample voicemail.conf:
; searchcontexts=yes ; Current default behavior is to search only the default context
; if one is not specified. The older behavior was to search all contexts.
; This option restores the old behavior [DEFAULT=no]
It looks like a CHANGE, not a bug, to me.
First, should Asterisk not be backward compatible? If you upgrade, it should not ‘break’ a feature that has been in place and working for sometime. Also, I am using ‘default’ as my context in the voicemail ARA database. Should Asterisk not automatically (as obviously it has in previous versions with ARA) default to ‘default’ if that parameter is not configured?
[quote=“MuppetMaster”]First, should Asterisk not be backward compatible? If you upgrade, it should not ‘break’ a feature that has been in place and working for sometime. Also, I am using ‘default’ as my context in the voicemail ARA database. Should Asterisk not automatically (as obviously it has in previous versions with ARA) default to ‘default’ if that parameter is not configured?[/quote]Maybe a CHANGE and a BUG?
I agree 100%, new versions SHOULD be backward compatible, unless there is a very good reason, like security or such.
[quote=“lonnie”][quote=“MuppetMaster”]First, should Asterisk not be backward compatible? If you upgrade, it should not ‘break’ a feature that has been in place and working for sometime. Also, I am using ‘default’ as my context in the voicemail ARA database. Should Asterisk not automatically (as obviously it has in previous versions with ARA) default to ‘default’ if that parameter is not configured?[/quote]Maybe a CHANGE and a BUG?
I agree 100%, new versions SHOULD be backward compatible, unless there is a very good reason, like security or such.
Lonnie[/quote]
Alright, I will report it to Mantis (report#6001) in this context. Lets see if I get spanked.
