Opened 9 years ago

Closed 9 years ago

#1095 closed enhancement (fixed)

New option to control the Route headers in the REGISTER request (thanks Henrik Envall for the suggestion)

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

Description (last modified by bennylp)

Currently the REGISTER request will be sent with Route header(s), if outbound proxies are set in the global config or proxies are set in the account config.

Some provider would like the REGISTER to be sent directly to the registrar, and this is not possible with existing settings.

This ticket adds a new account option to control if and how the Route headers will be added to the REGISTER request.

Change History (2)

comment:1 Changed 9 years ago by bennylp

  • Description modified (diff)
  • Summary changed from New option to bypass the account proxy setting in the registration to New option to control the Route headers in the REGISTER request (thanks Henrik Envall for the suggestion)

comment:2 Changed 9 years ago by bennylp

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

(In [3216]) Fixed #1095 (New option to control the Route headers in REGISTER request). Details:

  • added new account config setting: reg_use_proxy. This contains bitmask values to indicate whether outbound proxies and account proxies are to be added in the REGISTER request. Default value is to add both.
  • added new pjsua cmdline option to control this: --reg-use-proxy
  • miscellaneous minor fixes in other pjsua cmdline arguments
Note: See TracTickets for help on using tickets.