Using RFC5766 turn server / No Audio in both end

134 views
Skip to first unread message

Ron Menez

unread,
Nov 23, 2015, 3:44:50 AM11/23/15
to TURN Server (Open-Source project)
Hi,

Does anyone configured RFC5766 turn server using X-Lite (TURN) and Zoiper (STUN) as client? We are trying to create a complete SIP solution. The SIP registration and Call establishment are successful. But no media are being received in both ends. Below are the logs from the turn server:

Nov 23 08:19:40 ip-172-31-22-178 turnserver: 220: user <>: incoming packet message processed, error 401

Nov 23 08:19:40 ip-172-31-22-178 turnserver: 220: user <>: incoming packet message processed, error 401

Nov 23 08:19:40 ip-172-31-22-178 turnserver: 220: user <>: incoming packet message processed, error 401

Nov 23 08:19:40 ip-172-31-22-178 turnserver: 220: IPv4. Server relay addr: 172.31.22.178:0

Nov 23 08:19:40 ip-172-31-22-178 turnserver: 220: IPv4. Local relay addr: 172.31.22.178:52376

Nov 23 08:19:40 ip-172-31-22-178 turnserver: 220: new: session id=000000000000000007, username=<user>, lifetime=600

Nov 23 08:19:40 ip-172-31-22-178 turnserver: 220: user <user>: incoming packet ALLOCATE processed, success

Nov 23 08:19:40 ip-172-31-22-178 turnserver: 221: user <user>: incoming packet ALLOCATE processed, success

Nov 23 08:19:40 ip-172-31-22-178 turnserver: 221: user <user>: incoming packet ALLOCATE processed, success

Nov 23 08:19:40 ip-172-31-22-178 turnserver: 221: handle_udp_packet: New UDP endpoint: local addr 172.31.22.178:3478, remote addr 119.93.11.60:26001

Nov 23 08:19:40 ip-172-31-22-178 turnserver: 221: user <>: incoming packet message processed, error 401

Nov 23 08:19:41 ip-172-31-22-178 turnserver: 221: user <>: incoming packet message processed, error 401

Nov 23 08:19:41 ip-172-31-22-178 turnserver: 221: user <>: incoming packet message processed, error 401

Nov 23 08:19:41 ip-172-31-22-178 turnserver: 221: new: session id=000000000000000008, username=<user>, lifetime=600

Nov 23 08:19:41 ip-172-31-22-178 turnserver: 221: user <user>: incoming packet ALLOCATE processed, success

Nov 23 08:19:41 ip-172-31-22-178 turnserver: 221: user <user>: incoming packet ALLOCATE processed, success

Nov 23 08:19:41 ip-172-31-22-178 turnserver: 222: user <user>: incoming packet ALLOCATE processed, success

Nov 23 08:19:43 ip-172-31-22-178 turnserver: 224: user <user>: incoming packet CHANNEL_BIND processed, success

Nov 23 08:19:43 ip-172-31-22-178 turnserver: 224: user <user>: incoming packet CHANNEL_BIND processed, success

Nov 23 08:19:43 ip-172-31-22-178 turnserver: 224: user <user>: incoming packet CHANNEL_BIND processed, success

Nov 23 08:19:43 ip-172-31-22-178 turnserver: 224: user <user>: incoming packet CHANNEL_BIND processed, success

Nov 23 08:20:13 ip-172-31-22-178 turnserver: 253: refreshed: session id=000000000000000007, username=<user>, lifetime=0

Nov 23 08:20:13 ip-172-31-22-178 turnserver: 253: user <user>: incoming packet REFRESH processed, success

Nov 23 08:20:14 ip-172-31-22-178 turnserver: 254: TURN connection closed (non-mobile pattern), user <user>

Nov 23 08:26:52 ip-172-31-22-178 turnserver: 652: TURN connection closed (non-mobile pattern), user <user>

Nov 23 08:26:52 ip-172-31-22-178 turnserver: 652: delete: session id=000000000000000004, username=<user>

Nov 23 08:29:41 ip-172-31-22-178 turnserver: 821: TURN connection closed (non-mobile pattern), user <user>

