Me
Moderator Registered 12 years 57 days
Claudio Andrade (innovaphone) Thursday, 4 May 2017, 11:16 AM in response to Mario 2388
Re: Stun /turn liefert interne IP
Hi Mario,

Sorry the late reply,

The messages bellow are not relevant, this is part of the redundancy of messages that are sent to the TURN server from the client.

0: 2674: 621: 6 - ICE.0: TURN Allocate result Unauthorized: re-authorizing
0: 2674: 621: 7 - ICE.0: TURN Allocate req after Unauthorized
0: 2674: 622: 0 - ICE.0: TURN Allocate result parsing error

In this log seams that the client correctly obtained all his candidates:

--------------------------------
0:2674:605:1 - ICE.0: Initialized local candidates RTP(192.168.1.40:16400) RTCP(192.168.1.40:16401) T38(192.168.1.40:0)
CANDIDATES:LOCAL,count(3),fingerprint(5b1d772148e2724b199d8ffd3703b30e3335bf79e13e1709fc604c4ddce21fc6),usr(npQO),pwd(OVmw4Ks9uGBiJJgfmb+tgJ)
:HOST addr([192.168.1.40]:16400/16401) prio(2130569471/2130569726)
:SRFLX addr([77.239.63.126]:62586/60736) related([192.168.1.40]:16400/16401) prio(1693124351/1693124606)
:RELAY addr([192.168.33.41]:16402/16403) related([192.168.1.40]:16400/16401) prio(16683263/16683518)
-------------------------------

The TURN Server always provide his own IP, since it's on a private machine behind a NAT router we see the private IP on the candidates (what's correct and works).

Why the ICE fails it's not clear on this trace, to find out it's necessary to have trace from both endpoints envolved with the H.323 ICE trace flag and all TCP/UDP traffic so we could check each test that was made.

Important that the other endpoint involved also provided all his candidates.
← You can define your color theme preference here