Randomly my PAP2 w/ MJ credentials won't ring incoming calls. On my cell phone, when I click send.... I hear silence for about 20 seconds then it gets disconnected. At work I call and it rings for a minute or so and get disconnected. While I'm calling I look (via remote desktop) at the pap2 info and see:
Hook State: On Registration State: Online
Last Registration At: 12/16/2008 16:39:45 Next Registration In: 222 s
Message Waiting: No Call Back Active: No
Last Called Number: Last Caller Number:
Mapped SIP Port:
Call 1 State: Idle
Call 1 Tone: None
Normally during an incoming call the Call 1 State is "Ringing". I have to change some settings (any setting) that causes a re-registration then it rings incoming calls for a while then stops again.
I have the sip port as 5070 and the proxy as proxy1.atlanta.talk4free.com. It registers and shows ONLINE just fine. I have setup other MJ+PAP2 combinations for other people (5+ actually) and none of them have this problem. Is there such a thing as an incompatible phone with the PAP2? Defective PAP2? Bad settings?
PAP2 doesn't ring all incoming calls
Moderators: Bill Smith, Pilot
-
Mistar Muffin
- MagicJack Newbie
- Posts: 6
- Joined: Tue Jul 15, 2008 2:14 pm
-
Mistar Muffin
- MagicJack Newbie
- Posts: 6
- Joined: Tue Jul 15, 2008 2:14 pm
I am about to try.... My problem isn't exactly this but lets see if it works...overclock wrote:Make sure your router is forwarding the correct ports to your PAP2. I had the same thing happen where someone would call, wait 20 seconds, and then get a busy signal.
I fixed this by opening ports 5060->5070 and forwarded them directly to my PAP2. Now everything is working just fine.
Good luck!
Kumar
Will not be on forum until after June 15th.
As in you are "piggy backing" off your neighbor's Internet?Mistar Muffin wrote:I have not forwarded the ports but I will try that. What if you are in a situation where you cannot forward the ports? Like at University or a apt with a network you don't control? Thanks.
I don't think you can do anything if you are using the university's internet service. As far as your neighbors; if they left their wireless open, then most likely they left the routers default password.
same issue here with no ringing on spa 2012
i have an spa 2012 that i set up yesterday. i have forwarded ports 5060-5070 on my router to the linksys. it seems that if i make a config change on the linksys and save it when i try to call it it works fine for a few minutes. after that all calls to the mj number result in a pause and a quick busy signal.
i have tried to use the proxy server name and ip address in the linksys config but no luck.
is there anything that i am missing?
thanks.
i have tried to use the proxy server name and ip address in the linksys config but no luck.
is there anything that i am missing?
thanks.
-
zmaddmattz
- MagicJack Contributor
- Posts: 66
- Joined: Sat Nov 29, 2008 11:07 pm
-
Mistar Muffin
- MagicJack Newbie
- Posts: 6
- Joined: Tue Jul 15, 2008 2:14 pm
overclock wrote:As in you are "piggy backing" off your neighbor's Internet?Mistar Muffin wrote:I have not forwarded the ports but I will try that. What if you are in a situation where you cannot forward the ports? Like at University or a apt with a network you don't control? Thanks.
I don't think you can do anything if you are using the university's internet service. As far as your neighbors; if they left their wireless open, then most likely they left the routers default password.
As in, my aunt who live in a Lutheran home in Illinois (far from me) wants one. They provide net access and have ethernet ports on the walls. She obviously will not be doing any forwarding.
On another note I am still struggling with this problem. I have actually tried resetting factory defaults on the pap2 and even tried a new pap2. Same results, even using different credentials. I have ports 5060-5070 forwarded to the pap2 in my router. The pap2 has a static ip and registers and gets online just fine. A few minutes after registering, it cannot receive calls anymore. For the first few minutes, incoming calls ring perfectly. After that, when dialing from outside, like my cell phone, I don't hear anything and just get disconnected. The pap2 web interface shows no incoming calls. I can duplicate this on 2 physical pap2s and I've tried 2 diff MJ credentials, mine here at the house and the one I'm trying to send to my aunt. I don't want to send it to her if I can't get MINE to work right. I also set up one for my friend here in town before I set up mine. They have had ZERO problems. All calls ring in fine (as far as they know). I've called them randomly to check on them and haven't gotten the same silence mine gives, it always rings. I have a Linksys WRT54G with DD-WRT and they have a Belkin router with no mods. Could it be my router or something even though the ports are forwarded?
-
Mistar Muffin
- MagicJack Newbie
- Posts: 6
- Joined: Tue Jul 15, 2008 2:14 pm
I have a text field for NAT keep alive and its set to 15. I changed the register expires from 3600 to 180 and I will see if this fixes my issue. Thank you for your help joevvjoevv wrote:I have a pap2t and I was having a similiar problem. It was solved when I enabled NAT keep alive. Check and see if your unit has a setting for that.
Edit: Also set registration expires to 180
In my experience installing [thousands of] SIP clients it has never been necessary to modify a router's settings to make the SIP client work reliably.overclock wrote:Make sure your router is forwarding the correct ports to your PAP2. I had the same thing happen where someone would call, wait 20 seconds, and then get a busy signal.
I fixed this by opening ports 5060->5070 and forwarded them directly to my PAP2. Now everything is working just fine.
Good luck!
Mistar Muffin diagnosed your problem properly by having you reduce your re-Registration time from one hour to 3 minutes, although I generally recommend 60 seconds for anyone who does not have a severe monthly cap.
Your problem was that MJ's server timed your session out and waited for you to come back on line. A SIP server expects you to remind it that you are alive every so often, generally once every two minutes, because SIP is a non-manageable protocol (because the internet is unreliable by design). If you don't check in within the server's timeout, the server will assume you shut down the client or are suffering an internet outage and will no longer present calls to you.
So, your ATA was sitting around for 57 minutes each hour believing that it was on line, but MJ had disconnected you after about three minutes. Had you chanced to receive a call during that next three minute window (one hour later), it would have rung your phone. Outbound wasn't a problem because the ATA will automatically Register if it can't get through on the first try, costing you milliseconds in connect time that you wouldn't notice.
Great Explanation!mberlant wrote:In my experience installing [thousands of] SIP clients it has never been necessary to modify a router's settings to make the SIP client work reliably.overclock wrote:Make sure your router is forwarding the correct ports to your PAP2. I had the same thing happen where someone would call, wait 20 seconds, and then get a busy signal.
I fixed this by opening ports 5060->5070 and forwarded them directly to my PAP2. Now everything is working just fine.
Good luck!
Mistar Muffin diagnosed your problem properly by having you reduce your re-Registration time from one hour to 3 minutes, although I generally recommend 60 seconds for anyone who does not have a severe monthly cap.
Your problem was that MJ's server timed your session out and waited for you to come back on line. A SIP server expects you to remind it that you are alive every so often, generally once every two minutes, because SIP is a non-manageable protocol (because the internet is unreliable by design). If you don't check in within the server's timeout, the server will assume you shut down the client or are suffering an internet outage and will no longer present calls to you.
So, your ATA was sitting around for 57 minutes each hour believing that it was on line, but MJ had disconnected you after about three minutes. Had you chanced to receive a call during that next three minute window (one hour later), it would have rung your phone. Outbound wasn't a problem because the ATA will automatically Register if it can't get through on the first try, costing you milliseconds in connect time that you wouldn't notice.
I think MJ itself use 870 seconds or 14.5 minutes for re-Registration time. Not sure but; too frequent a re-Registration may flag MJ that your using an ATA.
Sad Times Ahead for this Obamanation !!!! Psalms 109:8
Good point. The SIP specification says several things in this regard. First of all, the SIP server is supposed to include a flag in its register acceptance packet indicating how many seconds into the future it expects to see the client's next registration. Naturally, the client is supposed to honor that flag.VaHam wrote:I think MJ itself use 870 seconds or 14.5 minutes for re-Registration time. Not sure but; too frequent a re-Registration may flag MJ that your using an ATA.
However, since the internet is unreliable by design, there is a failsafe mechanism. If the client does not receive this flag for any reason (server mangled it, failed to send it, got mangled in transit, got mangled by the client, etc.), there is a backup timer that is manually set in the client. This is the timer that we are fooling with.
In the real world, this all works well. However, the MJ world introduces the constraint that we are required by the ToS to use MJ's supplied softphone. So, our challenge now is to find out the value of this backup timer in the MJ softphone and use that value in any alternative client.