similarity index 100%

rename from modules_k/mediaproxy/Makefile

rename to modules/mediaproxy/Makefile

similarity index 100%

rename from modules_k/mediaproxy/README

rename to modules/mediaproxy/README

similarity index 100%

rename from modules_k/mediaproxy/doc/mediaproxy.xml

rename to modules/mediaproxy/doc/mediaproxy.xml

similarity index 100%

rename from modules_k/mediaproxy/doc/mediaproxy_admin.xml

rename to modules/mediaproxy/doc/mediaproxy_admin.xml

similarity index 100%

rename from modules_k/mediaproxy/mediaproxy.c

rename to modules/mediaproxy/mediaproxy.c

deleted file mode 100644

@@ -1,16 +0,0 @@

-# $Id$

-#

-# mediaproxy module makefile

-#

-# 

-# WARNING: do not run this directly, it should be run by the master Makefile

-

-include ../../Makefile.defs

-auto_gen=

-NAME=mediaproxy.so

-LIBS=

-

-DEFS+=-DSER_MOD_INTERFACE

-

-include ../../Makefile.modules

-

deleted file mode 100644

@@ -1,259 +0,0 @@

-

-                       Mediaproxy SER module

-

-                        Copyright Dan Pascu

-    		       2002-2004 AG Projects

-

-

-  Mediaproxy is a SER module that is designed to allow automatic NAT

-traversal for the majority of existing SIP clients. This means that there

-will be no need to configure anything in particular on the NAT box to allow

-these clients to work behind NAT when using the mediaproxy module.

-

-Section 1 for a description of the modus operandi.

-Section 2 describes the types of SIP phones that work with mediaproxy and a

-          short description about how the NAT traversal is working.

-Section 3 is about mediaproxy features.

-Section 4 describes the exported module parameters and functions.

-Section 5 is a comparison with nathelper.

-

-1. Principle of operation

-   ----------------------

-

-  This NAT traversal solution operates by placing a mediaproxy server in the

-middle between 2 SIP user-agents. It mangles the SDP messages for both of

-them in a way that will make the parties talk with mediaproxy while they

-think they talk directly with each other.

-

-To achieve this, mediaproxy is actually composed by 2 components:

-  - the SER mediaproxy module itself

