Changes between Version 1 and Version 2 of Using_Standalone_ICE

Timestamp:

Mar 16, 2009 2:39:12 PM (15 years ago)

Author:

bennylp

Comment:

--

Using_Standalone_ICE

@@ -29 +29 @@
 The following are terms used throughout this article:
 
- '''ice_strans''' ::
- The ICE stream transport as explained above.
+ '''ICE stream transport (ice_strans)''' ::
+ This is the PJNATH ''class'' name for the transport that implement ICE negotiation, as explained above.
 
  '''ICE session''' ::
- One multimedia session (e.g. one '''call''' session) between two ICE endpoint, within the ''ice_strans''.
+ One multimedia session (e.g. one ''call'' session) between two ICE endpoints, within the ''ice_strans''. One ''ice_strans'' object may be reused to facilitate multiple ICE sessions (but not simultaneously).
 
  '''ICE endpoint''' ::
@@ -199 +199 @@
 
 [[BR]]
-=== Notes === #notes
+== Notes == #notes
 
 Note that the information below applies to current PJSIP release (version 1.1 as of 2009/03/16). They may change (and definitely will be improved if we can) in subsequent releases.
 
-==== Keep-alive ====
+=== Keep-alive ===
 
 Once the ''ice_strans'' is created, the STUN and TURN keep-alive will be done automatically and internally. The default STUN keep-alive period is 15 seconds (PJ_STUN_KEEP_ALIVE_SEC), and TURN is also 15 seconds (PJ_TURN_KEEP_ALIVE_SEC).
 
-==== IP address change ====
+=== IP address change ===
 
 Changes in STUN mapped address is handled automatically by ''ice_strans'' via the STUN keep-alive exchanges, although currently there is no callback to notify application about this event. Call to [http://www.pjsip.org/pjnath/docs/html/group__PJNATH__ICE__STREAM__TRANSPORT.htm#g597a3c3493038d8b37ff0a63e8ad93e5 pj_ice_strans_enum_cands()] will get the updated address.
@@ -215 +215 @@
 If IP address change is of application's concern, currently we can only recommend the application to implement this detection, and destroy/recreate the ''ice_strans'' once it detects the IP address change.
 
-==== Negotiation time ====
+=== Negotiation time ===
 
 ICE negotiation may take tens to hundreds of milliseconds to complete. The time it takes to complete negotiation depends on the number of candidates across all components in one single ''ice_strans'' and the round-trip between the two ICE endpoints. In our brief and non-scientific test, it took about 100-150 msec to complete, in scenario where two (SIP) endpoints were behind ADSL connection (both are in UK), with two components and 2-4 candidates per component.
@@ -221 +221 @@
 But please also note that '''it may take seconds''' for ICE to report negotiation failure. ICE will wait until all STUN retransmissions have timed-out, and with the default setting, it will take 7-8 seconds before it will report ICE negotiation failure.
  
-
 
 {{{