Changes between Version 9 and Version 10 of IPAddressChange

Timestamp:

Jan 9, 2013 8:25:35 AM (10 years ago)

Author:

nanang

Comment:

Media transports recreation not necessary in 2.0 and PJSUA allow reinvite with contact update since 1.10

IPAddressChange

@@ -74 +74 @@
  If ICE is not used, then at present there is no mechanism to update the IP address of media transport, nor the media transport will update its address even when STUN is used. ~~~The only solution would be to recreate the media transports and supply them to PJSUA-LIB with {{{pjsua_media_transports_attach()}}}.~~~ You need to call {{{pjsua_media_transports_create()}}} to recreate the media transports.
 
+ '''Update''': since 2.0, media transports are created on demand, so recreating media transports is no longer necessary, see [wiki:ReleaseNotes-2.0#OnDemandMediaTransport On Demand Media Transport].
+
 
 ==== Call in progress issues ====
@@ -96 +98 @@
 
  Note that the usual caveats of including <pjsua_internal.h> apply (i.e. this is not public API and things may change in future releases).
+
+ '''Update''': since 1.10 or 2.0, application using PJSUA can update dialog Contact URI by specifying {{{PJSUA_CALL_UPDATE_CONTACT}}} flag in option parameter of {{{pjsua_call_reinvite()}}}, the corresponding ticket is #1209.
 
 
@@ -318 +322 @@
 </td></tr></table>
 }}}
-