Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Home
- Forums
- Internet & Home Phone
- magicJack Error 3002
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-30-2014 12:03 PM
I use a magicJack plus 2014 dongle for VOIP calling. It works until I get a cryptic "Error 3002" message. Rebooting the modem clears the problem but only temporarily. I have tried changed the Ethernet cable between the device and the router (Actiontec V1000H). Also, I replaced the AC power adapter but the error persists. magicJack suggests that the problem lies with the router. Any advice would be appreciated.
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-11-2014 09:12 PM - edited 07-11-2014 09:14 PM
I have not experienced any more 3002 error messages for the past couple of days and no dropped calls. Here is what I did:
External:
- Replaced the AC power adapter.
- Replaced the cheap MJ Ethernet cord with a Cat 5 patch cord.
- Removed the AC power adapter from the surge protector and used an extension cord to connect it to an AC outlet.
Router:
- Found the MJ MAC address under LAN status. The address starts with 6c....
- Assigned a static IP address to the MJ MAC address. I used 192.168.1.80 leaving some room for the dynamic assignment of IP addresses before it.
- Enabled port forwarding for the MJ static IP address. MJ uses ports 5060 and 5070.
- A MJ agent changed the DHCP server lease time to 365 days.
Incidentally, I was pleased to see that the MJ chat agents can and will remotely connect to one's computer and router to diagnose problems. I had to upgrade Java to build 60 before they could connect remotely but that was a trivial task.
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-30-2014 12:57 PM - edited 06-30-2014 01:04 PM
It's a common problem with the MJ+ regardless of the brand/model of router (Actiontc, D-Link, Lynksys, Belkin, etc.) and I've heard of issues with switches as well. The workaround seems to be reboot of the MJ+. Not a great solution since it needs to be done regularly. Some use a timer device to reboot every night.
Rebooting the router also works because it forces the MJ+ to re-acquire an IP address. This is not as convenient as rebooting the MJ+ because your network goes down instead of just the MJ+.
You may want to try assigning the MJ+ a static IP address to see if that helps.
[Edit] Check out this thread in the MS forum.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-01-2014 10:24 AM
Thanks. I forgot to mention in my original post that I had assigned a static IP address to the device; however, the error is still occurring.
Some of the material that has been posted on other forums suggests positioning the device outside the firewall. I am leary of that suggestion because the vulnerability to hackers.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-11-2014 09:12 PM - edited 07-11-2014 09:14 PM
I have not experienced any more 3002 error messages for the past couple of days and no dropped calls. Here is what I did:
External:
- Replaced the AC power adapter.
- Replaced the cheap MJ Ethernet cord with a Cat 5 patch cord.
- Removed the AC power adapter from the surge protector and used an extension cord to connect it to an AC outlet.
Router:
- Found the MJ MAC address under LAN status. The address starts with 6c....
- Assigned a static IP address to the MJ MAC address. I used 192.168.1.80 leaving some room for the dynamic assignment of IP addresses before it.
- Enabled port forwarding for the MJ static IP address. MJ uses ports 5060 and 5070.
- A MJ agent changed the DHCP server lease time to 365 days.
Incidentally, I was pleased to see that the MJ chat agents can and will remotely connect to one's computer and router to diagnose problems. I had to upgrade Java to build 60 before they could connect remotely but that was a trivial task.
