On 6/18/07, inge <inge@legos.fr> wrote:

Hi Jai,

That's the mean I used to provide call forward :

In route[3] :

        # ----------------------------------- Mark the CFU
----------------------------------

        if (avp_db_load("$ruri/username", "s:cfu/usr_callfw")) {
                setflag(22);
                avp_pushto("$ruri", "s:cfu");
                route(30);
                route(1);
                break;
        };

        # ----------------------------------- Mark the CFB
-----------------------------------

        if (avp_db_load("$ruri/username", "s:cfb/usr_callfw")) {
                if (!avp_check("s:cfb", "eq/$ruri/i")) {
                        setflag(20);
                };
        };

        # ----------------------------------- Mark the CFNA
-----------------------------------

        if (avp_db_load("$ruri/username", "s:cfna/usr_callfw")) {
                if (!avp_check("s:cfna", "eq/$ruri/i")) {
                        setflag(21);
                };
        };

For CFU I put the result taken from DB directly in URI and route to
PSTN.

For CFB & CFNA I do the same treatment but with an other way with a
flag. In the failure route :

        if (isflagset(20) && t_check_status("486")) {
                if (avp_pushto("$ruri", "s:cfb")) {
                        avp_delete("s:cfb");
                        resetflag(20);
                        setflag(23);
                        xlog("L_WARN","time=[%Tf] call id=[%ci] call seq=[%cs] contact
header=[%ct] from uri=[%fu] from tag=[%ft] request's method=[%rm]
request's uri=[%ru] to uri=[%tu] to tag=[%tt] sip message id=[%mi]
process id=[%pp] ip source=[%is] flags=[%mf], Forward on busy\n");
                        route(30);
                        route(1);
                        break;
                };
        };

Sincerely,

Adrien

Le vendredi 15 juin 2007 à 08:34 -0700, Jai Rangi a écrit :
> Hello Igne,
> Can you please share the piece of code for this.
>
> Thank you,
> -Jai
> On 6/15/07, inge <inge@legos.fr> wrote:
>         Hi Jai,
>
>         I don't have problems with caller ID. In a case of CFNA/CFB or
>         CFU, I
>         see on the terminal the right caller id.
>
>         I think thanks to unchange sip_from/sip_to URI, wich were use
>         for
>         signalisation maybe.
>
>
>         Le mardi 12 juin 2007 à 16:28 -0700, Jai Rangi a écrit :
>         > Not only billing part, but for caller id also. The final
>         destination
>         > should see the right caller id (Original call generator).
>         > Can you please share where I can find such a plugin. I have
>         been
>         > looking for something like that.
>         >
>         > Thank you,
>         > -Jai
>         >
>         >
>         > On 6/11/07, inge <inge@legos.fr> wrote:
>         >         Hi Greger,
>         >
>         >         Thanks for you answer and sorry for mine, I was away
>         from my
>         >         office
>         >         since some days.
>         >
>         >         In fact, it's a very special case. But finally I can
>         see the
>         >         forward
>         >         with i_uri and o_uri in my acc table. So I just have
>         to add a
>         >         plugin in
>         >         my script for use i_uri and o_uri instead of
>         sip_from/to
>         >         according to
>         >         some rules.
>         >
>         >         Regards
>         >
>         >         Le mardi 22 mai 2007 à 07:06 +0200, Greger V. Teigre
>         a écrit :
>         >         > Well, call forwarding is always a special case
>         because you
>         >         need to get
>         >         > the billing right according to how your billing
>         app needs
>         >         it. Look at
>         >         > the INVITE that comes for call forwarding and test
>         for it in
>         >         your
>         >         > script.
>         >
>         >         _______________________________________________
>         >         Serusers mailing list
>         >         Serusers@lists.iptel.org
>         >         http://lists.iptel.org/mailman/listinfo/serusers
>         >
>
>