Distro: OpenSUSE 10.2 (i586)
Kernel: 2.6.18.2-34 SMP
Skype: 1.4.0-74
Progs: kb2kskype-0.3.4a (built from source) and usbb2k-api-mod-2.2-2.suse10-2.i586.rpm
(note: same issue with 0.3.3)
Alsa modules: snd_pcm_oss snd_mixer_oss snd_cmipci snd_opl3_lib snd_mpu401_uart snd_usb_audio snd_pcm snd_timer snd_page_alloc snd_usb_lib snd_rawmidi snd_seq_device snd_hwdep snd soundcore
Alsa rev: 1.0.13
Modprobe.conf (note that I had unsucessfully been playing w/ bt drivers before switching to kb2k):
install char-major-116 snd
# OSS/Free portion
alias char-major-14 soundcore
# This is your normal sound card.
alias snd-card-0 snd_cmipci
# This is the new part
alias snd-card-1 snd-bt-sco
alias snd-card-2 snd-usb-audio
## OSS/Free portion
alias sound-slot-0 snd-card-0
alias sound-slot-1 snd-card-1
# Add the following lines if necessary
alias sound-service-1-0 snd-mixer-oss
alias sound-service-1-1 snd-seq-oss
alias sound-service-1-3 snd-pcm-oss
alias sound-service-1-8 snd-seq-oss
alias sound-service-1-12 snd-pcm-oss
> If you add the user running Skype to that group, it should get access to the sound system.
I could get Skype to see the sound devices as a non root user. Just putting my username into the audio group in /etc/group wasn't enough. I had to change permissions in /dev/snd. But, I still had to run usbb2k as root, and when I tried to answer a call, Skype would complain the sound device wasn't working.
In stracing why I couldn't run usbb2k as a non-root user, I saw it needed to modify /var/run/usbb2k_api.pid, so I figured it was intended to run as root.
I tried running skype as a regular user and both usbb2k and kb2kskype as root, and still, skype complained that the audio device wasn't working. So, I guess I still have something messed-up in my device permissions.
>The ring pattern syntax is described in the documentation (under the Help button from the kb2kskype GUI).
That button is also broken... it launches SuSEHelp, which complains:
"An error occurred while loading http:/susehelp/index.html.en:
No hostname specified."
...SuSEHelp may be broken in general, I don't ever use it.
>can you confirm that you are using a B2K telbox or a p1k phone ?
I believe it's the B2K Telbox. It has POTS in, tele out, and USB ports, and three LED's on the box, and dmesg contains:
usb 2-3: Manufacturer: Yealink Network Technology Ltd.
input: Yealink usb-p1k as /class/input/input4
usbcore: registered new driver yealink
drivers/usb/input/yealink.c: Yealink phone driver:yld-20051230
drivers/usb/input/yealink.c: urb_irq_callback - urb status -108
drivers/usb/input/yealink.c: urb_ctl_callback - usb_submit_urb failed -90
>If you pick up the phone and press * to switch to USB does it always change ?
This is getting too strange. That no longer works today. It worked fine yesterday (I'm fairly certain). Now, I have to manually switch. I don't think the GUI ever auto-changed which mode was selected, but I used to get a dial tone after pressing the "*"; now, I don't get the dial tone and need to switch selection to USB on the GUI in order to dial out or pick-up a call.
As these sorts of degrading issues go: I've upgraded kb2k, I've applied some security patches from SuSE (no kernel patches, nothing that should get in the way), I've modified some skype notifications (i.e. to ring the regular soundcard on incoming calls), and modified permissions on some sound devices.
I've tried down-grading to 3.3.3 and changing USB ports... does not help.
The tools/test_usbb2k.py seems to work, while the api_connect script segfaults.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
usbb2k_api must be run as root, and there are startup scripts to do this on boot because it needs to bind to the usb device.
skype and kb2kskype should be run as the same user. kb2kskype should be started after skype and after you are logged in or you will need to press refresh in the contact list, this is due to a change in the skype api, I'm working on a better way of doing this.
Have you tried all available devices in skype, I think I'm shown 2 for the box and its the second one that works? (i'm not at my desktop to check at the moment.)
When you next start kb2kskype do it from the run dialog or the command line and add --debugmessages, this should show you messages to and from skype and the b2k box. can you post any error messages or the whole thing (comment out your contact list) you get and also tell me the color of the text for that message.
are you starting api_connect like the line below when it segfaults ?:
api_connect /tmp/usbb2k.sock
Custom Ring Tone (from website)
The driver allows you to make up your own ring tone, but you only have on and off notes, so you can't do anything amazing, but its a nice feature. Enter a text string in the gui e.g. DbDt and click set. The text translates to A/a=0.1s, Y/y=2.5s, UPPER CASE means ring, lower case means don't ring Z/z is 'stop here', ie, only do one ring loop, give AaAaAx a try! DbDt is the default UK ring tone.
The docs seem to go in the wrong place on some distributions, if you want to try and fix it get the source code and uninstall it by doing configure, make, make uninstall. The run configure --prefix=/usr make, make install.
Good luck
Simon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
> usbb2k_api must be run as root... skype and kb2kskype should be run as the same user.
I'm currently running everything as root.
> Have you tried all available devices in skype?
Yes, both. The later works ("plughw" in the name).
> are you starting api_connect like the line below when it segfaults ?
oops, that fixed api_connect... I didn't have a clue what I was running or how to run it.
> --debugmessages, this should show you messages to and from skype and the b2k box. can you post any error messages or the whole thing (comment out your contact list)
Here goes... I called out and in, etc... no big errors:
Skype instance found, window id 52428859 (red)
NAME B2K_CONNECTOR (green)
USB Device Found (red)
PROTOCOL 7 (green)
OK (dark red)
PROTOCOL 7 (dark red)
CONNSTATUS ONLINE (dark red)
SEARCH FRIENDS (green)
USERSTATUS ONLINE
USB Device startup error, trying again.... (red)
USB Device Found (red)
HANDSET OFF (blue)
MINIMIZE (green)
OK (dark red)
HANDSET OFF (blue)
MINIMIZE (green)
OK (dark red)
HANDSET OFF (blue)
MINIMIZE (green)
OK (dark red)
HANDSET ON (blue)
FOCUS (blue)
FOCUS (green)
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK
CALL
CALL
CALL
OK (dark red)
CALL 280 STATUS UNPLACED (dark red)
CALL 280 STATUS ROUTING (dark red)
CALL 280 FAILUREREASON 7 (dark red)
CALL 280 STATUS FAILED (dark red)
CALL 280 VAA_INPUT_STATUS FALSE (dark red)
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK (dark red)
CALL 286 STATUS UNPLACED (dark red)
CALL 286 STATUS ROUTING (dark red)
CALL 286 FAILUREREASON 7 (dark red)
CALL 286 STATUS FAILED (dark red)
CALL 286 VAA_INPUT_STATUS FALSE (dark red)
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK
CALL 289 STATUS UNPLACED (dark red)
CALL 289 STATUS ROUTING (dark red)
CALL 289 STATUS RINGING (dark red)
CALL 289 VAA_INPUT_STATUS FALSE (dark red)
CALL 289 STATUS INPROGRESS (dark red)
CALL 289 DURATION 1 (dark red)
CALL 289 DURATION 2 (dark red)
CALL 289 DURATION 3 (dark red)
CALL 289 DURATION 4 (dark red)
CALL 289 DURATION 5 (dark red)
CALL 289 STATUS FINISHED (dark red)
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK
HANDSET OFF
MINIMIZE
HANDSET ON
FOCUS
FOCUS
OK
OK
Unknown Key: KEY 1c
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK
Unknown Key: KEY 1d (red)
CALL (blue)
CALL (green)
OK
HANDSET OFF
SET CALL 289 STATUS FINISHED (green)
MINIMIZE
ERROR 24 Cannot hangup inactive call (dark red)
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK
CALL (blue)
CALL ... (blue)
CALL ... (green)
OK
CALL 296 STATUS UNPLACED (dark red)
CALL 296 STATUS ROUTING (dark red)
CALL 296 RATE 0 (dark red)
CALL 296 RATE_PRECISION 3 (dark red)
CALL 296 RATE_CURRENCY USD (dark red)
CALL 296 STATUS RINGING (dark red)
CALL 296 STATUS EARLYMEDIA (dark red)
CALL 296 VAA_INPUT_STATUS FALSE (dark red)
HANDSET OFF (blue)
SET CALL 296 STATUS FINISHED (dark red)
MINIMIZE (green)
CALL 296 STATUS CANCELLED (dark red)
OK (dark red)
CALL 296 STATUS CANCELLED
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK
HANDSET OFF
MINIMIZE
OK
CALL 304 STATUS RINGING
CALL 304 CONF_ID 0
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET ON
SET CALL 304 STATUS INPROGRESS
FOCUS
FOCUS
CALL 304 STATUS INPROGRESS
OK
CALL 304 STATUS INPROGRESS
CALL 304 VAA_INPUT_STATUS FALSE
CALL 304 DURATION 1
CALL 304 STATUS FINISHED
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK
Unknown Key: KEY 1c
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
By the way do you still get the no max_periods error ? if not you might want to post back in the Skype forum thread to save the developers some effort.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Distro: OpenSUSE 10.2 (i586)
Kernel: 2.6.18.2-34 SMP
Skype: 1.4.0-74
Progs: kb2kskype-0.3.4a (built from source) and usbb2k-api-mod-2.2-2.suse10-2.i586.rpm
(note: same issue with 0.3.3)
Alsa modules: snd_pcm_oss snd_mixer_oss snd_cmipci snd_opl3_lib snd_mpu401_uart snd_usb_audio snd_pcm snd_timer snd_page_alloc snd_usb_lib snd_rawmidi snd_seq_device snd_hwdep snd soundcore
Alsa rev: 1.0.13
Modprobe.conf (note that I had unsucessfully been playing w/ bt drivers before switching to kb2k):
install char-major-116 snd
# OSS/Free portion
alias char-major-14 soundcore
# This is your normal sound card.
alias snd-card-0 snd_cmipci
# This is the new part
alias snd-card-1 snd-bt-sco
alias snd-card-2 snd-usb-audio
## OSS/Free portion
alias sound-slot-0 snd-card-0
alias sound-slot-1 snd-card-1
# Add the following lines if necessary
alias sound-service-1-0 snd-mixer-oss
alias sound-service-1-1 snd-seq-oss
alias sound-service-1-3 snd-pcm-oss
alias sound-service-1-8 snd-seq-oss
alias sound-service-1-12 snd-pcm-oss
> If you add the user running Skype to that group, it should get access to the sound system.
I could get Skype to see the sound devices as a non root user. Just putting my username into the audio group in /etc/group wasn't enough. I had to change permissions in /dev/snd. But, I still had to run usbb2k as root, and when I tried to answer a call, Skype would complain the sound device wasn't working.
In stracing why I couldn't run usbb2k as a non-root user, I saw it needed to modify /var/run/usbb2k_api.pid, so I figured it was intended to run as root.
I tried running skype as a regular user and both usbb2k and kb2kskype as root, and still, skype complained that the audio device wasn't working. So, I guess I still have something messed-up in my device permissions.
>The ring pattern syntax is described in the documentation (under the Help button from the kb2kskype GUI).
That button is also broken... it launches SuSEHelp, which complains:
"An error occurred while loading http:/susehelp/index.html.en:
No hostname specified."
...SuSEHelp may be broken in general, I don't ever use it.
>can you confirm that you are using a B2K telbox or a p1k phone ?
I believe it's the B2K Telbox. It has POTS in, tele out, and USB ports, and three LED's on the box, and dmesg contains:
usb 2-3: Manufacturer: Yealink Network Technology Ltd.
input: Yealink usb-p1k as /class/input/input4
usbcore: registered new driver yealink
drivers/usb/input/yealink.c: Yealink phone driver:yld-20051230
drivers/usb/input/yealink.c: urb_irq_callback - urb status -108
drivers/usb/input/yealink.c: urb_ctl_callback - usb_submit_urb failed -90
>If you pick up the phone and press * to switch to USB does it always change ?
This is getting too strange. That no longer works today. It worked fine yesterday (I'm fairly certain). Now, I have to manually switch. I don't think the GUI ever auto-changed which mode was selected, but I used to get a dial tone after pressing the "*"; now, I don't get the dial tone and need to switch selection to USB on the GUI in order to dial out or pick-up a call.
As these sorts of degrading issues go: I've upgraded kb2k, I've applied some security patches from SuSE (no kernel patches, nothing that should get in the way), I've modified some skype notifications (i.e. to ring the regular soundcard on incoming calls), and modified permissions on some sound devices.
I've tried down-grading to 3.3.3 and changing USB ports... does not help.
The tools/test_usbb2k.py seems to work, while the api_connect script segfaults.
usbb2k_api must be run as root, and there are startup scripts to do this on boot because it needs to bind to the usb device.
skype and kb2kskype should be run as the same user. kb2kskype should be started after skype and after you are logged in or you will need to press refresh in the contact list, this is due to a change in the skype api, I'm working on a better way of doing this.
Have you tried all available devices in skype, I think I'm shown 2 for the box and its the second one that works? (i'm not at my desktop to check at the moment.)
When you next start kb2kskype do it from the run dialog or the command line and add --debugmessages, this should show you messages to and from skype and the b2k box. can you post any error messages or the whole thing (comment out your contact list) you get and also tell me the color of the text for that message.
are you starting api_connect like the line below when it segfaults ?:
api_connect /tmp/usbb2k.sock
Custom Ring Tone (from website)
The driver allows you to make up your own ring tone, but you only have on and off notes, so you can't do anything amazing, but its a nice feature. Enter a text string in the gui e.g. DbDt and click set. The text translates to A/a=0.1s, Y/y=2.5s, UPPER CASE means ring, lower case means don't ring Z/z is 'stop here', ie, only do one ring loop, give AaAaAx a try! DbDt is the default UK ring tone.
The docs seem to go in the wrong place on some distributions, if you want to try and fix it get the source code and uninstall it by doing configure, make, make uninstall. The run configure --prefix=/usr make, make install.
Good luck
Simon
> usbb2k_api must be run as root... skype and kb2kskype should be run as the same user.
I'm currently running everything as root.
> Have you tried all available devices in skype?
Yes, both. The later works ("plughw" in the name).
> are you starting api_connect like the line below when it segfaults ?
oops, that fixed api_connect... I didn't have a clue what I was running or how to run it.
> --debugmessages, this should show you messages to and from skype and the b2k box. can you post any error messages or the whole thing (comment out your contact list)
Here goes... I called out and in, etc... no big errors:
Skype instance found, window id 52428859 (red)
NAME B2K_CONNECTOR (green)
USB Device Found (red)
PROTOCOL 7 (green)
OK (dark red)
PROTOCOL 7 (dark red)
CONNSTATUS ONLINE (dark red)
SEARCH FRIENDS (green)
USERSTATUS ONLINE
USB Device startup error, trying again.... (red)
USB Device Found (red)
HANDSET OFF (blue)
MINIMIZE (green)
OK (dark red)
HANDSET OFF (blue)
MINIMIZE (green)
OK (dark red)
HANDSET OFF (blue)
MINIMIZE (green)
OK (dark red)
HANDSET ON (blue)
FOCUS (blue)
FOCUS (green)
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK
CALL
CALL
CALL
OK (dark red)
CALL 280 STATUS UNPLACED (dark red)
CALL 280 STATUS ROUTING (dark red)
CALL 280 FAILUREREASON 7 (dark red)
CALL 280 STATUS FAILED (dark red)
CALL 280 VAA_INPUT_STATUS FALSE (dark red)
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK (dark red)
CALL 286 STATUS UNPLACED (dark red)
CALL 286 STATUS ROUTING (dark red)
CALL 286 FAILUREREASON 7 (dark red)
CALL 286 STATUS FAILED (dark red)
CALL 286 VAA_INPUT_STATUS FALSE (dark red)
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK
CALL 289 STATUS UNPLACED (dark red)
CALL 289 STATUS ROUTING (dark red)
CALL 289 STATUS RINGING (dark red)
CALL 289 VAA_INPUT_STATUS FALSE (dark red)
CALL 289 STATUS INPROGRESS (dark red)
CALL 289 DURATION 1 (dark red)
CALL 289 DURATION 2 (dark red)
CALL 289 DURATION 3 (dark red)
CALL 289 DURATION 4 (dark red)
CALL 289 DURATION 5 (dark red)
CALL 289 STATUS FINISHED (dark red)
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK
HANDSET OFF
MINIMIZE
HANDSET ON
FOCUS
FOCUS
OK
OK
Unknown Key: KEY 1c
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK
Unknown Key: KEY 1d (red)
CALL (blue)
CALL (green)
OK
HANDSET OFF
SET CALL 289 STATUS FINISHED (green)
MINIMIZE
ERROR 24 Cannot hangup inactive call (dark red)
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK
CALL (blue)
CALL ... (blue)
CALL ... (green)
OK
CALL 296 STATUS UNPLACED (dark red)
CALL 296 STATUS ROUTING (dark red)
CALL 296 RATE 0 (dark red)
CALL 296 RATE_PRECISION 3 (dark red)
CALL 296 RATE_CURRENCY USD (dark red)
CALL 296 STATUS RINGING (dark red)
CALL 296 STATUS EARLYMEDIA (dark red)
CALL 296 VAA_INPUT_STATUS FALSE (dark red)
HANDSET OFF (blue)
SET CALL 296 STATUS FINISHED (dark red)
MINIMIZE (green)
CALL 296 STATUS CANCELLED (dark red)
OK (dark red)
CALL 296 STATUS CANCELLED
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK
HANDSET OFF
MINIMIZE
OK
CALL 304 STATUS RINGING
CALL 304 CONF_ID 0
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET ON
SET CALL 304 STATUS INPROGRESS
FOCUS
FOCUS
CALL 304 STATUS INPROGRESS
OK
CALL 304 STATUS INPROGRESS
CALL 304 VAA_INPUT_STATUS FALSE
CALL 304 DURATION 1
CALL 304 STATUS FINISHED
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK
HANDSET OFF
MINIMIZE
OK
HANDSET ON
FOCUS
FOCUS
OK
Unknown Key: KEY 1c
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
HANDSET OFF
MINIMIZE
OK
I am such an idiot!
I had tried the yealink driver that came with the box, and couldn't get it to work... so I switched to the kb2Kskype... which worked.
Somehow, the yealing driver got loaded after a reboot last week... and has been fighting for control.
All works fine.
I do have another issue (when on a skype call and a pots call comes in; skype gets disconnected), but I'll see if I can find a work-around first.
Sorry to raise a non-issue.
I'm glad you found it.
I'm sure Frank will take a look at the other issue you have.
Simon
By the way do you still get the no max_periods error ? if not you might want to post back in the Skype forum thread to save the developers some effort.