public class InviteClientTransactionsStateMachineTest extends MessageFlowHarness
|INVITE from TU Timer A fires |INVITE sent Reset A, V Timer B fires INVITE sent +-----------+ or Transport Err. +---------| |---------------+inform TU | | Calling | | +-------->| |-------------->| +-----------+ 2xx | | | 2xx to TU | | |1xx | 300-699 +---------------+ |1xx to TU | ACK sent | | | esp. to TU | 1xx V | | 1xx to TU -----------+ | | +---------| | | | | |Proceeding |-------------->| | +-------->| | 2xx | | +-----------+ 2xx to TU | | 300-699 | | | ACK sent, | | | resp. to TU| | | | | NOTE: | 300-699 V | | ACK sent +-----------+Transport Err. | transitions | +---------| |Inform TU | labeled with | | | Completed |-------------->| the event | +-------->| | | over the action | +-----------+ | to take | ˆ | | | | | Timer D fires | +--------------+ | - | | | V | +-----------+ | | | | | Terminated|<--------------+ | | +-----------+ Figure 5: INVITE client transactionTODO Currently, transactions' behaviour is not tested for misappropriation of incoming messages. TODO Currently, invite transactions are not tested for proper termination upon respective timeouts.
counter, eventCollector, EXTENSION_HDR, MESSAGES_ARRIVE_FOR, RETRY_OBJECT_DELETES, RETRY_OBJECT_DELETES_AFTER, riListeningPoint, riSipProvider, riSipStack, STACKS_SHUT_DOWN_FOR, STACKS_START_FOR, tiListeningPoint, tiSipProvider, tiSipStack, TRANSACTION_TIMES_OUT_FOR
ABORT_ON_FAIL, abortOnFail, console, IMPLEMENTATION_PATH, LOCAL_ADDRESS, LOG_FILE_NAME, logFileName, path, printWriter, riAddressFactory, riFactory, riHeaderFactory, riMessageFactory, testCounter, testResult, tiAddressFactory, tiFactory, tiHeaderFactory, tiMessageFactory
Constructor and Description |
---|
InviteClientTransactionsStateMachineTest(String name) |
Modifier and Type | Method and Description |
---|---|
static Test |
suite() |
void |
testCallingCompletedTerminatedScenario()
Tries to steer a TI client transaction through the following scenario
Calling-->Completed-->Terminated.
|
void |
testCallingProceedingCompletedTerminatedScenario()
Tries to steer a TI client transaction through the following scenario
Calling-->Proceeding-->Completed-->Terminated.
|
void |
testCallingProceedingTerminatedScenario()
Tries to steer a TI client transaction through the following scenario
Calling-->Proceeding-->Terminated.
|
void |
testCallingTerminatedScenario()
Tries to steer a TI client transaction through the following scenario
Calling-->Terminated.
|
void |
testInviteCancel()
JvB: Tests transmission of an INVITE followed by CANCELlation of that
request
-> INVITE <- 100 -> CANCEL <- OK <- 487 -> ACK
|
addStatus, addStatus, createRequest, createRiContact, createRiInviteRequest, createRiRegisterRequest, createTiContact, createTiInviteRequest, createTiRegisterRequest, setUp, sleep, tearDown, waitForMessage, waitForTimeout, waitLongForMessage, waitShortForMessage
assertEquals, assertEquals, assertEquals, assertEquals, assertNotNull, assertNull, assertSame, assertTrue, assertTrue, checkImplementsInterface, fail, fail, fail, getImplementationPath, getRiProperties, getTiProperties, implementsInterface, logTestCompleted, logTestCompleted
public InviteClientTransactionsStateMachineTest(String name)
public void testCallingProceedingCompletedTerminatedScenario()
public void testInviteCancel()
public void testCallingCompletedTerminatedScenario()
public void testCallingProceedingTerminatedScenario()
public void testCallingTerminatedScenario()
public static Test suite()
Copyright © 2018. All Rights Reserved.