Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kamailio refuses custom global variable #1773

Closed
mckaygerhard opened this issue Dec 20, 2018 · 4 comments
Closed

kamailio refuses custom global variable #1773

mckaygerhard opened this issue Dec 20, 2018 · 4 comments

Comments

@mckaygerhard
Copy link

Description

triying to config kamailio using default config file with proper parameters, and also aparte few other in kamailio-local.cfg.. en that second file i put a variable (for global) as kamailioip=10.10.10.10 but refuses to reconoce it

Troubleshooting

kamailio seems does not reconoce it the global variable in kamailio-local.cfg file that are sourcered by the kamailio.cfg main file

Reproduction

download, configure and make build of kamailio
use the main config file
touch kamilio-local.cfg that will be sourcered by kamailio.cfg
in that file put only kamailioip=10.10.10.10
i tri also with "101.10.10.10" and same problem

Log Messages

 0(1542) DEBUG: <core> [core/modparam.c:83]: set_mod_param_regex(): 'debugger' matches module 'debugger'
 0(1542) DEBUG: <core> [core/sr_module.c:811]: find_param_export(): found <log_level_name> in module debugger [/usr/lib/x86_64-linux-gnu/kamailio/modules/debugger.so]
 0(1542) DEBUG: <core> [core/modparam.c:99]: set_mod_param_regex(): found <log_level_name> in module debugger [/usr/lib/x86_64-linux-gnu/kamailio/modules/debugger.so]
 0(1542) CRITICAL: <core> [core/cfg.y:3450]: yyerror_at(): parse error in config file kamailio-localmods.cfg, line 9, column 6: syntax error
 0(1542) CRITICAL: <core> [core/cfg.y:3450]: yyerror_at(): parse error in config file kamailio-localmods.cfg, line 9, column 6: unknown config variable
 0(1542) CRITICAL: <core> [core/cfg.y:3447]: yyerror_at(): parse error in config file kamailio-localmods.cfg, line 9, column 7-8: 
ERROR: bad config file (3 errors)
 0(1542) WARNING: <core> [core/ppcfg.c:221]: pp_ifdef_level_check(): different number of preprocessor directives: N(#!IF[N]DEF) - N(#!ENDIF) = 1

Additional Information

  • Kamailio Version - output of kamailio -v
version: kamailio 5.1.6 (x86_64/linux) 
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144 MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: unknown 
compiled with gcc 4.9.2
  • Operating System:
Linux ip-10-101-2-78 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1 (2016-12-30) x86_64 GNU/Linux
@mckaygerhard
Copy link
Author

mckaygerhard commented Dec 20, 2018

seems related to #1159 but was closed, if i use directly the value then the problem described in #1159 raised ... how can i use my hardcoded ip in the if-else clausules?

@SipSeb
Copy link
Contributor

SipSeb commented Dec 21, 2018

I think, in your case, the syntax could be wrong.

Try:
config.kamailioip=10.10.10.10

@miconda
Copy link
Member

miconda commented Dec 21, 2018

Like @SipSeb said, the syntax for custom varaibles is group.name:

Closing it.

@miconda miconda closed this as completed Dec 21, 2018
@mckaygerhard
Copy link
Author

|@·2#$%" puff @SipSeb and @miconda i tried that also, do you guys noted that same problem happened in the other -...

seems the "dots" are misinterperted due the presence of the aliases variable that already are present! and that generated a very very older problem! what f++ happend close it and no verification of an acient bug!???

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants