TANDBERG 880 MXP - Manual (Page 219)

General Use
205
Server Address: <text field>
Examples:
“sipserver.example.com”
“sipserver.example.com:5060”
“10.0.0.2”
“10.0.0.2:5061”
Authentication
User Name
This is the user name part of the credentials used to authenticate toward the SIP Server.
User name: <text field>
Password
This is the password part of the credentials used to authenticate toward the SIP Server.
Password: <text field>
Server Type
Available servers are: Auto, Nortel, Microsoft and Experimental.
Current RFC’s and Drafts supported:
ƒ RFC 3261 SIP: Session Initiation Protocol
ƒ RFC 3581 An Extension to the Session Initiation Protocol (SIP) for Symmetric Response
Routing
ƒ RFC 2327 SDP: Session Description Protocol
ƒ RFC 3264 An Offer/Answer Model with the Session Description Protocol (SDP)
ƒ RFC 3263: Session Initiation Protocol (SIP): Locating SIP Servers - No support for
NAPTR records.
ƒ RFC 3311 The Session Initiation Protocol (SIP) UPDATE Method
ƒ RFC 2976 SIP INFO Method
ƒ Draft-levin-mmusic-xml-media-control-03.txt - Used for video fast picture update
requests
ƒ RFC 3361 Dynamic Host Configuration Protocol (DHCP-for-IPv4) Option for Session
Initiation Protocol (SIP) Servers
ƒ RFC 3550 RTP: A Transport Protocol for Real-Time Applications
ƒ RFC 2032 RTP Payload Format for H.261 Video Streams
ƒ Draft-ietf-avt-rfc2032-bis-06.txt - Draft for advanced video signaling including
resolution and mpi.
ƒ RFC 2190 RTP Payload Format for H.263 Video Streams
ƒ RFC 2429 RTP Payload Format for the 1998 Version of ITU-T Rec. H.263 Video
(H.263+)