tree 718144aa24fff9e8cec65e18f2330c7fc65d3033
parent 3241af342e8d6d89fb1c6e658fd685138f3b4d7f
author Philipp Maier <pmaier@sysmocom.de> 1684834710 +0200
committer Philipp Maier <pmaier@sysmocom.de> 1684843665 +0200

MGCP_Test: fix TC_one_crcx_loopback_rtp_implicit

The testcase TC_one_crcx_loopback_rtp_implicit creates a loopback
connection using CRCX but without SDP. It selects AMR using LCO. The MGW
responds with an MDCX and acknowledges AMR with a payload type of 112,
The TTCN3 testcase then sends AMR RTP packets with payload type 111, those
are accepted and looped back but the payload type will be converted to 112
as negotiated in the CRCX response. However the TTCN3 test still expects
111 in the packets comming back from the MGW. This is obviously a wrong
expectation and the testcase did only pass because Osmo-MGW was behaving
incorrectly.

To fix this let's just use 112 as payload type as payload type in this
test. This is the recommended payload type number for AMR (3GPP TS 48.103,
Table 5.4.2.2.1) and used by the MGW by default in case the call agent does
not specify a different one in SDP.

Change-Id: Idc370e9dc2e4954374fc7d07f7b117788028635a
Related: OS#5461