Login | Register


Documentation -> Manuals -> Manual 1.7 -> Script Flags

Pages for other versions: devel 3.5 3.4 3.2 Older versions: 3.3 3.1 3.0 2.4 2.3 2.2 2.1 1.11 1.10 1.9 1.8 1.7 1.6 1.5 1.4

Script Flags v1.7

1.  Types of flags

  • message flags (or transaction flags) these flags are transaction persistent. They are visible in all routes and cases where the transaction context is visible
  • branch flags are saved also in transaction, but per branch; also they will be saved in usrloc (per contact). A new set of functions were added for manipulating these flags from script. So, there flags will be registration persistent and branch persistent.
  • script flags are no-message-related flags - they are only script persistent and you can strictly use them for scripting. Once you exit a top level route, they will be lost. These flags are useful and they offer an option to de-congest the message flags - many flags have no need to be saved as they just reflect some scripting status.

2.  Corresponding Functions

2.1  Message/transaction flags

setflag(flag_idx) resetflag(flag_idx) isflagset(flag_idx)

2.2  Branch flags

setbflag/setbranchflag(branch_idx,flag_idx) resetbflag/resetbranchflag(branch_idx,flag_idx) isbflagset/isbranchflagset(branch_idx,flag_idx)

or, the shorter format, working on the default (branch 0) flags:

setbflag(flag_idx) resetbflag(flag_idx) isbflagset(flag_idx)

2.3  Script flags

setsflag/setscriptflag(flag_idx) resetsflag/resetscriptflag(flag_idx) issflagset/isscriptflagset(flag_idx)

3.  Flags and Pseudo Variables

3.1  Message/transaction flags

$mf - decimal value $mF - hexa value

3.2  Branch flags

$bf - decimal value $bF - hexa value

3.3  Script flags

$sf - decimal value $sF - hexa valu

4.  Flags and routes

4.1  Message/transaction flags

These flags will show up in all routes where messages related to the initial request are processed. So, they will be visible and changeable in onbranch, failure and onreply routes; the flags will be visible in all branch routes; if you change a flag in a branch route, the next branch routes will inherit the change.

4.2  Branch flags

There flags will show up in all routes where messages related to initial branch request are processed. So, in branch route you will see different sets of flags (as they are different branches); in onreply route yo will see the branch flags corresponding to the branch the reply belongs to; in failure route, the branch flags corresponding to the branch the winning reply belongs to will be visible. In request route, you can have multiple branches (as a result of a lookup(), enum query, append_branch(), etc) - the default branch is 0 (corresponding to the RURI); In reply routes there will be only one branch , the 0 one. In branch route the default branch is the current process branch (having index 0); In failure route, initially there is only one branch (index 0), corresponding the failed branch.

4.3  Script flags

There flags are available only in script and are reset after each top level route execution (routes internally triggered by OpenSIPS). They will be persistent per main route, onreply_route, branch_route, failure_route. Note they will be inherit in routes called from other routes.

5.  Example

5.1  Nat flag handling

 # 3 - the nat flag

 route {
   if (nat detected)
      setbflag(3); # set branch flag 3 for the branch 0

   if (is_method("REGISTER")) {
      # the branch flags (including 3) will be saved into location
   } else {
      # lookup will load the branch flag from location
      if (!lookup("location")) {
         sl_send_reply("404","Not Found");

 branch_route[1] {
   xlog("-------branch=$T_branch_idx, branch flags=$bF\n");
   if (isbflagset(3)) {
      #current branch is marked as natted

if no parallel forking is done, you can get rid of the branch route and add instead of t_on_branch():

   if (isbflagset(3)) {
      #current branch is marked as natted

Add Comment 
Sign as Author 
Enter code 955

Page last modified on August 05, 2013, at 01:57 PM