From: David Yat Sin <dyatsin@sangoma.com>
Date: Thu, 18 Feb 2010 18:42:36 +0000 (+0000)
Subject: Increased timeout in sangoma_boost_channel_request to match PRI specs
X-Git-Tag: v1.0.6~38^2~27
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=5aa34213dfa63b7eb5919fa516e13ebec937b790;p=thirdparty%2Ffreeswitch.git

Increased timeout in sangoma_boost_channel_request to match PRI specs

git-svn-id: http://svn.openzap.org/svn/openzap/trunk@1035 a93c3328-9c30-0410-af19-c9cd2b2d52af
---

diff --git a/libs/openzap/src/ozmod/ozmod_sangoma_boost/ozmod_sangoma_boost.c b/libs/openzap/src/ozmod/ozmod_sangoma_boost/ozmod_sangoma_boost.c
index e658854cb1..04ee26ccb0 100644
--- a/libs/openzap/src/ozmod/ozmod_sangoma_boost/ozmod_sangoma_boost.c
+++ b/libs/openzap/src/ozmod/ozmod_sangoma_boost/ozmod_sangoma_boost.c
@@ -237,7 +237,13 @@ static ZIO_CHANNEL_REQUEST_FUNCTION(sangoma_boost_channel_request)
 	zap_status_t status = ZAP_FAIL;
 	sangoma_boost_request_id_t r;
 	sangomabc_event_t event = {0};
-	int sanity = 5000;
+
+		/* sanity has to be more than 8 seconds.
+	 * In PRI specs, timeout is 4 seconds for remote switch to respond to a SETUP,
+	 * and PRI stack will retransmit a second SETUP after the first timeout, so
+	 * we should allow for at least 8 seconds */
+
+	int sanity = 10000;
 	sangoma_boost_request_status_t st;
 	char ani[128] = "";
 	char *gr = NULL;