• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

Incoming calls fail, System stops resonding to registration requests

Status
Not open for further replies.

honcoop

Customer
Basic Certified
Joined
Mar 25, 2016
Messages
5
Reaction score
0
Hello,
I have a Debian ISO installed on Intel NUC, with 3CX version 15.5.12227.5.

The main system ran as expected for about 5 weeks and then the customer started complaining about inbound calls not ringing in. There are 4 lines connected to a Patton FXO gateway.

Using packet traces, we found that the NUC is not seeing the calls offered, but we do see the gateway sending the calls. We found that the NUC just stops responding to incoming SIP messages. The system isn't locked up because I'm still able to manage the device, and run packet captures on the appliance.

My suspicion is that this started after an automatic firmware update, but I don't know how to revert back to an older version to confirm that.

We have replaced, the NUC, the gateway, the network switches, and we have also programmed a new system from scratch rather than restoring from backup.

Any advice would be appreciated.

Thanks,
Brian
 
Hello @honcoop

Are the calls reaching the NIC of the NUC after being sent by the Patton? If not then is there anything between the Patton that could be causing the issue? Is the Invite generated by the Patton sent to the correct IP? Did the local IP of the PBX change when the issue started?
Is the patton configured with the 3CX configuration file?
 
Thanks for the reply.
The Patton is using the generated profile. There is nothing between the NUC and the gateway except a layer 2 switch, which was swapped out to test.

We used the trace tool on the 3CX appliance and it did not see the packets but that could still be an appliance issue. We do see the packets leave the gateway device.

No IP address change and the packets leaving the Patton are destined for the right IP.

My plan this morning is to switch to a Windows installation on a different platform.

Thanks,
Brian
 
The PBX captures packets on the NIC level of the appliance so if the packets were reaching the appliance the chances are that you would be able to see them.
My plan this morning is to switch to a Windows installation on a different platform.
Let us know of the results
 
What I'm seeing is that the Patton is happily registering to the 3CX server, but then when a call comes in, it doesn't offer the call to it at all.
upload_2018-7-17_9-4-1.png
 
On the Patton, I see the call come in:

