ALERT Buh-bye CentOS.

[Halea]

I'd stick with the Debian 2021 B5 for a fresh install of Asterisk-16. So far, its pretty bullet proof. There are some gotchas in moving to Asterisk-18 and it took me a good bit of googling and comparing scripts to get it to work. I don't know what other hidden gotchas are waiting to be discovered.

I agree. That's what I got up and running on my new hardware, first on bare metal, next under proxmox with 2 cores and 2GB of RAM. Both worked very well. I think I figured out the delay issue with the dashboard, or at least found a way to avoid it. It seems that the software needs to resolve a name (not an RSS feed as they were all removed) which was being prevented by the secure DNS server on our network. I switched to a regular public DNS server and the dashboard started to load instantly. Later I enabled that protection again but the delay seems to be permanently gone. Unfortunately I couldn't find the name in the DNS/firewall logs as verbosity was set to minimal.
So 5 stars well deserved for iPBX2021!

 

[wardmundy]

Faxing passes with flying colors with Skyetel, Debian 10.7, and Asterisk 18...

 

[wardmundy]

Beta6 Now Available

Hopefully, this will be the final beta release before Opening Day on January 1, 2021. Beta6 adds the ability to install either Asterisk 16 or Asterisk 18 initially. The default is now Asterisk 18, but you can edit the shell script and change ASTVER to 16 in Line 34, if desired.

 

[kenn10]

I am seeing some issues in Asterisk 18 where if the far end disconnects before the extension hangs up, the connection is not torn down. Then the extension is rung back and disconnects when you answer. Not sure what's up but the trunk is BulkVS. Still testing and will try other provider trunks.

Added info: trunks and station are PJSIP. I'm fairly pedantic in testing so I'll be spending the next few days in testing. I'm not ready to put my production systems on Asterisk-18 until I clear up the issues I find.

 

[wardmundy]

@kenn10: Tested with Skyetel trunk and Asterisk 18 dropped the connection about 10 seconds after remote hangup.

 

[kenn10]

@kenn10: Tested with Skyetel trunk and Asterisk 18 dropped the connection about 10 seconds after remote hangup.

Yeah but if you hang up the extension called before the call drops does it ring back the extension?

 

[wardmundy]

Well, I've tried 3 times to replicate the hangup delay and now all the hangups are instantaneous at least with Skyetel. Will try VoIP.ms next.

 

[wardmundy]

Instantaneous disconnects with VoIP.ms.

 

[kenn10]

Skyetel works ok but still slow for Skyetel to BulkVS to disconnect. My DIDs are with BulkVS for incoming so the slow teardown is an issue. I think it is Asterisk related, maybe some changes needed in PJSIP settings. I'm researching. The system I'm testing is duplicate (except for trunk registrations) to my CentOS 7, Asterisk 17 system. The original system doesn't have this issue so it seems to point to Asterisk 18 or something in PJSIP.

 

[kenn10]

I'm seeing slightly different screens on a pjsip extension > advanced tab. The two FreePBX versions are identical but on Asterisk-18, "Send Connected Line" is omitted. Still checking other things within FreePBX.

 

[Halea]

Is BulkVS' recent call visualization / call ladders tool of any help to figure out why there is a delay?

 

[kenn10]

Is BulkVS' recent call visualization / call ladders tool of any help to figure out why there is a delay?

I haven't gotten that far yet. I'm concentrating on the Asterisk side since the same trunk from BulkVS on my Centos Asterisk 17 system does not have the issue.

 

[tbrummell]

I'm on Debian 10.7, Asterisk 18.1.1, VoipMS PJSip TLS trunk, PJSip Mitel 6867 phone. Incoming call via trunk, straight to extension as destination, caller disconnects, line is immediately disconnected.
Same results with extension calling outbound to destination, destination answers, talks, and hangs up.
All seems well for me in this scenario.

You're probably going to need a SIP trace, but my guess is your phone/solution isn't responding to the BYE that the provider sends, either at the PBX level, or the phone level (most likely the phone is my guess).

 

[kenn10]

Oddly enough, the test system is working this morning. The connection is dropping immediately upon remote disconnect. No changes to anything since yesterday but today its OK. I pointed my DID's from Anveo Direct Vitelity to this system and they did not have the issue. I'm guessing there may have been some weird issue related to he BulkVS trunk. I will continue to monitor.

I did use a sip trace yesterday and the handshake between systems was delayed from the Bulkvs end upon far-end disconnect. Not so today.

 

[smccloud]

Will the OSS endpoint manager work in this release?

 

[kenn10]

Apparently not. See this thread: https://www.voip-info.org/forum/threads/asternic-cdr-reports-module-unsigned.24825/#post-153591

 

[smccloud]

Just finished up the install, cannot access it over the network at all. I did add-ip to add the /24 for the LAN subnet as well.

 

[Eliad]

Just finished up the install, cannot access it over the network at all. I did add-ip to add the /24 for the LAN subnet as well.

Where is this install, local or the cloud? Did you run incrediblepbx script through the SSH or through the console?

 

[smccloud]

Where is this install, local or the cloud? Did you run incrediblepbx script through the SSH or through the console?

Local, through the console.

 

[smccloud]

After re-doing the install over SSH the web interface is working. What is the best way to migrate from Incredible PBX 2020 to Incredible PBX 2021?