|
NIST SIP Parser and Stack (v1.2) API | ||||||||||
PREV NEXT | FRAMES NO FRAMES |
Packages that use javax.sip.header | |
gov.nist.javax.sip | This is the root of the JAIN implementation of SIP. |
gov.nist.javax.sip.address | Implementation of the address package of the JAIN SIP API. |
gov.nist.javax.sip.header | Contains implementations of the SIP headers as defined in JAIN-SIP 1.1 and an implementation of the JAIN-SIP header factory. |
gov.nist.javax.sip.stack | This package contains the classes for building a SIP stack. |
javax.sip | This package contains the main interfaces that model the JAIN SIP architectute from both an application developer and a stack vendor view. |
javax.sip.address | This package contains interfaces that represent the Addressing components of the SIP protocol. |
javax.sip.header | This package contains all the headers interfaces supported by this specification. |
javax.sip.message |
Classes in javax.sip.header used by gov.nist.javax.sipCallIdHeader
|
The Call-ID header field uniquely identifies a particular invitation or all registrations of a particular client. |
Classes in javax.sip.header used by gov.nist.javax.sip.addressParameters
|
This interface defines methods for accessing generic parameters for Headers that contain generic parameter values. |
Classes in javax.sip.header used by gov.nist.javax.sip.headerAcceptEncodingHeader
|
This interface represents the Accept-Encoding request-header. AcceptHeader
|
This interface represents an Accept request-header. AcceptLanguageHeader
|
The Accept-Language header field is used in requests to indicate the preferred languages for reason phrases, session descriptions, or status responses carried as message bodies in the response. AlertInfoHeader
|
When present in an INVITE request, the Alert-Info header field specifies an alternative ring tone to the UAS. AllowEventsHeader
|
This interface represents the AllowEvents SIP header, as defined by RFC3265, this header is not part of RFC3261. AllowHeader
|
The Allow header field lists the set of methods supported by the User Agent generating the message. AuthenticationInfoHeader
|
The Authentication-Info header field provides for mutual authentication with HTTP Digest. AuthorizationHeader
|
The Authorization header is used when a user agent wishes to authenticate itself with a server - usually, but not necessarily, after receiving an UNAUTHORIZED Response - by including an AuthorizationHeader with the Request. CallIdHeader
|
The Call-ID header field uniquely identifies a particular invitation or all registrations of a particular client. CallInfoHeader
|
The Call-Info header field provides additional information about the caller or callee, depending on whether it is found in a request or response. ContactHeader
|
A Contact header field value provides a URI whose meaning depends on the type of request or response it is in. ContentDispositionHeader
|
The Content-Disposition header field describes how the message body or, for multipart messages, a message body part is to be interpreted by the UAC or UAS. ContentEncodingHeader
|
A ContentEncodingHeader is used as a modifier to the "media-type". ContentLanguageHeader
|
The Content-Language header field is used to indicate the language of the message body. ContentLengthHeader
|
The Content-Length header field indicates the size of the message-body, in decimal number of octets, sent to the recipient. ContentTypeHeader
|
The Content-Type header field indicates the media type of the message-body sent to the recipient. CSeqHeader
|
A CSeq header field in a request contains a single decimal sequence number and the request method. DateHeader
|
The Date header field reflects the time when the request or response is first sent. Encoding
|
This interface represents encoding methods for any header that contains an encoding value. ErrorInfoHeader
|
The Error-Info header field provides a pointer to additional information about the error status response. EventHeader
|
This interface represents the Event SIP header, as defined by RFC3265, this header is not part of RFC3261. ExpiresHeader
|
The Expires header field gives the relative time after which the message (or content) expires. ExtensionHeader
|
This interface represents an Extension SIP header that is not currently defined by JAIN SIP. FromHeader
|
The From header field indicates the logical identity of the initiator of the request, possibly the user's address-of-record. Header
|
This interface is the super interface of all SIP headers supported explicitly by JAIN SIP. HeaderAddress
|
This interface represents methods for manipulating Address object values for any header that contains a Address value. HeaderFactory
|
This interface provides factory methods that allow an application to create Header object from a particular implementation of JAIN SIP. InReplyToHeader
|
The In-Reply-To header field enumerates the Call-IDs that this call references or returns. MaxForwardsHeader
|
The Max-Forwards header field must be used with any SIP method to limit the number of proxies or gateways that can forward the request to the next downstream server. MediaType
|
This interface represents media type methods for any header that contain content type and content sub-type values. MimeVersionHeader
|
SIP messages MAY include a single MIME-Version general-header field to indicate what version of the MIME protocol was used to construct the message. MinExpiresHeader
|
The Min-Expires header field conveys the minimum refresh interval supported for soft-state elements managed by that server. OptionTag
|
This interface represents methods for manipulating OptionTags values for any header that contains an OptionTag value. OrganizationHeader
|
The OrganizationHeader conveys the name of the organization to which the entity issuing the Request or Response belongs. Parameters
|
This interface defines methods for accessing generic parameters for Headers that contain generic parameter values. PriorityHeader
|
The Priority header field indicates the urgency of the request as perceived by the client. ProxyAuthenticateHeader
|
A Proxy-Authenticate header field value contains an authentication challenge. ProxyAuthorizationHeader
|
The Proxy-Authorization header field allows the client to identify itself (or its user) to a proxy that requires authentication. ProxyRequireHeader
|
The Proxy-Require header field is used to indicate proxy-sensitive features that must be supported by the proxy. RAckHeader
|
This interface represents the RAck header, as defined by RFC3262, this header is not part of RFC3261. ReasonHeader
|
This interface represents the Reason header, as defined by RFC3326, this header is not part of RFC3261. RecordRouteHeader
|
The Record-Route header field is inserted by proxies in a request to force future requests in the dialog to be routed through the proxy. ReplyToHeader
|
The Reply-To header field contains a logical return URI that may be different from the From header field. RequireHeader
|
The Require header field is used by UACs to tell UASs about options that the UAC expects the UAS to support in order to process the request. RetryAfterHeader
|
The Retry-After header field identifies the time to retry the request after recipt of the response. RouteHeader
|
The Route header field is used to force routing for a request through the listed set of proxies. RSeqHeader
|
This interface represents the RSeq header, as defined by RFC3262, this header is not part of RFC3261. ServerHeader
|
The Server header field contains information about the software used by the UAS to handle the request. SubjectHeader
|
The Subject header field provides a summary or indicates the nature of the call, allowing call filtering without having to parse the session description. SubscriptionStateHeader
|
This interface represents the Subscription State header, as defined by RFC3265, this header is not part of RFC3261. SupportedHeader
|
The Supported header field enumerates all the extensions supported by the UAC or UAS. TimeStampHeader
|
The Timestamp header field describes when the UAC sent the request to the UAS. ToHeader
|
The To header field first and foremost specifies the desired "logical" recipient of the request, or the address-of-record of the user or resource that is the target of this request. UnsupportedHeader
|
The Unsupported header field lists the features not supported by the UAS. UserAgentHeader
|
The User-Agent header field contains information about the UAC originating the request. ViaHeader
|
The Via header field indicates the transport used for the transaction and identifies the location where the response is to be sent. WarningHeader
|
The Warning header field is used to carry additional information about the status of a response. WWWAuthenticateHeader
|
This interface represents the WWW-Authenticate response-header. |
Classes in javax.sip.header used by gov.nist.javax.sip.stackCallIdHeader
|
The Call-ID header field uniquely identifies a particular invitation or all registrations of a particular client. |
Classes in javax.sip.header used by javax.sipCallIdHeader
|
The Call-ID header field uniquely identifies a particular invitation or all registrations of a particular client. HeaderFactory
|
This interface provides factory methods that allow an application to create Header object from a particular implementation of JAIN SIP. |
Classes in javax.sip.header used by javax.sip.addressParameters
|
This interface defines methods for accessing generic parameters for Headers that contain generic parameter values. |
Classes in javax.sip.header used by javax.sip.headerAcceptEncodingHeader
|
This interface represents the Accept-Encoding request-header. AcceptHeader
|
This interface represents an Accept request-header. AcceptLanguageHeader
|
The Accept-Language header field is used in requests to indicate the preferred languages for reason phrases, session descriptions, or status responses carried as message bodies in the response. AlertInfoHeader
|
When present in an INVITE request, the Alert-Info header field specifies an alternative ring tone to the UAS. AllowEventsHeader
|
This interface represents the AllowEvents SIP header, as defined by RFC3265, this header is not part of RFC3261. AllowHeader
|
The Allow header field lists the set of methods supported by the User Agent generating the message. AuthenticationInfoHeader
|
The Authentication-Info header field provides for mutual authentication with HTTP Digest. AuthorizationHeader
|
The Authorization header is used when a user agent wishes to authenticate itself with a server - usually, but not necessarily, after receiving an UNAUTHORIZED Response - by including an AuthorizationHeader with the Request. CallIdHeader
|
The Call-ID header field uniquely identifies a particular invitation or all registrations of a particular client. CallInfoHeader
|
The Call-Info header field provides additional information about the caller or callee, depending on whether it is found in a request or response. ContactHeader
|
A Contact header field value provides a URI whose meaning depends on the type of request or response it is in. ContentDispositionHeader
|
The Content-Disposition header field describes how the message body or, for multipart messages, a message body part is to be interpreted by the UAC or UAS. ContentEncodingHeader
|
A ContentEncodingHeader is used as a modifier to the "media-type". ContentLanguageHeader
|
The Content-Language header field is used to indicate the language of the message body. ContentLengthHeader
|
The Content-Length header field indicates the size of the message-body, in decimal number of octets, sent to the recipient. ContentTypeHeader
|
The Content-Type header field indicates the media type of the message-body sent to the recipient. CSeqHeader
|
A CSeq header field in a request contains a single decimal sequence number and the request method. DateHeader
|
The Date header field reflects the time when the request or response is first sent. Encoding
|
This interface represents encoding methods for any header that contains an encoding value. ErrorInfoHeader
|
The Error-Info header field provides a pointer to additional information about the error status response. EventHeader
|
This interface represents the Event SIP header, as defined by RFC3265, this header is not part of RFC3261. ExpiresHeader
|
The Expires header field gives the relative time after which the message (or content) expires. FromHeader
|
The From header field indicates the logical identity of the initiator of the request, possibly the user's address-of-record. Header
|
This interface is the super interface of all SIP headers supported explicitly by JAIN SIP. HeaderAddress
|
This interface represents methods for manipulating Address object values for any header that contains a Address value. InReplyToHeader
|
The In-Reply-To header field enumerates the Call-IDs that this call references or returns. MaxForwardsHeader
|
The Max-Forwards header field must be used with any SIP method to limit the number of proxies or gateways that can forward the request to the next downstream server. MediaType
|
This interface represents media type methods for any header that contain content type and content sub-type values. MimeVersionHeader
|
SIP messages MAY include a single MIME-Version general-header field to indicate what version of the MIME protocol was used to construct the message. MinExpiresHeader
|
The Min-Expires header field conveys the minimum refresh interval supported for soft-state elements managed by that server. OptionTag
|
This interface represents methods for manipulating OptionTags values for any header that contains an OptionTag value. OrganizationHeader
|
The OrganizationHeader conveys the name of the organization to which the entity issuing the Request or Response belongs. Parameters
|
This interface defines methods for accessing generic parameters for Headers that contain generic parameter values. PriorityHeader
|
The Priority header field indicates the urgency of the request as perceived by the client. ProxyAuthenticateHeader
|
A Proxy-Authenticate header field value contains an authentication challenge. ProxyAuthorizationHeader
|
The Proxy-Authorization header field allows the client to identify itself (or its user) to a proxy that requires authentication. ProxyRequireHeader
|
The Proxy-Require header field is used to indicate proxy-sensitive features that must be supported by the proxy. RAckHeader
|
This interface represents the RAck header, as defined by RFC3262, this header is not part of RFC3261. ReasonHeader
|
This interface represents the Reason header, as defined by RFC3326, this header is not part of RFC3261. RecordRouteHeader
|
The Record-Route header field is inserted by proxies in a request to force future requests in the dialog to be routed through the proxy. ReplyToHeader
|
The Reply-To header field contains a logical return URI that may be different from the From header field. RequireHeader
|
The Require header field is used by UACs to tell UASs about options that the UAC expects the UAS to support in order to process the request. RetryAfterHeader
|
The Retry-After header field identifies the time to retry the request after recipt of the response. RouteHeader
|
The Route header field is used to force routing for a request through the listed set of proxies. RSeqHeader
|
This interface represents the RSeq header, as defined by RFC3262, this header is not part of RFC3261. ServerHeader
|
The Server header field contains information about the software used by the UAS to handle the request. SubjectHeader
|
The Subject header field provides a summary or indicates the nature of the call, allowing call filtering without having to parse the session description. SubscriptionStateHeader
|
This interface represents the Subscription State header, as defined by RFC3265, this header is not part of RFC3261. SupportedHeader
|
The Supported header field enumerates all the extensions supported by the UAC or UAS. TimeStampHeader
|
The Timestamp header field describes when the UAC sent the request to the UAS. ToHeader
|
The To header field first and foremost specifies the desired "logical" recipient of the request, or the address-of-record of the user or resource that is the target of this request. TooManyHopsException
|
This Exception is thrown when a user attempts decrement the Hop count when the message as already reached its max number of forwards. UnsupportedHeader
|
The Unsupported header field lists the features not supported by the UAS. UserAgentHeader
|
The User-Agent header field contains information about the UAC originating the request. ViaHeader
|
The Via header field indicates the transport used for the transaction and identifies the location where the response is to be sent. WarningHeader
|
The Warning header field is used to carry additional information about the status of a response. WWWAuthenticateHeader
|
This interface represents the WWW-Authenticate response-header. |
Classes in javax.sip.header used by javax.sip.messageCallIdHeader
|
The Call-ID header field uniquely identifies a particular invitation or all registrations of a particular client. ContentDispositionHeader
|
The Content-Disposition header field describes how the message body or, for multipart messages, a message body part is to be interpreted by the UAC or UAS. ContentEncodingHeader
|
A ContentEncodingHeader is used as a modifier to the "media-type". ContentLanguageHeader
|
The Content-Language header field is used to indicate the language of the message body. ContentLengthHeader
|
The Content-Length header field indicates the size of the message-body, in decimal number of octets, sent to the recipient. ContentTypeHeader
|
The Content-Type header field indicates the media type of the message-body sent to the recipient. CSeqHeader
|
A CSeq header field in a request contains a single decimal sequence number and the request method. ExpiresHeader
|
The Expires header field gives the relative time after which the message (or content) expires. FromHeader
|
The From header field indicates the logical identity of the initiator of the request, possibly the user's address-of-record. Header
|
This interface is the super interface of all SIP headers supported explicitly by JAIN SIP. MaxForwardsHeader
|
The Max-Forwards header field must be used with any SIP method to limit the number of proxies or gateways that can forward the request to the next downstream server. ToHeader
|
The To header field first and foremost specifies the desired "logical" recipient of the request, or the address-of-record of the user or resource that is the target of this request. |
|
NIST SIP Parser and Stack (v1.2) API | ||||||||||
PREV NEXT | FRAMES NO FRAMES |