한국어

소프트스위치

온누리070 플레이스토어 다운로드
    acrobits softphone
     온누리 070 카카오 프러스 친구추가온누리 070 카카오 프러스 친구추가친추
     카카오톡 채팅 상담 카카오톡 채팅 상담카톡
    
     라인상담
     라인으로 공유

     페북공유

   ◎위챗 : speedseoul


  
     PAYPAL
     
     PRICE
     

pixel.gif

    before pay call 0088 from app



http://www.opensips.org/Documentation/Tutorials-WebSocket-2-1



1.  Tutorial Overview

WebSocket is a protocol that provides full-duplex communication between web clients and servers over TCP connections. Using the WebSocket protocol, browsers can connect to web servers and exchange data, regardless the type or nature of the application protocol. RFC 7118 leveraged this protocol in order to allow browsers to make VoIP calls using the SIP protocol.

This document describes how to use OpenSIPS as the core component of a SIP platform that connects both SIP clients (over UDP, TCP or TLS) as well as browser based clients (using SIP over WebSockets). While OpenSIPS handles the SIP signalling part, media is handled by RTPengine, a high performance media proxy that is able to handle both RTP and SRTP media streams, as well as bridging between them.

This tutorial is inspired from

2.  Setup

2.1  RTPengine

Installation

The RTPengine consists of two main components: a kernel module used to efficiently route the RTP packets directly in kernel, and a daemon used to communicate with OpenSIPS. You can find more details here. Both components can be installed from debs (on Debian based systems) or directly from sources. Simply follow the official documentation to install RTPengine.

Usage

After installing the kernel module and the additional libraries, the rtpengine daemon has to be configured. This can be done from /etc/default/ngcp-rtpengine-daemon if installed from debs, or from the command line if the daemon is started manually. On systemd based OSes, Eric Tamme created some startup scripts.

The interesting parameters we are using are as follows:

  • -i: the listening interface for RTP/SRTP
  • -n: the listening IP and port that is used by OpenSIPS to communicate with the RTPengine (NOTE: the rtpengine module only works with the rtpengine NG protocol, so you must use -n/--listen-ng; Using -u/--listen-udp or -l/--listen-tcp will not work!)
  • -c: the IP and port of the CLI - this is used to gather statistics for the RTP/SRTP sessions
  • -m, -M: both take an integer as argument and together define the local port range from which rtpengine will allocate UDP ports for media traffic relay. Default to 30000 and 40000 respectively.
  • -L: indicates the debugging level

You can find all the parameters available here.

Here is an example that runs rtpengine from cli that talks with OpenSIPS over localhost and RTP using the 1.1.1.1 IP:

./rtpengine -p /var/run/rtpengine.pid -i eth0/1.1.1.1 -n 127.0.0.1:60000 -c 127.0.0.1:60001 -m 50000 -M 55000 -E -L 7
Troubleshoot

First make sure the rtpengine daemon is started:

ps -ef | grep rtpengine

If the rtpengine daemon does not start, make sure the xt_RTPENGINE kernel module is loaded:

lsmod | grep xt_RTPENGINE

If the module is not loaded, make sure the ip_tables and x_tables kernel modules are loaded. Also, check the logs for the last errors of the system

dmesg

2.2  OpenSIPS

In order to use WebSocket in OpenSIPS, one has to load the proto_ws into its configuration file and define a listener for the WebSocket protocol.

listen=ws:127.0.0.1:8080
...
loadmodule "proto_ws.so"

Next, the rtpengine module has to be loaded and configured to communicate with the rtpengine daemon.

loadmodule "rtpengine.so"
modparam("rtpengine", "rtpengine_sock", "udp:127.0.0.1:60000")

Note that the rtpengine_sock parameter should be the same as the -n parameter sent to the rtpengine daemon, and OpenSIPS should have IP connectivity to that socket.

Next, the routing logic has to be changed in order to treat different the clients that use DTLS-SRTP, from the ones that use plain RTP and enable bridging if necessary. To do that, one can check if the request message was received over the WebSocket protocol. This can be achieved using the following code:

if (proto == WS)
    setflag(SRC_WS);

In case the request is a REGISTER, we want to store this information in the location table, so that we know then the user is called. To do that, we can set a branch flag before calling the save()function. This way, when the lookup() method returns, we will be able to determine whether the client uses WebSocket or not.

    if (is_method("REGISTER")) {
        if (isflagset(SRC_WS))
            setbflag(DST_WS);

        fix_nated_register();
        if (!save("location"))                                                                                                                                 
            sl_reply_error();

        exit;
    }

