[sip-comm-dev] Jingle Nodes Relay


#1

Hi Thiago, Sebastian,

Now i'm successfully using the JN Relay using Openfire updated to latest Beta 3.7, i can see it has been used successfully in the log file, i can successfully make calls and video calls with 2 NAT, one Symmetric NAT and one side Port Restricted Cone NAT, the problem i still cannot solve is no 2 NAT both Port Restricted Cone NAT, in this case the result is that the Caller party still ringing and the Callee party enter in Connected state, or both Caller and Callee are in Ringing mode even the call has been accepted by the callee. I'm not using any other stun server rather the SC one.
Could you please have a look at the logs to find out any possible reason ?

Thanks
Fabio

log.zip (44.8 KB)


#2

Hi Fabio,

Can you tell me if your Openfire is running in a Public IP?
Do you see any warnings in the Openfire Jingle Nodes Admin page?

Thiago Rocha Camargo
barata7@gmail.com
http://jinglenodes.org
My profiles: [image: Twitter] <http://twitter.com/xmppjingle>
Contact me: [image: Google Talk/] barata7@gmail.com
Signature powered by
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
WiseStamp<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>

···

On Thu, Dec 23, 2010 at 2:35 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Thiago, Sebastian,

Now i'm successfully using the JN Relay using Openfire updated to latest
Beta 3.7, i can see it has been used successfully in the log file, i can
successfully make calls and video calls with 2 NAT, one Symmetric NAT and
one side Port Restricted Cone NAT, the problem i still cannot solve is no
2 NAT both Port Restricted Cone NAT, in this case the result is that the
Caller party still ringing and the Callee party enter in Connected state,
or both Caller and Callee are in Ringing mode even the call has been
accepted by the callee. I'm not using any other stun server rather the SC
one.
Could you please have a look at the logs to find out any possible reason ?

Thanks
Fabio

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Hi Thiago,

yes it is running on public IP, but i see this message in attach, if you or anybody want to test the JN relay server the address is jn.telme.sg and it is open to public,
You can see in the log file i sent before the relay IP is 74.81.175.107

Thanks for the help
Fabio

···

Il giorno 23/dic/2010, alle ore 14.41, thiagoc ha scritto:

Hi Fabio,

Can you tell me if your Openfire is running in a Public IP?
Do you see any warnings in the Openfire Jingle Nodes Admin page?

Thiago Rocha Camargo
barata7@gmail.com
http://jinglenodes.org
My profiles:
Contact me: barata7@gmail.com
Signature powered by WiseStamp

On Thu, Dec 23, 2010 at 2:35 PM, Fabio Telme <fabio@telme.sg> wrote:
Hi Thiago, Sebastian,

Now i'm successfully using the JN Relay using Openfire updated to latest Beta 3.7, i can see it has been used successfully in the log file, i can successfully make calls and video calls with 2 NAT, one Symmetric NAT and one side Port Restricted Cone NAT, the problem i still cannot solve is no 2 NAT both Port Restricted Cone NAT, in this case the result is that the Caller party still ringing and the Callee party enter in Connected state, or both Caller and Callee are in Ringing mode even the call has been accepted by the callee. I'm not using any other stun server rather the SC one.
Could you please have a look at the logs to find out any possible reason ?

Thanks
Fabio

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#4

Which machine are you running windows or Linux?

Thiago Rocha Camargo
barata7@gmail.com
http://jinglenodes.org
My profiles: [image: Twitter] <http://twitter.com/xmppjingle>
Contact me: [image: Google Talk/] barata7@gmail.com
Signature powered by
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
WiseStamp<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>

···

On Thu, Dec 23, 2010 at 2:49 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Thiago,

yes it is running on public IP, but i see this message in attach, if you
or anybody want to test the JN relay server the address is jn.telme.sgand it is open to public,
You can see in the log file i sent before the relay IP is 74.81.175.107

Thanks for the help
Fabio

Il giorno 23/dic/2010, alle ore 14.41, thiagoc ha scritto:

Hi Fabio,

Can you tell me if your Openfire is running in a Public IP?
Do you see any warnings in the Openfire Jingle Nodes Admin page?

