magicJack and MagicJack Plus Support, Reviews, FAQs and Hacks

Roman1974 · MagicJack Newbie Joined: 17 Sep 2009 Posts: 1

I'm normally one of those Google hunting jerks that resolve my technical issues through the hints associated with uploads of other sufferers. But when I resolve nagging issues, I dont contribute. This stupid magicjack problem caused me 4 hours of pain last night, in part because they (MagicJack) didn't load necessary XPe drivers onto the mj key, but also because MagicJack Chat Support was counterproductive, basically leaving me with no solution.

So after I resolved it, I didnt want anyone else to have to suffer this (especially considering how rampant it is), so I'm registering on this site to provide you guys a solution (for what could be my only time doing so), and I'll hope that I've dropped enough keywords in here that Google hunters around the globe will hit this thread. I didnt resolve this all by myself. Other people have fixed it, but no one ever wrote up a concise chronology towards resolution that included ALL the information. There's just bits and pieces around the web, to which I've tried to give credit where I could. *** This solution is meant for Thin Client XPe users.

My system...

* t5700 1Ghz w/ 512MB Flash & 512MB RAM.
* XPe loaded with Service Pack 2
* "Sygate Security Agent" disabled and then removed with a downloaded program from HP.

Here's some additional information you'll need to know...

* STOP hunting for the magicjack or tigerjet or ymax driver. They dont have one (for download). The driver is native to XP Pro, but not XPe
* XP Pro and XPe are the same OS. It's just that E is stripped of useful drivers (amongst other things). You CAN copy XP Pro files to XPe and expect them to work.
* After you have registered your MagicJack and gotten your phone number, you can then plug the jack into any XP PRO system and it will all load up for you. No drivers, nothing. That's because everything is stored on the jack inself, or automagically downloaded from magicjack's website. I mention this so you can quickly verify your mj key is not defective. Nor your oft blamed telephone, for that matter.

Like many of you, I had the following symptoms...

* XPe cannot find the magicjack driver. It merely references a yellow splatted "USB Internet Phone by TigerJet" under "Other Devices".
* Dial pad can send and recieve calls just fine.
* Inability to select "Telephone" in the magicjack software.
* The physical phone will only get dialtone before the magicjack software loads up. The moment the MJ application comes online, no more dialtone. If you restart the mj software and quickly test the handset, you have dialtone (for a moment).

