Hello all,
We manage multiple 3CX instances in our datacenter for multiple customers.
We encountered a peculiar problem on two of those instances for two separate customers.
Problem is this: extensions on snom D785 phones are unregistered in their respective 3CX pbx after a call ends. This happens randomly when caller or callee ends the call.
The Snom phones are configured with the default template in 3CX, re-register timer in the phones is default set to 30 seconds, so after 30 seconds the extension does register again with the pbx and calls arrive and can be made again as expected.
I also noticed this behavior when a call arrives on a call queue with 2 extensions: the 2 phones (each with one extension) ring, one takes the call, ends the call, then both extensions are unregistered for 30 seconds.
Extract from the D785 log:
Aug 7 07:53:29.571 [WARN ] SIP: transaction_timeout udp: 1006623 (32000ms)->Udp:pbxinternalIP:5060
Aug 7 07:53:29.571 [ERROR ] SIP: transport error: 1006623 -> Udp:pbxinternalIP:5060
Aug 7 07:53:29.571 [NOTICE] SIP: Add dirty host: Udp:pbxinternalIP:5060 (0 sec)
Aug 7 07:53:29.571 [NOTICE] SIP: Registration 0 0 set to unregistered due to transport error
This problem started to occur after the new templates for Snom were published in one of the last V18 updates, I believe it was V18.0.9.
Meanwhile both 3CX instances of the customers have been migrated to V20 on Debian as per the manual, but unfortunately the problem persists.
Snom phones are connnected with the 3CX instances through IPSEC tunnels. We use pfSense firewalls, one customer also uses pfSense for the IPSEC, the other customer uses AXSGuard for the IPSEC.
Snom phones are on the latest 3CX compatible firmware version 10.1.175.0.
Anyone has an idea what is going on?
We manage multiple 3CX instances in our datacenter for multiple customers.
We encountered a peculiar problem on two of those instances for two separate customers.
Problem is this: extensions on snom D785 phones are unregistered in their respective 3CX pbx after a call ends. This happens randomly when caller or callee ends the call.
The Snom phones are configured with the default template in 3CX, re-register timer in the phones is default set to 30 seconds, so after 30 seconds the extension does register again with the pbx and calls arrive and can be made again as expected.
I also noticed this behavior when a call arrives on a call queue with 2 extensions: the 2 phones (each with one extension) ring, one takes the call, ends the call, then both extensions are unregistered for 30 seconds.
Extract from the D785 log:
Aug 7 07:53:29.571 [WARN ] SIP: transaction_timeout udp: 1006623 (32000ms)->Udp:pbxinternalIP:5060
Aug 7 07:53:29.571 [ERROR ] SIP: transport error: 1006623 -> Udp:pbxinternalIP:5060
Aug 7 07:53:29.571 [NOTICE] SIP: Add dirty host: Udp:pbxinternalIP:5060 (0 sec)
Aug 7 07:53:29.571 [NOTICE] SIP: Registration 0 0 set to unregistered due to transport error
This problem started to occur after the new templates for Snom were published in one of the last V18 updates, I believe it was V18.0.9.
Meanwhile both 3CX instances of the customers have been migrated to V20 on Debian as per the manual, but unfortunately the problem persists.
Snom phones are connnected with the 3CX instances through IPSEC tunnels. We use pfSense firewalls, one customer also uses pfSense for the IPSEC, the other customer uses AXSGuard for the IPSEC.
Snom phones are on the latest 3CX compatible firmware version 10.1.175.0.
Anyone has an idea what is going on?
