Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


breakaway

112 posts

Master Geek
+1 received by user: 5


#251259 15-Jun-2019 16:29
Send private message

Hi,

I've never used this setup before. Basically, I have a device on-site that requires analog telephony service. I have a Linksys SPA2102 that I am trying to configure to make this work.

Can I put the SPA2102 in between my UFB ONT + my ER-X, enable "bridge" mode on the SPA2102, then set my Ubiquiti ER-X as "DHCP", and it will get handed a DHCP IP? And the phones will also work?

Or is it better to put the ER-X behind my ont and have the SPA2102 behind the ER-X? Seeking to minimise grief with Double NAT etc.


Create new topic
cyril7
9073 posts

Uber Geek
+1 received by user: 2499

ID Verified
Trusted
Subscriber

  #2258785 15-Jun-2019 16:35
Send private message

Hi who is the isp and what service is the ata connecting to.


The correct setup is the erx connected to the ont and the ata just as a lan device.

Cyril



RunningMan
9184 posts

Uber Geek
+1 received by user: 4833


  #2258789 15-Jun-2019 16:41
Send private message

The only device doing NAT should be the ERX - SPA just sits as a device on that NAT'd network. SPA should cope with a single layer of NAT if correctly set up.


breakaway

112 posts

Master Geek
+1 received by user: 5


  #2258791 15-Jun-2019 16:45
Send private message

cyril7: The correct setup is the erx connected to the ont and the ata just as a lan device.

 

 

 

Thought so. The remote end is a Asterisk based FreePBX IP PBX.




cyril7
9073 posts

Uber Geek
+1 received by user: 2499

ID Verified
Trusted
Subscriber

  #2258797 15-Jun-2019 17:22
Send private message

Yep that should be fine with the ata behind the erx

Cyril

breakaway

112 posts

Master Geek
+1 received by user: 5


  #2258799 15-Jun-2019 17:26
Send private message

Ok, I've got it plugged in, set the "WAN" to "DHCP" but wouldn't pick up an IP from my ER-X. Setting it to "Static" and manually putting in IP/Subnet/Gatewy/DNS solved that. However now it says register fail.

Is there some way to access logs on this thing to see why register is failing?

Edit: I have a number of PBXes, including an ancient "PBX In a Flash" on CentOS as well. PBX in a flash works... but not my newer FreePBX. Any ideas on how I can figure out why registration fails (e.g. incorrect password etc) would be apprecaited.


RunningMan
9184 posts

Uber Geek
+1 received by user: 4833


  #2258825 15-Jun-2019 17:43
Send private message

If it can't pick up an address via DHCP then you likely have to sort your router config before anything else.


 
 
 

Shop now at Mighty Ape (affiliate link).
breakaway

112 posts

Master Geek
+1 received by user: 5


  #2258828 15-Jun-2019 17:46
Send private message

As I mentioned, I don't believe this to be a connectivity issue since the SPA2102 can register against my ancient "PBX in A Flash" running Asterisk 1.8.28.0, but can't register against my newer FreePBX install which runs Asterisk 13.18.3. It just says "Failed", and asterisk -rvvvvvv on the box isn't showing anything useful.


breakaway

112 posts

Master Geek
+1 received by user: 5


  #2259079 16-Jun-2019 13:57
Send private message

After using wireshark to read the syslog and getting nowhere (it turns out that even syslog provides virtually no info), I decided to re-check each setting one by one. The default SIP port was set to 5061, that's not right - It should be 5060 by default.

All working now. Thanks guys.


Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.