Strange problem on Linksys SPA3102 when using FNB Connect

[seven7seven]

Hi all,


I'm having a strange problem with my SPA3102.

I've configured it to use FNB Connect and outgoing calls work fine EXCEPT after receiving an incoming call on the PSTN line (which is configured to Ring Thru Line 1)!

After an incoming PSTN call I can no longer dial out over Line 1 at all!

The only way to fix it is to reboot the unit by changing some Line 1 configuration (a hard powercycle doesn't work).


This is what happens:

1. Receive call via PSTN - call completes successfully
2. Try dial out over Line 1 SIP account - call FAILS, I get the "Reorder" tone.



This is the syslog of a SUCCESSFUL call over Line 1:

Feb 09 14:40:49 192.168.0.1 [0]Off Hook
Feb 09 14:40:53 192.168.0.1 2. Report digit 0 (1)(40 ms)
Feb 09 14:40:53 192.168.0.1 2. Report digit 8 (1)(40 ms)
Feb 09 14:40:53 192.168.0.1 2. Report digit 3 (1)(40 ms)
Feb 09 14:40:54 192.168.0.1 2. Report digit x (1)(40 ms)
Feb 09 14:40:54 192.168.0.1 2. Report digit x (1)(40 ms)
Feb 09 14:40:54 192.168.0.1 2. Report digit x (1)(40 ms)
Feb 09 14:40:54 192.168.0.1 2. Report digit x (1)(40 ms)
Feb 09 14:40:55 192.168.0.1 2. Report digit x (1)(40 ms)
Feb 09 14:40:55 192.168.0.1 2. Report digit x (1)(40 ms)
Feb 09 14:40:55 192.168.0.1 2. Report digit x (1)(40 ms)
Feb 09 14:40:55 192.168.0.1 Calling:[email protected]:0
Feb 09 14:40:55 192.168.0.1 [0:0]AUD ALLOC CALL (port=16450)
Feb 09 14:40:55 192.168.0.1 [0:0]RTP Rx Up
Feb 09 14:40:56 192.168.0.1 [0:0]ENC INIT 18
Feb 09 14:40:56 192.168.0.1 [0:0]RTP Rx 1st PKT @16450(2)
Feb 09 14:40:56 192.168.0.1 [0:0]RTP Tx Up (pt=18->29b7000e:13650)
Feb 09 14:40:56 192.168.0.1 [0:0]RTCP Tx Up
Feb 09 14:40:56 192.168.0.1 CC:CallProgress
Feb 09 14:40:56 192.168.0.1 [0:0]DEC INIT 18
Feb 09 14:41:02 192.168.0.1 [0:0]LAT++ 6(2)
Feb 09 14:41:03 192.168.0.1 [0:0]LAT++ 5(2)
Feb 09 14:41:15 192.168.0.1 [0:0]LAT++ 5(2)
Feb 09 14:41:15 192.168.0.1 CC:Ringback
Feb 09 14:41:15 192.168.0.1 [0:0]RTP Rx Dn
Feb 09 14:41:22 192.168.0.1 [0:0]RTP Tx Dn
Feb 09 14:41:22 192.168.0.1 [0:0]ENC INIT 18
Feb 09 14:41:22 192.168.0.1 [0:0]RTP Tx Up (pt=18->29b7000e:13650)
Feb 09 14:41:22 192.168.0.1 CC:Remote Resume
Feb 09 14:41:22 192.168.0.1 CC:Connected
Feb 09 14:41:22 192.168.0.1 [0:0]RTP Rx Up
Feb 09 14:41:22 192.168.0.1 [0:0]RTP Rx 1st PKT @16450(2)
Feb 09 14:41:22 192.168.0.1 [0:0]DEC INIT 18
Feb 09 14:41:24 192.168.0.1 CC:Ended
Feb 09 14:41:24 192.168.0.1 [0]FM Alert Stop RxTx (c=0024e5e8;a=0)
Feb 09 14:41:24 192.168.0.1 [0:0]AUD Rel Call
Feb 09 14:41:29 192.168.0.1 [0]On Hook

And this is the log of a FAILED call over Line 1, after having receive a PSTN call:

Feb 07 23:05:19 192.168.0.1 [0]Off Hook
Feb 07 23:05:20 192.168.0.1 2. Report digit 0 (1)(40 ms)
Feb 07 23:05:21 192.168.0.1 2. Report digit 8 (1)(40 ms)
Feb 07 23:05:21 192.168.0.1 2. Report digit 3 (1)(40 ms)
Feb 07 23:05:21 192.168.0.1 2. Report digit x (1)(40 ms)
Feb 07 23:05:22 192.168.0.1 2. Report digit x (1)(40 ms)
Feb 07 23:05:22 192.168.0.1 2. Report digit x (1)(40 ms)
Feb 07 23:05:22 192.168.0.1 2. Report digit x (1)(40 ms)
Feb 07 23:05:22 192.168.0.1 2. Report digit x (1)(40 ms)
Feb 07 23:05:23 192.168.0.1 2. Report digit x (1)(40 ms)
Feb 07 23:05:23 192.168.0.1 2. Report digit x (1)(40 ms)
Feb 07 23:05:24 192.168.0.1 Calling:[email protected]:0
Feb 07 23:05:24 192.168.0.1 [0:0]AUD ALLOC CALL (port=16416)
Feb 07 23:05:24 192.168.0.1 [0:0]RTP Rx Up
Feb 07 23:05:24 192.168.0.1 [0]FM Alert Stop RxTx (c=0024e5e8;a=0)
Feb 07 23:05:24 192.168.0.1 [0:0]AUD Rel Call
Feb 07 23:05:24 192.168.0.1 CC:Failed w/ Calling
Feb 07 23:05:25 192.168.0.1 [0]RegOK. NextReg in 58 (1)
Feb 07 23:05:26 192.168.0.1 [0]On Hook

Line 1 is still REGISTERED after the PSTN call (or at least the unit reports it to be).


The strange part is that this problem DOES NOT OCCUR when I try a different SIP provider (MWeb)??

So it seems something specifically related to FNB Connect - I have not yet seen any other reports of this problem from any other users so maybe it is some specific setting I must change?


All help is much appreciated

Thanks!

Richard

 

[seven7seven]

It turns out this is a known bug in the 5.1.10 firmware (see here).

The problem occurs because after receiving a call on the FXO port (PSTN line) the SPA will only offer the G711u codec on outgoing VoIP calls.

FNB Connect doesn't seem to allow that codec and therefore the calls do not succeed.

The current workaround is to downgrade to 5.1.7.

 

[rapidblue]

Hi there @Richard7

Just wondering if you by any chance know what settings to use to make outgoing calls through the PSTN line? I can get the dial plan setup ok but I don't seem to have the right settings for line voltages etc. etc.

Any ideas??

Thanx man

 

[rapidblue]

Ok, actually got it working - changed my Min CPC Duration from 0.2 to 0.35 I can now dial out through my Telkom line too