Opened 16 years ago

Closed 16 years ago

Last modified 5 years ago

#643 closed enhancement (fixed)

Consider the server IP address before trying to re-register with a new Contact when the REGISTER response contains different IP address

Reported by: bennylp Owned by: bennylp
Priority: normal Milestone: release-1.0-rc3
Component: pjsua-lib Version: trunk
Keywords: Cc:
Backport to 1.x milestone: Backported: no

Description

Ticket #409 (from 0.8.0 milestone) adds the feature to automatically re-register the account if the Via address in the 200/OK response to REGISTER contains different address than the one being registered as Contact header.

This feature is intended to work with symmetric NATs.

However there are cases where this feature do not work very well. Some NAT in the middle might mess up with the SIP/SDP addresses, and eventhough the initial REGISTER request contains public address in the Via header, the router may change the Via header in the response back to the private IP, causing the client to re-register using the private IP.

Attachments (1)

NAT switch.txt​ (1.3 KB) - added by bennylp 16 years ago.

Download all attachments as: .zip

Change History (5)

comment:1 Changed 16 years ago by bennylp

  • Summary changed from Option to not try to re-register with a new Contact when the REGISTER response contains private IP address to Do not try to re-register with a new Contact when the REGISTER response contains private IP address

comment:2 Changed 16 years ago by bennylp

  • Resolution set to fixed
  • Status changed from new to closed

Done in r2316:

  • we will not switch if the Contact and server IP are in public network but the address in Via header contains private IP

comment:3 Changed 16 years ago by bennylp

  • Summary changed from Do not try to re-register with a new Contact when the REGISTER response contains private IP address to Consider the server IP address before trying to re-register with a new Contact when the REGISTER response contains different IP address

Changed 16 years ago by bennylp

comment:4 Changed 5 years ago by nanang

  • Backported unset

In r2325:

  • added setting to disable this ticket (by setting allow_contact_rewrite to 2)
Note: See TracTickets for help on using tickets.