| |||||||||
![]() | | ||||||||
| |||||||||||||||
| |||||||||||||||
| Meridian Systems Welcome to the Nortel Meridian Forums Including Meridian Options 11-81C CS1000M Meridian Mail Call Pilot Companion and Sucession Hospitality OTM MAT MICB RAN NetGateway ..., and all other Applications |
| Tags: 3904, phone, problems, strange |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) | ||||||||
| Junior Member
Location: Missouri Rep Power: 6 ![]() | TN and 3904 strange phone problems Had a strange issue with a 3904 in the past few days. Last week the 3904 was dropped on the floor. Part of the display had issues and the Plantronics headset amp stopped working, but the phone continued to work. I replaced the Plantronics amp on Thursday. Friday I had an open repair ticket when the phone user couldn't use the connect button to complete the transfer of callers into CP Express Messaging. (The connect button is the leftmost button when needed; this also happens to be the side of the display that has issues). Over the weekend I tried some remote troubleshooting when I saw in the TTY log ERR057 on the phone's TN. Tried to IDU and FWVU the phone and it would not respond, so tonight I swapped out the phone; enable/disable the TN did not work either. However, when I put the new phone into place the brandline and time/date appeared, but the time/date remained at midnight, and none of the DN keys appeared. Took the phone to the MDF, pulled the jumpers and put the new phone into place - same problem, so its not the wiring. Next, I copied the TN to another TN and put the new phone onto it - the phone worked perfectly, and transfers could be completed properly. OUTed the old TN and copied another phone TN onto it - it now worked perfectly (old and new phone); both also respond to IDU and FWVU commands. Should I be concerned about any corruption in the switch? Or, could their have been physical problems with the old phone that sent the TN into never-never land that outing and rebuilding the TN reset? I did run a LD1 template audit prior to doing any of the TN work and it came up clean. System is running 4.5 on the 11c platform. | ||||||||
| | |
| | #3 (permalink) | ||||||||
| Junior Member
Location: Houghton, NY Rep Power: 7 ![]() | I have had this happen before (without the dropping). When printing the TNB I would find that there would be holes (spaces) in the TNB printout. I have also seen where the programming would jump from key 0 to 7 with nothing inbetween. You are normally all set if you were able to out and rebuild. You may want to run some template audits LD 1 to make sure there is no corruption there, and lastley. Always do an EDD when making major changes. | ||||||||
| | |
| | #4 (permalink) | |||||||||
| Junior Member
Location: Missouri Rep Power: 6 ![]() | Quote:
One of the other strange things was that even though the key labels didn't show up on the new phone on the original TN, the keylamps would light and I could get dial tone, only I wouldn't get labels. I think the TN hardware/software just probably got flaked out somehow (given the ERR057 indication) and was not database corruption. I ran template audits prior to and after I did the TN work. Last edited by telecom116 : 03-27-2006 at 01:03 PM. | |||||||||
| | |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |