Changes between Version 15 and Version 16 of IPv6

Timestamp:

Jul 27, 2017 7:26:28 AM (7 years ago)

Author:

ming

Comment:

--

IPv6

@@ -197 +197 @@
 Therefore, to support IPv6-IPv4 interoperability in NAT64 environment:
  1. Our RECOMMENDATION is that when the client is put with an IPv6-only connectivity, the SIP server must also support IPv6 connectivity. For the media, user needs a "dual stack" TURN (a TURN server which supports IPv6 connectivity and able to provide an IPv4 relay address upon request). Then all the application needs to do is enable ICE and use TURN (support for dual stack TURN is only available in PJSIP 2.6 or later).
- 2. If 1) is not possible (no IPv6 server or not desirable to use TURN), application needs to replace all IPv6 occurences with IPv4 in the SIP messages and SDP. To do this, you need to be able to synthesize IPv4 from IPv6 address. Apple provides the API getaddrindo() for this, however this is only specific to Apple, so may not be able to work on other platforms.
+ 2. If 1) is not possible (no IPv6 server or not desirable to use TURN), we will need to replace all IPv6 occurences with IPv4 in the SIP messages and SDP. This feature is available in release 2.7.
+  a. You need a STUN server which resides in an IPv4 network. Then set your {{{pjsua_config}}} to try IPv6 resolution of the STUN servers.
+  b. Create UDP6 transport to get an IPv4-mapped address from the above STUN server.
+  c. Bind account to a specific IPv6 transport, and enable IPv6 in media transport.
+  d. Set account's NAT64 option to PJSUA_NAT64_ENABLED.
+{{{
+cfg->stun_try_ipv6 = PJ_TRUE;
+
+tp_type = PJSIP_TRANSPORT_UDP6;
+status = pjsua_transport_create(tp_type, &tp_cfg, &udp6_tp_id);
+
+acc_cfg.transport_id = udp6_tp_id; // or tcp6_tp_id or tls6_tp_id
+acc_cfg.ipv6_media_use = PJSUA_IPV6_ENABLED;
+
+acc_cfg.nat64_opt = PJSUA_NAT64_ENABLED;
+  }}}