Routers not responding to Jitsi's UPnP discovery broadcasts


#1

Hi.
Now that the project has changed to Beta status, this UPnP error
really needs to be fixed.

Can I make an issue on the tracker for this please? How about 'Routers
not responding to Jitsi's UPnP discovery broadcasts'? Then I can
attach all the files to this one location.

I have tried talkr.im but that doesn't work either. (Sorry for not
replying to your question on IRC, things got quite hectic that
morning.) Anyway, XEP-0278 has experimental status and is only version
0.1:
http://xmpp.org/extensions/xep-0278.html

I'd prefer to make direct P2P connections rather than using relaying,
so I'd appreciate this being fixed.

Thank you.
James.

···

On 25/02/2011, James Haigh <james.r.haigh@gmail.com> wrote:

Hi,
I have attached a dump of successful UPnP. I found a package in the
Ubuntu repos called 'gupnp-tools'. I ran 'gupnp-universal-cp' and it
displayed info about the UPnP enabled router, then I closed it.

HTH.
James.

On 23/02/2011, James Haigh <james.r.haigh@gmail.com> wrote:

Hi,
I have some more data for you. Perhaps an attempt on a new network
will help. I tried to call my girlfriend as described:

Soldeu, Andorra:
UPnP enabled router
Thinkpad laptop:
- Ubuntu 10.04 i386, SC 3312 with experimental UPnP enabled

Girlfriend's house:
BT broadband with BT Home Hub (UPnP probably enabled)
MacBook Pro:
- Mac OS X 10.6.5, SC 3284 with experimental UPnP enabled

At 18:35:10 GMT I called her. (ICE failed.)
At 18:35:43 GMT she called me. (ICE failed.)

Good luck with the fix.

On 15/02/2011, Emil Ivov <emcho@sip-communicator.org> wrote:
...

GoogleTalk use their own relaying mechanism so you may have been using

Is this relaying mechanism accessible from SC?

Thank you.
James.

On 18/02/2011, James Haigh <james.r.haigh@gmail.com> wrote:

Hi Emil,
After over 2 hours I finally have the data. I really hope this is what
you need to fix the ICE failures.

All attached files were collected on my parents' laptop by my younger
brother and sent to me so that I could check them and remove passwords
first. Yes, he was bored, I asked him to call it 'dump'!

The relevant calls were between my parents' laptop and my Thinkpad (at
college). I also used the Dell to screen share to begin with to assist
with installation and configuration of Wireshark.

Home:
Plusnet broadband with UPnP enabled Belkin router (192.168.0.1)
Parents' laptop:
- Ubuntu 10.04 i386, SC 3285, 3298 with experimental UPnP enabled
(192.168.0.5)

College:
Dell laptop connected directly to 3 dongle:
- Ubuntu 10.10 i386, SC 3298
- Connected to an access point and used as a gateway for a small WLAN
(no
UPnP)
Thinkpad laptop:
- Ubuntu 10.04 i386, SC 3285

Summary:
* Installed and configured Wireshark on parents' laptop.
* Opened Wireshark, started capture with filter.
* At 22:40:36 I called my brother. (ICE failed.)
* At 22:42:20 my brother called me. (ICE failed.)
* Upgraded from 3285 to 3298 on parents' laptop because I notice that
ice4j is updated in 3296.
* At 22:59:27 I called my brother. (ICE failed.)
* At 22:59:52 my brother called me. (ICE failed.)
* Stopped capture, saved and closed dump.

Good luck with the fix.

Best wishes.
James.

On 17/02/2011, Emil Ivov <emcho@sip-communicator.org> wrote:

На 17.02.11 00:10, James Haigh написа:

On 16/02/2011, Emil Ivov <emcho@sip-communicator.org> wrote:
...

We don't currently have enough logging running in the upnp code so I
am
afraid I'd need to bug you for some more debug info. Could you please
send me a wireshark dump containing upnp related exchanges?

Yes I will, although it's now very awkward because I'm back at
college. Due to a holiday and some other arrangements I probably won't
be able to make this call again until March 25th - 27th.

No worries, we can wait.

I can make a similar call tomorrow evening: my Thinkpad (at college)
to my parents' laptop.

It's still very awkward because, in this scenario, it's my parents'
laptop where UPnP should definitely work. I will have to ask my
younger brother whether I can assist him with step-by-step
instructions to collect the data. If I'd known that you would need
this data last weekend, I could have easily collected it within
minutes.

I will assist him to collect:
* Wireshark dump
* Logs
* sip-communicator.properties

Anything else? Place your orders now because tomorrow will be the last
chance for 10 days to collect data on a call where UPnP is definitely
enabled.

This should be fine for now, but then again, if we need something else,
we can wait for you to get back there.

Thanks,
Emil


#2

No reply in over 2 weeks!...

Hi.
Now that the project has changed to Beta status, this UPnP error
really needs to be fixed.

Can I make an issue on the tracker for this please? How about 'Routers
not responding to Jitsi's UPnP discovery broadcasts'? Then I can
attach all the files to this one location.

This /is/ an issue! It needs to go on the tracker. As you (devs) don't
seem to want /me/ to file it, then can /you/ please think of a
specific name and file the bug.

James.

···

On 27/03/2011, James Haigh <james.r.haigh@gmail.com> wrote:

I have tried talkr.im but that doesn't work either. (Sorry for not
replying to your question on IRC, things got quite hectic that
morning.) Anyway, XEP-0278 has experimental status and is only version
0.1:
http://xmpp.org/extensions/xep-0278.html

I'd prefer to make direct P2P connections rather than using relaying,
so I'd appreciate this being fixed.

Thank you.
James.

On 25/02/2011, James Haigh <james.r.haigh@gmail.com> wrote:

Hi,
I have attached a dump of successful UPnP. I found a package in the
Ubuntu repos called 'gupnp-tools'. I ran 'gupnp-universal-cp' and it
displayed info about the UPnP enabled router, then I closed it.

HTH.
James.

On 23/02/2011, James Haigh <james.r.haigh@gmail.com> wrote:

Hi,
I have some more data for you. Perhaps an attempt on a new network
will help. I tried to call my girlfriend as described:

Soldeu, Andorra:
UPnP enabled router
Thinkpad laptop:
- Ubuntu 10.04 i386, SC 3312 with experimental UPnP enabled

Girlfriend's house:
BT broadband with BT Home Hub (UPnP probably enabled)
MacBook Pro:
- Mac OS X 10.6.5, SC 3284 with experimental UPnP enabled

At 18:35:10 GMT I called her. (ICE failed.)
At 18:35:43 GMT she called me. (ICE failed.)

Good luck with the fix.

On 15/02/2011, Emil Ivov <emcho@sip-communicator.org> wrote:
...

GoogleTalk use their own relaying mechanism so you may have been using

Is this relaying mechanism accessible from SC?

Thank you.
James.

On 18/02/2011, James Haigh <james.r.haigh@gmail.com> wrote:

Hi Emil,
After over 2 hours I finally have the data. I really hope this is what
you need to fix the ICE failures.

All attached files were collected on my parents' laptop by my younger
brother and sent to me so that I could check them and remove passwords
first. Yes, he was bored, I asked him to call it 'dump'!

The relevant calls were between my parents' laptop and my Thinkpad (at
college). I also used the Dell to screen share to begin with to assist
with installation and configuration of Wireshark.

Home:
Plusnet broadband with UPnP enabled Belkin router (192.168.0.1)
Parents' laptop:
- Ubuntu 10.04 i386, SC 3285, 3298 with experimental UPnP enabled
(192.168.0.5)

College:
Dell laptop connected directly to 3 dongle:
- Ubuntu 10.10 i386, SC 3298
- Connected to an access point and used as a gateway for a small WLAN
(no
UPnP)
Thinkpad laptop:
- Ubuntu 10.04 i386, SC 3285

Summary:
* Installed and configured Wireshark on parents' laptop.
* Opened Wireshark, started capture with filter.
* At 22:40:36 I called my brother. (ICE failed.)
* At 22:42:20 my brother called me. (ICE failed.)
* Upgraded from 3285 to 3298 on parents' laptop because I notice that
ice4j is updated in 3296.
* At 22:59:27 I called my brother. (ICE failed.)
* At 22:59:52 my brother called me. (ICE failed.)
* Stopped capture, saved and closed dump.

Good luck with the fix.

Best wishes.
James.

On 17/02/2011, Emil Ivov <emcho@sip-communicator.org> wrote:

На 17.02.11 00:10, James Haigh написа:

