"Julien Buratto" <kannel 'at' linkas.it> writes: > With my smsc we are trying to debug some problems upon transmissions > (strange chars) > > After some tests, the engineer says I have a tcp error when talking to his > smsc, and he sent me this trace: > ---------------------------------------------------------------------------- > ---- > > TCPtrace RCV packet 6365 at 7-JUL-2004 12:32:22.40 > > IP Address Port Seq # Ack # > > Source 10.97.22.130 9000 1727127392 3807603810 > Destination 10.97.11.98 5002 > > Packet Length 40 > TCP flags FIN ACK > window 11792 > > Hex Count Ascii > -------- -------- -------- -------- ---- ---------------- > 8216610A 57E9063C 0040D31E 28000045 0000 E..([EMAIL PROTECTED]<..W.a.. > 626CF3E2 60DFF166 8A132823 | 620B610A 0010 .a.b#(..f..`..lb > 0000 00000000 | 0000C37E 102E1150 0020 P...~......... > > The engineer says that they receive my FIN ACK before they can send an ACK > so the trasmission get confused. > > Can anyone help ?
Hum.. The TCP protocol is handled at the kernel level. Programs such as Kannel build and control network access with the socket interface. It must be possible to "hack" the contents of a TCP transmission with enough permissions, but I don't think this is what Kannel is doing :). A quick look at the EMI implementation seems to confirm that. -- Guillaume Cottenceau
