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 
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
