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
This commit is contained in:
David Yat Sin 2010-02-18 18:42:36 +00:00
parent fa836e6e08
commit 5aa34213df
1 changed files with 7 additions and 1 deletions

View File

@ -237,7 +237,13 @@ static ZIO_CHANNEL_REQUEST_FUNCTION(sangoma_boost_channel_request)
zap_status_t status = ZAP_FAIL; zap_status_t status = ZAP_FAIL;
sangoma_boost_request_id_t r; sangoma_boost_request_id_t r;
sangomabc_event_t event = {0}; 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; sangoma_boost_request_status_t st;
char ani[128] = ""; char ani[128] = "";
char *gr = NULL; char *gr = NULL;