Enabling Syslog for 9611G Phone

[mbong]

Using 9611G with 6.3037 firmware for H.323, I cannot seem to get syslog output working.

I've set the LOGSRVR option that I've been using with 9630G and 4621SW sets also on H.323 firmwares.

I've tried setting the following parameters as well:
SET LOGLOCAL 8
SET LOCAL_LOG_LEVEL 3
SET LOG_CATEGORY DHCP,NETMGR,AUDIO


I've also set the LOG option on the phone to DEBUG (and tried other options as well).

Am I missing a parameter to enable syslog on the 9611G?

Thanks in advance for any assistance.

[sunilkumarv]

hello,

here is the procedure

In the 46xxsettings.txt file under the “EVENT LOGGING SETTINGS”

· SET LOGSRVR X.X.X.X (Where X.X.X.X is the IP address of the Syslog Server/PC you already setup with syslog server application. Make sure that the syslog server and phones are reachable in the Network)
· On the settings file, SET LOGLOCAL 8 (For debug level).

For 46xx, 96xx, 16xx and 96x1-H323 phones:
Enter MUTE CRAFT #. Scroll down to Debug and set it ON. Also scroll down to Log and set it to Debug.
· Reboot the phones to pickup the new settings file.
· Make sure that the Syslog Server is up and running at this time to capture any event on the phones
· Do the test to reproduce problem

[mbong]

Hi sunilkumarv. Thanks for your response.

I tried the settings changes you noted, however I cannot find a DEBUG option from the phone on the 9611G. I tried adding SET NVDEBUG 1 to the settings file, but that didn't seem to do anything.

I do see a DEBUG option on a 9630G set, but checking that setting it is set to Off and syslog is working from that phone.

I want to add that I am trying to get this working on our phones with VPN enabled. I don't think that should make a difference with the syslog though.

[sunilkumarv]

I checked this on a 9608 phone 6.4fw as i dont have 9611G phone which i can use right now. i did not see debug option initially in craft menu.

i added below changes in the settings file, rebooted the phone and now i could see the debug option.

SET LOGLOCAL 5
SET LOCAL_LOG_LEVEL 7

I believe the phones may not be picking the settings file, you can use HTTP and then run a sniffer and see if the phones are taking the right settings files

Regards
Sunil

[gwebster]

With current releases of software on the 9611G and 9630G, you need to change the CRAFT password from it's default in order to access the DEBUG menu.

[mbong]

Thanks gwebster. I was able to get to the DEBUG menu by changing the CRAFT password. However, that didn't get me closer to getting the syslog working on the 9611G.

Currently, we have syslog working on a 9611G in the office by setting the LOGSRVR and going into the phone and changing the LOG setting to anything other than Disabled. Is there any way we can set this LOG setting from the settings.txt file? Changing around LOGLOCAL, LOCAL_LOG_LEVEL, and/or LOG_CATEGORY didn't seem to have any effect.

We are still not getting any syslog data from a 9611G connected to our system via VPN. We've had no issues with syslog on 9630G and 4621SW over VPN. I would think this rules out any port issues.

[mlombardi1]

Maybe this?

######### DEBUGGING SETTINGS (96x1 H.323 only) ###########
##
## LOGTOFILE specifies whether logging of optional debug messages
## to an internal file will be enabled or disabled.
## Value Operation
## 0 Disabled (default)
## 1 Enabled
## This parameter is supported by:
## 96x1 H.323 R6.2.3 and later
## B189 H.323 R1.0 and later
## SET LOGTOFILE 1

[mbong]

Just to note, I did try the LOGTOFILE setting. It's set to 1, but we are still not getting Syslog data from a 9611G on VPN.

[wstg]

Syslog

Go back into the phone via craft procedure, scroll down until you see a section called log. Set it to debug and save. This worked for me on a 9621G.

Within my 46xxsettings.txt:
a. LOGSRVR 192.168.1.4 in this case the IP is my desktop computers IP.
b. LOGLOCAL 8 – specifies the severity levels of events logged to the phone. 8 is Debug, Informational, Notice, Warning, Error, Critical, Alert and Emergency events are logged.
c. LOCAL_LOG_LEVEL – Set this to 7 Debug.

[mbong]

Resolved with Release 6.6.1

Recently, I contacted Avaya support again about this after trying what I thought was the latest release. I was promptly informed:
H323 96x1G VPN phones support syslog beginning with 6.6.1.

Yay, it is working now. Doesn't have quite the same info as the 9630G or 4621IP SW phones, but finally I can get certificate expiration info.