
| 
 | SIP Release Notes | 1. What's New in Release 6.2 | 
 | 
| 
 | 
 | 
 | 
 | 
| 
 | Parameter | Description | 
 | 
| 
 | 
 | 
 | 
 | 
| 
 | Flash Keys Sequence Style | Modification: Option [2] added  | 
 | 
| 
 | [FlashKeysSequenceStyle | MSBG, Mediant 1000 MSBG, Mediant 1000). | 
 | 
| 
 | ] | Hook flash keys sequence style. | 
 | 
| 
 | 
 | [0] 0 = Flash hook (default) - only the phone's Flash button is used, | 
 | 
| 
 | 
 | according to the following scenarios: | 
 | 
| 
 | 
 | During an existing call, if the user presses Flash, the call is put | 
 | 
| 
 | 
 | on hold; a dial tone is heard and the user is able to initiate a | 
 | 
| 
 | 
 | second call. Once the second call is established,  | 
 | 
| 
 | 
 | transfers the first (held) call to the second call. | 
 | 
| 
 | 
 | During an existing call, if a call comes in (call waiting), pressing | 
 | 
| 
 | 
 | Flash places the active call on hold and answers the waiting | 
 | 
| 
 | 
 | call; pressing Flash again toggles between these two calls. | 
 | 
| 
 | 
 | [1] 1 = Sequence of Flash Hook and digit: | 
 | 
| 
 | 
 | Flash + 1: holds a call or toggles between two existing calls | 
 | 
| 
 | 
 | Flash + 2: makes a call transfer. | 
 | 
| 
 | 
 | Flash + 3: makes a  | 
 | 
| 
 | 
 | Way Conference feature is enabled, i.e., the parameter | 
 | 
| 
 | 
 | Enable3WayConference is set to 1 and the parameter | 
 | 
| 
 | 
 | 3WayConferenceMode is set to 2). | 
 | 
| 
 | 
 | [2] 2 = Sequence of Flash Hook and digit: | 
 | 
| 
 | 
 | Flash Hook only: places a call on hold. | 
 | 
| 
 | 
 | Flash + 2: places a call on hold and answers a  | 
 | 
| 
 | 
 | or toggles between active and  | 
 | 
| 
 | 
 | Flash + 3: makes a  | 
 | 
| 
 | 
 | Enable3WayConference is set to 1 and the parameter | 
 | 
| 
 | 
 | 3WayConferenceMode is set to 2). Note that the settings of the | 
 | 
| 
 | 
 | ConferenceCode parameter are ignored. | 
 | 
| 
 | 
 | Flash + 4: makes a call transfer. | 
 | 
| 
 | Modification: Option [2]  | 
 | |
| 
 | [3WayConferenceMode] | Mediant 1000 MSBG, Mediant 1000). | 
 | 
| 
 | 
 | Defines the mode of operation when the  | 
 | 
| 
 | 
 | used. | 
 | 
| 
 | 
 | [0] AudioCodes Media Server = The  | 
 | 
| 
 | 
 | (sent by the device) uses the ConferenceID concatenated with a | 
 | 
| 
 | 
 | unique identifier as the  | 
 | 
| 
 | 
 | as the  | 
 | 
| 
 | 
 | to the two remote parties. This conference mode is used when | 
 | 
| 
 | 
 | operating with AudioCodes IPMedia conferencing server. (Default) | 
 | 
| 
 | 
 | [1]  | 
 | 
| 
 | 
 | INVITE (sent by the device) uses only the ConferenceID as the | 
 | 
| 
 | 
 | 
 | |
| 
 | 
 | 200 OK response to the actual unique identifier (Conference URI) to | 
 | 
| 
 | 
 | be used by the participants. This Conference URI is then included | 
 | 
| 
 | 
 | (by the device) in the  | 
 | 
| 
 | 
 | messages sent by the device to the remote parties. The remote | 
 | 
| 
 | 
 | parties join the conference by sending INVITE messages to the | 
 | 
| 
 | 
 | conference using this conference URI. | 
 | 
| 
 | 
 | [2] On Board =  | 
 | 
| 
 | 
 | established on the device without the need for an external | 
 | 
| 
 | 
 | Conference server. The device sets up the call conference using its | 
 | 
| 
 | 
 | IP media channels. These channels are obtained from the IP media | 
 | 
| 
 | 
 | module (i.e., MPM module). Note that the MPM module(s) must be | 
 | 
| 
 | 
 | installed to support  | 
 | 
| Version 6.2 | 107 | December 2010 | 
