However, WebRTC to a PBX in the cloud may be the only relatively stable solution. Adjust Transport type according to your providers recommendation. Go back to Accounts -> select your account and then scroll down to ' Network settings '. Go back, open Advanced and enable ' Run in background '. Go to Config -> Connectivity and enable ' Wi-Fi keepalive ' and ' Stay awake '. WebRTC has a lot of features designed to cope with such environments, but is reportedly a moving target and requires a wide range of technical knowledge to debug, when things go wrong. Receiving calls when running in background. Even then you may have problems with phone registration addresses being unstable (or as I think is happening with someone on the Asterisk forum, problems handling one way media streams - their one way stream is video, which prevent Asterisk learning the true media address). That means you really need to put FreePBX in the cloud. In that situation, you need to put FreePBX on the real internet, or at least in an environment where NAT is minimal, and translations are stable. Your big problem is that any SIP device that can take incoming calls is a server and the sort of consumer grade connection you are using is only designed to cope with information consumers, where the consumer always sets up activities, and these are short duration (e.g request a web page and get the corresponding page back). If I haven’t covered your situation, please describe in detail, including what country the system is in, who is the ISP, and what kind(s) of trunks you will have. For US or Canada, consider Callcentric, VoIP.ms or Anveo. If you need an on-site PBX but also want SIP trunks, get a trunking provider that does NAT traversal at their end. If all your trunking resources are local, CGNAT is not a problem, since the internet connection is just for software updates, etc. For example, you have POTS lines and/or a cellular gateway, and want to be able to make emergency calls during an internet outage. However, you may have a good reason for an on-site PBX. Even if you solve the basic issues, behind CGNAT you won’t be able to have any external extensions, and remote administration would require an external device and service. If you want to run a PBX behind CGNAT, I normally would not recommend it and suggest setting up your system in the cloud. 120 seconds, and/or using the device’s keepalive function. If your registration is unstable, try setting a short expiry, e.g. If you just have endpoints (IP phones, softphones, etc.) behind CGNAT, registering to Asterisk on a public IP, you should have no trouble, since Asterisk handles the NAT traversal.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |