Bob Nelson
IS-IT--Management
Here's the deal: My company isn't a telephone company - at all. We're bench techs, field service, etc., in the electronics, computer, networking, security/surveillance and two-way radio fields. We're in a geographically isolated area of the US and so, occasionally, I get asked to do things I'd prefer to stay away from but need to keep my customer happy. Such is the case here...
A small firm needed to move, on short order, their office. They had an old Merlin II system and nobody that could move it - and the one telephone guy in the 60 mile range said he'd be happy to sell them a new system but didn't know anything about their Merlin and couldn't move it for a month anyway... Sooo... I was asked if I'd take it on as part of their IT movement requirements, to which I foolishly said I would.
I carefully documented the connections, etc., and moved the system to the new location, wired in new jacks, etc., and restored the system to life (mostly). Smally caveat, I didn't get to pull the phones from the old location - including the receptionist's 7318H, so I didn't get a first-hand view of how it was connected, nor preserve/secure the station to my satisfaction for the move. Overall, things are working except for this tweeky issue I can't resolve. I'm looking for someone willing to provide advice and happy to kick down some PayPal bucks for a successful resolution to this problem...
Here's what's going on: They have a receptionist's station that is labeled 7318H01A. All calls from 6 lines are supposed to ring at that station (which they do). However, the station only rings once at that station (the light indicates that the line is ringing, but no additional ringing sound at the receptionist's station). About 2-3 seconds later, all the "group phones" ring and can be answered and the call properly completed. If the receptionist can catch things quickly, before another extension picks up, she can manually select the ringing line and answer the call. I was told that the way the system worked before the move (of course, that makes it my fault... LOL) was that the receptionist's station would ring 3 times and if she didn't pick up, then it would go to the group and her phone would continue to ring, allowing anyone in the group - or reception - to pick up the ringing line. Testing the system out, I noted that this new behavior happens on all 6 incoming lines.
What I've done so far: Tested all the desksets and the receptionist's system to ensure incoming and outgoing calls behaved properly, as well as deskset-to-deskset calls work properly. Pulled a manual for the 7318H and read it cover-to-cover, but didn't see anything helpful. Toggled their after-hours switch (thought maybe it thought it was in after-hours mode or something along those lines). Now I'm trying to wade through the Merlin II Release 3 System Manual to see if I can glean some idea that may solve the problem.
So, I'm after some cheating answers so I have some clue about this system, namely:
Is there a way to get a dump from the 7318H to see what has been programmed into the buttons? (I'm assuming the problem here is relatively small and maybe some "feature" was turned on/off during the move)
Any idea of a situation that would cause the problem cited, and a solution I can test?
Other than, "Take that old crap out in the parking lot and burn it," any other thoughts?
Thanks in advance,
Bob Nelson, Westside Technologies
Aberdeen, Wa
A small firm needed to move, on short order, their office. They had an old Merlin II system and nobody that could move it - and the one telephone guy in the 60 mile range said he'd be happy to sell them a new system but didn't know anything about their Merlin and couldn't move it for a month anyway... Sooo... I was asked if I'd take it on as part of their IT movement requirements, to which I foolishly said I would.
I carefully documented the connections, etc., and moved the system to the new location, wired in new jacks, etc., and restored the system to life (mostly). Smally caveat, I didn't get to pull the phones from the old location - including the receptionist's 7318H, so I didn't get a first-hand view of how it was connected, nor preserve/secure the station to my satisfaction for the move. Overall, things are working except for this tweeky issue I can't resolve. I'm looking for someone willing to provide advice and happy to kick down some PayPal bucks for a successful resolution to this problem...
Here's what's going on: They have a receptionist's station that is labeled 7318H01A. All calls from 6 lines are supposed to ring at that station (which they do). However, the station only rings once at that station (the light indicates that the line is ringing, but no additional ringing sound at the receptionist's station). About 2-3 seconds later, all the "group phones" ring and can be answered and the call properly completed. If the receptionist can catch things quickly, before another extension picks up, she can manually select the ringing line and answer the call. I was told that the way the system worked before the move (of course, that makes it my fault... LOL) was that the receptionist's station would ring 3 times and if she didn't pick up, then it would go to the group and her phone would continue to ring, allowing anyone in the group - or reception - to pick up the ringing line. Testing the system out, I noted that this new behavior happens on all 6 incoming lines.
What I've done so far: Tested all the desksets and the receptionist's system to ensure incoming and outgoing calls behaved properly, as well as deskset-to-deskset calls work properly. Pulled a manual for the 7318H and read it cover-to-cover, but didn't see anything helpful. Toggled their after-hours switch (thought maybe it thought it was in after-hours mode or something along those lines). Now I'm trying to wade through the Merlin II Release 3 System Manual to see if I can glean some idea that may solve the problem.
So, I'm after some cheating answers so I have some clue about this system, namely:
Is there a way to get a dump from the 7318H to see what has been programmed into the buttons? (I'm assuming the problem here is relatively small and maybe some "feature" was turned on/off during the move)
Any idea of a situation that would cause the problem cited, and a solution I can test?
Other than, "Take that old crap out in the parking lot and burn it," any other thoughts?
Thanks in advance,
Bob Nelson, Westside Technologies
Aberdeen, Wa