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 wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
What's your CM Uptime? How often do you restart your physical CM servers?
- Thread starter fataldata
- Start date
AvayaTier3
Technical User
Unless you have issues that are known to be resolved by rebooting servers, why not let them continue to run?
Avaya has no regular scheduled maintenance that includes rebooting Linux servers running CM.
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
Avaya. Too little or no help? Expensive?
For FAST switch support at bargain rates, give bsh a call.
bsh
40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
Avaya has no regular scheduled maintenance that includes rebooting Linux servers running CM.
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
Avaya. Too little or no help? Expensive?
For FAST switch support at bargain rates, give bsh a call.
bsh
40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
- Thread starter
- #3
We have been advised by our Business Partner. Upgrading is the only option which has been suggested to resolve our issue however our organization is unwilling to do this due to the 7 figure cost (at least this is what I am told).
We have speculated on reloading our CM from scratch however the risk involved in doing this makes me uncomfortable. If we reload we would rebuild Translations from scratch as well.
What causes the software corruption in our system can only be speculated on it has been investigated via partners and Avaya ad nauseum and the only solution provided is to upgrade. It has a vague connection to when we had SIP enabled on our CM3.1.5
We are considering removing all SIP from this system.
We have speculated on reloading our CM from scratch however the risk involved in doing this makes me uncomfortable. If we reload we would rebuild Translations from scratch as well.
What causes the software corruption in our system can only be speculated on it has been investigated via partners and Avaya ad nauseum and the only solution provided is to upgrade. It has a vague connection to when we had SIP enabled on our CM3.1.5
We are considering removing all SIP from this system.
AvayaTier3
Technical User
What type software corruption have you experienced? Rebuilding CM translations from scratch is rarely needed as an option.
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
Avaya. Too little or no help? Expensive?
For FAST switch support at bargain rates, give bsh a call.
bsh
40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
Avaya. Too little or no help? Expensive?
For FAST switch support at bargain rates, give bsh a call.
bsh
40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
- Thread starter
- #5
It's an issue that renders Hunt Groups unavailable and ACD's that are logged in are some times in the wrong skills.
I believe you may be familiar with this. Donald S may have reviewed some logs with you on 4/12 and that is where the recommendation to reboot the servers is coming from. I just was curious how long other users servers have been up. We will most likely follow this suggestion when traffic volume subsides.
I believe you may be familiar with this. Donald S may have reviewed some logs with you on 4/12 and that is where the recommendation to reboot the servers is coming from. I just was curious how long other users servers have been up. We will most likely follow this suggestion when traffic volume subsides.
AvayaTier3
Technical User
The bug and corruption you speak of is in the software tables for hunt group members.
The bug is fixed in CM4 and the fix was not ported back to cm4 software versions.
Reloading and rebuilding from scratch will not fix your issue. The issue will return.
The software pointers to unused records becomes corrupt and causes used records and linkages
of used records to no longer work.
reboot of CM rebuilds these linkages as agents login. For EAS agents, the records have no data and are
not linked to other agents until they login after the reboot.
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
Avaya. Too little or no help? Expensive?
For FAST switch support at bargain rates, give bsh a call.
bsh
40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
The bug is fixed in CM4 and the fix was not ported back to cm4 software versions.
Reloading and rebuilding from scratch will not fix your issue. The issue will return.
The software pointers to unused records becomes corrupt and causes used records and linkages
of used records to no longer work.
reboot of CM rebuilds these linkages as agents login. For EAS agents, the records have no data and are
not linked to other agents until they login after the reboot.
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
Avaya. Too little or no help? Expensive?
For FAST switch support at bargain rates, give bsh a call.
bsh
40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
- Thread starter
- #7
- Thread starter
- #8
AvayaTier3
Technical User
I thought you moved your call center off the Avaya cm3 platform as a work-around.
Forgive the above typo:
The bug is fixed in CM4 and the fix was not ported back to cm4 (should have read CM3) software versions
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
Avaya. Too little or no help? Expensive?
For FAST switch support at bargain rates, give bsh a call.
bsh
40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
Forgive the above typo:
The bug is fixed in CM4 and the fix was not ported back to cm4 (should have read CM3) software versions
A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"
Avaya. Too little or no help? Expensive?
For FAST switch support at bargain rates, give bsh a call.
bsh
40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]
- Thread starter
- #10
We have mostly, currently there are some Front Desks that are still using the ACD functions of the CM3. Those are to be removed by the 29th. After that if the Hunt corruption continues it's main effect is to cause Voicemail to become unavailable. Lately the corruption recurrence has accelerated even with drastically reduced agent usage on the system. The issue you helped investigate Friday looks to be coincidental with an SES login that was up for 99.9 hours. We are investigating why that may have been.
- Status
Similar threads