# Functions

## `msg_apply_changes()`

Use this function to apply changes performed on SIP message content. Be careful when using this function; due to special handling of changes to the SIP message buffer so far, using this function might change the behaviour of your config. Do test your config properly!

The function returns true (1) on success. If it is failure before the new content is built, the function returns false (-1), the old content is still in place. If parsing of the new content is failing, the function stops executions of the config file (the internal structure is no longer valid for config processing, like it happens when a broken message is received from network).

This function can be used from REQUEST_ROUTE or core REPLY_ROUTE.

Note: It must be used before the transaction is created in request_route and not inside the onreply_route[name] executed by tm module. Also, do not use after resuming a suspended request or reply, at that moment the transaction is already created.

### `msg_apply_changes()` usage

    ...
    append_hf("My-Header: yes\r\n");
    if(msg_apply_changes())
    {
        # msg buffer has a new content
        if(is_present_hf("My-Header"))
        {
            # will get here always
        }
    }
    ...

## `msg_changed_route(rname)`

Execute a route block specified by rname, using a new SIP message structure build using the current SIP message with applied changes. The current SIP message does not get the changes applied.

This function can be used from ANY_ROUTE.

### `msg_changed_route()` usage

    ...
    append_hf("My-Header: yes\r\n");
    msg_changed_route("UPDATEDMSG");
    ...
    route[UPDATEDMSG] {
       xinfo("My-Header-Value: $hdr(My-Header)\n");
    }
    ...

## `msg_set_buffer(data)`

Set the content of the SIP message buffer, replacing the exiting data. The parameter can contain variables, its value must be a valid SIP request or reply, a matter of what the old message is.

This function can be used from REQUEST_ROUTE or core REPLY_ROUTE.

Note: It must be used before the transaction is created in request_route and not inside the onreply_route[name] executed by tm module. Also, do not use after resuming a suspended request or reply, at that moment the transaction is already created.

### `msg_set_buffer()` usage

    ...
    msg_set_buffer("INVITE sip:...");
    ...

## `change_reply_status(code, reason)`

Intercept a SIP reply (in an onreply_route) and change its status code and reason phrase prior to forwarding it.

Meaning of the parameters is as follows:

- code - Status code.

- reason - Reason phrase.

This function can be used from ONREPLY_ROUTE.

### `change_reply_status` usage

    ...
    reply_route {
        if (status == "603") {
            change_reply_status(404, "Not Found");
            exit;
        }
    }
    ...

## `change_reply_status_code(vcode)`

Change the status code for a SIP reply .

Meaning of the parameters is as follows:

- vcode - the new status code.

This function can be used from ONREPLY_ROUTE.

### `change_reply_status_code` usage

    ...
    reply_route {
        if (status == "604") {
            change_reply_status_code("404");
            exit;
        }
    }
    ...

## `remove_body()`

Use this function to remove the body of SIP requests or replies.

This function can be used from ANY_ROUTE.

### `remove_body()` usage

    ...
    remove_body();
    ...

## `keep_hf([regexp])`

Remove headers that don't match the regular expression regexp. Several header are ignored always (thus not removed): Via, From, To, Call-ID, CSeq, Content-Length, Content-Type, Max-Forwards, Contact, Route, Record-Route -- these can be removed one by one with remove_hf(). If regexp is missing, then only the headers listed above are kept, the rest are removed.

This function can be used from ANY_ROUTE.

### `keep_hf()` usage

    ...
    keep_hf("User-Agent");
    ...

## `fnmatch(value, expr [, flags])`

Match the value against the expr using shell-style pattern for file name matching (see man page for C function fnmatch()). It is known to be faster and use less-memory than regular expressions.

Parameter 'flags' is optional and can be 'i' to do case insensitive matching.

This function can be used from ANY_ROUTE.

### `fnmatch()` usage

    ...
    if(fnmatch("$rU", "123*"))
    {
        ...
    }
    ...

## `append_hf_value(hf, hvalue)`

Append new header value after an existing header, if no index acquired append at the end of list. Note that a header may consist of comma delimited list of values.

Meaning of the parameters is as follows:

- hf - Header field to be appended. Format: HFNAME [ [IDX] ]. If index is not specified new header is inserted at the end of message. The index 1 corresponds to the first header.

- hvalue - Value to be added, config var formatting supported.

### `append_hf_value` usage

    ...
    append_hf_value("foo", "gogo;stamp=$Ts")   # add new header
    append_hf_value("foo[1]", "gogo")  # add new value behind first value
    append_hf_value("foo[-1]", "$var(Bar)") # try add value to the last header, if not exists add new header
    ...

## `insert_hf_value(hf, hvalue)`

Insert new header value before an existing header, if no index acquired insert before first hf header. Note that a header may consist of comma delimited list of values. To insert a value behind the last value use `append_hf_value`.

Meaning of the parameters is as follows:

- hf - Header field to be appended. Format: HFNAME [ [IDX] ]. If index is not specified new header is inserted at the top of message. The index 1 corresponds to the first header.

- hvalue - Value to be added, config var formatting supported.

