AASTRA 480i Manual Do Utilizador
Administrator Level Options
41-001129-00 Rev 09, Release 1.4.1
3-17
Administrator Options
Administrator Options
•
Explicit MWI Subscription
If the IP phone has a message waiting subscription with the Service Provider,
a Message Waiting Indicator (MWI) (LED or display icon) tells the user there
is a message on the IP Phone. You can enable and disable MWI by setting this
parameter to 0 (disable) or 1 (enable) in the configuration files or by checking
the box for this field in the Aastra Web UI. Default is disabled.
If the IP phone has a message waiting subscription with the Service Provider,
a Message Waiting Indicator (MWI) (LED or display icon) tells the user there
is a message on the IP Phone. You can enable and disable MWI by setting this
parameter to 0 (disable) or 1 (enable) in the configuration files or by checking
the box for this field in the Aastra Web UI. Default is disabled.
•
Send MAC Address in REGISTER Message
Adds an "Aastra-Mac:" header to the SIP REGISTER messages sent from the
phone to the call server, where the value is the MAC address of the phone.
Adds an "Aastra-Mac:" header to the SIP REGISTER messages sent from the
phone to the call server, where the value is the MAC address of the phone.
•
Send Line Number in REGISTER Message
Adds an "Aastra-Line:" header to the SIP REGISTER messages sent from the
phone to the call server, where the value is the line number that is being
registered.
Adds an "Aastra-Line:" header to the SIP REGISTER messages sent from the
phone to the call server, where the value is the line number that is being
registered.
•
Session Timer
The time, in seconds, that the IP phone uses to send periodic re-INVITE
requests to keep a session alive. The proxy uses these re-INVITE requests to
maintain the status' of the connected sessions. See RFC4028 for details.
Default is 0.
The time, in seconds, that the IP phone uses to send periodic re-INVITE
requests to keep a session alive. The proxy uses these re-INVITE requests to
maintain the status' of the connected sessions. See RFC4028 for details.
Default is 0.
•
Timer 1 and Timer 2
The time, in milliseconds, that applies to an IP phone session. These timers
are SIP transaction layer timers defined in RFC 3261. Timer 1 is an estimate
of the round-trip time (RTT). Timer 2 represents the amount of time a
non-INVITE server transaction takes to respond to a request.
The time, in milliseconds, that applies to an IP phone session. These timers
are SIP transaction layer timers defined in RFC 3261. Timer 1 is an estimate
of the round-trip time (RTT). Timer 2 represents the amount of time a
non-INVITE server transaction takes to respond to a request.
•
Transaction timer
The amount of time, in
milliseconds that the phone allows the callserver (registrar/proxy) to respond
to SIP messages that it sends. If the phone does not receive a response in the
amount of time designated for this parameter, the phone assumes the message
has timed out. Valid values are 4000 to 64000. Default is 4000.
The amount of time, in
milliseconds that the phone allows the callserver (registrar/proxy) to respond
to SIP messages that it sends. If the phone does not receive a response in the
amount of time designated for this parameter, the phone assumes the message
has timed out. Valid values are 4000 to 64000. Default is 4000.
•
Transport Protocol
The protocol that the RTP port on the IP phone uses to send out RTP packets.
Valid values are 0 (both), 1 (UDP), or 2 (TCP). Default is 1 (UDP).
The protocol that the RTP port on the IP phone uses to send out RTP packets.
Valid values are 0 (both), 1 (UDP), or 2 (TCP). Default is 1 (UDP).
•
Registration Retry Timer
Specifies the time, in seconds, that the phone waits between registration
attempts when a registration is rejected by the registrar.
Specifies the time, in seconds, that the phone waits between registration
attempts when a registration is rejected by the registrar.