1. Call Scenarios / Call-Flows
Typical and special scenarios and their configuration
FonComfort - Comfort and ease for handling Lync calls

2. FonComfort Call Forwarding and Lync Call Forwarding
Difference between FonComfort and Lync Call Forwarding:
FC Call Forwarding must be used if one of these requirements have to be fulfilled:
Cascading of call forwarding in any case, including RGS calls and forwarded calls
Manager wants to forward all calls except calls from a defined exception list
FC Call Forwarding works AFTER Lync call routing (after RGS distribution)
Configuration options:
Centrally by Administrator via Settings Program or FonComfort Powershell extension (new in FC server 2.0)
Individually by each user via FonComfort Professional „Properties“ window
Team assistants or power users via QuickLink application (with appropriate rights)
FonComfort - Comfort and ease for handling Lync calls

3. Example Call-Flow (manager/assistant scenario 1)
Standard call flow for managers:
Forward all calls with exception of assistant team, other managers and home numbers
Configuration for Manager:
Define exceptions within the properties menu of FonComfort Pro: add telephone numbers always in E.164 (with „+“ < country code>)
Configure call forwarding destination in FC Pro
FonComfort - Comfort and ease for handling Lync calls

4. Example Call-Flow (manager/assistant scenario 2)
Required call flow:
Incoming call to a manager should be forwarded immediately to his/her personal assistant without ringing the manager’s phone first.
If the personal assistant is not available, forward to 2nd assistant.
If the 2nd assistant is not available, forward to voic of personal assistant (instead of manager, like Lync does!)
Solution:
Manager configuration:
FonComfort call forwarding to personal assistant
Personal assistant configuration:
Lync simultaneous ring for team group and add assistant 2 to the team group with a delay of, say 15 s
Unanswered calls will got to Voice mail with a delay of e.g. 30 s.
FonComfort - Comfort and ease for handling Lync calls

5. Example Call-Flow (manager/assistant scenario 3)
Required call flow:
Like Scenario 2, but additionally:
Personal calls to the personal assistant shall not overflow to assistant 2!
Solution:
Use of additional “Dynamic Routing” server extension
Manager configuration:
FonComfort call forwarding to a special application endpoint (e.g. “Manager1 Route point (RP1)”).
Personal assistant configuration:
Any configuration according to her personal preferences
Dynamic Routing configuration (via SQL table):
forward calls to assistant1 if available,
if not to assistant 2 if available,
if not to voic of assistant 1
This logic will be valid only for manager 1, other managers would need modified copies of this call flow, i.e. copies of routing point tables).
FonComfort - Comfort and ease for handling Lync calls

6. FonComfort and Lync Simultaneous Ringing
Difference between FonComfort and Lync Simultaneous Ringing :
FC Simultaneous Ringing must be used if one of these requirements have to be fulfilled:
Combination with Busy on busy or forwarding on busy
Multiple Simulring destinations needed (new in FC server 2.0)
Simulring setting must be independent on Lync client setting
Users should not change simulring configuration (in this case FC Pro must not be installed)
FC Simultaneous Ringing works BEFORE Lync call routing
FC Simultaneous Ringing may be used in combination with Lync call forwarding
FC Simultaneous Ringing may be used in combination with FC call forwarding (new in FC Server 2.0)
Lync SimulRing supports delayed call forking, FC not (yet)
Configuration options:
Centrally by Administrator via Settings Program or FonComfort Powershell extension (new in FC server 2.0)
Individually by each user via FonComfort Professional „Properties“ window
Team assistants or power users via QuickLink application (with appropriate rights)
FonComfort - Comfort and ease for handling Lync calls