### `insert_hf_value` usage

    ...
    insert_hf_value("foo[2]", "gogo")
    insert_hf_value("foo", "$avp(foo)")   # add new header at the top of list
    insert_hf_value("foo[1]", "gogo") # try add to the first header
    ...

## `remove_hf_value(hf_par)`

Remove the header value from existing header, Note that a header may consist of comma delimited list of values.

Meaning of the parameters is as follows:

- hf_par - Header field/param to be removed. Format: HFNAME [ [IDX] ] [. PARAM ] If asterisk is specified as index then all values are affected. The index 1 corresponds to the first header.

### `remove_hf_value` usage

    ...
    remove_hf_value("foo")  # remove foo[1]
    remove_hf_value("foo[*]")  # remove all foo's headers
    remove_hf_value("foo[-1]") # last foo
    remove_hf_value("foo.bar")  # delete parameter
    remove_hf_value("foo[*].bar") # for each foo delete bar parameters
    ...

## `remove_hf_value2(hf_par)`

Remove specified header or parameter. It is expected header in Authorization format (comma delimiters are not treated as multi-value delimiters).

Meaning of the parameters is as follows:

- hf_par - Header/param to be removed. Format: HFNAME [ [IDX] ] [. PARAM ] If asterisk is specified as index then all values are affected. The index 1 corresponds to the first header.

### `remove_hf_value2` usage

    ...
    remove_hf_value2("foo")  # remove foo[1]
    remove_hf_value2("foo[*]")  # remove all foo's headers, the same as remove_hf_header("foo[*]");
    remove_hf_value2("foo[-1]") # last foo
    remove_hf_value2("foo.bar")  # delete parameter
    remove_hf_value2("foo[*].bar") # for each foo delete bar parameters
    ...

## `assign_hf_value(hf, hvalue)`

Assign value to specified header value / param.

Meaning of the parameters is as follows:

- hf_para - Header field value / param to be appended. Format: HFNAME [ [IDX] ] [. PARAM] If asterisk is specified as index then all values are affected. The index 1 corresponds to the first header.

- hvalue - Value to be assigned, config var formatting supported. If value is empty then no equal sign appears in param.

### `assign_hf_value` usage

    ...
    assign_hf_value("foo", "gogo")  # foo[1]
    assign_hf_value("foo[-1]", "gogo")  # foo[last_foo]

    assign_hf_value("foo.bar", "")
    assign_hf_value("foo[3].bar", "")
    assign_hf_value("foo[*]", "")  # remove all foo's, empty value remains
    assign_hf_value("foo[*].bar", "")  # set empty value (ex. lr)
    ...

## `assign_hf_value2(hf, hvalue)`

Assign value to specified header. It is expected header in Authorization format (comma delimiters are not treated as multi-value delimiters).

Meaning of the parameters is as follows:

- hf_para - Header field value / param to be appended. Format: HFNAME [ [IDX] ] [. PARAM] If asterisk is specified as index then all values are affected. The index 1 corresponds to the first header.

- hvalue - Value to be assigned, config var formatting supported. If value is empty then no equal sign appears in param.

### `assign_hf_value2` usage

    ...
    assign_hf_value2("Authorization.integrity-protected", "\"yes\"")
    assign_hf_value2("foo[-1]", "gogo")  # foo[last_foo]
    assign_hf_value2("foo[*].bar", "")  # set empty value (ex. lr)
    ...

## `include_hf_value(hf, hvalue)`

Add value in set if not exists, eg. "Supported: path,100rel".

Meaning of the parameters is as follows:

- hf - Header field name to be affected.

- hvalue - config var formatting supported.

### `include_hf_value` usage

    ...
    include_hf_value("Supported", "path");
    ...

## `exclude_hf_value(hf, hvalue)`

Remove value from set if exists, eg. "Supported: path,100rel".

Meaning of the parameters is as follows:

- hf - Header field name to be affected.

- hvalue - config formatting supported.

### `exclude_hf_value` usage

    ...
    exclude_hf_value("Supported", "100rel");
    ...

## `hf_value_exists(hf, hvalue)`

Check if value exists in set. Alternate select @hf_value_exists.HF.VALUE may be used. It returns one or zero.

Meaning of the parameters is as follows:

- hf - Header field name to be affected. Underscores are treated as dashes.

- hvalue - config var formatting supported.

### `hf_value_exists` usage

    ...
    if (hf_value_exists("Supported", "100rel")) {

    }

    if (@hf_value_exists.supported.path == "1") {

    }
    ...

## `hf_iterator_start(iname)`

Start an iterator for headers in the current SIP message. The parameter iname is used to identify the iterator. There can be up to 4 iterators at the same time, with different name.

The parameter can be a dynamic string with variables.

This function can be used from ANY_ROUTE.

### `hf_iterator_start` usage

    ...
    hf_iterator_start("i1");
    ...

## `hf_iterator_end(iname)`

Close the iterator identified by iname parameter. The iname value must be the same used for hf_iterator_start().

The parameter can be dynamic string with variables.

This function can be used from ANY_ROUTE.

### `hf_iterator_end` usage

    ...
    hf_iterator_end("i1");
    ...

## `hf_iterator_next(iname)`

