About

About.News0041 History

Show minor edits - Show changes to markup

September 29, 2009, at 02:15 PM by anca_vamanu -
Added line 11:

Ex: $(avp(i:10)[1])=NULL.

September 03, 2009, at 01:39 PM by anca_vamanu -
Changed line 13 from:
  • syntax: avp_insert
to:
  • syntax: avp_insert.
Changed line 27 from:
  • the <reply> context can be used from failure route to access information from the reply
to:
  • the <reply> context can be used from failure route to access information from the reply.
September 03, 2009, at 01:38 PM by anca_vamanu -
September 03, 2009, at 01:37 PM by anca_vamanu -
Changed line 10 from:
  • overwrite the value of a pseudovariable at a certain index; syntax: pvar[_index_]=_value_.
to:
  • overwrite the value of a pseudovariable at a certain index; syntax: pvar[_index_]=_value_.
September 03, 2009, at 01:36 PM by anca_vamanu -
Changed line 9 from:
  • delete the pseudovariable at a certain index; syntax: pvar[_index_]=NULL%.
to:
  • delete the pseudovariable at a certain index; syntax: pvar[_index_]=NULL.
September 03, 2009, at 01:35 PM by anca_vamanu -
Changed line 9 from:
  • delete the pseudovariable at a certain index; syntax: pvar[_index_]=NULL.
to:
  • delete the pseudovariable at a certain index; syntax: pvar[_index_]=NULL%.
September 03, 2009, at 01:35 PM by anca_vamanu -
Added lines 1-5:

About -> News -> Pseudovariable implementation extended


Pseudovariable implementation extended

September 03, 2009, at 01:33 PM by anca_vamanu -
Changed lines 20-21 from:
  • example: - referencing $(<request>ru) from a reply route will get the Request-URI from the request
             - the <reply> context can be used from failure route to access information from the reply
to:
  • example:
    • referencing $(<request>ru) from a reply route will get the Request-URI from the request
    • the <reply> context can be used from failure route to access information from the reply
September 03, 2009, at 01:33 PM by anca_vamanu -
Changed lines 4-6 from:
  • delete the pseudovariable at a certain index; syntax: pvar[_index_]=NULL.
  • overwrite the value of a pseudovariable at a certain index; syntax: pvar[_index_]=_value_.
to:
  • delete the pseudovariable at a certain index; syntax: pvar[_index_]=NULL.
  • overwrite the value of a pseudovariable at a certain index; syntax: pvar[_index_]=_value_.
Changed line 8 from:
  • syntax: avp_insert
to:
  • syntax: avp_insert
Changed lines 11-13 from:
  • count the number of values; syntax: set_count(_pvar_name_).
  • select an element from the set based on fitness. The selection algorithm is the genetic algorithm roulette-wheel selection. One usage example is selecting a route based on costs. syntax: set_select_weight(_pvar_name_); it returns the index of the selected value.
to:
  • count the number of values; syntax: set_count(_pvar_name_).
  • select an element from the set based on fitness. The selection algorithm is the genetic algorithm roulette-wheel selection. One usage example is selecting a route based on costs. syntax: set_select_weight(_pvar_name_); it returns the index of the selected value.
Changed lines 15-17 from:
  • syntax: {nameaddr.param,param_name}
  • example: "test" <sip:test@opensips.org>;tag=dat43h' {nameaddr.param,tag} = dat43h
to:
  • syntax: {nameaddr.param,param_name}
  • example: "test" <sip:test@opensips.org>;tag=dat43h' {nameaddr.param,tag} = dat43h
Changed lines 20-21 from:
  • example: - referencing $(<request>ru) from a reply route will get the Request-URI from the request
             - the <reply> context can be used from failure route to access information from the reply
to:
  • example: - referencing $(<request>ru) from a reply route will get the Request-URI from the request
             - the <reply> context can be used from failure route to access information from the reply
September 03, 2009, at 01:31 PM by anca_vamanu -
Changed lines 4-6 from:
  • delete the pseudovariable at a certain index; syntax: pvar[_index_]=NULL.
  • overwrite the value of a pseudovariable at a certain index; syntax: pvar[_index_]=_value_.
