Bug #4957: ttcn3-sip-test is broken since 15 Dec 2020 - Cellular Network Infrastructure - Open Source Mobile Communications

Actions

Copy link

Bug #4957

closed

ttcn3-sip-test is broken since 15 Dec 2020

Added by fixeria about 3 years ago. Updated about 3 years ago.

Status:

Closed

Priority:

High

Assignee:

pespin

Target version:

Start date:

01/19/2021

Due date:

% Done:

100%

Spec Reference:

Description

All test cases fail under both Debian and CentOS:

https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-sip-test/1051/
https://jenkins.osmocom.org/jenkins/view/TTCN3-centos/job/TTCN3-centos-sip-test/238/

Although, the 'latest' is relatively stable:

https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-sip-test-latest/828/

I spent a few hours trying to investigate what's going on. Here are some intermediate results:

Q: Did sofia-sip change?
- A: No. All test cases on my machine also fail with v1.12.11 that I installed back in 2019.
Q: Did the test suite change?
- A: I could not find any changes that would affect the test suite behavior directly:
  - https://gerrit.osmocom.org/q/Ib4399aa488afd917e3eda5e79d56ea3797ef7c78 - only expected-results.xml was changed,
  - https://gerrit.osmocom.org/q/I37db9962f51baf2c63bd58ec47ec89f773d7a255 - changing code that is commended out.
Q: Did osmo-sip-connector's code change?
- A: Yes, some new commits have been merged recently:
- ... downgrading before them does not change anything though :/
  - tried I17e1adac40ac01daee0dd83da0a6aaebd78ea0dc and I3b1bebbcc9e36be43d8d055c8d28cbb38ff21b37
Q: Did libosmocore's code change?
- A: Needs to be investigated.
  - I tried downgrading to I781ab838bd02ac1b13d384ce3f4259e26cedb61e => nothing changed.

The test cases fail due to DTEs listed below:

"MNCC_CodecPort.ttcn:19 Dynamic test case error: Initializing a variable of enumerated type @MNCC_Types.MNCC_MsgType with invalid numeric value 346140544. (No such file or directory)"
"Dynamic test case error: SIP Test Port: syntax error "v" -> unexpected character at character position 1."
"MNCC_Emulation.ttcn:348 Dynamic test case error: Write error (Broken pipe)"

Sometimes it's one reason, sometimes another. Sometimes there is no DTE but "timeout of Tguard". Weird.

Actions

Copy link

Updated by fixeria about 3 years ago

I constantly see the following error in the output of osmo-sip-connector:

20210123182608924 DSIP NOTICE sip.c:679 tport_udp_error: Connection refused (111) [icmp type=3 code=3]
20210123182608924 DSIP NOTICE sip.c:679         reported by [127.0.0.2]:0
20210123182608924 DSIP NOTICE sip.c:679 nta_agent: tport: 127.0.0.2:5060: Connection refused
20210123182608924 DSIP NOTICE sip.c:679 tport(0x564d7bfb3530): zero length packet

Actions

Copy link

Updated by fixeria about 3 years ago

Assignee set to pespin

Actions

Copy link

Updated by pespin about 3 years ago

ttcn3-sip-test-latest doesn't fail probably because it's still using MNCCv6, while master uses MNCCv7.

It could be some TTCN3 MNCCv7 specific issue. I added MNCCv7 support to osmo-ttcn3-hacks.git in 563b3d013b166115a4f9e526d5e21df36f3bd399 (Sep 9 2020), not sure how it started later (JAN 16 2021).

Actions

Copy link