Started by dircom, February 16, 2022, 06:15:13 AM
Quote from: dircom on February 16, 2022, 06:15:13 AMAfter 8 years with VestaLink I ported to Voip.msreceived email from voip.ms saying port complete as of yesterday, Using VL SP2, I can still call and be called, although occasionally calling out does not go thru.
Quote from: dircomI can not call out or receive calls via Voip.ms (SP3)
Quote from: dircomI used the Obitalk portal to setup voip.msI made sub accounts, both are registered to the same server also, I can not call form one "extension" or sub account to the other. The are both registered to the same server.
Quote from: dircom on February 18, 2022, 11:38:36 AMWondering if T-Mobile home internet GATEWAY is blocking some port that Voip.ms uses that the other two don't?
Quote from: dircom on February 18, 2022, 11:38:36 AMOK, got Phonerlite to work changing the network from UDP to TCPon the Obi, I changed ProxyServerTransport to TCPWhere is that in the expert dashboard, voip.ms said, enable NAT Keep alive, send every 50 seconds, define register expire time to 300 seconds, change sip to TCP
Quote from: dircom on February 22, 2022, 06:42:38 AMWhat do you think is different with Cox Cable that lets it work using standard Obi config for voip.ms vs Tmobile Internet? Also, for bonus points, are there settings for PhonerLite?