Project

General

Profile

Bug #2857

No automatic testing of IuPS interface

Added by laforge about 1 year ago. Updated 5 days ago.

Status:
Stalled
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
01/23/2018
Due date:
01/23/2018
% Done:

20%

Spec Reference:
Tags:

Description

Similar to the situation in OsmoMSC with IuCS, we don't have any automatic testing of the IuPS interface. Once we figured out how to properly interface RANAP from TITAN, we should be able to write test cases in TTCN-3 to automatically test our IuPS implementation.


Related issues

Related to OsmoSGSN - Bug #3224: verify ciphering after UMTS AKANew2018-04-30

Follows OsmoMSC - Bug #2856: No automatic testing of IuCS interfaceStalled2018-01-22

History

#1 Updated by laforge about 1 year ago

  • Due date set to 01/23/2018
  • Start date changed from 01/22/2018 to 01/23/2018
  • Follows Bug #2856: No automatic testing of IuCS interface added

#2 Updated by laforge 11 months ago

  • Tags set to TTCN3, 3G

#3 Updated by laforge 10 months ago

  • Related to Bug #3224: verify ciphering after UMTS AKA added

#4 Updated by laforge 5 days ago

  • Status changed from New to In Progress
  • Assignee set to laforge
  • % Done changed from 0 to 20

I have RANAP encoding/decoding now working in TTCN-3, and I've also created a set of RANAP templates to use. Integration into the SGSN tets suite is currently ongoing.

#5 Updated by laforge 5 days ago

  • Status changed from In Progress to Stalled

The core RANAP integration, the templates etc. appear to be working. The problem is that due to bugs in the proprietary asn1 compiler we're not able to reliably transcode between BER and APER at this point. setting to stalled again.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)