Changes between Version 7 and Version 8 of Symbian_AP_Reconnection


Ignore:
Timestamp:
Feb 25, 2009 5:57:52 PM (10 years ago)
Author:
bennylp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Symbian_AP_Reconnection

    v7 v8  
    106106This is a problem with the socket in general and not PJSIP. Below are steps to reproduce with a plain UDP socket: 
    107107 1. Create RConnection, call Start() to connect to AP 
    108  1. Create UDP socket, call !SendTo() to send a packet 
    109  1. Disconnect the AP (Menu -> Connectivity -> Conn. mgr. -> Active data connections -> (highlight the AP) -> Options (menu) -> Disconnect). 
    110  1. Call udp.!SendTo() again 
    111  1. AP selection dialog appears, select different AP 
    112  1. !WaitForRequest() to the udp.!SendTo() operation now '''will get stuck for 1-2 minutes'''. 
    113  1. Now if you call udp.!SendTo() again, now !WaitForRequest() will get stuck indefinitely 
     108 2. Create UDP socket, call !SendTo() to send a packet 
     109 3. Disconnect the AP (Menu -> Connectivity -> Conn. mgr. -> Active data connections -> (highlight the AP) -> Options (menu) -> Disconnect). 
     110 4. Call udp.!SendTo() again 
     111 5. AP selection dialog appears, select different AP 
     112 6. !WaitForRequest() to the udp.!SendTo() operation now '''will get stuck for 1-2 minutes''' before ''tcpip6_error_NoRoute'' error (-5105) is returned. 
     113 7. Now if you call udp.!SendTo() again, now !WaitForRequest() will get stuck indefinitely 
    114114 
    115115The problem above does not occur if: 
     
    117117 - the user cancels the AP selection dialog. In this case the udp.!SendTo() will fail immediately with KErrCancel without blocking the application. 
    118118 - the socket is closed and re-opened. In this case the udp.!SendTo() should complete successfully 
     119 
     120As additional info: 
     121 - the problem still persists even if the RConnection is restarted (RConnection.Start() is called to select new AP) in between step 3 and 4 above. 
     122 
    119123 
    120124Currently we don't have a solution for this, except to only use one AP (perhaps to select the AP when PJSIP is started and lock the RConnection that is assigned to PJLIB to this AP).