Skype Community > USB-B2K basic Software

Pages: 1, 2, 3, 4

Simon_6162

Sat Oct 28 2006, 19:02

EDIT
There is now a website for this project here Please post questions and problems at the end of this thread.
end edit

Hello,

I've written some software that takes the x11 api example application provided by Skype and uses it to connect to a yamamoto easy blue b2k box. (this should do all b2k boxes though)

The software is in 2 parts, 1 the usb deamon written by someone else, and 2 is a small gui that connects to skype and the usb driver and is written by myself.

DRIVER: here
The driver is a slight mod of the original available at the link below, all I changed was a chmod to the socket that gets created, this means that my gui can be run from a normal user. The link below is so you can ask them for help about getting it to work

Please use my version for this application.
original: http://savannah.nongnu.org/projects/usbb2k-api/

To install the deamon download from the driver link above, extract, then run configure and make make then you need to run the application in src/usbb2k_api as root (do this on startup when its all working correctly). Test the driver first by using the simple program in the tools folder, the readme explains what to do for this, PLEASE read it and if you have problems look at the authors website.

To use my application download it from
SOFTWARE: here
extract the file and do the usual configure make make install.
To run the application type kb2kskype

If you want to have it minimized to the system tray use kdocker. (or an equlivant).

This software requires QT,kdelibs,libusb,automake,make,g++,gcc,.

USAGE
To use the software first start skype then launch kb2kskype. The application lets you change the mode of the box, and passes button presses from the phone to skype.

To make a call pick up the handset dial the number and then press the # key when your done hang up. If you make a mistake hang up the phone and pick it up again.

To change to pstn mode dial **# then hang up (not sure how to switch back again tho.)(any one have an idea?)

The box and phone should ring when you get an incoming call on skype, pick up the phone to answer the call.

KNOWN PROBLEMS
Skype for linux doesn't have speed dials yet and I'm not writing them. Please add them in the next build:)

My box currently doesn't work too well with alsa it locks up the sound after 1 call and requires skype to be restarted, using OSS is fine apart from a slight echo (I can live with that!)

If you spot any bug or have feature request post here, I might get round to doing them at some point but I quite busy with work at the minute.

Feel free to edit the code yourself and improve it I haven't had the time to put the effort in, but it works for me on FC5, also on FC6.

Regards

Simon Dible

p.s. Thanks to the guys at skype for the demo application, good choice with the x windows messageing I like it.) and thanks for the guys who wrote the b2k driver I'll get round to emailing you about the socket permissions at some point!!

Simon_6162

Tue Oct 31 2006, 18:20

Note that the link in the post above has been updated to fix some bugs i found. These are:

The main window now minimises on hang up.
Skype cancels outgoing calls when you hang up the phone.
The change to pstn now works.

updatelee

Mon Nov 27 2006, 05:24

awesome, works great with my FT-102 in gentoo.

thanks !

Juuso Alasuutari

Thu Nov 30 2006, 18:20

Hi, you replied to my thread (http://forum.skype.com/index.php?showtopic=69319), so I thought I'd reply to yours.

I tried out your app before starting to write my own -- actually you inspired me

. Your program is nice, but I wanted something without any extra dependencies (Qt, kdelibs). I also plan to keep mine as a text-mode app, and without audio controls. (I favor the Unix philosophy that a program should only do one thing and do it well, and there's already alsamixer.)

Another reason for writing my own app is because I wanted to make use of D-Bus. I plan to add the option to use X11 messaging, though, partly because I suspect there might be a bug in Skype's D-Bus code. I suppose you haven't experienced a problem where Skype just stops sending protocol messages at some point? I hope not, and I hope the bug's in my code (so there's a chance to fix it).

I haven't studied your code thoroughly yet, but I plan to do so when I need to know how to send and receive X11 messages. In the mean time I think we should collaborate by sharing overall info and experiences. Here's what I'm working on now:

Handling Skype events -- especially simultaneous/overlapping calls -- in relation to B2K events is a minor logistical puzzle. I'm going to implement an option to answer an incoming call while the previous one is in progress, and to switch between several simultaneous calls. In my plan you could have one call active at a time, and the others would be held. So if you're talking on the phone (CALL 1) and another call starts ringing in the background (CALL 2), pressing * will issue SET CALL 1 ONHOLD and SET CALL 2 INPROGRESS. And when you again press *, call 2 will be put on hold and call 1 resumed. (The same applies for any number of calls, they will be cycled through in order. I will implement a call queue for that purpose.)

If you want to I can write up some pseudocode, or maybe I'll just put my unfinished code online soon -- work stuff has kept me tied up for the past few weeks, but I'll try to make time for this, too.

Oh, forgot to mention: I think I'm going to call my program SkypeGate. So that one's taken now.

Simon_6162

Sun Dec 3 2006, 15:28

Hi that was a very quick reply, its a shame my email isn't so quick at telling me there was a reply.

I'm glad I inspired you to start your app and I agree with your idea of doing it without the requirements for QT (it shouldn't need kdelibs that is probably me getting the automake script wrong! I will look into this).

I haven't noticed the d-bus bug you were talking of in x11, and I can't test it out for you in d-bus as I don't have the correct version of d-bus on my system, which was my reason for the x11 messageing. My x11 code was directly from the skype demo application and just reworked into some threads, but feel free to use what you like.

I like the plan for multiple calls I didn't think about that, also I have no idea what happens when you get a PSTN call and you are in the USB call, so any pointers on what to do there might be useful, I don't have a PSTN line any more so I can't do any testing. The one problem that i can see is that you might get issues when you start to use automated phone services (like calling your bank and you have to type in the card number etc.) as these require you to use the * and # keys to get around their menu systems, so maybe a command line switch for enableing call waiting features would be useful.

As for implementing it I guess you just need a call stack and loop round it and just store the next available slot and currently active slot in to other variables. place the current call on hold and answer the new one. Let me know how you get one with it.

Is there any chance you could show my what your b2k box is listed as in alsa by doing
cat /proc/asound/cards
I'm trying to find a card way of identifying the card number as mine moves about as i have a few usb sound card devices.

Good luck and good name for the program, let me know if you need any help or testing

Simon

alatariel

Mon Dec 11 2006, 09:37

Seems to finally work for me too now ...

