Patton gateway options for allowing outbound/inbound call come undone

[woo60420]

3cx version 15.5.15502.6 runs on server 2008 r2 standard. We use 2 patton gateways model SN4960 for incoming/outgoing calls type T1. Suddenly today in the 3cx console under the gateway options the Call options Allow inbound and allow outbound become unchecked without anyone changing anything? The trunks stay online with 3cx. It's happening to both gateways at the same time. I've pretty confused even where to look as to why this would be happening. Any help appreciated. Thanks

 

[AWS2P]

I think you probably never know as there's no logging to follow settings changes on pbx, this feature is asked for a while.
Are you alone with admin access ?

 

[eddv123]

I have never known this to be the case and have used Pattons for around 12 years with 3CX. I would as a precaution check the firmwares the pattons are running and the templates. https://www.patton.com/support/upgrades/

2008 has run out of support for 3CX v16: https://www.3cx.com/docs/manual/ which I guess might explain why you are not upgrading yet.

 

[3C Technology]

I have had the same thing happen with a Beronet gateway at one customer and a SIP trunk on another system.Both on V15.5 SP6 have not seen it on V16 so far.

Kept getting an error that there were no available outgoing lines and inbound would be a busy signal for caller.

 

[YiannisH_3CX]

Hello @woo60420

Have never seen this happen without someone changing these settings manually. Make sure that no one is pressing the "Disable All" button as it will cause the behaviour you are describing.

 

[3C Technology]

Hi @YiannisH_3CX i have just been doing some maintenance on a customers 3cx server they had 2 SIP providers setup 1 and 2. Sip provider 1 is the default provider and 2 was an unused test account. I deleted SIP provider 2 that was no longer in use. A little while later i noticed calls were not connecting on SIP provider 1. When checking the allow outbound and inbound call check boxes were now unchecked on provider 1.

When i think back to my prior experiences it was also when deleting unused trunks/providers. Perhaps you can ask support to see if they can reproduce the error in the lab ?

Cheers

EDIT Ok so after rereading your post i may have been inadvertently been pressing the disable all thinking it will only deregister the provider, not change the settings mentioned above.