I went through the usual shenanigans. While I saw the yellow TigerJet driver in Device Manager, I ASSuME'd that was ok because the dialpad worked just fine. I ASSuME'd it was just a mj driver quirk. I replugged stuff, tried the magicFix (from microsoft), the "upgrade" from MagicJack, etc. I even considered replacing what must be a dud mj (after all the threads I'd read on this problem blaming the mj device) until I plugged it into my xp pro laptop and it worked great (with physical phone dialtone). No DevMan splats. No complaints. That's when I realized it HAD to be a driver issue. That stupid yellow splat that I had initially ignored. I wont bore you with my useless dialogues with inept mj chat techies, but I will say that I chatted with 4 of them, 2 of which were "higher level". I don't say they're inept because they couldnt resolve my problem, but because they continued to ignore my complaints about the yellow driver, and the fact that this is such a rampant and well documented issue, yet they knew nothing about it, nor would they even acknowledge it upon my multiple attempts to steer the troubleshooting in the driver direction.

Some useful information on my laptop XP Pro test...

When I had the mj plugged into the Thin Client, the app that loads is DIFFERENT than the one that loads up on the laptop. This is directly because of the driver issue. I know, weird. In the Thin client, the below picture represents the menu selection I see when clicking the menu button...

It's been my experience that if you have that menu selection at all, you're already in trouble. You know the one I'm talking about, where you're uselessly trying to select the Telephone radio button on the subscreen. On my XP Pro laptop however, the application that automatically loaded up had this menu selection...

No subinterface in this case, just a direct "Switch to Telephone" click. But now I know what you're thinking. Different versions of the mj software, right? The mj software "upgrade" is landed on the device itself. So after "upgrading" it four times via the inept mj support chat, you can be sure it was definitely upgraded. Nevertheless, I intentionally did the update on my laptop anyway just to see, but still the menus were different. It occured to me for a moment that perhaps I should try to "downgrade" the mj software, but it wont let you, so I quickly dismissed that.

Note ** I had to do a little screenshot photo doctoring since I'm at work right now, and dont have access to the magicjack. I didnt have the energy last night to write up this reply for you guys, so I'm having to make do at work. But those menu's are what I saw.

The below thread tipped me off on the USBAudio.sys file...

http://www.dslreports.com/forum/r20952483-MagicJack-Hewlett-Packard-T5720-Thin-Client-Tigerjet

"Somehow I was clicking between different folders to update the driver and it pops a dialog and looking for USBAUDIO.sys. I immediately copy the driver from my XP notebook under c:\windows\system32\drivers. Look for the one with all upper case file name: USBAUDIO.sys, 58KB size. After the driver update of that Tigerjet, my Magic Jack works like magic!"

Now as stated, this is not enough because you cant update the Tigerjet driver with a sys file. You have to use INF files. So while this didnt resolve my problem, at least it put me on the right track. *** It worked for him because somewhere along the way, he had applied the proper INF driver that subsequently ASKED for that sys file. He must have forgotten to mention that in his thread.

This seemingly unrelated thread tipped me off to the INF portion of the problem...

http://forums.techguy.org/windows-nt-2000-xp/585789-usb-audio-codec.html

So wdma_usb.inf and wdma_usb.pnf reference the usbaudio.sys driver. Seeing that tempting looking INF, I copied them over from XP Pro, and "updated" the "USB Internet Phone by TigerJet" with that INF. During the update it asked for the usbaudio.sys driver, which I had already copied over, and now I have dialtone and functionality with the handset. I also now have 3 new yellow splats in Device Manager, no doubt additional sys files that wdma_usb.inf had been hoping for, but never asked me for. But it is all working properly, and the Tigerjet driver has been replaced with "USB Audio Device" under Sound controllers (where it should be). And, my TC MJ SW telephone selection is as it appears on my laptop.

It is my intention to try to hunt down the remaining sys files, but at least the pressure is off now. I suspect that they might be listed under the "USB Audio Device" as seen in XP Pro (when you examine what files that driver is using), after you've inserted the MagicJack. If anyone knows them already, feel free to reply in the thread. (Im thinking about trying the file copy suggested in this thread: http://www.msfn.org/board/lofiversion/index.php/t83486.html )

So to resolve this problem, from an XP Pro system, copy over usbaudio.sys and place it in the C:\WINDOWS\system32\drivers folder (of the thin client) and the wdma_usb.inf and wdma_usb.pnf files into the C:\WINDOWS\inf folder. Bounce the the thin client, and then update the TigerJet driver with wdma_usb.inf. And dont forget to "Commit" the TC or you might have to do this every time you bounce the TC.

Edit* I couldnt find the usbaudio.sys in the XP Pro drivers directory, but a search of the C drive found it. Also, I've been told that some XP Pro versions dont have the INF and PNF files, but BAK versions instead (wdma_usbinf.bak & wdma_usbpnf.back). You can rename them to wdma_usb.inf and wdma.pnf and use those instead.)

Google · AdSense

haze10 · magicJack Apprentice Joined: 05 Jan 2010 Posts: 24

this same thing is happening to me, but I can't fix it .

I downloaded the files you cited to the proper directory.

don't know what you mean by 'bounce' the TC.

If I remove power and reboot the files dissappear.

I reloaded them again, and then insstalled MJ, but no change.

Don't know how to find the Tigerjet and update it, can you help

haze10 · magicJack Apprentice Joined: 05 Jan 2010 Posts: 24

I got it fixed. Alpman helped me. The trick was to go to the device manager in the control panel, and then select manual to install and to browse select the I386 directory.