Quantcast
Channel: Gkhan Tips
Viewing all 290 articles
Browse latest View live

Nexus1000v Installation and configuration manual CLI


Manually Switching Nexus1000v Active VSM to Standby

$
0
0

Manually Switching Nexus1000v Active VSM to Standby

Use this procedure to manually switch an active VSM to standby in a dual supervisor system.
BEFORE YOU BEGIN
Before beginning this procedure, you must know or do the following:
You are logged in to the active VSM CLI in EXEC mode.

You have completed the steps in the “Verifying that a System is Ready for a Switchover” section, and have found the       system to be ready for a switchover.
A switchover can only be performed when two VSMs are functioning in the switch.
If the standby VSM is not in a stable state (ha-standby), then you cannot initiate a manual switchover. You will see the following error message:

Failed to switchover (standby not ready to takeover in vdc 1)

Once you enter the system switchover command, you cannot start another switchover process on the same system until a stable standby VSM is available.

If a switchover does not complete successfully within 28 seconds, the supervisors will reset.

Any unsaved running configuration that was available at active VSM is still unsaved in the new active VSM. You can verify this unsaved running configuration using the show running-config diff command. Save that configuration, if needed, as you would do in the other VSM (by entering thecopy running-config startup-config command).

SUMMARY STEPS

1. system switchover

2. show running-config diff

3. copy running-config startup-config

EXAMPLES

This example shows how to switch an active VSM to the standby VSM and displays the output that appears on the standby VSM as it becomes the active VSM.

n1000v# system switchover
----------------------------
2009 Mar 31 04:21:56 n1000v %$ VDC-1 %$ %SYSMGR-2-HASWITCHOVER_PRE_START:  
This supervisor is becoming active (pre-start phase). 
2009 Mar 31 04:21:56 n1000v %$ VDC-1 %$ %SYSMGR-2-HASWITCHOVER_START:  
This supervisor is becoming active. 
2009 Mar 31 04:21:57 n1000v %$ VDC-1 %$ %SYSMGR-2-SWITCHOVER_OVER: Switchover completed. 
2009 Mar 31 04:22:03 n1000v %$ VDC-1 %$ %PLATFORM-2-MOD_REMOVE: Module 1 removed (Serial 
number )

This example shows how to display the difference between the running and startup configurations:

n1000v# show running-config diff

*** Startup-config

— Running-config

***************

*** 1,38 ****

version 4.0(4)SV1(1)

role feature-group name new

role name testrole

username admin password 5 $1$S7HvKc5G$aguYqHl0dPttBJAhEPwsy1 role network-admin

telnet server enable

ip domain-lookup

source link 

The post Manually Switching Nexus1000v Active VSM to Standby appeared first on Gkhan Tips.

EMC networker nsrvadp_save: Unable to find the VM with VM name

$
0
0

EMC networker nsrvadp_save: Unable to find the VM with VM name

Application information attribute VADP_VM_NAME for client “<xyz>” is set to “<xyz.gkhan.in>”.
Trying to connect to the VM using VM name ‘< xyz.gkhan.in >’.
80398:nsrvadp_save: Unable to find the VM with VM name: < xyz.gkhan.in>.
Temporary directory ‘c:\mnt\<xyz>’ for VADP deleted.

To Solve this issue you have to:

1- While configuring Client Backup Configuration use the Virtual  Machine Name from the computer properties as it is because Virtual  Machine name is case sensitive  .

2- In the application information attribute VADP_VM_NAME= virtual machine computer name

emcerror2

emcerror

 

 

 

 

 

 

 

 

 Note That : VADP_VM_NAME is case-sensitive. For example, if the VM host name is upper-case 

(such as MBX1), the value of VADP_VM_NAME must be set to MBX1. Also, if the name entered for VADP_VM_NAME contains spaces, the name must be contained within quotation marks (for example, VADP_VM_NAME=”this is my machine”)

Source link

The post EMC networker nsrvadp_save: Unable to find the VM with VM name appeared first on Gkhan Tips.

How to configure Elastix Virtual FAX

$
0
0

How to configure Elastix Virtual FAX

Elastix is having inbuilt FAX services as HylaFAX . which provide a facility to send and receive fax through web or fax client software or email .

To configure Fax in Elastix you have to configure Virtual Fax , IAX extension, Email services ,Fax Client List.

1- Login in to the Elastix Server  Click on Fax > New Virtual Fax

2-  Fill all the information

newfax3

 

3- Go to PBX >  PBX Configuration > Extension > Add Extension > Choose IAX Extension

iax

 

 

 

 

 

 

 

4- Under Extension option

iaxext

 

 

 

 

 

 

 

User Extension will be same as what you have given in the Virtual Fax  and SIP Alias will be same as Extension number.

4- under Assigned DID /CID

did

 

 

 

 

 

 

 

 

Provide your DID number  and secret as what you have given in virtual fax.

5- Click Apply and save . and now open the Extension configuration of IAX what just you have created .

and change the Requirecalltoken yes to no

token

 

 

 

 

 

 

 

 

 

 

 

 

 

Note if you will not do it your IAX Extension will not register as FAX services.

Submit and apply changes .

6- Now you can see under Fax >  Virtual FAX > Virtual Fax List

status   Running and idle on ttyIAX1

faxstats

 

you will see in IAX extension is registered under PBX > Operator Panel

faxreg

 

 

 

 

 

 

 

 

Now you can go to  Fax  > Virtual Fax  > Send Fax and you can send a fax

send fax

 

To Check the Fax Status

 

# faxstat -v

you will see following

faxstat

 

 

 

 

 

 

 

 

For Trouble shooting  http://www.hylafax.org/site2/troubleshooting.html

