Mediaproxy Module

The following modules must be loaded before this module:

The following libraries or applications must be installed before running OpenSIPS with this module loaded:

Boolean flag that specifies if mediaproxy should be disabled. This is useful when you want to use the same OpenSIPS configuration in two different context, one using mediaproxy, the other not. In the case mediaproxy is disabled, calls to its functions will have no effect, allowing you to use the same configuration without changes.

Default value is “0”.

...
modparam("mediaproxy", "disable", 1)
...
        

It is the path to the filesystem socket where the mediaproxy dispatcher listens for commands from the module.

Default value is “/var/run/mediaproxy/dispatcher.sock”.

...
modparam("mediaproxy", "mediaproxy_socket", "/var/run/mediaproxy/dispatcher.sock")
...
        

How much time (in milliseconds) to wait for an answer from the mediaproxy dispatcher.

Default value is “500”.

...
modparam("mediaproxy", "mediaproxy_timeout", 500)
...
        

Specification of the AVP which holds the IP address from where the SIP signaling originated. If this AVP is set it will be used to get the signaling IP address, else the source IP address from where the SIP message was received will be used. This AVP is meant to be used in cases where there are more than one proxy in the call setup path and the proxy that actually starts mediaproxy doesn't receive the SIP messages directly from the UA and it cannot determine the NAT IP address from where the signaling originated. In such a case attaching a SIP header at the first proxy and then copying that header's value into the signaling_ip_avp on the proxy that starts mediaproxy will allow it to get the correct NAT IP address from where the SIP signaling originated.

Default value is “$avp(s:signaling_ip)”.

...
modparam("mediaproxy", "signaling_ip_avp", "$avp(s:nat_ip)")
...
        

Specification of the AVP which holds an optional application defined media relay IP address of a particular media relay that is preferred to be used for the current call. If an IP address is written to this AVP before calling use_media_proxy(), it will be preferred by the dispatcher over the normal selection algorithm.

Default value is “$avp(s:media_relay)”.

...
modparam("mediaproxy", "media_relay_avp", "$avp(s:media_relay)")
...
        

Trigger the use of MediaProxy for all the dialog requests and replies that have an SDP body. This needs to be called only once for the first INVITE in a dialog. After that it will use the dialog module to trace the dialog and automatically call use_media_proxy() on every request and reply that belongs to the dialog and has an SDP body. When the dialog ends it will also call automatically end_media_session(). All of these are called internally on dialog callbacks, so for this function to work, the dialog module must be loaded and configured.

This function is an advanced mechanism to use a media relay without having to manually call a function on each message that belongs to the dialog. However this method is less flexible, because once things were set in motion by calling this function on the first INVITE, it cannot be stopped, not even by calling end_media_session(). It will only stop when the dialog ends. Until then it will modify the SDP content of every in-dialog message to make it use a media relay. If one needs more control over the process, like starting to use mediaproxy only later in the failure route, or stopping to use mediaproxy in the failure route, then the use_media_proxy and end_media_session functions should be used, and manually called as appropriate. Using this function should NOT be mixed with either of use_media_proxy() or end_media_session().

This function can be used from REQUEST_ROUTE.

...
if (method==INVITE && !has_totag()) {
    # We can also use a specific media relay if we need to
    #$avp(s:media_relay) = "1.2.3.4";
    engage_media_proxy();
}
...
        

Will make a call to the dispatcher and replace the IPs and ports in the SDP body with the ones returned by the media relay for each supported media stream in the SDP body. This will force the media streams to be routed through the media relay. If a mix of supported and unsupported streams are present in the SDP, only the supported streams will be modified, while the unsupported streams will be left alone.

This function should NOT be mixed with engage_media_proxy().

This function has the following return codes:

This function can be used from REQUEST_ROUTE, ONREPLY_ROUTE, FAILURE_ROUTE, BRANCH_ROUTE.

...
if (method==INVITE) {
    # We can also use a specific media relay if we need to
    #$avp(s:media_relay) = "1.2.3.4";
    use_media_proxy();
}
...
        

Will call on the dispatcher to inform the media relay to end the media session. This is done when a call ends, to instruct the media relay to release the resources allocated to that call as well as to save logging information about the media session. Called on BYE, CANCEL or failures.

This function should NOT be mixed with engage_media_proxy().

This function can be used from REQUEST_ROUTE, ONREPLY_ROUTE, FAILURE_ROUTE, BRANCH_ROUTE.

...
if (method==BYE) {
    end_media_session();
}
...