Changes between Version 4 and Version 5 of Ticket #1412


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

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1412 – Description

    v4 v5  
    11With #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 ==== New STUN setting arrangements ==== 
     3== New STUN setting arrangements == 
    44 
    55The 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}}}.  
    66 
    7 Rationale: 
     7 Rationale: :: 
     8  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: 
     9      - The STUN servers in the account will need to be rechecked, and this most likely will need to block the {{{pjsua_acc_add()}}}. 
     10      - 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. 
    811 
    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 ==== 
     12== ICE and TURN settings per account == 
    1413 
    1514ICE 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. 
    1615 
    17 ==== Contact header generation ==== 
     16== Contact header generation == 
    1817 
    19 The 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. 
     18The initial value of Contact header will take into account whether STUN is enabled or disabled in the account. If it is disabled, local IP will be used. 
    2019 
    21 ==== Via sent-by generation ==== 
     20Subsequent update to the Contact header doesn't change. 
     21 
     22== Via sent-by generation == 
    2223 
    2324'''Initial''' Via {{{sent-by}}} value now will be affected by STUN setting. Subsequent update of the value doesn't change; it follows the rules in #1537. 
    2425 
    25 ==== Media transports ==== 
     26== Media transports == 
    2627 
    2728STUN, ICE, and TURN setup of the media transports now will follow the account config settings instead.