Hi, Tito!

The 2.2 version already has WS client support. This means that the Proxy can connect to a WebSocket client. However, this is not fully correct, since a Proxy should never connect to a WebSocket client. Therefore your scenario should also work with 2.1, with a correct configuration.

I will shortly take a look on your traces and let you know my ideas.

Best regards,

Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com

On 06/05/2015 01:26 AM, Tito Cumpen wrote:
Razvan,


I'd like to correct my statement about this working in 2.1. It is actually working in 2.2. Here is the output of my opensips -V.

flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT

ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535

poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.

git revision: b7db080

main.c compiled on 22:15:49 Jun  4 2015 with gcc 4.8.3



Here the acks and byes sent from webrtc client work without a problem. Perhaps ws is not fully supported in 2.1?





On Thu, Jun 4, 2015 at 12:32 PM, Tito Cumpen <[email protected] <mailto:[email protected]>> wrote:

    Razvan,


    I think it didn't meet the size requirements when I attached it.
    Here is the dropbox link to the tar file containing the traces and
    logs.

    https://www.dropbox.com/s/3v7p42sxbvf2wv9/2.1issues.tar?dl=0

    On Thu, Jun 4, 2015 at 3:19 AM, Răzvan Crainea
    <[email protected] <mailto:[email protected]>> wrote:

        Hi, Tito!

        I can't find the traces anywhere. Can you post them on pastebin?

        Best regards,

        Răzvan Crainea
        OpenSIPS Solutions
        www.opensips-solutions.com  <http://www.opensips-solutions.com>

        On 06/03/2015 07:45 PM, Tito Cumpen wrote:
        The traces include the last 2000 lines of the opensips log.

        On Wed, Jun 3, 2015 at 12:44 PM, Tito Cumpen <[email protected]
        <mailto:[email protected]>> wrote:

            Razvan,


            I have attached two traces. The first call opensips
            doesn't transmit the bye sent from the ws UAS. The second
            call is initiated from the ws uac and answered by the sip
            tcp UAS. The ack from the ws uac is not sent back to the
            sip tcp side and so the call is hung up . Th with the
            last 2000 lines of opensips log running at level 3.

            On Wed, Jun 3, 2015 at 10:31 AM, Tito Cumpen
            <[email protected] <mailto:[email protected]>> wrote:

                Razvan,

                The ack is sourcing from the ws party to the b side
                which is registered via tcp. Note this is also
                occurring when a bye is sent from the ws side to the
                sip tcp b client. Meaning OpenSIPS drops of and
                throws the aforementioned error.  I will get a trace
                as soon as I can.

                Thanks,
                Tito

                Hi, Tito!

                I'm not sure why the proxy is trying to send the ACK
                over WS, since the R-URI contains a TCP connection.
                Can you send a full pcap trace for the call?

                Best regards,

                Răzvan Crainea
                OpenSIPS Solutions
                www.opensips-solutions.com  <http://www.opensips-solutions.com>

                On 06/03/2015 01:55 AM, Tito Cumpen wrote:
                Group,


                I checked out opensips 2.1  branch today as I had
                been running a trunk version from about a month ago.
                Now I am seeing issues transmitting acks and byes to
                the remote side when they source from a webrtc
                client. Opensips is displaying this statement in the
                logs.

                ERROR:proto_ws:proto_ws_send: no open tcp connection
                found. WebSocket connect is not supported!

                Jun 2 22:47:44/sbin/opensips[10323]:
                ERROR:tm:msg_send: send() for proto 5 failed

                Jun 2 22:47:44  /sbin/opensips[10323]:
                ERROR:tm:t_forward_nonack: sending request failed



                Here is an ack that fails,



                ACK
                sip:[email protected]:49819;transport=tcp
                
<mailto:sip:[email protected]:49819;transport=tcp>
                SIP/2.0

                Via: SIP/2.0/WS
                192.237.160.129:8080;branch=z9hG4bK1941.ac1ea01.3;i=11

                Via: SIP/2.0/WS
                
df7jal23ls0d.invalid;received=68.195.115.219;branch=z9hG4bKDkzZdVkwTIfn7Q6BMh0h;rport=62612

                From:
                "tito"<sip:[email protected]
                
<mailto:sip%[email protected]>>;tag=E6xwQCRGTOBxlP5EaIxL

                To: <sip:[email protected]
                
<mailto:sip%[email protected]>>;tag=k1GPy4-

                Contact:
                
"tito"<sip:[email protected];rtcweb-breaker=yes;click2call=no;transport=ws>
                
<mailto:sip:[email protected];rtcweb-breaker=yes;click2call=no;transport=ws>;+g.oma.sip-im;language="en,fr"

                Call-ID: bc03514a-10fd-b1ee-9b92-ca6046c3474f

                CSeq: 44222 ACK

                Content-Length: 0

                Max-Forwards: 69

                Proxy-Authorization: Digest
                username="[email protected]
                
<mailto:[email protected]>",realm="nurseliveconnect.org
                
<http://nurseliveconnect.org>",nonce="556e3411000001e8de622139149f48392dc597150508b7df",uri="sip:[email protected]:49819;transport=tcp"
                
<mailto:sip:[email protected]:49819;transport=tcp>,response="326e78b8a9de4423c3a7f5d3ecaadf84",algorithm=MD5

                Route:
                
<sip:192.237.160.129:8080;transport=ws;r2=on;lr;ftag=E6xwQCRGTOBxlP5EaIxL;did=795.654b3927>

                Route:
                
<sip:192.237.160.129;transport=tcp;r2=on;lr;ftag=E6xwQCRGTOBxlP5EaIxL;did=795.654b3927>

                User-Agent: IM-client/OMA1.0 sipML5-v1.2015.03.18

                Organization: Doubango Telecom


                .

                Jun 2 22:53:44 cloud-server-09
                /sbin/opensips[10323]: DBG:core:forward_request:
                orig. len=1174, new_len=1208, proto=5

                Jun 2 22:53:44 cloud-server-09
                /sbin/opensips[10323]: ERROR:proto_ws:proto_ws_send:
                no open tcp connection found. WebSocket connect is
                not supported!

                Jun 2 22:53:44 cloud-server-09
                /sbin/opensips[10323]: ERROR:core:msg_send: send()
                for proto 5 failed


                Please advise.





                _______________________________________________
                Users mailing list
                [email protected]  <mailto:[email protected]>
                http://lists.opensips.org/cgi-bin/mailman/listinfo/users


                _______________________________________________
                Users mailing list
                [email protected]
                <mailto:[email protected]>
                http://lists.opensips.org/cgi-bin/mailman/listinfo/users





        _______________________________________________
        Users mailing list
        [email protected]  <mailto:[email protected]>
        http://lists.opensips.org/cgi-bin/mailman/listinfo/users


        _______________________________________________
        Users mailing list
        [email protected] <mailto:[email protected]>
        http://lists.opensips.org/cgi-bin/mailman/listinfo/users





_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to