Passive VOIP| Call Recording Reference

Configure Passive VOIP recording

Passive 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 `cli>(config)` `->hw voip` `cli>(config-hw_voip)` `->?` `help\|? - embedded help` `enable [y\|n] - enable/disable hw` `niclist - show available NICs` `nicset [1-n] [y\|n] - set/unset NIC for monitoring` `rtp ports [val] - set rtp ports` `sip ports [val] - set sip protocol ports` `sip url [y\|n] - set full sip url in caller Id (default n)` `sccp ports [val] - set sccp (Cisco) protocol ports` `h323 ports [val] - set h323 protocol ports` `mgcp ports [val] - set mgcp protocol ports` `unistim ports [val] - set unistim (Nortel) protocol ports` `uaudp ports [val] - set uaudp (Alcatel) protocol ports` `numdev [1..n] - set max number of voip endpoints (phones)` `trunks - voip trunks configuration mode` `lync - lync filter configuration mode` `show - show current settings` `exit - exit current configuration mode` `cli>(config-hw_voip)`		Navigate to Setup -> Hardware -> VOIP, click edit
Use hw voip show - command to display the current configuration of this mode `cli>(config-hw_voip)` `->show` `----------------------------------------` `hw [voip]` `----------------------------------------` `available: y` `enabled: n` `rtp ports: 5100-65000` `sip ports: 5060-5061` `sip url: n` `sccp ports: 2000-2000` `h323 ports: 1720-1720` `mgcp ports: 2727-2727` `unistim ports: 5000-5000` `uaudp ports: 32000-32000` `numdev: 0` `dump: n` `dumppath:` `lync filter settings:` `----------------------------------------` `timeout: 30` `recext:` `notrecext:` `----------------------------------------` `nic# \|set \|ip \|id (description)` `----------------------------------------` `1 n 192.168.6.1 \Device\NPF_{14D2965F-F31D-461B-9D91-24645E9D8BE7} (VMware Virtual Ethernet Adapter)` `2 n 0.0.0.0 \Device\NPF_{77E092E8-B620-48AA-A839-E303080689F6} (Intel(R) 82574L Gigabit Network Connection)` `3 n 192.168.42.221 \Device\NPF_{9769D74F-AD39-4408-8088-74C2291CFE77} (Intel(R) 82574L Gigabit Network Connection)` `4 n 192.168.179.1 \Device\NPF_{FF1C11B5-7687-454C-AD17-570D8BB79EEF} (VMware Virtual Ethernet Adapter)` `cli>(config-hw_voip)`		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: Save pcap dump [ x] - enable/disable dump Store pcap files in folder [ E:\ dump ] - dump location Purge dump files after (days) [2] - limit dump size Attention!! Danger!! : Network traffic dump feature can cause loss of the recording if used incorrectly. If network capture dump files stored to volumes allocated for call recordings storage, recorder potentially can delete older recordings to free space for new recordings. To avoid the possibility of losing call recordings, follow following rules: Never point "Store pcap files in folder" parameter to drives used for call recording storage, especially if "auto-delete to free space" is enabled. If, for some reason, you still save network traffic dump to recording storage, make sure you have enough free storage space; limit dump process to shorter period of time (e.g. enough time to make several calls ); delete dump files storage folder shortly after their creation and usage.
Initial configuration steps 1. Enable voip hardware
`cli>(config-hw_voip)` `->enable y` `cli>(config-hw_voip)`		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 `cli>(config-hw_voip)` `->numdev 8` `cli>(config-hw_voip)`
3. Select Network card attached to MIRROR/SPAN port
Display all available Network Cards `cli>(config-hw_voip)` `->niclist` `----------------------------------------` `nic# \|set \|ip \|id (description)` `----------------------------------------` `1 n 192.168.6.1 \Device\NPF_{14D2965F-F31D-461B-9D91-24645E9D8BE7} (VMware Virtual Ethernet Adapter)` `2 n 0.0.0.0 \Device\NPF_{77E092E8-B620-48AA-A839-E303080689F6} (Intel(R) 82574L Gigabit Network Connection)` `3 n 192.168.42.221 \Device\NPF_{9769D74F-AD39-4408-8088-74C2291CFE77} (Intel(R) 82574L Gigabit Network Connection)` `4 n 192.168.179.1 \Device\NPF_{FF1C11B5-7687-454C-AD17-570D8BB79EEF} (VMware Virtual Ethernet Adapter)` Select card to record on. `cli>(config-hw_voip)` `->nicset 2` `cli>(config-hw_voip)` `->niclist` `----------------------------------------` `nic# \|set \|ip \|id (description)` `----------------------------------------` `1 n 192.168.6.1 \Device\NPF_{14D2965F-F31D-461B-9D91-24645E9D8BE7} (VMware Virtual Ethernet Adapter)` `2 y 0.0.0.0 \Device\NPF_{77E092E8-B620-48AA-A839-E303080689F6} (Intel(R) 82574L Gigabit Network Connection)` `3 n 192.168.42.221 \Device\NPF_{9769D74F-AD39-4408-8088-74C2291CFE77} (Intel(R) 82574L Gigabit Network Connection)` `4 n 192.168.179.1 \Device\NPF_{FF1C11B5-7687-454C-AD17-570D8BB79EEF} (VMware Virtual Ethernet Adapter)` 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: `rtp ports: 5100-65000` Can be changed by providing the different range `cli>(config-hw_voip)` `->rtp ports 5100-65535` 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 ports: 5060-5061.` 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 h323 ports [val] - set h323 protocol ports mgcp ports [val] - set mgcp protocol ports unistim ports [val] - set unistim (Nortel) protocol ports uaudp ports [val] - set uaudp (Alcatel) protocol ports Default ranges initially assigned to: `sccp ports: 2000-2000` `h323 ports: 1720-1720` `mgcp ports: 2727-2727` `unistim ports: 5000-5000` `uaudp ports: 32000-32000`		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. `cli>(config-hw_voip)` `->trunks` `add trunk [1-n][sip] [num of channels] - add voip trunk` `remove trunk [1-n] - remove trunk` `swap [trunk1][trunk2] - swap trunks` `set trunk [1-N] [ip\|numch] [val] - set trunk ip list(as ip1:natip,..., natip is optional) or number of trunk channels` `show - show available voip trunks` `cli>(config-hw_voip-trunks)` Add trunks `cli>(config-hw_voip-trunks)` `->add trunk 1 sip 4` `cli>(config-hw_voip-trunks)` `->show` `----------------------------------------` `trunk# \|protocol \|numch \|ips` `----------------------------------------` `1 sip 4` `cli>(config-hw_voip-trunks)` Change trunk number of channels `If you need to change number of channels on the trunk` `set trunk 1 numch 6` Set trunk IP addresses `cli>(config-hw_voip-trunks)` `->set trunk 1 ip 192.168.11.2:28.34.56.2,192.168.11.13:28.34.56.2` `cli>(config-hw_voip-trunks)` `->show` `----------------------------------------` `trunk# \|protocol \|numch \|ips` `----------------------------------------` `1 sip 4 192.168.11.2:28.34.56.2,192.168.11.13:28.34.56.2` `cli>(config-hw_voip-trunks)` `Notes: IP addresses associated with SIP trunk can contain one or more following entries, separated by comma:` IP, IP1:NATIP1, IP2:NATIP2,.. 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. Add trunks Change trunk number of channels & Set trunk IP addresses Protocol selection can be either SIP or MUTUALINK. Multiple IP Addresses are separated with commas. See CLI configuration comments
MS Lync filters configurations This 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)
`cli>(config-hw_voip)` `->lync` `add filter [host:port] - add filter (<addr/host>:<port>)` `set filter [host:port] - update filter` `remove filter [host] - remove filter` `timeout [val] - filter reconnect timeout (default 30 sec)` `recext [val] - recording extensions (record all if empty)` `notrecext [val] - not recording extensions` `show - show current configuration` `cli>(config-hw_voip-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
`cli>(config-hw_voip-lync)` `->add filter lyncserver1:44444` `cli>(config-hw_voip-lync)` `->add filter lyncserver2:44444` `cli>(config-hw_voip-lync)` `->show` `lync filter settings:` `----------------------------------------` `timeout: 30` `recext:` `notrecext:` `filters:` `lyncserver1:44444` `lyncserver2:44444`
Other parameters and commands
`set filter [host:port] - update filter (default port is 22443)` `remove filter [host] - remove filter` `timeout [val] - filter reconnect timeout (default 30 sec). in case connection is lost` `recext [val] - record specified extensions (record all if empty). Example: recext 1001-1010,1015,1016` `notrecext [val] - not recording extensions. Example: notrecext 1018-1020,1025` 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.		Reconnect Timeout: If connection is lost, how many seconds until reconnection attempt. 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.