cellular-infrastructure
/
osmo-msc
mirror of https://gerrit.osmocom.org/osmo-msc
9
0
Fork 0
Code Issues Releases Wiki Activity
osmo-msc/openbsc/tests/mgcp/mgcp_test.ok

62 lines
1.3 KiB
Plaintext
Raw Normal View History

mgcp: Add new for_each_line macro that also returns empty lines This patch add the for_each_line macro based on a strline_r() function (similar to strtok_r()), that is also part of this patch. This strline_r() function is tolerant with respect to line endings, it supports CR-only, CRLF, and LF-only and any combinations thereof (note that a CRLF is always detected as a single line break). Similar to for_each_non_empty_line (the former for_each_line) where the 'save' pointer needed to be initialised by a call to strtok_r(), the new for_each_line macro expects, that the 'save' pointer has been initialised by a call to strline_r(). Also note, that for_each_line/strline_r and for_each_non_empty_line/strtok_r may use the 'save' pointer differently, so calls to them can not be mixed. Sponsored-by: On-Waves ehf
2013-11-29 12:43:44 +00:00
line: 'one CR'
line: 'two CR'
line: ''
line: 'one CRLF'
line: 'two CRLF'
line: ''
line: 'one LF'
line: 'two LF'
line: ''
line: 'mixed (4 lines)'
line: ''
line: ''
line: ''
mgcp_test: Add wrong messages as input and check what happens Test parsing some invalid messages and see if we start to crash.
2012-03-16 08:53:49 +00:00
Testing AUEP1
Testing AUEP2
mgcp: Add testdata for MDCX handling
2012-12-10 11:54:57 +00:00
Testing MDCX1
Testing MDCX2
mgcp_test: Add wrong messages as input and check what happens Test parsing some invalid messages and see if we start to crash.
2012-03-16 08:53:49 +00:00
Testing CRCX
mgcp: Add testdata for MDCX handling
2012-12-10 11:54:57 +00:00
Testing MDCX3
mgcp: Add tests for payload types in MGCP messages These tests mainly check whether the SDP parsing works properly by looking at the payload type detected. Sponsored-by: On-Waves ehf
2013-11-29 12:43:45 +00:00
Testing MDCX4
mgcp: Test the second CRCX as a CRCX and not as a re-transmission The second CRCX would be mostly ignored and be handled by the retransmission layer of MGCP.
2012-12-07 13:42:03 +00:00
Testing DLCX
mgcp_test: Add wrong messages as input and check what happens Test parsing some invalid messages and see if we start to crash.
2012-03-16 08:53:49 +00:00
Testing CRCX_ZYN
Testing EMPTY
Testing SHORT1
Testing SHORT2
Testing SHORT3
Testing SHORT4
mgcp: Begin handling of the RQNT message as needed for DTMF Introduce a callback for the request and forward the signalrequest to the callback. This is not a full implementation of MGCP RQNT.
2012-11-29 11:54:22 +00:00
Testing RQNT1
Testing RQNT2
mgcp: Include statistics at the end of a connection Follow the MGCP specification and send the collected statistics at the end of a call. Right now this does not include jitter, packet loss and delay.
2012-09-14 15:18:12 +00:00
Testing DLCX
mgcp: Test and implement re-transmission handling MGCP is used over UDP and a response might be lost. The MGCP RFC asks for keeping a list of responses and then using the previous response to answer a duplicate request. I tried to conserve memory and just wanted to remember the last transaction identifier and result-code and re-generate the result from that. This made the code look bad and this is why the entire response will now be stored. It sadly increases the memory usage but can not be avoided at this time. Remove the msg->l3h pointer for the RQNT callback as strtok has modified the content of it.
2012-12-07 14:04:07 +00:00
Testing CRCX
Re-transmitting CRCX
Testing RQNT1
Re-transmitting RQNT1
Testing RQNT2
Re-transmitting RQNT2
Testing MDCX3
Re-transmitting MDCX3
Testing DLCX
Re-transmitting DLCX
mgcp: Calculate the packet loss as of Appendix A of RFC 3550 Calculate the expected packages and packet loss as of RFC 3550. The values should be clamped but our packet loss counter is 32 bits and not 24 and we should clamp at other values but I am waiting for some issues first before dealing with that.
2012-10-22 16:09:35 +00:00
Testing packet loss calculation.
nat: We want the remote to respond to our DLCX request We want to send a TRAP with the MGCP statistics from the NAT and the connected BSC. The BSC endpoint can be either released because of a DLCX from the MGCP CallAgent or the SCCP Connection release on the A-link. This is why we need to queue the statistics when the deleting the endpoint on the BSC. The processing is continued once the response arrives. This code assumes that the response of the DLCX will be sent by the remote side. The current amount of outstanding responses can be seen on the VTY. This assumption is based on the fact that the BSC has already responded to the CRCX and maybe to the MDCX. The MGCP RFC is bended to prefix the transaction identifier with "nat-" to easily detect the response and hand it to the handler. This will then parse the response and generate the TRAP. The current version is v1. We assume that the transaction space is big enough and we will not re-assign the transaction identifier too early.
2012-10-24 19:53:40 +00:00
Testing stat parsing
Parsing result: 0
Parsing result: 0
mgcp/rtp: Add test case for RTP timestamp patching and stats This patch adds a test case to check, whether RTP timestamps are generated properly after SSRC changes and whether the error counters work properly. Sponsored-by: On-Waves ehf
2013-11-25 11:53:29 +00:00
Testing packet error detection.
TS: 0, dTS: 0, TS Errs: in 0, out 0
TS: 160, dTS: 160, TS Errs: in 0, out 0
TS: 320, dTS: 160, TS Errs: in 0, out 0
TS: 320, dTS: 160, TS Errs: in 1, out 1
TS: 480, dTS: 160, TS Errs: in 1, out 1
TS: 640, dTS: 160, TS Errs: in 1, out 1
TS: 960, dTS: 320, TS Errs: in 2, out 2
TS: 1120, dTS: 160, TS Errs: in 3, out 3
TS: 1280, dTS: 160, TS Errs: in 3, out 3
TS: 1400, dTS: 120, TS Errs: in 4, out 4
TS: 1560, dTS: 160, TS Errs: in 5, out 5
TS: 1720, dTS: 160, TS Errs: in 5, out 5
mgcp/rtp: Fix timestamp offset when patching RTP packets The current implementation increments the seqno but does not increment the RTP timestamp, leading to two identical timestamps following one after the other. This patch fixes this by adding the computed tsdelta when the offset is calulated. In the unlikely case, that a tsdelta hasn't been computed yet when the SSRC changes, a tsdelta is computed based on the RTP rate and a RTP packet duration of 20ms (one speech frame per channel and packet). If the RTP rate is not known, a rate of 8000 is assumed. Note that this approach presumes, that the per RTP packet duration (in samples) is the same for the last two packets of the stream being replaced (the first one). Sponsored-by: On-Waves ehf
2013-11-25 14:23:35 +00:00
TS: 1880, dTS: 160, TS Errs: in 5, out 5
TS: 2040, dTS: 160, TS Errs: in 5, out 5
TS: 2200, dTS: 160, TS Errs: in 5, out 5
tests: Introduce running tests with GNU autotest in OpenBSC The quality of the tests is of different value but it is good to get started and improve from here.
2012-01-06 14:16:12 +00:00
Done