vty: update desc of conn-timeout
It can be used together with LCLS, just make sure to also enable
keep-alive packets.
In OS#3429 it was pointed out, that during LCLS the media path remains
active but is not used. Without any traffic flowing, this looks like a
timed out connection and so it will be killed if conn-timeout is set.
However, OsmoBSC and OsmoMSC have an option to enable RTP keep-alive
packets (through libosmo-mgcp, originally intended to keep connections
behind NAT open). If that option is enabled, the keep-alive packets
should also prevent the conn-timeout.
Related: OS#3783
Change-Id: Ib4d19104d558a26a444a80fb36f4b7b33bc5cc59
diff --git a/src/libosmo-mgcp/mgcp_vty.c b/src/libosmo-mgcp/mgcp_vty.c
index a479b95..5f9853b 100644
--- a/src/libosmo-mgcp/mgcp_vty.c
+++ b/src/libosmo-mgcp/mgcp_vty.c
@@ -1382,7 +1382,8 @@
"conn-timeout <0-65534>",
"Set a time after which inactive connections (CIs) are closed. Set to 0 to disable timeout. This can be used to"
" work around interoperability problems causing connections to stay open forever, and slowly exhausting all"
- " available ports. Do not enable when LCLS is used (connections in LCLS state appear to be inactive)!\n"
+ " available ports. Enable keep-alive packets in MGW clients when using this option together with LCLS (OsmoBSC,"
+ " OsmoMSC: 'rtp keep-alive')!\n"
"Timeout value (sec.)\n")
{
g_cfg->conn_timeout = strtoul(argv[0], NULL, 10);