[Serusers] features-callfwd.5.0.cfg to Asterisk VM

[Steve Blair]

Something like this will do the trick:

...
       t_on_failure("3");
       t_relay();
...

failure_route[3] {

    if (t_check_status("487")) {
            prefix("u");
            rewritehostport("<asterisk hostname>:<sip port>");
            append_branch();
            t_relay_to_udp("<asterisk hostname>", "<sip port>");
            break;
   } else if (t_check_status("486")) {
            prefix("b");
            rewritehostport("<asterisk hostname>:<sip port>");
            append_branch();
            t_relay_to_udp("<asterisk hostname>", "<sip port>");
            break;
  }

The prefix "u" and prefix "b" commands allow you to indicate to Asterisk 
whether to play the unavailable or busy greeting by prefixing the r-uri 
username with the appropriate letter. You'll need to check the actual 
status codes however because these are just examples.

-Steve

Ali Zaidi wrote:

> Z,
>  
> I will take a look on those config. I was just looking for a quick 
> fix, i know lot of ppl using this pre-config from onsip and also want 
> similar that i'm trying to achieve.
>  
> I will try that in this weekend.
>  
> Ali...
>
>
>  
> On 2/16/06, *zhangshuai* <zhangshuai at goldentek.biz 
> <mailto:zhangshuai at goldentek.biz>> wrote:
>
>     Dear Ali Zaidi,
>
>
>     I'm testing the forwarding now, too. I think you could be more
>     aware after read SER-GettingStarted doc at ONsip.org. And you may
>     want to try the onr.cfg, or redirect.cfg, which are much more
>     concise than features-callfwd.5.0.cfg, in the directory of
>     examples of SER src package, first.
>
>
>     >Hi,
>     >
>     >I'm having some problem forwarding to Asterisk VM. What i want is
>     when ever
>     >486, 404, 408 or 480 error triger then ser should forward INVITE to
>     >Asterisk.
>     >Some one please tell me where and what i write in my
>     >features-callfwd.5.0.cfg so it will forward to my asterisk box.
>     >
>     >Thanks,
>     >
>     >Ali... :lol:
>     >_______________________________________________
>     >Serusers mailing list
>     >serusers at lists.iptel.org <mailto:serusers at lists.iptel.org>
>     > http://lists.iptel.org/mailman/listinfo/serusers
>     >
>
>
>
>
>
>
>
>     _______________________________________________
>     Serusers mailing list
>     serusers at lists.iptel.org <mailto:serusers at lists.iptel.org>
>     http://lists.iptel.org/mailman/listinfo/serusers
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Serusers mailing list
>serusers at lists.iptel.org
>http://lists.iptel.org/mailman/listinfo/serusers
>  
>