Issue
When placing or receiving calls over Elastic SIP Trunking (ESIPT), customers expect to see active calls listed as “in-progress” in the Twilio Console or when querying the Calls API. Instead, the calls only appear after they have completed, which can be confusing when trying to monitor sip trunking traffic in real-time.
Product
SIP Calling Products
Environment
legacy Twilio Console
Cause
This behavior is expected and is due to a design difference between Elastic SIP Trunking (ESIPT) and Programmable Voice.
For Elastic SIP Trunking calls, Twilio does not maintain or expose a live “in-progress” Call resource in the same way as Programmable Voice. Instead, a Call Detail Record (CDR) is written once the call is terminated (for example, when Twilio receives the final BYE and the session is closed). At that point, the call becomes visible in the Console and via reporting endpoints.
Because of this architecture, active trunk calls will not show as “in-progress” in the Twilio Console or via the Calls API.
Note: ESIPT calls also cannot be terminated or updated via API. Trunking calls end only by a SIP BYE signal processed from either PSTN or SIP side, media/signaling timeout, or max call duration.
Resolution
There are no configuration changes required on the customer side, as this is the expected behavior for Elastic SIP Trunking. If you need to confirm or monitor live trunking calls, consider the following options:
Use your SBC, PBX or carrier-side tools for live monitoring.
Rely on Twilio Call Detail Records (CDRs) and the Console after calls complete.
Use Programmable Voice for use cases that require real-time call visibility.
In summary, there is no way to make Elastic SIP Trunking calls appear as “in-progress” in the Twilio Console; they will only be visible once the call has completed and the CDR has been generated.