Re: [Users] Server call forwarding

Sam: You can try something like the following. The flag callfwdall indicates whether call forwarding is on or off and is set by the user via a provisioning interface. fwdaaddr is another DB flag that contains the user portion of the "new" r-uri after the re-write is performed. $ocn is original called number and is saved so that it may be used elsewhere, such as in the voicemail handling routing. route[8] just types the call so I know which type of call is being processed. I also use a route block for checking class of service (call permissions) when needed. I use flags to indicate what feature has been enabled and finally route[2] just relays this particular type of call. I hope this helps. -Steve # call forward always if (avp_db_load("$ruri/username", "s:callfwdall")) { if (avp_check("s:callfwdall","eq/y/i")) { xlog("L_INFO", "\n[SER]: [%Tf] [%ci] User <%ru> has enabled Call Forward Always\n"); setflag(3); avp_write("$ruri", "$ocn"); if (avp_db_load("$ruri/username", "s:fwdaaddr")) { avp_pushto("$ruri/username", "s:fwdaaddr"); rewritehostport("voip.upenn.edu"); xlog("L_INFO", "\n[SER]: [%Tf] [%ci] Calls for user <%ru> FORWARDING to <%ru>\n"); route(8); if (avp_check("$calltype","eq/oncampus/i")) { if (avp_db_load("$to/username", "s:allow_oncampus")) { if (avp_check("s:allow_oncampus","eq/y/i")) { setflag(13); } else { resetflag(13); return; }; avp_delete("s:allow_oncampus"); }; route(2); ........