Thiago Rocha Camargo
barata7@gmail.com
http://jinglenodes.org
My profiles: [image: Twitter] <http://twitter.com/xmppjingle>
Contact me: [image: Google Talk/] barata7@gmail.com
Signature powered by
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
WiseStamp<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>

On Thu, Dec 23, 2010 at 2:35 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Thiago, Sebastian,

Now i'm successfully using the JN Relay using Openfire updated to latest
Beta 3.7, i can see it has been used successfully in the log file, i can
successfully make calls and video calls with 2 NAT, one Symmetric NAT and
one side Port Restricted Cone NAT, the problem i still cannot solve is no
2 NAT both Port Restricted Cone NAT, in this case the result is that the
Caller party still ringing and the Callee party enter in Connected state,
or both Caller and Callee are in Ringing mode even the call has been
accepted by the callee. I'm not using any other stun server rather the SC
one.
Could you please have a look at the logs to find out any possible reason ?

Thanks
Fabio

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#5

Hi

CentOS 5.x there are 2 IP 74.81.175.106 and 74.81.175.107

regards
Fabio

···

Il giorno 23/dic/2010, alle ore 14.50, thiagoc ha scritto:

Which machine are you running windows or Linux?

Thiago Rocha Camargo
barata7@gmail.com
http://jinglenodes.org
My profiles:
Contact me: barata7@gmail.com
Signature powered by WiseStamp

On Thu, Dec 23, 2010 at 2:49 PM, Fabio Telme <fabio@telme.sg> wrote:
Hi Thiago,

yes it is running on public IP, but i see this message in attach, if you or anybody want to test the JN relay server the address is jn.telme.sg and it is open to public,
You can see in the log file i sent before the relay IP is 74.81.175.107

Thanks for the help
Fabio

Il giorno 23/dic/2010, alle ore 14.41, thiagoc ha scritto:

Hi Fabio,

Can you tell me if your Openfire is running in a Public IP?
Do you see any warnings in the Openfire Jingle Nodes Admin page?

Thiago Rocha Camargo
barata7@gmail.com
http://jinglenodes.org
My profiles:
Contact me: barata7@gmail.com
Signature powered by WiseStamp

On Thu, Dec 23, 2010 at 2:35 PM, Fabio Telme <fabio@telme.sg> wrote:
Hi Thiago, Sebastian,

Now i'm successfully using the JN Relay using Openfire updated to latest Beta 3.7, i can see it has been used successfully in the log file, i can successfully make calls and video calls with 2 NAT, one Symmetric NAT and one side Port Restricted Cone NAT, the problem i still cannot solve is no 2 NAT both Port Restricted Cone NAT, in this case the result is that the Caller party still ringing and the Callee party enter in Connected state, or both Caller and Callee are in Ringing mode even the call has been accepted by the callee. I'm not using any other stun server rather the SC one.
Could you please have a look at the logs to find out any possible reason ?

Thanks
Fabio

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#6

Fabio,

Can you tell me if you opened your firewall on port range 20000 to 60000 UDP
for IN/OUT traffic?

CHeers,


#7

Hi Thiago

yes for testing purpose i disabled the firewall at all :slight_smile:

···

Il giorno 23/dic/2010, alle ore 14.52, thiagoc ha scritto:

Fabio,

Can you tell me if you opened your firewall on port range 20000 to 60000 UDP for IN/OUT traffic?

CHeers,

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#8

Hi Thiago,

i also still receioving this kind of error : Call ended by remote side. Reason: failed-application. Error: Could not establish connection (ICE failed)

Fabio

···

Il giorno 23/dic/2010, alle ore 14.52, thiagoc ha scritto:

Fabio,

Can you tell me if you opened your firewall on port range 20000 to 60000 UDP for IN/OUT traffic?

CHeers,

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#9

Which version of the plugin are you using?
Did you download it from where?

Thiago Rocha Camargo
barata7@gmail.com
http://jinglenodes.org
My profiles: [image: Twitter] <http://twitter.com/xmppjingle>
Contact me: [image: Google Talk/] barata7@gmail.com
Signature powered by
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
WiseStamp<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>

···

On Thu, Dec 23, 2010 at 2:57 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Thiago

yes for testing purpose i disabled the firewall at all :slight_smile:

Il giorno 23/dic/2010, alle ore 14.52, thiagoc ha scritto:

