You have to implement a serial forking logic inside your configuration script:
http://www.voice-system.ro/docs/avpops/ar01s08.html#ex_serial_forking
Based on failure reason (time out, busy) you can do the proper redirect from failure_routed -- use t_check_status() to get the reply code.
Cheers, Daniel
On 01/17/06 08:11, unplug wrote:
I am using the features-callfwd.cfg script with mediaproxy in a testing server. I can make call directly from phone to phone and forward call. However, it is failed to forward call on no answer and forward call on busy. In my testing server, it only has a network interface. I wonder if it is the cause of the problem. Does it need to have 2 network interfaces (one for external and one for internal) for those forward features work?
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users