46xxsettings.txt firmware 3.002 1

[wildcard100001]

My MV_IPtel application has been locking up on occasion -probably because I have 1400 IP phones on it. I noticed in the settings file this option SET LOGBACKUP 1 I don't have this set in my settings file but it appears the phones are backing up after each call... I'd like to only back up if the users make a change to their buttons. If I add SET LOGBACKUP 0 , would this work?

How do I limit the number of times a phone is backed up to only when a button change occurs? In looking at the MV_tel log files... phones are constantly backing up.

Also, It's a really pain when MV_tel locks up as the users get:
HTTP Authentication abc
Enter authentication credentials
Realm: LIB

http://WWW-UNKNOWN

User ID: [ ]
Password: [ ]

Any way to prevent this from happening if the server does lockup or goes offline? The users can hit cancel... but it does come back. Also no dialtone when they do get this message until they hit cancel.

Thanks,

Wildcard

 

[phoneguy55]

1400 phones doesn't seem like a lot of phones for MVIPTel. Are you running it on a server with W2K3?

Putting this into your file should stop them from backing up after each call.

## Backup of Call Log Entries
## When LOGBACKUP set to "1" Call Log entries are backed up
## to & restored from standard backup file.
## Note: This feature is available on H.323 release 3.0 for 96xx.
## SET LOGBACKUP 1
SET LOGBACKUP 0

 

[wildcard100001]

Thanks phoneguy55.

Yes, it's W2K3... though it's a VMware slice.

I'll make the addition.

To bad I can't just push the 46settings.txt file without rebooting them. What a pain to reboot 1400 phones.. I do this via command stacking.. but still a pain.

Also is there anyway to avoid the phone HTTP error if/when the server is not available? It generates needless help tickets... I'd prefer "backup failed" then back to normal.

Thanks

Wildcard

 

[atwebb]

I have 3 sites now with mv_iptel freezing or hanging and causing the ip phone to prompt for authentication after every call. The users would like to keep the backup of the call log. The common points are windows 2003 server sp2, mv_iptel version 0.96. Someone has suggested memory leak but I suspect overload when a large amount of phones backup the call log at the same time. The server has to be rebooted to cure this authentication request. I have not yet collected the server event logs prior to this happening as clients are usually demanding a quick fix. Any ideas?

 

[Mitch672]

I have 2 suggestions/guidlines:

#1 Don't use "MVIPtel", use "Apache", it's much more reliable, and also has nice logs to check that are very detailed.

#2 Don't run it in a Virtual machine. You probably are not giving it enough timeslices for 1400 IP phones, it would be better to dedicate a real PC/Server for this, and you will avoid the issue, even if you stayed with MVIPtel



Mitch

AVAYA Certified Expert

 

[wildcard100001]

I also suspected that a large number of endpoints were backing up at the same time causing a lockup - the server would peg 100% CPU utilization. (on my vm slice it was causing other slices to have issues as well) It seemed like the watchdog service was the culprit. We'd go a month or so before it would happen again.

I simply disabled the log backup via phoneguy55's suggestion - SET LOGBACKUP 0 in the settings file. No issues since.

I'd ditch the call log backup for the sake of stability. Or follow Mitch's suggestions.

Wildcard

 

[Ratman01]

Does anyone know if the Call Log Backup was a feature for the 96xx phones prior to 3.xxxx firmware versions? I don't recall it being an option before.

 

[jimbojimbo]

My suggestion would be to run Apache HTTP Server. It supports WebDAV for the backups. I haven't had any issues with it. I also use the AJP1.3 Tomcat Connector to link to a Tomcat server for phone registration and push capabilities. I want to deploy EJB's for the phones but just haven't had time to work on it.