IPerVoice call module not upgrading

Use this article to help you overcome the issue of an IPerVoice module not upgrading.

 

If there is an issue with an IPerVoice Call Module not upgrading or appearing in New Devices when connected to the IPerVoice system, this may be because of one of the following two reasons:

  1. Firstly if the DHCP is Blocked on the server configuration this will not allow the Call Module to obtain an IP address however you can add the Call Module manually.
  2. Secondly, there may be an issue with the network configuration. This will relate to the Spanning Tree Protocol (STP) and the BootP Protocols. Without BootP the Call Module will not receive the correct files to start the upgrade process.

 

How to fix these issues:

Please check Spanning Tree is Off and BootP is On.

Please ensure the following ports are open:

  • IGMPv2 or IGMPv3 Multicast Service must be enabled.

The following ports must be open and not restricted:

  • TCP ports 2049, 51234, 5060, 50118, 3306, 13451 to 3460, 111, 80, 433, 41365, 22, 918 & 40279.
  • UDP ports 32768, 2049, 514, 32771, 34956, 917, 34839, 67, 5060, 69, 975, 111, 123.

Additional Requirements:

  • Multicast must be enabled on 238.0.0.200:55000 and on 239.255.0.200 (all ports).
  • TCP/UDP ports used for Internet access (if any) TCP:5060,6060 UDP:5060,6060.
  • Bandwidth per end point (Kbps) 2500 for upload and 10000 for download

A simple test is to connect the Server directly to unmanaged POE switch and connect the Call Module to a POE Port and check the upgrade operation. The Call Module can take upto 15 Minutes to Upgrade and then appear in New Devices.