to:
  • delete the pseudovariable at a certain index; syntax: pvar[_index_]=NULL.
  • overwrite the value of a pseudovariable at a certain index; syntax: pvar[_index_]=_value_.
Changed line 8 from:
  • syntax: avp_insert
to:
  • syntax: avp_insert
Changed lines 11-13 from:
  • count the number of values; syntax: set_count(_pvar_name_).
  • select an element from the set based on fitness. The selection algorithm is the genetic algorithm roulette-wheel selection. One usage example is selecting a route based on costs. syntax: set_select_weight(_pvar_name_); it returns the index of the selected value.
to:
  • count the number of values; syntax: set_count(_pvar_name_).
  • select an element from the set based on fitness. The selection algorithm is the genetic algorithm roulette-wheel selection. One usage example is selecting a route based on costs. syntax: set_select_weight(_pvar_name_); it returns the index of the selected value.
Changed lines 15-17 from:
  • syntax: {nameaddr.param,param_name}
  • example: "test" <sip:test@opensips.org>;tag=dat43h' {nameaddr.param,tag} = dat43h
to:
  • syntax: {nameaddr.param,param_name}
  • example: "test" <sip:test@opensips.org>;tag=dat43h' {nameaddr.param,tag} = dat43h
Changed lines 20-21 from:
  • example: - referencing $(<request>ru) from a reply route will get the Request-URI from the request
             - the <reply> context can be used from failure route to access information from the reply
to:
  • example: - referencing $(<request>ru) from a reply route will get the Request-URI from the request
             - the <reply> context can be used from failure route to access information from the reply
September 03, 2009, at 01:29 PM by anca_vamanu -
September 03, 2009, at 01:28 PM by anca_vamanu -
Changed lines 4-6 from:
  • delete the pseudovariable at a certain index; syntax: pvar[_index_]=NULL.
  • overwrite the value of a pseudovariable at a certain index; syntax: pvar[_index_]=_value_.
to:
  • delete the pseudovariable at a certain index; syntax: pvar[_index_]=NULL.
  • overwrite the value of a pseudovariable at a certain index; syntax: pvar[_index_]=_value_.
Changed line 8 from:
  • syntax: avp_insert
to:
  • syntax: avp_insert
Changed lines 11-13 from:
  • count the number of values; syntax: set_count(_pvar_name_).
  • select an element from the set based on fitness. The selection algorithm is the genetic algorithm roulette-wheel selection. One usage example is selecting a route based on costs. syntax: set_select_weight(_pvar_name_); it returns the index of the selected value.
to:
  • count the number of values; syntax: set_count(_pvar_name_).
  • select an element from the set based on fitness. The selection algorithm is the genetic algorithm roulette-wheel selection. One usage example is selecting a route based on costs. syntax: set_select_weight(_pvar_name_); it returns the index of the selected value.
Changed lines 15-17 from:
  • syntax: {nameaddr.param,param_name}
  • example: "test" <sip:test@opensips.org>;tag=dat43h' {nameaddr.param,tag} = dat43h
to:
  • syntax: {nameaddr.param,param_name}
  • example: "test" <sip:test@opensips.org>;tag=dat43h' {nameaddr.param,tag} = dat43h
Changed lines 20-21 from:
  • example: - referencing $(<request>ru) from a reply route will get the Request-URI from the request
             - the <reply> context can be used from failure route to access information from the reply
to:
  • example: - referencing $(<request>ru) from a reply route will get the Request-URI from the request
             - the <reply> context can be used from failure route to access information from the reply
September 03, 2009, at 01:16 PM by anca_vamanu -
Changed line 21 from:
           - the <reply> context can be used from failure route to access information from the reply
to:
             - the <reply> context can be used from failure route to access information from the reply 
September 03, 2009, at 01:16 PM by anca_vamanu -
September 03, 2009, at 01:15 PM by anca_vamanu -
Changed lines 20-21 from:
  • example: ** referencing $(<request>ru) from a reply route will get the Request-URI from the request
           ** the <reply> context can be used from failure route to access information from the reply
to:
  • example: - referencing $(<request>ru) from a reply route will get the Request-URI from the request
           - the <reply> context can be used from failure route to access information from the reply
September 03, 2009, at 01:14 PM by anca_vamanu -
Changed lines 12-13 from:
  • select an element from the set based on fitness. The selection algorithm is the genetic algorithm roulette-wheel selection. One usage example is selecting a route based on costs.

syntax: set_select_weight(_pvar_name_); it returns the index of the selected value.

to:
  • select an element from the set based on fitness. The selection algorithm is the genetic algorithm roulette-wheel selection. One usage example is selecting a route based on costs. syntax: set_select_weight(_pvar_name_); it returns the index of the selected value.
September 03, 2009, at 01:11 PM by anca_vamanu -
Changed lines 4-6 from:
  • delete the pseudovariable at a certain index; syntax: pvar[_index_]=NULL.
  • overwrite the value of a pseudovariable at a certain index; syntax: pvar[_index_]=_value_.
to:
  • delete the pseudovariable at a certain index; syntax: pvar[_index_]=NULL.
  • overwrite the value of a pseudovariable at a certain index; syntax: pvar[_index_]=_value_.
Changed line 8 from:
  • syntax: avp_insert
to:
  • syntax: avp_insert
Changed line 11 from:
  • count the number of values; syntax: set_count(_pvar_name_).
to:
  • count the number of values; syntax: set_count(_pvar_name_).
Changed lines 13-14 from:

syntax: set_select_weight(_pvar_name_); it returns the index of the selected value.

to:

syntax: set_select_weight(_pvar_name_); it returns the index of the selected value.

Changed lines 16-18 from:
  • syntax: {nameaddr.param,param_name}
  • example: "test" <sip:test@opensips.org>;tag=dat43h' {nameaddr.param,tag} = dat43h
to:
  • syntax: {nameaddr.param,param_name}
  • example: "test" <sip:test@opensips.org>;tag=dat43h' {nameaddr.param,tag} = dat43h
Changed lines 21-22 from:
  • example: ** referencing $(<request>ru) from a reply route will get the Request-URI from the request
           ** the <reply> context can be used from failure route to access information from the reply
to:
  • example: ** referencing $(<request>ru) from a reply route will get the Request-URI from the request
           ** the <reply> context can be used from failure route to access information from the reply
September 03, 2009, at 01:05 PM by anca_vamanu -
Changed line 7 from:

2. Added one new function for avp: inserts a value to an avp set at a certain position

to:

2. Added one new function for avp: inserts a value to an avp set at a certain position

September 03, 2009, at 01:04 PM by anca_vamanu -
Changed line 3 from:
  1. Added 2 new operations on pseudovariables values from the script:
to:

1. Added 2 new operations on pseudovariables values from the script:

Changed line 7 from:
  1. Added one new function for avp: inserts a value to an avp set at a certain position\\
to:

2. Added one new function for avp: inserts a value to an avp set at a certain position

Changed lines 10-19 from:
  1. Added operations for set values of pseudovariables:
    * count the number of values; syntax: set_count(_pvar_name_).
    * select an element from the set based on fitness. The selection algorithm is the genetic algorithm roulette-wheel selection. One usage example is selecting a route based on costs.
    syntax: set_select_weight(_pvar_name_); it returns the index of the selected value.
  2. Added a new transformation: extract a parameter from a To like header
    * syntax: {nameaddr.param,param_name}
    * example: "test" <sip:test@opensips.org>;tag=dat43h' {nameaddr.param,tag} = dat43h
  3. Added context meaning to pseudovariables - a new token added in front of the pv type name that specifies the context where the pv should be taken from
to:

3. Added operations for set values of pseudovariables:

  • count the number of values; syntax: set_count(_pvar_name_).
  • select an element from the set based on fitness. The selection algorithm is the genetic algorithm roulette-wheel selection. One usage example is selecting a route based on costs.

syntax: set_select_weight(_pvar_name_); it returns the index of the selected value.

4. Added a new transformation: extract a parameter from a To like header

  • syntax: {nameaddr.param,param_name}
  • example: "test" <sip:test@opensips.org>;tag=dat43h' {nameaddr.param,tag} = dat43h

