Outgoing/Incoming Issue - Linksys SPA 3102

[aad999]

We are not able to make PSTN outgoing or incoming call using Linksys spa 3102. I have configured the linksys device as per the 3CX document.
Local extensions work fine.

Telephone line ----Connected to Line port
Ethernet cable----Connected to Ethernet port

Outbound rule is created to dial PSTN outgoing number.

When i dial PSTN outgoing number the call ring one time and shows connected.
When i dial in my PSTN number it keeps rining.

22:43:51.015 [CM503007]: Call(18): Device joined: sip:[email protected]:5061

22:43:51.015 [CM503007]: Call(18): Device joined: sip:[email protected]:5070;rinstance=14175665db07b636

22:43:51.015 [CM505002]: Gateway:[MyLinksys] Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA3102-3.3.6(GW)] Transport: [sip:192.168.1.101:5060]

22:43:51.000 [CM503002]: Call(18): Alerting sip:[email protected]:5061

22:43:50.390 [CM503004]: Call(18): Calling: PSTNline:99857687@(Ln.10001@MyLinksys)@[Dev:sip:[email protected]:5061]

22:43:50.359 [CM503010]: Making route(s) to <sip:[email protected]:5060>

22:43:50.359 [CM505001]: Ext.1001: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX VoIP Client;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Phone 7.0.4526.0] Transport: [sip:192.168.1.101:5060]

22:43:50.343 [CM503001]: Call(18): Incoming call from Ext.1001 to <sip:[email protected]:5060>

Any help would appreciated.

 

[alan2010iq]

As I explained in my previous post, the problem is not with the 3CX system or SPA3102 and here is the reason. When I plug in the line which is working ok with incoming PSTN caller ID to the first SPA3102 unit which does not show the caller on the second SPA3102, it works fine and the same when I plug in the line which is not working on the SPA3102 which does not show the caller id on the SPA unit which shows the caller id, it is the same and no caller id is showing. That means it is an issue with the PSTN line signaling/caller ID method which are from two different providers and it may be the caller ID method or other settings causing a problem with the caller ID. I am sure I know what the problem is but I don't know how to configure the SPA3102 to deal with it.

The problem is the line which is not showing PSTN caller ID according to the syslog sends the caller ID DTMF before the first ring, but the SPA3102 start detecting the caller ID FXO: Start CNDD after the first ring. I tried PSTN answer delay with different values it did not help.

Alan

 

[leejor]

Sorry, I missed that....

So these are two different providers, I assume. You may need to talk to the provider, to see what "method" they are using to send CID. As I understand it, in the UK, you have the "standard" BT method (which seems to send the data before the first ring after a line reversal) http://www.sinet.bt.com/ (go to document 227) and then some cable companies have adopted various "other" means of sending CID, including Bellcore. I have only used the North American (Bellcore)method, where it is sent after the first ring, the reason being that the first ring was used to "wake up" the CID unit (same reason BT sends a reversal). You may just have to try some of the other CID methods in the 3102 to see if one will work with your provider.

Can you verify, using a meter, that the non-working provider is sending the reversal before the CID info?

 

[alan2010iq]

Hi,

Thanks for your reply. Actually now I know exactly what the problem is. As suggested, the PSTN line which is working fine with SPA3102 with correct Caller ID for incoming PSTN calls sends polarity reversal. However, the other PSTN line which does not show the caller ID on the other SPA3102 does not send polarity reversal!! Also, when I swap the lines on both SPA3102, the one which is not showing the caller id does not show it on the other SPA3102. So it is definitely the polarity reversal issue. I also changed the detect polarity reversal setting to no and various caller id detection methods, still no caller id.

Any advice would be very much appreciated.

Alan

 

[leejor]

If it were me, I would be contacting the provider to see if the lack of reversal is intentional or a fault with your line equipment. Have they specified which CID devices will work with their service?

You don't say if your provider is supplying your dialtone via some sort of a cable box, in your home, or it is coming to you from a central office over a cable pair. If it is the former, then there may be a fault, or misconfiguration in your box. Have you tried any other BT type CID device on that line? Does it work?