OBI drops outbound calls - setup sysloging to help figure it out

My OBI-100 drops outbound calls usually right at 16 minutes. First thing I noticed there was some stale config on the OBI device. When I thought Google Voice (free) was going away I paid for another VOIP provider. Today I noticed there was some stale config related to the old VOIP provider related to keepalive server config. I restored all of that to default. So hopefully that will fix the problem. But then I wanted to setup syslog for my obi device and also to direct those logs to their own file.


  1. On Linux host which is on same LAN open up /etc/rsyslog.conf and uncomment the below lines:

# Provides UDP syslog reception
#$ModLoad imudp
#$UDPServerRun 514

# Provides TCP syslog reception
#$ModLoad imtcp
#$InputTCPServerRun 514

(i.e. remove the hashes in red).

  2. In /etc/ryslog.conf add the following lines just before the indicated lines (assuming that OBI is at 192.168.1.2). Notice that the & ~ line will discard the message so it won't also end up elsewhere.

#For OBI
if $fromhost-ip startswith '192.168.1.2' then /var/log/obi.log
& ~

# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
*.info;mail.none;authpriv.none;cron.none                /var/log/messages
 
(i.e. add the lines in red)

3. Touch the log file and restart the rsyslog service.

 # touch /var/log/obi.log && systemctl restart rsyslog.service

4. Go to the OBI and under SystemMangement/DeviceManagement/Syslog input the ip address of the Linux Host.
Post a Comment

Popular posts from this blog

Hit failing alternator with a hammer to confirm diagnosis of failing alternator due to bad brushes

alternatives --install gets stuck: failed to read link: No such file or directory

Using SSH, SOCKS, tsocks, and proxy settings to create a simultaneous "dual use" work/home computer