This method is the same as addBuddy(uri, duration, eventId, timeout)
except that the duration is defaulted to the default period defined in
the event package RFC (3600 seconds) and no event "id" parameter will be
included.
This method is the same as addBuddy(uri, duration, eventId, timeout)
except that the duration is defaulted to the default period defined in
the event package RFC (3600 seconds).
This method adds each of the given parameters, if not null, to the given
NOTIFY Request parameter which just contains the request line (created
from a string).
Asserts that the given SIP message contains at least one occurrence of
the specified header and that at least one occurrence of this header
contains the given value.
Asserts that the given SIP message contains at least one occurrence of
the specified header and that at least one occurrence of this header
contains the given value.
Asserts that the given SIP message contains no occurrence of the
specified header with the value given, or that there is no occurrence of
the header in the message.
Asserts that the given SIP message contains no occurrence of the
specified header with the value given, or that there is no occurrence of
the header in the message.
This method creates and returns to the caller the next SUBSCRIBE message
that would be sent out, so that the user can modify it before it gets
sent out (ie, to introduce errors - insert incorrect content, remove
content, etc.).
This method is the same as the basic disconnect() method except that it
allows the caller to specify a message body and/or additional JAIN-SIP
API message headers to add to or replace in the outbound message.
This method is the same as the basic disconnect() method except that it
allows the caller to specify a message body and/or additional message
headers to add to or replace in the outbound message without requiring
knowledge of the JAIN-SIP API.
The format() method can be used to obtain a human-readable string
containing the result of the last operation - either a successful
indication or all of the error information associated with the last
operation performed.
This method returns all the responses received on this subscription,
including any that required re-initiation of the subscription (ie,
authentication challenge).
The getErrorMessage() method returns a descriptive, human-readable string
indicating the cause of the problem encountered during the last operation
performed.
Returns the number of seconds left in the subscription, if active, or the
number of seconds that were remaining at the time the subscription was
terminated.
This method is the same as the basic initiateOutgoingCall() method except
that it allows the caller to specify a message body and/or additional
JAIN-SIP API message headers to add to or replace in the outbound
message.
This method is the same as the basic initiateOugoingCall() method except
that it allows the caller to specify a message body and/or additional
message headers to add to or replace in the outbound message without
requiring knowledge of the JAIN-SIP API.
This method is the same as the basic initiateOutgoingCall() method,
without the 'from URI' parameter which will be defaulted to the 'from'
address (me) specified when the SipPhone object was created
(SipStack.createSipPhone()).
This method is the same as the basic blocking makeCall() method except
that it allows the caller to specify a message body and/or additional
message headers to add to or replace in the outbound message without
requiring knowledge of the JAIN-SIP API.
This method is the same as the basic blocking makeCall() method except
that it allows the caller to specify a message body and/or additional
JAIN-SIP API message headers to add to or replace in the outbound INVITE
message.
This method is the same as the basic nonblocking makeCall() method except
that it allows the caller to specify a message body and/or additional
JAIN-SIP API message headers to add to or replace in the outbound INVITE
message.
This method is the same as the basic nonblocking makeCall() method except
that it allows the caller to specify a message body and/or additional
message headers to add to or replace in the outbound message without
requiring knowledge of the JAIN-SIP API.
This class represents a single Tuple element received in a NOTIFY SIP message -
it contains all information about a single active device associated with the
presentity (buddy, watchee).
This method validates the given (received) NOTIFY request, updates the
subscription information based on the NOTIFY contents, and creates and
returns the correctly formed response that should be sent back in reply
to the NOTIFY, based on the NOTIFY content that was received.
This method starts a thread that waits for up to 'timeout' milliseconds
to receive a SUBSCRIBE and if received, it sends a response with
'statusCode' and 'reasonPhrase' (if not null).
This method processes the initial SUBSCRIBE response received after
sending a SUBSCRIBE request and takes the SUBSCRIBE transaction to its
completion by collecting any remaining responses from the far end for
this transaction, handling authentication challenge if needed, and
updating the Subscription object with the results of the SUBSCRIBE
sequence.
This method is the same as refreshBuddy(uri, duration, eventId, timeout)
except that the SUBSCRIBE duration sent will be however much time is left
on the current subscription.
This method is the same as refreshBuddy(uri, duration, eventId, timeout)
except that the eventId remains unchanged from whatever it already was
and the SUBSCRIBE duration sent will be however much time is left on the
current subscription.
This method is the same as refreshBuddy(uri, duration, eventId, timeout)
except that instead of creating the SUBSCRIBE request from parameters
passed in, the provided request parameter is used for sending out the
SUBSCRIBE message.
This method removes a buddy from the buddy list and initiates a
SUBSCRIBE/NOTIFY sequence to terminate the subscription unless the
subscription is already terminated.
This method is the same as removeBuddy(uri, eventId, timeout) except that
instead of creating the SUBSCRIBE request from parameters passed in, the
provided request parameter is used for sending out the SUBSCRIBE message
if the subscription is active.
This method is equivalent to the basic respondToCancel() method except
that it allows the caller to specify a message body and/or additional
JAIN-SIP API message headers to add to or replace in the outbound
message.
This method is equivalent to the basic respondToCancel() method except
that it allows the caller to specify a message body and/or additional
JAIN-SIP API message headers to add to or replace in the outbound message
without requiring knowledge of the JAIN-SIP API.
This method is the same as the basic respondToDisconnect() method except
that it uses the given parameters for the status code and reason in the
response message sent out.
This method is the same as the basic respondToDisconnect() method except
that it uses the given parameters for the status code and reason in the
response message sent out and allows the caller to specify a message body
and/or additional JAIN-SIP API message headers to add to or replace in
the outbound message.
This method is the same as the basic respondToDisconnect() method except
that it uses the given parameters for the status code and reason in the
response message sent out and allows the caller to specify a message body
and/or additional message headers to add to or replace in the outbound
message without requiring knowledge of the JAIN-SIP API.
This method is the same as the basic respondToReinvite() plus it
additionally allows the caller to specify additional message headers to
add to or replace in the response message without requiring knowledge of
the JAIN-SIP API.
This method is equivalent to the basic respondToReinvite() method except
that it allows the caller to specify additional JAIN-SIP API message
headers to add to or replace in the outbound message.
This method is equivalent to the basic sendCancel() method except that it
allows the caller to specify a message body and/or additional JAIN-SIP
API message headers to add to or replace in the outbound message.
This method is equivalent to the basic sendCancel() method except that it
allows the caller to specify a message body and/or additional JAIN-SIP
API message headers to add to or replace in the outbound message without
requiring knowledge of the JAIN-SIP API.
This method is the same as the basic sendIncomingCallResponse() method
except that it allows the caller to specify a message body and/or
additional JAIN-SIP API message headers to add to or replace in the
outbound message.
This method is the same as the basic sendIncomingCallResponse() method
except that it allows the caller to specify a message body and/or
additional message headers to add to or replace in the outbound message
without requiring knowledge of the JAIN-SIP API.
This method is the same as the basic sendInviteOkAck() method except that
it allows the caller to specify a message body and/or additional JAIN-SIP
API message headers to add to or replace in the outbound message.
This method is the same as the basic sendInviteOkAck() method except that
it allows the caller to specify a message body and/or additional message
headers to add to or replace in the outbound message without requiring
knowledge of the JAIN-SIP API.
This method is equivalent to the basic sendReinvite() method except that
it allows the caller to specify additional JAIN-SIP API message headers
to add to or replace in the outbound message.
This method is the same as the basic sendReinvite() method except that it
allows the caller to specify additional message headers to add to or
replace in the outbound message without requiring knowledge of the
JAIN-SIP API.
This method is the same as the basic sendReinviteOkAck() method except
that it allows the caller to specify a message body and/or additional
JAIN-SIP API message headers to add to or replace in the outbound
message.
This method is the same as the basic sendReinviteOkAck() method except
that it allows the caller to specify a message body and/or additional
message headers to add to or replace in the outbound message without
requiring knowledge of the JAIN-SIP API.
This method is the same as the basic sendReply(RequestEvent, ...) method
except that it allows the caller to specify a message body and/or
additional JAIN-SIP API message headers to add to or replace in the
outbound message.
This method is the same as the basic sendReply(RequestEvent, ...) method
except that it allows the caller to specify a message body and/or
additional message headers to add to or replace in the outbound message,
without requiring knowledge of the JAIN-SIP API.
This method is the same as the basic sendReply(SipTransaction, ...)
method except that it allows the caller to specify a message body and/or
additional message headers to add to or replace in the outbound message,
without requiring knowledge of the JAIN-SIP API.
This method is the same as the basic sendReply(SipTransaction, ...)
method except that it allows the caller to specify a message body and/or
additional JAIN-SIP API message headers to add to or replace in the
outbound message.
This method is the same as the basic
sendRequestWithTransaction(String,...) method except that it allows the
caller to specify a message body and/or additional JAIN-SIP API message
headers to add to or replace in the outbound message.