Ticket #120 (new enhancement)

Opened 17 months ago

Last modified 17 months ago

Use one TLS transport per account

Reported by: adigeo Owned by: support@ag-projects.com
Priority: minor Milestone: 3rd
Component: SIP core Version: trunk
Keywords: Cc:

Description

Use a tls transport per account

The Engine currently runs one TLS transport which is initialized with the settings of the current default_account. In reality, there should be one tls transport for each account. It seems there might be support for this at the pjsip level.

Design notes

  • As the account settings change, its TLS transport needs to be changed as well
  • The account will need to know when the TLS transport gets re-initialized because it should then refresh it registration/subscriptions/publishes etc.
  • It might be the case that the account needs to manage its own TLS transport (thus the core should offer a suitable API for doing this)

Change History

comment:1 Changed 17 months ago by adigeo

  • Milestone changed from Future to Nice to have
Note: See TracTickets for help on using tickets.