- Infoshare
-
Signed in: Administrator
- Change Password
- Signoff
- Online Documentation
- Adutante ver. 5.0.1.0
PAGE TITLE
Date Last ModifiedPAGE TITLE
Date Last ModifiedPassive recording: When recorded media streams are retrieved from the network traffic by monitoring the Mirror Port on the network switch.
Terminating recording: When recorded media streams are sent by some device directly to the recorder (e.g. BIB enabled Cisco phones, SIPREC enabled device or similar protocol).
CLI (Command Line Interace) How to use CLI Tool - refer to CLI Tool Overview |
GUI (Graphical User Interface) | |
VSLogger Passive VOIP recording package is configured in config hw voip mode. Note: This mode is available only when WinPCap driver is installed Use hw voip ? - command to display all available configuration options for this mode
|
Navigate to Setup -> Hardware -> VOIP, click edit
|
|
Use hw voip show - command to display the current configuration of this mode
|
Navigate to Setup -> Hardware -> VOIP, click edit UI screen with corresponding parameters will be displayed. Important!! - Network traffic dump parameter notes: VSLogger server provides a powerful diagnostics and debugging capability to capture the network traffic. Captured traffic dump files can be sent for review by Versadial support or development team, as needed. Traffic dump configuration:
To avoid the possibility of losing call recordings, follow following rules:
|
|
Initial configuration steps1. Enable voip hardware |
||
|
|
Navigate to Setup -> Hardware -> VOIP, click edit, then enable
|
2. Set max number of recorded voip endpoints (phones) |
||
Attention!!. This operation will add the corresponding number of channels to recorder channels list. Channels list will be updated on config reload command
|
|
|
3. Select Network card attached to MIRROR/SPAN port |
||
Display all available Network Cards
Select card to record on.
Note that card 2 is selected now |
|
In the “Recorded Interfaces” section, select the network card attached to MIRROR/SPAN port |
Signaling specific configuration steps |
||
1. rtp ports Port numbers where programs should expect RTP streams. Applied to all RTP based communications. Default range initially assigned to:
Can be changed by providing the different range
2. SIP settings (applied to channels with SIP signaling) sip ports range defines, what ports should identify SIP signaling communication. Be careful to provide correct sip ports. Default range initially assigned to:
sip url n -(default) parse phone number from SIP Address(URL) to be placed in CallerId field sip url y - put full SIP Address(URL) CallerId field
3. Other Signaling Port settings (applied to channels with corresponding signalling) sccp ports [val] - set sccp (Cisco) protocol ports Default ranges initially assigned to:
|
|
RTP ports range Port numbers where programs should expect RTP streams. Applied to all RTP based communications. Default range initially assigned to: 5100-65000 Can be changed by providing the different range SIP ports range (applied to channels with SIP signaling) sip ports range defines, what ports should identify SIP signaling communication. Be careful to provide correct sip ports. Default range initially assigned to: 5060-5061 Other Signaling Port default settings SCCP ports range: 2000-2000 H323 ports range: 1720-1720 MGCP ports range: 2727-2727 UNISTIM ports range: 5000-5000 UAUDP ports range: 32000-32000 |
VOIP trunks |
||
Use hw voip trunks mode to define SIP trunk channels. Attention!!. Each configured VoIP trunk adds the corresponding number of channels to recorder channels list. Channels list will be updated on config reload command.
Add trunks
Change trunk number of channels
Set trunk IP addresses
The list should include IP of the signaling packets, IP receiving RTP streams ( sometimes, RTP streams can be received on more than one IP). Actual entries will also depend on your voice network configuration and point where network traffic is captured. Example 1: your network has a router between PBX trunk port and trunk service provider, traffic captured inside the LAN, Single IP is handling signaling and receives RTP traffic. Trunk IP list entry contains single pair IP1:NATIP1, where IP1 - is IP of the SIP trunk on LAN and NATIP1 is external IP Example 2: your network has a router between PBX trunk port and trunk service provider, traffic captured outside the LAN (on router WAN port), Single IP is handling signaling and receives RTP traffic. Trunk IP list entry contains single entry IP1, where IP1 - is an external IP of the Router. (Note that it was set to NATIP1 in the previous example) Example 3: your network has a router between PBX trunk port and trunk service provider, traffic captured inside the LAN, one IP is handling signaling and another IP receives RTP traffic. Trunk IP list entry contains single pair IP1:NATIP,IP2:NATIP, where IP1 - SIP trunk signaling handler, IP2 - where RTP packets expected and NATIP is an external IP of the router
|
|
Navigate to Setup -> Hardware -> VOIP -> Edit, and scroll down to the IP Trunks section. Change trunk number of channels & Set trunk IP addresses Protocol selection can be either SIP or MUTUALINK. Multiple IP Addresses are separated with commas. |
MS Lync filters configurationsThis section allows configuring MS Lync filters. MS Lync filter is a special program installed on Lync server, to provide recorder with signaling information for recording MSLync calls. Settings made in this section used with VOIP channels (type = VSVOIP_CH, protocol=lync) |
||
Default lync filter port is 22443. If add filter or set filter command does not specify the port, 22443 will be applied |
|
Default lync filter port is 22443. |
Add filters |
||
|
|
|
Other parameters and commands |
||
Note: If one of the recorded extension in notrecext list, call between extensions will not be recorded even if other extension supposed to be recorded. |
|
Record extensions: Record the specified extensions. Ranges separated by dashes. Different extensions/ranges separated by commas. Not record extensions: No recording on the specified extensions. Ranges separated by dashes. Different extensions/ranges separated by commas. Note: If one of the recorded extension in Not recording extension list, calls between extensions will not be recorded even if the other extension supposed to be recorded. |
|
|
Finalize settings In order for submitted changes to take effect, it is necessary to save and reload the service. |