Rfc 3261 compliance – SpectraLink i640 User Manual

Page 5

Advertising
background image

SpectraLink Corporation

SIP User Agent: Features and Standards

3. RFC 3261 Compliance

Feature

Supported?

Transport:

UDP

Yes

UDP retransmit timers

Yes

UDP multicast

No

TCP

Yes

TLS

No

IPv6

No

Fatal transport errs treated as 503

responses.

No, 30 second timeout instead.

Loop detection

No, From tag, callId, and Cseq match but no dialog match. – 482 resp.

Method processing:

Unsupported method response

Yes, 501

Include “Allow” with all INVITEs

Yes

Include “Supported” with all

INVITEs

Yes

Include “Accept” with all INVITEs

Yes

Forked calls per RFC 3264

Yes

405 response to recognized but

unsupported method.

No

OPTIONS method resp should have

Accept header.

Yes

INVITE keep alive if no final response

(resend provisional response).

No.

All requests can be challenged.

Partial, REGISTER and INVITE only can be challenged.

Header processing:

Compact forms

Yes

Repeated headers

Yes for Via, Contact, Record-Route, Route, Proxy-Authenticate. Not for

WWW-Authenticate.

Case sensitivity

Yes for quoted strings, tags

Case insensitivity

Yes for header names, methods, tokens, parameters.

Line wrapping

Yes

UTF8 char set

No, UTF8 strings are handled as identifiers, only US ASCII chars are

displayed.

Via header in all responses

Yes

Via header sentby in IP format

Yes

Ignore unsupported headers

Yes

Reject response with more than one

via header.

No

Allow whitespace in header parsing

Yes

Via header support maddr and ttl

No

URIs:

Name/Address forms

Yes

sips: forms

No

tel: forms

No

user=phone forms

No

Escape/unescape URIs as

parameters

Yes only for Refer-To: parameters.

Security:

User Authentication

Yes, Digest

Proxy Authentication

Yes, Digest credentials are not yet cached

Transport level security (TLS)

No

SIP Proxies:

Proxy discovery methods

No

Part Number: 72-1089-01-C.doc

Page 5

Advertising
This manual is related to the following products: