Philipp Maier
28bb82990c
At the moment the RTP stream emulation is left in its default configuration, this means that the payload type that appears in the RTP stream is always 0. This may mismatch the payload type that is configured with MGCP. If nothing else is set, we should make sure that whan we create and modify flows, the RTP emulation is always reconfigured to use the payload-type that we set in the flow parameters. The other rtp-emulation parameters should be set to their defaults. - Make sure f_flow_modify and f_flow_create set the rtp flow parameters properly. Change-Id: Ie888424ac3e0bf0d960b6f071855b6dd43935a0e Related:OS#3384 |
||
---|---|---|
.. | ||
MGCP_Test.cfg | ||
MGCP_Test.default | ||
MGCP_Test.ttcn | ||
README.md | ||
RTP_CodecPort_CtrlFunct.ttcn | ||
RTP_CodecPort_CtrlFunctDef.cc | ||
RTP_Endpoint.ttcn | ||
expected-results.xml | ||
gen_links.sh | ||
regen_makefile.sh |
README.md
== MGW_Test.ttcn
- external interfaces
- MGCP (emulates call agent)
- RTP (stream source/sink)
{% dot mgw_tests.svg digraph G { rankdir=LR; MGW [label="IUT\nosmo-mgw",shape="box"]; ATS [label="ATS\nMGCP_Test.ttcn"];
ATS -> MGW [label="RTP"]; ATS -> MGW [label="MGCP"]; MGW -> ATS [label="RTP"]; } %}