| A quesiton about wtp wait timout interval |  Search
|
|
NowSMS Support Forums ⬆ WAP Technical Discussions (unsupported) ⬆ Archive through December 08, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Shawn Pan |
when i want to send a mms to gateway.the program is : wsp connect: wtp invoke(send) --------> (receive) <-------wtp result (send) wtp ack ----------> *** wait timeout interval*** wsp post: wtp invoke(send) --------> (receive) <-------wtp result (send) wtp ack ----------> but ,why the "wait timeout interval" is so long ,according to the different bearer,the value is 300 (gsm sms),60(gsm ussd),40 seconds(ip,e.g. GPRS,CDMA...).That means,if sending a mms through GPRS,i should wait 40 seconds after i connect the gateway,then i can "post" the mms,really? why the time is so long?please tell me. thanks very much. | |||
| Bryce Norwood - NowSMS Support |
Where are you seeing this "wait timeout interval" documented? If you can give me a documentation reference, perhaps I can explain. I certainly cannot see any reason to wait 40 seconds. | |||
| Bryce Norwood - NowSMS Support |
Ok. I searched the WAP specs, and I see the reference to "wait timeout interval" in the WTP specifications. I guess I see what you mean based upon Section 9.5 of the specification. It certainly looks like you enter a wait timeout state after you send the ACK. Of course, this doesn't necessarily mean that you couldn't start another transaction (especially if MOR > 1). But even if MOR=1, I really don't see the necessity to wait here. I've looked at a lot of protocol analyser logs with different WAP clients and different WAP gateways, and I've never seen an implementation that paused that long. I think what the spec is saying is that information about the transaction should be kept alive for the "wait timeout interval", so that if another packet is received for that transaction, it can be handled appropriately. But I don't see why you should delay starting another transaction. | |||
| Anonymous |
Hi,thanks for your answer,but the question is still exiting.Once i meet a thing,i connect the gateway,receive the connect reply pdu(wtp result pdu),then i send a wtp ack, after this,i don't wait and send a WSP post pdu at once,but 10 seconds later,i received the retransmitted pdu of wtp result pdu,means the ack i sent has been lost. so,not only i should retransmit the ack,but also the post pdu are also wasted.to avoid this thing,i think i should wait for"wait timeout interval"and make sure that the ack has been recieved by the gateway, then i can start another transaciton. i think it is improper for me to retransmit the ack pdu and post pdu at the time when wsp status has been set as SESSION CONNECTED.Can you give me some advise? thanks again. | |||
