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, there are two example TNs:
TN 01 | TN 02 |
HUNT VOICEMAIL | HUNT RECEPTION |
KEY 3 CFW | KEY 3 CFW |
KEY 2 6789 MARP | KEY 2 1100 |
KEY 1 2201 | KEY 1 2201 MARP |
KEY 0 1100 MARP | KEY 0 6789 |
In the above example:
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.
Here is another example:
TN 03 | TN 04 |
HUNT VOICEMAIL | HUNT RECEPTION |
KEY 3 CFW | KEY 3 CFW |
KEY 2 3511 MARP | KEY 2 5544 |
KEY 1 1654 | KEY 1 1654 MARP |
KEY 0 5544 MARP | KEY 0 1233 MARP |
In the above example:
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.
What if all you want to do is STOP a DN from being Call Forwarded?
Link to this page: http://www.ghtrout.net/rdr/cfw.html