한국어

소프트스위치

온누리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.

조회 수 :
53574
등록일 :
2017.09.06
08:19:51 (*.160.88.18)
엮인글 :
http://webs.co.kr/index.php?document_srl=3311817&act=trackback&key=60f
게시글 주소 :
http://webs.co.kr/index.php?document_srl=3311817
List of Articles
번호 제목 글쓴이 날짜 조회 수sort
81 The Impact of TLS on SIP Server Performance file admin 2014-03-12 41957
80 SIP Signaling-Messages OpenSIPS Running On Multicore Server file admin 2014-11-02 41967
79 opensips complete configuration example admin 2017-12-10 42064
78 Ekiga (formely known as GnomeMeeting) is an open source SoftPhone admin 2014-03-12 42119
77 Opensips Modules Documentation admin 2014-08-18 42143
76 Building Telephony Systems with OpenSIPS 1.6 books file admin 2014-03-06 42387
75 2017 08 31 opensips 2.32 install debian8.8 module install compile err modules admin 2017-09-04 42389
74 book-opensips-101 / content / 3.2. SIP TLS Secure Calling.mediawiki admin 2014-03-12 42447
73 OpenSIPS Module Interface admin 2017-12-07 42496
72 OpenSIPS Control Panel and Homer integration admin 2017-08-17 42925
71 Where to check OpenSIPS does not start? admin 2014-03-09 42943
70 MediaProxy wiki page install configuration admin 2014-08-11 43058
69 SIPSorcery admin 2014-03-18 43956
68 The FreeRADIUS Project admin 2011-12-14 44050
67 Open Source VOIP applications, both clients and servers. admin 2013-11-20 44185
66 opensips 1.11.2 install guide good 인스톨 가이드 admin 2014-08-09 44482
65 How to install OpenSIPS on CentOS Debian etc admin 2014-03-05 44853
64 Using TLS in OpenSIPS v2.2.x admin 2017-09-14 44998
63 Jitsi Videobridge meets WebRTC admin 2014-10-18 45029
62 OpenSIPS command line tricks admin 2017-09-13 45190
61 The SIP Router Project admin 2013-04-06 45241
60 Opensips TM module enables stateful processing of SIP transactions admin 2014-10-04 45359
59 the OpenSIPS Project OpenSIP admin 2011-12-14 45535
58 How to install OpenSIPS on CentOS debian module add xcap admin 2014-03-06 45815
57 Asterisk Installation Asterisk Realtime configuration admin 2013-04-06 45976
56 OpenSIPS routing logic admin 2017-12-12 46613
55 Using TLS in OpenSIPS v2.2.x configuration admin 2017-09-04 47302
54 OpenSIPS Installation Notes admin 2014-08-09 47471
53 Problem with presence_xml module Opensips 1.9 admin 2014-03-06 47810
52 Many OPENSIPS Configuration Examples This will Help you admin 2014-08-23 49009