CFB/1014, CFU/1014 not found in database

vaibhavs

Joined
Oct 2, 2009
Messages
95
Likes
0
Points
0
#1
I am seeing the following lines when executing:

tail -f /var/log/asterisk/full | grep "DEBUG"

1014 has "Call Waiting" Disabled! & no "Call Forwarding"



Code:
[Nov  2 10:41:12] DEBUG[24797] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:41:12] DEBUG[24797] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:41:24] DEBUG[24877] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:41:24] DEBUG[24877] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:41:29] DEBUG[24885] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:41:29] DEBUG[24885] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:41:35] DEBUG[24905] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:41:35] DEBUG[24905] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:41:40] DEBUG[24925] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:41:40] DEBUG[24925] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:41:45] DEBUG[24945] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:41:45] DEBUG[24945] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:41:51] DEBUG[24990] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:41:51] DEBUG[24990] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:41:56] DEBUG[25030] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:41:56] DEBUG[25030] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:42:01] DEBUG[25038] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:42:01] DEBUG[25038] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:42:07] DEBUG[25058] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:42:07] DEBUG[25058] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:42:12] DEBUG[25078] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:42:12] DEBUG[25078] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:42:24] DEBUG[25154] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:42:24] DEBUG[25154] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:42:29] DEBUG[25182] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:42:29] DEBUG[25182] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:42:35] DEBUG[25186] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:42:35] DEBUG[25186] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:42:40] DEBUG[25206] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:42:40] DEBUG[25206] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:42:45] DEBUG[25226] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:42:45] DEBUG[25226] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:42:51] DEBUG[25247] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:42:51] DEBUG[25247] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:42:56] DEBUG[25307] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:42:56] DEBUG[25307] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:43:01] DEBUG[25331] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:43:01] DEBUG[25331] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:43:06] DEBUG[25339] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:43:06] DEBUG[25339] func_db.c: DB: CFB/1014 not found in database.
[Nov  2 10:43:12] DEBUG[25361] func_db.c: DB: CFU/1014 not found in database.
[Nov  2 10:43:12] DEBUG[25361] func_db.c: DB: CFB/1014 not found in database.

Seems like some mis-configuration.

How should I solve this ?

Thx
Vai
 

vaibhavs

Joined
Oct 2, 2009
Messages
95
Likes
0
Points
0
#2
Any help here?

Thx
Vai
 

dicko

Joined
Oct 24, 2008
Messages
4,099
Likes
0
Points
0
#3
Perhaps you mis-understand the nature of debug messages, they are informational for debugging, not indicative of a "BUG"

If 1014 had "Call Forwarding Busy" or "Call Forwarding Unavailble" set, then the db entries for CFB and/or CFU WOULD have been found and acted on, and the log lines would not have been written.

Does that make sense?.

p.s.
You can see the Call forward status of all of your extensions with

rasterisk -x 'database show'|grep CF

p.p.s

If those lines annoy you you can turn them off with

core set debug 0

or

core set debug /file/of/your/choice

to redirect the debug output to a file.
 

vaibhavs

Joined
Oct 2, 2009
Messages
95
Likes
0
Points
0
#4
Ahhh!!! Thx for clarifying, makes sense now.

I will try to set `core set debug 0`

Thx
Vai
 

Members online

No members online now.

Latest posts

Forum statistics

Threads
30,900
Messages
130,884
Members
17,561
Latest member
marouen
Top