> Fabio,
>
> Can you tell me if you opened your firewall on port range 20000 to 60000
UDP for IN/OUT traffic?
>
> CHeers,

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#10

Drop me an email with your Jabber ID

Thiago Rocha Camargo
barata7@gmail.com
http://jinglenodes.org
My profiles: [image: Twitter] <http://twitter.com/xmppjingle>
Contact me: [image: Google Talk/] barata7@gmail.com
Signature powered by
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
WiseStamp<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>

···

On Thu, Dec 23, 2010 at 2:58 PM, thiagoc <barata7@gmail.com> wrote:

Which version of the plugin are you using?
Did you download it from where?

Thiago Rocha Camargo
barata7@gmail.com
http://jinglenodes.org
My profiles: [image: Twitter] <http://twitter.com/xmppjingle>
Contact me: [image: Google Talk/] barata7@gmail.com
Signature powered by
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
WiseStamp<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>

On Thu, Dec 23, 2010 at 2:57 PM, Fabio Telme <fabio@telme.sg> wrote:

Hi Thiago

yes for testing purpose i disabled the firewall at all :slight_smile:

Il giorno 23/dic/2010, alle ore 14.52, thiagoc ha scritto:

> Fabio,
>
> Can you tell me if you opened your firewall on port range 20000 to 60000
UDP for IN/OUT traffic?
>
> CHeers,

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#11

Hi

i downloaded from the official repositary http://code.google.com/p/jinglenodes/downloads/detail?name=jingleNodes.jar&can=2&q=

Fabio

···

Il giorno 23/dic/2010, alle ore 14.58, thiagoc ha scritto:

Which version of the plugin are you using?
Did you download it from where?

Thiago Rocha Camargo
barata7@gmail.com
http://jinglenodes.org
My profiles:
Contact me: barata7@gmail.com
Signature powered by WiseStamp

On Thu, Dec 23, 2010 at 2:57 PM, Fabio Telme <fabio@telme.sg> wrote:
Hi Thiago

yes for testing purpose i disabled the firewall at all :slight_smile:

Il giorno 23/dic/2010, alle ore 14.52, thiagoc ha scritto:

> Fabio,
>
> Can you tell me if you opened your firewall on port range 20000 to 60000 UDP for IN/OUT traffic?
>
> CHeers,

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#12

Hi

I have reason to think that the SC Stun server is not working properly for the Restricted Cone Nat, after i change it to "stun.xten.net" all problems are solved,
i don't have this error anymore , the Binding request is successfull

  15:18:30.741 INFO: org.ice4j.ice.ConnectivityCheckClient.startCheckForPair() Failed to send BINDING-REQUEST(0x1)[attrib.count=6 len=84 tranID=0xD46598132D012264575059A7] through /fe80:0:0:0:fa1e:dfff:fe94:7b59%9:5023
java.io.IOException: No route to host

Regards
Fabio

···

Il giorno 23/dic/2010, alle ore 14.58, thiagoc ha scritto:

Which version of the plugin are you using?
Did you download it from where?

Thiago Rocha Camargo
barata7@gmail.com
http://jinglenodes.org
My profiles:
Contact me: barata7@gmail.com
Signature powered by WiseStamp

On Thu, Dec 23, 2010 at 2:57 PM, Fabio Telme <fabio@telme.sg> wrote:
Hi Thiago

yes for testing purpose i disabled the firewall at all :slight_smile:

Il giorno 23/dic/2010, alle ore 14.52, thiagoc ha scritto:

> Fabio,
>
> Can you tell me if you opened your firewall on port range 20000 to 60000 UDP for IN/OUT traffic?
>
> CHeers,

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#13

Fabio,

На 23.12.10 18:04, Fabio Telme написа:

Hi

I have reason to think that the SC Stun server is not working properly

Interesting. From what I saw in your logs from yesterday you were not
using SC's stun server at all and the one that you were using was not
responding. From the logs you sent today you seemed to be using SC's
STUN sever again and you were getting the proper responses.

for the Restricted Cone Nat, after i change it to "stun.xten.net
<http://stun.xten.net>" all probley ms are solved,
i don't have this error anymore , the Binding request is successfull

  15:18:30.741 INFO:
org.ice4j.ice.ConnectivityCheckClient.startCheckForPair() Failed to send
BINDING-REQUEST(0x1)[attrib.count=6 len=84
tranID=0xD46598132D012264575059A7] through
/fe80:0:0:0:fa1e:dfff:fe94:7b59%9:5023
java.io.IOException: No route to host

The log entry you see happens during the connectivity checks. It
concerns your link-local IPv6 addresses which have little to do with STUN.

Hope this helps,
Emil

···

Regards
Fabio

Il giorno 23/dic/2010, alle ore 14.58, thiagoc ha scritto:

Which version of the plugin are you using?
Did you download it from where?

Thiago Rocha Camargo
barata7@gmail.com <mailto:barata7@gmail.com>
http://jinglenodes.org <http://jinglenodes.org/>
My profiles: Twitter <http://twitter.com/xmppjingle>
Contact me: Google Talk/ barata7@gmail.com <mailto:barata7@gmail.com>
Signature powered by
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>WiseStamp
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>

On Thu, Dec 23, 2010 at 2:57 PM, Fabio Telme <fabio@telme.sg >> <mailto:fabio@telme.sg>> wrote:

    Hi Thiago

    yes for testing purpose i disabled the firewall at all :slight_smile:

    Il giorno 23/dic/2010, alle ore 14.52, thiagoc ha scritto:

    > Fabio,
    >
    > Can you tell me if you opened your firewall on port range 20000
    to 60000 UDP for IN/OUT traffic?
    >
    > CHeers,

    ---------------------------------------------------------------------
    To unsubscribe, e-mail:
    dev-unsubscribe@sip-communicator.dev.java.net
    <mailto:dev-unsubscribe@sip-communicator.dev.java.net>
    For additional commands, e-mail:
    dev-help@sip-communicator.dev.java.net
    <mailto:dev-help@sip-communicator.dev.java.net>

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#14

Hi,

I'm continuing my test on the NAT performance of the Jingle Nodes Relay
solution and i notice that after some of successfull calls, something
happen to the SC that it require a reboot to work again, here is part of
the log that shows some problem on the PortAudio, i've also attached the
log of the calls, on the initial part of the file you can see the
successfull calls and on the latest part the failed calls.

Hope it can help to find a solution to this stability issue

Regards
Fabio Galdi

net.java.sip.communicator.service.protocol.OperationFailedException: Could
not establish connection (ICE failed)
  at
net.java.sip.communicator.impl.protocol.jabber.IceUdpTransportManager.wrapupConnectivityEstablishment(IceUdpTransportManager.java:940)
  at
net.java.sip.communicator.impl.protocol.jabber.CallPeerJabberImpl.answer(CallPeerJabberImpl.java:253)
  at
net.java.sip.communicator.impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl.answerCallPeer(OperationSetBasicTelephonyJabberImpl.java:427)
  at
net.java.sip.communicator.impl.gui.main.call.CallManager$AnswerCallThread.run(CallManager.java:1123)
21:38:17.878 GRAVE:
impl.neomedia.notify.PortAudioClipImpl.runOnceInPlayThread().317 Failed to
open PortAudioRenderer.
javax.media.ResourceUnavailableException: Device unavailable
  at
net.java.sip.communicator.impl.neomedia.jmfext.media.renderer.audio.PortAudioRenderer.open(PortAudioRenderer.java:405)
  at
net.java.sip.communicator.impl.neomedia.notify.PortAudioClipImpl.runOnceInPlayThread(PortAudioClipImpl.java:283)

Fabio,

На 23.12.10 18:04, Fabio Telme написа:

Hi

I have reason to think that the SC Stun server is not working properly

Interesting. From what I saw in your logs from yesterday you were not
using SC's stun server at all and the one that you were using was not
responding. From the logs you sent today you seemed to be using SC's
STUN sever again and you were getting the proper responses.

for the Restricted Cone Nat, after i change it to "stun.xten.net
<http://stun.xten.net>" all probley ms are solved,
i don't have this error anymore , the Binding request is successfull

  15:18:30.741 INFO:
org.ice4j.ice.ConnectivityCheckClient.startCheckForPair() Failed to

send

BINDING-REQUEST(0x1)[attrib.count=6 len=84
tranID=0xD46598132D012264575059A7] through
/fe80:0:0:0:fa1e:dfff:fe94:7b59%9:5023
java.io.IOException: No route to host

