Feeds:
Posts
Comments

Archive for the ‘VoIP’ Category

In our environment we use promiscuous mode in order to record calls between phones. In order to configure the VOIP you’ll need to follow the following steps:

  • Define a physical switch that will be your VOIP switch. In this switch you’ll need to define one port configured with port mirroring (span port). The span port is a port that all of the telephony traffic will be duplicated to it. In our environment we use CISCO 2960G switch for the VOIP.

             How to Define the “VOIP” Switch?  

                           

  • Connect the phones into the VOIP switch which you defined in the step above.
  • Make sure that in your ESX one physical network adapter is connected to hub while the other physical network adapters connected to your LAN switch.
  • Define a virtual switch with special parameters on each ESX server by using the following link: https://vvirtual.wordpress.com/2011/04/14/how-to-define-span-port-virtual-switch-in-esx-4/
  •  Connect one of your virtual machines into the virtual “VOIP” switch

             How to Connect your Virtual Machine into the Virtual “VOIP” Switch? 

  • Add the virtual machine 1 network adapter that is connected to the LAN
  • And another network adapter that is connected to the Voip.

                          For example:

                         

Below you can find a diagram which demonstrate how we have been implementing VOIP in our environment:

We hope that this article will help you to implement this solution in your environment 🙂 

Yaron & Idit.

Advertisements

Read Full Post »

Span Port Virtual Switch Configuration

  • From the vSphere client stand on one of the ESX servers
  • Go to Configuration > Networking > Add Networking  > Virtual Machine
  • Choose the physical NIC which is dedicated to the VOIP and is connected to the Hub
  • We have renamed the name of the virtual port group into: VoipCapture

             

  • Go to the Virtual Switch Properties
  • Go to vSwitch > Edit

             

  • Move to Security tab and change the Promiscuous Mode into : Accept

            

  • Go back to vSwitch > Edit ,stand on the VoipCapture virtual port Group > Edit
  • Move to Security tab and mark Promiscuous Mode : Accept

              

  • Move to Traffic Shaping tab and mark Status : Disabled

            

  • Move to NIC Teaming tab and mark Network Failover Detection: Link Status Only

              

  • Note:  If you have more than one ESX server, repeat these steps for each ESX server.

 Yaron & Idit.

Read Full Post »

I wanted to share with you a problem which affected us greatly and caused  a lot of problem. I am hoping it could help you in case you are suffering the same problem.

Problem                                                                                                                                                                                                                        We have installed a new Lab Manager 4 environment. Our environment includes several ESX servers version 4 update 1. Our working method is to work with a large number of configurations at the same time, therefore we use fencing. In addition, each configuration includes a few virtual machines with two network adapters.

We have mapped the second network adapter in each virtual machine which had two network adapters to work with Promiscuous Mode, but we have noticed that it didn’t actually worked. As part of our troubleshooting, we deployed an unfenced configuration which includes the same servers and the Promiscuous Mode worked perfectly.

 In order to solve this issue, we have taken out the second network adapter from the fencing by changing the second network adapter (in every virtual machine which has 2 network adapters) in the vCenter server into our unfenced network adapter that was defined with Promiscuous Mode. Sounds good? Not Quite… The new problem was that after that change , effective immediately another vCenter process started which undo the change that we have made, and left the second network adapter unconnected.

Solution                                                                                                                                                                       After consulting with VMware engineering support, we were asked to update a certain record in the lab manager’s database which dismisses the monitoring of the vCenter server from the lab manager’s DB.

Please be aware that this solution is highly risky; please make sure you have taken a full and updated backup of your lab manager’s database.       If you would like to cancel the monitoring of the vCenter from the lab manager server, please follow the instructions below:

1. Connect to you lab manager server.

2. Download and install: “SQL Server Management Studio Express” on the server

3. Run the following command:

UPDATE config SET VALUE=’0′ WHERE name=’NicPortgroupChangedOutsideConfigCondition’ AND CAT=’Reactions’

Idit.

Read Full Post »

 

Promiscuous Mode 

Promiscuous is defined as distributed or applied without order. It means the same in the world of information technology. When a network adapter is in promiscuous mode  it accepts all network packets whether they are intended for the specific machine or not.

Normally a node on the network will check the network packet before accepting to make sure it is the intended recipient. Promiscuous mode can be used for many things, such as troubleshooting network problems, software problems, recovering passwords, VoIP recording etc.

 

1.    vSwitch Definitions

Do the following steps under the virtual switch of the VoIP. 

2.    VoIP Virtual Port Group Definitions

Do the following steps under the virtual port group of the VoIP.

Idit.

Read Full Post »