MGCP_Test: Add VTY access
The MGCP_Test testsuite currenty lacks VTY access capabilities, lets
add them so that future testcases can access the VTY in order to change
options on the fly.
Depends: osmo-ttcn3-hacks Ife949c61156222de3026280071226ef6f5dbd959
Change-Id: If383f81af3306f8f5bdf50152498ae1303d390df
Related: OS#3807
diff --git a/mgw/MGCP_Test.default b/mgw/MGCP_Test.default
index 16027cc..4336033 100644
--- a/mgw/MGCP_Test.default
+++ b/mgw/MGCP_Test.default
@@ -2,12 +2,22 @@
FileMask := LOG_ALL | TTCN_MATCHING;
[TESTPORT_PARAMETERS]
+*.MGWVTY.CTRL_MODE := "client"
+*.MGWVTY.CTRL_HOSTNAME := "127.0.0.1"
+*.MGWVTY.CTRL_PORTNUM := "4243"
+*.MGWVTY.CTRL_LOGIN_SKIPPED := "yes"
+*.MGWVTY.CTRL_DETECT_SERVER_DISCONNECTED := "yes"
+*.MGWVTY.CTRL_READMODE := "buffered"
+*.MGWVTY.CTRL_CLIENT_CLEANUP_LINEFEED := "yes"
+*.MGWVTY.CTRL_DETECT_CONNECTION_ESTABLISHMENT_RESULT := "yes"
+*.MGWVTY.PROMPT1 := "OsmoMGW> "
[MODULE_PARAMETERS]
mp_local_udp_port := 2727;
mp_local_ip:= "127.0.0.1";
mp_remote_udp_port := 2427;
mp_remote_ip:= "127.0.0.1";
+Osmocom_VTY_Functions.mp_prompt_prefix := "OsmoMGW";
[MAIN_CONTROLLER]