CallerID Inbound SPA3102/3000

[gaijin]

I have found on the web that several people are having a simliar problem to me.

I inherited a site from another "VOIP" guy who unfortunately did not know his proverbial arse from his elbow.

Anyway this guy made wild promises about in relation to my clients setup with a total disregard for the limitations of NAT urgghhh. (but this is a different story)

I am only saying all this because I am stuck with the rubbish hardware (Linksys 3201) that the customer has already bought

I was however successful in convincing the customer to go with pbx in a flash over from TB CE.

OK NOW TO THE PROBLEM:
The thing that I thought I might be able to resolve, but has plagued me is that I can not seem to pass CID from the PSTN to pbxinaflash.
I have tried everything.
The PSTN is being recognised on the device as " ,08xxxxxxx" or "MOBILE,04xxxxxxxx" and I suspect that it is this "weird" presentation that might be throwing out Asterisk.

The obvious things I have done:
Fiddled with the dial plans (SO<:[email protected]>) etc. I have tried the lot!
Updated to the latest Australian version of the firmware 5.1.7

Has anyone else got this to work?

 

[gaijin]

Actually I just found the answer

By forcing the PSTN Caller ID Pattern (on the PSTN tab) to follow the Standard Australian 10 digit pattern with 10 "?"

??????????

It now works!

That was a mere 4 hours of my life down the tube

I can not find this solution documented ANYWHERE!!!

 

[dallas]

Where did you get 5.1.7

The Lynksys web site has version 3.1.20(GW)?

 

[Alex728]

use the American Linksys site

all the ones for us foreigners have outdated firmware

it seems to have all the international settings apart from the UK FXS port impedance (but you can just use the CTR21/Euro type setting as it works)

 

[dallas]

Should have mentioned

I have an SPA3000.

 

[happyddk]

anyone have a quick-and-dirty install and config summary for SPA-3102?

 

[wardmundy]

http://pbxinaflash.com/community/threads/spa3000-help.872/#post-6753

 

[steve54301]

To summarize, because I've had that problem... It probably has to do with the FXO Timer Values.

I've found the PSTN Answer Delay usually needs to be around 3 seconds, before passing the call over.

(Caller ID is sent between the first and second ring.)

 

[dallas]

I agree

I've had my SPA3000 for about 18 months and I've never had any issue getting caller id with PSTN Answer Delay = 3.

 

[steve54301]

use the American Linksys site

all the ones for us foreigners have outdated firmware

it seems to have all the international settings apart from the UK FXS port impedance (but you can just use the CTR21/Euro type setting as it works)

Speaking of outdated firmware:
For what it's worth, I'm still using an older SPA-3000, hardware version 2.0.1(574f) from about 2005? when I got into this.

It came with 3.1.7 firmware. I spent weeks trying to figure out a one way echo. Downgrading to 2.0.13 firmware fixed that to my amazement. I'm still running that.

So old firmware isn't necessarily a bad thing.

 

[wardmundy]

I spent weeks trying to figure out a one way echo. Downgrading to 2.0.13 firmware fixed that to my amazement. I'm still running that.

Another little trick that always worked for us when echo appeared during a conversation... put the call on hold and then pick it up again. Works like a champ to remove echo with the SPA-3000 at least.

 

[gaijin]

I've had my SPA3000 for about 18 months and I've never had any issue getting caller id with PSTN Answer Delay = 3.

The problem was not with the SPA

receiving​

the caller ID, The caller ID showed up in the SPA logs! It was just not passing it through to the

PiaF​

box. And it is

something​

to do with the

Australian​

CID system.

 

[gbrook]

Hi,
Never had a problem with CLI on these boxes and I am in Brisbane.

Cheers
Garry

 

[dallas]

gailin,
Australian CID is the same as the US (Bellcore).
In the PSTN Line tab, PSTN-to-VOIP Gateway Setup, I have "PSTN CID For VoIP CID" set to 'yes', "PSTN CID Number Prefix" is blank and "PSTN Caller ID Pattern" is also blank. If these settings don't work for you then I'd start looking at the Asterisk CLI to see what's arriving.

cheers
Dallas