Difference between revisions of "I have a problem with Asterisk"
From Kolmisoft Wiki
Jump to navigationJump to search
| (6 intermediate revisions by 4 users not shown) | |||
| Line 17: | Line 17: | ||
* [[Asterisk is slow]] | * [[Asterisk is slow]] | ||
* [[How to change User-Agent sent by MOR]] | * [[How to change User-Agent sent by MOR]] | ||
* [[I see lot of unknown peers]] | |||
* [[Maximum loadavg limit exceeded]] | |||
* [[Privilege escalation protection disabled]] | |||
* [[bad magic number for object. Object is likely destroyed.]] | |||
* [[calls do not work after glibc update]] | |||
* [[MOR does not send Contact header]] | |||
* [[FRACK!, Failed assertion bad magic number]] | |||
Latest revision as of 09:59, 31 January 2023
What problem do you have?
- libh323_linux_x86_64_r.so.1.18.0: cannot open shared object file
- I see "no samples for gxxx" warning messages on Asterisk CLI
- Two SIP listening ports for single Asterisk
- Two SIP listening IPs for single Asterisk
- Asterisk modules are not loading
- WARNING res_config_mysql.c: MySQL RealTime: Failed to query database. Check debug for more info
- Manager 'mor' logged off from 127.0.0.1
- Install Dahdi
- Using MOR with VoIP gateway
- Too many open files
- No application 'MYSQL' for extension
- How to change 'MOR Softswitch in SIP packets'
- How to change Qualify packets frequency
- Asterisk eats all CPU
- Asterisk is slow
- How to change User-Agent sent by MOR
- I see lot of unknown peers
- Maximum loadavg limit exceeded
- Privilege escalation protection disabled
- bad magic number for object. Object is likely destroyed.
- calls do not work after glibc update
- MOR does not send Contact header
- FRACK!, Failed assertion bad magic number
