Advanced Operational Features
6-40
•
Checks to see if the incoming call is from a registered proxy server.
•
If the call is forwarded via a registered proxy server, then the message has already been
verified and authenticated by the server. The caller is part of the Trusted Network. The IP
phone UI displays the caller information contained in the PAI header.
•
If the call is not forwarded via a registered proxy server - and therefore is not a “Trusted
Entity” - the IP phone UI does not display any trust information contained in the PAI header.
Using the "
sip pai
" parameter, Administrators are able to select which URI field ("sip" or "tel")
the phone should use when displaying the PAI URI information. Valid options include:
0:
Disabled: PAI information is ignored.
1:
Use sip URI only: (Default) The phone will use the URI information contained in the "sip"
URI field (if available) and ignore the information contained in the "tel" URI field (if available).
2:
sip URI preferred: The phone will use the URI information contained in the "sip" URI field.
If the "sip" URI field is unavailable, the phone will use the URI information contained in the
"tel" URI field.
3:
Use tel URI only: The phone will use the URI information contained in the "tel" URI field (if
available) and ignore the information contained in the "sip" URI field (if available).
4:
tel URI preferred:
The phone will use the URI information contained in the "tel" URI field. If
the "tel" URI field is unavailable, the phone will use the URI information contained in the
"sip" URI field.
ENABLING/DISABLING P-ASSERTED IDENTITY (PAI)
Use the following procedure to enable/disable PAI.
For the specific parameter you can set in the configuration files, see Appendix A, the section,
CONFIGURABLE ROUTE HEADER IN SIP PACKET
The IP Phones support the following parameter:
•
sip remove route
This parameter enables or disables the addition of the Route header in a SIP packet. Enable
this parameter for outbound proxies that do not support Route headers.
Note:
The default value (i.e. "1") will be enforced if this parameter is defined with any
unsupported value.
CONFIGURATION FILES
Note:
When enabled this will break all support for SIP routing, so if some other device
in the network attempts to add itself to the route it will fail.
Summary of Contents for 6800 Series
Page 1: ...Mitel 6800 Series SIP Phones 58014473 REV02 RELEASE 4 2 0 SERVICE PACK 2 ADMINISTRATOR GUIDE ...
Page 22: ...Chapter 1 OVERVIEW ...
Page 53: ...Chapter 2 CONFIGURATION INTERFACE METHODS ...
Page 72: ...Chapter 3 ADMINISTRATOR OPTIONS ...
Page 154: ...Chapter 4 CONFIGURING NETWORK AND SESSION INITIATION PROTOCOL SIP FEATURES ...
Page 264: ...Chapter 5 CONFIGURING OPERATIONAL FEATURES ...
Page 590: ...Chapter 6 CONFIGURING ADVANCED OPERATIONAL FEATURES ...
Page 698: ...Chapter 7 ENCRYPTED FILES ON THE IP PHONE ...
Page 704: ...Chapter 8 UPGRADING THE FIRMWARE ...
Page 713: ...Chapter 9 TROUBLESHOOTING ...
Page 743: ...Appendix A CONFIGURATION PARAMETERS ...
Page 1065: ...Appendix B CONFIGURING THE IP PHONE AT THE ASTERISK IP PBX ...
Page 1069: ...Appendix C SAMPLE CONFIGURATION FILES ...
Page 1085: ...Appendix D SAMPLE BLF SOFTKEY SETTINGS ...
Page 1090: ...Appendix E SAMPLE MULTIPLE PROXY SERVER CONFIGURATION ...
Page 1094: ...Appendix F CERTIFICATE SUPPORT ...
Page 1113: ......