Difference between revisions of "316 Freeswitch did not find termination point details"

From Kolmisoft Wiki
Jump to navigationJump to search
(Created page with 'Hangupcause Code - 316. Freeswitch did not find termination point details <br/><br/> This error happens when FreeSwitch is asked to dial specific termination point, but FreeSwitc…')
 
Line 8: Line 8:
* Check if /var/log/m2/m2_freeswitch_devices.log is updated when termination point is created or updated via GUI
* Check if /var/log/m2/m2_freeswitch_devices.log is updated when termination point is created or updated via GUI
* Check if /var/log/m2/m2_freeswitch_devices.log show any errors. If everything is OK, then log should end with "Job complete. TP: X, GW: Y configured.". If this line is not present, then something is wrong.
* Check if /var/log/m2/m2_freeswitch_devices.log show any errors. If everything is OK, then log should end with "Job complete. TP: X, GW: Y configured.". If this line is not present, then something is wrong.
* Manually execute /usr/local/m2/m2_freeswitch_devices and check if it crashes.
* Even if log does not show errors, manually execute /usr/local/m2/m2_freeswitch_devices and check if it crashes.


Report this issue to developers
Report this issue to developers

Revision as of 12:35, 6 October 2016

Hangupcause Code - 316. Freeswitch did not find termination point details

This error happens when FreeSwitch is asked to dial specific termination point, but FreeSwitch doesn't have any details about this termination point.

How to solve this problem:

  • Check if /tmp/m2 directory has 777 permisions
  • Check if /var/log/m2/m2_freeswitch_devices.log is updated when termination point is created or updated via GUI
  • Check if /var/log/m2/m2_freeswitch_devices.log show any errors. If everything is OK, then log should end with "Job complete. TP: X, GW: Y configured.". If this line is not present, then something is wrong.
  • Even if log does not show errors, manually execute /usr/local/m2/m2_freeswitch_devices and check if it crashes.

Report this issue to developers



See also