Time Profile Problem on V2.1

[IPGuru]

There is a minor buggete with time profiles on V2.1

If a group is using a time progile the indicator on the handset does not get updated to the current status untill a call is recieved.

this can lead customers to believe that N/S has not activated or cleared at the correct time.

 

[VOiDDude]

This bug was also in 1.2 or 1.3 (if I remember well).

This is not the only problem with the time profiles under 2.1.
On large systems we see that the time profiles just don't work and they take 5 to 15 minutes longer (it seems to be random) before they activate.

Avaya confimed this bug and the're working on a special build (with also fixes for queueing and overflow).

 

[Morrack]

Yes I'm anxiously awaiting the upcoming maintenance patch, especially for the queuing fixes.

btw I've recently confirmed a problem with 2.1 that avaya was NOT aware of, so we may not see a fix for a bit. The 8 port hub on a 403/406 has a tendancy to lock up occasionally. Rebooting the switch will clear it for a while. I've seen this at 2 sites now.

Peter

 

[dencom]

Peter,

Do you know if the queueing problem is also a problem in 2.0(18)? I have also a site where we experience almost every day the famous ghost calls.

Thxs

Arnoud

 

[IPGuru]

I do not believe that Avaya will be able to fix the Indicator problem.

I suspect that the software only checks the time profile for the group when a call is being proccesed.
It is at this point that the indicator is updated.

In short do not rely on the phone indicator to give a true Indication of the group status it could be minutes or even hours befor the 1st call arives & updates the display

 

[Morrack]

I sure hope not Arnoud, as I just downgraded a 2.1 site that was having major phantom calls to a 2.0(18). They also had way too few VMS ports for their needs, and I just installed a licence that doubled their ports, so I'll have to see how it goes in the next few days.

I've been sick at home most of this week so haven't been on top of this client like I would like - but spoke with them today and no mention of phantom calls, although the conversation was brief.

 

[IPOUK]

one of my sites, their time profile seems to be kicking in about 15 minutes late either way on 2.1. The vm server is the correct time and the phones display the correct time too! hope this maintenance update helps!

 

[IPGuru]

IPOUK, is the NS realy kicking in late or are they just complaining that the phone says day service?

What happens when you make a cal to the number?

I have been looking at a site that was making this complaint & have proved that when the call arives it is processed correctly. I have not been able to cause a true timeservice failure on any of my test systems (yet)

 

[alan24]

I also have a site that is doing this, again all the times are correct but it goes into N/S approx 15mins late. I have been on site a couple of times and tried it myself. The time profile worked fine before upgrading 2.1

 

[VOiDDude]

IPGuru,

I think you need to test the time profiles on 'loaded' systems. It think the delay of the time profile is related to the load on the system.

 

[IPGuru]

that would certainly seem to fit the reports here, I ahave a troublesom site I will start to monitor closley

 

[alan24]

Does anyone know when the maintenance patch mentioned earlier in this thread will be available?

 

[IPOUK]

nope - I have called the number on my way home on the train. Directly at 6, the calls are still going through as usual. I have tried it in the morning as well, and the calls are going through to Night Service still at 9am! I try 15 or so minutes later and it seems ok.

I have deleted the time profile, taken it away from the hunt group, rebooted, added a new time profile and again added it the hunt group and still the problem is there. I suspect a dodgy/corrupt config, as I didn't do the install and there have been tons of problems.

 

[IPGuru]

Avaya Have admited that there is an issue with time profiles!
this should be fixed when the maintanence release becomes avaialblke at the end of august.

I have also just seen my test system enter n/s 1/2 hour fast!

 

[IPGuru]

Avaya have now advised thet the problem seemes to be caused by Compaq/HP PC's using an onboard network adapter.

Is anyone experianceing this porblem with other makes of PC?

 

[VOiDDude]

Huh ?

One the time of the IPO is correct the system should do the rest, no ? Do you mean the problem occurs when running the VMPro on a Comapq PC or the manager ?

 

[IPGuru]

The problem seems to be relted to the PC acting as the time server (this is usualy the VM PC)

Somthing strange in the compaq/hp bios appears to be causing the interferance.

Pc's with a seperate NIC do not seem to have the problems but Avaya will not garantee this as a fix.

 

[Morrack]

Very interesting.... that site that I mentioned earlier with the TONS of problems (although no NS probs) is using an HP server with onboard NIC....

Although the downgrade to 2.0.18 appears to have solved the problems...

Peter

 

[mforrence]

Strange... I have the time profile problem with our house system, but am using a Dell PC for Voicemail.

Mike

 

[IPGuru]

I have been running test today, the feed back from Avaya's Tech support appears faulty.
on a default IP403 with no time server (time set manualy) I am having the same problems.
My IP 401 however seems to work without problems.