Move the iterator to the next header. It must be called also after hf_iterator_start() to get the first header.

The return code is false when there is no other header in the list.

The item name and value are accessible via variables: $hfitname(iname) and $hfitbody(iname).

The parameter can be dynamic string with variables.

This function can be used from ANY_ROUTE.

### `hf_iterator_next` usage

    ...
        hf_iterator_start("i1");
        while(hf_iterator_next("i1")) {
            xlog("hdr[$hfitname(i1)] is: $hfitbody(i1)\n");
        }
        hf_iterator_end("i1");
    ...

## `hf_iterator_prev(iname)`

Move the iterator to the previous header. It must be called also after hf_iterator_start() and hf_iterator_next().

The parameter can be dynamic string with variables.

This function can be used from ANY_ROUTE.

### `hf_iterator_prev` usage

    ...
        hf_iterator_start("i1");
        hf_iterator_next("i1");
    ...
        hf_iterator_next("i1");
    ...
        hf_iterator_prev("i1");
    ...
        hf_iterator_end("i1");
    ...

## `hf_iterator_rm(iname)`

Remove the header at the current iterator position.

The parameter can be dynamic string with variables.

This function can be used from ANY_ROUTE.

### `hf_iterator_rm` usage

    ...
        hf_iterator_start("i1");
        while(hf_iterator_next("i1")) {
            if($hfitname(i1)=="My-Header") {
                hf_iterator_rm("i1");
            }
        }
        hf_iterator_end("i1");
    ...

## `hf_iterator_append(iname, htext)`

Add headers after the one at the current iterator possition.

The parameters can be dynamic strings with variables.

This function can be used from ANY_ROUTE.

### `hf_iterator_append` usage

    ...
        hf_iterator_start("i1");
        while(hf_iterator_next("i1")) {
            if($hfitname(i1)=="My-Header") {
                hf_iterator_append("i1", "My-New-Header: abc\r\n");
                break;
            }
        }
        hf_iterator_end("i1");
    ...

## `hf_iterator_insert(iname, htext)`

Add headers before the one at the current iterator possition.

The parameters can be dynamic strings with variables.

This function can be used from ANY_ROUTE.

### `hf_iterator_insert` usage

    ...
        hf_iterator_start("i1");
        while(hf_iterator_next("i1")) {
            if($hfitname(i1)=="My-Header") {
                hf_iterator_insert("i1", "My-New-Header: abc\r\n");
                break;
            }
        }
        hf_iterator_end("i1");
    ...

## `bl_iterator_start(iname)`

Start an iterator for lines in the body of the current SIP message. The parameter iname is used to identify the iterator. There can be up to 4 iterators at the same time, with different name.

The parameter can be a dynamic string with variables.

This function can be used from ANY_ROUTE.

### `bl_iterator_start` usage

    ...
    bl_iterator_start("b1");
    ...

## `bl_iterator_end(iname)`

Close the iterator identified by iname parameter. The iname value must be the same used for bl_iterator_start().

The parameter can be dynamic string with variables.

This function can be used from ANY_ROUTE.

### `bl_iterator_end` usage

    ...
    bl_iterator_end("b1");
    ...

## `bl_iterator_next(iname)`

Move the iterator to the next line in the body. It must be called also after bl_iterator_start() to get the first header.

The return code is false when there is no other header in the list.

The body line accessible via variable $blitval(iname) - it contains also the EOL chars.

The parameter can be dynamic string with variables.

This function can be used from ANY_ROUTE.

### `bl_iterator_next` usage

    ...
        bl_iterator_start("b1");
        while(bl_iterator_next("b1")) {
            xlog("body line: $blitval(b1)");
        }
        bl_iterator_end("b1");
    ...

## `bl_iterator_rm(iname)`

Remove the body line at the current iterator position.

The parameter can be dynamic string with variables.

This function can be used from ANY_ROUTE.

### `bl_iterator_rm` usage

    ...
        bl_iterator_start("b1");
        while(bl_iterator_next("b1")) {
            if($blitval(b1)=~"abc") {
                bl_iterator_rm("b1");
            }
        }
        bl_iterator_end("b1");
    ...

## `bl_iterator_append(iname, text)`

Add text after the line at the current iterator possition.

The parameters can be dynamic strings with variables.

This function can be used from ANY_ROUTE.

### `bl_iterator_append` usage

    ...
        bl_iterator_start("b1");
        while(bl_iterator_next("b1")) {
            if($blitval(b1)=~"^a=info:xyz") {
                bl_iterator_append("b1", "a=info:abc\r\n");
                break;
            }
        }
        bl_iterator_end("b1");
    ...

## `bl_iterator_insert(iname, text)`

Add text before the line at the current iterator possition.

The parameters can be dynamic strings with variables.

This function can be used from ANY_ROUTE.

### `bl_iterator_insert` usage

    ...
        bl_iterator_start("b1");
        while(bl_iterator_next("b1")) {
            if($blitval(b1)=~"^a=info:xyz") {
                bl_iterator_insert("b1", "a=info:abc\r\n");
                break;
            }
        }
        bl_iterator_end("b1");
    ...