Switched to Kubuntu 6.10 and installed your driver-solution
and after some more hours of tweaking it seemed to work like a charm ...

(among minor hiccups I could mention are
that make install had some problems which I fixed with manual placement and linking of the binaries;
and that I had to do some shellscripting to get skype up and running at autologin under KDE and after some delay the B2K-control-app too)

one thing which was causing more serious troubles was that the alsa-mixer wasn't set up correctly initially ... and that OTHER mixers like kmix continually reset the values for the mic(s?) and speaker(s?)
[I don't know why everything is detected TWICE on the USB-B2K but it seems to work so it's a minor problem]
- so that basically noone could hear me and i not too well either ... But

* running alsamixer a first time - for both the normal soundcard (-c 0 in my case) and the USB-B2K (-c 1 in my case)
* running alsactl names (to save the hardware names)
* running alsamixer -c 1 once again to double-check that all four devices (two output, two input devices) were set up correctly
* saving the info with alsactl store 0 (and 1 respectively)
seems to have done the trick ...

will continue to test this solution, but it seemed to work exactly as I had hoped! thanks a bunch for it!!!!

links that could be useful to others:
http://knowledge76.com/index.php/Guide_to_Sound_Problems
http://alsa.opensrc.org/index.php?page=MultipleCards

Simon_6162

Mon Dec 11 2006, 11:17

Thanks for the feedback and the links, I didn't realise you could use the alias to force the card number, that had been annoying me for quite a while now.

Could you post me the output of

CODE

cat /proc/asound/cards

I'm trying to find a card way of identifying the card number so i can add a mixer control, which will save others having the problem you had, with the sound levels. I have had trouble with kmix as well for this device but i did notice alsamixer worked fine.

danci1973

Tue Dec 12 2006, 15:48

Hi,

I have an USB SPEAKER PHONE USB-P4K. Using 'lsusb' it is identified as 'Bus 003 Device 006: ID 6993:b001 Freshtel FT-102 VoIP USB Phone', however when I connect it to USB, I get:

hiddev96: USB HID v1.00 Device [Yealink Network Technology Ltd. VOIP USB Phone ] on usb-0000:00:03.1-3

Anyway, is this supposed to work with your 'usbb2k-api'? When I connect to api, all I get is:

Connected.
SEND> RECV> USB DEVICE FOUND 010
RECV> HANDSET OFF

There is no reaction to commands (like 'RING 1') or pressing the keys on the phone...

Thanks, D.

PS: Forgot to mention that audio devices seem to work well - if I connect to other users via Skype, I can talk to them...

d9t

Thu Dec 28 2006, 10:59

Excellent work Simon

I got this working easily with Gentoo.. Using skype from portage (accepting ~x86 keywords, i believe the version i have install is masked - 1.3.0.53)

Works fine, except for one problem - when calling the test call, the robot (person im calling) sounds fine, but when i hear myself being played back, its hugely slow, my voice sounds really slowed down.

I've tested this a few times, with the same result.

Also, on my first call I clicked hang up on the phone instead of on skype first, which seemed kb2kskype to become unresponsive briefly (blacked out in beryl) and the crashed when i tried to minimize it.. But skype still works

Below is the console output from kb2skype:

CODE

~$ kb2kskype
Xlib: unexpected async reply (sequence 0x54d) !
In file kernel/qpixmap_x11.cpp, line 633: Out of memory
Segmentation fault

Edit/update:
I updated my kernel and after rebooting, the delay is gone.. I'm not sure if this is just coincidence from trying skype/rebooting but I did add OSS emulation.

However, I'm still have an odd issue where the 'dial tone' when I first pick up the phone stays there for duration of the call, instead of going away once skype starts dialing. I've tried starting the call, then picking up the phone, and other possible combinations.. But it will always be there over the call, unless kb2kskype crashed, or if I kill it while it's in USB mode.. then calls work perfectly, but no dial tone when I pick up the phone.. No big deal, it's kind of nice starting kb2kskype then killing it so I dont have an extra window around

I'm on xfce4 btw.

alatariel

Thu Dec 28 2006, 21:24

sure, here's the output of
cat /proc/asound/cards

CODE

0 [Live           ]: EMU10K1 - SB Live 5.1
                      SB Live 5.1 (rev.7, serial:0x80641102) at 0xa000, irq 11
1 [default        ]: USB-Audio - VOIP USB Phone
                      Yealink Network Technology Ltd. VOIP USB Phone            at usb-0000:00:07.2-2

alatariel

Sun Jan 7 2007, 11:24

for what it is worth

- I'm posting them here - feel free to critizise, use, whatever

I THINK I finally set up the system nice and proper - including these shellscripts ...
(that is a server with one auto-logged in person where skype and this stuff should start automatically at boot and be shut down properly at a reboot)

setup:
Kubuntu 6.10
the USB-B2K software is installed to (or symlinked at least in) /usr/local/bin (too much of a FreeBSD user I guess

...)

the shellscript in /etc/init.d
(make sure that it is run in the proper runlevels! if you have chkconfig installed, use that. I had to resort to the graphical way in Kubuntu to make sure it is run wherever there is graphical environment and network)

CODE

#! /bin/sh
### BEGIN INIT INFO
# Provides:          usbb2k_api
# Required-Start:
# Required-Stop:
# Should-Start:
# Should-Stop:
# Default-Start:
# Default-Stop:
# Short-Description: init the usbb2k_api
# Description:
### END INIT INFO

PATH=/sbin:/bin:/usr/bin:/usr/local/bin:/home/theuser/bin

do_start() {
    #
    # create the socket in /tmp
    #
        /usr/local/bin/usbb2k_api & > /dev/null 1>&2
    sleep 5
}

case "$1" in
  start)
    do_start
;;
  restart|reload|force-reload)
    echo "Error: argument '$1' not supported" >&2
    exit 3
;;
  stop)
    killall kb2kskype > /dev/null 1>&2
    killall skype > /dev/null 1>&2
    if [ -e /var/run/usbb2k_api.pid ]; then
        kill `cat /var/run/usbb2k_api.pid` > /dev/null 1>&2
        sleep 5
        rm /var/run/usbb2k_api.pid > /dev/null 1>&2
    fi
    sleep 3
    if [ -e /tmp/usbb2k.sock ]; then
        rm /tmp/usbb2k.sock > /dev/null 1>&2
    fi
    exit 0
