Jiri,

If you want failure_route to be evoked only for some calls, then
set t_on_failure_route for such. You already do so in your script,
don't you?
**************** Yes, t_on_failure is only set for calls to internal network addresses. VM works great for users that aren't logged in.

There is other problem though -- the failure_route logic for VM should be different
from that in route block -- you can't create transaction state two times
(first time with t_relay, second time with t_newtran). SER will certainly
complain with some error message in your logs.
*********  THIS is the big questioin. SER certainly does complain with error messages. What should the failure route logic for VM be? I can't find any examples of this in the documentation. I've tried calling the vm command without the t_newtran() function in front of it but that results in another error in the logs. (see below)

Sep 25 19:46:49 jiffypop /usr/local/sbin/ser[23840]: submit_query(): You have an error in your SQL syntax. C

heck the manual that corresponds to your MySQL server version for the right syntax to use near ''' at line 1

Sep 25 19:46:49 jiffypop /usr/local/sbin/ser[23840]: submit_query(): Error while submitting query

Sep 25 19:46:49 jiffypop /usr/local/sbin/ser[23840]: ERROR: vm: db_query() failed.

Sep 25 19:46:49 jiffypop /usr/local/sbin/ser[23840]: ERROR: vm: vm_get_user_info failed

Sep 25 19:46:49 jiffypop /usr/local/sbin/ser[23840]: route[3]:vm:voicemail failed

So what's the work around? Is there a way to get around this? What should the failure_route logic be?

Thanks,

G.