Copyright © 2003 FhG FOKUS
| Revision History | |
|---|---|
| Revision $Revision: 5901 $ | $Date$ |
Table of Contents
work_modeservice_typesp1_uri, sp2_uri, ..., sp16_urisp1_weight, sp2_weight, ..., sp16_weightdevice_ipuse_security_featurestoken_formatprivate_key, local_certificate, ca_certificatesenable_crypto_hardware_supportssl_lifetimepersistenceretry_delayretry_limittimeoutsupport_nonsip_protocolmax_destinationsreport_networkidvalidate_call_iduse_number_portabilityappend_userphonenetworkid_locationnetworkid_parameterparameterstring_locationparameterstring_valuesource_device_avpsource_networkid_avpcustom_info_avpcnam_avpsource_media_avp, destination_media_avprequest_date_avpsdp_fingerprint_avpidentity_signature_avp, identity_algorithm_avp, identity_information_avp, identity_type_avp, identity_canon_avpList of Examples
The OSP module enables OpenSIPS to support secure, multi-lateral peering using the OSP standard defined by ETSI (TS 101 321 V4.1.1). This module will enable your OpenSIPS to:
Send a peering authorization request to a peering server.
Validate a digitally signed peering authorization token received in a SIP INVITE message.
Report usage information to a peering server.
The OSP module depends on the following modules which must be loaded before the OSP module.
auth -- Authentication Framework module
avpops -- AVP operation module
maxfwd -- Max-Forward processor module
mi_fifo -- FIFO support for Management Interface
options -- OPTIONS server replier module
registrar -- SIP Registrar implementation module
rr -- Record-Route and Route module
signaling -- SIP signaling module
sipmsgops -- SIP operations module
sl -- Stateless replier module
tm -- Transaction (stateful) module
uac -- UAC functionalies (FROM mangling and UAC auth)
uac_auth -- UAC Authentication functionality
usrloc -- User location implementation module
OSP Toolkit -- The OSP Toolkit, available from http://sourceforge.net/projects/osp-toolkit, must be built before building OpenSIPS with the OSP module. For instructions on building OpenSIPS with the OSP Toolkit, see http://www.http://transnexus.com/wp-content/uploads/OSP-Routing-and-CDR-Collection-Server-with-OpenSIPS-1.7.2.pdf. For OpenSIPS 1.11.5, OSP Toolkit 4.5.0 or later versions should be used.
The work_mode (integer) parameter instructs the OSP module what mode it should work in. If this value is set to 0, the OSP module wokes in direct mode. If this value is set to 1, the OSP module works in indirect mode. The default value is 0.
The service_type (integer) parameter instructs the OSP module what services it should provide. If this value is set to 0, the OSP module provides normal voice service. If this value is set to 1, the OSP module provides ported number query service. If this value is set to 2, the OSP module provides CNAM query service. The default value is 0.
Example 1.2. Instructing the module to provide normal voice service
modparam("osp","service_type",0)
These sp_uri (string) parameters define peering servers to be used for requesting peering authorization and routing information. At least one peering server must be configured. Others are required only if there are more than one peering servers. Each peering server address takes the form of a standard URL, and consists of up to four components:
An optional indication of the protocol to be used for communicating with the peering server. Both HTTP and HTTP secured with SSL/TLS are supported and are indicated by "http://" and "https://" respectively. If the protocol is not explicitly indicated, the OpenSIPS defaults to HTTP secured with SSL.
The Internet domain name for the peering server. An IP address may also be used, provided it is enclosed in square brackets such as [172.16.1.1].
An optional TCP port number for communicating with the peering server. If the port number is omitted, the OpenSIPS defaults to port 5045 (for HTTP) or port 1443 (for HTTP secured with SSL).
The uniform resource identifier for requests to the peering server. This component is not optional and must be included.
Example 1.3. Setting the OSP servers
modparam("osp","sp1_uri","http://osptestserver.transnexus.com:5045/osp")
modparam("osp","sp2_uri","https://[1.2.3.4]:1443/osp")
These sp_weight (integer) parameters are used for load balancing peering requests to peering servers. These parameters are most effective when configured as factors of 1000. For example, if sp1_uri should manage twice the traffic load of sp2_uri, then set sp1_weight to 2000 and sp2_weight to 1000. Shared load balancing between peering servers is recommended. However, peering servers can be configured as primary and backup by assigning a sp_weight of 0 to the primary server and a non-zero sp_weight to the back-up server. The default values for sp1_weight and sp2_weight are 1000.
The device_ip (string) is a recommended parameter that explicitly defines the IP address of OpenSIPS in a peering request message (as SourceAlternate type=transport). The dotted-decimal IP address must be in brackets as shown in the example below.
The use_security_features (integer) parameter instructs the OSP module how to use the OSP security features. If this value is set to 1, the OSP module uses the OSP security features. If this value is set to 0, the OSP module will not use the OSP security features. The default value is 0.
Example 1.6. Instructing the module not to use OSP security features
modparam("osp","use_security_features",0)
When OpenSIPS receives a SIP INVITE with a peering token, the OSP module will validate the token to determine whether or not the call has been authorized by a peering server. Peering tokens may, or may not, be digitally signed. The token_format (integer) parameter defines if OpenSIPS will validate signed or unsigned tokens or both. The values for token format are defined below. The default value is 2.
If use_security_features parameter is set to 0, signed tokens cannot be validated.
0 - Validate only signed tokens. Calls with valid signed tokens are allowed.
1 - Validate only unsigned tokens. Calls with valid unsigned tokens are allowed.
2 - Validate both signed and unsigned tokens are allowed. Calls with valid tokens are allowed.
These parameters identify files are used for validating peering authorization tokens and establishing a secure channel between OpenSIPS and a peering server using SSL. The files are generated using the 'Enroll' utility from the OSP Toolkit. By default, the proxy will look for pkey.pem, localcert.pem, and cacart_0.pem in the default configuration directory. The default config directory is set at compile time using CFG_DIR and defaults to /usr/local/etc/opensips/. The files may be copied to the expected file location or the parameters below may be changed.
If use_security_features parameter is set to 0, these parameters will be ignored.
Example 1.8. Set authorization files
If the default CFG_DIR value was used at compile time, the files will be loaded from:
modparam("osp","private_key","/usr/local/etc/opensips/pkey.pem")
modparam("osp","local_certificate","/usr/local/etc/opensips/localcert.pem")
modparam("osp","ca_certificates","/usr/local/etc/opensips/cacert.pem")
The enable_crypto_hardware_support (integer) parameter is used to set the cryptographic hardware acceleration engine in the openssl library. The default value is 0 (no crypto hardware is present). If crypto hardware is used, the value should be set to 1.
The ssl_lifetime (integer) parameter defines the lifetime, in seconds, of a single SSL session key. Once this time limit is exceeded, the OSP module will negotiate a new session key. Communication exchanges in progress will not be interrupted when this time limit expires. This is an optional field with default value is 200 seconds.
The persistence (integer) parameter defines the time, in seconds, that an HTTP connection should be maintained after the completion of a communication exchange. The OSP module will maintain the connection for this time period in anticipation of future communication exchanges to the same peering server.
The retry_delay (integer) parameter defines the time, in seconds, between retrying connection attempts to an OSP peering server. After exhausting all peering servers the OSP module will delay for this amount of time before resuming connection attempts. This is an optional field with default value is 1 second.
The retry_limit (integer) parameter defines the maximum number of retries for connection attempts to a peering server. If no connection is established after this many retry attempts to all peering servers, the OSP module will cease connection attempts and return appropriate error codes. This number does not count the initial connection attempt, so that a retry_limit of 1 will result in a total of two connection attempts to every peering server. The default value is 2.
The timeout (integer) parameter defines the maximum time in milliseconds, to wait for a response from a peering server. If no response is received within this time, the current connection is aborted and the OSP module attempts to contact the next peering server. The default value is 10 seconds.
The support_nonsip_protocol (integer) parameter is used to tell the OSP module if non-SIP signaling protocol destination devices are supported. The default value is 0.
Example 1.15. Setting support non-SIP destination devices
modparam("osp","support_nonsip_protocol",0)
The max_destinations (integer) parameter defines the maximum number of destinations that OpenSIPS requests the peering server to return in a peering response. The OSP module supports up to 12 destinations. The default value is 12.
The report_networkid (integer) parameter is used to tell the OSP module if to report network ID in completed call CDRs. If it is set to 0, ths OSP module does not report any network ID. If it is set to 1, the OSP module reports source network ID. If it is set to 2, the OSP module reports destination network ID. If it is set to 3, the OSP module report both source and destination network IDs. The default value is 3.
The validate_call_id (integer) parameter instructs the OSP module to validate call id in the peering token. If this value is set to 1, the OSP module validates that the call id in the SIP INVITE message matches the call id in the peering token. If they do not match the INVITE is rejected. If this value is set to 0, the OSP module will not validate the call id in the peering token. The default value is 1.
The use_number_portability (integer) parameter instructs the OSP module how to use the number portability parameters in the Request URI of the SIP INVITE message. If this value is set to 1, the OSP module uses the number portability parameters in the Request URI when these parameters exist. If this value is set to 0, the OSP module will not use the number portability parameters. The default value is 1.
Example 1.19. Instructing the module to use number portability parameters in Request URI
modparam("osp","use_number_portablity",1)
The append_userphone (integer) parameter instructs the OSP module if to append "user=phone" parameter in URI. If this value is set to 0, the OSP module does not append "user=phone" parameter. If this value is set to 1, the OSP module will append "user=phone" parameter. The default value is 0
The networkid_location (integer) parameter instructs the OSP module where the destination network ID should be appended. The default value is 2
0 - network ID is not appended.
1 - network ID is appended as userinfo parameter.
2 - network ID is appended as URI parameter.
The networkid_parameter (string) parameter instructs the OSP module to use which parameter name in outbound destination URIs to append destination network ID. The default value is "networkid"
The parameterstring_location (integer) parameter instructs the OSP module where the parameter string should be appended. The default value is 0
0 - parameter string is not appended.
1 - parameter string is appended as userinfo parameter.
2 - parameter string is appended as URI parameter.
The parameterstring_value (string) parameter instructs the OSP module to append the parameter string in outbound URIs. The default value is ""
The source_device_avp (string) parameter instructs the OSP module to use the defined AVP to pass the source device IP value in the indirect work mode. The default value is "$avp(_osp_source_device_)". Then the source device IP can be set by "$avp(_osp_source_device_) = pseudo-variables". All pseudo variables are described in http://www.opensips.org/Resources/DocsCoreVar.
The source_networkid_avp (string) parameter instructs the OSP module to use the defined AVP to pass the source network ID value. The default value is "$avp(_osp_source_networkid_)". Then the source network ID can be set by "$avp(_osp_source_networkid_) = pseudo-variables". All pseudo variables are described in http://www.opensips.org/Resources/DocsCoreVar.
The custom_info_avp (string) parameter instructs the OSP module to use the defined AVP to pass the custom information values. The default value is "$avp(_osp_custom_info_)". Then the custom information can be set by "$avp(_osp_custom_info_) = pseudo-variables". All pseudo variables are described in http://www.opensips.org/Resources/DocsCoreVar.
The cnam_avp (string) parameter instructs the OSP module to use the defined AVP to pass the CNAM values. The default value is "$avp(_osp_cnam_)". Then the CNAM can be used by "$avp(_osp_cnam_)". All pseudo variables are described in http://www.opensips.org/Resources/DocsCoreVar.
These parameters are used to tell the OSP module which AVPs are used to store media addresses. The default values are "$avp(_osp_source_media_address_)" and "$avp(_osp_destination_media_address_)". All pseudo variables are described in http://www.opensips.org/Resources/DocsCoreVar.
Example 1.29. Setting the media address AVPs
modparam("osp", "source_media_avp", "$avp(srcmedia)")
modparam("osp", "destination_media_avp", "$avp(destmedia)")
The request_date_avp (string) parameter instructs the OSP module to use the defined AVP to pass the SIP request Date header values. The default value is "$avp(_osp_request_date_)". Then the request date can be used by "$avp(_osp_request_date_)". All pseudo variables are described in http://www.opensips.org/Resources/DocsCoreVar.
The sdp_fingerprint_avp (string) parameter instructs the OSP module to use the defined AVP to pass the SDP fing print attribute values. The default value is "$avp(_osp_sdp_fingerprint_)". Then the SDP finger print attributes can be used by "$avp(_osp_sdp_fingerprint_)". All pseudo variables are described in http://www.opensips.org/Resources/DocsCoreVar.
These parameters instruct the OSP module to use the defined AVPs to pass the Identity related values. The default values are "$avp(_osp_identity_signature_)", "$avp(_osp_identity_algorithm_)", "$avp(_osp_identity_information_)", "$avp(_osp_identity_type_)", "$avp(_osp_identity_canon_)". Then the indentity related values can be used by these AVPs. All pseudo variables are described in http://www.opensips.org/Resources/DocsCoreVar.
Example 1.32. Setting the Identity related AVPs
modparam("osp","identity_signature_avp","$avp(idsign)")
modparam("osp","identity_algorithm_avp","$avp(idalg)")
modparam("osp","identity_information_avp","$avp(idinfo)")
modparam("osp","identity_type_avp","$avp(idtype)")
modparam("osp","identity_canon_avp","$avp(idcanon)")
This function checks for the existence of the OSP-Auth-Token header field.
This function can be used from REQUEST_ROUTE.
Example 1.33. checkospheader usage
...
if (checkospheader()) {
log(1,"OSP header field found.\n");
} else {
log(1,"no OSP header field present\n");
};
...
This function validates an OSP-Token specified in the OSP-Auth-Tokenheader field of the SIP message. If a peering token is present, it will be validated locally. If no OSP header is found or the header token is invalid or expired, -1 is returned; on successful validation 1 is returned.
This function can be used from REQUEST_ROUTE.
Example 1.34. validateospheader usage
...
if (validateospheader()) {
log(1,"valid OSP header found\n");
} else {
log(1,"OSP header not found, invalid or expired\n");
};
...
This function gets the receiving IP address of SIP response and stores it as proxy egress address.
This function can be used from ONREPLY_ROUTE.
Example 1.35. getlocaladress usage
...
if (getlocaladdress()) {
log(1,"Obtain proxy local egress address\n");
} else {
log(1,"Failed to get proxy local egress address\n");
};
...
This function gets the receiving IP address of SIP response and stores it as proxy egress address.
This function can be used from REQUEST_ROUTE.
Example 1.36. setrequestdate usage
...
if (setrequest()) {
log(1,"Set request date\n");
} else {
log(1,"Failed to set request date\n");
};
...
This function launches a query to the peering server requesting the IP address of one or more destination peers serving the called party. If destination peers are available, the peering server will return the IP address and a peering authorization token for each destination peer. The OSP-Auth-Token Header field is inserted into the SIP message and the SIP uri is rewritten to the IP address of destination peer provided by the peering server.
The address of the called party must be a valid E164 number, otherwise this function returns -1. If the transaction was accepted by the peering server, the uri is being rewritten and 1 returned, on errors (peering servers are not available, authentication failed or there is no route to destination or the route is blocked) -1 is returned.
This function can be used from REQUEST_ROUTE.
Example 1.37. requestosprouting usage
...
if (requestosprouting()) {
log(1,"successfully queried OSP server, now relaying call\n");
} else {
log(1,"Authorization request was rejected from OSP server\n");
};
...
This function is used to check if there is any route for the call.
This function can be used from REQUEST_ROUTE.
Example 1.38. checkosproute usage
...
if (checkosproute()) {
log(1,"There is at least one route for the call\n");
} else {
log(1,"There is not any route for the call\n");
};
...
This function tries to prepare the INVITE to be forwarded using the destination in the list returned by the peering server. If the calling number is translated, a RPID value for the RPID AVP will be set. If the route could not be prepared, the function returns 'FALSE' back to the script, which can then decide how to handle the failure. Note, if checkosproute has been called and returns 'TRUE' before calling prepareosproute, prepareosproute should not return 'FALSE' because checkosproute has confirmed that there is at least one route.
This function can be used from BRANCH_ROUTE.
Example 1.39. prepareosproute usage
...
if (prepareosproute()) {
log(1,"successfully prepared the route, now relaying call\n");
} else {
log(1,"could not prepare the route, there is not route\n");
};
...
This function tries to prepare all the routes in the list returned by the peering server into SIP 300 Redirect or SIP 380 Alternative Service message. The message is then replied to the source. If unsuccessful in preparing the routes a SIP 500 is sent back and a trace message is logged.
This function can be used from REQUEST_ROUTE.
Example 1.40. prepareospresponse usage
...
if (prepareospresponse()) {
log(1,"Response is prepared.\n");
} else {
log(1,"Could not prepare the response.\n");
};
...
This function tries to prepare all the routes in the list returned by the peering server. The message is then forked off to the destinations. If unsuccessful in preparing the routes a SIP 500 is sent back and a trace message is logged.
This function can be used from REQUEST_ROUTE.
Example 1.41. prepareallosproutes usage
...
if (prepareallosproutes()) {
log(1,"Routes are prepared, now forking the call\n");
} else {
log(1,"Could not prepare the routes. No destination available\n");
};
...
This function is used to check if the calling number is translated. Before calling checkcallingtranslation, prepareosproute should be called. If the calling number does been translated, the original Remote-Party-ID, if it exists, should be removed from the INVITE message. And a new Remote-Party-ID header should be added (a RPID value for the RPID AVP has been set by prepareosproute). If the calling number is not translated, nothing should be done.
This function can be used from BRANCH_ROUTE.
Example 1.42. checkcallingtranslation usage
...
if (checkcallingtranslation()) {
# Remove the Remote_Party-ID from the received message
# Otherwise it will be forwarded on to the next hop
remove_hf("Remote-Party-ID");
# Append a new Remote_Party
append_rpid_hf();
}
...
This function should be called after receiving a BYE message. If the message contains an OSP cookie, the function will forward originating and/or terminating duration usage information to a peering server. The function returns TRUE if the BYE includes an OSP cookie. The actual usage message will be send on a different thread and will not delay BYE processing. The function should be called before relaying the message.
Meaning of the parameter is as follows:
"0" - Source device releases the call.
"1" - Destination device releases the call.
This function can be used from REQUEST_ROUTE.
Example 1.43. reportospusage usage
...
if (is_direction("downstream")) {
log(1,"This BYE message is from SOURCE\n");
if (!reportospusage("0")) {
log(1,"This BYE message does not include OSP usage information\n");
}
} else {
log(1,"This BYE message is from DESTINATION\n");
if (!reportospusage("1")) {
log(1,"This BYE message does not include OSP usage information\n");
}
}
...