faxclient

 

Put here the users desktop ip address from where they are sending fax otherwise the fax client will ask username and password and keep popup.

Download the fax client from  Extras > Download > Fax Utilities

 

fax client

 

For Receiving Fax as Email your Elastix Email services must be configured and running.

The post How to configure Elastix Virtual FAX appeared first on Gkhan Tips.

Elastix Voicemail to Email not working

$
0
0

Elastix Voicemail to Email not working

I was trying to configure my Elastix voicemail to send voicemail on Email. but the email was not being delivered to the  my email address. I had configured properly my remote SMTP under mail configuration. I was able to send email from my elastix mail system and emails was being delivered to my email address.

But  Voice mail was not being delivered to users email address.

I started troubleshooting I checked the log

tail -f /var/log/maillog

I found below error message

Apr 16 01:29:26 localhost postfix/qmgr[1820]: 6B600C90A91: from=<asterisk@pockw.localdomain>, size=813, nrcpt=1 (queue active)
Apr 16 01:29:49 localhost postfix/smtp[1937]: 6B600C90A91: to=<gkhanin@outlook.com>, relay=gkhan.in[173.254.220.66]:25, delay=23, delays=0.02/0.01/22/0.33, dsn=5.0.0, status=bounced (host gkhan.in[173.254.220.66] said: 550-Verification failed for <asterisk@pockw.localdomain> 550-The mail server could not deliver mail to asterisk@pockw.localdomain. The account or domain may not exist, they may be blacklisted, or missing the proper dns entries. 550 Sender verify failed (in reply to RCPT TO command))
Apr 16 01:29:49 localhost postfix/cleanup[1934]: 7537CC90A92: message-id=<20160415222949.7537CC90A92@pockw.localdomain>
Apr 16 01:29:49 localhost postfix/qmgr[1820]: 7537CC90A92: from=<>, size=3184, nrcpt=1 (queue active)
Apr 16 01:29:49 localhost postfix/bounce[1939]: 6B600C90A91: sender non-delivery notification: 7537CC90A92

The problem was asterisk@pockw.localdomain  which was sending voicemail to email it was not a proper email address and it was not being resolved by the DNS server as pockw.localdomain  was my server host name .

I found below article 

http://community.freepbx.org/t/change-from-email-for-voicemails/15735/3

As it says
in freepbx gui set serveremail in voicemail admin > settings to noreply@mydomainname.com

Above point I did not find in freepbx setting so I left that. and followed the next point.

edited /etc/postfix/main.cf
a. uncommented mydomain paramater in INTERNET HOST AND DOMAIN NAMES section
b. set mydomain = mydomainname.com
service postfix restart
accounts set to email voicemails as attachments are now receiving emails from noreply@mydomainname.com

Is it a bug that the postfix setting has to be manually changed?

Thats work for me it just changed the sender email address from asterisk@pockw.localdomain to asterisk@pockw.gkhan.in  but still mail was not being delivered.

Now I was getting below messge.

Apr 16 02:18:24 localhost postfix/cleanup[2354]: 143F1C90A91: message-id=<Asterisk-6-1160313698-111-2974@pockw>
Apr 16 02:18:24 localhost postfix/qmgr[2228]: 143F1C90A91: from=<asterisk@pockw.gkhan.in>, size=55680, nrcpt=1 (queue active)
Apr 16 02:18:46 localhost postfix/smtp[2357]: 143F1C90A91: to=<gkhanin@outlook.com>, relay=gkhan.in[173.254.220.66]:25, delay=23, delays=0.03/0.01/22/0.35, dsn=5.0.0, status=bounced (host gkhan.in[173.254.220.66] said: 550-Verification failed for <asterisk@pockw.gkhan.in> 550-No Such User Here 550 Sender verify failed (in reply to RCPT TO command))
Apr 16 02:18:47 localhost postfix/cleanup[2354]: 37D98C90A92: message-id=<20160415231847.37D98C90A92@pockw.gkhan.in>
Apr 16 02:18:47 localhost postfix/qmgr[2228]: 37D98C90A92: from=<>, size=2515, nrcpt=1 (queue active)
Apr 16 02:18:47 localhost postfix/bounce[2359]: 143F1C90A91: sender non-delivery notification: 37D98C90A92
Apr

To resolve the issue I did the following .

I created a sub domain pockw.gkhan.in  and created a mx record pointed to gkhan.in mx record and created a email id user under  pockw.gkhan.in  as   asterisk@pockw.gkhan.in  .

Note :- All above i did it on my  Domain Cpanel .

Now the mails was being delivered successfully.

Apr 16 20:34:56 localhost postfix/cleanup[7935]: 66C17C90A91: message-id=<Asterisk-9-1233714121-111-2974@pockw>
Apr 16 20:34:56 localhost postfix/qmgr[2228]: 66C17C90A91: from=<asterisk@pockw.gkhan.in>, size=72822, nrcpt=1 (queue active)
Apr 16 20:35:21 localhost postfix/smtp[7938]: 66C17C90A91: to=<gkhanin@outlook.com>, relay=gkhan.in[173.254.220.66]:25, delay=25, delays=0.03/0.01/23/2.1, dsn=2.0.0, status=sent (250 OK id=1arU7o-0003I6-4t)
Apr 16 20:35:21 localhost postfix/qmgr[2228]: 66C17C90A91: removed

Now It was working fine and voicemail was being delivered to users email address.

 

I got good solution from below link on comment of Billsion . postfix-masquerade.

http://community.freepbx.org/t/solved-asterisk-does-not-respect-email-from-settings/9513

you can masquerade the sender email address to the real one which you want .which will accepted by the you SMTP server .

