Administrator Guide: net.Buzz 3.5 Integration v.3

Requirements

System Requirements

The main system requirements can be found in the Product Specification.

Additionally, on the client system:
  • Microsoft Windows Installer 3.1
  • Microsoft .NET 4.0
  • Microsoft VC 9.0 Runtime Service Pack 1

The installer will take care of installing the dependencies above if the system doesn't have them.

Please make sure when using headsets, who need drivers installed on the pc, that these drivers are up to date. (ex: Jabra)

QoS

The Windows platform used should either be configured to set QoS parameters or allow the net.Buzz application to set the QoS parameters for audio/video. For Windows Vista / 7 / 8:
  • If Group Policies are in use, the QoS settings should be configured in these Group Policies.
  • If no Group Policies are in use, the QoS settings will be erased by default. To avoid that the QoS settings would be erased, a QoS Policy must be added to allow the net.Buzz client to set DSCP settings. How to do this is out of scope of this document.

Multimedia Device Requirements

net.Buzz requires both speakers and a microphone to make calls. Any of the following are acceptable:

  • External speakers and microphone
  • Built-in speakers and microphone
  • Dual-jack multimedia headset
  • Bluetooth® multimedia headset
  • USB multimedia headset
  • USB phone.
  • HID-compliant devices can be configured to work with net.Buzz.
  • Webcam

Firewall Requirements

From To Protocol Port Explanation
PC client SOP TCP HTTP (80) Authentication and provisioning
PC client SOP TCP LDAP (389) Corporate directory via default LDAP directory (optional)
PC client Customer's LDAP server TCP LDAP (389) Corporate directory via customer LDAP directory (optional)
PC client SOP UDP SIP (5060) SIP control channel
PC client secure.counterpath.com (alternatively but not recommended, 69.90.51.170 & 216.93.246.170 & 137.135.52.175 ) TCP HTTPS (443) Licensing server
SOP PC Client UDP SIP (5060) SIP control channel
PC client SOP UDP RTP (port range 30000-31000 by default) RTP traffic
SOP PC client UDP RTP (port range 10000-20000 by default) RTP traffic

ALERT! Network Address Translation is not supported.

All network and firewall requirements can be found here.

Service enabling

This section describes all the steps required prior to configuring the net.Buzz user base.

Module installation

In order to make the net.Buzz client available for your users, you just have to install the net.Buzz module 1.4.0 or higher on your SOP(s). It can be installed on a cluster or a standalone SOP. See here for the module configuration.

License management

net.Buzz can use either an individual or a group license.

An individual license can be configured in the net.Buzz phone resource. If there is no license configured for a net.Buzz phone, it will try to use the group license configured in the net.Buzz module. If a license is not found, net.Buzz will not start.

User configuration

The following tasks must be performed at the SMP:

  • Create an extension
  • Create a net.Buzz phone
  • Assign the net.Buzz phone to the extension.

Create the net.Buzz phone

net.Buzz needs its own resource like any phones to works on the SOP and this is where all the parameters can be set for a particular net.Buzz account.

DONE Navigate to: Resources > IP Phones

Please note that, in order to be able to login with net.Buzz, the configuration for an extension must contain one and only one softphone.

Apply the changes

Apply the changes you just made.

DONE Navigate to: Apply changes > Apply changes

Client

Installation

Fresh installation:
  • To install the net.Buzz, download the installer from http://sop_ip/netBuzz/ where sop_ip designates the IP address of the SOP appliance on which your user account has been registered. Once saved, run it and walk through the installer wizard.

Upgrading from a previous version:
  • If your previous version was installed with the Microsoft installer, you need to uninstall the previous version and run the new Microsoft installer.

Users login

The URL needed for your users to log in is http://<SOP IP>/netBuzz/login.php. net.Buzz will do an HTTP request to this script to authenticate and receive its configuration.

Uninstallation

To uninstall net.Buzz, launch the uninstaller from the 'Start Menu' or go to 'Control Panel' and launch 'Add or Remove Programs', then select 'net.Buzz' and click the 'Remove' button.

LDAP directory

Default values

The default values are:

  • LDAP Base DN: "dc=directory"
  • LDAP first name attribute: "givenName"
  • LDAP last name attribute: "sn"
  • LDAP phone number attribute: "telephoneNumber"
  • LDAP maximum number of records to retrieve: 5000

SOP as LDAP server

If you want to use your SOP as the LDAP server, just fill in the LDAP server to use parameter with your SOP's IP address, and leave the other parameters empty. net.Buzz will bind anonymously to the LDAP server on the SOP, and the default value for the parameters will be used. This will fetch contacts and display them correctly in the "Directory" tab into net.Buzz.

External LDAP server

If you want to use an external LDAP server, fill in the LDAP server to use parameter with your LDAP server's IP address, and set the other parameters according to your configuration if needed.

Active-active support

In order to use active-active, you have to configure the net.Buzz resource (SDX4xxx) and the extension on the two same SOPs in the cluster.

In order to preserve your contacts in failover mode, you will need to activate the DNS SRV record feature so that net.Buzz will work with a single consolidated SIP domain.

In the resource set 'Use DNS SRV Record' to 'yes' and in 'SIP server 1' set the DNS chosen name (without the prefix "_sip._udp.").

The SRV record is basically a name that points towards one or more A record. You can weight the A zone to set priorities while resolving the DNS names.

So, it is a way to define a primary server and servers that will be there as backups in case the primary server doesn't answer.

In order to be able to configure Active-Active for the netBuzz devices in an Escaux environment, you will need to set one SRV record and two A records.

