Spectralink 84-Series Series Wireless Telephones Administration Guide
1725-86984-000_P.docx
September 2016
219
Parameter
Permitted Values
log.sched.x.startDay
0 to 7
When startMode is
abs
, specifies the day of the week to start command execution. 1=Sun, 2=Mon, ..., 7=Sat
log.sched.x.startMode
abs, rel
Start at an
abs
olute time or
rel
ative to boot.
log.sched.x.startTime
positive integer OR hh:mm
Seconds since boot when startMode is
rel
or the start time in 24-hour clock format when startMode is
abs
.
Microsoft Skype for Business Integration
See the Microsoft Interoperability Guides for Microsoft Skype for Business or Microsoft Lync
Server 2013 or 2010. for complete information.
Network Address Translation (NAT)
The handset can work with certain types of network address translation (NAT). NAT enables a
local area network (LAN) to use one set of IP addresses for internal traffic and another set for
external traffic. The handset
’s signaling and Real-Time Transport Protocol (RTP) traffic use
symmetric ports. You can configure the external IP
address
and ports used by the NAT on the
handset
’s behalf on a per-handset basis. Note that the source port in transmitted packets is the
same as the associated listening port used to receive packets.
These parameters define port and IP address changes used in NAT traversal. The port changes
will change the port used by the handset, while the IP entry simply changes the IP advertised in
the SIP signaling. This allows the use of simple NAT devices that can redirect traffic, but does
not allow for port mapping. For example, port 5432 on the NAT device can be sent to port 5432
on an internal device, but not to port 1234.
Table 10-12: Network Access Translation
Parameter
Permitted Values
Default
nat.ip
1
dotted- decimal IP address
Null
IP address to advertise within SIP signaling - should match the external IP address used by the NAT device.
nat.keepalive.interval
0 to 3600
0
The keep-alive interval in seconds. Sets the interval for handsets to send a keep-alive packet to the gateway/NAT
device to keep the communication port open so that NAT can continue to function. If Null or 0, the handset will not
send out keep-alive messages.
The Microsoft Live Communications Server 2005 keep-alive feature will overrule this parameter. If you want to
deploy handsets behind a NAT and connect them to Live Communications Server, the keep-alive interval received
from the Live Communications Server must be short enough to keep the NAT port open. Once the TCP connection
is closed, the handsets stop sending keep-alive packets.
nat.mediaPortStart
1
0 to 65440
0
The initially allocated RTP port. Overrules the value set for
tcIpApp.port.rtp.mediaPortRangeStart
.
