gflagsStandard The module implements global flags. The difference between the global flags and flags that can be used in the configuration file or AVPs is that they the scope of the global flags is not limited to the SIP message or transactioni being processed. Global flags are always available, their contents is not forgotten when a SIP transaction gets destroyed in SERi. Jiri Kuthan Copyright © 2004 FhG FOKUS
The module implements global flags. The difference between the global flags and flags that can be used in the configuration file or AVPs is that they the scope of the global flags is not limited to the SIP message or transactioni being processed. Global flags are always available, their contents is not forgotten when a SIP transaction gets destroyed in SERi. Global flags can be accessed from the configuration script, for example: if (is_gflag("1")) {
t_relay_to_udp("10.0.0.1", "5060");
} else {
t_relay_to_udp("10.0.0.2", "5060");
};
The value of the global flags can be manipulated by external tools such as the web interface of SER or cmd line administration tools. One particular application of global flags could be runtime configuration changes without the need to restart SER. Set the flag identified by flag_num to 1. The range of flag_num is 0 to 31. Set the flag identified by flag_num to 0. The range of flag_num is 0 to 31. The state of the global flags can be read and modified over the FIFO interface of SER. This module implements the following FIFO interface functions:
The state of the global flags can be read and modified over the XMLRPC interface. This module implements the following XMLRPC interface commands:
|
Navigation |
||||