Changes between Version 4 and Version 5 of IPAddressChange

Timestamp:

Mar 9, 2011 11:23:52 PM (14 years ago)

Author:

bennylp

Comment:

--

IPAddressChange

@@ -77 +77 @@
 ==== Call in progress issues ====
 
- '''Task:''' ::
+ '''Task 1:''' ::
  Dialog's Contact URI needs to be updated.
 
@@ -98 +98 @@
 
 
- '''Task:''' ::
+ '''Task 2:''' ::
  Changing of RTP/RTCP media addresses of ongoing call
 
@@ -107 +107 @@
 
  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.
- - Note: by default we bind transports to INADDRANY/0.0.0.0, so when sending outgoing (UDP) packets, we rely on the OS to select the correct interface for us, based on what interfaces are currently online and the OS's internal routing table. In other words, we just call {{{sendto()}}} and let the OS "do the right thing". In case of IP address change, we are also relying on the OS to switch the interface from one interface to the new one for our UDP transmissions.
+
+ - Note:
+     * by default we bind transports to INADDRANY/0.0.0.0, so when sending outgoing (UDP) packets, we rely on the OS to select the correct interface for us, based on what interfaces are currently online and the OS's internal routing table. In other words, we just call {{{sendto()}}} and let the OS "do the right thing". In case of IP address change, we are also relying on the OS to switch the interface from one interface to the new one for our UDP transmissions.
 
 [[BR]]