On 16/02/2011, Emil Ivov <emcho@sip-communicator.org> wrote:
...

We don't currently have enough logging running in the upnp code so I
am
afraid I'd need to bug you for some more debug info. Could you
please
send me a wireshark dump containing upnp related exchanges?

Yes I will, although it's now very awkward because I'm back at
college. Due to a holiday and some other arrangements I probably
won't
be able to make this call again until March 25th - 27th.

No worries, we can wait.

I can make a similar call tomorrow evening: my Thinkpad (at college)
to my parents' laptop.

It's still very awkward because, in this scenario, it's my parents'
laptop where UPnP should definitely work. I will have to ask my
younger brother whether I can assist him with step-by-step
instructions to collect the data. If I'd known that you would need
this data last weekend, I could have easily collected it within
minutes.

I will assist him to collect:
* Wireshark dump
* Logs
* sip-communicator.properties

Anything else? Place your orders now because tomorrow will be the
last
chance for 10 days to collect data on a call where UPnP is definitely
enabled.

This should be fine for now, but then again, if we need something
else,
we can wait for you to get back there.

Thanks,
Emil


#3

Hey James,

Yes could you please file an issue and attach there all captures that you
have?

Thank you for letting me file an issue on the tracker. :slight_smile:

http://java.net/jira/browse/JITSI-934

Note that most of the developers currently have their hands full with other
tasks which is why this is taking a while.

At least now it's tracked it won't be forgotten. :wink:

Thank you.
James.

···

On 12/04/2011, Emil Ivov <emcho@jitsi.org> wrote:

Thanks,
Emil

--sent from my mobile

On 12 avr. 2011, at 02:25, James Haigh <james.r.haigh@gmail.com> wrote:

No reply in over 2 weeks!...

On 27/03/2011, James Haigh <james.r.haigh@gmail.com> wrote:

Hi.
Now that the project has changed to Beta status, this UPnP error
really needs to be fixed.

Can I make an issue on the tracker for this please? How about 'Routers
not responding to Jitsi's UPnP discovery broadcasts'? Then I can
attach all the files to this one location.

This /is/ an issue! It needs to go on the tracker. As you (devs) don't
seem to want /me/ to file it, then can /you/ please think of a
specific name and file the bug.

James.

I have tried talkr.im but that doesn't work either. (Sorry for not
replying to your question on IRC, things got quite hectic that
morning.) Anyway, XEP-0278 has experimental status and is only version
0.1:
http://xmpp.org/extensions/xep-0278.html

I'd prefer to make direct P2P connections rather than using relaying,
so I'd appreciate this being fixed.

Thank you.
James.

On 25/02/2011, James Haigh <james.r.haigh@gmail.com> wrote:

Hi,
I have attached a dump of successful UPnP. I found a package in the
Ubuntu repos called 'gupnp-tools'. I ran 'gupnp-universal-cp' and it
displayed info about the UPnP enabled router, then I closed it.

HTH.
James.

On 23/02/2011, James Haigh <james.r.haigh@gmail.com> wrote:

Hi,
I have some more data for you. Perhaps an attempt on a new network
will help. I tried to call my girlfriend as described:

Soldeu, Andorra:
UPnP enabled router
Thinkpad laptop:
- Ubuntu 10.04 i386, SC 3312 with experimental UPnP enabled

Girlfriend's house:
BT broadband with BT Home Hub (UPnP probably enabled)
MacBook Pro:
- Mac OS X 10.6.5, SC 3284 with experimental UPnP enabled

At 18:35:10 GMT I called her. (ICE failed.)
At 18:35:43 GMT she called me. (ICE failed.)

Good luck with the fix.

On 15/02/2011, Emil Ivov <emcho@sip-communicator.org> wrote:
...

GoogleTalk use their own relaying mechanism so you may have been using

Is this relaying mechanism accessible from SC?

Thank you.
James.

On 18/02/2011, James Haigh <james.r.haigh@gmail.com> wrote:

Hi Emil,
After over 2 hours I finally have the data. I really hope this is what
you need to fix the ICE failures.

All attached files were collected on my parents' laptop by my younger
brother and sent to me so that I could check them and remove passwords
first. Yes, he was bored, I asked him to call it 'dump'!

The relevant calls were between my parents' laptop and my Thinkpad (at
college). I also used the Dell to screen share to begin with to assist
with installation and configuration of Wireshark.

