Changes between Version 10 and Version 11 of IPv6


Ignore:
Timestamp:
Jun 8, 2016 8:20:45 AM (8 years ago)
Author:
nanang
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • IPv6

    v10 v11  
    8686 - the {{{rem_addr}}} and {{{rem_rtcp}}} fields in {{{pjmedia_stream_info}}} also have been changed to use {{{pj_sockaddr}}} union. 
    8787 
    88 == IPv6 Support in pjnath (STUN and ICE) == 
    89  
    90 To be done. 
     88== IPv6 Support in pjnath (ICE) == 
    9189 
    9290The work for adding IPv6 support in pjnath is documented by ticket #422. 
    9391 
     92STUN and TURN transports support IPv6 already, and now ICE stream transport support IPv6 too. Also, ICE stream transport has been updated to be able to have multiple STUN and TURN transports and each STUN/TURN transport may use either IPv4 and IPv6. 
     93 
     94Modifications in {{{pj_ice_strans_cfg}}}: 
     95 - Deprecated {{{af}}} field, if it is set, the value will be ignored, address family setting is now specified via STUN/TURN transport setting, i.e: {{{stun_tp.af}}} and {{{turn_tp.af}}}. 
     96 - Deprecated {{{stun}}} and {{{turn}}} fields, but for backward compatibility, those fields will still be used only if {{{stun_tp_cnt}}} and/or {{{turn_tp_cnt}}} is set to zero. 
     97 - Added {{{stun_tp}}} and {{{turn_tp}}} as replacement of {{{stun}}} and {{{turn}}} respectively, and they are array so application can have multiple STUN/TURN transports. 
     98 - Added function {{{pj_ice_strans_stun_cfg_default()}}} and {{{pj_ice_strans_stun_cfg_default()}}} to initialize {{{stun_tp}}} and {{{turn_tp}}} respectively with default values. 
     99 - Added compile-time settings {{{PJ_ICE_MAX_STUN}}} and {{{PJ_ICE_MAX_TURN}}} to specify maximum number of STUN/TURN transports in each ICE component. 
    94100 
    95101== Enabling IPv6 support in application using PJSUA == #appusingpjsua