[sip-comm-dev] Jingle ICE "Failed-Application" Error


#1

Hi,

After i upgrade the latest build 3189 all the Jingle calls fail with ICE Error Reason "Failed-Application" now is 100% of the calls, before the patch some calls was successful about 30%. The patch on my own build improve it but not solve the issue at all. It is possible to understand from the Log how the error is caused ? i'm testing now with 2 NAT box, both on Port Restricted Con NAT other tests with 2 symmetric NAT gives the same problem.
Calls are from a MAC release to a Win7

Regards
Fabio Galdi

log.zip (22.5 KB)


#2

Hey Fabio,

На 23.12.10 03:01, Fabio Telme написа:

Hi,

After i upgrade the latest build 3189 all the Jingle calls fail
with ICE Error Reason "Failed-Application" now is 100% of the
calls, before the patch some calls was successful about 30%. The
patch on my own build improve it but not solve the issue at all. It
is possible to understand from the Log how the error is caused ?

It seems from your logs that the STUN server you are using is not
replying to your binding requests. Make sure you have it properly setup.
Otherwise you can just remove it and let SIP Communicator use its
default fallback STUN server.

i'm
testing now with 2 NAT box, both on Port Restricted Con NAT other
tests with 2 symmetric NAT gives the same problem.

Establishing sessions between clients located behind NATs with endpoint
dependent mapping is only possible if you are using a TURN server or a
Jingle Nodes relay.

Cheers,
Emil

Calls are from a
MAC release to a Win7

Regards Fabio Galdi

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

To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net

···

For additional commands, e-mail:
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


#3

Hi Emil,

Thanks for the explanation, actually i tried to setup a Jingle Nodes relay using "Openfire" but the Jingle Nodes plugin jar fail to be imported, so i'm tring to understand how to fix it. Any suggestion on how to implement a Jingle Node Relay ?
Apologize for the stupid question, but SC should be able to find other Jingle Nodes and use it for relay ? in this case for Jingle nodes are we considering the other SC client in your Roster contact list ?

Thanks for the explanation.

Regards
Fabio Galdi

···

Il giorno 23/dic/2010, alle ore 10.15, Emil Ivov ha scritto:

Hey Fabio,

На 23.12.10 03:01, Fabio Telme написа:

Hi,

After i upgrade the latest build 3189 all the Jingle calls fail
with ICE Error Reason "Failed-Application" now is 100% of the
calls, before the patch some calls was successful about 30%. The
patch on my own build improve it but not solve the issue at all. It
is possible to understand from the Log how the error is caused ?

It seems from your logs that the STUN server you are using is not
replying to your binding requests. Make sure you have it properly setup.
Otherwise you can just remove it and let SIP Communicator use its
default fallback STUN server.

i'm
testing now with 2 NAT box, both on Port Restricted Con NAT other
tests with 2 symmetric NAT gives the same problem.

Establishing sessions between clients located behind NATs with endpoint
dependent mapping is only possible if you are using a TURN server or a
Jingle Nodes relay.

Cheers,
Emil

Calls are from a
MAC release to a Win7

Regards Fabio Galdi

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

To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net

For additional commands, e-mail:
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

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


#4

Hi Fabio,

Which Openfire Version are you trying to use?

SIP Comm should be able to discover Nodes from Server and Contact List.

Regards,

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 10:43 AM, Fabio Telme <fabio@telme.sg> wrote:

Hi Emil,

Thanks for the explanation, actually i tried to setup a Jingle Nodes relay
using "Openfire" but the Jingle Nodes plugin jar fail to be imported, so
i'm tring to understand how to fix it. Any suggestion on how to implement a
Jingle Node Relay ?
Apologize for the stupid question, but SC should be able to find other
Jingle Nodes and use it for relay ? in this case for Jingle nodes are we
considering the other SC client in your Roster contact list ?

Thanks for the explanation.

Regards
Fabio Galdi

Il giorno 23/dic/2010, alle ore 10.15, Emil Ivov ha scritto:

