Main Directory
Spaces
Apps
Templates
Create
Support
All content
Blogs
Space settings
Content
Audian Phone Articles
•
Audian Booklet
Audian Portal
Fax Articles
Features & Services
Hardware
•
SMS Registration
Tools & Downloads
Troubleshooting
•
How To - Stopping your numbers from being marked as Spam
•
How To - Change Transport Options (TCP, UDP, NAPTR Settings)
•
How To - Find MAC or IP Address on Phones
How To - Optimize Networks for VoIP
•
How To - Report Service Interruption
•
How To - Resolve Missing Voicemail Emails - Outlook
•
How To - Statically Assign NTP Server (Portal)
•
How To - Troubleshoot Voicemail Light Indicator
•
How To - Verify If The Audian Portal Is Down
•
How To - Verify Phone Registration
How To - View Call Logs
•
How To - Verify Call Example "Recovery_on_timer" Error
•
How To - Export and Filter Raw Call Logs
•
How To - View Config Files
•
Internet Connection Sharing
Phone Troubleshooting
•
Stop call volume from auto lowering
•
What Is - Double NAT
Audian SMS Articles
CRM Integration
•
New Feature Release Log
Audian Onboarding App
Support
/
/
How To - View Call Logs
/
How To - Verify Call Example "Recovery_on_timer" Error
Summarize
How To - Verify Call Example "Recovery_on_timer" Error
David Klein
Eric Ronhovde
Owned by
David Klein
Last updated:
Aug 22, 2019
by
Eric Ronhovde
1 min read
Loading data...
Description:
This article will show you how to do the following.
Check call logs for Recovery_on_timer errors
Methods:
Reboot the phone by
un
plugging the phones power
and plugging it back in.
Place a test call
after the phone is finished rebooting.
Login to the Audian Portal
Click the
9 square button
at the top right of the screen.
Click on the
Smart PBX
app.
Click
Call Logs
Click the
Custom
filter option at the top.
Select the
date range
of the calls, and then click
Filter
.
When downloading the call log it include all calls within the time range.
Click on the desired
call
to expand the records.
Verify if the Hangup Cause shows as
Recovery_on_timer
.
If calls are getting a
Recovery_on_timer
it may be an issue with the firewall or ALG.
{"serverDuration": 27, "requestCorrelationId": "66ffb4c09d85424ab0f21cd5fc94d808"}