| Why the Gateway doesn't react on GET retransmission |  Search
|
|
NowSMS Support Forums ⬆ Now.WAP Proxy Support ⬆ Archive through October 01, 2008 ⬆ |
◄ ► |
| Author | Message | |||
| Nabil OUALI New member Username: Nabixm Post Number: 1 Registered: 07-2007 |
Hi, After the GET is sent, the Gateway responds with 3 PDUs (0,1,2). The mobile is not receiving anything so it sends again a new GET, but the Gateway doesn't take it into consideration and it retransmits only the last PDU (PDU2) after a fixed timer (10s). Can you please tell me if there's a way to retransmit data after reception of a retransmitted GET or decrease this timer (10s). thank you very much | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7334 Registered: 10-2002 |
Hi, Are you asking this question in the context of being a software developer for the client? Or are you asking as an end-user/IT professional? If the client actually sees SAR PDU #2, and the TTR or GTR flag is set in this PDU (which I assume to be the case), but the mobile does not have PDU #0 or #1, then the client should send back a NACK indicating that it is missing packets #0 and #1. I suspect either the client does not understand SAR (segmentation and re-assembly), or the client is not actually seeing PDU #2, including the retransmitted copies. There is not a setting to trigger retransmission after receipt of a retransmitted GET. There are settings that can be used to control segment size, the number of segments per group, and timeouts. I do recommend extreme caution in using these settings. Under the [WAPGW] section header of WAPGW.INI, the following settings are valid: WTPSarSegmentSize=1400 (# of bytes per segment) WTPSarWindowSize=3 (# of segments in a group) WTPSarAckTimeoutResend=8 (# of seconds to wait before resending when sending a segmented reply) WTPSarAckTimeout=90 (# of seconds of no ack/nack before aborting a segmented reply) WTPAckTimeoutResend=5 (# of seconds to wait for ack on single segment reply) WTPAckTimeout=90 (# of seconds of no ack before aborting a single segment reply) My suspicion is that the mobile phone is not seeing any of the PDUs in the response. you might want to try setting the WTPSarWindowSize=1, and see if that makes a difference. If it doesn't make a difference, then that suggests that something else is wrong. -bn | |||
