Could also try DD.
Find it here.
Though if you think pmdump is difficult...
Using MJ on ATA
Moderators: Bill Smith, Pilot
-
SpamBox
- Dan isn't smart enough to hire me
- Posts: 417
- Joined: Fri Dec 14, 2007 4:31 am
- Location: Rocky Mountains Front Range
And since we're being helpful, here's a microsoft tool that does things.
Find it here
Or if you're a MAC user, maybe try "xxd"
So like I said, might just be easier to wait until we're allowed.
Find it here
Or if you're a MAC user, maybe try "xxd"
So like I said, might just be easier to wait until we're allowed.
Morpheus: What is "coming soon"? How do you define "coming soon"?
-
kingfisher1111
- MagicJack Expert
- Posts: 76
- Joined: Tue Nov 27, 2007 6:17 pm
-
kingfisher1111
- MagicJack Expert
- Posts: 76
- Joined: Tue Nov 27, 2007 6:17 pm
ATA Magicjack is comming soon
I was reading in a website www.dslreports.com that ATA dvice magicjack is comming in march as per saying of dan.
Is it correct?
thanks
Is it correct?
thanks
Re: ATA Magicjack is comming soon
I emailed Dan on 6/9/2008 on this issue. Dan stated that the BYOD service should be available late 3rd quarter or early 4th quarter of 2008. He also indicated that porting of existing phone numbers should be available within the same timeframe.banaa007 wrote:I was reading in a website www.dslreports.com that ATA dvice magicjack is comming in march as per saying of dan.
Is it correct?
thanks
-
Taken83oveR
- Dan isn't smart enough to hire me
- Posts: 119
- Joined: Wed Jun 11, 2008 2:07 pm
For those running ATA's, can you verify settings? As this thread is kinda old, and some data might be outdated.
For example, What is the proper "Register Expires" value for the PAP2 people? Do I really want it calling home once a minute(52), as suggested in December by jeffnyc, on the 2nd page of this thread?
Here is a screenshot of my settings, which seem to work for the most part.
I have put a redbox around the info that is important and blurred some info to protect the innocent
Like I said above, it works well for the most part, but I do get this error here and there (note red box section in the pic below).
One thing I did not take a pic of, I disabled Provisioning, which can be done in Provisioning section.
I would appreciate tweaks, or comments. Also is this the latest version of firmware for PAP2-NA V1? I did some googling, and didnt find much for V1. Do not leave me reply's asking how to obtain Sip info, as this "public" forum is not the place for it. There are other ways of asking.
For example, What is the proper "Register Expires" value for the PAP2 people? Do I really want it calling home once a minute(52), as suggested in December by jeffnyc, on the 2nd page of this thread?
Here is a screenshot of my settings, which seem to work for the most part.
I have put a redbox around the info that is important and blurred some info to protect the innocent
Like I said above, it works well for the most part, but I do get this error here and there (note red box section in the pic below).
One thing I did not take a pic of, I disabled Provisioning, which can be done in Provisioning section.
I would appreciate tweaks, or comments. Also is this the latest version of firmware for PAP2-NA V1? I did some googling, and didnt find much for V1. Do not leave me reply's asking how to obtain Sip info, as this "public" forum is not the place for it. There are other ways of asking.
You are running the latest public firmware.
Unless something very strange is happening, the only disadvantage of your short Register Expires is that it beats on the server a little more. The normal interval on MJ is 180 seconds. If your router times out the NAT association quicker than that, you could use NAT keepalive. I would not play with those parameters until you find out why you are losing registration.
It may be useful to set Reg Retry Long Intvl to e.g. 30, so if some glitch causes a registration error, it will try to regain reg fairly quickly. However, your screen shot shows that it will retry in 10 seconds, which seems strange for a 'no response' type of error. Do you know if it really does retry so fast, and if the retry usually succeeds?
I don't see any obvious reason why you should be losing registration. You could try running pings to the proxy and see if packets were lost when the reg fails. If not, use SIP Debug to see what response, if any, is received when reg fails.
Unless something very strange is happening, the only disadvantage of your short Register Expires is that it beats on the server a little more. The normal interval on MJ is 180 seconds. If your router times out the NAT association quicker than that, you could use NAT keepalive. I would not play with those parameters until you find out why you are losing registration.
It may be useful to set Reg Retry Long Intvl to e.g. 30, so if some glitch causes a registration error, it will try to regain reg fairly quickly. However, your screen shot shows that it will retry in 10 seconds, which seems strange for a 'no response' type of error. Do you know if it really does retry so fast, and if the retry usually succeeds?
I don't see any obvious reason why you should be losing registration. You could try running pings to the proxy and see if packets were lost when the reg fails. If not, use SIP Debug to see what response, if any, is received when reg fails.
-
Taken83oveR
- Dan isn't smart enough to hire me
- Posts: 119
- Joined: Wed Jun 11, 2008 2:07 pm
The Reg Retry, happens after the countdown is over, which was 52 seconds (not 10 seconds, thats just what the number was at, when I took the pic), but I changed it to 180, to be in line with the official Magicjack adapter. I am guessing this can be logged, so I would like it to be the same as the official adapter. If Reg does fail, the only way I can get logged back in, is if I plug the official adapter in, let it login, then unplug, and relogin via the pap2. Otherwise, I keep failing at login. Usually, anytime I change "Line 1's" settings, I will get the fail logged in message, and have to do the little trick with the official magicjack to get it login again with my pap2.
I am not sure how to "Sip Debug", as I see no log or anything via the admin page.
From what I can see my PAP2-NA is a V1.
Edit: I just changed some settings and logged in just fine, so I am at a total loss here. Maybe the firmware is a little buggy?
Edit 2: Changing the setting to 180, has cleared up my problems. I now have no problems getting connected via pap2.
I am not sure how to "Sip Debug", as I see no log or anything via the admin page.
From what I can see my PAP2-NA is a V1.
Edit: I just changed some settings and logged in just fine, so I am at a total loss here. Maybe the firmware is a little buggy?
Edit 2: Changing the setting to 180, has cleared up my problems. I now have no problems getting connected via pap2.
-
Taken83oveR
- Dan isn't smart enough to hire me
- Posts: 119
- Joined: Wed Jun 11, 2008 2:07 pm
OK I have been monitoring, and have found some "weird going on's". The Pap2 will be fine as long as my PC is on, as far as I can tell. Once I shut my pc down, shortly after (not right away), the Pap2 will loose connection, on line 1, but ofcourse still be connected to the internet (via router with ports forwarded). So its not loosing connection to the internet, but just on line 1. The minute I turn my pc on. and access the admin page, on the next attempt, the Pap2 will successfully connect on line1. Has anyone else experienced this?
I really can't try a 2nd router, as I am a ATT Uverse user, and that also rules out a direct connect sense my router/modem is one unit.
A little info.
Magicjack is not plugged into the pc.
PAP2-NA (v1 i believe).
Router/modem = 3800HGV-B Gateway
Ports are open for the PAP2 Ip address.
Edit 1: I setup Line 2, with a free account from www.freeworlddialup.com. I guess if both lines get disconnected after a short while, then it might be a problem with the router/modem setup.
Edit 2: After about 30min, Line 1(magicjack) failed to connect, while line 2(fwd) remain connected. So the problem is not with the router/modem or pap2, but could be settings or something the magicjack devs are doing? This seems to only happen when the pc is off.
Edit 3: Turned Pc off at 9:50, and watched the status leds. At Aprox 10:22, the led for line 1, was off, telling me it failed to register. So it happened after aprox 30 min again. I turned my pc on, and soon after, line 1 led lit back up, telling me is had successfully registered.
This is rather annoying.... What could cause the "line 1(magicjack)" to fail to register after 30min of my pc being off? Note, Line 2(fwd), continue's to function normally. I even tried swapping the settings, back and forth from line 1 and 2, but this does not fix the problem.
We really need to nail down the proper config for ata's, as there is alot of conflicting information on this board.
I really can't try a 2nd router, as I am a ATT Uverse user, and that also rules out a direct connect sense my router/modem is one unit.
A little info.
Magicjack is not plugged into the pc.
PAP2-NA (v1 i believe).
Router/modem = 3800HGV-B Gateway
Ports are open for the PAP2 Ip address.
Edit 1: I setup Line 2, with a free account from www.freeworlddialup.com. I guess if both lines get disconnected after a short while, then it might be a problem with the router/modem setup.
Edit 2: After about 30min, Line 1(magicjack) failed to connect, while line 2(fwd) remain connected. So the problem is not with the router/modem or pap2, but could be settings or something the magicjack devs are doing? This seems to only happen when the pc is off.
Edit 3: Turned Pc off at 9:50, and watched the status leds. At Aprox 10:22, the led for line 1, was off, telling me it failed to register. So it happened after aprox 30 min again. I turned my pc on, and soon after, line 1 led lit back up, telling me is had successfully registered.
This is rather annoying.... What could cause the "line 1(magicjack)" to fail to register after 30min of my pc being off? Note, Line 2(fwd), continue's to function normally. I even tried swapping the settings, back and forth from line 1 and 2, but this does not fix the problem.
We really need to nail down the proper config for ata's, as there is alot of conflicting information on this board.
Check that PPP on Demand is not set in your router.
Please explain how you arrived at your settings. In most cases, MJ will work fine with no port forwarding, and with NAT Mapping Enable turned off. What happens in that configuration? What ports are you forwarding? Do you have another PC on your network that could be used to monitor the failing case? When it fails, can you make a call on the FWD line? Does that bring the MJ line back to life?
Please explain how you arrived at your settings. In most cases, MJ will work fine with no port forwarding, and with NAT Mapping Enable turned off. What happens in that configuration? What ports are you forwarding? Do you have another PC on your network that could be used to monitor the failing case? When it fails, can you make a call on the FWD line? Does that bring the MJ line back to life?
-
Taken83oveR
- Dan isn't smart enough to hire me
- Posts: 119
- Joined: Wed Jun 11, 2008 2:07 pm
PPP on Demand? I doubt my router supports that, as it always has to be on to serve 3 televisions(IPTV)+internet, in my home. But I will have a look.Stewart wrote:Check that PPP on Demand is not set in your router.
Please explain how you arrived at your settings. In most cases, MJ will work fine with no port forwarding, and with NAT Mapping Enable turned off. What happens in that configuration? What ports are you forwarding? Do you have another PC on your network that could be used to monitor the failing case? When it fails, can you make a call on the FWD line? Does that bring the MJ line back to life?
As far as settings. I have tried several different settings, spread across the forums, which very from user to user. It gets quiet confusing, and there is to much conflicting info out there, to be sure which settings to use. The settings u see above is just a example, and yes I have tried turning mapping off. I am forwarding all the ports recommended for pap2 and magicjack
(udp 5060-5070, tcp 80, tcp 443, udp 10000-20000, tcp/udp 53, tcp/udp 69, ) Some of these I might not need open, but like I said, I have tried alot of different things. But I doubt the firewall is a issue, as Line 1 works fine for 30 min or so with the pc off, and works forever with the pc on. Line 2, never stops working (my FWD test provider). When it fails, I just get voicemail when I call the number, and does not bring it back to life.
I am currently in the process of testing a spa1001 firmware on my pap2-na v1(yes its possible). I will let you know how it holds up. The first test with this firmware was positive, as it lasted over 35minutes(never got that far with original firmware), while my pc was off with no issues. The real test is the overnight test. Hopefully its still working, when I check tomorrow.
-
Taken83oveR
- Dan isn't smart enough to hire me
- Posts: 119
- Joined: Wed Jun 11, 2008 2:07 pm
I got up this morning, and my phone actually was working, without my pc being on. It survived the night. I will continue to monitor, and hopefully my biggest issue has been resolved.
Modified SPA1001 Firmware version 3.1.19 for my PAP2-NA V1. Note, this firmware is for V1 Pap2's, and will not work on V2. It's nice because you can use both line's, by just pressing the "#" key to switch lines. This could be useful for those who want to use one phone, for two different voip companies (say one for incoming, and a another for outgoing). For example, you could use freedigits for unlimited incoming, and voipbuster for limited outgoing(1-3 minute phone calls), for a totally free solution.
Here are a couple links for those interested in this firmware. Also good for those needing to unlock there PAP2's, but I just used it as a guide to change firmware.
http://www.dslreports.com/forum/remark,14450684
http://www.bargainshare.com/index.php?showtopic=69607
To save you a little time, google "NOTHING_TO_SEE_HERE.zip" In this zip are two firmware's for V1 PAP2 V1's(yes this includes PAP2-NA V1's). Flash the SPA firmware to your PAP2V1, and then flash a newer version from
http://www.sipura.net/download/spa1001/
Once you use one of the modified firmware's, you don't need to modify the newer versions. So flash the old, then flash the newer.
I used spa1001-3.1.19, but you might want to use a lower version, if your pap2 was previously locked, as I hear newer versions can read Vonage info. I did not have to worry about that sense I have a PAP2-NA, which is factory unlocked.
If you decide you don't want the modified firmware, then flash the pap2 firmware from "NOTHING_TO_SEE_HERE", and then grab the latest official linksys firmware (3.1.22), and flash. I really can't offer much support for doing this, but you should find plenty of info in those two links.
Modified SPA1001 Firmware version 3.1.19 for my PAP2-NA V1. Note, this firmware is for V1 Pap2's, and will not work on V2. It's nice because you can use both line's, by just pressing the "#" key to switch lines. This could be useful for those who want to use one phone, for two different voip companies (say one for incoming, and a another for outgoing). For example, you could use freedigits for unlimited incoming, and voipbuster for limited outgoing(1-3 minute phone calls), for a totally free solution.
Here are a couple links for those interested in this firmware. Also good for those needing to unlock there PAP2's, but I just used it as a guide to change firmware.
http://www.dslreports.com/forum/remark,14450684
http://www.bargainshare.com/index.php?showtopic=69607
To save you a little time, google "NOTHING_TO_SEE_HERE.zip" In this zip are two firmware's for V1 PAP2 V1's(yes this includes PAP2-NA V1's). Flash the SPA firmware to your PAP2V1, and then flash a newer version from
http://www.sipura.net/download/spa1001/
Once you use one of the modified firmware's, you don't need to modify the newer versions. So flash the old, then flash the newer.
I used spa1001-3.1.19, but you might want to use a lower version, if your pap2 was previously locked, as I hear newer versions can read Vonage info. I did not have to worry about that sense I have a PAP2-NA, which is factory unlocked.
If you decide you don't want the modified firmware, then flash the pap2 firmware from "NOTHING_TO_SEE_HERE", and then grab the latest official linksys firmware (3.1.22), and flash. I really can't offer much support for doing this, but you should find plenty of info in those two links.