Strange STUN behavior seems to be the last barrier before achieving the first milestone.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

I am trying to establish a sip call over UMTS (3G) and couldn't get
along with it.
Looking at the log showed me  that the client did not get any response
from the stun server.

Other clients, behind other NATs are able to call when using the same
STUN server.
I've tried it all using few public STUN servers and got the same results.

I am dumping the lines from the log which seems to be relevant to the issue.

 08:28:23.000 sip_endpoint.c  Module "mod-pjsua-log" registered
 08:28:23.000   pjsua_core.c  Nameserver 208.67.222.222 added
 08:28:23.000 sip_endpoint.c  Module "mod-tsx-layer" registered
 08:28:23.000 sip_endpoint.c  Module "mod-stateful-util" registered
 08:28:23.000 sip_endpoint.c  Module "mod-ua" registered
 08:28:23.000 sip_endpoint.c  Module "mod-100rel" registered
 08:28:23.000 sip_endpoint.c  Module "mod-pjsua" registered
 08:28:23.000 sip_endpoint.c  Module "mod-invite" registered
 08:28:23.000   pjsua_core.c  STUN server stun.xten.com resolved,
address is 75.101.138.128:3478
 08:28:23.000      pasound.c  PortAudio sound library initialized, status=0
 08:28:23.000      pasound.c  PortAudio host api count=2
 08:28:23.000      pasound.c  Sound device count=5
 08:28:23.000          pjlib  select() I/O Queue created (002639C4)
 08:28:23.000  speex_codec.c  Adjusting quality to 5 for uwb
 08:28:23.000  pjsua_media.c  pjmedia_codec_speex_init
 08:28:23.000   conference.c  Creating conference bridge with 254 ports
 08:28:23.000   conference.c  Sound device successfully created for port 0
 08:28:23.000  natck0026DD80  Local address is 0.0.0.0:1146
 08:28:23.000  natck0026DD80  Server set to 75.101.138.128:3478
 08:28:23.000  natck0026DD80  Performing Test I: Binding request to
75.101.138.128:3478
 08:28:23.000  natck0026DD80  TX 28 bytes STUN message to 75.101.138.128:3478:
--- begin STUN message ---
STUN Binding request
 Hdr: length=8, magic=11a95549, tsx_id=73267e830ffb599800000000
 Attributes:
  CHANGE-REQUEST: length=4, value=0 (0x0)
--- end of STUN message ---

 08:28:23.000 stuntsx00289B0  STUN client transaction created
 08:28:23.000 stuntsx00289B0  STUN sending message (transmit count=1)
 08:28:23.000 sip_endpoint.c  Module "mod-evsub" registered
 08:28:23.000 sip_endpoint.c  Module "mod-presence" registered
 08:28:23.000        evsub.c  Event pkg "presence" registered by mod-presence
 08:28:23.000 sip_endpoint.c  Module "mod-refer" registered
 08:28:23.000        evsub.c  Event pkg "refer" registered by mod-refer
 08:28:23.000 sip_endpoint.c  Module "mod-pjsua-pres" registered
 08:28:23.000 sip_endpoint.c  Module "mod-pjsua-im" registered
 08:28:23.000 sip_endpoint.c  Module "mod-pjsua-options" registered
 08:28:23.000   pjsua_core.c  1 SIP worker threads created
 08:28:23.000   pjsua_core.c  pjsua version 0.9.0-trunk for
win32-wince initialized
 08:28:24.000  natck0026DD80  Performing Test II: Binding request with
change address and port request to 75.101.138.128:3478
 08:28:24.000  natck0026DD80  TX 28 bytes STUN message to 75.101.138.128:3478:
--- begin STUN message ---
STUN Binding request
 Hdr: length=8, magic=00294823, tsx_id=18be67844ae13d6c00000001
 Attributes:
  CHANGE-REQUEST: length=4, value=6 (0x6)
--- end of STUN message ---

 08:28:24.000 stuntsx0028C46  STUN client transaction created
 08:28:24.000 stuntsx0028C46  STUN sending message (transmit count=1)
 08:28:24.000 stuntsx00289B0  STUN sending message (transmit count=2)
 08:28:25.000  natck0026DD80  Performing Test III: Binding request
with change port request to 75.101.138.128:3478
 08:28:25.000  natck0026DD80  TX 28 bytes STUN message to 75.101.138.128:3478:
--- begin STUN message ---
STUN Binding request
 Hdr: length=8, magic=2cd672ae, tsx_id=69525f9016496df100000002
 Attributes:
  CHANGE-REQUEST: length=4, value=2 (0x2)
--- end of STUN message ---

 08:28:25.000 stuntsx0028CC6  STUN client transaction created
 08:28:25.000 stuntsx0028CC6  STUN sending message (transmit count=1)
 08:28:25.000 stuntsx0028C46  STUN sending message (transmit count=2)
 08:28:25.000 stuntsx00289B0  STUN sending message (transmit count=3)
 08:28:26.000 stuntsx0028CC6  STUN sending message (transmit count=2)
 08:28:26.000 stuntsx0028C46  STUN sending message (transmit count=3)
 08:28:26.000 stuntsx00289B0  STUN sending message (transmit count=4)
 08:28:27.000 stuntsx0028CC6  STUN sending message (transmit count=3)
 08:28:27.000 stuntsx0028C46  STUN sending message (transmit count=4)
 08:28:27.000 stuntsx00289B0  STUN sending message (transmit count=5)
 08:28:27.000   pjsua_core.c  Error contacting STUN server: Received
no response from STUN server (PJLIB_UTIL_ESTUNNOTRESPOND)
[status=320010]
 08:28:28.000 stuntsx0028CC6  STUN sending message (transmit count=4)
 08:28:28.000 stuntsx0028C46  STUN sending message (transmit count=5)
 08:28:29.000 stuntsx00289B0  STUN sending message (transmit count=6)
 08:28:29.000 stuntsx0028CC6  STUN sending message (transmit count=5)
 08:28:30.000 stuntsx0028C46  STUN sending message (transmit count=6)



[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux