Changes between Version 2 and Version 4 of Ticket #1412


Ignore:
Timestamp:
Aug 1, 2012 4:07:53 AM (7 years ago)
Author:
bennylp
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1412

    • Property Summary changed from Add media transport preferences (STUN, ICE settings) to account setting (thanks Régis Montoya for the suggestion) to Add transport preferences (STUN, ICE settings) to account setting (thanks Régis Montoya for the suggestion)
  • Ticket #1412 – Description

    v2 v4  
    1 With #539 it is now possible to configure media transport settings on per account basis. This is needed for example when application is supporting multiple accounts where one is connecting through Internet and the other is through VPN. The specification is as follows. 
     1With #539 it is now possible to configure STUN, ICE, and TURN settings on per account basis. This is needed for example when application is supporting multiple accounts where one is connecting through Internet and the other is through VPN. The specification is as follows. 
    22 
    3 ==== Configurations ==== 
     3==== New STUN setting arrangements ==== 
    44 
    5 STUN, ICE, and TURN configurations will be added to {{{pjsua_acc_config}}} with the default values values taken from the {{{pjsua_config}}} and {{{pjsua_media_config}}}. The settings in the {{{pjsua_acc_config}}} are the ones that will actually be used. 
     5The STUN server settings are still in the global {{{pjsua_config}}}. New settings are introduced in the account config to disable or enable STUN for either SIP or media transports: {{{sip_stun_use}}} and {{{media_stun_use}}}.  
     6 
     7Rationale: 
     8 
     9 This simple arrangement is chosen over providing full STUN server settings in the account config, i.e. having the list of servers in the account config as well as in the global config. There are several difficulties with the complex approach: 
     10   - The STUN servers in the account will need to be rechecked, and this most likely will need to block the {{{pjsua_acc_add()}}}. 
     11   - We need the STUN server when creating SIP UDP transport. Which STUN server to use? We definitely cannot use account's STUN server(s), because account is created later! Hence we need to provide yet another list of STUN servers in the transport config, and possibly need to recheck them too. 
     12 
     13==== ICE and TURN settings per account ==== 
     14 
     15ICE and TURN configurations will be added to account config with the default values values taken from the global media config. Media transport creation will look for the value in account config. 
    616 
    717==== Contact header generation ==== 
    818 
    9 The generation rule of the Contact header value doesn't change, apart from the fact that STUN setting is now account specific. 
     19The initial value of Contact header will take into account whether STUN is enabled or disabled in the account. Subsequent update to the Contact header doesn't change. 
    1020 
    1121==== Via sent-by generation ====