5. Added context meaning to pseudovariables - a new token added in front of the pv type name that specifies the context where the pv should be taken from

September 03, 2009, at 01:01 PM by anca_vamanu -
Changed lines 3-4 from:
  1. Added 2 new operations on pseudovariables values from the script:
    *delete the pseudovariable at a certain index; syntax: pvar[_index_]=NULL. \\
to:
  1. Added 2 new operations on pseudovariables values from the script:
  • delete the pseudovariable at a certain index; syntax: pvar[_index_]=NULL.
Deleted line 17:
September 03, 2009, at 12:55 PM by anca_vamanu -
Changed lines 3-7 from:
  1. Added 2 new operations on pseudovariables values from the script:
  • delete the pseudovariable at a certain index; syntax: pvar[_index_]=NULL.
  • overwrite the value of a pseudovariable at a certain index; syntax: pvar[_index_]=_value_.
  1. Added one new function for avp: inserts a value to an avp set at a certain position
to:
  1. Added 2 new operations on pseudovariables values from the script:
    *delete the pseudovariable at a certain index; syntax: pvar[_index_]=NULL.
    *overwrite the value of a pseudovariable at a certain index; syntax: pvar[_index_]=_value_.
  2. Added one new function for avp: inserts a value to an avp set at a certain position\\
Changed lines 10-18 from:
  1. Added operations for set values of pseudovariables:
  • count the number of values; syntax: set_count(_pvar_name_).
  • select an element from the set based on fitness. The selection algorithm is the genetic algorithm roulette-wheel selection. One usage example is selecting a route based on costs.

syntax: set_select_weight(_pvar_name_); it returns the index of the selected value.

  1. Added a new transformation: extract a parameter from a To like header
  • syntax: {nameaddr.param,param_name}
  • example: "test" <sip:test@opensips.org>;tag=dat43h' {nameaddr.param,tag} = dat43h
to:
  1. Added operations for set values of pseudovariables:
    * count the number of values; syntax: set_count(_pvar_name_).
    * select an element from the set based on fitness. The selection algorithm is the genetic algorithm roulette-wheel selection. One usage example is selecting a route based on costs.
    syntax: set_select_weight(_pvar_name_); it returns the index of the selected value.
  2. Added a new transformation: extract a parameter from a To like header
    * syntax: {nameaddr.param,param_name}
    * example: "test" <sip:test@opensips.org>;tag=dat43h' {nameaddr.param,tag} = dat43h
September 03, 2009, at 12:54 PM by anca_vamanu -
Added lines 1-23:

The pseudovariable implementation has been extended with new operations to give more power to the script writer:

  1. Added 2 new operations on pseudovariables values from the script:
  • delete the pseudovariable at a certain index; syntax: pvar[_index_]=NULL.
  • overwrite the value of a pseudovariable at a certain index; syntax: pvar[_index_]=_value_.
  1. Added one new function for avp: inserts a value to an avp set at a certain position
  • syntax: avp_insert
  1. Added operations for set values of pseudovariables:
  • count the number of values; syntax: set_count(_pvar_name_).
  • select an element from the set based on fitness. The selection algorithm is the genetic algorithm roulette-wheel selection. One usage example is selecting a route based on costs.

syntax: set_select_weight(_pvar_name_); it returns the index of the selected value.

  1. Added a new transformation: extract a parameter from a To like header
  • syntax: {nameaddr.param,param_name}
  • example: "test" <sip:test@opensips.org>;tag=dat43h' {nameaddr.param,tag} = dat43h
  1. Added context meaning to pseudovariables - a new token added in front of the pv type name that specifies the context where the pv should be taken from

The implementation is made general - with a mechanism of registering pv context functions, allowing for extensions and addition of custom contexts. For now there are 2 pv contexts: reply and request, registered by the tm module.

  • example: ** referencing $(<request>ru) from a reply route will get the Request-URI from the request
           ** the <reply> context can be used from failure route to access information from the reply

Page last modified on September 29, 2009, at 02:15 PM