New Setup - Unable to receive calls

[ret]

I've spent hours fiddling around with this over the past couple of days. I have no issues calling out(local or long distance) but incoming calls go straight to voice mail.
Device Information:
SIP: Grandstream HT286 ATA / IP: 192.168.0.20
modem/router(all in one): Rogers - Cisco DPC3825

I forwarded the ports 5060-5061 & 10000-20000 in the router.


Grandstream Status




Other troubleshooting: Turned the modem/router into a bridge and hooked up a DLINK router and forwarded the ports but still with no luck. I've seen other posts of more ports to forward(still nothing) and also turned off the firewall on both routers(all in one, and DLINK).

I'm out of ideas although I searched the forum and saw a thread that said the backend had rings to voicemail set to 0/1 although on the web profile the user had it set to 3(I set my to 5 first, now to 3). So I will call tomorrow to see if that could be an issue.

If anyone see's something wrong or has any things I could try that would be much appreaciated!

Thanks!

[FONGO_mike]

I know this may sound silly, but how rings do you have configured before voicemail picks up? can you PM me your number so i can make sure everything is ok on our end please?

[cu2o2o2]

I've spent hours fiddling around with this over the past couple of days. I have no issues calling out(local or long distance) but incoming calls go straight to voice mail.

...

If anyone see's something wrong or has any things I could try that would be much appreaciated!

Thanks!

Don't try this...just do it! Anyone of the following will work.

In the Port Range Forwarding section of your router, change the UDP 10000-20000 to UDP 5004-5006 (allowing for 3-way calling). Do not change your ATA settings.

___OR___

On your ATA, change the local RTP port to any value between 10000-20000. Also set Use random port to No. Do not change any of your router settings.


After doing any of the above, shutdown your router and ATA. Then power up your router then after a minute, power up your ATA. Enjoy your free phone.

P.S.
You may want to check the NAT traversal to NO, as I am not convinced that it is of any help. My PAP2T's had been solid for more than 2 years without using a STUN server.

And if I were you, I would check Use Bell-style 3-way conference to YES, in which case you would connect the 3rd party to a conference call the way you did with a Bell landline.

[Melchizedek]

If you ported your number from another provider, make sure it is not still listed in your account from that provider (eg. I had to delete my number from my voip.ms account before being able to receive calls).

[dibsmft]

You do have stun selected but no server named, so, you can also try with stun and a named server (eg. stun.callwithus.com). I use stun on my 286 with the provider I have registered on there,

[cu2o2o2]

You do have stun selected but no server named, ...,

Good catch! THAT could be one cause of his problem.

[ret]

You do have stun selected but no server named, so, you can also try with stun and a named server (eg. stun.callwithus.com). I use stun on my 286 with the provider I have registered on there,

I tried this as well last night using stun.callwithus.com- no dice!

[ret]

I've spent hours fiddling around with this over the past couple of days. I have no issues calling out(local or long distance) but incoming calls go straight to voice mail.

...

If anyone see's something wrong or has any things I could try that would be much appreaciated!

Thanks!

Don't try this...just do it! Anyone of the following will work.

In the Port Range Forwarding section of your router, change the UDP 10000-20000 to UDP 5004-5006 (allowing for 3-way calling). Do not change your ATA settings.

___OR___

On your ATA, change the local RTP port to any value between 10000-20000. Also set Use random port to No. Do not change any of your router settings.


After doing any of the above, shutdown your router and ATA. Then power up your router then after a minute, power up your ATA. Enjoy your free phone.

P.S.
You may want to check the NAT traversal to NO, as I am not convinced that it is of any help. My PAP2T's had been solid for more than 2 years without using a STUN server.

And if I were you, I would check Use Bell-style 3-way conference to YES, in which case you would connect the 3rd party to a conference call the way you did with a Bell landline.

Thanks, I'll try this after work!

[cu2o2o2]

...
In the Port Range Forwarding section of your router, change the UDP 10000-20000 to UDP 5004-5006 (allowing for 3-way calling). Do not change your ATA settings.
...

After reviewing my post, the above should read...

In the Port Range Forwarding section of your router, change the UDP 10000-20000 to UDP 5004-5006 (allowing for 3-way calling). In your ATA, set Use random port to NO.

Good luck!

[ret]

...
In the Port Range Forwarding section of your router, change the UDP 10000-20000 to UDP 5004-5006 (allowing for 3-way calling). Do not change your ATA settings.
...

After reviewing my post, the above should read...

In the Port Range Forwarding section of your router, change the UDP 10000-20000 to UDP 5004-5006 (allowing for 3-way calling). In your ATA, set Use random port to NO.

Good luck!

Well tried that - again no luck. I'm going to try it at a neighbors - different provider/modem/router and phone.

Could it be the phone at all? I downloaded the app and it works fine receiving calls although I'm guessing it uses different protocols

Thanks for all the help so far!

[bridonca]

Your Grandstream ATA needs one incoming RTP port to be forwarded to it. I believe it is 5004, but whatever it is, make sure the router and the ATA is on the same page.

Quit forwarding 10000-20000. no real damage, but no real point.

You can forward SIP port 5060 form the router to the ATA, but it really is not necessary.

You might want to set up STUN, use a STUN server like stun.callwithus.com

Turn off everything for a minute, the modem/router, and ATA. Then turn on the modem/router, wait 30 secs, then turn on the ATA.

[ret]

Sorry was away for a few days. So I've tried all suggested




I enabled forwarding - when I dial my voip number from my cell it rings twice then starts ringing on the # I forwarded too, yet never rings on my voip phone.

[TheHardy]

*rereading*

Errr ... I did not see that before ... forwarding eh ...

[TheHardy]

I enabled forwarding - when I dial my voip number from my cell it rings twice then starts ringing on the # I forwarded too, yet never rings on my voip phone.

So ... did you try it WITHOUT the forwarding??

Cuz the forwarding is done on a platform level before the ATA even gets involved ...

Check your forward settings via the web interface -- confirm that it is not ALWAYS FWD, but rather FWD when UNAVAIL ... otherwise, the above behaviour is correct ...

If you are having problems with in the INCOMING calls, leave the forwarding alone until you get the incoming correctly, otherwise you are just juggling more balls in the air at one time than you need to ...

Of course this could be a silly suggestion too, but what happens if you disconnect the ATA, load the PC software and try placing and receiving calls via the PC softphone? Does that go to voicemail or fwd without ringing the softphone app too??