Changes between Version 6 and Version 7 of Symbian_AP_Reconnection

Timestamp:

Feb 25, 2009 5:40:13 PM (15 years ago)

Author:

bennylp

Comment:

--

Symbian_AP_Reconnection

@@ -101 +101 @@
 
 === Socket call get stucked after reconnecting to different access point (AP) ===
-Steps to reproduce:
+ '''Symptom:''' ::
+ The library gets stucked in {{{pjsua_destroy()}}} when the application tries to destroy the stack when it detects that the AP connection is down. 
+
+This is a problem with the socket in general and not PJSIP. Below are steps to reproduce with a plain UDP socket:
  1. Create RConnection, call Start() to connect to AP
  1. Create UDP socket, call !SendTo() to send a packet
@@ -115 +118 @@
  - the socket is closed and re-opened. In this case the udp.!SendTo() should complete successfully
 
-The implication of above symptom is the library may get stucked in {{{pjsua_destroy()}}} when the application tries to destroy the stack when it detects that the AP connection is down. 
-
 Currently 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).