Difference between revisions of "Asterisk modules are not loading"
From Kolmisoft Wiki
Jump to navigationJump to search
(→Reason) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 30: | Line 30: | ||
Try to use ping command to detect network packets losses. <br> | Try to use ping command to detect network packets losses. <br> | ||
Exapmle: | Exapmle: | ||
ping 22.19.13.71 <br> | ping 22.19.13.71 <br> | ||
| Line 37: | Line 38: | ||
86 packets transmitted, 0 received, '''100% packet loss''', time 85003ms''' | 86 packets transmitted, 0 received, '''100% packet loss''', time 85003ms''' | ||
<br><br> | <br><br> | ||
=How to solve= | =How to solve= | ||
If you see packet loss please contact your Datacenter or Internet Provider. <br> | If you see packet loss please contact your Datacenter or Internet Provider. <br> | ||
Fix the internet connection and system should work fine.<br> | Fix the internet connection and system should work fine.<br> | ||
Latest revision as of 09:57, 4 March 2012
About
If Asterisk server are failing with various hang up causes server or is giving these responses:
Asterisk CLI output
-- Executing [88518888@mor:4] Set("Zap/29-1", "TIMEOUT(response)=20") in new stack
[2011-12-25 17:13:27] ERROR[7591]: pbx.c:1584 ast_func_write: Function TIMEOUT not registered
-- Executing [88518888@mor:5] Set("Zap/29-1", "TIMEOUT(digit)=10") in new stack
[2011-12-25 17:13:27] ERROR[7591]: pbx.c:1584 ast_func_write: Function TIMEOUT not registered
Either:
[2011-12-25 17:19:14] WARNING[9047]: config.c:1335 find_engine: Realtime mapping for 'realtime_ext' found to engine 'mysql', but the engine is not available
[2011-12-25 17:19:14] WARNING[9047]: config.c:1335 find_engine: Realtime mapping for 'realtime_ext' found to engine 'mysql', but the engine is not available
Reason
These errors happens because network is not working and Asterisk cannot start.
This mean that necessary functions are not loaded to Asterisk yet due to network lag.
Some modules need network connectivity in order to load properly.
Try to use ping command to detect network packets losses.
Exapmle:
ping 22.19.13.71
PING 22.19.13.71 (22.19.13.71) 56(84) bytes of data.
--- 22.19.13.71 ping statistics ---
86 packets transmitted, 0 received, 100% packet loss, time 85003ms
How to solve
If you see packet loss please contact your Datacenter or Internet Provider.
Fix the internet connection and system should work fine.
