Difference between revisions of "Talk:Jingle/test"

From JaWiki (Jabber/XMPP wiki)
Jump to: navigation, search
(log)
 
(STUN)
Line 1: Line 1:
−
=== STD out psi media 0.14 (FreeBSD) + psi media 0.14 (Ubuntu) ==
+
=== STD out psi media 0.14 (FreeBSD) + psi media 0.14 (Ubuntu) ===
 
Без STUN, на одной стороне NAT
 
Без STUN, на одной стороне NAT
  
Line 134: Line 134:
  
 
=== STUN ===
 
=== STUN ===
 +
Все то же самое, но со STUN.
 +
 
На стороне клиента с NAT прописан stun.iptel.org
 
На стороне клиента с NAT прописан stun.iptel.org
 +
 +
Он рабочий. Проверил его
 +
stun_client stun.xten.com
 +
STUN client version 0.96
 +
Primary: Indepndent Mapping, Port Dependent Filter, preserves ports, no hairpin
 +
Return value is 0x000017
 +
 +
Но все равно соединение не удается установить. Видно что nat пробрасывает пакеты, но почему-то при этом не подменяет своим адресом (?)
 +
 +
tcpdump -n -i re0 "udp and (src 79.104.207.182 or dst 79.104.207.182)"
 +
<PRE>
 +
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
 +
listening on re0, link-type EN10MB (Ethernet), capture size 96 bytes
 +
13:46:56.043772 IP 192.168.5.11.8010 > 79.104.207.182.8010: UDP, length 92
 +
13:46:56.043997 IP 192.168.5.11.8011 > 79.104.207.182.8011: UDP, length 92
 +
13:46:56.044221 IP 192.168.5.11.8010 > 79.104.207.182.8010: UDP, length 92
 +
13:46:56.044429 IP 192.168.5.11.8010 > 79.104.207.182.8010: UDP, length 92
 +
13:46:56.044640 IP 192.168.5.11.8010 > 79.104.207.182.8010: UDP, length 92
 +
13:46:56.044837 IP 192.168.5.11.8011 > 79.104.207.182.8011: UDP, length 92
 +
13:46:56.045039 IP 192.168.5.11.8011 > 79.104.207.182.8011: UDP, length 92
 +
13:46:56.045254 IP 192.168.5.11.8011 > 79.104.207.182.8011: UDP, length 92
 +
13:46:56.115508 IP 79.104.207.182.8011 > 192.168.5.11.8011: UDP, length 64
 +
13:46:56.116626 IP 79.104.207.182.8011 > 192.168.5.11.8011: UDP, length 64
 +
13:46:56.117875 IP 79.104.207.182.8011 > 192.168.5.11.8011: UDP, length 64
 +
13:46:56.118992 IP 79.104.207.182.8011 > 192.168.5.11.8011: UDP, length 64
 +
13:46:56.120242 IP 79.104.207.182.8010 > 192.168.5.11.8010: UDP, length 64
 +
13:46:56.121741 IP 79.104.207.182.8010 > 192.168.5.11.8010: UDP, length 64
 +
13:46:56.122868 IP 79.104.207.182.8010 > 192.168.5.11.8010: UDP, length 64
 +
13:46:56.124113 IP 79.104.207.182.8010 > 192.168.5.11.8010: UDP, length 64
 +
13:46:56.523891 IP 79.104.207.182.8010 > 192.168.5.11.8010: UDP, length 88
 +
13:46:56.524301 IP 192.168.5.11.8010 > 79.104.207.182.8010: UDP, length 64
 +
13:46:56.525635 IP 79.104.207.182.8010 > 192.168.5.11.8010: UDP, length 88
 +
13:46:56.525872 IP 192.168.5.11.8010 > 79.104.207.182.8010: UDP, length 64
 +
13:46:56.528900 IP 79.104.207.182.8011 > 192.168.5.11.8011: UDP, length 88
 +
13:46:56.529523 IP 192.168.5.11.8011 > 79.104.207.182.8011: UDP, length 64
 +
13:46:56.530504 IP 79.104.207.182.8011 > 192.168.5.11.8011: UDP, length 88
 +
</PRE>

Revision as of 10:58, 29 June 2011

STD out psi media 0.14 (FreeBSD) + psi media 0.14 (Ubuntu)

Без STUN, на одной стороне NAT 

send clock is master
state changed
sendbin:
  apprtpsink4
  audioencbin:
    rtpspeexpay5
    speexenc5
    capsfilter9
    audioresample10
    audioconvert10
  volume5
%using speexdsp
Readying AudioIn:[oss,/dev/dsp0.0], refs=1
codec=speex
rate=16000,width=16,channels=1
changing state...
send clock is master
state changed
sendbin:
  apprtpsink5
  audioencbin:
    rtpspeexpay6
    speexenc6
    capsfilter11
    audioresample12
    audioconvert12
  volume6
queue5
bin5:
  capsfilter10
  audioresample11
  audioconvert11
  osssrc15
tee5
speexdsp5
rtppay caps audio: [application/x-rtp, media=(string)audio, clock-rate=(int)16000, encoding-name=(string)SPEEX, encoding-params=(string)1, payload=(int)110, ssrc=(uint)2180135228, clock-base=(uint)3949246459, seqnum-base=(uint)16483]
rtp_started
there are audio payload types
types=1
resolver finished
starting ice for audio
starting transport 192.168.5.11:8010 for component 1
starting transport 192.168.5.11:8011 for component 2
lt_started
lt_started
ice_started
after_ice_started
local candidate ready
flushing local candidates
incoming request: [transport-info]
audio candidates=4
adding 4 remote candidates
4 pairs
1, 192.168.5.11:8010 -> 79.104.207.182:8010
2, 192.168.5.11:8011 -> 79.104.207.182:8011
1, 192.168.5.11:8010 -> 79.104.207.182:8010
2, 192.168.5.11:8011 -> 79.104.207.182:8011
4 after pruning
connectivity check from 192.168.5.11:8010 to 79.104.207.182:8010
connectivity check from 192.168.5.11:8011 to 79.104.207.182:8011
connectivity check from 192.168.5.11:8010 to 79.104.207.182:8010
connectivity check from 192.168.5.11:8011 to 79.104.207.182:8011
received validated response
check success
received validated response
check success
received validated response
check success
component 1 already active, not signalling
connectivity check from 192.168.5.11:8011 to 79.104.207.182:8011
received validated response
check success
component 2 already active, not signalling
audio: average packet size=82, kbps=41
incoming request: [session-terminate]
cleaning up...
Releasing AudioIn:[oss,/dev/dsp0.0], refs=0
cleaning done.

Вторая сторона 

incoming request: [transport-info]
audio candidates=2
adding 2 remote candidates
4 pairs
1, 79.104.207.182:8010 -> 192.168.5.11:8010
2, 79.104.207.182:8011 -> 192.168.5.11:8011
1, 79.104.207.182:8010 -> 192.168.5.11:8010
2, 79.104.207.182:8011 -> 192.168.5.11:8011
4 after pruning
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011
using speexdsp
Readying AudioIn:[alsa,default], refs=1
codec=speex
rate=16000,width=16,channels=1
received validated request or indication
received validated request or indication
received validated request or indication
received validated request or indication
changing state...
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011
received validated request or indication
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011
error/timeout while setting send pipeline to PLAYING
cleaning up...
Releasing AudioIn:[alsa,default], refs=0
cleaning done.
cleaning up...
cleaning done.
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011
connectivity check from 79.104.207.182:8010 to 192.168.5.11:8010
connectivity check from 79.104.207.182:8011 to 192.168.5.11:8011

STUN

Все то же самое, но со STUN.

На стороне клиента с NAT прописан stun.iptel.org

Он рабочий. Проверил его 

stun_client stun.xten.com
STUN client version 0.96
Primary: Indepndent Mapping, Port Dependent Filter, preserves ports, no hairpin 
Return value is 0x000017

Но все равно соединение не удается установить. Видно что nat пробрасывает пакеты, но почему-то при этом не подменяет своим адресом (?) 

tcpdump -n -i re0 "udp and (src 79.104.207.182 or dst 79.104.207.182)"

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on re0, link-type EN10MB (Ethernet), capture size 96 bytes
13:46:56.043772 IP 192.168.5.11.8010 > 79.104.207.182.8010: UDP, length 92
13:46:56.043997 IP 192.168.5.11.8011 > 79.104.207.182.8011: UDP, length 92
13:46:56.044221 IP 192.168.5.11.8010 > 79.104.207.182.8010: UDP, length 92
13:46:56.044429 IP 192.168.5.11.8010 > 79.104.207.182.8010: UDP, length 92
13:46:56.044640 IP 192.168.5.11.8010 > 79.104.207.182.8010: UDP, length 92
13:46:56.044837 IP 192.168.5.11.8011 > 79.104.207.182.8011: UDP, length 92
13:46:56.045039 IP 192.168.5.11.8011 > 79.104.207.182.8011: UDP, length 92
13:46:56.045254 IP 192.168.5.11.8011 > 79.104.207.182.8011: UDP, length 92
13:46:56.115508 IP 79.104.207.182.8011 > 192.168.5.11.8011: UDP, length 64
13:46:56.116626 IP 79.104.207.182.8011 > 192.168.5.11.8011: UDP, length 64
13:46:56.117875 IP 79.104.207.182.8011 > 192.168.5.11.8011: UDP, length 64
13:46:56.118992 IP 79.104.207.182.8011 > 192.168.5.11.8011: UDP, length 64
13:46:56.120242 IP 79.104.207.182.8010 > 192.168.5.11.8010: UDP, length 64
13:46:56.121741 IP 79.104.207.182.8010 > 192.168.5.11.8010: UDP, length 64
13:46:56.122868 IP 79.104.207.182.8010 > 192.168.5.11.8010: UDP, length 64
13:46:56.124113 IP 79.104.207.182.8010 > 192.168.5.11.8010: UDP, length 64
13:46:56.523891 IP 79.104.207.182.8010 > 192.168.5.11.8010: UDP, length 88
13:46:56.524301 IP 192.168.5.11.8010 > 79.104.207.182.8010: UDP, length 64
13:46:56.525635 IP 79.104.207.182.8010 > 192.168.5.11.8010: UDP, length 88
13:46:56.525872 IP 192.168.5.11.8010 > 79.104.207.182.8010: UDP, length 64
13:46:56.528900 IP 79.104.207.182.8011 > 192.168.5.11.8011: UDP, length 88
13:46:56.529523 IP 192.168.5.11.8011 > 79.104.207.182.8011: UDP, length 64
13:46:56.530504 IP 79.104.207.182.8011 > 192.168.5.11.8011: UDP, length 88
Retrieved from "http://wiki.jrudevels.org/index.php?title=Talk:Jingle/test&oldid=13964"