Asterisk log files

General Help
1

Hi, we seem to be getting loads of warning notices in the debug log and not sure what they really mean or whether we need to correct them. We are using piaf 1.3 FreePBX 2.5.1.2 and using the Custom Contexts module for routing specific extensions via specific voip accounts.

Things seem to be working OK but feel a little concerned in case there’s something lurking to break things later on.

Any advice on these greatly welcomed. I can post the full log if required.

Here are some of the warning notices:

(Mar 26 18:49:25] WARNING[23974] rtp.c: Unable to set TOS to 184
[Mar 26 18:49:50] WARNING[23986] res_musiconhold.c: Cannot open dir /dev/null or dir does not exist
[Mar 26 18:49:50] NOTICE[23986] cdr.c: CDR simple logging enabled.
[Mar 26 18:49:50] WARNING[23986] res_musiconhold.c: Cannot open dir /dev/null or dir does not exist
[Mar 26 18:49:50] NOTICE[23986] indications.c: Removed default indication country ‘es’
[Mar 26 18:49:50] WARNING[23986] pbx_config.c: The use of ‘_.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 1917
[Mar 26 18:49:50] WARNING[23986] pbx_config.c: The use of '.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 1918
[Mar 26 18:49:50] WARNING[23986] pbx_config.c: The use of '.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 1919
[Mar 26 18:49:50] WARNING[23986] pbx_config.c: The use of '.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘X.’ instead at line 1920
[Mar 26 18:49:50] WARNING[23986] pbx_config.c: The use of '.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘_X.’ instead at line 2128
[Mar 26 18:49:50] WARNING[23986] pbx.c: Context ‘from-pstn’ tries to include nonexistent context ‘from-pstn-custom’
[Mar 26 18:49:50] WARNING[23986] pbx.c: Context ‘from-internal-additional’ tries to include nonexistent context ‘from-internal-additional-custom’
[Mar 26 18:49:50] WARNING[23986] pbx.c: Context ‘macro-vm’ tries to include nonexistent context ‘macro-vm-custom’
[Mar 26 18:49:50] WARNING[23986] pbx.c: Context ‘vm-callme’ tries to include nonexistent context ‘vm-callme-custom’
[Mar 26 18:49:50] WARNING[23986] pbx.c: Context ‘from-zaptel’ tries to include nonexistent context ‘from-zaptel-custom’
[Mar 26 18:49:50] WARNING[23986] pbx.c: Context ‘macro-systemrecording’ tries to include nonexistent context ‘macro-systemrecording-custom’
[Mar 26 18:49:50] WARNING[23986] pbx.c: Context ‘macro-agent-del’ tries to include nonexistent context ‘macro-agent-del-custom’

2

This is a case of too much information… as long as things are working there is nothing here you really need to worry about. Asterisk is like an old person that tends to complain about everything, to the point of being a pain in the butt sometimes. For example, the multiple warnings about “The use of ‘_.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘_X.’” is really saying, “We think you’re an idiot that doesn’t know what you’re doing” - except that there are cases where nothing other than _. will yield the desired result (if you wonder why, keep in mind that X only represents the numbers 0-9 - but phones can also dial strings with * and/or # in them, and if you are using certain types of endpoints you can even send other characters. So no, Mr. Asterisk, ‘X.’ is NOT the same as '.’, so would you kindly STFU about it… but it complains each and every time it encounters a line like that). And a file or directory may not exist because it’s simply not needed, yet Asterisk complains about it.

I will just mention that if for some reason you have set the debug level to something higher than normal, Asterisk will complain even more than usual, so don’t do that unless you’re specifically trying to track down a problem. But in any case, as long as things are working as you expect, there’s nothing I see there that would cause me any concern whatsoever.

3

Many thanks for your comments wiseoldowl. Being new to voip and FreePBX I thought it better to seek an opinion and be corrected rather than let it run it’s course and break later.