You must have more than one SIP trunk and/or multiple GSM gateways? I ask because 70 seconds is way longer than it would take for a single SIP trunk to fail if there is no response to the INVITE using default settings. By default the SIP trunk should fail after 3.5 seconds (1 INVITE + 6 INVITE Retries * 500ms). A good way to bring this down would be to change the INVITE Retries from six (6) to two (2) on the SIP Profile. You could also use a tool such as TranslatorX to parse Detail-level SDI logs from CUCM and see what's happening in the dialog.
Otherwise you could see if the GSM gateways support SIP OPTIONS PING (requires CUCM 8.5+). This is a keepalive mechanism that causes CUCM to consider the SIP trunk down if in-dialog SIP messages do not receive a response.
And it states that the first retry starts with 500ms and then it doubles the time for each new retry, at least that is what I understood. I will try reducing the retries and using the tool you mentioned.
Yeah I read about the SIP Options Ping unfortunately this is a CUCM 8.0.3.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...