Opened 10 years ago

Last modified 6 weeks ago

#647 new defect

Assign STUN and TURN as default candidate only when the resolution/allocation is complete (thanks Stephen D. Strowes for the suggestion)

Reported by: bennylp Owned by: bennylp
Priority: minor Milestone: Known-Issues-and-Ideas
Component: pjnath Version: trunk
Keywords: Cc:
Backport to 1.x milestone: Backported: no

Description

Quoting Stephen's email:

At the moment, the default seems to be set while possibly still pending
full initialisation (e.g., if I set stun-srv, the default_cand is set to
indicate that this is the default candidate while STUN is still pending
a response; if a response never arrives, then the default candidate addr
is 0.0.0.0, and things may then fall over on attempting a call).


Would it make more sense to only set the default candidate to the HOST
address on init, and then subsequently set the default candidate inside
the stun_on_status() and turn_on_status() functions, if a more
appropriate default becomes available?

Change History (3)

comment:1 Changed 10 years ago by bennylp

  • Milestone changed from release-1.0 to Known-Issues

comment:2 Changed 9 years ago by bennylp

  • Type changed from enhancement to defect

comment:3 Changed 6 weeks ago by nanang

  • Backported unset

TeluuCon2019: a valid issue, solution: only update the default candidate to STUN candidate when STUN binding has been completed successfully (like in TURN).

Note: See TracTickets for help on using tickets.