> 10.14.4 | Socket Client Sends Data via TCP Connection (Polling Mode)

> The example uses service profile 0 configured for Socket service and TCP.

> AT^SISO=0 | The host opens service profile 0.
> OK | Note: URC ^SISW:0, 1 does not appear! The host must poll the service state by means of AT^SISI until the service is in <srvState> "Up".
> AT^SISI=0
> ^SISI: 0,3,0,0,0,0 | The service is still in <srvState> "Connecting".
> OK
> AT^SISI=0
> ^SISI: 0,4,0,0,0,0 | The service is now in <srvState> "Up" and is ready to accept data.
> OK
> AT^SISW=0,10 | The host requests to write 10 bytes.
> ^SISW: 0,10,10 | Response that 10 bytes can be sent and are unacknowledged.
> 0123456789
> OK
> AT^SISW=0,10,1 | The host requests to write next 10 bytes and enables the end-of-data flag.
> ^SISW: 0,0,10 | But the service refuses the request, even the end-of-data flag remains without effect.
> OK
> AT^SISW=0,10,1 | Next try (polling).
> ^SISW: 0,10,20 | Response that the service accepts 10 bytes and this data and the previously sent data are unacknowledged.
> 0123456789
> OK
> AT^SISW=0,0,0 | Polling to request unacknowledged data.
> ^SISW: 0,0,10 | There are 10 bytes still unacknowledged.
> OK
> AT^SISI=0 | Polling for <srvState> change ("Closing" -> "Down").
> ^SISI: 0,5,0,20,10,10 | 20 bytes are transfered via serial interface, 10 bytes are acknowledged by remote peer, 10 bytes are on the way.
> OK
> AT^SISI=0 | Polling for <srvState> change ("Closing" -> "Down").
> ^SISI: 0,6,0,20,20,0 | The Service is in state "Down" and all data is confirmed by the remote peer.
> OK
> AT^SISC=0 | Closing the Socket service.
> OK