thread1329-1730030
UPDATE
For anyone interested, an easy solution to my earlier issue has been found that takes less than 5 minutes to implement. Credit to one of my co-workers
Issue, when secondary line keys programmed as phantoms are used as park keys they do not recall unless you use transfer.
You can use system forwarding after all.
[ul]
[li]The first destination of system forwarding will be itself[/li]
[li]the second destination will be the reception or ring group or whatever you want to designate. Second destination timer is configurable (System Forward Advance)[/li]
[li]For the system forwarding path you need to enable CO and intercom recall[/li]
[li]Each "Park" will of course need its own system forwarding path - see first step above[/li]
[/ul]
**********************************************
What's most important is that you realise ... There is no spoon.
UPDATE
For anyone interested, an easy solution to my earlier issue has been found that takes less than 5 minutes to implement. Credit to one of my co-workers
Issue, when secondary line keys programmed as phantoms are used as park keys they do not recall unless you use transfer.
You can use system forwarding after all.
[ul]
[li]The first destination of system forwarding will be itself[/li]
[li]the second destination will be the reception or ring group or whatever you want to designate. Second destination timer is configurable (System Forward Advance)[/li]
[li]For the system forwarding path you need to enable CO and intercom recall[/li]
[li]Each "Park" will of course need its own system forwarding path - see first step above[/li]
[/ul]
**********************************************
What's most important is that you realise ... There is no spoon.