Difference between revisions of "Voice/Technical"

From Second Life Wiki
Jump to navigation Jump to search
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Voice]] in Second Life uses [http://www.vivox.com/ Vivox] technology that is based on RTP (using the [http://www.linphone.org/index.php/eng/code_review/ortp oRTP] library), SIP (using the amsip library from [http://www.antisip.com/ Antisip]), [http://www.openal.org/ OpenAL], [http://tinyxpath.sourceforge.net/ TinyXPath], [http://www.openssl.org/ OpenSSL], and [http://curl.haxx.se/ libcurl] for the transmission of voice data. The positional 3D audio is achieved with technology from [http://www.dw.com/about.php DiamondWare]. These technologies are contained in external daemon software that is started and stopped by the Second Life client.
{{TOCright}}
== Overview ==
[[Voice]] in Second Life uses [http://www.vivox.com/ Vivox] technology that is based on RTP (using the [http://www.linphone.org/index.php/eng/code_review/ortp oRTP] library), SIP (using the amsip library from [http://www.antisip.com/ Antisip]), [http://www.openal.org/ OpenAL], [http://tinyxpath.sourceforge.net/ TinyXPath], [http://www.openssl.org/ OpenSSL], and [http://curl.haxx.se/ libcurl] for the transmission of voice data. These technologies are contained in external daemon software started and stopped by the Second Life Viewer.


You can find the official [http://jira.secondlife.com/secure/attachment/12026/Vivox-SLVoice-SDK-2007-09-20.pdf ViVox documentation on the JIRA].
You can find the official [http://jira.secondlife.com/secure/attachment/12026/Vivox-SLVoice-SDK-2007-09-20.pdf Vivox documentation on the JIRA].


The SecondLife viewer handles configuration, control, and display functions, but the voice streams (from the microphone and from the Vivox voice server) do not enter the viewerUnfortunately the source code for the external SLVoice daemon is not available due to contractual obligations between Linden Lab and Vivox.
The Second Life Viewer handles configuration, control, and display functions, but the voice streams (from the microphone and from the Vivox voice server) do not enter the ViewerThe source code for the external SLVoice daemon is not available due to contractual obligations between Linden Lab and Vivox.  Vivox has, however, announced plans to open up the code in phases as described [http://www.vivox.com/open/ here].


==Executables==
==Executables==


The executables can be found in the Program Files\SecondLife directory of the runtime and in the linden\indra\newview\vivox-runtime\(platform) directory of the source distribution.
The executable files are in the <code>Program Files\SecondLife</code> directory of the Viewer runtime and in the <code>linden\indra\newview\vivox-runtime\(platform)</code> directory of the source distribution. The executable files are:


* SLVoice.exe
* '''SLVoice.exe'''
** Thin wrapper around the [http://www.vivox.com/ Vivox] SDK
** Thin wrapper around the [http://www.vivox.com/ Vivox] SDK
** Launched when voice is enabled in SL
** Launched when voice is enabled in SL
** Runs a TCP server that listens and replies to commands and queries using an XML format
** Runs a TCP server that listens and replies to commands and queries using an XML format
* SLVoiceAgent.exe
* '''SLVoiceAgent.exe'''
** Actually called the [http://www.dw.com/about.php DiamondWare] Thin Voice Client
** Actually called the [http://www.dw.com/about.php DiamondWare] Thin Voice Client
** Launched by SLVoice, but don't know under what conditions
** Launched by SLVoice, but don't know under what conditions
** Unclear how this fits in the communication chain
** Unclear how this fits in the communication chain
** Not launched for normal proximity voice chat; don't know about group chat or P2P yet
** Not launched for normal proximity voice chat; don't know about group chat or P2P yet
* vivoxsdk.dll
* '''vivoxsdk.dll'''
** The [http://www.vivox.com/ Vivox] SDK
** The [http://www.vivox.com/ Vivox] SDK
** Used by SLVoice.exe
** Used by SLVoice.exe
Line 24: Line 26:
** Uses [http://www.openal.org/ OpenAL] for playing and recording audio
** Uses [http://www.openal.org/ OpenAL] for playing and recording audio
** Additionally implements the [http://www.itu.int/rec/T-REC-G.722.1-200505-I/en G.722.1/C] (aka Siren14) codec
** Additionally implements the [http://www.itu.int/rec/T-REC-G.722.1-200505-I/en G.722.1/C] (aka Siren14) codec
* ortp.dll
* '''ortp.dll'''
** Real-time Transport Protocol (RFC3550) stack under LGPL
** Real-time Transport Protocol (RFC3550) stack under LGPL
** Used by vivoxsdk.dll
** Used by vivoxsdk.dll
** Originally from [http://www.linphone.org/index.php/eng/code_review/ortp Linphone]
** Originally from [http://www.linphone.org/index.php/eng/code_review/ortp Linphone]
** Distributed as part of amsip by [http://www.antisip.com/ Antisip]
** Distributed as part of amsip by [http://www.antisip.com/ Antisip]
* wrap_oal.dll
* '''wrap_oal.dll'''
** [http://www.openal.org/ OpenAL], a cross-platform 3D audio API
** [http://www.openal.org/ OpenAL], a cross-platform 3D audio API
** Used by vivoxsdk.dll
** Used by vivoxsdk.dll
* alut.dll
* '''alut.dll'''
** The [http://openal.org/openal_webstf/specs/alut.html OpenAL Utility Toolkit (ALUT)]
** The [http://openal.org/openal_webstf/specs/alut.html OpenAL Utility Toolkit (ALUT)]
** Used by vivoxsdk.dll
** Used by vivoxsdk.dll
* ssleay32.dll and libeay32
* '''ssleay32.dll and libeay32'''
** From the [http://www.openssl.org/ OpenSSL Project], a collaborative effort to develop a robust, commercial-grade, full-featured, and Open Source toolkit implementing the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols as well as a full-strength general purpose cryptography library.  
** From the [http://www.openssl.org/ OpenSSL Project], a collaborative effort to develop a robust, commercial-grade, full-featured, and Open Source toolkit implementing the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols as well as a full-strength general purpose cryptography library.  
** Used by SLVoiceAgent.dll
** Used by SLVoiceAgent.dll
* tntk.dll and srtp.dll
* '''tntk.dll and srtp.dll'''
** Part of the [http://www.dw.com/about.php DiamondWare] distribution
** Part of the [http://www.dw.com/about.php DiamondWare] distribution
** Apparently not used
** Apparently not used
Line 90: Line 92:
==Logging==
==Logging==


The logging for SLVoice is controlled by a viewer variable, VivoxDebugLevel.  You can set it directly in your '''Documents and Settings\<user>\Application Data\SecondLife\user_settings\settings.xml''' file
The logging for SLVoice is controlled by a viewer variable, VivoxDebugLevel specified in <code>Documents and Settings\<user>\Application Data\SecondLife\user_settings\settings.xml</code> file


:: <nowiki><!</nowiki>--Logging level to use when launching the vivox daemon-->
:: <nowiki><!</nowiki>--Logging level to use when launching the vivox daemon-->
:: <VivoxDebugLevel value="5 -lf myDirectory -lp myPrefix -ls .txt"/>
:: <VivoxDebugLevel value="5 -lf myDirectory -lp myPrefix -ls .txt"/>


or you can set it from the viewer.  To set it from the viewer, you have to enable the [[advanced menu]] if you haven't already using {{KeyCombo|ctrl=*|alt=*|shift=*|D}} (not to be confused with {{KeyCombo|ctrl=*|alt=*|Del}}).  Then select
or you can set it from the Viewer.  To set it from the viewer, you have to enable the [[advanced menu]] if you haven't already using {{KeyCombo|ctrl=*|alt=*|shift=*|D}} (not to be confused with {{KeyCombo|ctrl=*|alt=*|Del}}).  Then select


: Advanced -> Debug Settings
: Advanced -> Debug Settings
Line 980: Line 982:
:</Response>
:</Response>
<br />
<br />


[[Category:Voice]]
[[Category:Voice]]

Latest revision as of 21:19, 18 November 2009

Overview

Voice in Second Life uses Vivox technology that is based on RTP (using the oRTP library), SIP (using the amsip library from Antisip), OpenAL, TinyXPath, OpenSSL, and libcurl for the transmission of voice data. These technologies are contained in external daemon software started and stopped by the Second Life Viewer.

You can find the official Vivox documentation on the JIRA.

The Second Life Viewer handles configuration, control, and display functions, but the voice streams (from the microphone and from the Vivox voice server) do not enter the Viewer. The source code for the external SLVoice daemon is not available due to contractual obligations between Linden Lab and Vivox. Vivox has, however, announced plans to open up the code in phases as described here.

Executables

The executable files are in the Program Files\SecondLife directory of the Viewer runtime and in the linden\indra\newview\vivox-runtime\(platform) directory of the source distribution. The executable files are:

  • SLVoice.exe
    • Thin wrapper around the Vivox SDK
    • Launched when voice is enabled in SL
    • Runs a TCP server that listens and replies to commands and queries using an XML format
  • SLVoiceAgent.exe
    • Actually called the DiamondWare Thin Voice Client
    • Launched by SLVoice, but don't know under what conditions
    • Unclear how this fits in the communication chain
    • Not launched for normal proximity voice chat; don't know about group chat or P2P yet
  • vivoxsdk.dll
    • The Vivox SDK
    • Used by SLVoice.exe
    • Uses a solution from Antisip for SIP, RTP, and G.711
    • Uses OpenAL for playing and recording audio
    • Additionally implements the G.722.1/C (aka Siren14) codec
  • ortp.dll
    • Real-time Transport Protocol (RFC3550) stack under LGPL
    • Used by vivoxsdk.dll
    • Originally from Linphone
    • Distributed as part of amsip by Antisip
  • wrap_oal.dll
    • OpenAL, a cross-platform 3D audio API
    • Used by vivoxsdk.dll
  • alut.dll
  • ssleay32.dll and libeay32
    • From the OpenSSL Project, a collaborative effort to develop a robust, commercial-grade, full-featured, and Open Source toolkit implementing the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols as well as a full-strength general purpose cryptography library.
    • Used by SLVoiceAgent.dll
  • tntk.dll and srtp.dll
    • Part of the DiamondWare distribution
    • Apparently not used


See also: Third Party Libraries

SLVoice parameters

SLVoice is started from the viewer in SLVoiceClient::stateMachine() using:

SLVoice.exe -p tcp -h -c -ll <VivoxDebugLevel, default -1>

usage: SLVoice [flags]

valid flags are:

[-ll <log-level>] 0-5, or -1 for no logging
[-lf <log-folder>]
[-lp <log-file prefix>]
[-ls <log-file suffix>]
[-p tcp]
[-i <address>] application sends requests to this address
[-o <address>] according to the executable, the gateway sends responses and events to this address, but according to the official documentation, the gateway both sends and receives to/from this address. Please update this if you determine which is correct.
[-vo] vivox only functionality
[-ov] (undocumented and unused)
[-c] cleanup orphaned SLVoice processes. If this is the only argument to SLVoice, then it cleans up and exits; if there are other arguments, it cleans up any old instances and launches a new one.
[-h] hide the window associated with SLVoice. On MS Windows, this appears to be the default, because there is no window whether this parameter is set ot not.
[-r] (undocumented and unused)

SLVoice.exe was called vivox-gw.exe in the beta release, so you may still see some references to the old name.

IP Addresses

By default, the SecondLife viewer uses IP address 127.0.0.1 (localhost), port 44124 to communicate with SLVoice, the voice client gateway.

It is possible to connect to a client gateway running on another host. This is useful for testing. According to comments in the source code: to do this, launch the gateway on a nearby host,

SLVoice.exe -p tcp -i 0.0.0.0:44124

and modify the Settings for VoiceHost and VoicePort to set the host IP address.

The following ports are used for external communication.

  • Port 21002 - TCP - for voice control signals
  • Ports 12000-13000 - UDP - for voice media
  • Port 80/443 - TCP - for Web server
  • Ports 5060 or 5062 - UDP - for voice control signals

If the SIP connection on the default port 5062 fails (as it might if the router is designed to provide VoIP services of its own) the viewer will automatically retry and fall back on port 5060. This means that port 5060 may need to be opened on some restrictive firewalls in rare instances.

Logging

The logging for SLVoice is controlled by a viewer variable, VivoxDebugLevel specified in Documents and Settings\<user>\Application Data\SecondLife\user_settings\settings.xml file

<!--Logging level to use when launching the vivox daemon-->
<VivoxDebugLevel value="5 -lf myDirectory -lp myPrefix -ls .txt"/>

or you can set it from the Viewer. To set it from the viewer, you have to enable the advanced menu if you haven't already using Ctrl-Alt-⇧ Shift-D (not to be confused with Ctrl-Alt-Del). Then select

Advanced -> Debug Settings

to get the Debug Settings window. In the selection box, hit the triangle to bring up the list of debug variables and select VivoxDebugLevel. In the text entry box, you'll see the current value. Above it is the description, "Logging level to use when launching the Vivox daemon." You can set the level as you like. If you want the output to go somewhere other than the default location, you can enter it in the box as well, for example,

5 -lf myDirectory -lp myPrefix -ls .txt

If <log-folder> is a relative path, it is relative to the directory that SecondLife is running in, ususally C:\Program Files\SecondLife

The default folder is c:/Documents and Settings/<user>/Local Settings/Application Data/Vivox/logs. The default prefix is SLVoice and the default suffix is .txt.

The log file is named <log-file prefix>-<yyyy>-<mm>-<dd><log-file suffix>

The default on September 3, 2007, for example, would be: SLVoice-2007-09-03.txt

The <log-level> must be at least 2 to see INFO messages and 4 to see TRACE messages.


Whenever log level is other than "-1", there is also a log file written to LL_PATH_LOGS, which is usually set to c:/Documents and Settings/<user>/Application Data/SecondLife/logs, with the <log-file prefix> "Connector," that contains log information for the Connector. This logging comes from vivoxsdk.dll which is used by SLVoice.exe. The content does not depend on the log level for SLVoice; the Connector.Create.1 request hardcodes the Connector log level at 10.


17:11:38.988, 0x00001414, INFO , disconnectHandler Client Connection Closed - shutting down
17:11:38.988, 0x00001414, INFO , shutdownGateway Terminating Gateway Process


SLVoice logs commands with added default values for fields not sent by the viewer, for example,

for Account.Login.1 the log includes fields
<AccountURI />
<ParticipantPropertyFrequency>10</ParticipantPropertyFrequency>
<EnableBuddiesAndPresence>false</EnableBuddiesAndPresence>
for Connector.Create.1
<AttemptStun>AttemptStunUnspecified</AttemptStun>
<MinimumPort>22860</MinimumPort>
<MaximumPort>22892</MaximumPort>
for Session.Create.1
<Password />
<JoinAudio>true</JoinAudio>
<JoinText>false</JoinText>
<PasswordHashAlgorithm>ClearText</PasswordHashAlgorithm>
for Session.Set3DPosition.1
<OrientationType>legacy</OrientationType>


Message Protocol

<---- is a request from the viewer to SLVoice
----> is a response from SLVoice to the viewer
====> is an event notice from SLVoice to the viewer


Login

If someone else is already there

for each participant

Movement

many times per second


Teleporting

and if anyone is there

for each participant

Participant enters the area


Participant leaves the area


Speech

many times per second


Mute your microphone


Adjust the volume of your microphone

many times per second

Mute or adjust participant volume

This first command is internal to SLVoice

many times per second

Audio Wizard

many times per second


Logout

We usually disappear before getting the rest


Message Format

Events

These are examples of the Vivox SDK event messages sent to the SecondLife viewer.

AuxAudioPropertiesEvent

<Event type="AuxAudioPropertiesEvent">
<MicIsActive>true</MicIsActive>
<MicEnergy>0.0764444</MicEnergy>
<MicVolume>0</MicVolume>
<SpeakerVolume>0</SpeakerVolume>
</Event>


LoginStateChangeEvent

<Event type="LoginStateChangeEvent">
<AccountHandle>c1_m1000abcdefghijklmnopqrstuvwxy</AccountHandle>
<StatusCode>200</StatusCode>
<StatusString>OK</StatusString>
<State>1</State>
</Event>


ParticipantPropertiesEvent

<Event type="ParticipantPropertiesEvent">
<SessionHandle>c1_m1000abcdefghijklmnopqrstuvwxy2</SessionHandle>
<ParticipantURI>aBcDeFgHiJkLmNoPqRsTuVwXy</ParticipantURI>
<IsLocallyMuted>false</IsLocallyMuted>
<IsModeratorMuted>false</IsModeratorMuted>
<IsSpeaking>true</IsSpeaking>
<Volume>50</Volume>
<Energy>0.400826</Energy>
</Event>


ParticipantStateChangeEvent

<Event type="ParticipantStateChangeEvent">
<SessionHandle>c1_m1000abcdefghijklmnopqrstuvwxy2</SessionHandle>
<StatusCode>0</StatusCode>
<StatusString>'</StatusString>
<State>7</State>
<ParticipantURI>aBcDeFgHiJkLmNoPqRsTuVwXy</ParticipantURI>
<AccountName>aBcDeFgHiJkLmNoPqRsTuVwXy</AccountName>
<ParticipantType>0</ParticipantType>
</Event>


SessionMediaEvent

Ignored by the viewer
<Event type="SessionMediaEvent">
<SessionHandle>c1_m1000abcdefghijklmnopqrstuvwxy1</SessionHandle>
<HasText>false</HasText>
<HasAudio>false</HasAudio>
<HasVideo>false</HasVideo>
<Terminated>true</Terminated>
</Event>


SessionNewEvent

Used by p2p


SessionStateChangeEvent

<Event type="SessionStateChangeEvent">
<SessionHandle>c1_m1000abcdefghijklmnopqrstuvwxy0</SessionHandle>
<StatusCode>200</StatusCode>
<StatusString>OK</StatusString>
<State>4</State>
<URI>sip:confctl-505189@bhr.vivox.com</URI>
<IsChannel>true</IsChannel>
<ChannelName />
</Event>


Actions

These are examples of the Vivox SDK commands used by the SecondLife viewer.

The requestId must be unique for each request, but other than that there doesn't appear to be any restrictions on its value.

Each request is followed by three newline characters "\n\n\n" to indicate the end of the message.

Account.ChannelGetList.1

Coded in llvoiceclient.cpp but not used


Account.Login.1

AudioSessionAnswerMode may be either "AutoAnswer" or "VerifyAnswer" but the viewer always uses "VerifyAnswer."

The ParticipantPropertyFrequency sets the rate at which ParticipantPropertiesEvent events are sent to the viewer, but its value is quite counterintuitive. According to the official ViVox documentation, the valid values and their interpretations are:

  • 0 to disable event messages
  • 5 to get 10 messages per second
  • 10 to get 5 messages per second
  • 50 to get one message per second
  • 100 to get an event message only when the participant starts/stops talking or is muted/unmuted. According to the official documentation, this is the default, but the viewer does not set it and it gets a response indicating that it is set to 10 (5 per sec).


<Request requestId="3" action="Account.Login.1">
<ConnectorHandle>c1_m1000</ConnectorHandle>
<AccountName>abcdefghijklmnopqrstuvwxy</AccountName>
<AccountPassword>ABCDEFGHIJKLMNOPQRSTUVW</AccountPassword>
<AudioSessionAnswerMode>VerifyAnswer</AudioSessionAnswerMode>
<AccountURI />
<ParticipantPropertyFrequency>10</ParticipantPropertyFrequency>
<EnableBuddiesAndPresence>false</EnableBuddiesAndPresence>
</Request>
<Response requestId="3" action="Account.Login.1">
<ReturnCode>0</ReturnCode>
<Results>
<StatusCode>0</StatusCode>
<StatusString>OK</StatusString>
<AccountHandle>c1_m1000abcdefghijklmnopqrstuvwxy</AccountHandle>
</Results>
<InputXml>
<Request requestId="3" action="Account.Login.1">
<ConnectorHandle>c1_m1000</ConnectorHandle>
<AccountName>abcdefghijklmnopqrstuvwxy<AccountName>
<AccountPassword>ABCDEFGHIJKLMNOPQRSTUVW</AccountPassword>
<AudioSessionAnswerMode>VerifyAnswer</AudioSessionAnswerMode>
<AccountURI />
<ParticipantPropertyFrequency>10</ParticipantPropertyFrequency>
<EnableBuddiesAndPresence>false</EnableBuddiesAndPresence>
</Request>
</InputXml>
</Response>


Account.Logout.1

<Request requestId="557" action="Account.Logout.1">
<AccountHandle>c1_m1000abcdefghijklmnopqrstuvwxy</AccountHandle>
</Request>
The viewer doesn't get the response before the Connector shuts down
<Response requestId="557" action="Account.Logout.1">
<ReturnCode>0</ReturnCode>
<Results>
<StatusCode>0</StatusCode>
<StatusString>OK</StatusString>
</Results>
<InputXml>
<Request requestId="557" action="Account.Logout.1">
<AccountHandle>c1_m1000abcdefghijklmnopqrstuvwxy</AccountHandle>
</Request>
</InputXml>
</Response>


Aux.CaptureAudioStart.1

<Request requestId="171" action="Aux.CaptureAudioStart.1">
<Duration>10000</Duration>
</Request>
<Response requestId="171" action="Aux.CaptureAudioStart.1">
<ReturnCode>0</ReturnCode>
<Results>
<StatusCode>0</StatusCode>
<StatusString />
</Results>
<InputXml>
<Request requestId="171" action="Aux.CaptureAudioStart.1">
<Duration>10000</Duration>
</Request>
</InputXml>
</Response>


Aux.CaptureAudioStop.1

<Request requestId="174" action="Aux.CaptureAudioStop.1" />
<Response requestId="174" action="Aux.CaptureAudioStop.1">
<ReturnCode>0</ReturnCode>
<Results>
<StatusCode>0</StatusCode>
<StatusString />
</Results>
<InputXml>
<Request requestId="174" action="Aux.CaptureAudioStop.1" />
</InputXml>
</Response>


Aux.GetCaptureDevices.1

<Request requestId="0" action="Aux.GetCaptureDevices.1" />
<Response requestId="0" action="Aux.GetCaptureDevices.1">
<ReturnCode>0</ReturnCode>
<Results>
<StatusCode>0</StatusCode>
<StatusString />
<CaptureDevices>
<CaptureDevice>
<Device>Realtek HD Front Pink Jack</Device>
</CaptureDevice>
<CaptureDevice>
<Device>Realtek HD Digital input</Device>
</CaptureDevice>
<CaptureDevice>
<Device>Realtek HD Front Green Jack</Device>
</CaptureDevice>
<CaptureDevice>
<Device>Back Line in/Mic, Front Line in</Device>
</CaptureDevice>
</CaptureDevices>
<CurrentCaptureDevice>
<Device>Realtek HD Front Pink Jack</Device>
</CurrentCaptureDevice>
</Results>
<InputXml>
<Request requestId="0" action="Aux.GetCaptureDevices.1" />
</InputXml>
</Response>


Aux.GetRenderDevices.1

<Request requestId="1" action="Aux.GetRenderDevices.1" />
<Response requestId="1" action="Aux.GetRenderDevices.1">
<ReturnCode>0</ReturnCode>
<Results>
<StatusCode>0</StatusCode>
<StatusString />
<RenderDevices>
<RenderDevice>
<Device>Realtek HD Audio rear output</Device>
</RenderDevice>
</RenderDevices>
<CurrentRenderDevice>
<Device>Realtek HD Audio rear output</Device>
</CurrentRenderDevice>
</Results>
<InputXml>
<Request requestId="1" action="Aux.GetRenderDevices.1" />
</InputXml>
</Response>


Aux.RenderAudioStart.1

Coded in llvoiceclient.cpp but not used


Aux.RenderAudioStop.1

Coded in llvoiceclient.cpp but not used


Aux.SetCaptureDevice.1

<Request requestId="9" action="Aux.SetCaptureDevice.1">
<CaptureDeviceSpecifier>Realtek HD Front Green Jack</CaptureDeviceSpecifier>
</Request>
<Response requestId="9" action="Aux.SetCaptureDevice.1">
<ReturnCode>0</ReturnCode>
<Results>
<StatusCode>0</StatusCode>
<StatusString />
</Results>
<InputXml>
<Request requestId="9" action="Aux.SetCaptureDevice.1">
<CaptureDeviceSpecifier>Realtek HD Front Green Jack</CaptureDeviceSpecifier>
</Request>
</InputXml>
</Response>


Aux.SetMicLevel.1

The range for Value is -100 to 100. This only sets the microphone level while running the audio wizard. A Connector.SetLocalMicVolume.1 must be used to set the level for chat.

<Request requestId="172" action="Aux.SetMicLevel.1">
<Level>50</Level>
</Request>
<Response requestId="172" action="Aux.SetMicLevel.1">
<ReturnCode>0</ReturnCode>
<Results>
<StatusCode>0</StatusCode>
<StatusString />
</Results>
<InputXml>
<Request requestId="172" action="Aux.SetMicLevel.1">
<Level>50</Level>
</Request>
</InputXml>
</Response>


Aux.SetRenderDevice.1

<Request requestId="31" action="Aux.SetRenderDevice.1">
<RenderDeviceSpecifier>Realtek HD Audio rear output</RenderDeviceSpecifier>
</Request>
<Response requestId="31" action="Aux.SetRenderDevice.1">
<ReturnCode>0</ReturnCode>
<Results>
<StatusCode>0</StatusCode>
<StatusString />
</Results>
<InputXml>
<Request requestId="31" action="Aux.SetRenderDevice.1">
<RenderDeviceSpecifier>Realtek HD Audio rear output</RenderDeviceSpecifier>
</Request>
</InputXml>
</Response>


Aux.SetSpeakerLevel.1

The range for Value is -100 to 100. This only sets the speaker level while running the audio wizard. A Connector.SetLocalSpeakerVolume.1 must be used to set the level for chat.

<Request requestId="173" action="Aux.SetSpeakerLevel.1">
<Level>50</Level>
</Request>
<Response requestId="173" action="Aux.SetSpeakerLevel.1">
<ReturnCode>0</ReturnCode>
<Results>
<StatusCode>0</StatusCode>
<StatusString />
</Results>
<InputXml>
<Request requestId="173" action="Aux.SetSpeakerLevel.1">
<Level>50</Level>
</Request>
</InputXml>
</Response>


Connector.Create.1

<Request requestId="2" action="Connector.Create.1">
<ClientName>V2 SDK</ClientName>
<AttemptStun>AttemptStunUnspecified</AttemptStun>
<AccountManagementServer>https://www.bhr.vivox.com/api2/</AccountManagementServer>
<MinimumPort>22860</MinimumPort>
<MaximumPort>22892</MaximumPort>
<Logging>
<Enabled>false</Enabled>
<Folder>C:\Documents and Settings\HP_Administrator\Application Data\SecondLife\logs</Folder>
<FileNamePrefix>Connector</FileNamePrefix>
<FileNameSuffix>.log</FileNameSuffix>
<LogLevel>10</LogLevel>
</Logging>
</Request>
<Response requestId="2" action="Connector.Create.1">
<ReturnCode>0</ReturnCode>
<Results>
<VersionID>2.0.2961.1968</VersionID>
<StatusCode>0</StatusCode>
<StatusString />
<ConnectorHandle>c1_m1000</ConnectorHandle>
</Results>
<InputXml>
<Request requestId="2" action="Connector.Create.1">
<ClientName>V2 SDK</ClientName>
<AttemptStun>AttemptStunUnspecified</AttemptStun>
<AccountManagementServer>https://www.bhr.vivox.com/api2/</AccountManagementServer>
<MinimumPort>22860</MinimumPort>
<MaximumPort>22892</MaximumPort>
<Logging>
<Enabled>false</Enabled>
<Folder>C:\Documents and Settings\HP_Administrator\Application Data\SecondLife\logs</Folder>
<FileNamePrefix>Connector</FileNamePrefix>
<FileNameSuffix>.log</FileNameSuffix>
<LogLevel>10</LogLevel>
</Logging>
</Request>
</InputXml>
</Response>


Connector.InitiateShutdown.1

<Request requestId="558" action="Connector.InitiateShutdown.1">
<ConnectorHandle>c1_m1000</ConnectorHandle>
</Request>
The viewer doesn't wait for a response
<Response requestId="558" action="Connector.InitiateShutdown.1">
<ReturnCode>0</ReturnCode>
<Results>
<StatusCode>0</StatusCode>
<StatusString />
</Results>
<InputXml>
<Request requestId="558" action="Connector.InitiateShutdown.1">
<ConnectorHandle>c1_m1000</ConnectorHandle>
</Request>
</InputXml>
</Response>


Connector.MuteLocalMic.1

<Request requestId="6" action="Connector.MuteLocalMic.1">
<ConnectorHandle>c1_m1000</ConnectorHandle>
<Value>true</Value>
</Request>
<Response requestId="6" action="Connector.MuteLocalMic.1">
<ReturnCode>0</ReturnCode>
<Results>
<StatusCode>0</StatusCode>
<StatusString />
</Results>
<InputXml>
<Request requestId="6" action="Connector.MuteLocalMic.1">
<ConnectorHandle>c1_m1000</ConnectorHandle>
<Value>true</Value>
</Request>
</InputXml>
</Response>


Connector.MuteLocalSpeaker.1

Used only if AudioLevelVoice is 0 at startup

<Request requestId="7" action="Connector.MuteLocalSpeaker.1">
<ConnectorHandle>c1_m1000</ConnectorHandle>
<Value>true</Value>
</Request>
<Response requestId="7" action="Connector.MuteLocalSpeaker.1">
<ReturnCode>0</ReturnCode>
<Results>
<StatusCode>0</StatusCode>
<StatusString />
</Results>
<InputXml>
<Request requestId="7" action="Connector.MuteLocalSpeaker.1">
<ConnectorHandle>c1_m1000</ConnectorHandle>
<Value>true</Value>
</Request>
</InputXml>
</Response>


Connector.SetLocalMicVolume.1

The range for Value is -100 to 100.

<Request requestId="8" action="Connector.SetLocalMicVolume.1">
<ConnectorHandle>c1_m1000</ConnectorHandle>
<Value>50</Value>
</Request>
<Response requestId="8" action="Connector.SetLocalMicVolume.1">
<ReturnCode>0</ReturnCode>
<Results>
<StatusCode>0</StatusCode>
<StatusString />
</Results>
<InputXml>
<Request requestId="8" action="Connector.SetLocalMicVolume.1">
<ConnectorHandle>c1_m1000</ConnectorHandle>
<Value>50</Value>
</Request>
</InputXml>
</Response>


Connector.SetLocalSpeakerVolume.1

The range for Value is -100 to 100.

<Request requestId="7" action="Connector.SetLocalSpeakerVolume.1">
<ConnectorHandle>c1_m1000</ConnectorHandle>
<Value>50</Value>
</Request>
<Response requestId="7" action="Connector.SetLocalSpeakerVolume.1">
<ReturnCode>0</ReturnCode>
<Results>
<StatusCode>0</StatusCode>
<StatusString />
</Results>
<InputXml>
<Request requestId="7" action="Connector.SetLocalSpeakerVolume.1">
<ConnectorHandle>c1_m1000</ConnectorHandle>
<Value>50</Value>
</Request>
</InputXml>
</Response>


Session.Connect.1

Used by p2p


Session.Create.1

<Request requestId="4" action="Session.Create.1">
<AccountHandle>c1_m1000abcdefghijklmnopqrstuvwxy</AccountHandle>
<URI>sip:confctl-505189@bhr.vivox.com</URI>
<Name />
<Password />
<JoinAudio>true</JoinAudio>
<JoinText>false</JoinText>
<PasswordHashAlgorithm>ClearText</PasswordHashAlgorithm>
</Request>
<Response requestId="4" action="Session.Create.1">
<ReturnCode>0</ReturnCode>
<Results>
<StatusCode>0</StatusCode>
<StatusString />
<SessionHandle>c1_m1000abcdefghijklmnopqrstuvwxy0</SessionHandle>
</Results>
<InputXml>
<Request requestId="4" action="Session.Create.1">
<AccountHandle>c1_m1000abcdefghijklmnopqrstuvwxy</AccountHandle>
<URI>sip:confctl-505189@bhr.vivox.com</URI>
<Name />
<Password />
<JoinAudio>true</JoinAudio>
<JoinText>false</JoinText>
<PasswordHashAlgorithm>ClearText</PasswordHashAlgorithm>
</Request>
</InputXml>
</Response>


Session.Set3DPosition.1

When sending a 3D position for speaker and listener, the "listener" is either the avatar position or the camera position. That is, it describes the speaking position and the listening position for this avatar.

<Request requestId="114" action="Session.Set3DPosition.1">
<SessionHandle>c1_m1000abcdefghijklmnopqrstuvwxy1</SessionHandle>
<OrientationType>legacy</OrientationType>
<SpeakerPosition>
<Position>
<X>261451</X>
<Y>26.9568</Y>
<Z>-283000</Z>
</Position>
<Velocity>
<X>0</X>
<Y>0</Y>
<Z>0</Z>
</Velocity>
<AtOrientation>
<X>0.816965</X>
<Y>0</Y>
<Z>0.576688</Z>
</AtOrientation>
<UpOrientation>
<X>0</X>
<Y>1</Y>
<Z>0</Z>
</UpOrientation>
<LeftOrientation>
<X>0.576688</X>
<Y>0</Y>
<Z>-0.816965</Z>
</LeftOrientation>
</SpeakerPosition>
<ListenerPosition>
<Position>
<X>261448</X>
<Y>27.9639</Y>
<Z>-283001</Z>
</Position>
<Velocity>
<X>0</X>
<Y>0</Y>
<Z>0</Z>
</Velocity>
<AtOrientation>
<X>0.795791</X>
<Y>0</Y>
<Z>0.559283</Z>
</AtOrientation>
<UpOrientation>
<X>0</X>
<Y>1</Y>
<Z>0</Z>
</UpOrientation>
<LeftOrientation>
<X>0.574999</X>
<Y>0</Y>
<Z>-0.818154</Z>
</LeftOrientation>
</ListenerPosition>
</Request>
The viewer doesn't get a response


Session.SetParticipantMuteForMe.1

This message is additionally processed internally by SLVoice whenever a Session.SetParticipantVolumeForMe.1 is sent from the viewer.

<Request requestId="ic0" action="Session.SetParticipantMuteForMe.1">
<SessionHandle>c1_m1000abcdefghijklmnopqrstuvwxy1</SessionHandle>
<ParticipantURI>sip:aBcDeFgHiJkLmNoPqRsTuVwXy@bhr.vivox.com</ParticipantURI>
<Mute>0</Mute>
</Request>
No response is sent to the viewer.


Session.SetParticipantVolumeForMe.1

Used by IM panel and Active Speakers volume control

<Request requestId="83" action="Session.SetParticipantVolumeForMe.1">
<SessionHandle>c1_m1000abcdefghijklmnopqrstuvwxy1</SessionHandle>
<ParticipantURI>sip:aBcDeFgHiJkLmNoPqRsTuVwXy@bhr.vivox.com</ParticipantURI>
<Volume>57</Volume>
</Request>
<Response requestId="83" action="Session.SetParticipantVolumeForMe.1">
<ReturnCode>0</ReturnCode>
<Results>
<StatusCode>0</StatusCode>
<StatusString />
</Results>
<InputXml>
<Request requestId="83" action="Session.SetParticipantVolumeForMe.1">
<SessionHandle>c1_m1000abcdefghijklmnopqrstuvwxy1</SessionHandle>
<ParticipantURI>sip:aBcDeFgHiJkLmNoPqRsTuVwXy@bhr.vivox.com</ParticipantURI>
<Volume>57</Volume>
</Request>
</InputXml>
</Response>


Session.Terminate.1

<Request requestId="25" action="Session.Terminate.1">
<SessionHandle>c1_m1000abcdefghijklmnopqrstuvwxy0</SessionHandle>
</Request>
<Response requestId="25" action="Session.Terminate.1">
<ReturnCode>0</ReturnCode>
<Results>
<StatusCode>0</StatusCode>
<StatusString />
</Results>
<InputXml>
<Request requestId="25" action="Session.Terminate.1">
<SessionHandle>c1_m1000abcdefghijklmnopqrstuvwxy0</SessionHandle>
</Request>
</InputXml>
</Response>