> Hey Fabio,
>
> На 23.12.10 03:01, Fabio Telme написа:
>> Hi,
>>
>> After i upgrade the latest build 3189 all the Jingle calls fail
>> with ICE Error Reason "Failed-Application" now is 100% of the
>> calls, before the patch some calls was successful about 30%. The
>> patch on my own build improve it but not solve the issue at all. It
>> is possible to understand from the Log how the error is caused ?
>
> It seems from your logs that the STUN server you are using is not
> replying to your binding requests. Make sure you have it properly setup.
> Otherwise you can just remove it and let SIP Communicator use its
> default fallback STUN server.
>
>> i'm
>> testing now with 2 NAT box, both on Port Restricted Con NAT other
>> tests with 2 symmetric NAT gives the same problem.
>
> Establishing sessions between clients located behind NATs with endpoint
> dependent mapping is only possible if you are using a TURN server or a
> Jingle Nodes relay.
>
> Cheers,
> Emil
>
>
>> Calls are from a
>> MAC release to a Win7
>
>
>>
>> Regards Fabio Galdi
>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>>
>>
> To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
>> For additional commands, e-mail:
>> 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
>

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

the version i use is Openfire, Version: 3.6.4 , the pluging is present on the server i can see the folder and the file uploaded, but in the list of plugins it is not showed up, so i'm not sure is working or not. Any suggestion ?

Thanks
Fabio

···

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

Hi Fabio,

Which Openfire Version are you trying to use?

SIP Comm should be able to discover Nodes from Server and Contact List.

Regards,

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 10:43 AM, Fabio Telme <fabio@telme.sg> wrote:
Hi Emil,

Thanks for the explanation, actually i tried to setup a Jingle Nodes relay using "Openfire" but the Jingle Nodes plugin jar fail to be imported, so i'm tring to understand how to fix it. Any suggestion on how to implement a Jingle Node Relay ?
Apologize for the stupid question, but SC should be able to find other Jingle Nodes and use it for relay ? in this case for Jingle nodes are we considering the other SC client in your Roster contact list ?

Thanks for the explanation.

Regards
Fabio Galdi

Il giorno 23/dic/2010, alle ore 10.15, Emil Ivov ha scritto:

> Hey Fabio,
>
> На 23.12.10 03:01, Fabio Telme написа:
>> Hi,
>>
>> After i upgrade the latest build 3189 all the Jingle calls fail
>> with ICE Error Reason "Failed-Application" now is 100% of the
>> calls, before the patch some calls was successful about 30%. The
>> patch on my own build improve it but not solve the issue at all. It
>> is possible to understand from the Log how the error is caused ?
>
> It seems from your logs that the STUN server you are using is not
> replying to your binding requests. Make sure you have it properly setup.
> Otherwise you can just remove it and let SIP Communicator use its
> default fallback STUN server.
>
>> i'm
>> testing now with 2 NAT box, both on Port Restricted Con NAT other
>> tests with 2 symmetric NAT gives the same problem.
>
> Establishing sessions between clients located behind NATs with endpoint
> dependent mapping is only possible if you are using a TURN server or a
> Jingle Nodes relay.
>
> Cheers,
> Emil
>
>
>> Calls are from a
>> MAC release to a Win7
>
>
>>
>> Regards Fabio Galdi
>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>>
>>
> To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
>> For additional commands, e-mail:
>> 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
>

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


#6

Hi Fabio,

Try with Latest Openfire Version. If possible I would even recommend
building from source and SVN.

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 10:51 AM, Fabio Telme <fabio@telme.sg> wrote:

Hi Thiago,

the version i use is Openfire, Version: 3.6.4 , the pluging is present on
the server i can see the folder and the file uploaded, but in the list of
plugins it is not showed up, so i'm not sure is working or not. Any
suggestion ?

Thanks
Fabio

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

Hi Fabio,

Which Openfire Version are you trying to use?

SIP Comm should be able to discover Nodes from Server and Contact List.

Regards,

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 10:4


#7

Hi Thiago,

i've now correctly installed the plugin on Openfire, i've just one more question, should i enter the Jingle Nodes relay Address manually or the SC is able to detect with the feature "Auto discover Jingle Nodes relay" enable ? it will use the realm of the Jabber account to detect it ?

Thanks
Fabio

···

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

Hi Fabio,

Try with Latest Openfire Version. If possible I would even recommend building from source and SVN.

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 10:51 AM, Fabio Telme <fabio@telme.sg> wrote:
Hi Thiago,

the version i use is Openfire, Version: 3.6.4 , the pluging is present on the server i can see the folder and the file uploaded, but in the list of plugins it is not showed up, so i'm not sure is working or not. Any suggestion ?

Thanks
Fabio

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

Hi Fabio,

Which Openfire Version are you trying to use?

SIP Comm should be able to discover Nodes from Server and Contact List.

Regards,

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 10:4