4-74
41-001343-01 Rev 02, Release 3.2.2
Contact Header Matching
When sending SIP packets, the IP Phones observe the Contact header by matching the username,
domain name, port, and transport per SIP RFC 3261.This is called “strict SIP Contact header
matching.” However, in specific networks (such as behind some SOHO routers), the phone
registers with its private address in the Contact, but when the response is sent back, the router
maintains the public side IP address in the Contact header. This causes a non-matching Contact
header and the phone does not accept the new registration expiry timer.
You can set the parameter, “
sip contact matching
”, which allows the Administrator to specify
the method used by the phone to match the Contact Header. This parameter is available via the
configuration files only.
Enabling/Disabling the “Contact Header Matching” Feature
Use the following procedure to enable/disable the “Contact Header Matching” feature.
Configuring Basic SIP Authentication Settings
You can configure SIP authentication settings using the configuration files, the IP Phone UI, or
the Aastra Web UI.
Reference
For more information about setting the call waiting parameters, see Chapter 5, the section,
“Call
Waiting”
on
page 5-71
. Call Waiting cannot be set via the IP Phone UI.
Configuration Files
For the specific parameter you can set in the configuration files, see Appendix A, the section,
“Contact
Header Matching”
on
page A-72.
Note:
To configure the SIP settings per-line, use the configuration files or
the Aastra Web UI.
Configuration Files
For specific parameters you can set in the configuration files, see Appendix A, the section,
“SIP Basic,
Global Settings”
on
page A-73
or
“SIP Basic, Per-Line Settings”
on
page A-83.
For specific parameters you
can set in the configuration files for call waiting, see the section,
“Call Waiting Settings”
on
page A-76
or
“SIP
Per-Line Call Waiting Setting”
on
page A-88
.
Note:
You can set global configuration only using the IP Phone UI.