| MM1 via WSP - responder re-transmits Ack |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Gary Chapman Unregistered guest |
Hi all, I'm trying to send a large message via MM1 (WSP). After I send the 2nd packet, the responder re-transmits the Ack for the first packet. Can anyone suggest a reason for this? --- Connect (send): 0A 00 00 12 01 10 0A 04 04 80 8F F8 00 04 81 8F F8 00 80 BE 80 80 Connect Reply (recv): 12 80 00 02 87 46 00 00 Connect Reply Ack (send): 18 00 00 Packet 0 (send): 0C 00 01 12 60 22 20 68 74 ... Packet 0 Ack (recv): 98 80 01 19 00 Packet 1 (send): 2C 00 01 01 ... Packet 0 Ack again (recv): 99 80 01 19 00 <--- Why would the responder re-transmit an Ack? Is it expecting me to Ack the original Ack?! --- Thanks, Gary | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3809 Registered: 10-2002 |
You're doing a segmented invoke. The responder is telling you that the last packet of the segmented invoke that it received and understood was 00. Either the responder did not receive your packet 1 ... or it did not understand it. Therefore it is resending the last ack, in case you did not receive it. This is standard SAR behaviour. -bn | |||
