Search results

Thanks for clarifying!

While I can't access my PBX from networks I haven't whitelisted, there's still this entry in iptables: $ iptables -L Chain INPUT (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhere Why? And why is it not a problem?

It just dawned on me that apparently OpenVPN server was never meant to be installed on the same machine as Incredible PBX. :oops:

Couldn't find a way to disable IPv6 on my phone and changing the RTP range didn't help. :( Meanwhile, I ruled out that it's related to the hosting provider. I set up another server from scratch on Vultr and I'm running into the same issue.

Thanks for your help. Extending the port range to 9000-65535 didn't make a difference, unfortunately. This reddit thread makes me think it might have to do with a lack of IPv6 on the PBX.

Here you go. This is the log of two subsequent calls. The first one works fine, on Wifi. The second one, on LTE, gets terminated due to "lack of RTP activity" https://pastebin.com/3b1MnUFz

I installed a new cloud server from scratch and the issue is the same. Everything works fine, except no audio on calls from a client registered via mobile. This applies to both chan_sip and pjsip extensions/trunks.

I'm wondering if it has to do with PJSIP. I did a fresh install from scratch and haven't installed PUBLIC yet. The preconfigured PJSIP extension 701 doesn't work with the preconfigured Skyetel chan_sip trunks. Extension 702 (chan_sip) works fine however. Haven't tested 701 with a PJSIP trunk and...

1. Cloud-Server at Hetzner 2. Not when I'm on cellular, everything works as expected in my home network 3. see above 4. I did this, from a 2020 public CentOS server to a fresh Debian install. Afterwards, I followed the new 2021 public setup tutorial

FQDN

Done, but that is not the idea of public, right? I'd like to use my smartphone for calls without being permanently connected to the VPN.

Sorry, the VPN Part was confusing. I just used a VPN to test calls from an external network/IP. The PBX is not connected to the VPN. The VPN server is independent of the PBX server and has its own IP. A client that is connected to the VPN should act like any other external or mobile client when...

Permitted codecs on Groundwire are the same for wifi and cellular

Yes, the correct IP is configured there.

Hi, calls to/from my local wifi work as expected, however when I'm connected to a VPN or when I'm on LTE, calls get established but there's no audio. Groundwire shows the call state as "established" but with 100% package loss and ?/G.722 as the codec. Network: pdp_ip0 [192.0.0.1]. The...

Thanks, that pointed me to the right place: https://docs.hetzner.com/cloud/servers/static-configuration/#debian--ubuntu

No, it's a static IP. I've used CrownCloud before, but wanted to see if I get better performance at Hetzner.

Server entered the "network unreachable" state again. Ping didn't work even after the above adjustment and iptables-restart. After some googling, I tried ifconfig -a and realized that there was no IP address assigned. dhclient eth0 solved the problem - for now. Can this be an issue with IPBX or...

Super helpful, thanks. I was able to reset the root password through the web interface and log in on the web console. Next time the network becomes "unreachable" I'm prepared. So while right now, I can SSH and register my SIP client just fine, pinging e.g. 8.8.8.8 or any other server times out.

I thought about using the console from the provider's control panel, but I don't think it's an option since I disabled SSH password login.