Technical specifications, Call control capability, Echnical – ATL Telecom IP300S User Manual

Page 7: Pecifications, Ontrol, Apability

Advertising
background image

IP SIP Phone v2 User’s Guide

Mar. 2005

[7/100]

z Regular alarm and one-time alarm.
z Prompt user on call diversion for better security support (Configurable)
z Menu driven configuration by keypad, Web browser or TELNET.
z Use of Simple Network Time Protocol (SNTP) to synchronize time with network time server

and adjust to time-zone (configurable) and daylight saving time (configurable).

z Use of Trivial File Transport Protocol (TFTP) and HTTP for auto-provisioning and image

update

z IEEE 802.1Q VLAN tagging support
z Support both 802.1P link layer precedence bits and IP layer type-of-service (ToS) bits for

voice streaming, such that IP SIP Phone would perfectly replace your desktop analog phone
within a switched network.

z SNMPv2 for network management and supervision.
z Call-related statistics, including total inbound/outbound calls, average conversation duration,

connected ratio of the last 50 calls, and the conversation time distribution (less than 3
minutes, 3-20 minutes and longer than 20 minutes) during the last 72 hours, or since system
startup.

1.2. Technical Specifications

1.2.1. Call Control Capability

z Fully complies with RFC 3261 (SIP) with RFC 2543 backward compatible.
z Fully complies with RFC 2327 (SDP) and RFC 3264 for capability negotiation based on SDP

offer and answer model.

z Multiple Outbound Proxy, Registrar and Redirect server support, up to 3 different service

domains.

z Support SIP server authentication procedure (HTTP digest authentication scheme)
z On-demand registration and re-registration on network configuration changed (auto-detect

the changed IP of host, NAT, Dynamic DNS)

z Auto-locating SIP server (RFC 3263) by DNS NAPTR/SRV record (RFC 2782) lookup
z Supports SIP multicast registration to 224.0.1.75
z Call Transfer (RFC3515 for REFER method, RFC3420 for sipfrag support, RFC3891 for

replaces header and RFC3892 for Referred-by header).

z Message waiting indication, MWI, (RFC 3842).
z Fully Implementation of RFC 2916 (E.164 and DNS) for ENUM translation by NAPTR

(RFC 2915)

z Configurable SIP signaling port (default 5060), support both UDP and TCP.
z Support rport and received in VIA header (RFC3581) (Configurable)
z Redundancy SIP proxy server support by DNS NAPTR/SRV/AAAA records.

Advertising