Skip to main content
Version: 1.x.x

Test Plan

DUT and Endpoints Configuration

  • Routr has a Gateway resource configured to use TCP transport.
  • The Gateway resource is configured with a range of E.164 numbers.
  • Routr is configured to support Registration mode.
  • A Domain named sip.local exist with Agents 1001@sip.local and 1002@sip.local
  • The Gateway is capable of handling RFC6140 registrations

Test Case Summary

Test Case IDTitleRequired
1.1.1Registration SetupYes
1.1.2Registration FailureYes
1.1.3Maintaining RegistrationYes
1.1.4AuthenticationYes
1.1.5TLS Server ModeNo
1.2.1DNS LookupYes
1.2.2Static Mode Failure DetectionNo
1.2.3TLS AuthenticationNo
1.2.4TLS Certificate ValidationNo
1.3.1Intra-Domain Routing / Successful Invite SetupYes
1.3.2Intra-Domain Routing / Invite Rejected by CalleeYes
1.3.3Intra-Domain Routing / Invite Cancelled by CallerYes
1.3.4Intra-Domain Routing / Invite Cancelled by CalleeYes
1.4.1Domain-Ingress Routing / Successful Invite SetupYes
1.4.2Domain-Ingress Routing / Invite Rejected by CalleeYes
1.4.3Domain-Ingress Routing / Invite Cancelled by CallerYes
1.4.4Domain-Ingress Routing / Invite Cancelled by CalleeYes
1.5.1Domain-Egress Routing / Successful Invite SetupYes
1.5.2Domain-Egress Routing / Invite Rejected by CalleeYes
1.5.3Domain-Egress Routing / Invite Cancelled by CallerYes
1.5.4Domain-Egress Routing / Invite Cancelled by CalleeYes
1.6.1Peer-Egress Routing / Successful Invite SetupYes

Test Cases

Test Case 1.1.1: Registration Setup

Objective: This section tests the registration compatibility between Routr and the SIP Trunk provider. If the SIP Trunk provider under testing is IP-based, this section can be skipped.

Procedure:

DescriptionExpected Result
Step 1Restart Routr to send a REGISTER message to the GatewayRoutr restarts
Step 2Wait for the server to restartUAS receives correct registration sequence
Step 3Clear the registration tableRegistry table is empty