KrisBoutilier
IS-IT--Management
So, on my old Norstar system I could have a line appear on more than one key on a set. The first call that arrived on the set would start it ringing and the indicator next to the 'first' line key would start indicating. When a second or subsequent call arrived and the first call was still in progress the indicator next to the second (or subsequent) key would indicate. The indicator would simply hunt up the keys. All good...
Now, when my CS1000 was configured by the installer they configured each TN with its prime DN on key 00 SCR (eg. 6901) and a different DN on key 01 SCR (eg. 7901) and used LHK to 'overflow' the second call into the second DN. I was informed that this was how multiple appearances needed to be done on release 4.5. Fine, a little odd and costly in terms of assigned DNs, but no real problem...
Finally, we had some DNs programmed on the system that appear on multiple TNs (such as the IT helpdesk). Unfortunatly, as installed, they were SCR which caused any one call to block all the operators. We converted them to MCR and, voila!, multiple concurrent calls on multiple TNs, as expected.
Now we've added a second appearance of the group DN (eg. IT helpdesk) on a phone that already has two of its own DN appearances. Eg. on an i2004:
KEY 00 SCR 6901 1 MARP
01 SCR 7901 D MARP
02 MCR 6441 D
03 MCR 6441 D
LHK 2
EFD 6888
HUNT 6888
EHT 6888
This seems to work fine from a dialplan perspective, however the first incoming call on 6441 always flashes the indicator on both key 02 and key 03, unlike the Norstar which would only indicate on key 02 unless there really were two concurrent starts on 6441... it hasn't been too much of an issue for helpdesk staff, but now the users at large would like the same facility and I'm worried we're going to be spending a lot of time trying to explain the phantom second call. The 'fix' would seem to be to create yet another DN (7441) and use it on key 03, but then what would the interaction with LHK be like? And how would we add a third appearance as 8441 is not available?
I can't believe CS1000/Succession would be less capable than lowly Norstar/MICS in this regard (one indicator per underlying call per TN for MCR keys).
Any suggestions?
Now, when my CS1000 was configured by the installer they configured each TN with its prime DN on key 00 SCR (eg. 6901) and a different DN on key 01 SCR (eg. 7901) and used LHK to 'overflow' the second call into the second DN. I was informed that this was how multiple appearances needed to be done on release 4.5. Fine, a little odd and costly in terms of assigned DNs, but no real problem...
Finally, we had some DNs programmed on the system that appear on multiple TNs (such as the IT helpdesk). Unfortunatly, as installed, they were SCR which caused any one call to block all the operators. We converted them to MCR and, voila!, multiple concurrent calls on multiple TNs, as expected.
Now we've added a second appearance of the group DN (eg. IT helpdesk) on a phone that already has two of its own DN appearances. Eg. on an i2004:
KEY 00 SCR 6901 1 MARP
01 SCR 7901 D MARP
02 MCR 6441 D
03 MCR 6441 D
LHK 2
EFD 6888
HUNT 6888
EHT 6888
This seems to work fine from a dialplan perspective, however the first incoming call on 6441 always flashes the indicator on both key 02 and key 03, unlike the Norstar which would only indicate on key 02 unless there really were two concurrent starts on 6441... it hasn't been too much of an issue for helpdesk staff, but now the users at large would like the same facility and I'm worried we're going to be spending a lot of time trying to explain the phantom second call. The 'fix' would seem to be to create yet another DN (7441) and use it on key 03, but then what would the interaction with LHK be like? And how would we add a third appearance as 8441 is not available?
I can't believe CS1000/Succession would be less capable than lowly Norstar/MICS in this regard (one indicator per underlying call per TN for MCR keys).
Any suggestions?