Home:
Plusnet broadband with UPnP enabled Belkin router (192.168.0.1)
Parents' laptop:
- Ubuntu 10.04 i386, SC 3285, 3298 with experimental UPnP enabled
(192.168.0.5)

College:
Dell laptop connected directly to 3 dongle:
- Ubuntu 10.10 i386, SC 3298
- Connected to an access point and used as a gateway for a small WLAN
(no
UPnP)
Thinkpad laptop:
- Ubuntu 10.04 i386, SC 3285

Summary:
* Installed and configured Wireshark on parents' laptop.
* Opened Wireshark, started capture with filter.
* At 22:40:36 I called my brother. (ICE failed.)
* At 22:42:20 my brother called me. (ICE failed.)
* Upgraded from 3285 to 3298 on parents' laptop because I notice that
ice4j is updated in 3296.
* At 22:59:27 I called my brother. (ICE failed.)
* At 22:59:52 my brother called me. (ICE failed.)
* Stopped capture, saved and closed dump.

Good luck with the fix.

Best wishes.
James.

On 17/02/2011, Emil Ivov <emcho@sip-communicator.org> wrote:

На 17.02.11 00:10, James Haigh написа:

On 16/02/2011, Emil Ivov <emcho@sip-communicator.org> wrote:
...

We don't currently have enough logging running in the upnp code so
I
am
afraid I'd need to bug you for some more debug info. Could you
please
send me a wireshark dump containing upnp related exchanges?

Yes I will, although it's now very awkward because I'm back at
college. Due to a holiday and some other arrangements I probably
won't
be able to make this call again until March 25th - 27th.

No worries, we can wait.

I can make a similar call tomorrow evening: my Thinkpad (at college)
to my parents' laptop.

It's still very awkward because, in this scenario, it's my parents'
laptop where UPnP should definitely work. I will have to ask my
younger brother whether I can assist him with step-by-step
instructions to collect the data. If I'd known that you would need
this data last weekend, I could have easily collected it within
minutes.

I will assist him to collect:
* Wireshark dump
* Logs
* sip-communicator.properties

Anything else? Place your orders now because tomorrow will be the
last
chance for 10 days to collect data on a call where UPnP is
definitely
enabled.

This should be fine for now, but then again, if we need something
else,
we can wait for you to get back there.

Thanks,
Emil


#4

Hi James,

Yesterday evening, while playing a bit with linux-igd on a router, I discover that it does not response to the weupnp (library that Jitsi use) discover messages. It looks like your case. I will investigate more on this maybe today or next week.

···

--
Seb

Le 12/04/11 15:33, James Haigh a écrit :

On 12/04/2011, Emil Ivov<emcho@jitsi.org> wrote:

Hey James,

Yes could you please file an issue and attach there all captures that you
have?

Thank you for letting me file an issue on the tracker. :slight_smile:

http://java.net/jira/browse/JITSI-934

Note that most of the developers currently have their hands full with other
tasks which is why this is taking a while.

At least now it's tracked it won't be forgotten. :wink:

Thank you.
James.

Thanks,
Emil

--sent from my mobile

On 12 avr. 2011, at 02:25, James Haigh<james.r.haigh@gmail.com> wrote:

No reply in over 2 weeks!...

On 27/03/2011, James Haigh<james.r.haigh@gmail.com> wrote:

Hi.
Now that the project has changed to Beta status, this UPnP error
really needs to be fixed.

Can I make an issue on the tracker for this please? How about 'Routers
not responding to Jitsi's UPnP discovery broadcasts'? Then I can
attach all the files to this one location.

This /is/ an issue! It needs to go on the tracker. As you (devs) don't
seem to want /me/ to file it, then can /you/ please think of a
specific name and file the bug.

James.

I have tried talkr.im but that doesn't work either. (Sorry for not
replying to your question on IRC, things got quite hectic that
morning.) Anyway, XEP-0278 has experimental status and is only version
0.1:
http://xmpp.org/extensions/xep-0278.html

I'd prefer to make direct P2P connections rather than using relaying,
so I'd appreciate this being fixed.

Thank you.
James.

On 25/02/2011, James Haigh<james.r.haigh@gmail.com> wrote:

Hi,
I have attached a dump of successful UPnP. I found a package in the
Ubuntu repos called 'gupnp-tools'. I ran 'gupnp-universal-cp' and it
displayed info about the UPnP enabled router, then I closed it.

HTH.
James.

On 23/02/2011, James Haigh<james.r.haigh@gmail.com> wrote:

Hi,
I have some more data for you. Perhaps an attempt on a new network
will help. I tried to call my girlfriend as described:

Soldeu, Andorra:
UPnP enabled router
Thinkpad laptop:
- Ubuntu 10.04 i386, SC 3312 with experimental UPnP enabled

Girlfriend's house:
BT broadband with BT Home Hub (UPnP probably enabled)
MacBook Pro:
- Mac OS X 10.6.5, SC 3284 with experimental UPnP enabled

At 18:35:10 GMT I called her. (ICE failed.)
At 18:35:43 GMT she called me. (ICE failed.)

Good luck with the fix.

On 15/02/2011, Emil Ivov<emcho@sip-communicator.org> wrote:
...

GoogleTalk use their own relaying mechanism so you may have been using

Is this relaying mechanism accessible from SC?

Thank you.
James.

On 18/02/2011, James Haigh<james.r.haigh@gmail.com> wrote:

Hi Emil,
After over 2 hours I finally have the data. I really hope this is what
you need to fix the ICE failures.

All attached files were collected on my parents' laptop by my younger
brother and sent to me so that I could check them and remove passwords
first. Yes, he was bored, I asked him to call it 'dump'!

The relevant calls were between my parents' laptop and my Thinkpad (at
college). I also used the Dell to screen share to begin with to assist
with installation and configuration of Wireshark.

Home:
Plusnet broadband with UPnP enabled Belkin router (192.168.0.1)
Parents' laptop:
- Ubuntu 10.04 i386, SC 3285, 3298 with experimental UPnP enabled
(192.168.0.5)

College:
Dell laptop connected directly to 3 dongle:
- Ubuntu 10.10 i386, SC 3298
- Connected to an access point and used as a gateway for a small WLAN
(no
UPnP)
Thinkpad laptop:
- Ubuntu 10.04 i386, SC 3285

Summary:
* Installed and configured Wireshark on parents' laptop.
* Opened Wireshark, started capture with filter.
* At 22:40:36 I called my brother. (ICE failed.)
* At 22:42:20 my brother called me. (ICE failed.)
* Upgraded from 3285 to 3298 on parents' laptop because I notice that
ice4j is updated in 3296.
* At 22:59:27 I called my brother. (ICE failed.)
* At 22:59:52 my brother called me. (ICE failed.)
* Stopped capture, saved and closed dump.

Good luck with the fix.

Best wishes.
James.

On 17/02/2011, Emil Ivov<emcho@sip-communicator.org> wrote:

На 17.02.11 00:10, James Haigh написа:

On 16/02/2011, Emil Ivov<emcho@sip-communicator.org> wrote:
...

We don't currently have enough logging running in the upnp code so
I
am
afraid I'd need to bug you for some more debug info. Could you
please
send me a wireshark dump containing upnp related exchanges?

Yes I will, although it's now very awkward because I'm back at
college. Due to a holiday and some other arrangements I probably
won't
be able to make this call again until March 25th - 27th.

No worries, we can wait.

I can make a similar call tomorrow evening: my Thinkpad (at college)
to my parents' laptop.

It's still very awkward because, in this scenario, it's my parents'
laptop where UPnP should definitely work. I will have to ask my
younger brother whether I can assist him with step-by-step
instructions to collect the data. If I'd known that you would need
this data last weekend, I could have easily collected it within
minutes.

I will assist him to collect:
* Wireshark dump
* Logs
* sip-communicator.properties

Anything else? Place your orders now because tomorrow will be the
last
chance for 10 days to collect data on a call where UPnP is
definitely
enabled.

This should be fine for now, but then again, if we need something
else,
we can wait for you to get back there.

Thanks,
Emil


#5

Thank you Seb, I appreciate it.

Good luck.
James.

···

On 15/04/2011, Sebastien Vincent <seb@sip-communicator.org> wrote:

Hi James,

Yesterday evening, while playing a bit with linux-igd on a router, I
discover that it does not response to the weupnp (library that Jitsi
use) discover messages. It looks like your case. I will investigate more
on this maybe today or next week.

--
Seb

Le 12/04/11 15:33, James Haigh a écrit :

