Changes between Version 8 and Version 9 of IPAddressChange


Ignore:
Timestamp:
Aug 26, 2011 7:40:10 AM (8 years ago)
Author:
bennylp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • IPAddressChange

    v8 v9  
    115115== Handling IP Change on iPhone == #iphone 
    116116 
    117 [Update 2011/01/26] 
     117[Update 2011/01/26][[BR]] 
    118118[Update 2011/08/26] 
    119119 
    120 TCP is preferred on iPhone because of the background feature, but it has been reported that simply re-registering after an IP address change is detected may not work, presumably because the TCP socket itself is already in bad state and is unable to communicate anymore. The following steps can be used to perform re-registration with a new TCP transport. For a demonstration, please apply {{{iphone_ip_change_pjsip_1_12.patch}}} attached (see the bottom of this page). The patch is tested on version pjsip-1.12. 
     120TCP is preferred on iPhone because of the background feature, but it has been reported that simply re-registering after an IP address change is detected may not work, presumably because the TCP socket itself is already in bad state and is unable to communicate anymore. The following steps can be used to perform re-registration with a new TCP transport. For a demonstration, please apply attachment:iphone_ip_change_pjsip_1_12.patch at the bottom of this page. The patch is tested on version pjsip-1.12. 
    121121 
    122122 0. You need to implement reachability API (sample is provided in the patch). With this API we can monitor the access point connection status and perform re-registration when necessary.