When a call is placed, based on the two flags (STR_WS and DST_WS) we can determine what our caller and callee can "speak" (either RTP or DTLS-SRTP) and instruct the rtpengine daemon how to handle the call. We can do that by tuning the parameters passed to the rtpengine_offer() function.

    if (isflagset(SRC_WS) && isbflagset(DST_WS))
        $var(rtpengine_flags) = "ICE=force-relay DTLS=passive";
    else if (isflagset(SRC_WS) && !isbflagset(DST_WS))
        $var(rtpengine_flags) = "RTP/AVP replace-session-connection replace-origin ICE=remove";
    else if (!isflagset(SRC_WS) && isbflagset(DST_WS))
        $var(rtpengine_flags) = "UDP/TLS/RTP/SAVPF ICE=force";
    else if (!isflagset(SRC_WS) && !isbflagset(DST_WS))
        $var(rtpengine_flags) = "RTP/AVP replace-session-connection replace-origin ICE=remove";

    rtpengine_offer("$var(rtpengine_flags)");

The rtpengine_answer() function logic should look like this:

    if (isflagset(SRC_WS) && isbflagset(DST_WS))
        $var(rtpengine_flags) = "ICE=force-relay DTLS=passive";
    else if (isflagset(SRC_WS) && !isbflagset(DST_WS))
        $var(rtpengine_flags) = "UDP/TLS/RTP/SAVPF ICE=force";
    else if (!isflagset(SRC_WS) && isbflagset(DST_WS))
        $var(rtpengine_flags) = "RTP/AVP replace-session-connection replace-origin ICE=remove";
    else if (!isflagset(SRC_WS) && !isbflagset(DST_WS))
        $var(rtpengine_flags) = "RTP/AVP replace-session-connection replace-origin ICE=remove";

    rtpengine_answer("$var(rtpengine_flags)");

Now, all we have to do is to close the RTP/SRTP session when the call is ended. To do that, we use the rtpengine_delete() function:

    if (is_method("BYE|CANCEL")) {                                                                                                                      
        rtpengine_delete();

Having done all these settings should provide a full setup for interconnecting SIP clients over both UDP, TCP, etc. protocols, as well as browser based SIP clients over WebSocket.

조회 수 :
52732
등록일 :
2017.09.06
08:19:51 (*.160.88.18)
엮인글 :
http://webs.co.kr/index.php?document_srl=3311817&act=trackback&key=ebf
게시글 주소 :
http://webs.co.kr/index.php?document_srl=3311817
List of Articles
번호 제목 글쓴이 날짜 조회 수
138 Using TLS in OpenSIPS v2.2.x admin 2017-09-14 44052
137 opensips tls cfg admin 2017-09-14 29165
136 How to setup a Jabber / XMPP server on Debian 8 (jessie) using ejabberd admin 2017-09-13 122988
135 SIP to XMPP Gateway + SIP Presence Server opensips admin 2017-09-13 51446
134 OpenSIPS command line tricks admin 2017-09-13 44246
133 Fail2Ban Freeswitch How to secure admin 2017-09-12 60587
132 opensips.cfg. sample admin 2017-09-12 23514
131 Advanced SIP scenarios with Event-based-Routing admin 2017-09-11 32443
130 PUSH SERVER 푸시서버 안드로이드 애플 admin 2017-09-11 206809
129 오픈소스 (사내)메신저 서버 구축, 오픈 파이어(openfire) 설치방법과 세팅(리눅스 기준) admin 2017-09-09 70696
» rtpengine config basic and opensips configuration and command admin 2017-09-06 52732
127 WebSocket Transport using OpenSIPS configuration 웹 소켓 컨피그레이션 기본 admin 2017-09-06 20380
126 OpenSIPS basic configuration script 기본 컨피그 admin 2017-09-05 104048
125 rtpengine install and config admin 2017-09-05 57791
124 Installing RTPEngine on Ubuntu 14.04 admin 2017-09-05 31562
123 compile only the textops module make modules=modules/textops modules admin 2017-09-05 18528
122 opensips command /sbin/opensipsctl detail admin 2017-09-04 123748
121 2017 08 31 opensips 2.32 install debian8.8 module install compile err modules admin 2017-09-04 41472
120 Build-Depends debian 8.8 opensips 2.3 admin 2017-09-04 63702
119 What is new in 2.3.0 opensips admin 2017-09-04 243270
118 ubuntu 安装配置opensips,rtpproxy,mediaproxy admin 2017-09-04 23163
117 How to install Mediaproxy 2.5.2 on CentOS 6 64 bit admin 2017-09-04 142140
116 Using TLS in OpenSIPS v2.2.x configuration admin 2017-09-04 46467
115 How to 2.3 download , OpenSIPS new apt repository. DEBs for Debian / Ubuntu admin 2017-09-02 18234
114 You can install CDRTool in the following ways: admin 2017-09-01 19745
113 How to Install OpenSIPS 2.1.2 Server on Ubuntu 15.04 admin 2017-09-01 25880
112 Opensips 2.32 download admin 2017-09-01 17626
111 OpenSIPS 2.3 install admin 2017-09-01 23684
110 JsSIP: The JavaScript SIP Library admin 2017-09-01 19901
109 WebSocket Transport using OpenSIPS admin 2017-09-01 23508