Copyright © 2003 FhG FOKUS
search(re)
search_append(re, txt)
replace(re, txt)
append_to_reply(txt)
append_hf(hf)
append_urihf(prefix, suffix)
is_present_hf(hf_name)
search
usagesearch_append
usagereplace
usageappend_to_reply
usageappend_hf
usageappend_urihf
usageis_present_hf
usageThis is mostly an example module. It implements text based operation (search, replace, append a.s.o).
search ignores folded lines. For example, search("(From|f):.*@foo.bar") doesn't match the following From header field:
From: medabeda <sip:medameda@foo.bar>;tag=1234
The following modules must be loaded before this module:
No dependencies on other SER modules.
The following libraries or applications must be installed before running SER with this module loaded:
None.
search(re)
Searches for the re in the message.
Meaning of the parameters is as follows:
re - Regular expression.
search_append(re, txt)
Searches for the first match of re and appends txt after it.
Meaning of the parameters is as follows:
re - Regular expression.
txt - String to be appended.
replace(re, txt)
Replaces the first occurence of re with txt.
Meaning of the parameters is as follows:
re - Regular expression.
txt - String.
append_to_reply(txt)
Append txt to the reply.
Meaning of the parameters is as follows:
txt - String.
append_hf(hf)
Appends txt after the last header field.
Meaning of the parameters is as follows:
hf - Header field to be appended.
append_urihf(prefix, suffix)
Append header field name with original Request-URI in middle.
Meaning of the parameters is as follows:
prefix - string (usually at least header field name).
suffix - string (usually at least line terminator).
is_present_hf(hf_name)
Return true if a header field is present in message.
![]() | Takes header field names "as is" and doesn't distinguish compact names. |
Meaning of the parameters is as follows:
hf_name - Header field name.
The module does not provide any sort of API to use in other SER modules.
Take a look at http://iptel.org/ser.
First at all check if your question was already answered on one of our mailing lists:
E-mails regarding any stable version should be sent to <serusers@iptel.org>
and e-mail
regarding development versions or CVS snapshots should be send to <serdev@iptel.org>
.
If you want to keep the mail private, send it to <serhelp@iptel.org>
.
Please follow the guidelines provided at: http://iptel.org/ser/bugs