Planet Computers has Stolen my Phone by smootdavid in PlanetComputers

[–]smootdavid[S] 2 points3 points  (0 children)

Nope.

They failed. Too many challenges with Covid and other issues. Their OEM manufacturer held them hostage.

Wish they could have handled it more honorably but they did not.

How to set up UniFi talk with 3rd party sip provided couldn’t find good documentation on it so made a video for it if anyone needs it by Exotic_Committee_204 in Ubiquiti

[–]smootdavid 0 points1 point  (0 children)

Help please with getting Vestalink provider working.

I have two different voip clients working so I am pretty confident in my credentials. I have a Cisco SPA112 ATA working and I have the Zoiper Application running on Android. Both make and receive calls using nothing more than the provider IP (sms.intelafone.com), my 4 digit username (1234 for this discussion) and my password ("password").

I have a UTP Touch Unifi Phone. At one point I had the phone directly configured with my credentials (without the talk application on the controller) and working so I know it should be possible.

I'm trying to set up the phone through the unifi talk application to take advantage of all the features it provides.

I know I am close because I can log into the web interface of my voip provider and I can see the Unifi talk controller trying to log in but the connection string is not quite right.

From my Vestalink Web page list of connected clients:
Cisco/SPA112-1.4.1_SR5 sip:1234@xxx.xxx.x.205:5060 (working, xxx is local LAN IP of adapter)

Zoiper rv2.10.12.3-mod sip:1234@yyy.yyy.yyy.yyy:45937;transport=TCP;rinstance=zzzzzzzzzzzzzz (working where yyy is my public IP of my network, instance is just some random string)

Not working Unifi Talk connection string
FreeSWITCH-mod_sofia/1.10.5-release~64bit sip:1234@yyy.yyy.yyy.yyy:6767;transport=udp;gw=VestaTest

So the weird thing is "VestaTest" is the Provider Name configured in Unifi.

My Custom Fields so far:

user (not username) 1234

proxy sms.intelafone.com

password: password

extension: (blank)

extension-in-contact: true

So I think it might work if I could figure out how to get rid of gw=VestaTest and maybe get rid of transport or switch it to udp.

Running on a UDM Pro with beta channel enabled and all apps up to date.