Is there a way autoselect a specific bluetooth device upon it becoming active, for Magicjack?
Due to a very bad echo problem in using the laptops internal mic and speakers, and not taking my phone (and dsl filter) with me, I tried a bluetooth and it works fine.
The down side is that as soon as I turn off the bluetooth or get out of range, Magicjack reverts to the default or next available audio device.
To get back to bluetooth seems to be to time consuming manual, loose or miss the call.
Simply put what I want:
Phone rings (computer speakers) alerting me to an incoming call.
I turn on the blue tooth device and Magicjack automatically switches to it, where upon I can answer the call.
Call done, turn off blue tooth device, saving its battery charge.
As there can be more than one bluetooth device in range, setting a specific device is required.
Note: if they hadn't crapped on user rights to make use of computers for automation (who'd thunk computers and automation are one and the same) then I might have been able to figure this out with autoit. Better yet, why haven't they done this already with a user preference option better than what they have?
Auto select Bluetooth when bluetooth becomes available
Moderators: Bill Smith, Pilot
A few notes:
What I want is so fundamental that I expect it to come with the purchase price of Magicjack, nothing more paid for it. Certainly it'd help sell MJ.
I have to say this in light of the additional third party add-ons for a price.
Additionally I expect a user config option allowing this setting of the primary audio device and a secondary setting, before then resorting to the system default device. as I have become aware next on the list doesn't work for those with additional audio devices installed. In other words, shutting the bluetooth device down doesn't then cause MJ to go to the default device but the next on the list.
I see no useful purpose in the current audio device handling method.
I am quite disappointed in QT, that it masks from such automation tools as Autoit. I suspect the choice to use QT is based on making MJ more cross platform compatible --- the path to MJ on Linux perhaps. The Linux Problem is Distribution compatibility. It is ironic effort to port to an open system causes closed access.
Like so many so called upgrade in the computer industry, this "Lucky you" seems more another hypocrisy than an upgrade.
Is there any documentation on the functionality in the Magicjack dll's.
What I want is so fundamental that I expect it to come with the purchase price of Magicjack, nothing more paid for it. Certainly it'd help sell MJ.
I have to say this in light of the additional third party add-ons for a price.
Additionally I expect a user config option allowing this setting of the primary audio device and a secondary setting, before then resorting to the system default device. as I have become aware next on the list doesn't work for those with additional audio devices installed. In other words, shutting the bluetooth device down doesn't then cause MJ to go to the default device but the next on the list.
I see no useful purpose in the current audio device handling method.
I am quite disappointed in QT, that it masks from such automation tools as Autoit. I suspect the choice to use QT is based on making MJ more cross platform compatible --- the path to MJ on Linux perhaps. The Linux Problem is Distribution compatibility. It is ironic effort to port to an open system causes closed access.
Like so many so called upgrade in the computer industry, this "Lucky you" seems more another hypocrisy than an upgrade.
Is there any documentation on the functionality in the Magicjack dll's.
Here is an available hardware based solution http://bestgiftsaround.com/Bluetooth-La ... 82958.aspx that meets your basic requirements except for the one about being free.
I actually researched the type of solution you are describing and it was technically feasible with a bit of R&D and investment dollars. I dropped the possible project after MJ formally announced it was coming out with a micro cell based MJ dongle (that has never formally made it to the market). The "in coverage area" bluetooth idea still makes more sense to me than the micro cell based MJ dongle.
I actually researched the type of solution you are describing and it was technically feasible with a bit of R&D and investment dollars. I dropped the possible project after MJ formally announced it was coming out with a micro cell based MJ dongle (that has never formally made it to the market). The "in coverage area" bluetooth idea still makes more sense to me than the micro cell based MJ dongle.
I tried to switch audio devices during an incoming call, before answering, and magicjack crashed. This indicates the local MJ user interface software is very immature.redpepper wrote:Here is an available hardware based solution http://bestgiftsaround.com/Bluetooth-La ... 82958.aspx that meets your basic requirements except for the one about being free.
I actually researched the type of solution you are describing and it was technically feasible with a bit of R&D and investment dollars. I dropped the possible project after MJ formally announced it was coming out with a micro cell based MJ dongle (that has never formally made it to the market). The "in coverage area" bluetooth idea still makes more sense to me than the micro cell based MJ dongle.
Your link made me realize something, The solution is perhaps only a matter of creating an audio I/O device handler and pointing magicjack to it as the audio I/O device. This way Magicjack need not even know of any audio I/O switching, leaving the switching up to the device handler. and as such config options can be as I mentioned with a primary if available and a secondary before resorting to default system settings.
the hardware device you pointed to is not workable for me as I have no room in my laptop briefcase for it, otherwise I'd just use my one piece phone which can't be much larger than this device.
Simply put, a software based solution is possible and probably with a great deal less effort than such free software as dopdf (dopdf.com) as it'd be more a wrapper than a full out device.
of course more complete integration of bluetooth headsets with magicjack would be good too. I.E. the on/off hook button and other capabilities such as voice command in selection of number to call, etc..
from the bluetooth device manual I have for a Motorola H720
controlled by the three buttons on the headset.
answer a call
ignore a call
make a voice dial call
redial last call
mute or unmute a call
end a call
besides the on/off hook button there is two buttons referred to as volume keys though in combination do other things.
obviously these are dependent on the device the bluetooth is connecting to. Currently none of these bluetooth function buttons apply to magicjack, but the bluetooth only act as the audio I/O device of Magicjack.
Windows 7 has voice recognition of which I have yet to make any use of, but the point being: the supporting software/data is perhaps already there for voice commands of such, for those who know the hooks into the magicjack dlls.
This might be reasonable to sell as third party, but not the audio i/o switcher device driver/wrapper.
as a comparison I found this on http://update.broadcom.com/help/how_to.htm#wp470265
"To use a hands-free audio device with Skype™
You can begin using Skype as soon as you are connected to your hands-free audio device. Skype automatically recognizes your hands-free audio device, adjusts Audio In and Audio Out settings to use a Bluetooth Hands-free Audio device, and routes calls to your device. You can use the button on your device to accept or reject a call, place a call on hold, hang up, or redial a number."
from the bluetooth device manual I have for a Motorola H720
controlled by the three buttons on the headset.
answer a call
ignore a call
make a voice dial call
redial last call
mute or unmute a call
end a call
besides the on/off hook button there is two buttons referred to as volume keys though in combination do other things.
obviously these are dependent on the device the bluetooth is connecting to. Currently none of these bluetooth function buttons apply to magicjack, but the bluetooth only act as the audio I/O device of Magicjack.
Windows 7 has voice recognition of which I have yet to make any use of, but the point being: the supporting software/data is perhaps already there for voice commands of such, for those who know the hooks into the magicjack dlls.
This might be reasonable to sell as third party, but not the audio i/o switcher device driver/wrapper.
as a comparison I found this on http://update.broadcom.com/help/how_to.htm#wp470265
"To use a hands-free audio device with Skype™
You can begin using Skype as soon as you are connected to your hands-free audio device. Skype automatically recognizes your hands-free audio device, adjusts Audio In and Audio Out settings to use a Bluetooth Hands-free Audio device, and routes calls to your device. You can use the button on your device to accept or reject a call, place a call on hold, hang up, or redial a number."