I have tried a different telephone and there is still the same issue. If i use the onboard sound then the call works fine. this issue has only arisen since the new version of Skype. I have pathced up to the latest. I am currently using Ubuntu 7.04 X64.
With the previous version of skype this would happen but it would be a good 20 minutes into the conversation.
I would gladly turn on logging or anything needed to track this. it takes around 4 seconds to the skype test call to reproduce.
Regards
Richard
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Does it hang up and go back to the dial tone or just go silent ?
I'm using 1.4.0.74 as the 99 version breaks the usb sound devices. If you can go back to that, hopefully this will be fixed soon. If you still have the problem on that let me know
Simon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It just goes stright back to dail tone. Having looked through the logs it apparently has received a OFF command from the box!! Really not sure how / why but I think that it is skype version related as the 1.3 release seemed to have worked. Although it did hang up sometimes without warning
Sorry for being a noob, but can you tell me how to get the older version? I have not kept any as I have re-installed my system since just in case there was something horribly wrong with my layout
thanks
Richard
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
thank you for your help this far. I have tried .79 version of Skype and have found that the problem does not occur in that version. I have therefore upgraded to re-create the situation, and have done so successfully.
Here is the output of the debug, all sectins marked [...] are sections that I have edited personal details.
---------------------
Skype instance found, window id 62914629
NAME B2K_CONNECTOR
PROTOCOL 7
OK
PROTOCOL 7
CONNSTATUS ONLINE
CURRENTUSERHANDLE beebock
SEARCH FRIENDS
USERSTATUS INVISIBLE
[...]
USB Device Found
USB Device startup error, trying again....
USB Device Found
USER beebock ONLINESTATUS OFFLINE
USERSTATUS OFFLINE
CONNSTATUS CONNECTING
HANDSET OFF
MINIMIZE
OK
CONNSTATUS ONLINE
USER beebock ONLINESTATUS INVISIBLE
USERSTATUS INVISIBLE
[...]
GROUP 23 NROFUSERS 2
USER linda_rae ONLINESTATUS NA
CALL 59 STATUS UNPLACED
CALL 59 STATUS ROUTING
HANDSET ON
FOCUS
FOCUS
OK
[...]
CALL 59 STATUS RINGING
CALL 59 VAA_INPUT_STATUS FALSE
CALL 59 STATUS INPROGRESS
CALL 59 DURATION 1
CALL 59 DURATION 2
CALL 59 DURATION 3
HANDSET OFF
SET CALL 59 STATUS FINISHED
MINIMIZE
HANDSET ON
FOCUS
FOCUS
CALL 59 STATUS FINISHED
OK
OK
CALL 59 STATUS FINISHED
CALL 66 STATUS UNPLACED
CALL 66 STATUS ROUTING
CALL 66 STATUS RINGING
CALL 66 VAA_INPUT_STATUS FALSE
CALL 66 STATUS INPROGRESS
CALL 66 DURATION 1
HANDSET OFF
SET CALL 66 STATUS FINISHED
MINIMIZE
HANDSET ON
FOCUS
FOCUS
CALL 66 STATUS FINISHED
OK
OK
CALL 66 STATUS FINISHED
HANDSET OFF
MINIMIZE
OK
------------------
above you can see the issue occuring. Call 66 and the one just before both had the same issue.
Here is the output of the terminal upon running kb2kskype --debugmessages
----------------
richard@richard-desktop:/usr/bin$ kb2kskype --debugmessages
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
----------------
Even though the errors are reported, the app has launched
Another piece of information that you may need. There is no PSTN line plugged into this installation. I have also installed all the lib32 compatable libraries for the 64 bit OS.
If there is anything else you need to know, please don't hesitate to ask.
Regards
Richard
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hold on. It seems that I found the problem and managed to fix it.
On my FC5 (dual core Intel), when a call was in progress, usbb2k sometimes registered mysterious keysrokes. These led to a variety of odd events like spontaneous hangups or missing keystrokes. It is quite possible that while ago another thread was discussing the same problem.
Please, give me a day or two to test my fixes and I'll post them.
Dima
P.S. I can only provide source files. You will have to compile them for your environment. If your system is not Fedora Core or Red Hat, then you might need to port them.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is this in PSTN mode ? Aas that is what the thread you linked was talking about, or at least the changing mode between PSTN and USB.
Am I correct in assuming the problem you are talking about is unreleated to the new Skype problem that this thread was about ? as my fc is only running 1.3.
Simon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Simon, all problems - missing or spontaneous keypresses, occasional hangups, spontaneous calls to blank or non-existing destinations - all happened to me in USB mode. I might be wrong, but I have feeling that this thread was about the same or closely related issue:
I found that USB modem was apparently busy (maybe timing of async polling loop in USB server thread caused stalls sometimes) and occasionally returned error flags along with garbage in data registers. The usbb2k driver did not filter these errors out and passed random keystrokes to client app.
I am running the latest Skype 1.4.0.99 and the skype itself is fine.
Not problems whatsoever, except that its functionality is limited compared to version 3.5, which is not available for Linux.
Dima
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi that thread was actually about trying to read from the socket before the connected signal had come back and some random keys during switch between usb and pstn.
I get the same issues you are talking about but only on 1.4.0.99. Skype 1.4.0.74 works 100% I'm hoping it might be something to do with Skype flooding the USB interface, as a result of agc. I'll see what happens in the next version of Skype and then look more. They are adding a disable option for it to the UI and other things.
One thing I never tested was to put the box into usb mode and then exit kb2kskype and stop usbb2k_api and then make a call using the Skype UI and see it the problem still happens. This would then mean it isn't anything wrong on my part it would mean either snd_usb_audio or Skype. Would you like to try for me ?
Richard glad you got everything working, let me know if you have any more problems.
Simon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Simon - inless I got it wrong, your idea won't work. How would I detect keypress errors if usbb2k_api were not running? I suggest trying my patch on systems with spontaneous telbox errors (a typical behavior under race conditions). What currently is happening in usbb2k driver is a typical race condition created by frequent reads from a slow USB device.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Richard
Currently, I can only provide you with a patch, which is not in any release yet.
To use the patch, you need to download sources for both, 2.2-4 USB driver and 0.3.4 b2k controller. Once you have all source files installed and build environment configured, you may download the patch from:
The patch contains updates for 3 files (diff outputs). Please, apply the updates, rebuild the source, install new executables, and restart driver and controller.
Dima
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the patches. The usbb2k-api one look good I see what you mean about the error checking. I assume the new version of Skype is flooding the audio endpoints that is causing the errors on the control endpoint that weren't there before in previous versions of Skype so I'll still blame Skype :) The audio is also still useless although it doesn't hang up anymore.
One question about the mixer patch I don't see any different apart from you added in a comma but the command works with and without it. I'm reluctant to change it, as knowing my look it will cause other problems, do you really need this patch ? If you use this from skype you have to drag the slider not just click it to fire the event, i tried the click but it made the GUI go very slow, due to the high number of system calls.
amixer -q -c 1 sset Mic 0 25% cap
check in alsamixer, it changed.
amixer -q -c 1 sset Mic,0 50% cap
check in alsamixer it changed.
amixer -q -c 1 sset Mic 0 75% cap
check in alsamixer it changed.
I'll post the updated code as soon as you anser the sound issue
Thanks for the help
Simon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Guys,
I have jsut upgraded to the latest skype, and the latest KB2kskype app.
Now everytime I want to make a call it hangs up after 4-10 seconds.
Any ideas?
There are no errors in the logs
Regards
Richard
Hi,
Additional information.
I have tried a different telephone and there is still the same issue. If i use the onboard sound then the call works fine. this issue has only arisen since the new version of Skype. I have pathced up to the latest. I am currently using Ubuntu 7.04 X64.
With the previous version of skype this would happen but it would be a good 20 minutes into the conversation.
I would gladly turn on logging or anything needed to track this. it takes around 4 seconds to the skype test call to reproduce.
Regards
Richard
Does it hang up and go back to the dial tone or just go silent ?
I'm using 1.4.0.74 as the 99 version breaks the usb sound devices. If you can go back to that, hopefully this will be fixed soon. If you still have the problem on that let me know
Simon
Hi Simon,
It just goes stright back to dail tone. Having looked through the logs it apparently has received a OFF command from the box!! Really not sure how / why but I think that it is skype version related as the 1.3 release seemed to have worked. Although it did hang up sometimes without warning
Sorry for being a noob, but can you tell me how to get the older version? I have not kept any as I have re-installed my system since just in case there was something horribly wrong with my layout
thanks
Richard
Can you post me the stuff in the message window when you start with
kb2kskype --debugmessages
cut out your contact names though as I don;t need them.
I did this in google, "index of" skype-1.4.0.74.deb
Try http://ftp.das.ufsc.br/pub/das/GNU-Linux/config/
Simon
Hi Simon,
thank you for your help this far. I have tried .79 version of Skype and have found that the problem does not occur in that version. I have therefore upgraded to re-create the situation, and have done so successfully.
Here is the output of the debug, all sectins marked [...] are sections that I have edited personal details.
---------------------
Skype instance found, window id 62914629
NAME B2K_CONNECTOR
PROTOCOL 7
OK
PROTOCOL 7
CONNSTATUS ONLINE
CURRENTUSERHANDLE beebock
SEARCH FRIENDS
USERSTATUS INVISIBLE
[...]
USB Device Found
USB Device startup error, trying again....
USB Device Found
USER beebock ONLINESTATUS OFFLINE
USERSTATUS OFFLINE
CONNSTATUS CONNECTING
HANDSET OFF
MINIMIZE
OK
CONNSTATUS ONLINE
USER beebock ONLINESTATUS INVISIBLE
USERSTATUS INVISIBLE
[...]
GROUP 23 NROFUSERS 2
USER linda_rae ONLINESTATUS NA
CALL 59 STATUS UNPLACED
CALL 59 STATUS ROUTING
HANDSET ON
FOCUS
FOCUS
OK
[...]
CALL 59 STATUS RINGING
CALL 59 VAA_INPUT_STATUS FALSE
CALL 59 STATUS INPROGRESS
CALL 59 DURATION 1
CALL 59 DURATION 2
CALL 59 DURATION 3
HANDSET OFF
SET CALL 59 STATUS FINISHED
MINIMIZE
HANDSET ON
FOCUS
FOCUS
CALL 59 STATUS FINISHED
OK
OK
CALL 59 STATUS FINISHED
CALL 66 STATUS UNPLACED
CALL 66 STATUS ROUTING
CALL 66 STATUS RINGING
CALL 66 VAA_INPUT_STATUS FALSE
CALL 66 STATUS INPROGRESS
CALL 66 DURATION 1
HANDSET OFF
SET CALL 66 STATUS FINISHED
MINIMIZE
HANDSET ON
FOCUS
FOCUS
CALL 66 STATUS FINISHED
OK
OK
CALL 66 STATUS FINISHED
HANDSET OFF
MINIMIZE
OK
------------------
above you can see the issue occuring. Call 66 and the one just before both had the same issue.
Here is the output of the terminal upon running kb2kskype --debugmessages
----------------
richard@richard-desktop:/usr/bin$ kb2kskype --debugmessages
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
----------------
Even though the errors are reported, the app has launched
Another piece of information that you may need. There is no PSTN line plugged into this installation. I have also installed all the lib32 compatable libraries for the 64 bit OS.
If there is anything else you need to know, please don't hesitate to ask.
Regards
Richard
Hold on. It seems that I found the problem and managed to fix it.
On my FC5 (dual core Intel), when a call was in progress, usbb2k sometimes registered mysterious keysrokes. These led to a variety of odd events like spontaneous hangups or missing keystrokes. It is quite possible that while ago another thread was discussing the same problem.
http://sourceforge.net/forum/forum.php?thread_id=1743127&forum_id=653443
Please, give me a day or two to test my fixes and I'll post them.
Dima
P.S. I can only provide source files. You will have to compile them for your environment. If your system is not Fedora Core or Red Hat, then you might need to port them.
Cool let me know how you go.
Is this in PSTN mode ? Aas that is what the thread you linked was talking about, or at least the changing mode between PSTN and USB.
Am I correct in assuming the problem you are talking about is unreleated to the new Skype problem that this thread was about ? as my fc is only running 1.3.
Simon
Hi Guys,
I am in USB mode only as I don't use the PSTN at all. There is a floor and a couple of walls between the phone socket and the pooter :|
Thanks
Richard
Simon, all problems - missing or spontaneous keypresses, occasional hangups, spontaneous calls to blank or non-existing destinations - all happened to me in USB mode. I might be wrong, but I have feeling that this thread was about the same or closely related issue:
http://sourceforge.net/forum/forum.php?thread_id=1743127&forum_id=653443
I found that USB modem was apparently busy (maybe timing of async polling loop in USB server thread caused stalls sometimes) and occasionally returned error flags along with garbage in data registers. The usbb2k driver did not filter these errors out and passed random keystrokes to client app.
I am running the latest Skype 1.4.0.99 and the skype itself is fine.
Not problems whatsoever, except that its functionality is limited compared to version 3.5, which is not available for Linux.
Dima
Richard, Simon
I posted the patch - please, let me know whether it helped or not.
Hi that thread was actually about trying to read from the socket before the connected signal had come back and some random keys during switch between usb and pstn.
I get the same issues you are talking about but only on 1.4.0.99. Skype 1.4.0.74 works 100% I'm hoping it might be something to do with Skype flooding the USB interface, as a result of agc. I'll see what happens in the next version of Skype and then look more. They are adding a disable option for it to the UI and other things.
One thing I never tested was to put the box into usb mode and then exit kb2kskype and stop usbb2k_api and then make a call using the Skype UI and see it the problem still happens. This would then mean it isn't anything wrong on my part it would mean either snd_usb_audio or Skype. Would you like to try for me ?
Richard glad you got everything working, let me know if you have any more problems.
Simon
Simon - inless I got it wrong, your idea won't work. How would I detect keypress errors if usbb2k_api were not running? I suggest trying my patch on systems with spontaneous telbox errors (a typical behavior under race conditions). What currently is happening in usbb2k driver is a typical race condition created by frequent reads from a slow USB device.
Hi Dima,
I have installed 2.2-4 of the USB API and the problem still exists.
Can you confirm that is the one that you uploaded?
Regards
Richard
Richard
Currently, I can only provide you with a patch, which is not in any release yet.
To use the patch, you need to download sources for both, 2.2-4 USB driver and 0.3.4 b2k controller. Once you have all source files installed and build environment configured, you may download the patch from:
http://sourceforge.net/tracker/download.php?group_id=186708&atid=918377&file_id=244477&aid=1789197
The patch contains updates for 3 files (diff outputs). Please, apply the updates, rebuild the source, install new executables, and restart driver and controller.
Dima
Hi Dima,
I'll play with that tonight.
Thanks
Richard
Dima,
YOU ARE A STAR
That has worked perfectly. I am going to test it for a little while and report any error back :)
If you don;t hear from me consider it FIXED!!
Regards
Richard
Hi Dima,
Thanks for the patches. The usbb2k-api one look good I see what you mean about the error checking. I assume the new version of Skype is flooding the audio endpoints that is causing the errors on the control endpoint that weren't there before in previous versions of Skype so I'll still blame Skype :) The audio is also still useless although it doesn't hang up anymore.
One question about the mixer patch I don't see any different apart from you added in a comma but the command works with and without it. I'm reluctant to change it, as knowing my look it will cause other problems, do you really need this patch ? If you use this from skype you have to drag the slider not just click it to fire the event, i tried the click but it made the GUI go very slow, due to the high number of system calls.
amixer -q -c 1 sset Mic 0 25% cap
check in alsamixer, it changed.
amixer -q -c 1 sset Mic,0 50% cap
check in alsamixer it changed.
amixer -q -c 1 sset Mic 0 75% cap
check in alsamixer it changed.
I'll post the updated code as soon as you anser the sound issue
Thanks for the help
Simon
Hi Simon - mixer patch 1787984 is not mine.
It is signed by Jose Alberto.
Dima
About the mixer patch:
[root@jar ~]# amixer -c 1 sset Mic 1 25% cap
Simple mixer control 'Mic',0
Capabilities: cvolume cswitch cswitch-joined
Capture channels: Mono
Limits: Capture 0 - 65534
Mono: Capture 16384 [25%] [-127.99dB] [on]
[root@jar ~]# amixer -c 1 sset Mic,1 25% cap
Simple mixer control 'Mic',1
Capabilities: cvolume cswitch cswitch-joined
Capture channels: Mono
Limits: Capture 0 - 65534
Mono: Capture 16384 [25%] [-127.99dB] [on]
[root@jar ~]#
Look at Simple mixer control
Jose alberto
Jose I see your point, thanks for the patch it has been included in the new version.
Simon