Nov 23 08:29:41 ip-172-31-22-178 turnserver: 821: delete: session id=000000000000000008, username=<user>


Also attached the trace taken from the turn server while doing the call.


Hoping for your expert advice.


BR,


Ron

RFC5766_x-lite_zoiper.pcap

Oleg Moskalenko

unread,
Nov 23, 2015, 4:40:50 AM11/23/15
to Ron Menez, TURN Server (Open-Source project)
The pcap file looks great, everything is going on well.

But take a look at the last 4 packets in pcap (36th second). The TURN
client sends "refresh" message with lifetime 0. It means that the
clients force the server to close the sessions. The clients decided
that they do not need the TURN session anymore.
> --
> You received this message because you are subscribed to the Google Groups
> "TURN Server (Open-Source project)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
> turn-server-project-rfc57...@googlegroups.com.
> To post to this group, send email to
> turn-server-project...@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/turn-server-project-rfc5766-turn-server.
> For more options, visit https://groups.google.com/d/optout.

Ron Menez

unread,
Nov 23, 2015, 4:48:00 AM11/23/15
to TURN Server (Open-Source project), ron....@entropysolution.com
Thanks Oleg.

The "refresh" was a manual termination of the session. 

So this means that the turn server is working just fine? 

Still stock in this issue. No media in both sides.

Does anyone tried using X-Lite (TURN) and Zoiper (STUN) as client?

BR,

Ron
> To post to this group, send email to

Oleg Moskalenko

unread,
Nov 23, 2015, 4:57:57 AM11/23/15
to Ron Menez, TURN Server (Open-Source project)
as far I see, nothing is wrong.

Check the firewall settings and other network configurations.


On Mon, Nov 23, 2015 at 1:48 AM, Ron Menez
>> > turn-server-project-rfc57...@googlegroups.com.
>> > To post to this group, send email to
>> > turn-server-project...@googlegroups.com.
>> > Visit this group at
>> > http://groups.google.com/group/turn-server-project-rfc5766-turn-server.
>> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "TURN Server (Open-Source project)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
> turn-server-project-rfc57...@googlegroups.com.
> To post to this group, send email to
> turn-server-project...@googlegroups.com.

Ron Menez

unread,
Nov 23, 2015, 5:19:57 AM11/23/15
to Oleg Moskalenko, TURN Server (Open-Source project)
Thanks Oleg.

We'll check on those.

BR,
Ron

Ron Menez

unread,
Nov 24, 2015, 3:47:43 AM11/24/15
to TURN Server (Open-Source project), mom0...@gmail.com
Hi Oleg,

Quick question. While taking another trace while doing a call, we found out that the TURN server was sending ICMP (ping) to one of the clients. Is this a normal behaviour of the RFC5766 turn server? Does this have an impact for the media concern?

Attached is the said trace.

BR,
Ron

>> > To post to this group, send email to

>> > Visit this group at
>> > http://groups.google.com/group/turn-server-project-rfc5766-turn-server.
>> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "TURN Server (Open-Source project)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to

> To post to this group, send email to
rons-mbp.zyxel.com11242015-143205 (YAHOO).pcap

Oleg Moskalenko

unread,
Nov 24, 2015, 3:50:37 AM11/24/15
to Ron Menez, TURN Server (Open-Source project)
I guess you got something wrong. TURN server never uses ping or ICMP
directly. The TCP/IP stack of the server system may send ICMP messages
because of some errors. That is a normal situation.
>> >> > turn-server-project-rfc57...@googlegroups.com.
>> >> > To post to this group, send email to
>> >> > turn-server-project...@googlegroups.com.
>> >> > Visit this group at
>> >> >
>> >> > http://groups.google.com/group/turn-server-project-rfc5766-turn-server.
>> >> > For more options, visit https://groups.google.com/d/optout.
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "TURN Server (Open-Source project)" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> > an
>> > email to
>> > turn-server-project-rfc57...@googlegroups.com.
>> > To post to this group, send email to
>> > turn-server-project...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages