requestData or callback.
@param requestData the data to send as part of the request
@param callback the response handler to be notified when the request failsor completes
@return a {@link Request} object that can be used to track the request
@throws NullPointerException if callback null
null for this Connection, no number will be assigned. By default, the {@link ie.omk.smpp.util.DefaultSequenceScheme}class is used to assign sequence numbers to packets. bind and unbind methods to carry out those operations. Attempting to send an bind or unbind packet using this method will result in an UnsupportedOperationException being thrown.
@param request The request packet to send to the SMSC
@return The response packet returned by the SMSC, or null if asynchronouscommunication is being used.
@throws java.lang.NullPointerException if r is null.
@throws java.net.SocketTimeoutException If a socket timeout occurs while waiting for a response packet. (Only in synchronized mode).
@throws java.io.IOException If an I/O error occurs while writing the request packet to the network connection.
@throws ie.omk.smpp.UnsupportedOperationException If this connection type does not support operation r. For example, a receiver link does not support the submit_sm operation.
@throws ie.omk.smpp.AlreadyBoundException If the request type is a bind packet and this connection is already bound.
@throws ie.omk.smpp.message.SMPPProtocolException If synchronous communications is in use and the incoming response packet violates the SMPP specification, this exception will be thrown.
@see #setSeqNumScheme
This method assumes that the Request is sent out of Dialog. It uses the Router to determine the next hop. If the Router returns a empty iterator, and a Dialog is associated with the outgoing request of the Transaction then the Dialog route set is used to send the outgoing request.
This method implies that the application is functioning as either a UAC or a stateful proxy, hence the underlying implementation acts statefully. @throws SipException if the SipProvider cannot send the Request for any reason. @see Request
This method implies that the application is functioning as UAC hence the underlying SipProvider acts statefully. This method is useful for sending Bye's to terminate a dialog or Re-Invites/Refers on the Dialog for third party call control, call hold etc.
This method will set the From and the To tags for the outgoing request. This method increments the dialog sequence number and sets the correct sequence number to the outgoing Request and associates the client transaction with this dialog. Note that any tags assigned by the user will be over-written by this method. If the caller sets no RouteHeader in the Request to be sent out, the implementation of this method will add the RouteHeader from the routes that are mantained in the dialog. If the caller sets the RouteHeader's, the implementation will leave the route headers unaltered. This allows the application to manage its own route set if so desired.
The User Agent traditionally must not send a BYE on a confirmed INVITE until it has received an ACK for its 2xx response or until the server transaction timeout is received.
A Dialog may be created by an INVITE request and subsequently SUBSCRIBE/NOTIFY are sent withing that Dialog. In this case the application may call {@link Dialog#terminateOnBye } to prevent the Dialogfrom Terminating upon reciept of a BYE. @param clientTransaction -the new ClientTransaction object identifying this transaction, this clientTransaction should be requested from {@link SipProvider#getNewClientTransaction(Request)} @throws TransactionDoesNotExistException if the clientTransaction does not correspond to any existing client transaction. @throws SipException if implementation cannot send the Request for any reason.
Once the Request message has been passed to this method, the SipProvider will forget about this Request. No transaction semantics will be associated with the Request and the SipProvider will not handle retranmissions for the Request. If these semantics are required it is the responsibility of the application not the SipProvider. @see Request @param request the Request message to send statelessly @throws SipException if the SipProvider cannot send the Request for any reason.
This method will use the provided ScepResponseHandler to parse the SCEP server response. If the response can be correctly parsed, this method will return the response. Otherwise, this method will throw a TransportException @param < T> the response type. @param msg the message to send. @param handler the handler used to parse the response. @return the SCEP server response. @throws TransportException if any transport error occurs.
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |