SIP: doesn't handle suspend w/ network change

[jamincollins]

Qutecom doesn't appear to properly handle/detect having been suspended and resuming with a network change.

As far as I can tell the SIP registration is updated correctly, but any attempted call results in no audio until the application is fully exited and restarted.

Qutecom should more gracefully detect network changes such as this.

[vadim]

Can you please provide some more info about your system? Is it windows, linux, desktop, portable?

[jamincollins]

Linux, Ubuntu 8.10, Thinkpad T61p. I frequently suspend the unit when traveling from home to work and vice versa. So, the unit will suspend on one network and resume on another. Network Manager handles all the connection changes.

[vadim]

Can you please do the following 2 tests:

launch in the shell window:

apic_listen >samenet.log

then suspend and resume ON THE SAME NET

And a second one:

apic_listen >anothernet.log

Then suspend and resume on DIFFERENT network

and post here the samenet.log and anothernet.log

Thanks

[jamincollins]

do you perhaps mean acpi_listen?

If so, I've done the same network suspend and resume, but there's not much in the file.

$ cat samenet.log
ibm/hotkey HKEY 00000080 00001004
processor CPU0 00000081 00000000
processor CPU1 00000081 00000000

[vadim]

After further investigation it seems that the best way is to install a resume script in the /etc/acpi/resume.d directory sending some kind of DBus message to QuteCom upon resume...

Any volunteers?

[jamincollins]

Why go with a resume script? That would still (presumably) leave Qutecom unable to handle general network changes. Say, for example, a user has Qutecom running and switches wireless networks or moves from wireless to wired what happens? If Qutecom were to instead monitor the Network Manager dbus state it would be able to proactively adjust to network changes.

[vadim]

Excellent idea!!!
Do you have any pointers on docs about related DBus events?

[jamincollins]

For Network Manager:
​http://people.redhat.com/dcbw/NetworkManager/NetworkManager%20DBUS%20API.txt
​http://projects.gnome.org/NetworkManager/developers/spec.html

Looks like qutecom is mostly written in C++, not a language I'm very good at. I did however find this tutorial:
​http://dbus.freedesktop.org/doc/dbus-tutorial.html

It also appears that there is some python in the archive. A python dbus tutorial:
​http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html

[vadim]

Thinking some more about it.

Actually QuteCom detect network connectivity and loss pretty well, the only problem will is this suspend/resume scenario...
So maybe my idea about QuteCom specific resume script will be simpler to implement

[vadim]

I've commited a fix to this issue: ​http://hg.qutecom.com/qutecom-2.2/rev/0c9ef25e8554

PLease check it...

[cervajs]

Milestone milestone3 deleted