Incoming call from my work line doesn't connect

[sternem]

I have a SPA 3102 that works fine for any incoming and outgoing I've thrown at it except from my work. We use Cisco IP phones and when I call to my home ATA, it rings for 1 or 2 rings then the line is dropped before my wife picks up. When I check the call log for the failed call, it shows Description "Normal completed call" and Disconnect Reason "Normal call clearing".

Any clues as to what could be going on?

[FONGO_steve]

Is your ATA set to not use only the preferred codec? I'm wondering if there's some sort of codec negotiation issue going on between your ATA and the IP phone setup at your work.

If you can PM me exact details of one call, I can see if a detailed SIP log will show anything.

[sternem]

Hi Steve, I set my preferred codec to G729a and Use preferred codec only to No. I'll PM you the time and number of one of the failed calls. Thanks.

[hongster]

Hi,
I've used FPL for over a year now and has been satisfied, but it's been a while that others have claimed they've called me that I never had my phone ring at all. I didn't believe it, so just today I checked the log on FPL and under the Failed Calls section, two calls, at 01.04.11 12:44:30 and at 01.04.11 12:44:48, did not ring at all. Interestingly, the Description is "Normal call completed" while the Disconnect reason is "Normal call clearing" .What is wrong? I've done like others in the forum said, setting the expiry to 60 (instead of 3600). I use a UTStar IAN-02EX. Everything else seems to work fine. Am I not configuring things right, or is there something wrong at FPL from time to time?

[hongster]

FYI - the caller got a busy signal. I'm already using G729a as my preferred codec.

[FONGO_steve]

Hi,
I've used FPL for over a year now and has been satisfied, but it's been a while that others have claimed they've called me that I never had my phone ring at all. I didn't believe it, so just today I checked the log on FPL and under the Failed Calls section, two calls, at 01.04.11 12:44:30 and at 01.04.11 12:44:48, did not ring at all. Interestingly, the Description is "Normal call completed" while the Disconnect reason is "Normal call clearing" .What is wrong? I've done like others in the forum said, setting the expiry to 60 (instead of 3600). I use a UTStar IAN-02EX. Everything else seems to work fine. Am I not configuring things right, or is there something wrong at FPL from time to time?

Hi Hongster,
According to SIP logs for the two calls you mention in your post, it appears as if your ATA is not responding to our invites. The first call sent five invites from our server to your device, but none were responded to. The device is registered with us though and we do see it in the SIP log, so it appears to be a device related problem.

Also, please be sure to read the rules and be careful not to hijack threads

[marginal]

I have the same problem.
Every now ant then incoming calls get silence, then fast busy signal and my phone does not ring.
I am using a Linksys PAP2, Firmware Version: 3.1.22(LS).
Please help.

[FREEA_k]

I have the same problem.
Every now ant then incoming calls get silence, then fast busy signal and my phone does not ring.
I am using a Linksys PAP2, Firmware Version: 3.1.22(LS).
Please help.

does it shows a incoming call in FPL portal? just to check there is a call and pap2 is not ringing on its own.

if yes, try a hard reboot(30 second power off for both router and pap2 and then on again) sometime a port redirection is easily solved by a reboot.

if still a problem, match the pap2 settings with the settings on the forum here and reboot.

shd be no pb.

[marginal]

I have not checked that out yet ...
For now, I believe the problem disappeared.

Thanks a lot.

[sternem]

Hey guys, just thought I'd update with the fix I found.

It turns out I had a STUN server set to try and eliminate port forwarding. This was failing for some reason, but not before trying 8 times. This was probably just long enough to caused the work side connection to think my home line was busy (versus calls from other incoming lines). When the ATA eventually gave up on the STUN server, my home line would ring, but no connection at this point.

I removed my STUN server settings and relied on the NAT traversal settings. Now calls from my work line are fine! The other side effect is outgoing calls dial super fast now, from 2 - 4 seconds.

I set up a slogsrv.exe on a separate computer to log debug messages. This was how I was able to see the large number of attempts with the stun server. Highly recommended to anyone that has connectivity issues. Here's the link that helped out: https://supportforums.cisco.com/docs/DOC-9862/