New Features in Release 2.5.3
4
RN-001029-04, Release 2.5.3, Rev 05
IP Phone Release Notes 2.5.3
New Features in Release 2.5.3
This section provides the new features in SIP IP Phone Release 2.5.3. These new features apply
to all of the Aastra IP Phones, unless specifically stated otherwise. Each feature also specifies
whether it affects the Administrator, the User, or both.
New Parameter for Configurable 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.
A new parameter, “
sip contact matching
”, now 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.
Configuring the Contact Header Matching
Feature
Description
Configuration
New Parameter for Configurable
Contact Header Matching
(Administrator)
An Administrator can now specify whether or not to use strict SIP contact header
matching on the IP Phones using the following new parameter in the configuration
files:
sip contact matching
.
Configuration Features
Parameter
–
sip contact matching
Configuration Files
aastra.cfg, <mac>.cfg
Description
Specifies the method for which the phone uses to match the Contact
header in a SIP registration packet.
Format
Integer
Default Value
0
Range
0
(default) URI matching of username, domain name, port, and
transport
1
matching of port only
2
matching of username only
3
matching of port and username only
Example
sip contact matching: 1
