SPA122 not receive incoming call

[jenyin]

I DO search a lot here, no luck, so I have to pose here.

ATA: SPA122
Firmware Version: 1.3.3 (015) Dec 13 2013
NEW phone number from FPL.
I follow this post,http://forum.fongo.com/viewtopic.php?f=15&t=7918
Change these below after reset to factory setting.

User ID: **
Password: **
Realm: voip.freephoneline.ca or voip2.freephoneline.ca
RTP Packet Size: 0.020
Ring Tone Frequency: 52
Ring Tone Voltage: 90
Dial Plan:(911|[2-9]xxxxxxxxx|1xxxxxxxxxx|011xxxxxxxxxxxx.|98*|[6-7]x*xxxxxxxxxxx.)
or
(*xxS0|[3469]11S0|0|[2-9]xxxxxx|[2-9]xx[2-9]xxxxxxS0|1[2-9]xx[2-9]xxxxxxS0|xxxxxxxxxxxx.)


Network:
Modom ==> ATA ==> router


1)still can only call out and talk, but can not receive incoming call from my cell,647716****. get answer 'The customer you are calling is unavailable, please try later'. But can receive calls from other FPL number.
2) Already try *73 and *79. no luck.
3) Check the call log on website, no any log. I call from my cell,647716****

Please help. THx.

[bridonca]

What do you have for a router? Did you route some RTP ports from the router to the ATA? 16384 to 16438 seems to be the default RTP port range for the SPA122. The router not being able to properly route RTP ports to the ATA is the main cause of no incoming calls.

[jenyin]

What do you have for a router? Did you route some RTP ports from the router to the ATA? 16384 to 16438 seems to be the default RTP port range for the SPA122. The router not being able to properly route RTP ports to the ATA is the main cause of no incoming calls.

Hello, thank you for your reply, but as I said
Network:
Modom ==> ATA ==> router

So I don't think have problem with the router? is it?

[jenyin]

Problem resolved. After customer support change a phone number for me, from 437 to 647, quite wired.

[wt76]

I think a lot of cell carriers have routing issues with the 437 numbers. I recently signed up as well and was assigned a 437 number. I was able to call the number with no issues using Bell POTS, Skype Out and Google Voice, but it was a no go from a cell phone. After having the service active for about 3 or 4 days it eventually started working from a cell phone automatically.