Toggle sidebar Toggle sidebar

Connect 3CX To Unmanaged ATA

Status
Not open for further replies.

Michael.S

Bronze Partner
Joined
Jul 14, 2015
Messages
11
Reaction score
4
Hi

My customer has a VOIP solution from their ISP. There is an unsupported Cisco SPA3000 ATA and a router. (The SPA3000 ATA FXS ports are currently hard wired into their very old phone system... this does not bother me.)

I have access to both devices but cannot see VOIP URL's/Usernames/Passwords. The ISP will NOT give them to me either...

I already sold my client 3CX..... is there a way to somehow configure 3CX to just "use" the ATA's IP address or something and to force all calls through that?

Thanks
Mike
 
For use with a 3rd party device registration must be achieved, this is for security and location confirmation.

Pattons can be used for what I assume is bridging or migration of your customers legacy phone system to the newer one, I have achieved this before myself with an old Avaya >> 3CX migration, if you cannot achieve registration to 3CX (for which you will need IP/Domain name, username and password access) you will be stuck.

https://www.patton.com/solution/PSTN-to-All-IP-Migration/
https://www.3cx.com/voip-gateways/
 
So it is the VoiP password you can't get. What is the service on the 3K. Is it a VoIP to analogue line only, Just the FXS port being used? If that is the case, and this doesn't involve the FXO port, then you could connect the FXS to the FXO and bring the line into 3CX as a trunk.
 
Can’t you just do a factory reset on the ata?
 
CentrexJ said:
Can’t you just do a factory reset on the ata?
Click to expand...

It seems he wants to use 3CX in lieu of the ATA. Resetting the ATA wouldn't do anything for him in this case.
 
This will be no different than being forced to use an ATA supplied by your provider, which could be a multi-line unit. Most are reluctant to give customers the VoIP settings as they wish to retain control over the hardware. This usually reduces the customer complaints as the provider has control over all hardware up to the RJ11 socket. As with getting any analogue lines into 3CX, you will require a PSTN gateway. As the 3102 has one, if it is not being used currently, you can make use of that.
 
Dear all,

Thank you for your super quick responses!


I can't touch the ATA, its supplied by the ISP... I'm forced to use it. But how?

So i get a Patton and connect it to this ATA then somehow the Patton knows to use the ATA to make calls then I configure "something" in 3CX to connect the Patton?
 
If you cannot access the settings on the 3102 (it's supplied and locked by the provider), then you will have to bring the PSTN L line coming out of the 3102 (FXS port) into 3CX as you would any other PSTN line. You'd have to plug it into a PSTN gateway that 3CX then sees as a trunk.
 
Ok, one of the hardwired lines goes to a fax machine and the other goes to their old phone system...

The old phone system will be thrown away once I get 3CX going with VOIP handsets.

I need something with 2 ethernet ports I guess... one to connect to the ISP supplied locked ATA and the other to connect to the router.

is this the right setup?

Can you recommend a device?

Thank you
 
You are overcomplicating things. Pretend the provider ATA are regular POTS lines, because that's what they are emulating. You need a 3CX supported ATA (something from this page https://www.3cx.com/voip-gateways/ ) to connect to the provider's ATA.
 
ok thanks for persevering, I haven't come across this type of setup before with 3CX.

I already purchased a grandstream HT802... I can register it in 3CX no problem. My problem is getting it to talk to the Cisco ATA that has all the VOIP SIP details preconfigured..

I guess I bought the wrong one?

The physical POTS lines Im not worried about, im just trying to work out how to get my Grandstream to talk to this Cisco ATA so I can make calls. I'll work out POTS later (fax).

has anyone done this sort of thing before? As in connect a Supported 3CX PSTN gateway device to a non supported pre-configured PSTN ATA VOIP Gateway device?
 
Again, you are confusing the issue and as well as not understanding the difference between FXO and FXS. Pretend the providers ATA is just PSTN lines and then read this article:

https://www.3cx.com/pbx/fxs-fxo/

And yes you have the wrong ATA.
 
You require a PSTN gateway, not another ATA (Analogue Telephone Adapter). The output from the 3000, an ATA, is the equivalent of a PSTN phone line (48 volts & ring generator), the FXS port. That must plug into an FXO port on a gateway. The gateway will have to be programmed as a trunk device in 3CX, and outbound and inbound rules/routing created. The 3000 is also a Gateway (it's two devices in one), but since you do not have access to programme it, you'd have to purchase another gateway. Single line gateways are rare now-a-days. Most common ones are 4 line and up. You could look for another SPA3000, or the newer SPA3102, which can still be found if you do a search (try Amazon). If you foresee using other PSTN lines in the future, then buying a 4 line FXO gateway may be worth looking into. One issue may be in the splitting of the trunks (a single line in one group and the remaining 3 in another). Some handle this better than others, but you best be prepared to do some manual programming on the device.
 
Last edited:
Yep, im confused. I think I understand what I need to do now. Thank you to all above I really do appreciate your input.

I will respond with results in case others ever see this thread.

Thank you.
 
Thanks eddv123, i'll ask my supplier for a quote on a 4141 JS (FXO).
 
  • Like
Reactions: eddv123
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,934
Messages
589,818
Members
164,810
Latest member
astrobalaji
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom