Ignore IP Station Warnings

[Novo1]

We have a lot of home workers using IP Softphones and every time one logs off it creates a warning in the error logs. I know with analog stations you can tell the PBX not to monitor the connection status of these devices. Can I do that with IP stations? I can't seem to find a setting for it and the logs are chalk full of these warnings.

Thanks

 

[SF0751]

Try setting "Record IP Registrations in History Log" to NO - page 2; cha sys fea.

Susan
“Before you criticize someone, you should walk a mile in their shoes. That way when you criticize them, you are a mile away from them and you have their shoes.”

 

[AvayaTier3]

what is the warning? what is the maintenance object?

cut and paste the error log entry here.

maybe you can disable an MO and keep these out of the error logs.

another option is logging levels. This is a little long but I am going to put it here anyway. What Susan is asking you to try will keep registrations out of list history but not the error logs.

Information about commands and history of transactions in CM and Linux commands (has nothing to do with error logs)
Sorry.

"all commands entered at the console or Definity terminal emulator"

This is not possible because the software only logs commands for add, change, remove, and some maintenance commands like test, busy, release, reset to name a few. Display, list, status, commands and many others do not get logged and you would never know that anyone is doing them unless you do status logins while these type commands are active.

You can monitor user's changes with Command: notify history (in realtime)

Command: list history (1800 line circular buffer of commands)

How fast this buffer fills is determined by numbers of changes and what data you are sending to the history log. (This can be controlled in cm4 and higher)

Items like tti / psa / cms agent changes in loads before cm4 can also be controlled.
----------------------
cm4 and higher:

Command: change logging-levels

change logging-levels Page 1 of 2

LOGGING LEVELS

Enable Command Logging? y
Log Data Values: none

When enabled, log commands associated with the following actions:

add? y export? y refresh? y
busyout? y get? n release? y
campon-busyout? y go? y remove? y
cancel? n import? y reset? y

change logging-levels Page 2 of 2

LOGGING LEVELS

Log All Submission Failures: y
Log PMS/AD Transactions: n
Log IP Registrations and events: y
Log CTA/PSA/TTI Transactions: y
---------------
prior to cm4:

system-parameters features

Record CTA/PSA/TTI Transactions in History Log? y
Record All Submission Failures in History Log? y
Record PMS/AD Transactions in History Log? y
Record IP Registrations in History Log? n
------------------
different versions of CM store commands (CM and linux) in different files.
Data that is stored in the files changed from version to version.
Basically all of this is in the file system and you will have to look at the files and timestamps on the files to see what your system normally stores before the data is overwritten. These files will store more than the 1800 lines that you can access from CM Command: list history
Also be aware that on duplicated servers, the offline (standby) server logfiles
will not have current CM commands stored. The commands logfiles will have data from the last time the server was active. Knowing this about your system and doing interchanges based on times just before files are to be overwritten will double the amount of stored data in the combined server's files.

/var/log/messages
/var/log/messages.1
/var/log/messages.2
/var/log/messages.3
/var/log/messages.4
/var/log/commandhistory
/var/log/commandhistory.1
/var/log/commandhistory.2
/var/log/commandhistory.3
/var/log/commandhistory.4
----------------------------------
you could write a script to copy or tar and zip and copy to another server on an as needed basis.

script could be as simple as follows which will create a tar.gz file with the server_name and date in the file name. Then use scp or ftp to copy the archive file off of the server to another server.

tar cvf /var/home/ftp/pub/`uname -n`_`date +%m%d%y`_hist_logs.tar /var/log/mess*
tar rvf /var/home/ftp/pub/`uname -n`_`date +%m%d%y`_hist_logs.tar /var/log/ecs/commandhist*
gzip /var/home/ftp/pub/`uname -n`_`date +%m%d%y`_hist_logs.tar


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting

http://bshtele.com

 

[Novo1]

Yeah I don't think logging is the issue. I am running CM 3.1.3 by the way. Below is what I am receiving in the error logs. There are 6 pages of these. Some dates are old because the phones are set up but not in use at this time so not connected.


display errors Page 1

HARDWARE ERROR REPORT - ACTIVE ALARMS

Port Mtce Alt Err Aux First Last Err Err Rt/ Al Ac
Name Name Type Data Occur Occur Cnt Rt Hr St

S00070 DIG-IP-S 14001 1537 40968 09/24/10:18 09/24/10:18 1 0 0 a n
S00070 DIG-IP-S 14001 1 09/24/10:33 09/24/10:33 2 0 0 a n
S00447 DIG-IP-S 14819 1537 40968 09/26/12:54 09/26/12:54 1 0 0 a n
S00447 DIG-IP-S 14819 1 09/26/12:55 09/26/12:55 2 0 0 a n
S00393 DIG-IP-S 14307 0 40968 10/24/08:08 10/24/08:09 2 120 0 a n
S00393 DIG-IP-S 14307 1 10/24/08:10 10/24/08:10 2 0 0 a n
S00530 DIG-IP-S 14324 1 10/31/07:31 10/31/07:31 2 0 0 a n
S00531 DIG-IP-S 14325 1 10/31/07:31 10/31/07:31 2 0 0 a n
S00509 DIG-IP-S 14318 0 40968 11/08/17:00 11/08/17:00 1 0 0 a n
S00509 DIG-IP-S 14318 1 11/08/17:10 11/08/17:10 2 0 0 a n
S00501 DIG-IP-S 14315 0 40968 11/09/20:24 11/09/20:24 1 0 0 a n
S00501 DIG-IP-S 14315 1 11/09/20:26 11/09/20:26 2 0 0 a n
S00432 DIG-IP-S 14804 1537 40968 11/21/14:05 11/21/14:56 2 2 0 a n

 

[Novo1]

By the way Susan the "Record IP Registrations in History Log" are set to No for my system so that's not it.

Thanks anyways though

 

[AvayaTier3]

If these stations are programmed as Port: X they should not have entries in the error log.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting

http://bshtele.com

 

[phoneguy55]

these are stations that are out of service. Put them in service and the alarm will go away.

 

[Novo1]

phoneguy55: As I noted in my original post, I know they are out of service. They are home agents on soft phones. Not always connected. So no, I can't just put them in service. They will constantly go in and out of service since they aren't always connected.

AvayaTier3: They are programmed as 4610s to match what our brick and mortar systems have so a port was auto assigned by the system. Someone else suggested a 6424D+ but that gives me an error saying that auto answer and incoming auto answer can't be administered at the same time. We need auto answer so any ideas there?

 

[Mitch672]

Yes, live with the warnings. I don't see it as a big deal, show stopper.



Mitch

AVAYA Certified Expert

 

[phoneguy55]

Exactly, what Mitch said.

 

[Novo1]

Not a big deal no. More of an annoyance when I have to sift through 6 pages of disconnected soft phones looking to see if something else that IS important is wrong.

 

[PeteBull]

I agree. I would like to find a way to disable the alarms and errors for IP Agent phones that are disconnected.