Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Time Profile Problem on V2.1
- Thread starter IPGuru
- Start date
- Status
- Thread starter
- #22
- Thread starter
- #25
intrigrant
Systems Engineer
Nice discussion,
As IPGuru said, the notification on extensions will only change after receiving a call when the time profile is active, this has been the way it works from the beginning ( even Network Alchemy does it this way i believe ) and as it is upto Avaya it will never change. Keys programmed to switch the night mode of a group wil not lit even if a time profile switches a group to night mode.
I've been testing time profiles last week because of a problem. I noticed that the time profile will become active after the time set, e.g. if you program 12:00 hours to switch it will switch after 12:00,59.
The profile must be at least 5 minutes active before another switch can be made.
Calls ringing the group at the point of switching will not be affected as it did in the first 1.3 version.
A profile for a Incoming Call route works reversed as it does for a group ( IPO 2.1(24) ), that was the problem!
I experienced no problem with turing on/off a group with a time profile, the display is very confusing if you do not know how it works, not lighting up a programmed key for switching night mode of a group is idiot and you cannot explain this to a customer as it does lit if you press the key. ( a challenge for Avaya!, i reported this as a 3.0 feature request )
Then some tips on the time server for IPO:
I use a Compaq Proliant Win2K server as a VM pro for a year now and never had any problem with it, i only had a problem with a Compaq as a VM Pro server with multiple processors in it ( to fast for Avaya? ).
The timeserver of the VM Pro will only become active as the VM pro server is started and there is no Manager or another time server active on the PC.
You can make the PC act as a timeserver wether VM Pro is active or not, change the registry :
HKEY LOCAL MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\ReliableTimeSource : value = 0 or 1 ( 0 = client 1 = server )
This will make your PC act as a timeserver.
Do NOT do this if there is a Domain controller! It will disturb the network logins as WinNT,2000 and 2003 uses Kerberos 5 as a security on logons and this service is depending on the time on the Domain controller ( users cannot logon anymore as their PC's receive the time from your VM Pro, nice if they don't wanna give you coffee!
.
You can check for a DomainController typing the following command in a DOS box : net time /rtsdomain:domainname, if it gives back a time then there is a domain controller active as a timeserver, use the DomainController for the time of IP Office as it is supposted to have a reliable time.
Even better is if you have direct access to the Internet, use a SNTP server on the internet, there are several of them, check : for available servers you can use.
Check the following document for more details on time service on Windows 2000/2003/XP:
As IPGuru said, the notification on extensions will only change after receiving a call when the time profile is active, this has been the way it works from the beginning ( even Network Alchemy does it this way i believe ) and as it is upto Avaya it will never change. Keys programmed to switch the night mode of a group wil not lit even if a time profile switches a group to night mode.
I've been testing time profiles last week because of a problem. I noticed that the time profile will become active after the time set, e.g. if you program 12:00 hours to switch it will switch after 12:00,59.
The profile must be at least 5 minutes active before another switch can be made.
Calls ringing the group at the point of switching will not be affected as it did in the first 1.3 version.
A profile for a Incoming Call route works reversed as it does for a group ( IPO 2.1(24) ), that was the problem!
I experienced no problem with turing on/off a group with a time profile, the display is very confusing if you do not know how it works, not lighting up a programmed key for switching night mode of a group is idiot and you cannot explain this to a customer as it does lit if you press the key. ( a challenge for Avaya!, i reported this as a 3.0 feature request )
Then some tips on the time server for IPO:
I use a Compaq Proliant Win2K server as a VM pro for a year now and never had any problem with it, i only had a problem with a Compaq as a VM Pro server with multiple processors in it ( to fast for Avaya? ).
The timeserver of the VM Pro will only become active as the VM pro server is started and there is no Manager or another time server active on the PC.
You can make the PC act as a timeserver wether VM Pro is active or not, change the registry :
HKEY LOCAL MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\ReliableTimeSource : value = 0 or 1 ( 0 = client 1 = server )
This will make your PC act as a timeserver.
Do NOT do this if there is a Domain controller! It will disturb the network logins as WinNT,2000 and 2003 uses Kerberos 5 as a security on logons and this service is depending on the time on the Domain controller ( users cannot logon anymore as their PC's receive the time from your VM Pro, nice if they don't wanna give you coffee!
.You can check for a DomainController typing the following command in a DOS box : net time /rtsdomain:domainname, if it gives back a time then there is a domain controller active as a timeserver, use the DomainController for the time of IP Office as it is supposted to have a reliable time.
Even better is if you have direct access to the Internet, use a SNTP server on the internet, there are several of them, check : for available servers you can use.
Check the following document for more details on time service on Windows 2000/2003/XP:
- Thread starter
- #28
intrigrant
Systems Engineer
It is solved in 2.1(24) i have checked today.
And ok, i could be shorter but there was nothing on TV and i had nothing else to do, apologies for that.
And ok, i could be shorter but there was nothing on TV and i had nothing else to do, apologies for that.
- Status
Similar threads