VoiceCallSessionData
When an inbound SIP INVITE arrives, the Telephony service creates a VoiceCallSessionData record associated with the VoiceCall and inserts the SIP header values from the request. The inbound Omni-Channel flow can query this record by VoiceCallId to read those headers for routing and context decisions. Customers can also update DisconnectMethod and related fields in their escalation or fallback flows to control how Salesforce signals the end of the call to the telephony partner.
Supported Calls
create(), delete(), describeLayout(), describeSObjects(), getDeleted(), getUpdated(), query(), retrieve(), undelete(), update(), upsert()
Special Access Rules
Available with Agentforce Voice.
Fields
| Field | Details |
|---|---|
| AssertedIdentityInfo |
|
| DisconnectMethod |
|
| DisconnectReason |
|
| FallbackFlowApiName |
|
| Name |
|
| PreferredIdentityInfo |
|
| PriorityInfo |
|
| PrivacyInfo |
|
| ReasonInfo |
|
| ReferToUri |
|
| ReferredByInfo |
|
| RequestUri |
|
| UserToUserInfo |
|
| VoiceCallId |
|
Usage
The Telephony service creates one VoiceCallSessionData record per call when an inbound SIP INVITE arrives. Each record has a one-to-one relationship with its parent VoiceCall.
Access SIP headers in an inbound flow
The Telephony service populates the standard SIP header fields (such as AssertedIdentityInfo and UserToUserInfo) before the inbound Omni-Channel flow executes. Query the record using VoiceCallId to retrieve header values for routing and context decisions.
To store additional SIP headers not covered by the standard fields, add custom fields to this object using the convention-based naming approach: replace hyphens in the SIP header name with underscores and append the __c suffix. For example, the X-Account-ID header maps to a custom field named X_Account_ID__c. The Telephony service maps incoming header values to matching custom fields automatically.
Configure the disconnect method
Set DisconnectMethod in your escalation flow or fallback flow to control whether Salesforce sends SIP_BYE or SIP_REFER to the telephony partner when the call ends. When using SIP_REFER, also set ReferToUri to specify the transfer destination.
Configure a fallback flow
Set FallbackFlowApiName to the API name of an autolaunched flow that should execute when an Agentforce Voice session ends in a failure or unsupported state. The fallback flow has access to DisconnectReason and other fields on this record, allowing you to set the appropriate disconnect method per scenario. If FallbackFlowApiName is null when a failure occurs, Salesforce defaults to SIP_BYE.