Switchvox - What do I do if my Switchboard is not loading?

Switchvox - What do I do if my Switchboard is not loading?

Answer the following questions:

  1. Have we made any recent network changes to the PBX or the subnet my PC having the issue resides on?

  2. Have we tried and replicated the issue in multiple browsers?

  3. Are our browsers up to date?

  4. Is everyone on the network effected?  If not, take note on who is effected.

  5. When did the issue start occuring?

Basic Troubleshooting Steps:

  1. Clear your browsers cache

  2. If the PBX is accessible externally attempt to connect from another network or hotspot to access the Switchboard.  This will help rule out any internal network failures.

  3. If the system is in production with active calls go to Server > System Reload and choose the blue button Software Reload.  Note: This does not terminate any calls.

  4. If the system is not in production go to Server > IP Configuration and save the page.  This will rewrite your hosts file and ensure your jabber host is properly populated.

  5. Ensure there are absolutely no restrictions on your network for the following ports:

    • 443 TCP/UDP

    • 80 TCP/UDP

    • 5222 TCP

    • 843 TCP

    • 5269 TCP

If this does not resolve the issue we will need a sample of the failed connection.

Obtaining a sample:

We will use a packet capture to record your work station attempting to load the Switchboard.

Packet Capture:

  1. Navigate to Server>Diagnostics>Advanced Debugging

  2. Select Start Debugging Session

  3. Select Packet Capture

  4. Set the Duration for any time up to one hour

  5. For most Packet captures Capture Only SIP Packets should be set to No

  6. Select Begin Debugging Session

Note: The largest packet capture Support can generally use is one hour, but the smaller the packet capture is the easier it will be to diagnose. The recommended length is usually 10 minutes.

Once the capture is running attempt to access or reload any current Switchboard connections to ensure a request is sent during the time the capture is running.

With this information call support for further troubleshooting.