StatusLine
RFC name: Status-Line Description: The first line of a response message. Does not correspond to a header proper but is accessed with the header interface in reSIP. Example: SIP/2.0 200 OK Parts: RFC Name accessor reSIP type settable -------------------------------------------------------------- Status-Code statusCode() int yes SIP-Version getSipVersion() Data no Reason-Phrase reason() Data yes
Auth
RFC name: challenge Description: Identifies the authentication scheme in a challenge response. Example: Digest-Authenticate: username="Alice", realm="atlanta.com", nonce="84a4cc6f3082121f32b42a2187831a9e", response="7587245234b3434cc3412213e5f113a5432" Parts: RFC Name accessor reSIP type settable ---------------------------------------------------------- auth-scheme scheme() Data yes
CSeqCategory
RFC name: CSeq Description: Places the message in sequence in the call. Example: CSeq: 314159 INVITE Parts: RFC Name accessor reSIP type settable -------------------------------------------------------------- sequence() int yes Method method() MethodTypes yes unknownMethodName() Data no
CallId
RFC name: Call-ID Description: Uniquely identifies the call. Example: Call-ID: a84b4c76e66710@pc33.atlanta.com Parts: RFC Name accessor reSIP type settable ---------------------------------------------------------- value() Data yes
DateCategory
RFC name: SIP-date Description: Human readable date string. Example: Date: Sat, 13 Nov 2010 23:29:00 GMT Parts: RFC Name accessor reSIP type settable ---------------------------------------------------------- wkday dayOfWeek() DayOfWeek yes date1 dayOfMonth int yes month() int yes year() int yes time hour() int yes minute() int yes second() int yes
GenericUri
RFC name: absoluteURI Description: Non-structured human readable URI. Example: Alert-Info: <http://www.example.com/sounds/moo.wav> Parts: RFC Name accessor reSIP type settable ---------------------------------------------------------- uri() Data yes
RFC Headers:
-
Alert-Info
-
Call-Info
-
Error-Info
ExpiresCategory
RFC name: expires Description: Seconds to expiration. Example: Expires: 5 Parts: RFC Name accessor reSIP type settable ---------------------------------------------------------- value() int yes
RFC Headers:
-
Expires
Mime
RFC name: media-type Description: Mime type and sub-type. Example: Content-Type: application/sdp Parts: RFC Name accessor reSIP type settable ---------------------------------------------------------- m-type type() Data yes m-subtype subType() Data yes
RFC Headers:
-
Accept multi-valued
-
Content-Type
NameAddr
RFC name: name-addr Description: URI and display name. Example: To: Bob <sip:bob@biloxi.com> Parts: RFC Name accessor reSIP type settable ---------------------------------------------------------- display-name displayName() Data yes addr-spec uri() Uri yes
RFC Headers:
-
Contact multi-valued
-
From
-
Record-Route multi-valued
-
Refer-To
-
Referred-By
-
Reply-To
-
Route multi-valued
-
To
StringCategory
RFC name: TEXT-UTF8-TRIM Description: Unstructured human readable text. Example: Organization: Boxes by Bob Parts: RFC Name accessor reSIP type settable ---------------------------------------------------------- value() Data yes
RFC Headers:
-
Content-Transfer-Encoding
-
Organization
-
Server
-
Subject
-
User-Agent
-
Timestamp
-
Extension Header multi-valued
Token
RFC name: token Description: A word. Example: Accept-Encoding: gzip Parts: RFC Name accessor reSIP type settable ---------------------------------------------------------- value() Data yes
RFC Headers:
-
Accept-Encoding multi-valued
-
Accept-Language multi-valued
-
Allow multi-valued
-
Allow-Events multi-valued
-
Content-Disposition
-
Content-Encoding
-
Content-Language multi-valued
-
Event
-
Mime-Version
-
Priority
-
Proxy-Require multi-valued
-
Require multi-valued
-
Security-Client multi-valued
-
Security-Server multi-valued
-
Security-Verify multi-valued
-
Subscription-State multi-valued
-
Supported multi-valued
-
Unsupported multi-valued