KiwiVOIP / Unifi Talk / Starlink

Forums › VoIP › KiwiVOIP / Unifi Talk / Starlink

StephenNZ

49 posts

Geek
+1 received by user: 3

ID Verified

#318048 10-Dec-2024 10:56

Hi all,

I've spent some time with the KiwiVOIP techs (who have been very helpful) but can't get my Unifi Talk system to receive calls.

My internet is served by Starlink (in bypass mode) to my UDM-SE running talk.

Does anyone have a list of the field codes to set up KiwiVOIP as a third party SIP using Unifi Talk?

Has anyone had luck setting any special port forwarding / routing when using Starlink?

Any help would be hugely appreciated!

BlueOwl

87 posts

Master Geek
+1 received by user: 69

Lifetime subscriber

#3318754 10-Dec-2024 12:25

Not a UDM user, but I've got a GrandStream ATA setup with Starlink to KiwiVOIP. I use a 3rd party router (not the Starlink Wifi/router) connected to the dish much like yours.

No special port forwarding was required, but enabling detailed debug logs on the ATA helped find config problems.

nztim

4012 posts

Uber Geek
+1 received by user: 2710

ID Verified

Trusted

TEAMnetwork

Subscriber

#3318768 10-Dec-2024 12:57

This sounds like a UDP time out thing

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

StephenNZ

49 posts

Geek
+1 received by user: 3

ID Verified

#3318776 10-Dec-2024 13:57

I'm guessing its some firewall or NAT issue, but I've tried everything and come up with no solutions. Making calls is fine, receiving them just comes up with an engaged / user busy tone.

speed

296 posts

Ultimate Geek
+1 received by user: 101

#3318778 10-Dec-2024 14:16

On your SIP client, try enabling TCP transport (as opposed to UDP), and failing that, try enabling TLS.

[I make these recommendations as they are approaches that have historically been beneficial for me in cases of working around multiple levels of NAT, silly SIP application level gateways, short UDP timeouts and various other firewall sins that can sh|t all over your signalling, and therefore I think either could be worth a try in your scenario]

nztim

4012 posts

Uber Geek
+1 received by user: 2710

ID Verified

Trusted

TEAMnetwork

Subscriber

#3318795 10-Dec-2024 14:38

speed:

short UDP timeouts and various other firewall sins that can sh|t all over your signalling, and therefore I think either could be worth a try in your scenario

A good quality firewall appliance allows you to extend the UDP Time out

With Voice traffic you want to use UDP so its fire and forget (and who cares if a UDP packet is dropped)

TCP requires acknowledgement which means that if the ACK packet doesn't get back it wont send the next

Fix the issues with the firewall before changing to stuff like TCP

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

cyril7

9075 posts

Uber Geek
+1 received by user: 2499

ID Verified

Trusted

Subscriber

#3318837 10-Dec-2024 17:40

Hi I have over 50 VoIP lines on Starlink, never had any issues. Most likely issue as Tim pointed out is your sitting behind cg-nat which is the standard Starlink offering and their router is tidying away your UDP sip sessions, change to TCP for SIP transport and see if that helps, I can just about say 100% it will.

Cyril

Dyson

Shop now for Dyson appliances (affiliate link).

coffeebaron

6304 posts

Uber Geek
+1 received by user: 3567

Trusted

Lifetime subscriber

#3318839 10-Dec-2024 17:45

You can also get public IP on Starlinks entry level 40GB priority business plan, $200 / month.

Rural IT and Broadband support.

Broadband troubleshooting and master filter installs.
Starlink installer - one month free: https://www.starlink.com/?referral=RC-32845-88860-71
Wi-Fi and networking
Cel-Fi supply and installer - boost your mobile phone coverage legally

Need help in Auckland, Waikato or BoP? Click my email button, or email me direct: [my user name] at geekzonemail dot com

raytaylor

4076 posts

Uber Geek
+1 received by user: 1296

Trusted

#3320376 14-Dec-2024 09:41

nztim:

TCP requires acknowledgement which means that if the ACK packet doesn't get back it wont send the next

Fix the issues with the firewall before changing to stuff like TCP

Just to clarify, switching the sip transport to TCP will only improve the chances of sucessful registration and incoming call setup.

The audio streams remain UDP.

I always use tcp for the sip transport because at least you know the phone will ring on an incoming call. Getting the RTP audio stream to work is the next separate challenge.

Ray Taylor

There is no place like localhost

Spreadsheet for Comparing Electricity Plans Here

raytaylor

4076 posts

Uber Geek
+1 received by user: 1296

Trusted

#3320377 14-Dec-2024 09:43

I have never used starlink however I understand you do have direct ipv6 connectivity even though IPv4 is CG-Natted.
Therefore can you register against the voip server using a client device that supports IPv6?

Ray Taylor

There is no place like localhost

Spreadsheet for Comparing Electricity Plans Here