http://www.cyberciti.biz/tips/howto-postfix-masquerade-change-email-mail-address.html

 

Postfix MTA offers smtp_generic_maps parameter. You can specify lookup tables that replace local mail addresses by valid Internet addresses when mail leaves the machine via SMTP.

Open your main.cf file
# vi /etc/postfix/main.cf

Append following parameter
smtp_generic_maps = hash:/etc/postfix/generic

Save and close the file. Open /etc/postfix/generic file:
# vi /etc/postfix/generic

Make sure tom-01@server01.hosting.com change to tom@domain.com
tom-01@server01.hosting.com tom@domain.com

Save and close the file. Create or update generic postfix table:
# postmap /etc/postfix/generic

Restart postfix:
# /etc/init.d/postfix restart

When mail is sent to a remote host via SMTP this replaces tom-01@server01.hosting.com by tom@domain.com mail address. You can use this trick to replace address with your ISP address if you are connected via local SMTP.

 

I check with my PBX its working fine.

The post Elastix Voicemail to Email not working appeared first on Gkhan Tips.

How to Install the noip Client on Linux

$
0
0

How to Install the noip Client on Linux

noip  provides free Dynamic DNS services  ( http://www.noip.com/remote-access) as DynDns was providing but its allow only three hostnames as free.

This guide will walk you through the installation and setup of the Dynamic Update Client (DUC) on a computer running Linux.  If you are using Ubuntu or Debian Linux please check our support site for guides on their specific setup.

If you are using Ubuntu Linux, please click here.

Installing the Client

The below commands should be executed from a terminal window (command prompt) after logging in as the “root” user.  You can become the root user from the command line by entering “sudo su -” followed by the root password on your machine.

Note: If you do not have privileges on the machine you are on, you may add the “sudo” command in front of steps (5 and 6).

  1. cd /usr/local/src
  2. wget http://www.no-ip.com/client/linux/noip-duc-linux.tar.gz
  3. tar xzf noip-duc-linux.tar.gz
  4. cd no-ip-2.1.9
  5. make
  6. make install

If you get “make not found” or “missing gcc” then you do not have the gcc compiler tools on your machine. You will need to install these in order to proceed.

To Configure the Client

As root again (or with sudo) issue the below command:

  • /usr/local/bin/noip2 -C   (dash capital C, this will create the default config file)

You will then be prompted for your username and password for No-IP, as well as which hostnames you wish to update.  Be careful, one of the questions is “Do you wish to update ALL hosts”.  If answered incorrectly this could affect hostnames in your account that are pointing at other locations.

Now that the client is installed and configured, you just need to launch it.  Simply issue this final command to launch the client in the background:

  • /usr/local/bin/noip2

Read the README file in the no-ip-2.1.9 folder for instructions on how to make the client run at startup. This varies depending on what Linux distribution you are running.

Source link 

The post How to Install the noip Client on Linux appeared first on Gkhan Tips.

Goautodial 2.1 Getting Started Guide

$
0
0

Goautodial 2.1 Getting Started Guide

I found the below guide helpfull to start with GOautodial

 

Requirements

Download the GoAutoDial CE 2.1 final release from http://goautodial.com/download/ – Burn to CD using program like Nero on Windows or K3B on Linux and configure your server to boot from CD.

Installation

Boot machine from the GoAutoDial CD and hit Enter to get started.

 

The automated installer takes care of everything so you just need to wait for around 15 minutes depending on your hardware for the whole installation process to finish

Starting package installation

Halfway through the package installation

Package Installation almost finished

Running post-install scripts

Installation Complete! Press Enter and remove the installation CD.

System Configurations

Goautodial does not have a desktop manager installed so you need to access it via network from your workstation, the server’s default IP Address is192.168.1.2

Open http://192.168.1.2/ using Firefox (We highly recommend using Firefox web browser)

Click ADMIN LOGIN
username: admin
password: goautodial

Configure Default Gateway

Default Gateway is not configured by default so you have to manually configure it, you can also change the IP Address from the same menu.

Click on Systems/Network > Configuration > eth0 config

Set the default gateway and click Go

Update Database IP

If you changed the IP address of the server you also need to update the IP addresses entries in the database:

Click on Systems/Network > Configuration > Update Database IP

Carrier Configuration

Before you can start dialing, you need to configure your carrier/trunk, if you do not have your own carrier yet you can sign up for an account athttp://goautodial.com/voip-store/

Click in VICIDIAL Admin > Admin > Carriers > Add A New Carrier

Below is a sample carrier configuration:

Registration String:

register => username:password@sip.goautodial.com:5060/username

Account Entry:

[goautodial]
disallow=all
allow=g729
allow=gsm
allow=ulaw
type=friend
secret=password
username=username
host=sip.goautodial.com
dtmfmode=rfc2833
context=trunkinbound
qualify=yes
insecure=very
nat=yes

Dialplan Entry:

US:

exten => _91XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91XXXXXXXXXX,2,Dial(SIP/${EXTEN:1}@goautodial,,tTo)
exten => _91XXXXXXXXXX,3,Hangup 

UK:

exten => _944.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _944.,2,Dial(SIP/${EXTEN:1}@goautodial,,tTo)
exten => _944,3,Hangup 

Australia:

exten => _961.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _961.,2,Dial(SIP/${EXTEN:1}@goautodial,,tTo)
exten => _961,3,Hangup

Activate Newly created Trunk by setting Active = Y and click Submit

How To Load Leads

1. If this is the first time you will load leads, you need to create a List first, go to Lists > Add a New List and make sure you select the campaign you will use, for this guide you can use the default campaign TESTCAMP

See below for a sample .csv format list/leads file:

"PHONE NUMBER","FIRST NAME","LAST NAME ","ADDRESS1","CITY","STATE","POSTAL CODE" 
2127773456,"first1","last1","Address 1","city","NY",12345
2127773456,"first2","last2","Address 2","city","NY",12345
2127773456,"first3","last3","Address 3","city","NY",12345
2127773456,"first4","last4","Address 4","city","NY",12345
2127773456,"first5","last5","Address 5","city","NY",12345

2. Go to Lists > Load New Leads > Browse the list file in .csv format > type the Listid you created in the List ID Override > type 1 in the Phone Code Override if you are calling US numbers > Select Custom Layout > Submit

3. Select the appropriate fields via the drop down menu then click OK TO PROCESS

If the loading of leads is successful you will see something similar to this:

Go to Campaigns > TESTCAMP

You can see that the leads are successfully loaded and there are currently 5 leads in the dial hopper.

If the dial hopper is not being populated try to set the Local Call Time to 24hours:
Campaigns > TESTCAMP > Detail view> Set the Local Call Time to 24 Hours > Submit

Softphone Configurations

Below is a link for 2 of the most popular freely downloadable softphones, for this guide we can use the following SIP account:
Username: 8001
Password: goautodial
Realm/Domain: 192.168.1.2

  1. Xlite 4 Configuration
  2. Zoiper Classic Configuration

Agent Login

1. Open http://192.168.1.2/ and click the AGENT LOGIN link:

2. Login using one of the default user accounts.

Phone Login: 8001
Phone Password: goautodial
User Login: agent001
User Password: goautodial
Campaign: TESTCAMP

After clicking on SUBMIT your phone/extension will ring, ANSWER the call and you will hear “You are currently the only person in this conference” DO NOT HANG UP.

3. If the campaign is configured as Manual/Preview dialing you will see the agent screen below, Click DIAL NEXT NUMBER > DIAL LEAD , If the campaign is configured for Predictive Dialing Mode just click the RESUME button to start receiving calls.


If the call is successful you will see the LIVE CALL indicator turn to GREEN, If you are in Predictive Dialing Mode you will hear a short beep sound every time a call comes in.

4. After each call click HANGUP reverse phone lookup and select a CALL DISPOSITION.

Video

1-goautodial-installation-boot-screen.png (41 kB) Carlo Taguinod, 06/01/2011 12:17 am

7-goautodial-installation-package-installation-3.png (44.4 kB) Carlo Taguinod, 06/01/2011 12:18 am

8-goautodial-installation-running-post-install-scripts.png (22.6 kB) Carlo Taguinod, 06/01/2011 12:18 am

2-goautodial-installation-installation-progress.png (28.3 kB) Carlo Taguinod, 06/01/2011 12:18 am

3-goautodial-installation-formatting-file-system.png (27.3 kB) Carlo Taguinod, 06/01/2011 12:18 am

4-goautodial-installation-copying-files.png (28 kB) Carlo Taguinod, 06/01/2011 12:18 am

5-goautodial-installation-package-installation-1.png (38.8 kB) Carlo Taguinod, 06/01/2011 12:18 am

6-goautodial-installation-package-installation-2.png (42.1 kB) Carlo Taguinod, 06/01/2011 12:18 am

goautodial-index.png (138.8 kB) Carlo Taguinod, 06/01/2011 01:06 am

4-800px-26-goautodial-agent-screen-dial-lead.png (115.8 kB) Carlo Taguinod, 07/04/2011 10:45 am

5-27-goautodial-agent-screen-dispo.png (25.7 kB) Carlo Taguinod, 07/04/2011 10:45 am

800px-20-goautodial-vicidial-admin-load-new-leads-4.png (77.7 kB) Carlo Taguinod, 07/04/2011 10:45 am

800px-21-goautodial-vicidial-admin-campaign-local-call-time.png (47.9 kB) Carlo Taguinod, 07/04/2011 10:45 am

1-639px-23-goautodial-index-agent.png (230.4 kB) Carlo Taguinod, 07/04/2011 10:45 am

2-800px-24-goautodial-agent-login-screen.png (169 kB) Carlo Taguinod, 07/04/2011 10:45 am

3-800px-25-goautodial-agent-screen-lead-preview.png (104.9 kB) Carlo Taguinod, 07/04/2011 10:45 am

Disclaimer

The author of this document does not warrant or assume any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, product, or process disclosed. Any consequences or results achieved directly or indirectly by this document or information are entirely your responsibility.

About This Document

The author of this document does not warrant or assume any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, product, or process disclosed. Any consequences or results achieved directly or indirectly by this document or information are entirely your responsibility.

 

Source link :- http://goautodial.org/projects/goautodialce/wiki/Goautodial_Getting_Started_Guide

 

The post Goautodial 2.1 Getting Started Guide appeared first on Gkhan Tips.

Goautodial 3.0 Getting Started Guide

$
0
0

Goautodial 3.0 Getting Started Guide

Requirements

Download the GoAutoDial CE 3.0 release from http://goautodial.com/download/ – Burn to CD using program like Nero on Windows or K3B on Linux and configure your server to boot from CD.

Installation

Before starting, please make sure machine is CONNECTED TO A NETWORK.
Boot machine from the GoAutoDial CD and hit Enter to get started.

The automated installer takes care of everything so you just need to wait for around 15 minutes depending on your hardware for the whole installation process to finish

Enter your desired root password

Halfway through the package installation


Installation Complete! Remove the installation CD then press ENTER to reboot.

After the reboot, you need to run an update. Type “yum update” on your console (see picture below). After the update completes, reboot your server.

By default DHCP is enabled. The IP of your server depends on what is assigned by your DHCP server.

GoAutoDial does not have a desktop manager installed so you need to access it via network from your workstation or login physically to the server.

How to Configure Static IP

1. via SSH or Putty type setup then Press Enter

2. Select Network Configuration

3. Edit Device

4. select eth0

5. click the SPACE Bar in your keyboard to unchecked the DHCP option after that input your Static IP

6. Edit DNS configuration

7.Then input DNS (e.g 8.8.8.8 / 208.67.222.222)

After saving the Network configuration Restart the Network services by running this command service network restart via SSH

How to change Time zone

1. via SSH or Putty type setup then Press Enter

2. select Timezone Configuration press enter

3. select Timezone then OK

4. after configuring your Timezone restart mysqld and httpd by typing /etc/init.d/mysqld restart and service httpd restart

5. after restarting mysqld and httpd type date to see Date and Time in your Server

Open your GoAutodial CE portal via a browser by putting the IP address on the address bar.

Login : admin
Password : goautodial|

How to setup an Outbound Campaign

1. Login to your portal as an administrator and Select TELEPHONY and CAMPAIGNS on the left side panel.

2. Click on ADD NEW CAMPAIGN and select the CAMPAIGN TYPE (Outbound).

3. Check the tickbox to manually edit the Campaign ID and Campaign Name

4. Browse to your Lead File directory, Select the Specific Country/Code then Select a Duplicate phone checker between Check for duplicates by phone in List ID and Check for duplicates by phone in all Campaign List then click Upload Leads once done.

5. Select the correct fields for your leads e.g. Phone Number, First Name, Last Name

6. Lead status will be posted after you successfully uploaded your lead file, Click Next to proceed.

7. Select a preferred settings for your Campaign. For the Dial Method you can choose Manual, Auto_Dial or Predictive and for the Auto Dial Levelyou can choose Slow, Normal, Max or High. “Carrier to use for this Campaign” allows you to choose between Manually created carrier and an existing JustGoVoIP account for your campaign. Please note that only active carriers will appear/ will be shown. Click “Finish” once done.

Softphone Configurations

For this guide we can use the following SIP account:

Username: 8001
Password: goautodial
Realm/Domain: (Server IP)

Please visit the links below for 2 of the most popular freely downloadable softphones,

Agent Login Procedure

1. On the GoAutoDial main page click Agent Login

2. Input the agent credentials below then click LOGIN.

Agent Login: agent001
Agent Password: goautodial

After clicking on SUBMIT your softphone/extension will ring, ANSWER the call and you will hear “You are currently the only person in this conference” DO NOT HANG UP.

Note: You must input the correct credentials for the campaign name to show up. Click Refresh Campaign List to double check

3. Click Resume Button to start receiving calls if your campaign is using a Predictive dialing or Auto Dial method of dialing

4. To do Manual Dial click the Manual Dial Button on your agent interface

NOTE:
Dial Code

  • For USA and Canada Route, use 1 Dial Code
  • For UK, use 44 Dial code
  • For AUS, use 61 Dial Code
    Then input the Phone Number and Click Dial Now


The highlighted “LIVE CALL” will be the key/basis to know if the call was successfully connected

5. Click Hangup Button on the agent portal to hangup the call and select a Call Disposition

NOTE: When you are done with your shift, click on the “Logout” button in the upper right corner of the
agent screen.

Default usernames and passwords

Goautodial 3.0:

Login Password
MySQL (mysql -u root -p) http://ServerIPAddress/phpmyadmin/ root vicidialnow
Limesurvey https://ServerIPAddress/limesurvey/admin/admin.php admin kamote1234
Portal – http://ServerIPAddress/ admin goautodial
User Login agent001 to agent020 goautodial
Phone Login (SIP) 8001 to 8020 goautodial

Source link :- http://goautodial.org/projects/goautodialce/wiki/Goautodial_Getting_Started_Guidev3

Disclaimer

The author of this document does not warrant or assume any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, product, or process disclosed. Any consequences or results achieved directly or indirectly by this document or information are entirely your responsibility.

About This Document

The author of this document does not warrant or assume any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, product, or process disclosed. Any consequences or results achieved directly or indirectly by this document or information are entirely your responsibility.

The post Goautodial 3.0 Getting Started Guide appeared first on Gkhan Tips.


VMware vSphere Update Manager logs

$
0
0

VMware vSphere Update Manager logs

Login to vCenter server

Click Start > All Programs > VMware > Generate Update Manager log bundle.

A command prompt appears, displaying the progress of logs being collected.  When the process is complete, the command prompt closes and you see a log bundle on the desktop of the server. The log file for VMware vCenter Update Manager shows as vum-support-xxxxx.zip , where xxxxx represents the user who ran the report, as well as the date and time the report was run.

By default, VMware vCenter Update Manager logs are available in these directories:
  • Windows XP, 2000, and 2003:
C:\Documents and Settings\All Users\Application Data\VMware\Update Manager
  • Windows 2008 and later operating systems:
C:\ProgramData\VMware\VMware Update Manager\Logs\
  • ESX:

    /var/log/vmware/esxupdate.log

    ESXi (patch and update installation logs):

/var/log/esxupdate.log
for more details click here

The post VMware vSphere Update Manager logs appeared first on Gkhan Tips.

How to add driver in VMware ESX ISO

$
0
0

How to add driver in VMware ESX ISO .

While installing or upgrading VMware Vsphere servers some time we have to add the drivers in the ISO .which is not available in the  ISO .

In example I have to add Nexus 1000v VEM module in the ESXi 5.5 update 3 ISO . Which required to upgrade my ESXi 5.0 and support current running my Nexus 1000v VSM.

1- we have to get VMware Vsphere 5.5 update 3 bundle as ZIP from VMware website .

download link

 

 

 

 

2-  Now create a folder and copy in it . in My Example I am copying in C:\Patch

3- Add ESXi offline bundle to Software Depot

Now open the VMware PowerCLI and run Below Command

PowerCLI > Add-EsxSoftwareDepot    c:\patch\ESXi510-201210001.zip

4- Now Copy the Driver Zip file in to C:\patch folder and add to the software depot

PowerCLI > Add-EsxSoftwareDepot  C:\patches\cisco-vem-v260-5.2.1.3.1.15.0-3.2.1.zip

5- Check the Driver is added to Software Depot

PowerCLI> Get-EsxSoftwarePackage  -Vendor Cisco

6- Check the Image profiles

PowerCLI> Get-EsxImageProfile

6-Now  Clone your  offline bundle image to a new image

PowerCLI> New-EsxImageProfile -CloneProfile ESXi-5.5.0-20151204001-standard -name Custom-cisco

7- Now check the vib list created in new Custom-cisco image

PowerCLI> (Get-EsxImageProfile -Name “brain-cisco”).VibList

8-  Get the name of vib added to image software depot

PowerCLI> Get-EsxSoftwarePackage -Vendor  Cisco

viblist

 

 

 

9- Add this vib to custom-cisco image

PowerCLI> add-esxsoftwarepackage -imageprofile Custom-cisco -softwarepackage cisco-vem-v260-esx

10- Now Export the Custom image as ISO

PowerCLI> export-esximageprofile  -imageprofile Custom-cisco  -exporttoiso  -filepath “c:imagebuilderbrian.iso”

11- Now you can compare offline base image to new Cusctom-cisco image

PowerCLI> compare-esximageprofile ESXi-5.5.0-20151201001s-standard Custom-cisco

compae

 

 

 

Source link which helped me to create custom iso .

The post How to add driver in VMware ESX ISO appeared first on Gkhan Tips.

WS-POE-8-ENC POE Injector Cisco Phone Patch Cord Pin config

$
0
0

WS-POE-8-ENC POE Injector Cisco Phone Patch Cord Pin config

I have purchased  WS-POE-8-ENC POE Injector from http://wifi-texas.com/ for my home LAB.

8port+ps

 

 

 

 

 

 

 

 

I tried to power on my Cisco Phone  7940 or 7960 with the normal patch cord , It was not powering up .
I went to the vender website now they asked for purchased patched card to power up phone to support
WS-POE-8-ENC POE injector.

I searched on the google found many article and came to below patch cord pining configuration and its worked for me .
PinlayoutPOE11

 

 

 

 

 

 

 

 

 

Just swap pin no 4-5  with 7-8  or change the colour  one side normal colour code
OW-O-GW-B-BW-G-BrW-Br      another side  OW-O-GW-Br-BrW-G-BW-B
My Phones are working fine. if you want to use  standard  patch cable  then use  RJ45 coupler.
to change the pin layout .
cuplor

 

 

 

 

 

 

For more information below links I refered.

http://wifi-texas.com/pdf/WS-POE-8-ENC-insert.pdf
http://www.itworkedinthelab.com/tag/7940/
https://nycwireless.net/projects/poe-power-over ethernet/
http://pinoutsguide.com/Net/poe_pinout.html

The post WS-POE-8-ENC POE Injector Cisco Phone Patch Cord Pin config appeared first on Gkhan Tips.

How to get list of Virtual Machines with RDM PowerCLI

$
0
0

How to get list of Virtual Machines with RDM PowerCLI

Today we had a requirement to know all virtual machines with RDM LUN mapped .So we can plan the carefully move that machine to another ESXi hots .I found a PowerCLI script that gave me good information about Virtual machines mapped with RDM LUNs. Source link

I got the below result .It show all VM and there connected RDM with LUN ID and HDD Details.

LUNID

 

 

 
$vcenter = "name-of-your-vcenter-server-here"
$outputFile = "c:\temp\All-RDMs-" + (get-date -Format yyyy-MM-dd-HHmm) + ".csv"

"Connecting vCenter servers ..."
Connect-VIServer $vcenter -AllLinked

$report = @()
$luns = @{}

"Getting VM(s). Be patient, this can take up to an hour ..."

$vms = Get-VM | Get-View
("Got " + $vms.Count + " VMs ...")

foreach($vm in $vms) {
     ("Processing VM " + $vm.Name + " ...")
     $ctl = $null
     $esx = $null
     write-host -NoNewLine "   Scanning VM's devices for RDMs ..."
     foreach($dev in $vm.Config.Hardware.Device){
          if(($dev.gettype()).Name -eq "VirtualDisk"){
               if(($dev.Backing.CompatibilityMode -eq "physicalMode") -or ($dev.Backing.CompatibilityMode -eq "virtualMode")){
                    if ($ctl -eq $null) {
                       " Found at least one ..."
                       "   Getting VM's SCSI controllers ..."
                       $ctl = Get-ScsiController -VM ($vm).Name
                    }
                    if ($esx -eq $null) {
                        write-host -NoNewLine "   Getting VM's host ..."
                        $esx = (Get-View $vm.Runtime.Host).Name
                        write-host (": " + $esx)
                    }
                    if ($luns[$esx] -eq $null) {
                        ("   Getting SCSI LUNs of host " + $esx + " ...")
                        $luns[$esx] = Get-ScsiLun -VmHost $esx -luntype disk
                    }
                    $row = "" | select VMName, GuestDevName, GuestDevID, VMHost, HDFileName, HDMode, HDsize, RuntimeName, CanonicalName
                    $row.VMName = $vm.Name
                    $row.GuestDevName = $dev.DeviceInfo.Label
                    $SCSIBus = ($ctl | where {$_.ExtensionData.Key -eq $dev.ControllerKey}).ExtensionData.BusNumber
                    $SCSIID = $dev.UnitNumber
                    $row.GuestDevID = "scsi" + $SCSIBus + ":" + $SCSIID
                    $row.VMHost = $esx
                    $row.HDFileName = $dev.Backing.FileName
                    $row.HDMode = $dev.Backing.CompatibilityMode
                    $row.HDSize = $dev.CapacityInKB
                    $lun = ($luns[$esx] | where {$_.ExtensionData.Uuid -eq $dev.Backing.LunUuid})
                    $row.CanonicalName = $lun.CanonicalName
                    $row.RuntimeName = $lun.RuntimeName
                    $report += $row
               }
          }
     }
     if ($ctl -eq $null) { " None found." }
}

"Exporting report data to $outputFile ..."
$report | Export-CSV -Path $outputFile
"All done."

 

 

Download file All_VM_RDM_List

The post How to get list of Virtual Machines with RDM PowerCLI appeared first on Gkhan Tips.

How to change VOS3000 server sip port 5060

$
0
0

How to change VOS3000 server sip port 5060

If you want to change vos3000 default sip port 5060 , 6060. you can change the SIP port no by editing

file  softswitch.conf   /usr/kunshi/mbx3000/etc/softswitch.conf

#!/bin/sh

SS_NAME=”MBX3000″
SS_H323RASPORT=”1719″
SS_H323RC4RASPORT=”3719″
SS_H323SIGNALPORT=”1720″
SS_H323RC4SIGNALPORT=”3720″
SS_SIPPORT=”5060,6060″       (Change port no here)
SS_SIPRC4PORT=”5070″

SS_EMBEDDEDSERVICEIP=”192.168.1.1″
SS_EMBEDDEDSERVICEPORT=”5065″

SS_MEDIAPROXYMODENABLE=”1″

 

The post How to change VOS3000 server sip port 5060 appeared first on Gkhan Tips.

How to get ESXi HBA information PowerCLI

$
0
0

How to get ESXi HBA information PowerCLI

If you want to gather information about you VMware ESXi Storage Connection information about HBA.

Below are the script which I tested and its works for me Its generate Cluster Name , ESXi Host name ,HBA card No, WWPN.

hbainfo

 

 

 

Below are the script. copy in notepad and save as hbainfo.ps1

#Initialize variables
$VCServer = "vcserver.yourdomain.local"
$objHba = @()

#Connect to vCenter Server
Connect-VIServer $VCServer

$clusters = Get-cluster

foreach ($cluster in $clusters) {
    $vmhosts = $cluster | Get-vmhost
    if ($null -ne $vmhosts) {
        foreach ($vmhost in $vmhosts) {
            $vmhostview = $vmhost | Get-View
            foreach ($hba in $vmhostview.config.storagedevice.hostbusadapter) {
                if ($hba.PortWorldWideName) {
                    #Define Custom object
                    $objWwpn = "" | Select Clustername,Hostname,Hba,Wwpn
                    #Add porperties to the newly created object
                    $objWwpn.ClusterName = $cluster.Name
                    $objWwpn.HostName = $vmhost.Name
                    $objWwpn.Hba = $hba.Device
                    $objWwpn.Wwpn = "{0:x}" -f $hba.PortWorldWideName
                    $objHba += $ObjWwpn
                }
            }
        }
    }
}

$objHba | Export-Csv Get-Hba.csv

Disconnect-VIServer -Confirm:$false

source link 

 

The post How to get ESXi HBA information PowerCLI appeared first on Gkhan Tips.

Windows Server 2008 TCP /IP Default gateway missing

$
0
0

Windows Server 2008 TCP /IP Default gateway missing

After rebooting of Windows 2008 server there TCP/IP setting Default gateway configuration removed .

Event putting back Default gateway configuration its not taking .

So you need to reset TCP/IP configuration . Refer to Microsoft Knowledge Base  299357.

1- Open Command Prompt with Admin privilege.

2-  netsh int ip reset c:\resetlog.txt

3- Reboot the server

4- Give the TCP/IP default gateway  and check .

The post Windows Server 2008 TCP /IP Default gateway missing appeared first on Gkhan Tips.


Cisco UCS KVM console Connection failed

$
0
0

Cisco UCS KVM console Connection failed

After java update java version 1.8.0_101 I was unable to access Cisco UCS KVM console . I was able to access Cisco UCS manager but not KVM console of the blades. It was working till java version 1.8.0_51.

KVMconsole

 

 

 

 

 

 

 

 

 

 

So I downgraded Java Version then I was able to access KVM console .Till I am not able to get solution on updated java version.

To Add old version of java in your java run time environment do the following.

1- Check your current java JRE version

Go to >start >  search program and files >  type “java”

Click on Configure Java

Click on Java Click on View

javaversion

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Now Add old version of Java  for example I added 1.7

copy the java folder on    C:\Program Files\Java

Click on Add  go to java folder\bin\javaw.exe

Click on OK

oldjava

 

 

 

 

 

 

 

 

 

Click on Apply

 

Now Close UCS Manager  and access UCS Manager and KVM console .

You should be able to access KVM Console .

Hope it will help. if there are not network issues.

The post Cisco UCS KVM console Connection failed appeared first on Gkhan Tips.

How to use another sip port on Elastix or Asterisk

$
0
0

How to use another sip port on Elastix or Asterisk

I was trying to configure  Elastix PBX SIP client but the SIP port UDP 5060  was blocked from the ISP .

I don’t wanted to change server SIP port 5060 .  I google the internet and get the trick and tested and

its worked for me .elastix

Hope it will work for others also

 

 

 

 

I just added  one rule in IPTABLES

iptables -t nat -A PREROUTING -i eth0 -p udp –dport 6060 -j REDIRECT –to-ports 5060
on above rule I used port 6060 but you can use port of your choice.

It was the easy way to use different sip port on client side without changing any server configuration.

Help link   source link

 

The post How to use another sip port on Elastix or Asterisk appeared first on Gkhan Tips.

fail2ban missing whois program

$
0
0

fail2ban missing whois program

missing whois program in fail2ban email alerts . you are not able to receive IP information .

#yum search whois

gnome-nettool.x86_64 : A GNOME interface for various networking tools
jwhois.x86_64 : Internet whois/nicname client.
perl-Net-Whois.noarch : Get and parse “whois” domain data from InterNIC
perl-Net-Whois-IP.noarch : Perl extension for looking up the whois information
: for ip addresses

# yum install jwhois.x86_64

now test whois command

[root@Elastixegy ~]# whois 221.229.172.35
[Querying whois.apnic.net]
[whois.apnic.net]
% [whois.apnic.net]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

% Information related to ‘221.224.0.0 – 221.231.255.255’

inetnum: 221.224.0.0 – 221.231.255.255
netname: CHINANET-JS
descr: CHINANET jiangsu province network
descr: China Telecom
descr: A12,Xin-Jie-Kou-Wai Street
descr: Beijing 100088
country: CN
admin-c: CH93-AP
tech-c: CJ186-AP
mnt-by: APNIC-HM
mnt-lower: MAINT-CHINANET-JS
mnt-routes: MAINT-CHINANET-JS
remarks: This object can only modify by APNIC hostmaster
remarks: If you wish to modify this object details please
remarks: send email to hostmaster@apnic.net with your
remarks: organisation account name in the subject line.
status: ALLOCATED PORTABLE
source: APNIC
mnt-irt: IRT-CHINANET-CN
changed: hm-changed@apnic.net 20030626

irt: IRT-CHINANET-CN
address: No.31 ,jingrong street,beijing
address: 100032
e-mail: anti-spam@ns.chinanet.cn.net
abuse-mailbox: anti-spam@ns.chinanet.cn.net
admin-c: CH93-AP
tech-c: CH93-AP
auth: # Filtered
mnt-by: MAINT-CHINANET
changed: anti-spam@ns.chinanet.cn.net 20101115
source: APNIC

role: CHINANET JIANGSU
address: 260 Zhongyang Road,Nanjing 210037
country: CN
phone: +86-25-86588231
phone: +86-25-86588745
fax-no: +86-25-86588104
e-mail: ip@jsinfo.net
remarks: send anti-spam reports to spam@jsinfo.net
remarks: send abuse reports to abuse@jsinfo.net
remarks: times in GMT+8
admin-c: CH360-AP
tech-c: CS306-AP
tech-c: CN142-AP
nic-hdl: CJ186-AP
remarks: www.jsinfo.net
notify: ip@jsinfo.net
mnt-by: MAINT-CHINANET-JS
changed: dns@jsinfo.net 20090831
changed: ip@jsinfo.net 20090831
changed: hm-changed@apnic.net 20090901
source: APNIC
changed: hm-changed@apnic.net 20111114

person: Chinanet Hostmaster
nic-hdl: CH93-AP
e-mail: anti-spam@ns.chinanet.cn.net
address: No.31 ,jingrong street,beijing
address: 100032
phone: +86-10-58501724
fax-no: +86-10-58501724
country: CN
changed: dingsy@cndata.com 20070416
changed: zhengzm@gsta.com 20140227
mnt-by: MAINT-CHINANET
source: APNIC

% Information related to ‘221.228.0.0/14AS23650’

route: 221.228.0.0/14
descr: CHINANET jiangsu province network
country: CN
origin: AS23650
mnt-by: MAINT-CHINANET-JS
changed: ip@jsinfo.net 20030630
source: APNIC

% This query was served by the APNIC Whois Service version 1.69.1-APNICv1r0 (UNDEFINED)

 

The post fail2ban missing whois program appeared first on Gkhan Tips.

How to Add the sip register port in VOS3000 2.1.4.0

$
0
0

How to  Add the sip register port in VOS3000 2.1.4.0

Vos3000 sip default port is 5060 and 6060
The rc4 is 5070(the encryption is defined by linknat.com)
You can modify the mbx3000 config file to add the register port
by editing   “/home/kunshi/mbx3000/etc/softswitch.conf ”

nano /home/kunshi/mbx3000/etc/softswitch.conf


SS_NAME=”MBX3000″
SS_H323_RAS_PORT=”1719″
SS_H323_RC4_RAS_PORT=”3719″
SS_H323_SIGNAL_PORT=”1720″
SS_H323_RC4_SIGNAL_PORT=”3720″
SS_SIP_PORT=”5060,6060
SS_SIP_RC4_PORT=”5070″

 

Add the ports and save and exit

Now restart the mbx services

/etc/init.d/mbx3000d   reload

now check the new ports which you have added

netstat -anp|grep “port number” (you added)

The post How to Add the sip register port in VOS3000 2.1.4.0 appeared first on Gkhan Tips.

VOS3000 Switch Firewall rules

$
0
0

VOS3000 Switch  Firewall rules

If you are running you VOS3000 server behind the firewall then you need to allow the following ports on your firewall.

tcp port:
vos-client: 1202
web: 8080
H323: 1719 1720 3719 3720
H245: 10000-39999

UDP port:
SIP:5060, 5070(RC4) and addition you added
RTP: 10000-39999

 

The post VOS3000 Switch Firewall rules appeared first on Gkhan Tips.

Viewing all 290 articles
Browse latest View live