;;
  *)
    echo "Usage: usbb2k_api [start|stop]" >&2
    exit 3
;;
esac

placed a symlink in /home/theuser/.kde/Autostart
to
/home/theuser/bin/skype.sh
which goes as follows:

CODE

#!/bin/bash

/home/theuser/skype/skype& > /dev/null 1>&2
sleep 20
/usr/local/bin/kb2kskype& > /dev/null 1>&2
sleep 5
exit 0

maybe trivial - but maybe someone has a need for it

(and of course theuser is not called theuser here

...)

Simon_6162

Mon Jan 8 2007, 15:07

alatariel
Thanks for the shell start scripts they look nice, I'll try them later.

I plan to set up a site later this week with some of the info from this board on, I'll post a link to this thread on it, and use your scripts as well if you don't mind.

I have a new version that adds sound control so it now does everything the windows app does. I'll post this later in the week as well. To do the sound control it calls amixer on the command line so you will need this installed if you want sound controls, but it isn't a requirement!

Thanks for the feedback on the device names that was what I was hopeing for!

d9t the dial tone goes away when you press a key on the phone. This is the hardware and i can't work out how to fake a key press to fix this, so if you dial echo123 on the skype interface just press 1 on your phone and the dial tone goes off. Also are you still getting the crash problem? I know what might be causing this but its a pain to fix and I haven't had it happen to me more than once.

One thing I will say is I use kdocker so the app isn't on the screen the whole time it sits in the system tray.
see http://kdocker.sourceforge.net/ there are other simillar progs around as well.

CODE

kdocker -l kb2kskype

danci1973
The usbb2k-api isn't my code so I don't fully know how it works I put the link for the origional authors in my first post, for what you say it does sound like it should work, but as I don't have that phone I can't really try. Have you tried sending the command to switch to usb mode first? eg. using api_connect type SWITCH USB then try RING 1.

EDIT:
I just looked on the usbbk2-api web site and there is mention of the p4k and the use of an extra module first see here , maybe give that a try and if you want any extra commands sending from skype to it let me know what they are and I can add them.

Simon

bod7777

Mon Jan 8 2007, 22:34

I'm looking forward to the info as I would love to get skypmate running on my ubuntu system.

Thanks for the work you all have done on this.

notariaugusto

Thu Jan 11 2007, 23:56

Hello!

do you know if your sofware runs with 06e6:c31c Tiger Jet Network, Inc, a usb adapter sold by www.cuphone.com? i already have sound correctly, but cannot dial and the linux driver they provide doesn't work under ubuntu.

thanks in advance,

Paolo

Simon_6162

Fri Jan 12 2007, 13:15

QUOTE(notariaugusto @ Thu Jan 11 2007, 23:56) [snapback]342959[/snapback]

I don't think it will assuming that the 06e6:c31c is the usb product id. This driver looks for the device listed below. You could try changing it to your vendor/product id but I doubt it will be that simple.
#define telbox_idVendor 0x6993
#define telbox_idProduct 0xb001

alatariel

Sun Jan 14 2007, 01:28

QUOTE(Simon_6162 @ Mon Jan 8 2007, 15:07) [snapback]341145[/snapback]

Sure, feel free to use them

you might have to edit them a bit though, for example I guess it's not need to sleep THAT much on faste systems

I could mail you a link to a document I've written where I have tried to summarize how I managed to set up the stuff I needed ...

Simon_6162

Sun Jan 14 2007, 01:41

alatariel that would be useful my email address is in the source code. The site I have set up is quite biased towards fedora as thats all I have, so i will add in your notes.

The site is now on sourceforge at
http://kb2kskype.sourceforge.net/index.html

There is also a new version of k2bskype and the usbb2k-api with some bug fixes like the dial tone now goes on and off and I've added in ring tone support that was already in the driver. There is also a volume control although it isn't the best. You will need to remove the old version of usbb2k_api and install the latest version. You should be able to install kb2kskype over its self without any problems

I also changed your init scripts slightly. let me know if they cause you any problems. and let me know of any new bugs i might have caused.

Simon

alatariel

Sun Jan 14 2007, 13:39

Simon: you should have gotten some mails now ... they DO cause some troubles

and I still can't rely on the system booting correctly it seems

... more often than not I either get some weird notions in the logfiles from the yealink driver itself or else programs like yours or skype might crash ...
it's basically a plain vanilla Kubuntu fresh install (re-installed yesterday to try some theories) with most of the "office" and "gaming" and "graphics/multimedia applications" stuff removed ...

and BTW, my telbox is this one ...
http://www.clasohlson.se/Product/Product.aspx?id=386735
a grey one, but they do sell it under their own name with a custom information leaflet ...

edit: I might add that NetBSD (in the form of the ghost4unix/g4u-NetBSD-based cd) found the device as

QUOTE

uaudio0 at uhub1 port 1 configuration 1 interface 0: Yealink Network Technology Ltd. VOIP USB Phone, rev. 2.00/0.00, addr 2
uaudio0: audio rev. 1.00
audio1 at uaudio0: full duplex, independant
uhiddev0 at uhub1 port 1 configuration 1 interface 3
uhiddev0: Yealink Network Technology Ltd. VOIP USB Phone, rev. 2.00/0.00, addr 2, iclass 3/0
uhid0 at uhiddev0: input=16, output=16, feature=0

