• We do not provide troubleshooting help for unsupported phones. Please try with a supported phone.
  • V20 Update 10 Alpha 2 Learn more

Unsupported Temporary FXO for PSTN

Status
Not open for further replies.

nbl1268

Free User
Advanced Certified
Joined
Aug 17, 2021
Messages
19
Reaction score
2
Hi All, I'm new to 3CX and looking for some advice, have recently set up 3CX v18 on a Raspberry Pi, working well with 2 IP handsets.
Have worked through the training academy videos for the basic certification (haven't bother with actual certification... well as yet) so covered perhaps the minimum knowledge for 3CX,

As a temporary measure (perhaps for 2 or 3 months), I am looking to connect an ATA, that has a single FXO port, to my 3CX setup so that i can make use my current PSTN line as a trunk.
I see that there is a list of 'certified/supported' ATA devices, some of which have FXO port/s (and range in price from AU$300 up to nearly AU$700), also that throughout the 3CX forum discussions there are indications and part examples of where other 3CX users have been able to successfully set up other ATA units, those not (or simply no longer) on the 'certified list'.

So i am rather keen to avoid the unnecessary costs of purchasing a new ATA, and would like to make use of either the LinkSys SPA3102 I have on hand, or a GrandStream HT813 that i can borrow. The HT813 appears to me to be a newer device than the SPA3012, thus potentially the better choice for my circumstance. Thoughts??

However, what i haven't yet found is a clear (and ideally complete) guide to setting up the HT813 as I'm assuming a 'generic' PSTN gateway. Perhaps i simply haven't searched enough yet...
Anyhow if you have a HT813 set up on your system and happy to share advise to help me set up mine, that'd be appreciated.

Thanks
Neil
 
Thanks, that was easier than i expected, working extension using the 3102 FXS port.
Thanks for the link to the 3102 manual, might shelve that for another time (when i cant sleep ;) ).

A bit going on making up dial plans, but here's what made sense to me
Code:
(000S0|1xxS0|[2-9]xxxxxxxS0|0[23478]xxxxxxxxS0|1800xxxxxxS0|1300xxxxxxS0|13[1-9]xxxS0)
Got my 3 digit dialing covered as well as regional number ranges (freecall, local, area codes and mobiles). Can see that in 3CX | Settings | General has option for local emergency numbers.

So i reckon this is done! Many thanks for your help.
 
No problem, glad it worked for you. It's also one more thread, on the forum, to refer people to, wanting to use a 3102. Saves me having to type it all again. :)

It's really a shame that Cisco didn't see fit, to come out with an updated replacement, as they did with some of their ATA's, and instead, simply discontinued it.

Don't forget things like 999S0, for voicemail access (unless that it what the 000 is for), and star codes.
 
Oh, good point, hadn't thought about voicemail. Nope 000S0 (or 000<:@gw0>) is for my TripleZero Emerg number.
Also added 8xxS0 for access to internal paging/ring groups. And *11xxx# is working (perhaps because i pressed hash). Will check the other star codes.

Okay so have consolidated all the guidance notes and steps in to the attached document. Hopefully useful to someone else in the future. Do let me know if you see something in that document that I've got wrong.
 

Attachments

In 3F you mention using the Outbound Proxy, for any local 3102's, I've never had to make use of that, or set Use OB Proxy In Dialog: to yes.

Under section 4, I would recommend using Codec G711 u or a, as the first choice as low bit rate Codecs have an issue with passing audio DTMF, if required.

If the 3102 is factory reset, before you start, then it is not necessary to make mention of any setting (PSTN Caller x DP: 1), that is fine leaving at the default. It just makes things seem more complicated to someone unfamiliar with the 3102.

I've attached a scan, of the original 3CX page, that I had printed out, from number of years ago. Quality is poor as I had to reduce the file size.

Until this page was removed, 3CX also insisted that that Line 1 could not be used at the same time as the PSTN line, which was not correct, So I've always taken the guide with a grain of salt.
 

Attachments

Thanks @leejor, all good, have corrected those points under 3F and 4. I picked G729 as i tought that was the 3CX preferred but good to know about G711 instead. Hopefully this guide isn't removed and is help to others too.
 

Attachments

As far as Codecs go, generally, the "preferred one" is the one that your VoIP provider supports. If you have all devices use that, then you avoid 3CX having to do any transcoding, which, in the past, has led to some audio issues.

But, everyone has their own idea about which one they want to use, and as long a problems don't arise, then choose whatever you want.
 
Could you share the config file?
 
Because it is not supported, there is no 3CX configuration file. If you go though this thread, you shouldn't have a problem, unless you are trying to use it remotely.
 
Status
Not open for further replies.

Forum statistics

Threads
112,147
Messages
590,959
Members
165,167
Latest member
Finatra.us