Does Datahook includes Provider call ID

Egress / Ingress
1

Hi team, I wanted to check whether the data hooks capability includes the Provider Call ID. If not, what is the best way to retrieve this data?

2

Not sure what you are asking. What datahook do you mean? What are you trying to do?

3

Thanks @CWilson — let me be more precise. By data hooks I meant the SDK-side collection described in Data hooks, specifically ctx.make_session_report().

What I’m actually after: the SIP dashboard shows a Provider Call ID for each call, which I use to find that call logs in my SIP provider’s portal.

Three questions:

  1. Which ID is it? Is the dashboard’s “Provider Call ID” the same value as sip.callIDFull (“Trunk provider SIP call ID”) in the SIP participant attributes, or is it the provider-generated ID passed via SIP X headers that the troubleshooting guide describes?
  2. How do I collect it? Is reading participant.attributes in my entrypoint the right approach, and is that value guaranteed to be populated by the time the participant joins? The SIP participant docs note that attributes set via headers_to_attributes update asynchronously — should I be listening for participant_attributes_changed or calling lk.sip.GetRemoteHeaders instead?
  3. Non-Twilio trunks: there’s sip.twilio.callSid for Twilio. For other providers, is headers_to_attributes the recommended way to capture the provider’s own call ID, or is there a first-class path?
4

Hi, I didn’t generate a report to double-check but I checked the source code and SIP stats aren’t logged there.

The provider call ID is exposed as sip.callIDFull, documented here:

So, you can read it from there when the SIP participant joins and log it as needed.