Hi all;
I am a new suscriber in this forum, but i always visit it to solved a lot of things about MJ.
So, If someone can help us, I guess the community (i mean each member) will be agreed to donate $10 as minimum, in order to get this stuff working back on ATA's.
Please let's be united, I know we can do that.[/b]
Let's start donate to get MJ working back on ATA!!!
Moderators: Bill Smith, Pilot
I really don't know how they killed off the ATAs but if it is as one member suggested "That MagicJack central has blocked known ATA user accounts/numbers" No amount of money will fix the problem and new numbers will likely go down as soon as ATA use is detected.
If someone knows a different answer to the problem please chime in.
If someone knows a different answer to the problem please chime in.
-
Taken83oveR
- Dan isn't smart enough to hire me
- Posts: 119
- Joined: Wed Jun 11, 2008 2:07 pm
Here's the thing. Not that I don't think the person who figures out a proven solution, does not deserve compensation, because they very well may. But why would many people donate to get there $20/year MagicJack working again on a ATA, when they could just move on to a different VOIP, that natively supports ATA's, and not have to worry about future MagicJack tricks, that may bring down there ATA again?
Just keep that money in your pocket, and possibly use it, when you make the move to a SIP/ATA friendly VOIP provider.
Just keep that money in your pocket, and possibly use it, when you make the move to a SIP/ATA friendly VOIP provider.
Not optimistic and seems its a dead end for ATA now. If you use Wireshark, you'll notice there're some https/TLS traffic and certificate exchange during the registration, which wasn't there before the update. And, from I've read, old official MJ softphone can't register after the update. This makes me believe that MJ is using a new TLS/HTTPS related authorization process -- which is unsupported in majority ATAs(including PAP2)
-
agriffiths
- magicJack Apprentice
- Posts: 26
- Joined: Wed Apr 08, 2009 10:45 pm
An interesting post I found in the Google Voice Help Forum...
http://www.google.com/support/forum/p/v ... 46b46a94d9
If this is legit and somebody can find the actual post to contact the guy, he might be the one we're looking for. He would have the knowledge AND appears to have the motivation to let the secret out.
I tried a Google search but came up empty.
http://www.google.com/support/forum/p/v ... 46b46a94d9
If this is legit and somebody can find the actual post to contact the guy, he might be the one we're looking for. He would have the knowledge AND appears to have the motivation to let the secret out.
I tried a Google search but came up empty.
pagemen wrote:Not optimistic and seems its a dead end for ATA now. If you use Wireshark, you'll notice there're some https/TLS traffic and certificate exchange during the registration, which wasn't there before the update. And, from I've read, old official MJ softphone can't register after the update. This makes me believe that MJ is using a new TLS/HTTPS related authorization process -- which is unsupported in majority ATAs(including PAP2)
If that's the case then it *should* work with asterisk.
Get an openwrt router, throw asterisk on it, let it handle the authentication process and pass everything else to the ATA for voip calls.
I have to go do some work now. When I get back home I will play with this.
Thanks
ScarEye