I have posted my "many adventures" with virtual DNs and VMIs to make a fax server compatible with a Norstar MICS. I would like to post an observation and wonder if others have noticed it as well:
A virtual DN will stop working if the DN is rung with Set Reloction turned on.
I setup a couple of spare sets and a dozen Answer DNs. I setup spare ports with the DN, created lines with Recv'd and PrimeSet, and punching a phone down temporarily while I setup call forwarding. The virtual DN would ring twice on the phone and then forward to my VMI.
I had to move a users phone, so I turned on Set Relocation for about half an hour. When I went back to my phone closet, I observed that the calls were no longer forwarding. The phone I had hung the virtual DNs on was just ringing and ringing. So I had to repunch down a phone and reset the call forwarding.
Since my company has gotten used to moving agents offices around during the middle of the day, Set Relocation is really a good thing. But "randomly" losing virtual DNs is not good.
(I had a "test" system under 5.0 and originally blamed this behaviour on 6.0. But I think that it is a problem with Set Relocation as I did not have the Set Relocation turned on when I was testing.)
A virtual DN will stop working if the DN is rung with Set Reloction turned on.
I setup a couple of spare sets and a dozen Answer DNs. I setup spare ports with the DN, created lines with Recv'd and PrimeSet, and punching a phone down temporarily while I setup call forwarding. The virtual DN would ring twice on the phone and then forward to my VMI.
I had to move a users phone, so I turned on Set Relocation for about half an hour. When I went back to my phone closet, I observed that the calls were no longer forwarding. The phone I had hung the virtual DNs on was just ringing and ringing. So I had to repunch down a phone and reset the call forwarding.
Since my company has gotten used to moving agents offices around during the middle of the day, Set Relocation is really a good thing. But "randomly" losing virtual DNs is not good.
(I had a "test" system under 5.0 and originally blamed this behaviour on 6.0. But I think that it is a problem with Set Relocation as I did not have the Set Relocation turned on when I was testing.)