The log entry you see happens during the connectivity checks. It
concerns your link-local IPv6 addresses which have little to do with

STUN.

Hope this helps,
Emil

Regards
Fabio

Which version of the plugin are you using?
Did you download it from where?

Thiago Rocha Camargo
barata7@gmail.com <mailto:barata7@gmail.com>
http://jinglenodes.org <http://jinglenodes.org/>
My profiles: Twitter <http://twitter.com/xmppjingle>
Contact me: Google Talk/ barata7@gmail.com <mailto:barata7@gmail.com>
Signature powered by

<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>WiseStamp

<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>

Log-KO.rar (116 KB)

···

On Thu, 23 Dec 2010 18:14:50 +0200, Emil Ivov <emcho@sip-communicator.org> wrote:

Il giorno 23/dic/2010, alle ore 14.58, thiagoc ha scritto:

On Thu, Dec 23, 2010 at 2:57 PM, Fabio Telme <fabio@telme.sg >>> <mailto:fabio@telme.sg>> wrote:

    Hi Thiago

    yes for testing purpose i disabled the firewall at all :slight_smile:

    Il giorno 23/dic/2010, alle ore 14.52, thiagoc ha scritto:

    > Fabio,
    >
    > Can you tell me if you opened your firewall on port range 20000
    to 60000 UDP for IN/OUT traffic?
    >
    > CHeers,

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

    To unsubscribe, e-mail:
    dev-unsubscribe@sip-communicator.dev.java.net
    <mailto:dev-unsubscribe@sip-communicator.dev.java.net>
    For additional commands, e-mail:
    dev-help@sip-communicator.dev.java.net
    <mailto:dev-help@sip-communicator.dev.java.net>


#15

Hi

here another error generated after a call is not hung up properly, on
some calls one of the party hung-up , the windows are closed but the audio
is still received from the caller, and then is not possible to place any
more calls, because of this error : it looks like the address and ports
are still in use

at
net.java.sip.communicator.impl.gui.main.call.CallManager$CreateCallThread.run(CallManager.java:905)
22:34:22.007 INFO:
org.ice4j.ice.harvest.HostCandidateHarvester.createDatagramSocket()
Retrying a bind because of a failure to bind to address
/2001:0:5ef5:79fd:2832:c64:68bc:da5 and port 5006 (Address already in use:
Cannot bind)
22:34:22.007 INFO:
org.ice4j.ice.harvest.HostCandidateHarvester.createDatagramSocket()
java.net.BindException: Address already in use: Cannot bind

Hope it can help to improve the Jingle capability of SC

Fabio

Hi,

I'm continuing my test on the NAT performance of the Jingle Nodes Relay
solution and i notice that after some of successfull calls, something
happen to the SC that it require a reboot to work again, here is part

of

the log that shows some problem on the PortAudio, i've also attached the
log of the calls, on the initial part of the file you can see the
successfull calls and on the latest part the failed calls.

Hope it can help to find a solution to this stability issue

Regards
Fabio Galdi

net.java.sip.communicator.service.protocol.OperationFailedException:

Could

not establish connection (ICE failed)
  at

net.java.sip.communicator.impl.protocol.jabber.IceUdpTransportManager.wrapupConnectivityEstablishment(IceUdpTransportManager.java:940)

  at

net.java.sip.communicator.impl.protocol.jabber.CallPeerJabberImpl.answer(CallPeerJabberImpl.java:253)

  at

net.java.sip.communicator.impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl.answerCallPeer(OperationSetBasicTelephonyJabberImpl.java:427)

  at

net.java.sip.communicator.impl.gui.main.call.CallManager$AnswerCallThread.run(CallManager.java:1123)

21:38:17.878 GRAVE:
impl.neomedia.notify.PortAudioClipImpl.runOnceInPlayThread().317 Failed

to

open PortAudioRenderer.
javax.media.ResourceUnavailableException: Device unavailable
  at

net.java.sip.communicator.impl.neomedia.jmfext.media.renderer.audio.PortAudioRenderer.open(PortAudioRenderer.java:405)

  at

net.java.sip.communicator.impl.neomedia.notify.PortAudioClipImpl.runOnceInPlayThread(PortAudioClipImpl.java:283)

Fabio,

На 23.12.10 18:04, Fabio Telme написа:

Hi

I have reason to think that the SC Stun server is not working properly

Interesting. From what I saw in your logs from yesterday you were not
using SC's stun server at all and the one that you were using was not
responding. From the logs you sent today you seemed to be using SC's
STUN sever again and you were getting the proper responses.

for the Restricted Cone Nat, after i change it to "stun.xten.net
<http://stun.xten.net>" all probley ms are solved,
i don't have this error anymore , the Binding request is successfull

  15:18:30.741 INFO:
org.ice4j.ice.ConnectivityCheckClient.startCheckForPair() Failed to

send

BINDING-REQUEST(0x1)[attrib.count=6 len=84
tranID=0xD46598132D012264575059A7] through
/fe80:0:0:0:fa1e:dfff:fe94:7b59%9:5023
java.io.IOException: No route to host

The log entry you see happens during the connectivity checks. It
concerns your link-local IPv6 addresses which have little to do with

STUN.

Hope this helps,
Emil

Regards
Fabio

Which version of the plugin are you using?
Did you download it from where?

Thiago Rocha Camargo
barata7@gmail.com <mailto:barata7@gmail.com>
http://jinglenodes.org <http://jinglenodes.org/>
My profiles: Twitter <http://twitter.com/xmppjingle>
Contact me: Google Talk/ barata7@gmail.com <mailto:barata7@gmail.com>
Signature powered by

<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>WiseStamp

<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>

···

On Thu, 23 Dec 2010 21:19:40 +0000, <fabio@telme.sg> wrote:

On Thu, 23 Dec 2010 18:14:50 +0200, Emil Ivov <emcho@sip-communicator.org> > wrote:

Il giorno 23/dic/2010, alle ore 14.58, thiagoc ha scritto:

On Thu, Dec 23, 2010 at 2:57 PM, Fabio Telme <fabio@telme.sg >>>> <mailto:fabio@telme.sg>> wrote:

    Hi Thiago

    yes for testing purpose i disabled the firewall at all :slight_smile:

    Il giorno 23/dic/2010, alle ore 14.52, thiagoc ha scritto:

    > Fabio,
    >
    > Can you tell me if you opened your firewall on port range 20000
    to 60000 UDP for IN/OUT traffic?
    >
    > CHeers,

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

    To unsubscribe, e-mail:
    dev-unsubscribe@sip-communicator.dev.java.net
    <mailto:dev-unsubscribe@sip-communicator.dev.java.net>
    For additional commands, e-mail:
    dev-help@sip-communicator.dev.java.net
    <mailto:dev-help@sip-communicator.dev.java.net>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#16

Hi Fabio,

maybe I'vemissed it, but which OS do you use? If on Linux
then make sure you use the correct ALSA device setup. The
output device should be "dmix" or any other device that
supports output mixing. If you use the HW devices then it
may happen, that devices are blocked for some time (this
also depends on the HW and the ALSA driver for your HW).

Regards,
Werner

···

Am 23.12.2010 22:19, schrieb fabio@telme.sg:

Hi,

I'm continuing my test on the NAT performance of the Jingle Nodes Relay
solution and i notice that after some of successfull calls, something
happen to the SC that it require a reboot to work again, here is part of
the log that shows some problem on the PortAudio, i've also attached the
log of the calls, on the initial part of the file you can see the
successfull calls and on the latest part the failed calls.

Hope it can help to find a solution to this stability issue

Regards
Fabio Galdi

net.java.sip.communicator.service.protocol.OperationFailedException: Could
not establish connection (ICE failed)
  at
net.java.sip.communicator.impl.protocol.jabber.IceUdpTransportManager.wrapupConnectivityEstablishment(IceUdpTransportManager.java:940)
  at
net.java.sip.communicator.impl.protocol.jabber.CallPeerJabberImpl.answer(CallPeerJabberImpl.java:253)
  at
net.java.sip.communicator.impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl.answerCallPeer(OperationSetBasicTelephonyJabberImpl.java:427)
  at
net.java.sip.communicator.impl.gui.main.call.CallManager$AnswerCallThread.run(CallManager.java:1123)
21:38:17.878 GRAVE:
impl.neomedia.notify.PortAudioClipImpl.runOnceInPlayThread().317 Failed to
open PortAudioRenderer.
javax.media.ResourceUnavailableException: Device unavailable
  at
