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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Norstar 8 x 24 trbls

Status
Not open for further replies.

ebcomm

Vendor
May 16, 2005
35
CA
I am working on a 8 x 24 with DR5 DS and a Flash 4. There is a central answering position (M7324 with a CAP) that displays the message 'No Party Connect'(at times) when transferring a call to VM. I have tried adding intercom keys but this does not resolve this trbl. I also tried reversing the CAP power supply leads and no change.
The customer wants a CAP added to the backup answering position but after programming the CAP keys with the internal locals, I used F*0 to verify. Partway through the verification the whole system restarted. I am able to recreate this senario and it is definately happening when I use F*0 on that particular CAP. Has anyone else had this upsetting experience?
Is this a symptom of a defective KSU power supply or a software cartridge that is about to go south?
 
no party connect" Happens when you try to transfer without having an active call. Usally the operator will put the party on hold then try to transfer to VM. thus "no party connect"
Have you told the system waht station the second cap is assigned to?

 
The call is answered and not put on hold, the receptionist hits the VM key(F*0)and enters the VM#......response is 'no party connect'. It works at times,others not. If you disconnect the set then it will work great for 30 minutes or so and then back to the same old trbl.
Yes I have told the system where the second CAP is. The other CAP is on the backup answer position and is a seperate trbl.
 
I'm not sure I understand, F*0 is the code for checking what is under a button. The code for transfering to a VM box is F986.
Have you tried a system reboot, sometimes you just need clear all the junk.

 
F*0 is used to verify what is assigned to a key.
I replaced the CAP and the problem was verified as a defective CAP. This is a first because I have never seen a CAP cause a system restart. The 'No party connect' trbl experienced by the other erception position also was solved once the new CAP was installed on the second receptionists phone.
I know that F986 is the code for VM.
Thanks for the feedback.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top