Gone Phishin'

Sadly, that's not a "typo" in the title, but a reference to a nasty little practice that some folks have of trying to get you to visit a malicious site and give up your personal information. According to Wikipedia, "Phising is a way of attempting to acquire information such as usernames, passwords and credit card details by masquerading as a trustworthy entity in an electronic communication." 

Most often, your e-mail is the primary target for phishing scams although various social networking sites are sometimes utilized by scammers to make posts with links to the offending site. You can't really blame your e-mail client, ISP or favorite social networking site, these messages arrive with professional-looking logos and legitimate looking documentation that’s extremely convincing. All that's required to spring the trap is for you to follow the link they provide!
Clicking the link may take you to a very legitimate looking site that asks you to confirm your login information, social security numbers, passwords, etc... In fact, some phishing attempts have become so sophisticated that they can send you to a legitimate site (a bank for example) and then generate a pop-up window that asks you to confirm your information. In this case, the main page underneath the pop-up is a legitimate site, the pop-up is the actual scam!
So how can you avoid phishing scams?

If you receive an e-mail asking you to visit a Web site, you can find out who’s behind the message by checking the sender’s e-mail through WHOIS, before you click anything! Here’s how to do it:
  1. DO NOT CLICK THAT LINK!
  2. Hover your mouse over the link and copy the domain for the address that your e-mail client (Outlook for example)  displays. If you can't click inside the address box and highlight it, copy it down on a piece of paper. The domain is the component that is in front of dot com. For instance, the domain for http://bluelinenetworksolutions.com/ is  bluelinenetworksolutions .
  3. Point your Web browser to http://www.whois.net.
  4. Enter the domain from the e-mail’s link in the WHOIS Lookup control and click Go.
  5. WHOIS will display details about the site, including the company or person who registered it.
If your e-mail’s supposedly from a bank or legitimate institution but is registered to some company you never heard of, or even an individual out of the country, chances are this is a phishing attempt! Do yourself a favor and don't take the bait!
It's possible that the info you receive from WHOIS still doesn't provide you with the answer that you need. In that case, try to track down the phone number or actual website address for the company and see if things are legitimate. I remember a recent e-mail I received where all of the information was credible except for a phone number that was provided in the e-mail. When I tracked the legitimate company down I found out that they were aware of the scam being perpetrated in their name and an investigation was underway!

A few tips for avoiding phishing scams are:

  • If you receive an e-mail asking you to confirm information for your bank, credit card company, etc.. and it contains a link, don't follow the link. Close the e-mail and visit your bank's site the way you normally would.
  • Always make sure you are entering private information in on a secure website. These sites start with "https://" and a small "lock" icon will appear to confirm that the site is secure. If you click the lock icon the site's security information will come up and you can see who it is registered to.
  • Keep a close watch on the actual url of the site that you are at. For example, the text may say one thing but the link may lead you someplace else. In otherwords, if the link is supposed to go to "www.myfavoritebank.com" but the address in the toolbar says "www.yougotphished.com" then you need to get out fast!

If you'd like more information on how you can avoid phishing attacks, the FTC has published an article that can be found HERE. If you'd like more information on Blueline Network Solutions please feel free to visit our website at http://bluelinenetworksolutions.com or check us out on Facebook at https://www.facebook.com/Shopblueline.

How to Setup a Simple Multi-Account Avaya Meet-Me Conference

The free and built-in 6-party Avaya Meet-Me Conference feature is often missed or not setup.  To get you started, we’ve put together a quick and simple five step administration guide for you.

In this example, the following ranges were used:
  • Extensions 1200 through 1206 = Meet-Me Announcements (should be non-DID)
  • Extension 4000 = Main Meet-Me Access (should be a DID and optionally associated with a toll-free number)
  • Extensions 1401 through 1499 = Individual Meet-Me Accounts (only 1401 setup in our example however additional accounts can be configured for people, groups or even conference rooms)

STEP 1: SETUP THE MEET-ME ANNOUNCEMENTS 1200-1206: [add announcement 1200]

Record the following announcements:
1200 = “Welcome to the XYZ Company Conference Center. Please enter your bridge number.”
1201 = “The number you have entered is invalid. Please enter the number again.”
1202 = “The number entered is invalid. Please contact the conference call coordinator to make sure you have the correct information. Goodbye.”
1203 = “Your conference call is already in progress.”
1204 = “You are the first party to join the call.”
1205 = “This meet-me conference is filled to capacity. Please contact the conference call coordinator for assistance. Goodbye.”
1206 = “If you have a security code, please enter it now or simply press the pound sign to continue.”

STEP 2: SETUP THE MEET-ME MAIN ACCESS VECTOR 250: [change vector 250]


STEP 3: SETUP THE MEET-ME MAIN ACCESS VDN 4000: [add vdn 4000]

STEP 4: SETUP THE MEET-ME ACCOUNT VECTOR 251: [change vector 251]




STEP 5: SETUP THE MEET-ME INDIVIDUAL ACCOUNT VDN’S 14XX: [add vdn 1401]



In this example you can setup up to 100 individual Meet-Me accounts (14XX) pointed to the same vector 251, however the limit really depends on your server type and needed PSTN trunking for external callers.

To use the 6-party Meet-Me Conferencing in this configuration, the account holder of x1401 would send out an invite for the following ad-hoc meeting:  (XXX) XXX-4000 x1401 (internal users only have to dial x1401)
Notes:  Meet-Me Conference is available with R11 or higher (CMx) software.  Meet-Me passwords were not setup in this example however can be added.

Enjoy!