On 12/04/2011, Emil Ivov<emcho@jitsi.org> wrote:

Hey James,

Yes could you please file an issue and attach there all captures that you
have?

Thank you for letting me file an issue on the tracker. :slight_smile:

http://java.net/jira/browse/JITSI-934

Note that most of the developers currently have their hands full with
other
tasks which is why this is taking a while.

At least now it's tracked it won't be forgotten. :wink:

Thank you.
James.

Thanks,
Emil

--sent from my mobile

On 12 avr. 2011, at 02:25, James Haigh<james.r.haigh@gmail.com> wrote:

No reply in over 2 weeks!...

On 27/03/2011, James Haigh<james.r.haigh@gmail.com> wrote:

Hi.
Now that the project has changed to Beta status, this UPnP error
really needs to be fixed.

Can I make an issue on the tracker for this please? How about 'Routers
not responding to Jitsi's UPnP discovery broadcasts'? Then I can
attach all the files to this one location.

This /is/ an issue! It needs to go on the tracker. As you (devs) don't
seem to want /me/ to file it, then can /you/ please think of a
specific name and file the bug.

James.

I have tried talkr.im but that doesn't work either. (Sorry for not
replying to your question on IRC, things got quite hectic that
morning.) Anyway, XEP-0278 has experimental status and is only version
0.1:
http://xmpp.org/extensions/xep-0278.html

I'd prefer to make direct P2P connections rather than using relaying,
so I'd appreciate this being fixed.

Thank you.
James.

On 25/02/2011, James Haigh<james.r.haigh@gmail.com> wrote:

Hi,
I have attached a dump of successful UPnP. I found a package in the
Ubuntu repos called 'gupnp-tools'. I ran 'gupnp-universal-cp' and it
displayed info about the UPnP enabled router, then I closed it.

HTH.
James.

On 23/02/2011, James Haigh<james.r.haigh@gmail.com> wrote:

Hi,
I have some more data for you. Perhaps an attempt on a new network
will help. I tried to call my girlfriend as described:

Soldeu, Andorra:
UPnP enabled router
Thinkpad laptop:
- Ubuntu 10.04 i386, SC 3312 with experimental UPnP enabled

Girlfriend's house:
BT broadband with BT Home Hub (UPnP probably enabled)
MacBook Pro:
- Mac OS X 10.6.5, SC 3284 with experimental UPnP enabled

At 18:35:10 GMT I called her. (ICE failed.)
At 18:35:43 GMT she called me. (ICE failed.)

Good luck with the fix.

On 15/02/2011, Emil Ivov<emcho@sip-communicator.org> wrote:
...

GoogleTalk use their own relaying mechanism so you may have been
using

Is this relaying mechanism accessible from SC?

Thank you.
James.

On 18/02/2011, James Haigh<james.r.haigh@gmail.com> wrote:

Hi Emil,
After over 2 hours I finally have the data. I really hope this is
what
you need to fix the ICE failures.

All attached files were collected on my parents' laptop by my
younger
brother and sent to me so that I could check them and remove
passwords
first. Yes, he was bored, I asked him to call it 'dump'!

The relevant calls were between my parents' laptop and my Thinkpad
(at
college). I also used the Dell to screen share to begin with to
assist
with installation and configuration of Wireshark.

Home:
Plusnet broadband with UPnP enabled Belkin router (192.168.0.1)
Parents' laptop:
- Ubuntu 10.04 i386, SC 3285, 3298 with experimental UPnP enabled
(192.168.0.5)

College:
Dell laptop connected directly to 3 dongle:
- Ubuntu 10.10 i386, SC 3298
- Connected to an access point and used as a gateway for a small
WLAN
(no
UPnP)
Thinkpad laptop:
- Ubuntu 10.04 i386, SC 3285

Summary:
* Installed and configured Wireshark on parents' laptop.
* Opened Wireshark, started capture with filter.
* At 22:40:36 I called my brother. (ICE failed.)
* At 22:42:20 my brother called me. (ICE failed.)
* Upgraded from 3285 to 3298 on parents' laptop because I notice
that
ice4j is updated in 3296.
* At 22:59:27 I called my brother. (ICE failed.)
* At 22:59:52 my brother called me. (ICE failed.)
* Stopped capture, saved and closed dump.

Good luck with the fix.

