mirror of
https://gitea.osmocom.org/cellular-infrastructure/osmo-mgw.git
synced 2025-11-02 04:53:24 +00:00
Remove public API that makes no sense anymore and is dead code. I see the dropped API as a dead-end initial misconception of the early mgcp client, and it doesn't really make sense to drag this stuff along. It has not been used by osmo-msc,-bsc for a long time now, and just confuses the reader. It is public API, yes, and older versions of osmo-msc / osmo-bsc will not be able to compile against this, but even if it did, the resulting MGCP client would not work with the current osmo-mgw: this API is still based on the premise that the MGCP client dictates the MGW endpoint numbers, a concept that cannot be used with the current osmo-mgw. Instead, osmo-mgw expects a wildcarded endpoint upon CRCX and assigns its own endpoint names. Also, the bts-base configuration is unused and a legacy of when osmo-bsc_mgcp had explicit BTS and CN sides. Change-Id: I98a9f1f17a1c4ab20cea3b08c7d21663592134d6
70 lines
1.9 KiB
Plaintext
70 lines
1.9 KiB
Plaintext
DLMGCP message buffer to small, can not generate MGCP message
|
|
|
|
test_mgcp_client_cancel():
|
|
- composed msg with trans_id=1
|
|
- not in queue yet, cannot cancel yet
|
|
DLMGCP Cannot cancel, no such transaction: 1
|
|
- enqueue
|
|
- cancel succeeds
|
|
DLMGCP Canceled transaction 1
|
|
- late response gets discarded
|
|
DLMGCP Cannot find matching MGCP transaction for trans_id 1
|
|
- canceling again does nothing
|
|
DLMGCP Cannot cancel, no such transaction: 1
|
|
test_mgcp_client_cancel() done
|
|
|
|
test_sdp_section_start() test [0]:
|
|
body: ""
|
|
DLMGCP MGCP response: cannot find start of SDP parameters
|
|
got rc=-22
|
|
|
|
test_sdp_section_start() test [1]:
|
|
body: "\n\n"
|
|
got rc=0
|
|
got audio_port=0
|
|
|
|
test_sdp_section_start() test [2]:
|
|
body: "\r\n\r\n"
|
|
got rc=0
|
|
got audio_port=0
|
|
|
|
test_sdp_section_start() test [3]:
|
|
body: "\n\r\n\r"
|
|
got rc=0
|
|
got audio_port=0
|
|
|
|
test_sdp_section_start() test [4]:
|
|
body: "some mgcp header data\r\nand header params\n\nm=audio 23\r\n"
|
|
got rc=0
|
|
got audio_port=23
|
|
|
|
test_sdp_section_start() test [5]:
|
|
body: "some mgcp header data\r\nand header params\r\n\r\nm=audio 23\r\n"
|
|
got rc=0
|
|
got audio_port=23
|
|
|
|
test_sdp_section_start() test [6]:
|
|
body: "some mgcp header data\r\nand header params\n\r\n\rm=audio 23\r\n"
|
|
got rc=0
|
|
got audio_port=23
|
|
|
|
test_sdp_section_start() test [7]:
|
|
body: "some mgcp header data\r\nand header params\n\r\nm=audio 23\r\n"
|
|
DLMGCP MGCP response: cannot find start of SDP parameters
|
|
got rc=-22
|
|
|
|
test_sdp_section_start() test [8]:
|
|
body: "some mgcp header data\r\nand header params\r\n\rm=audio 23\r\n"
|
|
DLMGCP MGCP response: cannot find start of SDP parameters
|
|
got rc=-22
|
|
|
|
test_sdp_section_start() test [9]:
|
|
body: "some mgcp header data\r\nand header params\n\r\rm=audio 23\r\n"
|
|
DLMGCP MGCP response: cannot find start of SDP parameters
|
|
got rc=-22
|
|
DLMGCP ptmap contains illegal mapping: codec=113 maps to pt=2
|
|
DLMGCP ptmap contains illegal mapping: codec=0 maps to pt=100
|
|
DLMGCP ptmap contains illegal mapping: codec=113 maps to pt=2
|
|
DLMGCP ptmap contains illegal mapping: codec=0 maps to pt=100
|
|
Done
|