Review at

increase RAN timeout in MGCP FSM

The MGCP FSM implements a timeout when waiting for the RAN to complete
the call (assignment complete, alerting, connect...). This timeout
is currently set to 10sec. This means if the other end did not pick
up after 10sec, the MGCP connection will be lost while the phone keeps
ringing. When the other end finally picks up, the call gets

This behavior is odd and requires a proper fix. For now increasing the
timeout to 120sec. will decrese the probability that he problem occurs.

- Increas RAN timeout to 120sec (2 min).

Change-Id: I5a11d53f9701d9b11b18d7026ff2241c7c0b57f5
M src/libmsc/msc_mgcp.c
1 file changed, 2 insertions(+), 3 deletions(-)

  git pull ssh:// refs/changes/20/6320/1

diff --git a/src/libmsc/msc_mgcp.c b/src/libmsc/msc_mgcp.c
index bd60c13..9fee27b 100644
--- a/src/libmsc/msc_mgcp.c
+++ b/src/libmsc/msc_mgcp.c
@@ -44,7 +44,7 @@
 #define MGCP_MGW_TIMEOUT 4     /* in seconds */
-#define MGCP_RAN_TIMEOUT 10    /* in seconds */
+#define MGCP_RAN_TIMEOUT 120   /* in seconds */
 #define MGCP_REL_TIMEOUT 60    /* in seconds */
@@ -445,8 +445,7 @@
        /* Note: When we reach this point then the situation is basically that
         * we have two sides connected, both are in loopback. The local ports
         * of the side pointing towards the BSS should be already communicated
-        * and we are waiting now for the BSS to return with the assignment
-        * complete command. */
+        * and we are waiting now the other end to pick up. */
        osmo_fsm_inst_state_chg(fi, ST_MDCX_CN, MGCP_RAN_TIMEOUT, 

To view, visit
To unsubscribe, visit

Gerrit-MessageType: newchange
Gerrit-Change-Id: I5a11d53f9701d9b11b18d7026ff2241c7c0b57f5
Gerrit-PatchSet: 1
Gerrit-Project: osmo-msc
Gerrit-Branch: master
Gerrit-Owner: dexter <>

Reply via email to