Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Upgraded to 3.1. Now having several problems

Unanswered Question
Aug 9th, 2001
User Badges:

I upgraded to 3.1 on Wednesday morning. Half my phones have not reset themselves therefore they will not communicate with the new CallManager. These phones are distributed throughout the state. This is causing quite a problem.

Anyways, after the upgrade both Personal Assistant and AutoAttendant cease to work. I have current versions of both running with the JTAPI included in the 3.1 upgrade. On AutoAttendant JTAPI subsystems are in a constant state on initializing. Anyone else having these problems.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
tboynton Tue, 08/14/2001 - 07:10
User Badges:

Yah, I figured that. I assume you mean the autoattendant, not the webattendant? I don't use the webattendant. The autoattendant had to upgraded to the Extended Services Apps. It works fine now.

tvanblon Mon, 08/13/2001 - 06:42
User Badges:

I am having the same problem. Phones must be powered off and back on to properly reset. The event viewer shows alot of remote phones "unregistering", in addition to a "cpqarry" error and some "termserverprinting" errors. Remote phones are acting very screwy - I can't hang up the phone sometimes, and hear no ringback on remote phones. I wish I'd never put on that bios update or the 3.1(1).

tboynton Tue, 08/14/2001 - 07:08
User Badges:

I believe cpqarry error is referring to the array controller or driver. You may want to take a look at that error to make sure it is not telling you something critical about your drives. You wouldn't want to lose them.


This Discussion