Basic Troubleshooting

Article sections

    Basic Troubleshooting

    The essentials

    If you’ve encountered a problem it is essential to determine three things:

    • What happened?
    • What did you expect to happen?
    • How to re-produce what happened?

    Without there is little to troubleshoot. Then, in addition to your answers to the previous questions, the following steps are most helpful in debugging:

    1. Is just one phone involved? (do other phones work correctly?)
    2. Is it a problem you’re experiencing on just one pbx or more?
    3. Have you verified that your internet connection and all your netwerk devices are working correctly? (this includes firewall settings, looking for NAT issues, broken switch ports, cables, connectors, DSL modem, ISP outages, etc.)

    Voice quality problems like one-way audio or dropping audio can be traced to client-side LAN issues pretty much every time. Make sure you have disabled SIP ALG in your router/firewall. Most SIP helper functions in those devices are poorly implemented and cause issues. Also the pbx does not need them, so it’s better to disable SIP ALG, ICE, Stun in your devices.

    Gathering more details

    You can do the following to gather more information:

    1. log on as an admin user through ssh to your pbx (check your pbx firewall if you cannot connect)
    2. then log on to the pbx console and enter command aox_console you will then get the “CLI>” prompt
    3. run core set verbose 7 to see more debug info (to copy this info into an email to share with second line support staff if needed)
    4. if SIP debug is needed to see what the pbx and endpoints are communicating run pjsip set logger on (optional)
    5. make a call (or connect your own phone)
    6. turn off debug using core set verbose 0 and/or pjsip set logger off so you don’t cause unneccessary load on the pbx. DO NOT FORGET THIS!
    7. check the debug to find out what is happening
    8. check status/log viewer in the web interface for log details
    9. re-check whether or not the settings used in phones, PBX and SIP trunk provider are correct

    If the cause is still unclear try to re-produce the problem to be certain it is either local or not. For example connect your own phone to the pbx. Or ask the customer to change the phone with an other one.

    • Connect remote (hardware or software) phone to the PBX and try to replicate the issue
    • Verify the status of the phones and/or SIP trunk
    • Check the online Axeos knowledgebase

    Support cases

    If you need assistance please remember that the more complete your support case is the faster your supplier will be able to help you resolve the issue.
    When raising a support case with your supplier provide them the following information:

    • Describe:
      • What happened
      • What you expected to happen
      • How to re-produce what happened (the exact steps how to)
    • Provide all the troubleshooting information you have collected during all the above steps
    • PBX IP address and/or URL
    • PBX software version
    • Attach any logs and/or debugging data you’ve produced
    • Note the the last time it worked OK
    • Have you changed anything since the last time it worked OK? (if so, what?)

     

    Did this article answer your question?