It looks like the posted error message are from the second proxy. Thus the ser.cfg of the second proxy would be needed.
Which version of ser do you use? 0.8.14? 0.9? CVS head? I'm not familiar with vm, but there were some changes to vm handling in ser recently. vm handling moved from vm module to tm module. Maybe your problems are related with this change.
regards, klaus
PS: Please always Cc: to the list.
Llanos Serna García-Conde wrote:
Hello,
I use two proxies, the parts of ser.cfg I enclose are the SER_A.cfg;
SER_A <---IP interface--> SER-B <--fifo interface--> SEMS
172.25.97.19 172.25.97.19
port: 5060 port:5090
Thanks,
Llanos
Are you using one or two proxies (is there a dedicated vm proxy?)?
regards, klaus
Llanos Serna García-Conde wrote:
Hello, I'm trying to test voicemail just with one sip-phone destination (331106), and I want the calls to be forwarded to voicemail in case the phone is busy or doesn't answer in 15 seconds (modparam("tm","fr_inv_timer",15) and modparam("tm","fr_timer",10)). I looked at the examples and tried. I enclose the important parts of ser.cfg: First I tried: route { if (!uri=~"^sip:331105@*") //this will be sip 331106 { t_on_failure("1"); } if (!t_relay()) { sl_reply_error(); }
} failure_route[1]{ t_relay_to_udp ( "172.25.97.19","5090"); break; } I got the errors: ERROR: t_forward_nonack: no branched for fwding ERROR: failure_route: t_relay_to failed Then I changed failure_route to: failure_route[1]{ revert_uri(); rewritehostport("172.25.97.19:5090"); append_branch(); t_relay_to_udp ( "172.25.97.19","5090"); } And I got the errors: 1(9029) ERROR: t_should_relay: status rewrite by UAS: stored: 408, received: 487 9(9053) ERROR: fifo_t_reply: lookup failed 9(9053) ERROR: fifo_server: command (vm_reply) processing failed I'm sure the way to do it must be very simple, but I just don't know how to do it. Pleas help!! Llanos
Sems mailing list sems@lists.iptel.org http://lists.iptel.org/cgi-bin/mailman/listinfo/sems