How to troubleshoot Fax Calls
(New page to troubleshoot Fax) |
m (Added link to TBreport) |
||
| Line 19: | Line 19: | ||
== <br> Capture Application logs == | == <br> Capture Application logs == | ||
This is used to see if any errors or special cases found in the application logs. | This is used to see if any errors or special cases found in the application logs. | ||
| − | With version 2.9 or later, see [[ | + | With version 2.9 or later, see [[TBReport|Capture a TBReport log]]<br> |
With version 2.8 and below: [[How_to_troubleshoot_call_routing#Using_the_application_log_files|Application Log Files]]<br> | With version 2.8 and below: [[How_to_troubleshoot_call_routing#Using_the_application_log_files|Application Log Files]]<br> | ||
Latest revision as of 16:51, 5 August 2016
To troubleshoot Fax calls, these are the recommended steps:
- Capture Call Trace
- Capture recording (wav file)
- Capture SIP/RTP traffic
- Capture TBReport
Contents |
Call Trace
Call Trace was created to trace the callflow from any incoming call through the Tmedia system. It allows to see the incoming call, outgoing calls, TDM channel, SIP SDP and more. This can be accessed from the Web Portal. You can create a filter to see call information. See Using Unique call trace.
Capture Recording
This process records the media data in a wav file that can be listened to or replayed as a T.30 Fax stream. See Target Recording
Capture SIP/RTP traffic
This is used to capture the T.38 or passthrough traffic. See VoIP Capture
Capture Application logs
This is used to see if any errors or special cases found in the application logs.
With version 2.9 or later, see Capture a TBReport log
With version 2.8 and below: Application Log Files
