Bug #5729
closedttcn3-bsc-test-sccplite: +47 failues since build 1644 (Oct 21, 2022)
100%
Description
Starting from https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bsc-test-sccplite/1644/, we see a massive fallout. Most of them fail due to timeout waiting for response to CRCX.
Timeout waiting for response to { line := { verb := "CRCX", trans_id := "0", ep := "1@mgw", ver := "1.0" }, params := { { code := "M", val := "sendrecv" }, { code := "C", val := "51234" }, { code := "L", val := "p:20, a:AMR" } }, sdp := { protocol_version := 0, origin := { user_name := "-", session_id := "23", session_version := "42", net_type := "IN", addr_type := "IP4", addr := "127.0.0.4" }, session_name := "-", information := omit, uri := omit, emails := omit, phone_numbers := omit, connection := { net_type := "IN", addr_type := "IP4", conn_addr := { addr := "127.0.0.5", ttl := omit, num_of_addr := omit } }, bandwidth := omit, times := { { time_field := { start_time := "0", stop_time := "0" }, time_repeat := omit } }, timezone_adjustments := omit, key := omit, attributes := omit, media_list := { { media_field := { media := "audio", ports := { port_number := 14000, num_of_ports := omit }, transport := "RTP/AVP", fmts := { "3" } }, information := omit, connections := omit, bandwidth := omit, key := omit, attributes := { { ptime := { attr_value := "20" } } } } } } } BSC_Tests.ttcn:12030 BSC_Tests control part BSC_Tests.ttcn:4047 TC_assignment_fr_a5_0 testcase
Even more tests started to fail today: https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bsc-test-sccplite/1648/.
Updated by fixeria over 1 year ago
The MGCP flow for passing build (see PCAP):
605 7.186011 172.18.12.20 → 172.18.12.203 MGCP 129 CRCX 1 1@mgw MGCP 1.0 620 7.206782 172.18.12.203 → 172.18.12.20 MGCP/SDP 201 200 1 OK 669 7.253559 172.18.12.20 → 172.18.12.203 MGCP/SDP 210 MDCX 2 1@mgw MGCP 1.0 670 7.258926 172.18.12.203 → 172.18.12.20 MGCP/SDP 196 200 2 OK 763 9.283019 172.18.12.203 → 172.18.12.20 MGCP/SDP 241 CRCX 0 1@mgw MGCP 1.0 769 9.283298 172.18.12.20 → 172.18.12.203 MGCP/SDP 214 CRCX 0 1@mgw MGCP 1.0 770 9.284992 172.18.12.203 → 172.18.12.20 MGCP/SDP 207 200 0 OK 774 9.285245 172.18.12.20 → 172.18.12.203 MGCP/SDP 234 200 0 OK 827 9.308742 172.18.12.20 → 172.18.12.203 MGCP 91 DLCX 3 1@mgw MGCP 1.0
The MGCP flow for failing build (see PCAP):
608 7.546541 172.18.12.20 → 172.18.12.203 MGCP 129 CRCX 1 1@mgw MGCP 1.0 630 7.576665 172.18.12.203 → 172.18.12.20 MGCP/SDP 201 200 1 OK 668 7.583577 172.18.12.20 → 172.18.12.203 MGCP/SDP 210 MDCX 2 1@mgw MGCP 1.0 670 7.600665 172.18.12.203 → 172.18.12.20 MGCP/SDP 196 200 2 OK 759 9.625633 172.18.12.203 → 172.18.12.20 MGCP/SDP 241 CRCX 0 1@mgw MGCP 1.0 1030 14.632545 172.18.12.20 → 172.18.12.203 MGCP 91 DLCX 3 1@mgw MGCP 1.0 1031 14.632580 172.18.12.203 → 172.18.12.20 ICMP 119 Destination unreachable (Port unreachable)
In the failing PCAP, frame number 765 I see:
osmo_bsc_mgcp.c:81 error receiving data from MGCP<->IPA proxy UDP socket: Connection refused
Updated by fixeria over 1 year ago
- % Done changed from 0 to 20
The problem seems to be related to the recent VTY command rearrangements. I tried reverting Pau's recent commit:
commit 9a330b6fc32f4012626d25be4bbac2c5102203e3 Author: Pau Espin Pedrol <pespin@sysmocom.de> Date: Wed Oct 19 13:49:52 2022 +0200 ttcn3-bsc: Update osmo-bsc cfg files to use mgw pooling VTY commands OsmoBSC has supported this VTY interface since more than a year ago. Let's update the config files to use the new "mgw" node. The recently submitted VTY commands without the redundant "mgw" prefix are still not used here in order to have the config file work with latest release which still doesn't support those. Change-Id: Iabf117f9e6de02cac16e44d9a0ca32a30d71847c Related: SYS#5987
and this made all currently failing assignment related tests pass! This is the relevant part:
diff --git a/ttcn3-bsc-test/sccplite/osmo-bsc.cfg b/ttcn3-bsc-test/sccplite/osmo-bsc.cfg
index 1bb164e..c7c6f90 100644
--- a/ttcn3-bsc-test/sccplite/osmo-bsc.cfg
+++ b/ttcn3-bsc-test/sccplite/osmo-bsc.cfg
@@ -76,8 +76,6 @@ network
handover maximum distance 9999
timer t3113 10
timer t3212 30
- mgw 0
- mgw remote-ip 172.18.12.203
bts 0
type sysmobts
band DCS1800
@@ -478,6 +476,7 @@ msc 0
amr-config 5_15k forbidden
amr-config 4_75k forbidden
codec-list fr1 fr2 fr3 hr1 hr3
+ mgw remote-ip 172.18.12.203
asp-protocol ipa
bsc
mid-call-timeout 0
There seems to be some difference between the MSC-node scoped 'mgw remote-ip' and MGW-node scoped 'mgw remote-ip' commands?
Updated by fixeria over 1 year ago
- Status changed from In Progress to New
- Assignee changed from fixeria to pespin
pespin this regression is likely related to your recent patches, so I am assigning this ticket to you.
Updated by pespin over 1 year ago
- Status changed from New to Feedback
- % Done changed from 20 to 90
Should be fixed by:
https://gerrit.osmocom.org/c/osmo-bsc/+/29875 sccplite: Use mgwpool config to set up socket forwarding IPA-MGCP from MSC
Updated by pespin over 1 year ago
- Status changed from Feedback to Resolved
- % Done changed from 90 to 100