Re: [Ekiga-list] Coexistence of ekiga with an ATA

[ael <law_ence dev ntlworld com>]

ael wrote:
> Damien Sandras wrote:

>>>
>>>Ekiga makes the STUN checks at startup as described above?
>>>
>>
>>
>>It does.
>>
>>However, if STUN detects "Partially blocked NAT", it is because the
>>forwarded ports on the router do not correspond to the ports used by
>>Ekiga.
>>
>>Make sure the forwarding is correct.
>>Make sure the ATA is not using the same port range.
> 
> 
> Thanks Damien. I thought that I had things set up properly, but I will
> recheck. My situation is a slightly more complex than I reported ( I
> wanted to present the essence for simplicity and clarity). The ATA
> incorporates a router, NAT and so forth. And then feeds the main router.

I have done some experimenting with ekiga with debugging, but have not
got much further. {Apologies for wrap-around from this mailer in the
debug messages below.}

2007/01/04 22:56:58.748   0:05.734                        ekiga Set TCP
port range to 30000:30010
2007/01/04 22:56:58.798   0:05.792                        ekiga Set RTP
port range to 5010:5059
2007/01/04 22:56:58.863   0:05.849                        ekiga Set UDP
port range to 5062:5100

The above look ok. My main router has no logged any relevant blocked
packets. The ATA only exposes its SIP (set to 5060) and RTP (set to
5004) ports. I am now wondering about 30000:30010...

The "magic" manipulation of the Network setting was logged as

2007/01/04 22:57:41.372   0:48.346        GMStunClient:0853daa0 OPAL
STUN server "stun.ekiga.net" replies Cone NAT, external IP 86.3.137.146

A failed call without that "magic" has debug entries like:

------------------------------------------------------------------------
2007/01/04 23:12:12.923   1:13.466        GMURLHandler:084b7e38 PCSS
Outgoing call routed to sip:500 ekiga net for Call[1]-EP<pc>[Default]
2007/01/04 23:12:12.925   1:13.474        GMURLHandler:084b7e38 SIP
SetUpConnection: <sip:500 ekiga net>
2007/01/04 23:12:22.969   1:23.512        GMURLHandler:084b7e38 OpalUDP
Started connect to 86.64.162.35:5060
2007/01/04 23:12:22.994   1:23.537        GMURLHandler:084b7e38 RTP
STUN could not create RTP/RTCP socket pair; trying to create RTP socket
anyway.
2007/01/04 23:12:22.996   1:23.539        GMURLHandler:084b7e38 RTP
STUN could not create RTP socket either.
2007/01/04 23:12:22.997   1:23.541        GMURLHandler:084b7e38 RTP
STUN could not create RTP/RTCP socket pair; trying to create RTP socket
anyway.

[.. snip..]

2007/01/04 23:12:23.380   1:23.934        GMURLHandler:084b7e38 RTP
STUN could not create RTP socket either.
2007/01/04 23:12:23.433   1:23.988        GMURLHandler:084b7e38 RTP
STUN could not create RTP/RTCP socket pair; trying to create RTP socket
anyway.
2007/01/04 23:12:23.508   1:24.063        GMURLHandler:084b7e38 RTP
STUN could not create RTP socket either.
2007/01/04 23:12:23.562   1:24.116            OnRelease:8528118 OpalCon
Media stream threads closed.
2007/01/04 23:12:23.613   1:24.156        SIP Transport:8527db0 OpalUDP
Error on connection read select.
2007/01/04 23:12:23.619   1:24.163        SIP Transport:8527db0 SIP
Read thread finished.
2007/01/04 23:12:23.626   1:24.180            OnRelease:8528118 OpalCon
Media stream threads closed.
2007/01/04 23:12:23.682   1:24.237        GMURLHandler:084b7e38 RTP
STUN could not create RTP/RTCP socket pair; trying to create RTP socket
anyway.

[..snip..]

2007/01/04 23:12:25.713   1:26.267        GMURLHandler:084b7e38 RTP
STUN could not create RTP socket either.
2007/01/04 23:12:25.767   1:26.322        GMURLHandler:084b7e38 SIP
No authentication information present
2007/01/04 23:12:25.832   1:26.386        GMURLHandler:084b7e38 SIP
Did not start INVITE transaction on
udp$86.64.162.35:5060<if=udp$192.168.0.3:5071>
2007/01/04 23:12:25.909   1:26.463        GMURLHandler:084b7e38 SIP
Could not write to sip:500 ekiga net -
2007/01/04 23:12:25.962   1:26.524        GMURLHandler:084b7e38
SetUpCall succeeded
2007/01/04 23:12:26.013   1:26.567            OnRelease:852cd30 OpalCon
Media stream threads closed.

---------------------------------------------------------------------------------

I am not sure if the above messages suggest blocked ports: I guess that
fits the failure to create the sockets. Since they are RTP sockets and
those are open, I am not clear what is happening.

I can live with the present situation, but would like to understand what
is failing. But it is not urgent.

A E Lawrence