Best Regards,
~~Chris
<?xml version="1.0" encoding="utf-8"?>
<Configuration>
<!-- IP address of the SecureVRS GW. Typically this would be on a private IP address on the customer Intranet or an FQDN if the GW was cloud hosted
-->
<Hostname>45.59.226.188:35060</Hostname>
<!-- SecureVRS GW and host environment.
Used to authenticate the user signing in and retrieve minutes left for that user for that day
"h" == the customer's assigned environment name SecureVRS GW(s) ship with a default value of local.SecureVRS
-->
<ServerAuthUrl>http://45.59.226.188/status/?h=local.SecureVRS</ServerAuthUrl>
<!-- System status check=SecureVRS GW, assigned IP, and host environment status,
checks for VALID/nVALID
first response is the status of the entire system("h"),
second response is the status of the specific Kiosk("i") status
-->
<ServerAliveUrl>http://45.59.226.188/auth/?i=Infirmary&h=local.SecureVRS</ServerAliveUrl>
<!-- Where to find the How it Works videos.
Videos can be stored locally at the facility, at SecureVRS, or in the cloud
-->
<!-- Path to find the local video list. Local is checked first
-->
<LocalTutorialUrl>http://howitworks.securevrs.com:8090/local.SecureVRS/tutorials.xml</LocalTutorialUrl>
<!-- the contents of the xml file might look something like this.
The private IP address of the SecureVRS GW would be used when the customer does not want videos to be played from the internet
<VideoTutorials>
<TutorialUrl>http://192.168.0.100:8090/local.SecureVRS/first_video.mp4</TutorialUrl>
<TutorialUrl>http://192.168.0.100:8090/local.SecureVRS/second_video.mp4</TutorialUrl>
<TutorialUrl>http://192.168.0.100:8090/local.SecureVRS/third_video.mp4</TutorialUrl>
<TutorialUrl>http://192.168.0.100:8090/local.SecureVRS/etc.mp4</TutorialUrl>
</VideoTutorials>
-->
<!-- path to find the remote video list. Only checked if the xml file in the local path is not found
This would be used if the customer is ok with using our default videos
-->
<RemoteTutorialUrl>http://45.59.226.188:8090/local.SecureVRS/tutorials2.xml</RemoteTutorialUrl>
<!-- the contents of the xml file might look something like this.
The FQDN address of the SecureVRS cloud server is ok with using our default videos
xml file format of remote videos might look something like this
<VideoTutorials>
<TutorialUrl>http://howitworks.securevrs.com:8090/local.SecureVRS/first_video.mp4</TutorialUrl>
<TutorialUrl>http://howitworks.securevrs.com:8090/local.SecureVRS/second_video.mp4</TutorialUrl>
<TutorialUrl>http://howitworks.securevrs.com:8090/local.SecureVRS/third_video.mp4</TutorialUrl>
<TutorialUrl>http://howitworks.securevrs.com:8090/local.SecureVRS/etc.mp4</TutorialUrl>
</VideoTutorials>
-->
<!-- VRI Operating mode [ true | false ] defaults to false
fales means VRS mode. No control bar, minimize button, terminate, etc.
true means VRI mode. displays user functions to terminate the software. typically for Nurses, admins, disciplinary hearings
-->
<VRI>true</VRI>
<!-- Display the On Screen Keyboard [ true | false ] defaults to false
This option is for kiosks with no physical keyboar. It will only be considered if VRI mode is false
false means no OSK will be available.
true means OSK button is available.
-->
<OnScreenKeyboard>false</OnScreenKeyboard>
<!-- Where all log files are written. must be a full existing path
-->
<LogFilePath>D:\Logs\SecureVRSclient</LogFilePath>
<!-- Transport protocol [TCP | UDP] defaults to tcp
-->
<SipOverTcp>;transport=tcp</SipOverTcp>
<!-- Address of the stun server to be used by the client
-->
<StunServerAddress>stun.securevrs.com</StunServerAddress>
<!-- This parameter is used to select the video and audio codec sets that the client will use.
Please do not make any changes below this line without contacting first contacting SecureVRS support at (855) SEC-VRS1
Defaults to "0" == G711 audio and H264/h263 video
-->
<DefaultCodec>0</DefaultCodec>
<!-- Codec sets begin here
-->
<Codec>
<Name>H264</Name>
<MediaMask>!*uLaw*\n!*264-0</MediaMask>
<Priority>1</Priority>
</Codec>
<Codec>
<Name>H263+</Name>
<MediaMask>!G.711*\n!H.263*</MediaMask>
<Priority>2</Priority>
</Codec>
<Codec>
<Name>H263</Name>
<MediaMask>!G.711*\n!H.263*</MediaMask>
<Priority>3</Priority>
</Codec>
<Codec>
<Name>G711 mulaw</Name>
<MediaMask></MediaMask>
<Priority>4</Priority>
</Codec>
<Codec>
<Name>Negotiable</Name>
<MediaMask>!*uLaw*\n!*264-0\n!H.263*</MediaMask>
<Priority>0</Priority>
</Codec>
<!-- This section enables ManyCam integration to watermark calls that are to be recorded. -->
<!-- Set ManyCam Integration true if this PC has Manycam software installed for watermarks
[ true | false ] defaults to true
-->
<ManyCamIntegration>true</ManyCamIntegration>
<!-- Set This parameter equal to the friendly name of the ManyCam driver
defaults to ManyCam Virtual Webcam
-->
<Camera>ManyCam Virtual Webcam</Camera>
<!-- Set This parameter equal to the text you wish to be see on line 1 of the watermark
-->
<CallRecordingTextLine1>SecureVRS call from a prisoner</CallRecordingTextLine1>
<!-- Set This parameter equal to the text you wish to be see on line 2 of the watermark
The user name of the person that signed in will be placed in the "{0}" resulting in something like... ID 3105551212 - This call is being recorded
-->
<CallRecordingTextLine2>ID {0} - This call is being recorded</CallRecordingTextLine2>
</Configuration>_______________________________________________
ekiga-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/ekiga-list
