loose_route()
strict_route()
-- deprecatedrecord_route()
record_route_preset(string)
loose_route
usagestrict_route
usagerecord_route
usagerecord_route_preset
usageThe module contains record routing logic
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.
If set to 1 then ;lr=on instead of just ;lr will be used. This is to overcome problems with broken UAs which strip ;lr parameter when generating Route header fields from Record-Route (;lr=on seems to help).
Default value is 0 (no).
if turned on, request's from-tag is appended to record-route; that's useful for understanding whether subsequent requests (such as BYE) come from caller (route's from-tag==BYE's from-tag) or callee (route's from-tag==BYE's to-tag)
Default value is 1 (yes).
There are some situations when the server needs to insert two Record-Route header fields instead of one. For example when using two disconnected networks or doing cross-protocol forwarding from UDP->TCP. This parameter enables inserting of 2 Record-Routes. The server will later remove both of them.
Default value is 1 (yes).
loose_route()
The function performs loose routing as defined in RFC3261. See the RFC3261 for more details.
strict_route()
-- deprecatedIf there are any Route HFs in the message, the function takes the first one, rewrites Request-URI with it's value and removes the first URI from Route HFs.
record_route()
The function adds a new Record-Route header field. The header field will be inserted in the message before any other Record-Route header fields.
record_route_preset(string)
This function will put the string into Record-Route, don't use unless you know what you are doing.
Meaning of the parameters is as follows:
string - String to be inserted into the header field.
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