Ticket #2078 (closed enhancement: fixed)

Opened 12 months ago

Last modified 3 months ago

Revisit IPv4/IPv6 settings and behavior in pjsua

Reported by: ming Owned by: bennylp
Priority: normal Milestone: release-2.8
Component: pjsua-lib Version: trunk
Keywords: Cc:
Backport to 1.x milestone: Backported: no

Description (last modified by riza) (diff)

Currently, in the account settings, SIP and media has to be predetermined whether it wants to use a particular IP version, IPv4 or IPv6. As a result, typically two accounts are required for each IP version, one for IPv4, and one for IPv6.

It is desirable that a more flexible/smart detection mechanism is employed, such as:

  • Ability to handle both IP versions in SIP and media, especially in the case of incoming offer where we can check what the remote wants.
  • Specify a preference of one IP version over the other, but still can handle both.
  • Match the IP version for SIP and media, i.e. if SIP signalling is done via IPv6, then media will also use IPv6.

Thanks to Alexander Traud for the suggestion.

Will be continued in #2146

Change History

comment:1 Changed 8 months ago by nanang

In 5784:

Re #2078: Bind local account to the specified transport (thanks Kyle Kurz for the report and the patch).

comment:2 Changed 3 months ago by riza

  • Status changed from new to closed
  • Resolution set to fixed
  • Description modified (diff)
Note: See TracTickets for help on using tickets.