Fedora8下OpenSER安裝設定攻略

來源:互聯網
上載者:User

OpenSER首頁:http://www.openser.org

下載:http://www.openser.org/pub/openser/latest-1.2.x/src/openser-1.2.2-tls_src.tar.gz

準備

實驗平台為Fedora8, 預先裝好了MYSQL-5.0.45;

需要安裝相應的MySQL-devel-5.0.45開發包, 到這裡下載

http://ftp.plusline.de/mysql/Downloads/MySQL-5.0/MySQL-devel-5.0.45-0.i386.rpm

最好為mysql設定一個root密碼。

編譯
代碼:
tar zxvf openser-1.2.2-tls_src.tar.gz

cd openser-1.2.2-tls
make all
make prefix=/usr/local install

# 預先我編譯了幾個測試的模組和mysql
make prefix=/usr/local include_modules="dialog sl mysql" modules
make prefix=/usr/local include_modules="dialog sl mysql" install 


設定網域名稱
* 如果你的機器有網域名稱,直接使用就可以了,如果沒有,可以編輯一下/etc/hosts,加上一行:
代碼:
127.0.0.1    openser.fc8.home


* 把網域名稱加入到root使用者的OpenSER的資源檔中
代碼:
export SIP_DOMAIN=openser.fc8.home


運行
代碼:
/usr/local/sbin/openser_mysql.sh create

運行之後需要輸入上面提到的mysql資料庫的root密碼。

編輯設定檔
編輯/usr/local/etc/openser/openser.cfg,以下是我的配置,紅色部分是需要修改的,不用多講,看注釋就明白啦!:)代碼:
# ----------- global configuration parameters ------------------------

debug=3            # debug level (cmd line: -dddddddddd)
fork=yes
log_stderror=no    # (cmd line: -E)
children=4
#dns=yes
#rev_dns=yes

# Uncomment these lines to enter debugging mode
#fork=no
#log_stderror=yes
#
# 這裡是使用偵錯模式,可以將這兩個參數開啟調試你的設定檔是否
有錯


port=5060

# uncomment the following lines for TLS support
#disable_tls = 0
#listen = tls:your_IP:5061
#tls_verify_server = 1
#tls_verify_client = 1
#tls_require_client_certificate = 0
#tls_method = TLSv1
#tls_certificate = "/usr/local/etc/openser/tls/user/user-cert.pem"
#tls_private_key = "/usr/local/etc/openser/tls/user/user-privkey.pem"
#tls_ca_list = "/usr/local/etc/openser/tls/user/user-calist.pem"

# ------------------ module loading ----------------------------------

#set module path
mpath="/usr/local/lib/openser/modules/"


# Uncomment this if you want to use SQL database
loadmodule "mysql.so"

loadmodule "sl.so"
loadmodule "tm.so"
loadmodule "rr.so"
loadmodule "maxfwd.so"
loadmodule "usrloc.so"
loadmodule "registrar.so"
loadmodule "textops.so"
loadmodule "mi_fifo.so"

# Uncomment this if you want digest authentication
# mysql.so must be loaded !
loadmodule "auth.so"
loadmodule "auth_db.so"

# ----------------- setting module-specific parameters ---------------

# -- mi_fifo params --

modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo")

# -- usrloc params --

modparam("usrloc", "db_mode",   0)

# Uncomment this if you want to use SQL database
# for persistent storage and comment the previous line
modparam("usrloc", "db_mode", 2)

# -- auth params --
# Uncomment if you are using auth module
#
modparam("auth_db", "calculate_ha1", yes)
#


# If you set "calculate_ha1" parameter to yes (which true in this config),
# uncomment also the following parameter)
#
modparam("auth_db", "password_column", "password")

# -- rr params --
# add value to ;lr param to make some broken UAs happy
modparam("rr", "enable_full_lr", 1)

# -------------------------  request routing logic -------------------

# main routing logic

route{

        # initial sanity checks -- messages with
        # max_forwards==0, or excessively long requests
        if (!mf_process_maxfwd_header("10")) {
                sl_send_reply("483","Too Many Hops");
                exit;
        };

        if (msg:len >=  2048 ) {
                sl_send_reply("513", "Message too big");
                exit;
        };

        # we record-route all messages -- to make sure that
        # subsequent messages will go through our proxy; that's
        # particularly good if upstream and downstream entities
        # use different transport protocol
        if (!method=="REGISTER")
                record_route();

        # subsequent messages withing a dialog should take the
        # path determined by record-routing

        if (loose_route()) {
                # mark routing logic in request
                append_hf("P-hint: rr-enforced\r\n");
                route(1);
        };

        if (!uri==myself) {
                # mark routing logic in request
                append_hf("P-hint: outbound\r\n");
                # if you have some interdomain connections via TLS
                #if(uri=~"@tls_domain1.net") {
                #       t_relay("tls:domain1.net");
                #       exit;
                #} else if(uri=~"@tls_domain2.net") {
                #       t_relay("tls:domain2.net");
                #       exit;
                #}
                route(1);
        };

        # if the request is for other domain use UsrLoc
        # (in case, it does not work, use the following command
        # with proper names and addresses in it)
        if (uri==myself) {

                if (method=="REGISTER") {

                        # Uncomment this if you want to use digest authentication
                        if (!www_authorize("openser.org", "subscriber")) {
                                www_challenge("openser.org", "0");
                                exit;
                        };

                        save("location");
                        exit;
                };


                lookup("aliases");
                if (!uri==myself) {
                        append_hf("P-hint: outbound alias\r\n");
                        route(1);
                };

                # native SIP destinations are handled using our USRLOC DB
                if (!lookup("location")) {
                        sl_send_reply("404", "Not Found");
                        exit;
                };
                append_hf("P-hint: usrloc applied\r\n");
        };

        route(1);
}


route[1] {
        # send it out now; use stateful forwarding as it works reliably
        # even for UDP2TCP
        if (!t_relay()) {
                sl_reply_error();
        };
        exit;
}

 
 
代碼:
/usr/local/sbin/openserctl add 8001 1111 8001@tcl.com

  • 1
  • 2
  • 下一頁

聯繫我們

該頁面正文內容均來源於網絡整理,並不代表阿里雲官方的觀點,該頁面所提到的產品和服務也與阿里云無關,如果該頁面內容對您造成了困擾,歡迎寫郵件給我們,收到郵件我們將在5個工作日內處理。

如果您發現本社區中有涉嫌抄襲的內容,歡迎發送郵件至: info-contact@alibabacloud.com 進行舉報並提供相關證據,工作人員會在 5 個工作天內聯絡您,一經查實,本站將立刻刪除涉嫌侵權內容。

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.