-  - an external proxy server called SER MediaProxy (available from

-    http://mediaproxy.ag-projects.com/ )

-

-To avoid confusion in this document the mediaproxy module will be called

-'module' or 'mediaproxy module', while the mediaproxy server will be called

-'proxy server' from here on.

-

-  The proxy server can be run on the same machine as the module or on a

-remote host. Moreover it is possible for a single module to control multiple

-proxy servers running on multiple geographically distributed hosts. To find

-out more about the architecture of SER MediaProxy please read the

-documentation that comes with it.

-

-  To be able to act as a proxy between the 2 talking parties, the machine(s)

-running the module/proxy server must have a public IP address.

-

-  The module will ask the proxy server to allocate as many sockets as there

-are media streams in the SDP body of the SIP INVITE/Ok messages. The proxy

-server will send back to the module the address and port(s) for them. Then

-the module will replace the original contact IP and RTP ports from the SDP

-messages with the ones provided by the proxy server. By doing this both

-clients will try to contact the proxy server instead of talking directly

-with each other. Once the clients contact the proxy server, it will record

-the addresses they came from and will know where to forward packets received

-from the other party This is needed because the address/port the NAT box

-will allocate for the leaving streams is not known before they actually

-leave the NAT box. However the address of the proxy server is always known

-(being a public one) so the 2 parties know where to connect and then after

-they did so, the proxy learns the addresses they came from and can forward

-packets between them.

-

-

-2. Types of SIP clients

-   --------------------

-

-  The SIP clients that will work transparently behind NAT when using the

-mediaproxy module are the so-called symmetric clients. The symmetric clients

-have the particularity that use the same port to send the data as the one

-they use to receive it. In other words, if they are for example configured

-to use port 5060 for SIP signaling, they will use the same port when sending

-data as well as when receiving it. This must be true for both the SIP

-signaling as well as the RTP streams for a client to work transparently with

-the mediaproxy module without any additional configuration on the NAT box.

-

-  This ability is important because the only way to get back to a client

-behind NAT is to send to the IP address and port the packet was received

-from. Once a packet is sent from the client behind NAT to the outside world,

-it opens a communication channel in the NAT box that is open in both

-directions for a while (it will timeout after a while after no more data is

-sent through it, but it can be kept active by sending data through it at

-certain regular time intervals). While this channel is open, any data sent

-to the public address and port that the NAT box assigned for the address and

-port the client behind NAT is sending from (and this mapping is guaranteed

-to be unique), will go back straight to the address and port the client has

-sent from. This is why is necessary for the clients to be symmetric. If they

-listen on the same port they sent from, the data sent back to the public

-address that the NAT box assigned to the leaving packets will actually reach

-the listening port of the client behind NAT.

-

-  Some SIP clients implement particular algorithms to detect if they are

-actually behind a NAT box and try to act smart by detecting the IP address

-of the NAT box (or simply allowing one to manually configure it), and then

-use this IP address in the SIP and SDP messages instead of their own private

-IP address. This situation can be confusing for a module that tries to

-perform transparent NAT traversal as it can wrongly mistake such a client

-that is behind NAT with a client that is actually in the public address

-space. However for the mediaproxy module it is not important if the clients

-apply or not this kind of behavior, as it is able to cope with both

-situations gracefully.

-

-  This doesn't mean that mediaproxy is not able to work with asymmetric

-clients behind NAT, but in their case special static forwarding routes need

-to be configured on the NAT box.

-

-  Mediaproxy has special support for asymmetric clients, can detect them and

-send the data to the ports they expect it to, however they can work behind

-NAT only if static routes are configured on the NAT box since there is no

-way of getting back to an address/port that has not previously opened a data

-channel in the NAT box by sending something out first. Nevertheless the

-support for asymmetric clients is important, because without it they won't

-be able to work even when they have public Internet addresses. Also this

-support allows one to use an asymmetric client behind NAT if he can

-configure the NAT box to forward the packets meant to that client.

-

-  The only requirement a symmetric SIP client must met to be able to work

-transparently behind NAT when using the mediaproxy module is to accept to be

-configured to use a so called outbound proxy and this proxy must be the one

-running with the mediaproxy module loaded.

-

-

-3. Features

-   --------

-

-- make symmetric clients work behind NAT transparently if they use the SIP

-  server as the outbound SIP server.

-- handle all media streams specified in the SDP body. There is a limit of 64

-  RTP streams per session in the code now, but we hardly find this to be a

-  limitation for the time being.

-- able to distribute RTP traffic load on multiple proxy servers running on

-  multiple hosts.

-- able to specify which proxy server to use based on the SIP domain of the

-  caller/destination (done by the proxy server's dispatcher module)

-- handle asymmetric clients properly. They can even work behind NAT if a

-  proper port forwarding is done for them on the NAT box.

-

-

-4. Module parameters and exported functions

-   ----------------------------------------

-

-  The module exports the following parameters:

-

-  - mediaproxy_socket

-

-    it is the path to the filesystem socket where the proxy server

-    listens for commands from the module.

-

-  - sip_asymmetrics

-

-    it is the path to a file that lists regular expressions that match

-    'User-Agent' or 'Server' fields from clients that are asymmetric

-    regarding SIP signaling. Needed to detect when a client is asymmetric

-    regarding SIP signaling. An example file is in the config/ subdirectory.

-

-  - rtp_asymmetrics

-

-    it is the path to a file that lists regular expressions that match

-    'User-Agent' or 'Server' fields from clients that are asymmetric

-    regarding the RTP media. Needed to detect when a client is asymmetric

-    regarding the RTP media. An example file is in the config/ subdirectory.

-

-  - natping_interval

-

-    it holds an integer value representing how often the module will

-    send packets to all registered clients that are behind NAT to keep

-    their opened channels alive. Represents an interval in seconds.

-

-Parameters are set in the SER configuration file by using the modparam

-command. Below are examples, which contain the actual default values of the

-parameters. If you are Ok with them it is not necessary to specify them in the

-configuration file at all.

-

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

-modparam("mediaproxy", "sip_asymmetrics", "/etc/ser/sip-asymmetrics-clients")

-modparam("mediaproxy", "rtp_asymmetrics", "/etc/ser/rtp-asymmetrics-clients")

-modparam("mediaproxy", "natping_interval", 20)

-

-  The module exports the following functions:

-

-  - client_nat_test(type)

-

-    tests if the client is behind NAT or not. The types of tests are

-    specified by the type parameter which represents a sum of the 

-    following numbers (add the values of the ones you wish to perform

-    tests for):

-

-      1 - tests if client has a private IP address (as defined by RFC1918)

-          in the Contact field of the SIP message.

-

-      2 - tests if client has contacted SER from an address that is different

-          from the one in the 1st Via field. Both IP and port are checked,

-          except for asymmetric clients for which the port is ignored.

-

-      4 - tests if client has a private IP address (as defined by RFC1918)

-          in the top Via field of the SIP message.

-

-    for example calling client_nat_test("3") in ser.cfg will perform

-    first 2 tests listen above and return true as soon as one succeeds

-    if both fail will return false.

-

-  - fix_contact()

-

-    will replace the IP:Port in the Contact field of the SIP message

-    with the ones the SIP message was received from. For clients that

-    are asymmetric regarding SIP signaling (as determined from the

-    sip_asymmetrics file) will preserve the port.

-    usually called after an if (client_nat_test(type)) has succeded

-

-  - use_media_proxy()

-

-    will make a call to the proxy server and replace the IPs and ports

-    in the SDP body with the ones returned by the proxy server for

-    each media stream that the SDP message describes. This will force

-    the media streams to be routed through the proxy server.

-    called when you want to make the session go through a proxy server

-

-  - end_media_session()

-

-    will call on the proxy server to end the media session for that call

-    this is done at the end of the call to instruct the proxy server to

-    free the resources allocated to that call as well as to save log

-    information about the call.

-    called when a session should end (BYE or CANCEL received)

-

-

-5. Comparison with the nathelper module

-   ------------------------------------

-

-  After reading all this you may wonder what this module can offer you that

-the nathelper module (a similar nat traversal solution) can't and why was

-necessary to develop this module.

-

-While at surface they seem to offer about the same functionality, there are

-a few core differences that make them quite different.

-

-  The main and most notable difference is that mediaproxy offers a

-distributed environment, where the mediaproxy module can control multiple

-mediaproxy servers. The mediaproxy servers can be local or remote and they

-can be specified per domain or as defaults for domains that don't have their

-own mediaproxy servers defined. These mediaproxy servers can be arranged in

-load balancing and fallback schemes allowing the platform to scale up easily

-and also offer redundancy to keep the service running even if some of the

-mediaproxies go offline. Mediaproxy is able to detect the dead proxies and

-redistribute the calls among the other mediaproxies that are available.

-(More details about this can be found in the SER MediaProxy documentation)

-

-  Another important difference is that mediaproxy tries to move the complex

-logic of decision from the ser configuration file to the module and the

-proxy servers themselves. This is why there are very few functions in this

-module that take any parameters. Instead, control is achieved by modifying

-resources outside of ser.cfg. This includes for example specifying the

-mediaproxy servers using DNS SRV records, or declaring asymmetric clients

-in external files that are automatically re-read as soon as they change.

-This allows SER to run without interruption or restarts. If one wants to

-change SER's behavior, instead of changing ser.cfg and restarting SER, one

-will change these external resources and SER will adapt it's behavior on the

-fly without any need for restart.

-Another advantage of this is that ser.cfg becomes simpler and easier to

-maintain.

-

-

deleted file mode 100644

@@ -1,8 +0,0 @@

-

-sip-asymmetric-clients and rtp-asymmetric-clients list clients that are

-asymmetric regarding the SIP signaling respective the RTP media streams.

-

-By default these files should go in /etc/ser/ (unless specifically

-configured to be somewhere else using the sip_asymmetrics and/or

-rtp_asymmetrics options available with the mediaproxy module.

-

deleted file mode 100644

@@ -1,12 +0,0 @@

-#

-# Lines starting with a '#' character or empty lines are ignored.

-# Put a User-Agent name or regular expression per line.

-# Check is case insensitive.

-#

-# This file should only list SIP clients that are asymmetric regarding

-# the RTP media streams. For clients that are asymmetric regarding the SIP

-# signaling, use the equivalent SIP version of this file.

-# Clients that are asymmetric for both SIP signaling as well as RTP media

-# streams should go in both files.

-#

-

deleted file mode 100644

@@ -1,118 +0,0 @@

-# Example ser.cfg for mediaproxy functionality

-

-loadmodule "/usr/lib/ser/modules/registrar.so"

-loadmodule "/usr/lib/ser/modules/domain.so"

-loadmodule "/usr/lib/ser/modules/mediaproxy.so"

-

-modparam("mediaproxy", "natping_interval", 60)

-modparam("registrar",  "nat_flag",         2)

-

-route{

-    if (!mf_process_maxfwd_header("10")) {

-        if (method!="ACK") {

-            sl_send_reply("483", "Too many hops");

-        };

-        break;

-    };

-

-    if (msg:len >= max_len) {

-        if (method!="ACK") {

-            sl_send_reply("513", "Message too big");

-        };

-        break;

-    };

-

-    if (method=="REGISTER") {

-        if (is_from_local()) {

-            # Mark as NAT'ed

-            if (client_nat_test("3")) {

-                setflag(2);

-                force_rport();

-                fix_contact();

-            };

-

-            if (!www_authorize("", "subscriber")) {

-                www_challenge("", "0");

-                break;

-            } else if (!check_to()) {

-                sl_send_reply("403", "Username!=To not allowed");

-                break;

-            };

-

-            if (!save("location")) {

-                sl_reply_error();  

-            };

-        } else {

-            sl_send_reply("403", "This domain is not served here");

-        };

-

-        break;

-    };

-

-    if (method=="INVITE") {

-        if (!(is_from_local() || is_uri_host_local())) {

-            sl_send_reply("403", "Relaying is forbidden");

-            break;

-        };

-        t_on_failure("1");

-    } else if (method == "BYE" || method == "CANCEL") {

-        end_media_session();

-    };

-

-    if (loose_route()) { 

-        if (method=="INVITE" || method=="ACK") {

-            use_media_proxy();

-        };

-        # end media session for BYE and CANCEL is done above

-        # before entering the loose route. no need to call it here

-        t_relay();

-        break;

-    };

-

-    # Force subsequent messages to pass trough this proxy

-    if (method == "INVITE") {

-        record_route();

-    };

-

-    if (client_nat_test("3") && !search("^Record-Route:")) {

-        # Mark as NAT'ed

-        force_rport();

-        fix_contact();

-    };

-

-    if (method=="INVITE") {

-        t_on_reply("1");

-    };

-

-    if (is_uri_host_local()) { # join with next if?

-        if (!lookup("location")) {

-            sl_send_reply("404", "User not found");

-            break;

-        };

-    };

-

-    if (method=="INVITE" || method=="ACK") {

-        use_media_proxy();

-    };

-

-    if (!t_relay()) {

-        if (method=="INVITE" || method=="ACK") {

-            end_media_session();

-        };

-        sl_reply_error();

-    };

-}

-

-failure_route[1] {

-    end_media_session();

-}

-

-onreply_route[1] {

-    if (status=~"(183)|(2[0-9][0-9])") {

-        if (client_nat_test("1")) {

-            fix_contact();

-        };

-        use_media_proxy();

-    };

-}

-

deleted file mode 100644

@@ -1,14 +0,0 @@

-#

-# Lines starting with a '#' character or empty lines are ignored.

-# Put a User-Agent name or regular expression per line.

-# Check is case insensitive.

-#

-# This file should only list SIP clients that are asymmetric regarding

-# the SIP signaling. For clients that are asymmetric regarding the RTP

-# media streams, use the equivalent RTP version of this file.

-# Clients that are asymmetric for both SIP signaling as well as RTP media

-# streams should go in both files.

-#

-

-ipDialog SipTone.*

-

deleted file mode 100644

@@ -1,194 +0,0 @@

-/* $Id$

- *

- * Copyright (C) 2004 Dan Pascu

- * Copyright (C) 2003 Porta Software Ltd

- *

- * This file is part of ser, a free SIP server.

- *

- * ser is free software; you can redistribute it and/or modify

- * it under the terms of the GNU General Public License as published by

- * the Free Software Foundation; either version 2 of the License, or

- * (at your option) any later version

- *

- * For a license to use the ser software under conditions

- * other than those described here, or to purchase support for this

- * software, please contact iptel.org by e-mail at the following addresses:

- *    info@iptel.org

- *

- * ser is distributed in the hope that it will be useful,

- * but WITHOUT ANY WARRANTY; without even the implied warranty of

- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the

- * GNU General Public License for more details.

- *

- * You should have received a copy of the GNU General Public License

- * along with this program; if not, write to the Free Software

- * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

- *

- */

-

-static void

-pingClients(unsigned int ticks, void *param)

-{

-    static char pingbuf[4] = "\0\0\0\0";

-    static int length = 256;

-    struct hostent* hostent;

-    struct dest_info dst;

-    struct sip_uri uri;

-    void *buf, *ptr;

-    str contact;

-    int needed;

-    char proto;

-

-    buf = pkg_malloc(length);

-    if (buf == NULL) {

-        LOG(L_ERR, "error: mediaproxy/pingClients(): out of memory\n");

-        return;

-    }

-    needed = userLocation.get_all_ucontacts(buf, length, FL_NAT);

-    if (needed > 0) {

-        // make sure we alloc more than actually we were told is missing

-        // (some clients may register while we are making these calls)

-        length = (length + needed) * 2;

-        ptr = pkg_realloc(buf, length);

-        if (ptr == NULL) {

-            LOG(L_ERR, "error: mediaproxy/pingClients(): out of memory\n");

-            pkg_free(buf);

-            return;

-        } else {

-            buf = ptr;

-        }

-        // try again. we may fail again if _many_ clients register in between

-        needed = userLocation.get_all_ucontacts(buf, length, FL_NAT);

-        if (needed != 0) {

-            pkg_free(buf);

-            return;

-        }

-    }

-

-    ptr = buf;

-    while (1) {

-        memcpy(&(contact.len), ptr, sizeof(contact.len));

-        if (contact.len == 0)

-            break;

-        contact.s = (char*)ptr + sizeof(contact.len);

-        ptr = contact.s + contact.len;

-		init_dest_info(&dst);

-	memcpy(&dst.send_sock, ptr, sizeof(dst.send_sock));

-	ptr += sizeof(dst.send_sock);

-        if (parse_uri(contact.s, contact.len, &uri) < 0) {

-            LOG(L_ERR, "error: mediaproxy/pingClients(): can't parse contact uri\n");

-            continue;

-        }

-        if (uri.proto != PROTO_UDP && uri.proto != PROTO_NONE)

-            continue;

-        if (uri.port_no == 0)

-            uri.port_no = SIP_PORT;

-        proto=PROTO_UDP;

-        hostent = sip_resolvehost(&uri.host, &uri.port_no, &proto);

-        if (hostent == NULL){

-            LOG(L_ERR, "error: mediaproxy/pingClients(): can't resolve host\n");

-            continue;

-        }

-        hostent2su(&dst.to, hostent, 0, uri.port_no);

-	if (dst.send_sock==0) {

- 		dst.send_sock = get_send_socket(0, &dst.to, PROTO_UDP);

-        	if (dst.send_sock == NULL) {

-			LOG(L_ERR, "error: mediaproxy/pingClients(): can't get "

-			    "sending socket\n");

-			continue;

-		}

-        }

-		dst.proto=PROTO_UDP;

-        udp_send(&dst, pingbuf, sizeof(pingbuf));

-    }

-    pkg_free(buf);

-}

-

-

-// Replace IP:Port in Contact field with the source address of the packet.

-// Preserve port for SIP asymmetric clients

-static int

-FixContact(struct sip_msg* msg, char* str1, char* str2)

-{

-    str beforeHost, after, agent;

-    contact_t* contact;

-    struct lump* anchor;

-    struct sip_uri uri;

-    char *newip, *buf;

-    int len, newiplen, offset;

-    Bool asymmetric;

-

-    if (!getContactURI(msg, &uri, &contact))

-        return -1;

-

-    newip = ip_addr2a(&msg->rcv.src_ip);

-    newiplen = strlen(newip);

-

-    /* Don't do anything if the IP's are the same. Return success. */

-    if (newiplen==uri.host.len && memcmp(uri.host.s, newip, newiplen)==0) {

-        return 1;

-    }

-

-    if (uri.port.len == 0)

-        uri.port.s = uri.host.s + uri.host.len;

-

-    agent = getUserAgent(msg);

-    asymmetric = isSIPAsymmetric(agent);

-

-    beforeHost.s   = contact->uri.s;

-    beforeHost.len = uri.host.s - contact->uri.s;

-    if (asymmetric) {

-        // for asymmetrics we preserve the original port

-        after.s   = uri.port.s;

-        after.len = contact->uri.s + contact->uri.len - after.s;

-    } else {

-        after.s   = uri.port.s + uri.port.len;

-        after.len = contact->uri.s + contact->uri.len - after.s;

-    }

-

-    len = beforeHost.len + newiplen + after.len + 20;

-

-    // first try to alloc mem. if we fail we don't want to have the lump

-    // deleted and not replaced. at least this way we keep the original.

-    buf = pkg_malloc(len);

-    if (buf == NULL) {

-        LOG(L_ERR, "error: fix_contact(): out of memory\n");

-        return -1;

-    }

-

-    offset = contact->uri.s - msg->buf;

-    anchor = del_lump(msg, offset, contact->uri.len, HDR_CONTACT_T);

-

-    if (!anchor) {

-        pkg_free(buf);

-        return -1;

-    }

-

-    if (asymmetric && uri.port.len==0) {

-        len = sprintf(buf, "%.*s%s%.*s", beforeHost.len, beforeHost.s,

-                      newip, after.len, after.s);

-    } else if (asymmetric) {

-        len = sprintf(buf, "%.*s%s:%.*s", beforeHost.len, beforeHost.s,

-                      newip, after.len, after.s);

-    } else {

-        len = sprintf(buf, "%.*s%s:%d%.*s", beforeHost.len, beforeHost.s,

-                      newip, msg->rcv.src_port, after.len, after.s);

-    }

-

-    if (insert_new_lump_after(anchor, buf, len, HDR_CONTACT_T) == 0) {

-        pkg_free(buf);

-        return -1;

-    }

-

-    contact->uri.s   = buf;

-    contact->uri.len = len;

-

-    if (asymmetric) {

-        LOG(L_INFO, "info: fix_contact(): preserved port for SIP "

-            "asymmetric client: `%.*s'\n", agent.len, agent.s);

-    }

-

-    return 1;

-}

-

-

deleted file mode 100644

@@ -1,1604 +0,0 @@

-/* $Id$

- *

- * Copyright (C) 2004 Dan Pascu

- *

- * This file is part of ser, a free SIP server.

- *

- * ser is free software; you can redistribute it and/or modify

- * it under the terms of the GNU General Public License as published by

- * the Free Software Foundation; either version 2 of the License, or

- * (at your option) any later version

- *

- * For a license to use the ser software under conditions

- * other than those described here, or to purchase support for this

- * software, please contact iptel.org by e-mail at the following addresses:

- *    info@iptel.org

- *

- * ser is distributed in the hope that it will be useful,

- * but WITHOUT ANY WARRANTY; without even the implied warranty of

- * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the

- * GNU General Public License for more details.

- *

- * You should have received a copy of the GNU General Public License

- * along with this program; if not, write to the Free Software

- * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

- *

- */

-

-// TODO

-//

-// - make the asymmetric files use CFG_DIR

-// - find a way to install the config files with make install

-

-#include "../../sr_module.h"

-#include "../../dprint.h"

-#include "../../str.h"

-#include "../../error.h"

-#include "../../data_lump.h"

-#include "../../forward.h"

-#include "../../mem/mem.h"

-#include "../../resolve.h"

-#include "../../timer.h"

-#include "../../ut.h"

-#include "../../parser/parse_from.h"

-#include "../../parser/parse_to.h"

-#include "../../parser/parse_uri.h"

-#include "../../msg_translator.h"

-#include "../../id.h"

-#include "../registrar/sip_msg.h"

-#include "../usrloc/usrloc.h"

-

-#include <stdio.h>

-#include <stdlib.h>

-#include <unistd.h>

-#include <string.h>

-#include <ctype.h>

-#include <errno.h>

-#include <regex.h>

-#include <sys/types.h>

-#include <sys/stat.h>

-#include <sys/socket.h>

-#include <netinet/in.h>

-#include <arpa/inet.h>

-#include <sys/un.h>

-

-

-MODULE_VERSION

-

-

-// Although `AF_LOCAL' is mandated by POSIX.1g, `AF_UNIX' is portable to

-// more systems.  `AF_UNIX' was the traditional name stemming from BSD, so

-// even most POSIX systems support it.  It is also the name of choice in

-// the Unix98 specification. So if there's no AF_LOCAL fallback to AF_UNIX

-#ifndef AF_LOCAL

-# define AF_LOCAL AF_UNIX

-#endif

-

-

-#define min(x, y)         (((x) < (y)) ? (x) : (y))

-

-#define isAnyAddress(adr) ((adr).len==7 && memcmp("0.0.0.0", (adr).s, 7)==0)

-

-

-typedef int Bool;

-#define True  1

-#define False 0

-

-

-typedef int  (*CheckLocalPartyProc)(struct sip_msg* msg, char* s1, char* s2);

-

-typedef Bool (*NatTestProc)(struct sip_msg* msg);

-

-

-typedef enum {

-    NTNone=0,

-    NTPrivateContact=1,

-    NTSourceAddress=2,

-    NTPrivateVia=4

-} NatTestType;

-

-typedef enum {

-    STUnknown=0,

-    STAudio,

-    STVideo,

-    STAudioVideo

-} StreamType;

-

-typedef struct {

-    const char *name;

-    uint32_t address;

-    uint32_t mask;

-} NetInfo;

-

-typedef struct {

-    str ip;

-    str port;

-    str type;    // stream type (`audio', `video', ...)

-    int localIP; // true if the IP is locally defined inside this media stream

-} StreamInfo;

-

-typedef struct {

-    NatTestType test;

-    NatTestProc proc;

-} NatTest;

-

-typedef struct {

-    char *file;        // the file which lists the asymmetric clients

-    long timestamp;    // for checking if it was modified

-

-    regex_t **clients; // the asymmetric clients regular expressions

-    int size;          // size of array above

-    int count;         // how many clients are in array above

-} AsymmetricClients;

-

-

-/* Function prototypes */

-static int ClientNatTest(struct sip_msg *msg, char *str1, char *str2);

-static int FixContact(struct sip_msg *msg, char *str1, char *str2);

-static int UseMediaProxy(struct sip_msg *msg, char *str1, char *str2);

-static int EndMediaSession(struct sip_msg *msg, char *str1, char *str2);

-

-static int mod_init(void);

-

-static Bool testPrivateContact(struct sip_msg* msg);

-static Bool testSourceAddress(struct sip_msg* msg);

-static Bool testPrivateVia(struct sip_msg* msg);

-

-

-/* Local global variables */

-static char *mediaproxySocket = "/var/run/proxydispatcher.sock";

-

-static int natpingInterval = 60; // 60 seconds

-

-static usrloc_api_t userLocation;

-

-static AsymmetricClients sipAsymmetrics = {

-    "/etc/ser/sip-asymmetric-clients",

-    //CFG_DIR"/sip-asymmetric-clients",

-    0,

-    NULL,

-    0,

-    0

-};

-

-static AsymmetricClients rtpAsymmetrics = {

-    "/etc/ser/rtp-asymmetric-clients",

-    0,

-    NULL,

-    0,

-    0

-};

-

-//static CheckLocalPartyProc isToLocal;

-

-NetInfo rfc1918nets[] = {

-    {"10.0.0.0",    0x0a000000UL, 0xff000000UL},

-    {"172.16.0.0",  0xac100000UL, 0xfff00000UL},

-    {"192.168.0.0", 0xc0a80000UL, 0xffff0000UL},

-    {NULL,          0UL,          0UL}

-};

-

-NatTest natTests[] = {

-    {NTPrivateContact, testPrivateContact},

-    {NTSourceAddress,  testSourceAddress},

-    {NTPrivateVia,     testPrivateVia},

-    {NTNone,           NULL}

-};

-

-static cmd_export_t commands[] = {

-    {"fix_contact",       FixContact,      0, 0,             REQUEST_ROUTE | ONREPLY_ROUTE },

-    {"use_media_proxy",   UseMediaProxy,   0, 0,             REQUEST_ROUTE | ONREPLY_ROUTE },

-    {"end_media_session", EndMediaSession, 0, 0,             REQUEST_ROUTE | ONREPLY_ROUTE | FAILURE_ROUTE },

-    {"client_nat_test",   ClientNatTest,   1, fixup_int_1, REQUEST_ROUTE | ONREPLY_ROUTE | FAILURE_ROUTE },

-    {0, 0, 0, 0, 0}

-};

-

-static param_export_t parameters[] = {

-    {"mediaproxy_socket", PARAM_STRING, &mediaproxySocket},

-    {"sip_asymmetrics",   PARAM_STRING, &(sipAsymmetrics.file)},

-    {"rtp_asymmetrics",   PARAM_STRING, &(rtpAsymmetrics.file)},

-    {"natping_interval",  PARAM_INT,    &natpingInterval},

-    {0, 0, 0}

-};

-

-struct module_exports exports = {

-    "mediaproxy", // module name

-    commands,     // module exported functions

-    0,            // RPC methods

-    parameters,   // module exported parameters