Solved Trunk options -> Transport Protocol gets reset

[ZorgNed - JDooge]

A while back we had a lot of troubles making calls longer than 15 minutes and some other issues.
This turned out to be an issue with our SonicWall firewall. A workaround that solved all issues instantly was to set the Transport Protocol setting under the Trunk options to TCP instead of Any.

For some reason the issues started today again. Obviously the first thing I checked was this option.. And it had reset to Any.
The only moment I can imagine this happening is during the auto-update from 16.0.3 to 16.0.4.

 

[cobaltit]

Probably which is why you shouldn't have auto-update on.

 

[ZorgNed - JDooge]

Probably which is why you shouldn't have auto-update on.

Is this common knowledge?
Auto-update is enabled by default (and it seems like a smart thing with security in mind).

Also with auto-update disabled I suppose I can't be expected to check each and every setting. Perhaps it even resets on system reboot.

 

[cobaltit]

Auto-Update is not enabled by default. And far as not doing auto-updates it's pretty common knowledge among anyone who uses any software as it's not 3CX specific. Windows Updates is a great example of the joys of auto-updating.

As far as security, unless a vendor specifically releases an update for security reasons there's usually no urgency. And when they do, typically they are specifically security patches and don't have other changes like features,etc that can cause unintended consequences.

In your specific case you are the only person reporting the issue, and there's no mention of whether it was a supported provider and the associated template or a generic template. The changelog lists some template changes which may be relevant.

The moral of the story is auto-update at your own risk. There's basically three groups of people:

• Those who auto-update and pray between 3CX and the alpha/beta testers your exact scenario/configuration has been tested and works.
• Those who don't auto-update and wait xx days/weeks/months to see what broke and then install.
• Those who run really tight ships and have a test environment where they fully vet all changes because stability is of utmost importance.

 

[ZorgNed - JDooge]

@cobaltit We're using the Debian release of 3CX and I'm pretty sure updates were enabled out of the box, but that is besides the point. There is no way for a small company to have a back-up 3CX installation and check each and every setting after evert update (there are tens of thousands?).
It seems odd to me that this is the advised way of using the product.

I do check the changelog when I see a scheduled update (and otherwise afterwards because I get a mail post-update). I will now also check this setting - but to me it seems like a small bug with relatively low impact. I'd rather have the system auto-update so that its kept current than having it fall into disrepair and be unsupported.

Anyway, I was hoping to report this as a bug somewhere.

 

[YiannisH_3CX]

Hi @ZorgNed - JDooge

Which provider are you using? Are you using a supported 3CX provider with the default template?
If so then we can check if the update caused this or not.

 

[ZorgNed - JDooge]

Hi @ZorgNed - JDooge

Which provider are you using? Are you using a supported 3CX provider with the default template?
If so then we can check if the update caused this or not.

Hi @YiannisH_3CX, we're using Signet with their default template, except that to cross our SonicWall firewall successfully we have to change the "Transport Protocol"-setting to TCP instead of the default "Any".

 

[YiannisH_3CX]

Since Signet supported both TCP and UPD the default setting is ANY and the update to SP4 did reset that to the default value. This is done because of the DNS changes and addition of the transport protocol settings in SP3 and we want to make sure that the template defaults to the correct setting. Since you need the setting to be TCP you can manually change it.
Thank you for reporting though, we will take it into account for the next update

 

[ZorgNed - JDooge]

@YiannisH_3CX Thanks a lot!

 

[YiannisH_3CX]

You are welcome