Changes between Version 2 and Version 3 of IPAddressChange

Timestamp:

Mar 9, 2011 10:57:22 PM (13 years ago)

Author:

bennylp

Comment:

--

IPAddressChange

@@ -8 +8 @@
 
 '''Table of Contents'''
-[[PageOutline(1-4,,inline)]]
+[[PageOutline(2-4,,inline)]]
 
 This article describes some issues and their corresponding solutions related to access point disconnection, reconnection, IP address change, and how to handle these events in your PJSIP applications. The general issues related to the discussion will be explained, along with some specific issues to Symbian applications.
@@ -83 +83 @@
  The dialog's Contact URI is set initially when the dialog is created, from the account's Contact URI. While at the PJSIP level the {{{pjsip_inv_reinvite()}}} allows changing of Contact URI via the {{{new_contact}}} argument, currently this feature is not used by PJSUA-LIB, i.e. the {{{pjsua_call_reinvite()}}} does not allow the application to change the Contact URI.
 
- So this is an open issue.
+ As a workaround, application may #include {{{<pjsua-lib/pjsua_internal.h>}}} and perform the reinvite manually, as the snippet below shows:
+ {{{
+pjsip_tx_data *tdata;
+pj_str_t new_contact;
+pjsip_inv_sessin *inv = pjsua_var.calls[call_id].inv;
+
+new_contact = pjsua_var.acc[account_id].contact;
+status = pjsip_inv_reinvite(inv, &new_contact, NULL, &tdata);
+if (status==PJ_SUCCESS)
+    pjsip_inv_send_msg(inv, tdata);
+ }}}
+
+ 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).
+
 
  '''Task:''' ::
@@ -93 +106 @@
    - the media was previously inactive, since if media has been active (hence ICE session is active), the SDP will contain only the used candidates and not all the list of candidates.
 
- Alternatively, '''we may not need to inform the new RTP/RTCP address at all'''. If the remote media endpoint has the capability to switch its RTP/RTCP transmission to the source address of the RTP/RTCP packets (note: PJMEDIA has this capability), then it should automatically switch its destination address to our new address.
-
+ Alternatively, '''we may not need to inform the new RTP/RTCP address at all'''. If the remote media endpoint has the capability to switch its RTP/RTCP transmission to the source address of the RTP/RTCP packets (note: PJMEDIA has this capability), then it should automatically switch its destination address to our new address, provided that the source address of our RTP/RTCP packets (as viewed by the remote peer) have indeed changed.