THOMSON ST 2030 SIP, Administrator'S Manual

Page: 14 / 316

ST2030s VoIP Business Phone
ST2030s SIP Administrator Guide v3.0
Page 6 of 308
Phone set function support and Call Options:

Call hold, Call Transfer, Call Forward, Conference Call, Call Park and Call Pick-up.

On-hook dialing, Dial from call log, multi line (9 lines)

Redial, Mute, Call log, phone book (30 entries), 10 Speed dial memory keys

Hands free (full-duplex)
Supported Protocols
Your Thomson ST 2030 SIP Phone supports the following standard Internet protocols:

Internet Protocol (IP)
IP is a network layer protocol that sends datagram packets between nodes on the Internet.
IP also provides features for addressing, type-of-service (ToS) specification,
fragmentation and reassembly, and security.

User Datagram Protocol (UDP)
UDP is a simple protocol that exchanges data packets without acknowledgments or
guaranteed delivery. SIP can use UDP as the underlying transport protocol. If UDP is
used, retransmissions are used to ensure reliability.

Trivial File Transfer Protocol (TFTP)
TFTP allows files to be transferred from one computer to another over a network.

Dynamic Host Control Protocol (DHCP)
DHCP is used to dynamically allocate and assign IP addresses. DHCP allows you to
move network devices from one subnet to another without administrative attention. If
using DHCP, you can connect ST2030 IP phone to the network and become operational
without having to manually assign an IP address and additional network parameters.

Domain Name System (DNS)
DNS is used in the Internet for translating names of network nodes into addresses. Sip
uses DNS to resolve the host names of end points to IP addresses.

Hyper Text Transfer Protocol (HTTP)
HTTP is the underlying protocol used by the World Wide Web. It defines how messages
are formatted and transmitted, and what actions Web servers and browsers should take in
response to various commands.

Simple Network Time Protocol (SNTP)
SNTP is a simplified version of NTP. SNTP can be used when the ultimate performance
of the full NTP implementation described in RFC 1305 is not needed or justified
.