Originally posted by da phone guy:
Weird, I wonder why the KSU/LCR isn't detecting that the line its about to grab is busy.
Do the lines DIT straight to VM in whatever mode (1,2,3) the system is in? If the line is pointed to VM but is also set to ring for that mode on a keystrip that may be your problem... that split second before the VM picks up it could be "ringing" on a set.
All 4 of their lines are set to ring directly to the VM hunt group 400 Day 1 and Day 2. In night mode, I've got it set to No data so it doesn't ring at all to the CIX100 because they forward their calls to an answering service for emergency purposes. The only exception is line 4/fax line. In night mode I have it ringing directly to SLT port ext 225 connected to the fax, so they can still receive faxes overnight. There are no line appearances on any of their 12 phone sets.
Originally posted by phonemeister:
Verify that 9 is LCR and not a direct trunk access code. If it's a direct trunk access code, then change to LCR.
9 is set for LCR on all of their trunks and phonesets, the hunt order is line 3, line 2, line 1, then line 4/fax.
So it seems when line 1 and 2 are in use, someone calls the main number which rolls over to line 3 which is available, and at the same time someone is dialing 9 to get an outside line and because 3 is the first one it chooses it's also intercepting that incoming call.
It's weird, they say it's happened about 5 times in the past month or so, but the timing is so coincidental and precise that I can't seem to find a solution.