net.java.sip.communicator.impl.neomedia.jmfext.media.renderer.audio.PortAudioRenderer.open(PortAudioRenderer.java:405)
  at
net.java.sip.communicator.impl.neomedia.notify.PortAudioClipImpl.runOnceInPlayThread(PortAudioClipImpl.java:283)

On Thu, 23 Dec 2010 18:14:50 +0200, Emil Ivov <emcho@sip-communicator.org> > wrote:

Fabio,

На 23.12.10 18:04, Fabio Telme написа:

Hi

I have reason to think that the SC Stun server is not working properly

Interesting. From what I saw in your logs from yesterday you were not
using SC's stun server at all and the one that you were using was not
responding. From the logs you sent today you seemed to be using SC's
STUN sever again and you were getting the proper responses.

for the Restricted Cone Nat, after i change it to "stun.xten.net
<http://stun.xten.net>" all probley ms are solved,
i don't have this error anymore , the Binding request is successfull

  15:18:30.741 INFO:
org.ice4j.ice.ConnectivityCheckClient.startCheckForPair() Failed to

send

BINDING-REQUEST(0x1)[attrib.count=6 len=84
tranID=0xD46598132D012264575059A7] through
/fe80:0:0:0:fa1e:dfff:fe94:7b59%9:5023
java.io.IOException: No route to host

The log entry you see happens during the connectivity checks. It
concerns your link-local IPv6 addresses which have little to do with

STUN.

Hope this helps,
Emil

Regards
Fabio

Il giorno 23/dic/2010, alle ore 14.58, thiagoc ha scritto:

Which version of the plugin are you using?
Did you download it from where?

Thiago Rocha Camargo
barata7@gmail.com <mailto:barata7@gmail.com>
http://jinglenodes.org <http://jinglenodes.org/>
My profiles: Twitter <http://twitter.com/xmppjingle>
Contact me: Google Talk/ barata7@gmail.com <mailto:barata7@gmail.com>
Signature powered by

<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>WiseStamp

<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>

On Thu, Dec 23, 2010 at 2:57 PM, Fabio Telme <fabio@telme.sg >>>> <mailto:fabio@telme.sg>> wrote:

    Hi Thiago

    yes for testing purpose i disabled the firewall at all :slight_smile:

    Il giorno 23/dic/2010, alle ore 14.52, thiagoc ha scritto:

    > Fabio,
    >
    > Can you tell me if you opened your firewall on port range 20000
    to 60000 UDP for IN/OUT traffic?
    >
    > CHeers,

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

    To unsubscribe, e-mail:
    dev-unsubscribe@sip-communicator.dev.java.net
    <mailto:dev-unsubscribe@sip-communicator.dev.java.net>
    For additional commands, e-mail:
    dev-help@sip-communicator.dev.java.net
    <mailto:dev-help@sip-communicator.dev.java.net>

>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#17

Hi Werner,

The problem happens both on MAC and Windows, and after many tests i can see that it stop works after some other events that are not related to ICE or Jingle, in fact i've already produced some logs that shows different kind of failure, for example one of the most frequent failure is that after a call the Disconnection is not successful and the Client continue receiving the audio stream even if the call window is already closed, then also the webcam is still ON, after this event if i try a new call the Calls fail for the error "Address Already in Use". Another event regard the PortAudio, that also fail with error "
     GRAVE:

impl.neomedia.notify.PortAudioClipImpl.runOnceInPlayThread().317 Failed to
open PortAudioRenderer.
javax.media.ResourceUnavailableException: Device unavailable

So i belive that the calls that in Jingle works on and off are related to some other issues happened during the previous successful calls.

Regards
Fabio

···

Il giorno 24/dic/2010, alle ore 08.47, Werner Dittmann ha scritto:

Hi Fabio,

maybe I'vemissed it, but which OS do you use? If on Linux
then make sure you use the correct ALSA device setup. The
output device should be "dmix" or any other device that
supports output mixing. If you use the HW devices then it
may happen, that devices are blocked for some time (this
also depends on the HW and the ALSA driver for your HW).

Regards,
Werner

