Hello
Has this happened to anyone? We are using Twilio Elastic SIP Trunk. According to Twilio tech support, some incoming calls time out due to a "network connectivity" issue. See the example below. A call times out
Right after the call goes through
According to Twilio they send the invite but our PBX (hosted in Azure) does not respond in time.
And again the next very second the call goes through OK.
We monitor the PBX. There are no drops or time-outs. Resources-wise, the PBX never reaches high CPU or Memory. Any ideas what may be going on here?
A weird theory is that this could be happening when call recording and transcriptions are ongoing. I have not tested it but that could be the only moment where the PBX coulbe at its busiest time.
Your thoughts?
Has this happened to anyone? We are using Twilio Elastic SIP Trunk. According to Twilio tech support, some incoming calls time out due to a "network connectivity" issue. See the example below. A call times out
Right after the call goes through
According to Twilio they send the invite but our PBX (hosted in Azure) does not respond in time.
And again the next very second the call goes through OK.
We monitor the PBX. There are no drops or time-outs. Resources-wise, the PBX never reaches high CPU or Memory. Any ideas what may be going on here?
A weird theory is that this could be happening when call recording and transcriptions are ongoing. I have not tested it but that could be the only moment where the PBX coulbe at its busiest time.
Your thoughts?
