# Todo List **Module [aithinker_a6](group__aithinker__a6.md)** : In `dataConnectImpl()`: wait AT+CGATT? In `dtmfSendImpl()`: correctly handle the duration parameter In `modemGetConnected()`: correctly read the mux number **Module [digi_xbee](group__digi__xbee.md)** : In operator `GsmClientXBee::read()`: Read directly into user buffer? In `enterCommandMode()`: optimize this Add support for network time through the 'DT' command. Support uploading certificates using the [XModem library](https://github.com/gilman88/xmodem-lib) Implement baud rate forcing using a 6s serial break to temporarily enter command mode at 9600 and then switch to the desired baud rate. **Module [espressif_esp32](group__espressif__esp32.md)** : In `handleURCs()`: I'm not sure if each +IPD URC reports the amount newly received or the total now in the buffer. It appears to be the latter. **Class [GsmClient< modemType, tcpConfig >](class_gsm_client.md)** : In `GsmClient::connect()`, confirm that we can trust sock_connected at the start of a new connection before calling stop or if we should call stop regardless for static mux assignment. **Module [neoway_m590](group__neoway__m590.md)** : In `dataConnectImpl()`: configure DNS settings if needed In `dataDisconnectImpl()`: There is no command in AT command set In `modemConnect()`: no need for loop? **Module [quectel_bg96](group__quectel__bg96.md)** : In operator `GsmClientBG96::read()`: Read directly into user buffer? In `modemEndSend()`: Wait for ACK? (AT+QISEND=id,0 or AT+QSSLSEND=id,0) In `modemGetConnected()`: Verify mux **Module [quectel_m95](group__quectel__m95.md)** : In `modemEndSend()`: get len/ack properly In `modemRead()`: Does this even work???? **Module [quectel_mc60](group__quectel__mc60.md)** : In `modemEndSend()`: verify len/ack In `modemRead()`: Does this even work???? In `handleURCs()`: QIRD? or QIRDI? **Module [simcom_a7672x](group__simcom__a7672x.md)** : In GsmClientA7672X constructor: Ensure the secure socket mux isn't out of range In `getLocalIPSecure()`: figure out when to use each command properly In `deleteCertificateImpl()`: test In `dataDisconnectImpl()`: Should CCHSTOP come before NETCLOSE? Is it needed in addition to NETCLOSE? In `connect()` (secure path): verify the socket returned by CCHOPEN In `modemSend()`: make sure requested and confirmed bytes match **Module [simcom_sim7000ssl](group__simcom__sim7000ssl.md)** : In `configureSSLContext()`: Skip verifying the context number? **Module [simcom_sim7080](group__simcom__sim7080.md)** : In `configureSSLContext()`: Skip verifying the context number? **Module [simcom_sim7600](group__simcom__sim7600.md)** : In GsmClientSim7600 constructor: Ensure the secure socket mux isn't out of range In `dataDisconnectImpl()`: Should CCHSTOP come before NETCLOSE? Is it needed in addition to NETCLOSE? In `getGPSImpl()`: Can 1 be returned In `GsmClientSecureSim7600::connect()`: verify CCHOPEN In `modemSend()`: make sure requested and confirmed bytes match **Page [TinyGSM](index.md)** : Update size specs for TinyGSM **Struct [TinyGsmA7672XTcpConfig](group__simcom__a7672x.md)** : I think the number of TCP and SSL sockets are independent of each other and managed completely differently. That is, I think there can be two connection 0's, one using the SSL application on the module and the other using the TCP application on the module. Could someone who has a A7672x module test the real number of TCP and SSL connections that can be made at once? Handle the different number of sockets for TCP and SSL in the code. **Member [TinyGsmModem< modemType, modemConfig >::streamClear](class_tiny_gsm_modem.md#a7879aad8a0f9def7cd8d7450800b2d64) ()** : Should this be protected? **Member [TinyGsmModem< modemType, modemConfig >::streamDump](class_tiny_gsm_modem.md#a20ccc061bab4e038a8800c244e761ecd) (int16_t expected_len)** : Should this be protected? **Struct [TinyGsmSaraR4TcpConfig](group__ublox__sara__r4.md)** : Handle the different number of sockets for TCP and SSL in the code. **Struct [TinyGsmSim7000SSLTcpConfig](group__simcom__sim7000ssl.md)** : Handle the different number of sockets for TCP and SSL in the code. **Struct [TinyGsmSim7600TcpConfig](group__simcom__sim7600.md)** : I think the number of TCP and SSL sockets are independent of each other and managed completely differently. That is, I think there can be two connection 0's, one using the SSL application on the module and the other using the TCP application on the module. Could someone who has a SIM7600 module test the real number of TCP and SSL connections that can be made at once? Handle the different number of sockets for TCP and SSL in the code. **Struct [TinyGsmSim800TcpConfig](group__simcom__sim800.md)** : Handle the different number of sockets for TCP and SSL in the code. **Struct [TinyGsmSslConfigPreset< contextCount >](struct_tiny_gsm_ssl_config_preset.md)** : handle: - the number of SSL sockets supported by the modem - whether the socket numbering is shared between SSL and TCP sockets or separate - the SSL capabilities of the modem (e.g., whether it supports PSK, client certs, etc.) **Module [ublox_cellular](group__ublox__cellular.md)** : In `restartImpl()`: Verify delay timing here **Module [ublox_sara_r4](group__ublox__sara__r4.md)** : In `restartImpl()`: Verify delay timing here **Module [ublox_sara_r5](group__ublox__sara__r5.md)** : In `restartImpl()`: Verify delay timing here --- Generated by [Doxygen](https://www.doxygen.nl) and [m.css](https://mcss.mosra.cz/) with templates from [doxybook2](https://github.com/matusnovak/doxybook2)