Huge list of warnings in the "log files"

FreePBX
1

Hello everyone!
another day, another noob question!
Today i’m here to ask if someone is so kind to read my logfiles and tell me if i have to worry or not, because there is a HUGE list of warnings that i really cant figure out what they are referring to!

The whole systems seems to works totally fine, even if there are a lot of those errors/warnings

For the moment i will leave just some of the lines, and if someone wanna take a look at the full log i’ll post it ^^
.
.
.
.
.

first two type of warnings are like this:

[2018-12-10 09:39:23] WARNING[20483] pbx.c: Unable to register extension ‘_*72.’ priority 1 in ‘app-cf-on’, already in use

[2018-12-10 09:39:23] WARNING[20483] pbx_config.c: Unable to register extension at line 621 of /etc/asterisk/extensions_additional.conf

[2018-12-10 09:39:23] WARNING[20483] pbx_config.c: Unable to register extension at line 634 of /etc/asterisk/extensions_additional.conf

[2018-12-10 09:39:23] WARNING[20483] pbx.c: Unable to register extension ‘sstate’ priority 4 in ‘app-cf-on’, already in use

[2018-12-10 09:39:23] WARNING[20483] pbx_config.c: The use of ‘_.’ for an extension is strongly discouraged and can have unexpected behavior. Please use ‘_X.’ instead at line 965 of /etc/asterisk/extensions_additional.conf

Then there are those type of warnings:

[2018-12-10 09:39:23] WARNING[20483] pbx.c: Context ‘outrt-9’ tries to include nonexistent context ‘outrt-9-custom’
[2018-12-10 09:39:23] WARNING[20483] pbx.c: Context ‘outbound-allroutes’ tries to include nonexistent context ‘outbound-allroutes-custom’
[2018-12-10 09:39:23] WARNING[20483] pbx.c: Context ‘macro-prepend-cid’ tries to include nonexistent context ‘macro-prepend-cid-custom’
[2018-12-10 09:39:23] WARNING[20483] pbx.c: Context ‘ext-trunk’ tries to include nonexistent context ‘ext-trunk-custom’
[2018-12-10 09:39:23] WARNING[20483] pbx.c: Context ‘from-trunk-sip-90001’ tries to include nonexistent context ‘from-trunk-sip-90001-custom’
[2018-12-10 09:39:23] WARNING[20483] pbx.c: Context ‘from-did-direct-ivr’ tries to include nonexistent context ‘from-did-direct-ivr-custom’

then i get some errors:

[2018-12-10 09:39:23] ERROR[20483] res_sorcery_config.c: Unable to load config file ‘pjproject.conf’
[2018-12-10 09:39:23] VERBOSE[20483] loader.c: Reloading module ‘res_pjsip.so’ (Basic SIP resource)
[2018-12-10 09:39:23] ERROR[18242] res_pjsip_config_wizard.c: Unable to load config file ‘pjsip_wizard.conf’

2

These are all “IIRC” answers:

You have *72 defined twice in your configuration.

I don’t know what extension it’s complaining about, but you can look in the file on like 621 and see what the issue is. It’s probably a double definition of something; probably nothing.

Digium vs. Sangoma fight - stay out of this one.

All of the “-custom” contexts that don’t exist probably aren’t there and probably shouldn’t be. Seems to me there’s a way to turn that off in the Advanced Settings.

You don’t have a pjproject.conf file. This, along with the other pj-sip module errors tell me you don’t have PJ-SIP loaded.

In all, pretty typical.

1 Like
3

never touched anything about digium/sangoma, so i dont get why it even go with errors

founded and disabled, hope it wont make my system explode haha

pretty strange error since all my extensions are up, avaible and working fine!

cant figure out where is double defined since *72 is only in on of the call forwarding settings

from what i understand, nothing to worry about!

Well, first of all thanks for your time, i suppose there is no reason at all to scann the whole log file since the errors are very similar between them!
Overall, nothing i think i really have to care about, or i hope so!

Thanks again for your help,
Regards!

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.