Best wishes.
James.

On 17/02/2011, Emil Ivov<emcho@sip-communicator.org> wrote:

На 17.02.11 00:10, James Haigh написа:

On 16/02/2011, Emil Ivov<emcho@sip-communicator.org> wrote:
...

We don't currently have enough logging running in the upnp code
so
I
am
afraid I'd need to bug you for some more debug info. Could you
please
send me a wireshark dump containing upnp related exchanges?

Yes I will, although it's now very awkward because I'm back at
college. Due to a holiday and some other arrangements I probably
won't
be able to make this call again until March 25th - 27th.

No worries, we can wait.

I can make a similar call tomorrow evening: my Thinkpad (at
college)
to my parents' laptop.

It's still very awkward because, in this scenario, it's my
parents'
laptop where UPnP should definitely work. I will have to ask my
younger brother whether I can assist him with step-by-step
instructions to collect the data. If I'd known that you would need
this data last weekend, I could have easily collected it within
minutes.

I will assist him to collect:
* Wireshark dump
* Logs
* sip-communicator.properties

Anything else? Place your orders now because tomorrow will be the
last
chance for 10 days to collect data on a call where UPnP is
definitely
enabled.

This should be fine for now, but then again, if we need something
else,
we can wait for you to get back there.

Thanks,
Emil


#6

Hi James,

We have finally solve the linux-igd discover problem with weupnp and commit changes in SVN revision 8506, next build 3428 is currently baking.

Can you please test again and see if it works for you now ? Otherwise send us wireshark captures (that show upnp discover) and logs. Thanks.

Regards,

···

--
Seb

Le 15/04/11 16:31, James Haigh a écrit :

Thank you Seb, I appreciate it.

Good luck.
James.

On 15/04/2011, Sebastien Vincent<seb@sip-communicator.org> wrote:

Hi James,

Yesterday evening, while playing a bit with linux-igd on a router, I
discover that it does not response to the weupnp (library that Jitsi
use) discover messages. It looks like your case. I will investigate more
on this maybe today or next week.

--
Seb


#7

Hi James,

We finally discover one problem in ice4j that can prevent ICE negociation to succeed. I was wrong when I told you on IRC that you need both peer having UPnP, so just one UPnP enabled Jitsi is sufficient.

Can you test again with latest build (starting from 3432) and tell us if it works ?

Regards,

···

--
Seb

Le 18/04/11 09:12, Sebastien Vincent a écrit :

Hi James,

We have finally solve the linux-igd discover problem with weupnp and commit changes in SVN revision 8506, next build 3428 is currently baking.

Can you please test again and see if it works for you now ? Otherwise send us wireshark captures (that show upnp discover) and logs. Thanks.

Regards,
--
Seb

Le 15/04/11 16:31, James Haigh a écrit :

Thank you Seb, I appreciate it.

Good luck.
James.

On 15/04/2011, Sebastien Vincent<seb@sip-communicator.org> wrote:

Hi James,

Yesterday evening, while playing a bit with linux-igd on a router, I
discover that it does not response to the weupnp (library that Jitsi
use) discover messages. It looks like your case. I will investigate more
on this maybe today or next week.

--
Seb


#8

Hi James,

We finally discover one problem in ice4j that can prevent ICE
negociation to succeed. I was wrong when I told you on IRC that you need
both peer having UPnP, so just one UPnP enabled Jitsi is sufficient.

I really couldn't understand why both would need UPnP. If my NAT is
capable of receiving incoming connections, it really doesn't matter
what NAT she has, all NATs can make outgoing connections.

Can you test again with latest build (starting from 3432) and tell us if
it works ?

It's always awkward to test this bug.

Last night I went round to a neighbour with my Dell which still had
the last SC build, 3284. I SSHed and VNCoSSHed into my Thinkpad at
home, which had 3429. I tried a call as a control test, and as
expected, ICE failed. I updated the Dell to Jitsi 3432, and the call
connected.

So well done and thank you!

