Replace Slingshot Vibre+Wifi+VOIP Router with Unifi UDM

Forums › VoIP › Replace Slingshot Vibre+Wifi+VOIP Router with Unifi UDM

Muxa

12 posts

Geek

#274543 27-Aug-2020 19:43

I have VDSL/FIBRE Dual Band AC1600 Gigabit Gateway with VoIP from Slingshot.

I've replaced it with a Unifi Dream Machine Pro (UDM) for Internet access.

Now I need to restore VoIP functionality (with Slingshot).

I'm a newbie when it comes to VoIP. My understanding is I can get a new VoIP ATA box (e.g. like https://www.geekzone.co.nz/forums.asp?forumid=43&topicid=231983)

What I am not sure about is what configuration UDM requires. Just 5060 port forwarded to the ATA?

In addition, would it be possible to repurpose Slingshot's modem as an ATA box (instead of getting a new box)?

Any help will be appreciated.

Spyware

3261 posts

Uber Geek

Lifetime subscriber

#2550948 27-Aug-2020 20:18

Simply have the UDM present a tagged port with vlanid=10 and assign an address to Slingshot router WAN port via DHCP.

Note: Slingshot issue routers are configured IPoE (DHCP client) vlanid=10. There specification of use of PPPoE was for third party routers but either config works.

Spark Max Fibre using Mikrotik CCR1009-8G-1S-1S+, CRS125-24G-1S, Unifi UAP, U6-Pro, UAP-AC-M-Pro, Apple TV 4K (2022), Apple TV 4K (2017), iPad Air 1st gen, iPad Air 4th gen, iPhone 13, SkyNZ3151 (the white box). If it doesn't move then it's data cabled.

Pluralsight

Learn cloud, mobile, security, data and web technologies with Pluralsight (affiliate link).

cyril7

8950 posts

Uber Geek

ID Verified

Trusted

Subscriber

#2550949 27-Aug-2020 20:19

hi, you should not have to and most certainly not recommended to port forward any SIP traffic, infact no traffic at all.

The slingshot modem should simply create out bound connections to the servers and thats it.

You will find the ATA is bound to the wan port of the slingshot modem, so you will have to connect that to your new LAN, but you will need to remove the need for using vlan10 and ppoe and use dhcp on the wan instead.

Cyril

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#2550956 27-Aug-2020 20:39

I don't believe Slinsghot give out SIP credentials for 3rd party hardware.. And as pointed out you should never port forward SIP traffic unless you have very specific reasons for doing it and have either whitelisted firewall rules or a SBC to protect it.

Muxa

12 posts

Geek

#2550973 27-Aug-2020 21:21

Thanks for all your suggestions. I won't forward any ports.

I have also found this guide that explains exactly the same situation: https://www.geekzone.co.nz/forums.asp?forumid=81&topicid=274421&page_no=1

It sort of worked - I can make outbound calls, but incoming cals don't work. I have asked a question on that thread about this problem plus couple of other problems. I won't want to double it up here, it case duplication information on the forum is frowned upon.

speed

287 posts

Ultimate Geek

#2550974 27-Aug-2020 21:25

Muxa:

I can make outbound calls, but incoming cals don't work.

Nice work! At least you know your SIP auth details are confirmed correct then (otherwise outbound would have failed). Focus your investigations on 'registration' - it's registration that gets you inbound calls [in a modern NAT'd world].

nztim

2837 posts

Uber Geek

ID Verified

Trusted

TEAMnetwork

Subscriber

#2550985 27-Aug-2020 21:56

sbiddle:
I don't believe Slinsghot give out SIP credentials for 3rd party hardware.. And as pointed out you should never port forward SIP traffic unless you have very specific reasons for doing it and have either whitelisted firewall rules or a SBC to protect it.

I have my SIP details as I am on their legacy iTalk plan for VOIP since 2004

I can confirm it works just fine behind NAT using a Yealink Cordless Phone W56H

Any views expressed on these forums are my own and don't necessarily reflect those of my employer.

nztim

2837 posts

Uber Geek

ID Verified

Trusted

TEAMnetwork

Subscriber

#2550987 27-Aug-2020 21:57

speed:
Muxa:

I can make outbound calls, but incoming cals don't work.

Nice work! At least you know your SIP auth details are confirmed correct then (otherwise outbound would have failed). Focus your investigations on 'registration' - it's registration that gets you inbound calls [in a modern NAT'd world].

Need to enable NAT keep alive due to it been behind another router

Any views expressed on these forums are my own and don't necessarily reflect those of my employer.

Spyware

3261 posts

Uber Geek

Lifetime subscriber

#2551042 28-Aug-2020 05:41

Muxa:

Thanks for all your suggestions. I won't forward any ports.

I have also found this guide that explains exactly the same situation: https://www.geekzone.co.nz/forums.asp?forumid=81&topicid=274421&page_no=1

It sort of worked - I can make outbound calls, but incoming cals don't work. I have asked a question on that thread about this problem plus couple of other problems. I won't want to double it up here, it case duplication information on the forum is frowned upon.

That thread simply describes a butcher job on the Slingshot router that is unnecessary in your case as the UDM is capable of presenting a tagged port on another network for Slingshot WAN. Slingshot router could have been left on defaults in order to work as it should if required. Note: If Slingshot router has the same network, 192.168.1.0/24, on both its interfaces, LAN and WAN, then it won't route traffic.

nztim

2837 posts

Uber Geek

ID Verified

Trusted

TEAMnetwork

Subscriber

#2551058 28-Aug-2020 07:17

Spyware:

. Note: If Slingshot router has the same network, 192.168.1.0/24, on both its interfaces, LAN and WAN, then it won't route traffic.

this is a good point you would need to change away form this subset on either the slingshot router or UDM

Any views expressed on these forums are my own and don't necessarily reflect those of my employer.

Muxa

12 posts

Geek

#2554359 31-Aug-2020 18:52

I got it working. Not sure what exactly fixed it but here's what I did:

1. Restored settings to a backup that I took before attempting any of these changes

2. Removed all WAN interfaces

3. Added new IPoE interface, with address obtained automatically, VLAN 3 (my USG already had a VLAN 3), DNS1: USG's private IP (10.1.3.1), DNS2: 1.1.1.1

4. Left DHCP server and WiFi on (so I could connect to NF18 and configure it if required)

5. Plugged WAN into USG's LAN port

This made it work.

In addition, under LAN I've added a secondary IP address 10.1.1.2. I wanted to connect LAN1 port to another port of USG so that I can access NF18 from the network. But for some reason the network wend down (there might have been some kind of network loop). So I unplugged it.

I have also tried enabling port 80 on WAN port to be able to access NF18 from the network (under Management > Access Control > Services Controls) , but it still did not work for some reason.

Any ideas how I can connect to NF18 web UI from USG network?

Muxa

12 posts

Geek

#2554895 1-Sep-2020 15:41

Muxa:

Any ideas how I can connect to NF18 web UI from USG network?

Web access from the WAN port has started working. I think the problem was with IP (I assigned a static address, but it did not quite work as it was reverting to a different address, so I set the static address to the default value)