(looking through the code in both projects though I guess it will get HARD to port to FreeBSD or any other BSD

:-/, but well, as lonkg as I could get the server working under anything NOT Micro$oft I'd be glad ...)

ivowelch

Sun Jan 21 2007, 03:10

QUOTE(Simon_6162 @ Tue Oct 31 2006, 18:20) [snapback]314132[/snapback]

hi simon: thanks for having written this. the yeatech skypemate is useless, because it requires a 32bit (not a 64bit) machine.

you may not want to make the install more robust, in which case you may want to ignore this email. I am running gentoo with kde 3.5 as my main window manager, and everything is installed. I believe I have the headers---after all, I compiled kde on this machine. I believe the headers sit in /usr/kde/3.5/include/, my global KDEDIRS path is /usr/kde/3.5:/usr:/usr/local. (I also tried setting KDEDIR.)

<pre>
checking for Qt... libraries /usr/qt/3/lib, headers /usr/qt/3/include using -mt
checking for moc... /usr/qt/3/bin/moc
checking for uic... /usr/qt/3/bin/uic
checking whether uic supports -L ... yes
checking whether uic supports -nounload ... yes
checking if Qt needs -ljpeg... no
checking for rpath... yes
checking for KDE... configure: error:
in the prefix, you've chosen, are no KDE headers installed. This will fail.
So, check this please and use another prefix!
</pre>

This is not terribly informative. kb2kskype is also the first kde app with which I have encountered such a problem. If I can help trying out different things, please drop me an email to ivowel@gmail.com

regards,

/ivo

--- someone should also write a list of all the things that should be in place for these VOIP phones to work. it is a big trial and error. so far, I think I have learned the following:
<ul>
<li> use a recent kernel. 2.6.19 will work. enable the yealink driver (CONFIG_USB_YEALINK). enable the usb sound driver (CONFIG_SND_USB_AUDIO). [add some user diagnostics to check that this has been accomplished. if not, describe to the novice how to do this.]
<li> make sure you have an artsd (or equivalent) daemon working for skype's audio. [add some diagnostics to tell the user how to check that this has succeeded, too.]
<li> get kb2kskype to work.
</ul>

Simon_6162

Mon Jan 22 2007, 13:41

QUOTE

you may not want to make the install more robust, in which case you may want to ignore this email. I am running gentoo with kde 3.5 as my main window manager, and everything is installed. I believe I have the headers---after all, I compiled kde on this machine. I believe the headers sit in /usr/kde/3.5/include/, my global KDEDIRS path is /usr/kde/3.5:/usr:/usr/local. (I also tried setting KDEDIR.)
<pre>
checking for Qt... libraries /usr/qt/3/lib, headers /usr/qt/3/include using -mt
checking for moc... /usr/qt/3/bin/moc
checking for uic... /usr/qt/3/bin/uic
checking whether uic supports -L ... yes
checking whether uic supports -nounload ... yes
checking if Qt needs -ljpeg... no
checking for rpath... yes
checking for KDE... configure: error:
in the prefix, you've chosen, are no KDE headers installed. This will fail.
So, check this please and use another prefix!
</pre>

The configure script was generated using automake and autoconf in kdevelop, I have no idea how to write them myself. I believe the solution to your problem would be to edit line 29151. The error report is the default for kdevelop, if its good for them, then I'm not changing it, however if the path change works i will add it in if this is the default for your distro.

QUOTE

/ivo
--- someone should also write a list of all the things that should be in place for these VOIP phones to work. it is a big trial and error. so far, I think I have learnt the following:
<ul>
<li> use a recent kernel. 2.6.19 will work. enable the yealink driver (CONFIG_USB_YEALINK). enable the usb sound driver (CONFIG_SND_USB_AUDIO). [add some user diagnostics to check that this has been accomplished. if not, describe to the novice how to do this.]
<li> make sure you have an artsd (or equivalent) daemon working for skype's audio. [add some diagnostics to tell the user how to check that this has succeeded, too.]
<li> get kb2kskype to work.
</ul>

The person in the post above has provided some good notes on this kind of thing I will get them on the website when I can, however there is quite a bit on there already. You don't need the YEALINK module in the kernel as far as I know or at least its not in fedora's and my box works. You do need SND_USB_AUDIO, this is in fedora so I forgot to mention it as I haven't had to compile a kernel since I last used gentoo 2 years ago;). I have tried this software on 2.6.9 kernel and it works so I don't really think the kernel has much to do with anything. Do you need arts? I don't see why skype works on fluxbox that doesn't have arts running, I could be wrong tho.

In the notes on the website I do make reference to calling echo123 for testing sound and also tell you to use alsamixer and nothing else for initial sound setup, espically not kmix and there are links to alsa pages on testing sound cards, why repeat their good advice! If you want to check the sound card is there 1. it will be listed in /proc/asound/cards and 2. you can also use usbview and check the first 2 nodes are grabbed buy SND_USB_AUDIO with the third either by the yearlink driver or by nothing.

Other requirements are on the install page of the website, although this needs updating I will do this when I have time. Feel free to post things in here for others !!

p.s. on ubuntu and maybe other distro's the kde apps go in /usr/local/kde/bin which isn't in the executable path so you need to symlink it to /usr/local/bin for the init script to work correctly or edit your PATH variable.

something like

CODE

ln -s /usr/local/kde/bin/kb2kskype /usr/local/bin/

And Do the same for the skype executable if its not installed in your PATH

alatariel

Mon Jan 22 2007, 19:01

QUOTE(ivowelch @ Sun Jan 21 2007, 03:10) [snapback]347944[/snapback]

hi simon: thanks for having written this. the yeatech skypemate is useless, because it requires a 32bit (not a 64bit) machine.

...

</pre>

This is not terribly informative. kb2kskype is also the first kde app with which I have encountered such a problem. If I can help trying out different things, please drop me an email to ivowel@gmail.com

regards,

/ivo
--- someone should also write a list of all the things that should be in place for these VOIP phones to work. it is a big trial and error. so far, I think I have learned the following:
<ul>
<li> use a recent kernel. 2.6.19 will work. enable the yealink driver (CONFIG_USB_YEALINK). enable the usb sound driver (CONFIG_SND_USB_AUDIO). [add some user diagnostics to check that this has been accomplished. if not, describe to the novice how to do this.]
<li> make sure you have an artsd (or equivalent) daemon working for skype's audio. [add some diagnostics to tell the user how to check that this has succeeded, too.]
<li> get kb2kskype to work.
</ul>

Check your mail

on Kubuntu 6.10 I had to install all of these programs to be able to compile both parts of the "driver"

quoting from the link I sent to you and some parts (those which aren't already of course) of which will be included on the site as Simon mentioned:

QUOTE

(install via kpackage or apt-get install programname)

* automake 1.9
* libusb - i.e. both
* libusb-dev and
* lib-usb++-dev

the other part needs even more stuff installed: all of
* g++
* xorg-dev (which gives us the X includes)
* libjpeg62-dev
* libqt3-headers
* libqt3-mt-dev
* plus everything they install as dependencies!
* kdelibs
* kdelibs4-dev (which gives some more KDE headers which aren't in the default package)

if you have all this installed, you can begin to build the stuff

and, for Kubuntu 6.10 at least

QUOTE

make a symbolic link from /usr/local/kde/bin/kb2kskype to /usr/local/bin/kb2kskype so you can find all of the programs in the same directory

(easier for the scripting and backup)
o ln -s /usr/local/kde/bin/kb2kskype /usr/local/bin/kb2kskype

artsd I think is not necessary to be able to run the stuff, but you must have the following intalled:
alsa-utils
and you probably want
alsa-tools-gui
alsamixergui
too

and from the discussion with Simon I gather that on the contrary the yealink driver even might complicate things since it (on Kubuntu 6.10 at least) seems to grab some parts of the driver interface which the usbb2k is to provide! but I havent' finally checked that problem yet, have been to busy this weekend with other stuff ...

Simon_6162

Wed Jan 24 2007, 13:38

To anyone who has this working (kb2kskype that is).

If you had to change anything or do anything that I don't mention in the install and user guide on the website could you please post what you did in the sourceforge forum for the project and give details of your distribution and package versions were appropriate. This should help others and allow me to make future version easier to use.

Forum is located at

Sourceforge Project forum

Thanks

mfrazzz

Fri Jan 26 2007, 08:17

Thanks to all for doing all this work! I received my B2K box a few days ago, and setup a dedicated skypebox for it. Since I didn't want to deal with issues around skypemate on Linux, I decided to setup the box running WindowsXP. Well, my "easy" route turned out to be a headache. XP wouldn't detect my USB 2.0 card properly, etc etc etc... So I did some more google searching and found this thread

. After reading through it, I decided it was worth a shot. Since the box I'm using is older (PIII 500Mhz), I at first was going to use Xubuntu, but decided to try Fluxbuntu instead since its supposed to be even faster, smaller, lighter, etc...

After installing Fluxbuntu (very easy) I then pulled up alatariel's post above with all the packages needed. I grabbed them all with Synaptic (I also had to add the make package to that list), then downloaded the bz2 files, and followed the instructions. Next started the pieces, and I was floored.... IT WORKED! Not only did it work, but after a couple of test calls, I realized the quality of the sound was better than I was getting when I first hooked the B2K up to a more powerful PC I have (but didn't want to have this attached to it due to it has to be on a VPN for my work at times). I'm really impressed and a couple of people I called couldn't believe I was calling over Skype.

The next hurdle was setting up things to autostart. The only real difference to the instructions in the userguide, was around the chkconfig piece. I couldn't find that on fluxbuntu, so instead just created symlinks right in /etc/rc0.d and /etc/rc2.d to the usbb2k file in /etc/init.d.

For Fluxbox, you have to modify $HOME/.fluxbox/startup and I added a command to run the skypeautolaunch.sh .

Then, since I want Skype to startup when the box boots, I setup VNC, and added an automatic startup of a VNC session (this allows me to connect to the box from any PC in my house to be able to check status and stuff also since there is no monitor on this box) which then also does the skypeautolaunch.sh when it starts up

Very Cool! Again, thanks a ton for all of the work everyone has put into this project already, so that this was a very easy (ok, easy in a geeky way) to setup, and so far works really well!

One comment... the skypeautolaunch.sh should actually be modified to verify the usbb2k_api is running, and then abort if its not, or abort if this user already has Skype or the client piece running. I may look at doing that myself in the next few days, and if so I'll post the modified code if anyone is interested.

Simon_6162

Fri Jan 26 2007, 14:36

Thanks for the feedback.

To edit init scripts on ubuntu / debian based distros you should use,

CODE

update-rc.d usbb2k-api defaults

and for gentoo

CODE

rc-update

I've been meaning to change that, I'll do it soon, Also good suggestion with the autostart script I will modify that as well. And add the fluxbox instructions.

p.s. I'm not sure if it is my usb2 card but i find the b2k box works better on usb1 on the motherboard than on a pci usb2 card.

Simon

mfrazzz

Fri Jan 26 2007, 19:06

QUOTE(Simon_6162 @ Fri Jan 26 2007, 06:36) [snapback]350654[/snapback]

To edit init scripts on ubuntu / debian based distros you should use,

CODE

update-rc.d usbb2k-api defaults

and for gentoo

CODE

rc-update

Good to know. Thanks!

QUOTE

p.s. I'm not sure if it is my usb2 card but i find the b2k box works better on usb1 on the motherboard than on a pci usb2 card.

Yeah, I wonder about the quality of this PCI USB 2.0 card (Cheapo from Compusa), but it seems to work for me (is there any way to tell in Linux if its running as 2.0 or 1.1?). But this PC doesn't even have USB on the motherboard so it was my only option for now (hmmm... Wonder if the BIOS could be part of the issue here with recognizing this card properly under Windows. Not sure I want to "fix" something that is working though

amoore

Sat Jan 27 2007, 07:24

I would really like to see some ubuntu/(*)ubuntu.debs for these apps. I think they have a lot of potential!!! keep up the good work simon~~~

alatariel

Sat Feb 3 2007, 09:57

we can add Mandriva 2007 to the list of distributions where this works

edit:
seems like some problems I have had with my setup under different systems might be helped with blacklisting the default yealink kernel module ... and possibly the hiddev too ...
the stuff seems more stable under Mandriva at least after this!

as root edit /etc/modprobe.conf (OR add a /etc/modprobe.d/blacklist - depending on your distribution)
and add the following lines at the top (without the comment lines if you don't want them)

#blacklist the kernel module - the usbb2k-api should do this stuff!
#and we don't need the lcd stuff anyway here ...
blacklist yealink
#blacklist hiddev - otherwise it grabs some parts the usbb2k-api should provide!
blacklist usbhid

of course blacklisting the usbhid is a bad idea if you have usb keyboards or the like - I think

Simon_6162

Sun Feb 4 2007, 22:04

There is now a new version of kb2kskype on sourceforge.

Features
It has speed dials !
It now docks its self in the systray (seems to work on gnome fluxbox and kde)!
It looks for skype closing and closes its self.

notes,
You don't need kdocker anymore
The program now has a datafile stored in ~/.kb2kskype to store contact speeddials
The website has been updated slightly, let me know if you want anything adding
The autostart skype/kb2kskype script has been changed to look for skype already running.

Simon

Dacky

Mon Feb 5 2007, 13:38

QUOTE(mfrazzz @ Fri Jan 26 2007, 08:17) [snapback]350529[/snapback]

For Fluxbox, you have to modify $HOME/.fluxbox/startup and I added a command to run the skypeautolaunch.sh .

Then, since I want Skype to startup when the box boots, I setup VNC, and added an automatic startup of a VNC session (this allows me to connect to the box from any PC in my house to be able to check status and stuff also since there is no monitor on this box) which then also does the skypeautolaunch.sh when it starts up

I just about have this working on fluxbuntu (running on Neoware thin client with external hard drive, all spare parts). The only part I cannot figure out is how to autostart. Can you give more specific commands to what you did above?
1. How to modify the startup file in fluxbuntu
2. How to have the computer auto login at bootup with VNC.

I want the computer to start up, login to Skype, etc, after a power outage, which we sometimes have.

This is really great. I tried to install this on Kubuntu 6.06 but had some troubles. I tried Fluxbuntu and it is working except for above. The directions are easy enough to follow. Specific help in the User Guide about Ubuntu/Debian really helped me this time. New version of Kb2kskype is really nice.

Simon_6162

Mon Feb 5 2007, 14:15

alatariel has done a draft guide for setting up ubuntu with skype and kb2kskype via vnc here

http://kb2kskype.sourceforge.net/downloads...ype_bk2k_en.pdf

I think the startup scripts have changed so use the ones from the download page.

Simon

mfrazzz

Sun Feb 18 2007, 08:02

QUOTE(Dacky @ Mon Feb 5 2007, 05:38) [snapback]355159[/snapback]

1. How to modify the startup file in fluxbuntu

For the user that is going to run skype and kb2kskype, login as that user and then cd $HOME/.fluxbox . Then edit the startup file in this directory. Mine looks like this:

CODE

#! /bin/bash

# Comment The Line Below To Disable Desktop Icons
rox --pinboard=Default &

# Edit Line Below To Change Background If Not Using Rox (Desktop Icons)
#fbsetbg -f /usr/share/backgrounds/fluxbuntu_wallpaper_test2.png

#Checks and Kills All Running fbpager instance
killall fbpager

#Executes fbpager
fbpager -w &

#Start Skype stuff
$HOME/skypeautolaunch.sh

exit 0

QUOTE

2. How to have the computer auto login at bootup with VNC.

First, make sure you have vnc4common and vnc4server installed (use Symantic Package Manager to do this). Now from the user account you will run skype from, type vncserver. This will prompt you for a password (this is the password to access this account's vnc session) so put in whatever you want here for a password, then put it in again to verify it. After it finishes it will create the $HOME/.vnc directory and files for you. You can now try connecting to this vnc session from another server if you want to test this (but things won't be completely setup yet). Now cd $HOME/.vnc and then edit the xstartup file in here. Here's a copy of the one I use:

CODE

#!/bin/sh

# Uncomment the following two lines for normal desktop:
# unset SESSION_MANAGER
# exec /etc/X11/xinit/xinitrc

[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources

vncconfig -iconic &
fluxbox &

Next you need to setup an autostart for a VNC session for this user. Create the following file and name it vnc (change the username to be the name of the user you want to run Skype and you can specify whatever port you want on the vncserver command):

CODE

#!/bin/sh
#
# Startup/Stop script for vncservers for some users.
#

case "$1" in

'start')
   /bin/su - skypeuser -c "/usr/bin/vncserver :10"
;;

'stop')
   /bin/su - skypeuser -c "/usr/bin/vncserver -kill :10"
;;

*)
   echo "Usage: /etc/init.d/vnc { start | stop }"
;;

esac

do the following commands:

sudo cp vnc /etc/init.d
sudo chmod 755 /etc/init.d/vnc
sudo update-rc.d vnc defaults

You should now be able to reboot and the VNC session for your user will autostart, and then skype and kb2kskype should also startup up. Enjoy!

dotslashlycos

Sun Mar 4 2007, 15:04

Thanks for writing this - skypemate doesn't work, and this is the only thing I could find that *works.

Firstly - I must comment that when dialing numbers in the US, numbers need to be entered with a "+" character followed by a 1 and then the area code and number. I note this because when I try dialing any numbers on my phone, skype throws up an error message saying that I have not dialed the number correctly.

I made a little modification to the code so that what was "CALL 12345678901" is now "CALL +12345678901"

This seems to fix things.

Secondly - I am not currently able to get my phone to ring when I get an incoming call on skype. I'm not sure where this problem lies, but thats something I'm working on.

Thirdly - I have only had this program running for 24 hours, but it seems that the app locks up my system after running for more than an hour?? or so. I don't know what this is about.

Also - I should comment that I am running this on Ubuntu "edgy" under GNOME with KDE libs installed.

Finally - the aforementioned console based "skype gate" app sounds very promising. The box I am running this on was intended to be "headless", and while I have come to terms with the fact that I will have to run skype in all of its GUI glory, I would prefer this app be strictly console based.

Thanks again for everyone who has put work into this - I've had this box sitting on my floor for a couple months now because I bought it and was unable to use it. I appreciate all the work that has gone into making this thing functional.

alatariel

Mon Mar 5 2007, 19:26

QUOTE(dotslashlycos @ Sun Mar 4 2007, 15:04) [snapback]367565[/snapback]

Firstly - I must comment that when dialing numbers in the US, numbers need to be entered with a "+" character followed by a 1 and then the area code and number. I note this because when I try dialing any numbers on my phone, skype throws up an error message saying that I have not dialed the number correctly.

I made a little modification to the code so that what was "CALL 12345678901" is now "CALL +12345678901"

- which code? your local code?

hmmm ... here in Europe at least you can safely leave off the + sign when dialing calls inside a country.

if you DO use a "+" sign this signals that you are going to have that replaced with the proper "landcode" for a call outside your country ... especially on cellphones!

i.e. the + will get replaced by 00 if you are calling from Sweden (0046) to Austria (0043) and you enter
+43(stripped first 0)proper-telephone-number
but when you dial locally it's fine with 08-whatever-telephone number ....

is there a way to fix both?
//no programmer

dotslashlycos

Mon Mar 5 2007, 19:40

QUOTE(alatariel @ Mon Mar 5 2007, 19:26) [snapback]368127[/snapback]

- which code? your local code?
hmmm ... here in Europe at least you can safely leave off the + sign when dialing calls inside a country.

if you DO use a "+" sign this signals that you are going to have that replaced with the proper "landcode" for a call outside your country ... especially on cellphones!

i.e. the + will get replaced by 00 if you are calling from Sweden (0046) to Austria (0043) and you enter
+43(stripped first 0)proper-telephone-number
but when you dial locally it's fine with 08-whatever-telephone number ....

is there a way to fix both?
//no programmer

In the US, I believe that it is required that you first dial a "+" followed by 1 (the country code), then a 3 digit "area code" followed by the 7 digit phone number.

If I leave out the plus, the country code, or the area code - I get an error message from skype saying that I've done something wrong

Simon_6162

Tue Mar 6 2007, 19:15

There is now a new version out ! Enjoy and send me any bug reports to the sourceforge forum or here.

This version fixes a bug in the contacts list updateing when it shouldn't. And adds help and some icons to make it look more profesional

There are now rpm packages and debian packages available. They have been tested as much as possible, all credit for the packages should go to alatariel.

RE the +1:
I thought you could just dial 00 instead of a +. for +44 I dial 0044.

alatariel

Tue Mar 6 2007, 20:44

QUOTE(Simon_6162 @ Tue Mar 6 2007, 19:15) [snapback]368592[/snapback]

There are now rpm packages and debian packages available. They have been tested as much as possible, all credit for the packages should go to alatariel.

and please send all bugreports about the -packages- to me too!

- or post them in this thread in the project forum ...

QUOTE(Simon_6162 @ Tue Mar 6 2007, 19:15) [snapback]368592[/snapback]

RE the +1:
I thought you could just dial 00 instead of a +. for +44 I dial 0044.

that is at least as far as I know the -european- way of handling this ... would never have thought that you needed international prefixes inside a country!?

well ... looking at -this- didn't make that understanding easier ... never dreamt of that being this complicated!
http://en.wikipedia.org/wiki/List_of_inter...l_call_prefixes
edit: the above list could be -far- outdated, it was long time since Sweden changed from 009 to 00!

perhaps these are better?
http://en.wikipedia.org/wiki/List_of_country_calling_codes
http://www.itu.int/pub/T-SP-E.164D-2006/en

mfrazzz

Sun Mar 11 2007, 02:33

Ok, this may be asking too much, but due to reliability issues with Skype 1.3, I've downgraded to Skype 1.2.0.18 as I've heard there are less problems with sound going away and such. But now that I've done this, kb2kskype when it runs says it can't find the main window. I'm guessing thats due to differeneces between skype 1.2 and 1.3? I've tried rebuilding kb2kskype but that didn't seem to make a difference. Is it possible to get kb2kskype to work with skype 1.2.0.18?

Simon_6162

Sun Mar 11 2007, 18:39

QUOTE(mfrazzz @ Sun Mar 11 2007, 02:33) [snapback]370568[/snapback]

Sorry its not possible. The x11 messageing that is used to talk to skype was only added to version 1.3, 1.2 only used dbus, and quite an old version of it.

jareguero

Sun Mar 11 2007, 19:52

I have some stability problems with kb2kskype. The patch attached solve the problems for me.
Jose Alberto

mfrazzz

Sun Mar 11 2007, 20:41

I'm not an Xwindows / Linux programmer, so can you tell me what this patch fixes / corrects? I see you are changing a sync with an XFlush. What behavior were you seeing that this fixes?

The reliability issue that I was having had to do with the sound sometimes working and sometimes it doesn't. From the reports I've seen elsewhere with Linux, this is a Skype issue and not an issue with kb2kskype that I'm experiencing (thus the reason to look at going back to 1.2 as people say that sound issue doesn't happen (or is better) with 1.2.

jareguero

Mon Mar 12 2007, 11:57

The problem I have is that kb2kskype window freeze and there was errors like this:
Xlib: unexpected async reply
in the logs.
I first remove
XSync( disp, False );
and it works well, but with some delay.
With XFlush(disp); the program works similarly that with XSync( disp, False ); but without freezes.
I don't know if someone else have this problem, but it works well for me.
(I compiled kb2kskype for x86_64)
Jose Alberto

jareguero

Mon Mar 12 2007, 12:41

Respect the audio, I have sometimes no audio and looking at alsamixer, the volumen was muted. I comment:
//connect (volume, SIGNAL(sliderReleased()), this, SLOT(setCurrentVolume()));
//connect (record, SIGNAL(sliderReleased()), this, SLOT(setCurrentVolume()));
and put the volumens with alsamixer.

Jose Alberto

jareguero

Tue Mar 13 2007, 11:45

QUOTE(jareguero @ Mon Mar 12 2007, 12:41) [snapback]371034[/snapback]

I think that the volume settings are wrong. Se the attached patch.
Jose Alberto

lorek123

Sat Mar 17 2007, 10:27

i just install kb2kskype from rpm for my fedora 6. i do

CODE

[lorek123@c35-239 ~]$  cat /proc/asound/cards
0 [nForce2        ]: NFORCE - NVidia nForce2
                      NVidia nForce2 with ALC650F at 0xdc000000, irq 16
1 [UART           ]: MPU-401 UART - MPU-401 UART
                      MPU-401 UART at 0x330, irq 10
2 [Bt878          ]: Bt87x - Brooktree Bt878
                      Brooktree Bt878 at 0xd8001000, irq 22

i didn't see the usb telbox. anyone can help??
PS. sorry for my English

Simon_6162

Tue Mar 20 2007, 19:27

QUOTE(lorek123 @ Sat Mar 17 2007, 10:27) [snapback]373006[/snapback]

i just install kb2kskype from rpm for my fedora 6. i do

CODE

i didn't see the usb telbox. anyone can help??
PS. sorry for my English

1. Have you checked the box works on another machine / windows ?
2. What kernel version are you using ? What processor are you running on ?
3. Can you boot up the machine without the box plugged in. Then plug in the box and type the command below and post the output.

CODE

dmesg | tail -n 20

jareguero Thanks for the patches, I'll get a new release out soon. The volumes were wrong (Sorry everyone!) As for the other function that was taken out of the skype demo, so I don;t really know what it does, but if your fix works I'll add it! Let me know if you find anything else.

Simon

kpnut

Thu Mar 22 2007, 13:13

QUOTE(jareguero @ Mon Mar 12 2007, 11:57) [snapback]371022[/snapback]

I tried kb2kskype on Ubuntu 6.10 with KDE libs (all the items needed to get it to compile etc) and I had exactly this problem. I'm since messing around with Fedora Core 6 (since I thought I could also try the old SkypeMate from Yealink (hopefully easily)). I'll try before and after your patch on Fedora and post my results, if I get a chance (the kids don't seem to understand when I'm "busy" on the computer?!

) then I'll switch back to Ubuntu and try before/after the patch again. (Would it work in a VM I wonder? VMware server being free makes it easy enough to test I suppose. Ubuntu inside Fedora, what will the neighbours say?

)

