Changes between Initial Version and Version 1 of Ticket #2134


Ignore:
Timestamp:
May 2, 2019 6:41:42 AM (5 years ago)
Author:
ming
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2134

    • Property Summary changed from STUN IPv4 resolution failure causes delay to STUN server resolution failure causes delay

  • Ticket #2134 – Description

    initial v1  
    2525}}} 
    2626 
    27 The issue is caused by ticket #1962 which directly returns without setting any error status after failure, to prevent double destruction. However, setting a final error status is also not desirable since if IPv4 fails, we still need to try IPv6 resolution. 
     27The issue is caused when DNS resolution (pj_dns_srv_resolve() ) in pj_stun_sock_start() returns synchronously and the DNS resolution callback has been called. However, there is currently no mechanism to propagate the error from inside the callback to stun_sock, thus pj_stun_sock_start() will always return PJ_SUCCESS. This causes pjsua STUN server resolution to continue waiting until it times out. 
     28 
     29(Note that this issue first appears because of ticket #1962, which directly returns without setting any error status after synchronous failure, to prevent double destruction.) 
    2830 
    2931Thanks to Imad Khazali for the report and analysis.