Changes between Version 1 and Version 2 of IPAddressChange-2.7

Timestamp:

Sep 30, 2019 7:22:51 AM (4 years ago)

Author:

riza

Comment:

--

IPAddressChange-2.7

@@ -44 +44 @@
 Related to maintaining a call during IP change, there are some scenarios that are currently not implemented by IP change mechanism, so application needs to handle manually:
 If IP change occurs during SDP negotiation (and it is not completed yet, so there cannot be another SDP offer), updating such call needs to be done in two steps:
-First, updating Contact header, so remote endpoint can send its SDP answer to our new contact address, i.e: use UPDATE without SDP offer ({{{PJSUA_CALL_NO_SDP_OFFER}}} flag). 
+1. Update Contact header, so remote endpoint can send its SDP answer to our new contact address, i.e: use UPDATE without SDP offer ({{{PJSUA_CALL_NO_SDP_OFFER}}} flag). Note that, not every endpoint supports UPDATE. Contact is used by remote to 
+   resolve target before sending new requests. If proxy is used, then you can probably skip this.
+2. Update local media transport after SDP answer is received, by sending UPDATE/re-INVITE with {{{PJSUA_CALL_REINIT_MEDIA}}} flag.
 
-Note that, not every endpoint supports UPDATE. Contact is used by remote to resolve target before sending new requests. If proxy is used, then you can probably skip this.
-Update local media transport after SDP answer is received, by sending UPDATE/re-INVITE with {{{PJSUA_CALL_REINIT_MEDIA}}} flag.
 If IP change occurs before a call is established, there are two possible cases:
 Dialog is not yet created, since response with To tag is not received yet. The call needs to be cleared and reported to application via {{{on_call_state().}}}
 Dialog is created, (1xx response with To tag is received).
  - SDP nego is done, then update Contact and SDP is needed using re-INVITE or UPDATE.
- - SDP nego is not done, see point 2 above.
+ - SDP nego is not done, see the steps above.
+