I should add this is all plain x86 (even though I have an AMD64). Don't want to take this too far off topic, I just had all sorts of grief with XP 64bit, with very little benefits (none I could think of) so I'm shying away from 64bit for now at least (is it any better / worse on Linux? Driver support etc?) I realise 64bit is handy for addressing VERY large amounts of RAM but I don't have 1TB of RAM or anything (yet

) Am I missing out on anything that I'm unaware of?

EDIT:
Ok, just an aside, I ditched Fedora Core 6 (what a P.O.C it didn't find my sound card or my fusionhdtv HDTV capture card out of the box) and went back to Ubuntu 6.10 and everything worked like a charm. Then I built the source again. I can confirm that jareguero's patches solved the occassional issue with volume sliders being off (only a minor annoyance), but MORE importantly, solved the problem where everything would HANG - window no longer paints in kb2kskype and phone is then unresponsive (only ever used to work *once* for a phone call, then 2nd call the problem appeared - this is now CURED!. Wanted to say thanks to one and all - Simon for this great piece of software (I love the price!

) and all patches etc. Cheers guys!

PS. I should add that I have a dual-core CPU, not sure if that matters, but if there are timing related bugs, it's possible that's why I'd always see the problem before? Just a thought...

morsub4u

Sat Mar 24 2007, 03:21

Hey. I just bought one of these adapters, and I have gotten some of this software compiled and working on Mandrake 10.2, but I was wondering if there is a command line client for this app? I am really interested in using my PC as a PBX, and believe I can do this with Linux if I have a CLI version of this program. Is there any intention to support such a use? Thanks!

lorek123

Sun Mar 25 2007, 07:54

QUOTE

1. Have you checked the box works on another machine / windows ?

yes it work on my PC on windows. i'm newbie in linux

QUOTE

2. What kernel version are you using ? What processor are you running on ?

2.6.20-1.2933.fc6
Semptron 2300+
3.

CODE

Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=67.170.153.214 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=115 ID=47303 PROTO=UDP SPT=35576 DPT=8768 LEN=27
Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=71.227.66.183 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=114 ID=29300 PROTO=UDP SPT=11275 DPT=8768 LEN=27
Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=69.243.221.78 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=115 ID=40140 PROTO=UDP SPT=45191 DPT=8768 LEN=27
Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=71.67.120.38 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=108 ID=51004 PROTO=UDP SPT=11275 DPT=8768 LEN=27
Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=67.170.47.85 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=115 ID=55311 PROTO=UDP SPT=11275 DPT=8768 LEN=27
Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=59.161.2.114 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=114 ID=13614 PROTO=UDP SPT=7871 DPT=8768 LEN=27
Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=125.100.188.205 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=113 ID=30209 PROTO=UDP SPT=60254 DPT=8768 LEN=27
Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=67.162.189.168 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=117 ID=49727 PROTO=UDP SPT=34251 DPT=8768 LEN=27
Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=201.231.81.145 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=112 ID=55060 PROTO=UDP SPT=3343 DPT=8768 LEN=27
Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=207.255.221.110 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=116 ID=52132 PROTO=UDP SPT=11275 DPT=8768 LEN=27
Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=71.131.29.33 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=112 ID=28709 PROTO=UDP SPT=34251 DPT=8768 LEN=27
Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=70.224.80.6 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=113 ID=24314 PROTO=UDP SPT=34251 DPT=8768 LEN=27
Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=124.120.200.44 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=110 ID=29075 PROTO=UDP SPT=29821 DPT=8768 LEN=27
Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=217.25.84.90 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=115 ID=41451 PROTO=UDP SPT=11275 DPT=8768 LEN=27
Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=71.131.29.33 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=112 ID=28749 PROTO=UDP SPT=34251 DPT=8768 LEN=27
Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=70.241.198.111 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=112 ID=39201 PROTO=UDP SPT=11275 DPT=8768 LEN=27
Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=86.129.199.230 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=110 ID=44309 PROTO=UDP SPT=11275 DPT=8768 LEN=27
Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=67.170.47.85 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=115 ID=55434 PROTO=UDP SPT=11275 DPT=8768 LEN=27
Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=71.227.66.183 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=114 ID=29462 PROTO=UDP SPT=11275 DPT=8768 LEN=27
Inbound IN=eth0 OUT= MAC=00:11:2f:84:59:4e:00:13:5f:07:64:05:08:00 SRC=71.67.120.38 DST=62.21.4.57 LEN=47 TOS=0x00 PREC=0x00 TTL=108 ID=51217 PROTO=UDP SPT=11275 DPT=8768 LEN=27

jellund

Tue Apr 3 2007, 08:28

I have a B2K and OsX. The Yealink drivers work well enough, but it would be nice to fix some bugs and add more features (instead of having them in a text config file). However yealink's email is broken, and it is unlikely they would be interested in releasing sources anway.

Anyone started on OsX work based on the sources here? I've taken a quick look, but there is no reason that it could not be ported. Just needs to remove some of the Linux style hack code

(seriously? symlink to system autoconf area?

)

(someone asked earlier: NetBSD would not be hard, in fact you might find the emulation code is enough to run it. ).

Developer open to taking patches to sources?

jellund

Tue Apr 3 2007, 09:32

QUOTE(jellund @ Tue Apr 3 2007, 08:28) [snapback]379426[/snapback]

Anyone started on OsX work based on the sources here?

Initial attempts were promising:

SEND> RECV> USB DEVICE FOUND 007-6993-b001-00-00
RECV> <30>
Apr 3 17:29:02 usbb2k_api[12400]: Init usb
RECV> <27>
Apr 3 17:29:02 usbb2k_api[12400]: claim interface Failed

So maybe it can be done.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.