(It wasn't much of a call as there was no-one at the other end and my
Dell doesn't even have a built-in mic like my Thinkpad does. :stuck_out_tongue: )

I'm yet to test a call with my girlfriend, but I'm fairly sure it'll
work. I'll let you know later.

Please have UPnP enabled by default for new Jitsi installs . And
/maybe/ remove 'experimental' status, as now it's probably about as
stable as the rest of Jitsi.

Thank you very much!
James.

···

On 20/04/2011, Sebastien Vincent <seb@sip-communicator.org> wrote:

Regards,
--
Seb

Le 18/04/11 09:12, Sebastien Vincent a écrit :

Hi James,

We have finally solve the linux-igd discover problem with weupnp and
commit changes in SVN revision 8506, next build 3428 is currently baking.

Can you please test again and see if it works for you now ? Otherwise
send us wireshark captures (that show upnp discover) and logs. Thanks.

Regards,
--
Seb

Le 15/04/11 16:31, James Haigh a écrit :

Thank you Seb, I appreciate it.

Good luck.
James.

On 15/04/2011, Sebastien Vincent<seb@sip-communicator.org> wrote:

Hi James,

Yesterday evening, while playing a bit with linux-igd on a router, I
discover that it does not response to the weupnp (library that Jitsi
use) discover messages. It looks like your case. I will investigate
more
on this maybe today or next week.

--
Seb


#9

...

I'm yet to test a call with my girlfriend, but I'm fairly sure it'll
work. I'll let you know later.

Unfortunately, this turned out not to work. Emil reopened the issue
and I uploaded some Wireshark dumps:
http://java.net/jira/browse/JITSI-934?focusedCommentId=307924#action_307922

James.

···

On 24/04/2011, James Haigh <james.r.haigh@gmail.com> wrote:


#10

Hi James,

We have look at your last pcap traces and it appears gupnp and weupnp lib does not send the same discovery especially the ST parameter which is "upnp:rootdevice" for the first one and "urn:schemas-upnp-org:device:InternetGatewayDevice:1".

My thoughts is your router does not understand the "urn:...:InternetGatewayDevice:1" but possibly understand other such as "urn:...:WANIPConnection:1" or "urn:...:WANPPPConnection:1".

I have found an application called miniupnp (http://miniupnp.free.fr) which try many ST parameter. Can you try this program and send us the pcap traces ? Then if we have something returned by miniupnp traces, we will modify weupnp to try different ST parameters.

Best regards,

···

--
Seb

Le 10/05/11 16:44, James Haigh a écrit :

On 24/04/2011, James Haigh<james.r.haigh@gmail.com> wrote:
...

I'm yet to test a call with my girlfriend, but I'm fairly sure it'll
work. I'll let you know later.

Unfortunately, this turned out not to work. Emil reopened the issue
and I uploaded some Wireshark dumps:
http://java.net/jira/browse/JITSI-934?focusedCommentId=307924#action_307922

James.


#11

Hi James, all,

Attached is a modified weupnp jar, can you try with your UPnP router:
java -jar weupnp-0.1.2-SNAPSHOT.jar

It will be great if others can test it if they have an UPnP router.

You can also try with Jitsi (if you compile it from source) by:
cp weupnp-0.1.2-SNAPSHOT <jitsi_src>/lib/installer-exclude/weupnp-0.1.2-SNAPSHOT.jar
ant rebuild
ant run

Regards,

weupnp-0.1.2-SNAPSHOT.jar (25.4 KB)

···

--
Seb

Le 11/05/11 18:06, Sebastien Vincent a écrit :

Hi James,

We have look at your last pcap traces and it appears gupnp and weupnp lib does not send the same discovery especially the ST parameter which is "upnp:rootdevice" for the first one and "urn:schemas-upnp-org:device:InternetGatewayDevice:1".

My thoughts is your router does not understand the "urn:...:InternetGatewayDevice:1" but possibly understand other such as "urn:...:WANIPConnection:1" or "urn:...:WANPPPConnection:1".

I have found an application called miniupnp (http://miniupnp.free.fr) which try many ST parameter. Can you try this program and send us the pcap traces ? Then if we have something returned by miniupnp traces, we will modify weupnp to try different ST parameters.

Best regards,
--
Seb

Le 10/05/11 16:44, James Haigh a écrit :

On 24/04/2011, James Haigh<james.r.haigh@gmail.com> wrote:
...

I'm yet to test a call with my girlfriend, but I'm fairly sure it'll
work. I'll let you know later.

Unfortunately, this turned out not to work. Emil reopened the issue
and I uploaded some Wireshark dumps:
http://java.net/jira/browse/JITSI-934?focusedCommentId=307924#action_307922

James.