|
|
Joined: Jun 2011
Posts: 29
Member
|
Member
Joined: Jun 2011
Posts: 29 |
I have a 12 node Samsung SPNET with 6 - 7100, 2 - 7030 and two 7200s (MCP) (Customer refuses to upgrade to cloud) Everything works fine till one of the nodes loses internet... then other systems start having issues calling the other nodes that ARE up... My theory is the NAT tables in the routers/firewalls are getting full from the repeated attempts at making intercom calls to other nodes. If that is the case... how can this be remedied? TCP or UDP timers in the firewall? If the timer is reduced, wouldn't it cause issues with calls when everything is fine?
Last edited by CyberLaw; 4 hours ago.
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Aug 2004
Posts: 1,760 Likes: 49
Admin
|
Admin
Joined: Aug 2004
Posts: 1,760 Likes: 49 |
I am not at all familiar with SPNET or how it communicates, but I can't see it causing an abundance of entries in a NAT table just because another extension/system is unreachable. To do so would mean the PBX send each individual request (for the same call) from different port numbers.
It's probably worth running Wireshark while the issue occurs to see if a smoking gun appears...
Doe the issues they experience have to do with degraded audio? Or do calls simply fail to complete (and if so what message do they see)?
![[Linked Image from web.atcomsystems.ca]](https://web.atcomsystems.ca/pic/atcom_logo_60px-high.png) Looking for a VoIP Phone Canada provider? Put Atcom's valuable VoIP expertise to work for your business today!
|
|
|
|
Joined: Jun 2011
Posts: 29
Member
|
Member
Joined: Jun 2011
Posts: 29 |
I believe it's a "No User Response" error from the pbx. Had to clear an issue this am on this specific customer. The one 7200 causing the issue was unreachable via the maintenance software (TCP 5090), but reachable via an IP set at my location. Rebooted the system via 811 and everything came back just fine. It's difficult to get Wireshark in place... I have to act quickly to reboot which ever pbx is causing the issue and get them back online.
|
|
|
Forums84
Topics94,559
Posts640,135
Members49,862
|
Most Online5,661 May 23rd, 2018
|
|
1 members (Toner),
35
guests, and
78
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|