Scenario:
-
REGISTER to --oubound URL successful, gets received/rport
-
Proxy IP address changes due to round-robin DNS
-
INVITE -> new transport so Via header uses local IP address
-
<- 407 (includes new received/rport)
-
INVITE -> does not update IP address/port: still uses local IP
address in Via header; ignores received/rport from 407
-
CANCEL -> due to fix #1996 , uses original received/rport from
REGISTER transport
-
INVITE and CANCEL Via mismatch.
This is like the reverse of issue #1996 where the fix now causes Via
mismatch in the transaction.
Anthony
Scenario:
1. REGISTER to --oubound URL successful, gets received/rport
2. Proxy IP address changes due to round-robin DNS
3. INVITE -> new transport so Via header uses local IP address
4. <- 407 (includes new received/rport)
5. INVITE -> does not update IP address/port: still uses local IP
address in Via header; ignores received/rport from 407
6. CANCEL -> due to fix #1996 , uses original received/rport from
REGISTER transport
7. INVITE and CANCEL Via mismatch.
This is like the reverse of issue #1996 where the fix now causes Via
mismatch in the transaction.
Anthony
