|
|
|
|
Joined: Aug 2006
Posts: 26
Member
|
OP
Member
Joined: Aug 2006
Posts: 26 |
Inter Tel Axxess v9.115
Recently installed IPRC with 4 ip phones. They have been working fine(1 month)until this week when I started getting the SYS ALARM #32 INSUF BAND errors for the two phones that are in use. One phone is in California the other central Pennsylvania and both show that error. These phones are in home offices and one uses Verizon FIOS.Connection for IPRC card is routed through firewall with all appropriate ports opened and Public ip is NAT'd to the private ip of the card. What are some tests I could run to narrow down the cause.
Thanks
|
|
|
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: Jun 2010
Posts: 797
Moderator-Inter-Tel
|
|
Moderator-Inter-Tel
Joined: Jun 2010
Posts: 797 |
|
|
|
|
|
Joined: Aug 2006
Posts: 26
Member
|
|
OP
Member
Joined: Aug 2006
Posts: 26 |
Thanks Stix, I'll look through the threads.
|
|
|
|
|
Joined: Aug 2005
Posts: 908
Member
|
|
Member
Joined: Aug 2005
Posts: 908 |
This error means some packets took longer to arrive than the phone system feels it should. It's basically meaningless. They happen quite regularly with users on DSL. I ignore these errors unless they denote an entire node instead of a phone.
I may pop up and tell our network guy that I've received the error. At which point we do our best Chicken Little impersonation and then go on with our day.
|
|
|
|
Forums84
Topics94,284
Posts638,771
Members49,765
| |
Most Online5,661
May 23rd, 2018
|
|
|
2 members (dexman, Keyset6),
128
guests, and
354
robots. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|
|
