Ulticom Tests
Role: Client and Server
(Agent and Proxy implementation available -- but not tested)
Legend
- (ST) Successful tests
- (NT) Not tested (but implemented)
- (NI) Not implemented
Diameter Base Protocol Test Suite
| Test Case | Result | Test Partners |
| 3.1.1.1. Capabilities Negotiation | ST | 8 companies |
| 3.1.1.2. Election | ST | 2 companies |
| 3.1.1.3. Disconnection | ST | 1 company |
| 3.1.1.4. Re-Connection Algorithms | NT | X |
| 3.1.1.5. Failover and Failback | NT | X |
| 3.1.2.1. Peer Based Request Routing | ST | 8 companies |
| 3.1.2.2. Realm Based Routing | ST | 1 company |
| 3.1.2.3. Answer Message Routing | ST | 4 companies |
| 3.1.2.4. Loop Detection | NT | X |
| 3.1.3. Relay Agent | NT | X |
| 3.1.4. Redirection | NI | X |
| 3.2.1. General Statemachine | NT | X |
| 3.2.2. Dynamic Peer Discovery | NI | X |
| Duplicate Detection Test | NI |
TLS security comparison between FQDN of the peer and
SubjectAltName? and Organization Name of certificate.
Diameter Credit Control Test Suite
| Test Case | Result | Test Partners |
| 4.2.1.1. Session Based Credit Control First Interrogation | ST | 4 companies |
| 4.2.1.2. Session Based Credit Control Intermediate Interrogation | ST | 4 companies |
| 4.2.1.3. Session Based Credit Control Final Interrogation | ST | 4 companies |
| 4.2.1.4. Sub Sessions | NI | X |
| 4.2.1.5. Session Based Credit Control Failure Procedures | ST | 1 company |
| 4.2.1.6. Service Price Enquiry | ST | 3 companies |
| 4.2.1.7. Balance Check | ST | 3 companies |
| 4.2.1.8. Direct Debiting | ST | 3 companies |
| 4.2.1.9. Refunds | NT | X |
| 4.2.1.10. Event Based Credit Control Failure Procedures | ST | 2 companies |
| 4.2.2.1. Tariff Time Support | NI | X |
| 4.2.2.2. Graceful Service Termination | NI | X |
| 4.2.2.3. Validity Time | NT | X |
| 4.2.2.4. Server Initiated Credit Reauthorization | NI | X |
Monday:
Basic connectivity tests : 3.1.1.1 , 3.1.1.2, 3.1.1.3, 3.1.2.3
Tested basic capability exchange negotiation, negative capability negotiation tests (non-overlapping supported application set advertisement, CER/CEA messages with wrong message flags and wrong AVP flags, transport connection disconnect during capability negotiation)
Started with DCCA event based scenarios
Different event based scenarios (debit, price inquiry, balance check)
Tuesday:
Continued with DCCA tests 4.2.1.1, 4.2.1.2, 4.2.1.3
Multiple session based scenarios, exercised DCCA state machine failure transactions (unable to deliver, failure to send transactions)
Wednesday:
Continued with DCCA session based scenario tests
3GPP Sh/Cx interface tests, mainly single query response scenarios
4.4.1, 4.4.2
Rf interface tests 4.4.3
Election tests 3.1.1.2
--
DimeGroup - 29 Jan 2007