incoming calls goes to VM rightaway

[bedihardeep]

my device info
freephonline a/c
LInksys Spiura SPA 1001
teksavvy cable internet 18 Mbps


outgoing ok
VM ok
incoming call goes to VM right away

for dial tone there is fast beep followed by busy tone

i have forward the following ports

5060 5061 13000 13001

[Jake]

It could be you have DND activated or something like that. Try dialling these codes

*79 (disables DND)
*73 (disables all forwarding on ATA)

You say you get a busy tone when you call out, but you also say you can call out fine - is that right?

[bedihardeep]

yes fast beep followed by busy tone i can call out fine

[bedihardeep]

i dialed *79 still same issue

[julienvf]

Having the same problem with Teksavvy in Vidéotron land. I was able to dig that problem up: Plugged the ATA straight to the modem and it works BUT any router will give me the same problem even if ATA is set up as DMZ host or I do proper port forwarding. I tried 2 different TP-Link routers and a Linksys E1000. As for ATA's, I tried a PAP2T-NA and a new Cisco SPA112 with latest firmware (1.31).

Trace route to voip.freephoneline is:

Détermination de l'itinéraire vers fplproxy.fongo.com [208.65.240.165]
avec un maximum de 30 sauts :

1 <1 ms <1 ms <1 ms 10.10.1.1
2 9 ms 7 ms 8 ms 10.245.205.65
3 28 ms 23 ms 23 ms 10.170.179.81
4 9 ms 9 ms 8 ms 206.248.155.110
5 16 ms 16 ms 15 ms 206.248.155.109
6 16 ms 15 ms 15 ms gw-295ca.torontointernetxchange.net [206.108.34.
78]
7 15 ms 16 ms 18 ms host-208-65-240-165.static.295.ca [208.65.240.16
5]

Itinéraire déterminé.

I even tried this solution found here: http://www.dslreports.com/forum/r278564 ... r~start=20

Which is basically the following:


For those using PAP2 adapter:

Goto: Line 1 tab and make sure following settings are set as follows:
NAT Mapping Enable: YES NAT Keep Alive Enable: YES
NAT Keep Alive Msg: $NOTIFY NAT Keep Alive Dest: $PROXY

Goto: SIP Tab (bottom):
Handle VIA received: YES Handle VIA rport: YES
Insert VIA received: YES Insert VIA rport: YES

But it was no help either... Able to send calls but not receive any. My client was able to send/receive calls prior to the December outage. I set up her ATA around Dec. 15th and everything worked fine then on and off when the outtage occured (not able to register most of the time on PAP2T-NA) on Dec. 19th then since Jan 10-15th, outbound ok but no inbound. Feel free to PM me mods, we can remote desktop if needed for you guys to run all the tests you want.

For the record, my freephoneline account is working fine when I plug my ATA on an Acanac broadband connexion (distributel in Vidéotron land). Here's the traceroute on Distributel:

Détermination de l'itinéraire vers fplproxy.fongo.com [208.65.240.170]
avec un maximum de 30 sauts :

1 <1 ms <1 ms <1 ms 10.10.1.1
2 7 ms 7 ms 7 ms 10.249.153.1
3 * * * Délai d'attente de la demande dépassé.
4 10 ms 7 ms 7 ms 206-80-244-169.cpe.distributel.net [206.80.244.1
69]
5 9 ms 6 ms 8 ms ge-0-2-7.cr1.mtl1.ca.nlayer.net [69.31.142.117]

6 15 ms 15 ms 23 ms xe-0-1-0.cr1.tor1.ca.nlayer.net [69.22.142.81]
7 35 ms 30 ms 27 ms 10gigabitethernet9-9.core1.tor1.he.net [198.32.1
81.52]
8 16 ms 15 ms 15 ms fibernetics-corporation.10gigabitethernet3-1.cor
e1.tor1.he.net [209.51.163.214]
9 15 ms 24 ms 15 ms host-208-65-240-170.static.295.ca [208.65.240.17
0]

Itinéraire déterminé.

[bridonca]

You have this problem because your modem/router does not know where to send incoming RTP packets, and your SPA1001 is not doing much to help out the modem/router. You need to forward incoming ports from your router to the SPA1001.

The default RTP ports the SPA1001 accepts are from 16384 to 16482. You should do fine if you just forward 16384 if your router cannot forward port ranges.

Forwarding 5060 5061 13000 13001 will not really do anything for you, because they are not incoming ports.

Once you forward the correct ports, you should power down the router, ATA and modem, so that ensures the devices use the new parameters, instead of what is in each devices' RAM.

[julienvf]

Even with SPA122 plugged straight on the modem, incoming calls don't work. I even tried to set up SPA122 as bridge... It registers, I can make outbound calls but no incoming calls, even if ATA is registered. I also forwarded all RTP ports + 5060 port (default port) and same thing...

[hete]

I have the same issue, i thought it was my old pc (asterisk) dying alone, and i just created a new server with new settings (more simple) and i got the same problem. The rooter is the same from last month and i dont think it's the problem, because sometime incoming calls work.. and 5 mins later... not. It very random :-/

[gg22]

I can't get incoming calls today either, outbound works fine. This is a known problem with Freephoneline/Fongo lately, but they wouldn't admit it.

[AdeAhmed]

I'm having the exact same problems...going straight to VM.

I've rebooted the modem and I thought that had fixed it, but no, still calls are not getting through.

Strange thing is that on occasion some calls will come through, while others will not. This issue started on Jan 29th only after jeez more than a year of service at least.

On my call logs the ones that aren't working are saying destination out of order. As above, outgoing calls are fine.

I'm using a PAP2...any suggestions as to what to do to fix this?

[bf7041]

Try this:
check you papt 2 settings - under your line 1 tab (if line one is what you are using)

make sure your

Cfwd All Dest: Cfwd Busy Dest:
Cfwd No Ans Dest: Cfwd No Ans Delay:
Selective Call Forward Settings

are all BLANK

I have had a strange issue where on occasion a number will appear in one of these boxes at random - i believe it is an automated hack of some sort - and that will screw things up - you may be able to call out but not receive calls, or you may get a busy signal when trying to call out. Clearing out the number solves it.

I did have my papt 2 in the "demilitarized zone" but have since taken it out - and set up the passwords for user and admin.

Anyone with a papt2 should check this area.

Also, if you are having troubles I suggest imputing the DNS #'s and using a static ip address. Set this up in the system tab. You can use the DNS #s provided by your internet provider - or use public DNS #s. Doing this solved my papt2 re connection issues (actually not mine but my Dad who also has FPL). Tekksavy is his provider and he uses a Wrt54g router . Teksavvy (East) DNS #s are 206.248.154.22 and 206.248.154.170

Hope that helps.
John

[pigeonvoyageur]

I don't know what ATA you are using but you have to change the Proxy in the Line 1 section from voip.freephoneline.ca to 208.65.240.170. That did the trick for me and now all incoming calls work.

[bedihardeep]

Thanks Everyone for replying

i actually search through forum it was my call forward setting has changed or it was like that when i bought my ATA
as shown below in picture those fileds in red were filled up i just cleared those ok now

i had my ATA in DMZ zone as well
i took it out of DMZ zone now

Thanks again