This setup worked just fine for several months. But now, I am having problems receiving incoming calls. Sometimes I get them, most of the time I do not. This has been happening for the last 30 days or so.
A little info.
PAP2-NA Firmware Version: 3.1.22(LS)
proxy = proxy1.Columbus.talk4free.com:5070 (I live in Indianapolis)
SIP port = 5060
RTP Ports = 16384-16482
Use Outbound Proxy = Yes
Outbound Proxy = proxy1.Columbus.talk4free.com:5070
Register Expires = 180
SIP User Agent Name = MagicJack/1.80.466c (SJ Labs)
Dialing Plan = (*xx|911|<411:18004664411>|[235678]11!|<:1317>[2-9]xxxxxx|1xxx[2-9]xxxxxxS0|<:1>[2-9]xx[2-9]xxxxxxS0)
Thanks for the help.
PAP2 - Trouble receiving incoming calls lately.
Moderators: Bill Smith, Pilot
-
Taken83oveR
- Dan isn't smart enough to hire me
- Posts: 119
- Joined: Wed Jun 11, 2008 2:07 pm
-
Taken83oveR
- Dan isn't smart enough to hire me
- Posts: 119
- Joined: Wed Jun 11, 2008 2:07 pm
-
Taken83oveR
- Dan isn't smart enough to hire me
- Posts: 119
- Joined: Wed Jun 11, 2008 2:07 pm
Firmware version 3.1.22-LS is the latest, which I have been using sense I originally purchased the PAP2-NA.
The expire value I have set at 180, as I think that is what the MagicJack runs at.
No need for QOS, as I am not having trouble with sound quality. Its strange as everything worked fine for several months, prompting me to believe something changed on Magicjacks end. I will try your recommendations though.
The expire value I have set at 180, as I think that is what the MagicJack runs at.
No need for QOS, as I am not having trouble with sound quality. Its strange as everything worked fine for several months, prompting me to believe something changed on Magicjacks end. I will try your recommendations though.
You want to set this value to at most 840 seconds, since it must cause your ATA to re-Register before MJ's SIP Server can recognize that you have gone off the air. That value is reported to be 870 seconds. Setting your ATA to a value of more than 870 seconds exposes you to not being able to receive calls between the time that the SIP Server considers you dead and the time that your ATA decides to re-Register.zixy_tris wrote:...set your registry expiry to atleast [sic] 900 secs.
As Taken83oveR says, 180 seconds is a reasonable value if you have a reasonably stable internet service. I often set the value to 60 seconds, but many people believe that this is unnecessarily frequent.
-
Taken83oveR
- Dan isn't smart enough to hire me
- Posts: 119
- Joined: Wed Jun 11, 2008 2:07 pm
Actually I just realized I had the same problem once and I enabled keep NAT alive. It took care of problem. If not try using the dongle and see if you have the same problem. Most likely you should be ok. Try using the box at someones else house. This will atleast tell you that this is not an ISP problem or router problem. If everything fails I am not sure what is going wrong.
Not receiving calls on the PAP2-NA is not an uncommon issue; most common causes for this is when you're behind a NAT router. The ports are open for a set specific amount of time when it registers with MJ's servers; eventually it will close blocking inbound packets. This varies greatly from router to router.
Activating the "NAT keep alive" feature will keep the ports open so you are able to receive calls. The other option is to hard code your ATA to static IP outside of your router's DHCP range and port forward the range of 5060 to 5070 to it. Just choosing the "Yes" option of the "NAT keep alive" is alot easier. If my memory memory serves me correctly the opton is visible when you click the advanced feature link.
Word of caution: Please don't hook your ATA directly to NET (i.e. cable/dsl modem or a connection which pulls a public IP) with the "NAT keep alive" feature active for the reason that is beacons about every 15 seconds which may flag your account.
Activating the "NAT keep alive" feature will keep the ports open so you are able to receive calls. The other option is to hard code your ATA to static IP outside of your router's DHCP range and port forward the range of 5060 to 5070 to it. Just choosing the "Yes" option of the "NAT keep alive" is alot easier. If my memory memory serves me correctly the opton is visible when you click the advanced feature link.
Word of caution: Please don't hook your ATA directly to NET (i.e. cable/dsl modem or a connection which pulls a public IP) with the "NAT keep alive" feature active for the reason that is beacons about every 15 seconds which may flag your account.
That's my quarter's worth, but not enough to call someone who really cares at a pay telephone booth...
-
Taken83oveR
- Dan isn't smart enough to hire me
- Posts: 119
- Joined: Wed Jun 11, 2008 2:07 pm
You should never need to open ports on a router in order to make a SIP client work. I have performed more than a thousand SIP client installations and only once have had to open ports on a router to make the client device work. In that case the client device was in a third world country on an ISP that issued private addresses to their customers instead of public IP addresses. In all other cases, properly configuring the STUN functionality of the client device was sufficient to make the service work.
Another common reason for incoming calls not to work is if your re-Registration timer is set too long. As has been discussed in several other threads on this forum, this setting may not be any larger than 840 seconds, and certainly must not be left at the factory default 3600 seconds. Please read these threads again to understand the forces at play.
Another common reason for incoming calls not to work is if your re-Registration timer is set too long. As has been discussed in several other threads on this forum, this setting may not be any larger than 840 seconds, and certainly must not be left at the factory default 3600 seconds. Please read these threads again to understand the forces at play.
PAP2-NA - Incoming calls problem.
I have a very similar problem. Not able to receive the incoming calls. The problem seem to have been solved following Mberlant suggestion of reducing Register Expire value. While the factory setting is 3600, MagicDump changed to 180 and Mberlant uses 60.
My experience:
When I had it as 180, out of several incoming calls I get one ringing. I reduced that number to 60 it has improved quite well. I further reduced to 40. It has improved substantially. Now I set it at 30. That seems to have resolved the Incoming call problem completely. My thanks to Mberlant.
anant
My experience:
When I had it as 180, out of several incoming calls I get one ringing. I reduced that number to 60 it has improved quite well. I further reduced to 40. It has improved substantially. Now I set it at 30. That seems to have resolved the Incoming call problem completely. My thanks to Mberlant.
anant
And all this time I thought the fast busy was just crappy service from MJ.mberlant wrote:You should never need to open ports on a router in order to make a SIP client work. I have performed more than a thousand SIP client installations and only once have had to open ports on a router to make the client device work. In that case the client device was in a third world country on an ISP that issued private addresses to their customers instead of public IP addresses. In all other cases, properly configuring the STUN functionality of the client device was sufficient to make the service work.
Another common reason for incoming calls not to work is if your re-Registration timer is set too long. As has been discussed in several other threads on this forum, this setting may not be any larger than 840 seconds, and certainly must not be left at the factory default 3600 seconds. Please read these threads again to understand the forces at play.
Seeing this thread, I wanted to see if either one of these suggestions would improve the fast busy. I tried STUN, but that didn't seem to do anything. I then changed the Register Expires from 180 which is what MajicDump has his set as, to 120 and that seems to have fixed my problem.Nice, thanks mberlant.
Smee