Call Pilot 150 2.1 Burping

[MarvO1]

System is MICS 6.1 with CP150, 2.1 software.
A total of 64 mailbox seats and 64 Unified Messaging seats with about 95% of all seats being used.
Calls are front doored by receptionist, not CP
System has about 80 sets, PRI etc. Has been running flawlessly for 3 years.
For the last month or so, the Unified Messaging portion has been locking up about once a week and the customer reboots the CP and all returns to normal. This week when they rebooted it, all calls transferred to sets with CFNA to CP could not get to mailbox. Feature 985 shows EXT 276, but original v-mail DN was 275. Verified with a set that port for 275 is good on KSU, but when connected to CP, always shows busy. Changed all of my CFNA to 276 to get customer working for now since CP has a bad port.
Can't decide wheather to try a re-install, try upgrading it, or replace it. I have a backup of CP, but it is quite old. I did replace the power supply just to eliminate it.
Guess I'm looking for your words of wisdom because I'm not used to having CP problems. Any suggestions? This is a large Law Firm that relies heavily on their beloved CP.


MarvO said it

 

[norstarboy125]

i would see how much futher you get with chging the fwd dn to the new vmail dn and see if that holds up but if this happens again i would just back it up and replace the callpilot and re-download sftware and test...

 

[CJG3]

But keep in mind that replacing the CP may require new key codes to be purchased.

 

[Deweyhumbolt]

So, Call Pilot was able to give out a new Pilot DN after the original went down?

 

[MarvO1]

Ya Dewey, it bumped it up 1. F985 now shows the new DN of 276. Set relocation is not, and has never been used. A real head scratcher. I fear that it will get worse. Has been running fine on 7 ports for over 24 hours now.

MarvO said it

 

[MarvO1]

CJG3, I thought the keycodes could be ported over to a new unit.

MarvO said it

 

[Deweyhumbolt]

They'll credit you new keycodes on the replacement, you just got to send the defective one back within 30 days. Or they bill you.

 

[exsmogger]

If you have the R3 upgrade I'd try that first. Your programming will still be there, and it may flush out the software corruption.

Brian Cox

http://www.jandjcommunications.com

 

[MarvO1]

Thanks exsmogger, I think that just might be a good first step. Nothing to lose by trying it. I just hope that all of my client software for Unified Messaging continues to work. I have warned the customer that they could lose messages anytime. I have never seen a CP act quite like this one is doing. Especially the lost port.

MarvO said it

 

[exsmogger]

Marv,

I'd also have the keycodes available, just in case, before you start the upgrade.

I've never seen one lose a port like that either.

Brian Cox

http://www.jandjcommunications.com

 

[RikRodgers]

I have had 2 instances on MICS 7.1, one with a NAM, the other with CP, when the f985 dn mysteriously changed.

All the ports worked ok, so all that was involved was changing the call fwd on the sets.

At the time, I was changing dn's with set relo off, but none of the dn's I'd changed corresponded with vm (b1, or b2).

 

[ptstechnician]

I'm with EX - Upgrade to 3.1. I had a CP 2.0 that had one mailbox having issues and since the upgrade, no problems.