Code:
192.168.150.250>enable
192.168.150.250#debug ccfxo
192.168.150.250#debug fxo
192.168.150.250#debug call-router
192.168.150.250#debug call-control
192.168.150.250#debug media-gateway all
192.168.150.250#term monitor
%                ^ Keyword mismatch
192.168.150.250#
192.168.150.250#
192.168.150.250#
192.168.150.250#15:49:31  FXO   > [0 1] Driver: Line reversal
15:49:31  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:31  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:31  DP    > FXO-00/01: event(FXO/line reversal)
15:49:31  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:31  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:49:32  FXO   > [0 1] Driver: Line reversal
15:49:32  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:32  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:32  DP    > FXO-00/01: event(FXO/line reversal)
15:49:32  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:32  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:49:32  FXO   > [0 1] Driver: Line reversal
15:49:32  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:32  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:32  DP    > FXO-00/01: event(FXO/line reversal)
15:49:32  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:32  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:49:33  FXO   > [0 1] Driver: Line reversal
15:49:33  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:33  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:33  DP    > FXO-00/01: event(FXO/line reversal)
15:49:33  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:33  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:49:37  FXO   > [0 1] Driver: Line reversal
15:49:37  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:37  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:37  DP    > FXO-00/01: event(FXO/line reversal)
15:49:37  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:37  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:49:37  FXO   > [0 1] Driver: Line reversal
15:49:37  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:37  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:37  DP    > FXO-00/01: event(FXO/line reversal)
15:49:37  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:37  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:49:38  FXO   > [0 1] Driver: Line reversal
15:49:38  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:38  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:38  DP    > FXO-00/01: event(FXO/line reversal)
15:49:38  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:38  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:49:38  FXO   > [0 1] Driver: Line reversal
15:49:38  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:38  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:38  DP    > FXO-00/01: event(FXO/line reversal)
15:49:38  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:38  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:49:43  FXO   > [0 1] Driver: Line reversal
15:49:43  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:43  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:43  DP    > FXO-00/01: event(FXO/line reversal)
15:49:43  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:43  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:49:43  FXO   > [0 1] Driver: Line reversal
15:49:43  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:43  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:43  DP    > FXO-00/01: event(FXO/line reversal)
15:49:43  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:43  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:49:44  FXO   > [0 1] Driver: Line reversal
15:49:44  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:44  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:44  DP    > FXO-00/01: event(FXO/line reversal)
15:49:44  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:44  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:49:44  FXO   > [0 1] Driver: Line reversal
15:49:44  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:44  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:44  DP    > FXO-00/01: event(FXO/line reversal)
15:49:44  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:44  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:49:49  FXO   > [0 1] Driver: Line reversal
15:49:49  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:49  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:49  DP    > FXO-00/01: event(FXO/line reversal)
15:49:49  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:49  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:49:49  FXO   > [0 1] Driver: Line reversal
15:49:49  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:49  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:49  DP    > FXO-00/01: event(FXO/line reversal)
15:49:49  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:49  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:49:50  FXO   > [0 1] Driver: Line reversal
15:49:50  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:50  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:50  DP    > FXO-00/01: event(FXO/line reversal)
15:49:50  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:50  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:49:50  FXO   > [0 1] Driver: Line reversal
15:49:50  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:50  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:50  DP    > FXO-00/01: event(FXO/line reversal)
15:49:50  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:50  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:49:55  FXO   > [0 1] Driver: Line reversal
15:49:55  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:55  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:55  DP    > FXO-00/01: event(FXO/line reversal)
15:49:55  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:55  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:49:55  FXO   > [0 1] Driver: Line reversal
15:49:55  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:55  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:55  DP    > FXO-00/01: event(FXO/line reversal)
15:49:55  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:55  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:49:56  FXO   > [0 1] Driver: Line reversal
15:49:56  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:56  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:56  DP    > FXO-00/01: event(FXO/line reversal)
15:49:56  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:56  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:49:56  FXO   > [0 1] Driver: Line reversal
15:49:56  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:49:56  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:49:56  DP    > FXO-00/01: event(FXO/line reversal)
15:49:56  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:49:56  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:50:01  FXO   > [0 1] Driver: Line reversal
15:50:01  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:50:01  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:50:01  DP    > FXO-00/01: event(FXO/line reversal)
15:50:01  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:50:01  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
15:50:01  FXO   > [0 1] Driver: Line reversal
15:50:01  FXO   > [fxo 0 0 1/fxo 0] Dispatching event 'PortLineReversal' in state 'OnHook'
15:50:01  FXO   > [fxo 0 0 1/fxo 0] Action 'Line-Reversal'
15:50:01  DP    > FXO-00/01: event(FXO/line reversal)
15:50:01  FXO   > [fxo 0 0 1/fxo 0] Event 'PortLineReversal' handled in state 'OnHook'
15:50:01  CFXO  > [EP IF_FXO_1] State IDLE, event BATTERY REVERSAL
 
Update - The calls are now ringing in as expected on the Windows install. The issue today was that the Windows firewall turned back on and blocked those calls. SIP registrations were still working though and that had me believing there was no firewall issue. It appears at this point, that running the Debian load on the Intel NUC may be a problem.
 
Thank you for the update and glad to see that you got things working. Keep an eye on the issue and report back if you face any more issues.
 
Just one additional thing to check since you are getting some strange behavior here.

Ensure that your analogue lines are definitely not running any additional PBX like services such as feature-line or redcare. This is commonly missed and causes issues onsite if you are using a PBX systems yourself.
 
Status
Not open for further replies.

Getting Started - Admin

Latest Posts

Forum statistics

Threads
141,625
Messages
748,873
Members
144,738
Latest member
MattS
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.