Why most of time with no ring-tone heard ?

[Ainker]

Finally I have my SPA112 works (in/out calls) BUT...

1) most of time I don't hear ring tone after dialed my number ? however, FPL in fact does calling...

2) tried forward my FPL to my cell with *72..then my cell number...heard dial tone..hangup...however, calls to FPL does not goes to my cell but rather indicating the 'person you are calling is not available'...is not it the way for call forward with FPL ?

Router : SMC, ATA: SPA112, no portforward and after router configuration. I have NAT set as YES where option in the NAT section of SIP.

[Jake]

I am not sure about your #1, but with #2 log into your admin pages online and forward from there. I believe if you try and forward from the ATA itself it will just go to voicemail.

[Ainker]

Thanks Jake...
Regard to #1, that is after I have dialed my number (FPL phone), I expected that I should hear the ring-tone until the other end picks up the call. Most of time I don't and suddenly you just hear the vioce/answer from the callee.

#2, I have checked the online and have it setup now, will see how it works in the next few days...Thanks

[johnfreephone]

looking forward to #1 solution.

[Red89GT]

Question #1

you probably have a NAT issue. I do not know SMC modem/routers that well so I probably wont be much help but try doing a google search using something like the following search terms "(your smc model) NAT voip QOS"

Also read this: http://forum.fongo.com/viewtopic.php?f=8&t=8780 as its more of less the same problem your having.

[Ainker]

Sounded like NAT related. I have SPA112 be connected in a 'unusual way' ...
Modem/Router(SMC D3GN) --> wireless to --> AP Client/Repeater (gigafast) -- Lan port to --> SPA112 ...then analog phone. This is clearly a behind the router setup. It was no INBOUND voice until I have following checked.

NAT Support Parameters
Handle VIA received: yes Handle VIA rport: yes
Insert VIA received: yes Insert VIA rport: yes
Substitute VIA Addr: No Send Resp To Src Port: yes

SMC does has QoS feature but not sure how it works. Notied SAP112 'default' also has some QoS related fields checked ie. CoS (3)/(6)..something like that assumed SPA112 does somehow wanted to utilize the QoS feature if it is present.

Can anyone shed some lights on QoS setup please...Cheers

[Red89GT]

Sounded like NAT related. I have SPA112 be connected in a 'unusual way' ...
Modem/Router(SMC D3GN) --> wireless to --> AP Client/Repeater (gigafast) -- Lan port to --> SPA112 ...then analog phone. This is clearly a behind the router setup. It was no INBOUND voice until I have following checked.

NAT Support Parameters
Handle VIA received: yes Handle VIA rport: yes
Insert VIA received: yes Insert VIA rport: yes
Substitute VIA Addr: No Send Resp To Src Port: yes

SMC does has QoS feature but not sure how it works. Notied SAP112 'default' also has some QoS related fields checked ie. CoS (3)/(6)..something like that assumed SPA112 does somehow wanted to utilize the QoS feature if it is present.

Can anyone shed some lights on QoS setup please...Cheers

Well the first step would be to eliminate any extra piece of equipment that could cause an error. So if possible plus the SPA112 directly into the SMC modem/router. See if you are still getting the same problem.

[Ainker]

Problem remains..however, I do noticed that the next calls (within 5~10 seconds after handup from the first), it works fine, just as normal as expected. Its alway the first (cold) call that missing the ring-tone most of time.

Sounded like something has not be correctly initialized when I first make the first (cold) call and while second call kicks in, that 'setting' still intact and active therefore, it all good. Which setting ? I am looking for answer please.

[Jake]

This sounds like a router problem. What is happening is when a call is made you are re learning all the equipment as to where everything is. After a while your router is forgetting where things are and so isn't working properly.

By the looks of things you are also running things over a wireless access point which won't help.

First I would remove the ATA from the wireless side of your network and see if it works when it is just wired straight into your router.
I would also double check that you don't have two routers on the network trying to sort things out, Especially don't have two DHCP servers. You can help things along by making sure your ATA has a static IP and that the ports that it uses (especially the RTP ports) are forwarded and routed to it. This might help when your router starts forgetting.