Call end reason in All Call Status indication / Get All Call Info response
Reinhard Speyerer
rspmn at arcor.de
Sat Jun 7 12:52:53 UTC 2025
On Wed, Jun 04, 2025 at 01:28:52PM +0000, Juárez José Ramón wrote:
> Hi,
>
> Have you any plans to add the call end reason in the call status indication and call info response?
>
> We have been debugging a little bit and we have found a TLV 0x14 which looks that includes the call end reason (e.g. 0x92 = QMI_VOICE_CALL_END_REASON_USER_BUSY):
>
> <<<<<< TLV:
> <<<<<< type = 0x14
> <<<<<< length = 4
> <<<<<< value = 01:01:92:00
>
> We do not have access to the full Qualcomm MSM Interface, so we are not sure what the rest of bytes represent. It looks that the second byte is the call ID and first one could be the array elements. Could you provide this info to update the qmi-service-voice.json message data?
Hi José,
your assumption looks correct according to the Gobi API:
// Structure to describe indication TLV 0x14 for Voice AllCallStatusIndication
struct sVoiceAllCallStatusIndication_CallEndReason
{
UINT8 mCallInstanceCount;
struct sInstance
{
UINT8 mCallID;
eQMIVoiceEndReasons mEndReason;
};
// This array must be the size specified by mCallInstanceCount
// sInstance mInstances[1];
};
You can find snapshots of various Gobi API releases before
https://bye.codeaurora.org/ in the libqmi git repo and an archived copy
of the changes after the last CodeAurora release in 2013 as part of
https://git.codelinaro.org/clo/qsdk/oss/lklm/gobinet .
It might make sense to check
https://git.codelinaro.org/clo/le/platform/vendor/qcom-opensource/snaptel-sdk
for a type which corresponds to eQMIVoiceEndReasons (enum class FailureCause
in SuppServicesManager.hpp perhaps) and add the additional values to the
libqmi eqivalent of eQMIVoiceEndReasons.
Regards,
Reinhard
More information about the libqmi-devel
mailing list