Am 23.12.2010 22:19, schrieb fabio@telme.sg:

Hi,

I'm continuing my test on the NAT performance of the Jingle Nodes Relay
solution and i notice that after some of successfull calls, something
happen to the SC that it require a reboot to work again, here is part of
the log that shows some problem on the PortAudio, i've also attached the
log of the calls, on the initial part of the file you can see the
successfull calls and on the latest part the failed calls.

Hope it can help to find a solution to this stability issue

Regards
Fabio Galdi

net.java.sip.communicator.service.protocol.OperationFailedException: Could
not establish connection (ICE failed)
  at
net.java.sip.communicator.impl.protocol.jabber.IceUdpTransportManager.wrapupConnectivityEstablishment(IceUdpTransportManager.java:940)
  at
net.java.sip.communicator.impl.protocol.jabber.CallPeerJabberImpl.answer(CallPeerJabberImpl.java:253)
  at
net.java.sip.communicator.impl.protocol.jabber.OperationSetBasicTelephonyJabberImpl.answerCallPeer(OperationSetBasicTelephonyJabberImpl.java:427)
  at
net.java.sip.communicator.impl.gui.main.call.CallManager$AnswerCallThread.run(CallManager.java:1123)
21:38:17.878 GRAVE:
impl.neomedia.notify.PortAudioClipImpl.runOnceInPlayThread().317 Failed to
open PortAudioRenderer.
javax.media.ResourceUnavailableException: Device unavailable
  at
net.java.sip.communicator.impl.neomedia.jmfext.media.renderer.audio.PortAudioRenderer.open(PortAudioRenderer.java:405)
  at
net.java.sip.communicator.impl.neomedia.notify.PortAudioClipImpl.runOnceInPlayThread(PortAudioClipImpl.java:283)

On Thu, 23 Dec 2010 18:14:50 +0200, Emil Ivov <emcho@sip-communicator.org> >> wrote:

Fabio,

На 23.12.10 18:04, Fabio Telme написа:

Hi

I have reason to think that the SC Stun server is not working properly

Interesting. From what I saw in your logs from yesterday you were not
using SC's stun server at all and the one that you were using was not
responding. From the logs you sent today you seemed to be using SC's
STUN sever again and you were getting the proper responses.

for the Restricted Cone Nat, after i change it to "stun.xten.net
<http://stun.xten.net>" all probley ms are solved,
i don't have this error anymore , the Binding request is successfull

15:18:30.741 INFO:
org.ice4j.ice.ConnectivityCheckClient.startCheckForPair() Failed to

send

BINDING-REQUEST(0x1)[attrib.count=6 len=84
tranID=0xD46598132D012264575059A7] through
/fe80:0:0:0:fa1e:dfff:fe94:7b59%9:5023
java.io.IOException: No route to host

The log entry you see happens during the connectivity checks. It
concerns your link-local IPv6 addresses which have little to do with

STUN.

Hope this helps,
Emil

Regards
Fabio

Il giorno 23/dic/2010, alle ore 14.58, thiagoc ha scritto:

Which version of the plugin are you using?
Did you download it from where?

Thiago Rocha Camargo
barata7@gmail.com <mailto:barata7@gmail.com>
http://jinglenodes.org <http://jinglenodes.org/>
My profiles: Twitter <http://twitter.com/xmppjingle>
Contact me: Google Talk/ barata7@gmail.com <mailto:barata7@gmail.com>
Signature powered by

<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>WiseStamp

<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>

On Thu, Dec 23, 2010 at 2:57 PM, Fabio Telme <fabio@telme.sg >>>>> <mailto:fabio@telme.sg>> wrote:

   Hi Thiago

   yes for testing purpose i disabled the firewall at all :slight_smile:

   Il giorno 23/dic/2010, alle ore 14.52, thiagoc ha scritto:

Fabio,

Can you tell me if you opened your firewall on port range 20000

   to 60000 UDP for IN/OUT traffic?

CHeers,

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

   To unsubscribe, e-mail:
   dev-unsubscribe@sip-communicator.dev.java.net
   <mailto:dev-unsubscribe@sip-communicator.dev.java.net>
   For additional commands, e-mail:
   dev-help@sip-communicator.dev.java.net
   <mailto:dev-help@sip-communicator.dev.java.net>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net