Ticket #647 (new defect)

Opened 10 years ago

Last modified 9 years ago

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:


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, 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

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
Note: See TracTickets for help on using tickets.