Here is an overview of CFW, showing how it is not MARP dependent, and how some DNs simply cannot be CFW'd unless they are reconfigured on the set. For this "tip" I have two example TNs:
TN 01
HUNT VOICEMAIL
KEY 3 CFW
KEY 2 6789 MARP
KEY 1 2201
KEY 0 1100 MARP
TN 02
HUNT RECEPTION
KEY 3 CFW
KEY 2 1100
KEY 1 2201 MARP
KEY 0 6789
In the above example:
If you CFW TN 1, only 1100 will be affected. 2201 and 6789 will not be affected
If you CFW TN 2, only 6789 will be affected, even though it is MARP'd on TN 1
Even if you CFW TN 1 and TN 2, 2201 will not be affected.
To CFW a DN, it must meet one of these conditions:
1. it is KEY 00 (or the DN if a 500 set is CFWing) and may appear on other phones.
or
2. it is not KEY 00 but has only one appearance in the system, that being the TN that wants to forward it.
PS: Sorry to "flood". Previous, similar posts will hopefully be deleted.
~~~
[small]GHTROUT.com | CS1000 Programming and Feature Guides | Tek-Tips FAQs | Recent Replies[/small]
TN 01
HUNT VOICEMAIL
KEY 3 CFW
KEY 2 6789 MARP
KEY 1 2201
KEY 0 1100 MARP
TN 02
HUNT RECEPTION
KEY 3 CFW
KEY 2 1100
KEY 1 2201 MARP
KEY 0 6789
In the above example:
If you CFW TN 1, only 1100 will be affected. 2201 and 6789 will not be affected
If you CFW TN 2, only 6789 will be affected, even though it is MARP'd on TN 1
Even if you CFW TN 1 and TN 2, 2201 will not be affected.
To CFW a DN, it must meet one of these conditions:
1. it is KEY 00 (or the DN if a 500 set is CFWing) and may appear on other phones.
or
2. it is not KEY 00 but has only one appearance in the system, that being the TN that wants to forward it.
PS: Sorry to "flood". Previous, similar posts will hopefully be deleted.
~~~
[small]GHTROUT.com | CS1000 Programming and Feature Guides | Tek-Tips FAQs | Recent Replies[/small]