Mitel 6800 Series, Administrator'S Manual, Page: 516 / 1113

Mitel 6800 Series SIP Phone Release 4.2.0 SP2 Administrator Guide
5-253
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).
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
.
For specific parameters you can set in the configuration files, see Appendix A, the section,
“SIP
Diversion Display”
on
page A-193
.
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 directory, the IP phone will display the information stored in the 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 directory
lookup.
This parameter is useful in such cases where a call manager will intentionally modify the display
name according to a specific scenario. For example, if a Manager forwards an incoming call
to an employee, the call manager may modify the display 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 directory lookup and the phone’s screen
will display the call as intended by the call manager.
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 displays 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