Operational Features
41-001343-02 REV05 – 07.2014
5-226
SIP Phone Diversion Display
When an outgoing call is being diverted to another destination (i.e. via call forward), the phone displays the Caller ID
(phone number and/or caller name) of the new destination and the reason for the call diversion. Similarly, at the new des-
tination, the Caller ID of the original call destination displays.
Call Diversion Example
You can enable or disable this feature on a global or per-line basis using the configuration files only.
Configuring SIP Diversion Display on the Phone
Use the following procedures to configure SIP diversion display on the IP phones
.
Limitations
•
The diversion header assumes that the ID of the 'diverted' caller is passed in a URI style manner.
•
This feature relies on the server supporting and generating the Diversion header; the phone does not generate the
header itself.
•
Diversion header parameters such as counter, limit, privacy, screen, and extension are not recognized or supported by
the phone. However, they are still passed along during the diversion process.
Display Name Customization
By default, if the IP phone receives an incoming call and the number of the incoming call matches an entry in the local
directory, the IP phone will display the information stored in the local directory instead of the display name of the INVITE.
The “
directory lookup suppression pattern
” allows for the customization of the name displayed on the IP phone’s screen
and suppression of the local directory lookup.
This parameter is useful in such cases where a call manager will intentionally modify the display name according to a spe-
cific scenario. For example, if a Manager forwards an incoming call to an employee, the call manager may modify the dis-
play name to state “--> [Manager’s Name] Caller’s Name”. With the “
directory lookup suppression pattern
” parameter
configured for “-->” pattern matching, the IP phone will bypass the local directory lookup and the phone’s screen will dis-
play the call as intended by the call manager.
1.
Tim calls Mark at x400.
2.
Mark’s phone is busy.
3.
Mark’s phone diverts the incoming call to another destination (Roger @ x 464).
4.
Tim’s phone displays name and extension of where the call is being diverted to and reason for diverting the call.
5.
Roger’s phone accepts the call and displays the name and number of the incoming call (Tim) and the name (or number)
of the original destination (Mark).
Note:
If proxy servers exist in the network, it is possible that multiple diversions can take place on the phones. When multiple
diversion headers are returned in a single 302 response back to the originating phone, the phone that originated the
call (i.e., Tim’s phone in the above example) displays the URI of the newest (first encountered) Diversion header, but dis-
plays the REASON of the oldest (last encountered) Diversion Header. The phone that receives the diverted call (i.e.,
Roger’s phone in example above) displays the information of the oldest diverted call (last encountered).
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section,
.
