- Quick Start
- Server Setup
- User Management
- Telephone Book
- Team Management
- pascom Clients
- Trunk Templates
- Automatic Call Distribution
- Data protection and IT operations in the pascom cloud
- Monitoring via Nagios or Icinga
- Setup Mobile Access via the Internet
- Using a Lancom as a Router
- Subscription Downgrades
- Setup Extensions
- Remove Dialplan Loops
- Function / Service Codes
- Change SIP Header
- Mobile App Energy Optimisation Settings
- Telephone Provisioning via DHCP
- Support & Release Notes
- Developer APIs
Remove Dialplan Loops+ Cloud and Self Hosted
How to identify, avoid and fix Dialplan Loops
A dialplan loop exits when during a call, an extension is traversed 30 times.
In the job box, a warning notification will appear as below:
CRITICAL: A dialplan loop was detected, see /tmp/.dialplan-loop-detected
Under /tmp/.dialplan-loop-detected a file will have been written that contains details on which extension the Dialplan Loop was caused.
In order to avoid Dialplan loops occuring more often, you will find further information in the file regarding the affected extensions and you can then edit your call flow accordingly.
The notification will only disappear once the file .dialplan-loop-detected has been removed (either deleted or moved). To do this log into the pascom phone system via SSH.