qmi, imsd-pcscf: read the ims PDN's P-CSCF list from the modem's runtime settings
The network hands the P-CSCF addresses to the modem in the PDN's Protocol Configuration Options; ModemManager's bearer code does not ask the modem for them, qmicli (libqmi 1.39) prints none of them, and libqmi has no TLV for the IPv6 list (0x2E), which is why PCSCF= was a required setting. A second QMI WDS client reads them once it is bound to the bearer's mux data port (the binding ModemManager gives its own clients): Bind Mux Data Port, Set IP Family 6, Get Current Settings, over one AF_QIPCRTR socket. Imsd:Qmi holds the bytes and the readers (0x22 the flag, 0x23 IPv4, 0x24 FQDN, 0x2E IPv6 in Qualcomm's layout: a count, then 16 bytes each); imsd-pcscf is the socket, the service lookup and the sequence, and prints the list, one address per line; nothing runs it yet. It sends no Start Network and no Stop Network; the bearer stayed connected and the registration stood after its runs (the fp6 journal's probe capture 04, benches 38 and 39). The build, the CI cross-compile, the tarball and the apk gain the product; linux-headers is named in the sysroot for <linux/qrtr.h>. Tested: crafter-build test, 8 passed; the aarch64 build of this commit's helper on the dev phone (KPN) against the live ims bearer.
This commit is contained in:
parent
40a960f749
commit
a89ca5a60c
10 changed files with 701 additions and 25 deletions
|
|
@ -91,6 +91,7 @@ crafter-build -- $XTARGET
|
|||
crafter-build -- --product=media $XTARGET
|
||||
crafter-build -- --product=dialerd $XTARGET
|
||||
crafter-build -- --product=ofonod $XTARGET
|
||||
crafter-build -- --product=pcscf $XTARGET
|
||||
crafter-build test
|
||||
|
||||
# --- bundle + package
|
||||
|
|
|
|||
Loading…
Reference in a new issue