Example :

  • SRV record 
             _sip._udp.sop12249.escaux.com        SRV 0  1 5060   34.soplan.escaux.com.
                                                        SRV 10 1 5060   37.soplan.escaux.com.

ALERT! The prefix '_sip._udp.' is mandatory

  • A records 
             37.soplan.escaux.com  A               172.16.35.137
             34.soplan.escaux.com  A               172.16.35.96


root@00000004:/tftpboot# nslookup 
> set type=srv
>  _sip._udp.SDS40002.sop35.escaux.com    
Server:      172.16.35.252
Address:   172.16.35.252#53

Non-authoritative answer:
_sip._udp.sop12249.escaux.com   service = 10 1 5060 34.soplan.escaux.com.
_sip._udp.sop12249.escaux.com   service = 0 1 5060 37.soplan.escaux.com.

Authoritative answers can be found from:
escaux.com   nameserver = ns2.mydyndns.org.
escaux.com   nameserver = ns4.mydyndns.org.
escaux.com   nameserver = ns1.escaux.com.
escaux.com   nameserver = ns3.mydyndns.org.
34.soplan.escaux.com   internet address = 172.16.36.26
37.soplan.escaux.com   internet address = 172.16.36.22
ns1.escaux.com   internet address = 213.246.219.72
ns2.mydyndns.org   internet address = 208.76.60.2
ns3.mydyndns.org   internet address = 208.76.61.2
ns4.mydyndns.org   internet address = 208.76.58.2
ns4.mydyndns.org   has AAAA address 2600:2004::76
> 
> exit

root@00000004:/tftpboot# dig srv _sip._udp.sop12249.escaux.com

; <<>> DiG 9.7.0-P1 <<>> srv _sip._udp.sop12249.escaux.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20094
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 7

;; QUESTION SECTION:
;_sip._udp.sop12249.escaux.com. IN   SRV

;; ANSWER SECTION:
_sip._udp.sop12249.escaux.com. 3492 IN SRV 0 1 5060 37.soplan.escaux.com.
_sip._udp.sop12249.escaux.com. 3492 IN SRV 10 1 5060 34.soplan.escaux.com.

;; AUTHORITY SECTION:
escaux.com.      1430   IN   NS   ns3.mydyndns.org.
escaux.com.      1430   IN   NS   ns4.mydyndns.org.
escaux.com.      1430   IN   NS   ns1.escaux.com.
escaux.com.      1430   IN   NS   ns2.mydyndns.org.

;; ADDITIONAL SECTION:
34.soplan.escaux.com.   3492   IN   A   172.16.36.26
37.soplan.escaux.com.   3492   IN   A   172.16.36.22
ns1.escaux.com.      1175   IN   A   213.246.219.72
ns2.mydyndns.org.   686   IN   A   208.76.60.2
ns3.mydyndns.org.   5362   IN   A   208.76.61.2
ns4.mydyndns.org.   5362   IN   A   208.76.58.2
ns4.mydyndns.org.   5362   IN   AAAA   2600:2004::76

;; Query time: 10 msec
;; SERVER: 172.16.35.252#53(172.16.35.252)
;; WHEN: Fri Feb 28 15:18:22 2014
;; MSG SIZE  rcvd: 341

root@00000004:/tftpboot#

Registration

Except if the DNS SRV Record option is used, net.Buzz will register on both SOP, the "Primary" account will be on the first SOP, and the "Secondary" account on the second one. When the DNS SRV record is used only the primary account will be created.

If the first SOP goes down, net.Buzz will switch automatically on the second one after a short delay (maximum 2 minutes). Indeed, it needs to lose its registration on the first SOP before actually doing the switch. Once it has changed, the second SOP will remain the default one. To switch back, netBuzz needs to lose its registration on the second SOP.

Users Login

In active-active mode, you can chose to login to primary SOP (recommended) or the secondary SOP. If the primary SOP is down, you can tell your users to use the secondary SOP to login. In this case, be careful to configure the net.Buzz module on the two SOPs identically (LDAP settings, ...).

Chat

The Chat is based on the SIP Messages. In order to activate it you need the Communication Server module version 3.3.0 or higher. All the SIP messages will be routed to the context 'SipImMessages'. In order to route them add 'SipImMessages' Route Group

DONE Navigate to:  SMP > Communication Routing > Route Groups and Restriction Groups
  • add a Route Group 'SipImMessages'.

DONE Navigate to:  SMP > Communication Flow Studio > Callflow

DONE Navigate to:  SMP > Communication Flow Studio > Profiles
  • Create a profile 'IM'.

DONE Navigate to:  SMP > Communication Flow Studio > Statuses
  • Create a status 'Enable'.

DONE Navigate to:  SMP > Communication Flow Studio > Callflow Assignment
  • Use the Application Selector 'STARTMESSAGINGAPPLICATION.1.0' and create a Callflow Assignement between the 'Im' profile and the status 'Enable' and set the imported callflow.

DONE Navigate to:  SMP > Directory > Internal Directory
  • Add an extension, open the "Advanced View" and set the extension to "_X." value. Set the Profile to "IM.Enable" and the Context to "SipImMessages".

You then need to do an apply-changes.

Limitations

LDAP directory

The number of contacts that can be imported depends on the SOP configuration.

Other SIP softphones

The usage of the net.Buzz softphone excludes the usage of any other SIP softphone.

User Guide

A user guide can be found here. It also explains how to install the net.Buzz application.

Copyright © Escaux SA