data: qmi-service-ims: add binding message
These are messages and indications I observed on Android. Exchanging these messages do not enable any feature, but they can make it easier for debugging.
The number used in binding seems to be the subscription number like in WDS Bind Subscription. Android on the Pixel 3a (the Pixel 3a has eSIM support) binds both 0 and 1, even though binding 1 fails to do anything, and the Pinephone (without eSIM support) didn't need this bind request. I can't be completely certain though...
IMS settings service:
$ sudo qmicli -p -d qrtr://0 --client-no-release-cid --ims-bind=0
[qrtr://0] IMS Settings bind successful
[qrtr://0] Client ID not released:
Service: 'ims'
CID: '1'
$ sudo qmicli -p -d qrtr://0 --client-cid=1 --ims-get-ims-services-enabled-setting
[qrtr://0] IMS services:
IMS registration enabled: yes
Voice service enabled: yes
Voice WiFi service enabled: no
UE to TAS service enabled: yes
SMS service enabled: yes
USSD service enabled: yes
IMS application service:
$ sudo qmicli -p -d qrtr://0 --client-no-release-cid --imsa-bind=0
[qrtr://0] IMSA bind successful
[qrtr://0] Client ID not released:
Service: 'imsa'
CID: '1'
$ sudo qmicli -p -d qrtr://0 --client-no-release-cid --client-cid=1 --client-no-release-cid --imsa-get-ims-registration-status
[qrtr://0] IMS registration:
Status: 'registered'
Technology: 'wwan'
[qrtr://0] Client ID not released:
Service: 'imsa'
CID: '1'
$ sudo qmicli -p -d qrtr://0 --client-cid=1 --imsa-get-ims-services-status
[qrtr://0] IMS services:
SMS service
Status: 'available'
Technology: 'wwan'
Voice service
Status: 'available'
Technology: 'wwan'
Video Telephony service
Status: 'unavailable'
Technology: 'wwan'
UE to TAS service
Status: 'available'
Technology: 'wwan'
Video Share service
Edited by Richard Acayan