Teleflex FAQs

Subject:Teleflex Support Hours

Date:November 28th & 29th, 2019

Start Time: 11/28/19 @ 12:00 AM Central Time Zone

End Time:11/29/19 @ 11:59 PM Central Time Zone

Impact: Teleflex offices will be closed in observation of the Thanksgiving holiday. During this time window, the NOC/Help Desk will be available for emergency on-call support. If there are any questions or concerns, please contact Teleflex support via phone at 713-231-5005 or by email at [email protected].

Subject:Teleflex Support Hours

Date:September 2nd, 2019

Start Time: 09/02/19 @ 12:00 AM Central Time Zone

End Time:09/02/19 @ 11:59 PM Central Time Zone

Impact: Teleflex offices will be closed in observation of the Labor Day holiday. During this time window, the NOC/Help Desk will be available for emergency on-call support. If there are any questions or concerns, please contact Teleflex support via phone at 713-231-5005 or by email at [email protected].

Subject:Teleflex Support Hours

Date:July 4th, 2019

Start Time: 07/04/19 @ 12:00 AM Central Time Zone

End Time:07/05/19 @ 11:59 PM Central Time Zone

Impact: Teleflex offices will be closed in observation of the 4th of July holiday. During this time window, the NOC/Help Desk will be available for on-call support. If there are any questions or concerns, please contact Teleflex support via phone at 713-231-5005 or by email at [email protected].

Subject:Teleflex Support Hours

Date:May 27th, 2019

Start Time: 05/27/19 @ 7:00 AM Central Time Zone

End Time:05/27/19 @ 6:00 PM Central Time Zone

Impact: Teleflex offices will be closed in observation of Memorial Day. During this time window, the NOC/Help Desk will be available for on-call support. If there are any questions or concerns, please contact Teleflex support via phone at 713-231-5005 or by email at [email protected].

Event Description: Partial Voice Outage

Event Date: 05/21/2019

RFO Issue Date: 05/23/2019

Ticket Number: 70000

Scope of Impact

Services Impacted:

Customers on a subset of softswitch nodes experienced call completion errors on calls utilizing audio prompts and music resource files.

Event Description:

On May 21st, 2019, wile performing routine, non-service affecting maintenance, a Teleflex engineer inadvertently issued a command which reset network services on a LXD storage pool. Following this event the storage pool was active and accessible by the majority of softswitch nodes, which had failed over to alternate storage pools and maintained normal operation. TeleFlex NOC began inspection of dependent nodes. Shortly thereafter, Teleflex received reports of call issues from users on a subset of softswitches and engineers focused on the reported nodes to determine the cause of isolated service issues.

Logs on the subset of impacted softswitches showed errors reading certain audio files which, in certain dialplan actions, resulted in delayed call processing and call completion errors. The impacted softswitches had immediately re-established connections to shared storage pool following the network event; however, the file handler pointers were flagged as stale on some nodes. Since the effected softswitches had re-established the underlying storage maps to the pool linked with the network event, the process for failover to secondary storage pools was interrupted on these particular nodes.

To correct the issue, Teleflex went through each of the identified softswitches to validate active file handler pointers. For the effected nodes, engineers flushed the stale pointers and forced new connections to the active storage pools. Once pointers were re-established services for each impacted softswitch node resumed normal operation with full access to audio source files. Softswitch #25 was manually restored during troubleshooting activities. Once isolated a script to handle the refresh of storage pointers was successfully validated against Softswitch #46. The script was then deployed to the remaining identified nodes #30 and #34. Following resolution on the impacted nodes, the script was applied across all remaining (non-impacted) nodes to protect against any delayed impacts to nodes not initially effected.

Event Timeline:

Please note that all times listed in the timeline below are in 24-hour clock format, and refer to Central Daylight Time.

11:53 - Inadvertent restart of network services for LXD0001.11:55 - LXD0001 back online and fully functional. Subsystem check completed.12:03 - First reported call issues Softswitches #34, #25.12:05 - NOC Escalation to Senior Engineering12:10 - Log errors identified on #25 indicated problems opening audio resource files.12:16 - Issue cause isolated to stale file handler pointers on #25.12:24 - Softswitch #25 stale file pointers flushed and re-activated & verified resolution of node issue.12:38 - Script applied to SoftSwitch #46 and validated. Full service restored.12:54 - Script applied to remaining identified nodes #30, #32, #34, #35 and #37. Full service restored.13:14 - Script applied to all SoftSwitches (not impacted by event) as precaution against any further impacts.

Corrective/Preventative Actions

Maintenance schedules and practices will be reviewed to determine what can be moved to off-hour/planned maintenance windows. Teleflex will be reviewing supervision and review processes related to technician activities. Engineering is reviewing logs on the impacted nodes to determine the operational state of each node impacted versus the nodes that successfully rolled to alternate connections and will adjust failover algorithms to protect against the identified corner-cases.

Subject:Teleflex Support Hours

Date:April 19th, 2019

Start Time: 04/19/19 @ 7:00 AM Central Time Zone

End Time:04/19/19 @ 6:00 PM Central Time Zone

Impact: Teleflex offices will be closed in observation of Good Friday. During this time window, the NOC/Help Desk will be available for on-call support. If there are any questions or concerns, please contact Teleflex support via phone at 713-231-5005 or by email at [email protected].

Subject:Teleflex Corporate Event Support Hours

Date:April 12th, 2019

Start Time: 04/12/19 @ 2:00 PM Central Time Zone

End Time: 04/14/19 @ 6:00 PM Central Time Zone

Impact: Teleflex will be hosting our annual corporate retreat. During this time window, the NOC/Help Desk will be available for emergency support only. If there are any questions or concerns, please contact Teleflex support via phone at 713-231-5005 or by email at [email protected].

Subject:TeleFlex Service Advisory

Date:April 4th, 2019

Start Time: 04/04/19 @ 12:00 AM Central Time Zone

Reason:Some customers are experiencing issues with MWI not being lit, even though there are new messages in the inbox.

Action:TeleFlex will be applying a patch to the voice systems in order to correct the issue with MWI not notifying user phones of new voicemail messages in the inbox.

Impact: During this update, users on affected voice systems will be unable to place or receive phone calls. This will require a simple restart of the voice services on select servers and should last no more than 5 minutes.

User Action Required:None necessary.

Subject:TeleFlex Service Advisory

Date:April 3rd, 2019

Start Time: 04/03/19 @ 12:00 AM Central Time Zone

Reason:Some customers are experiencing issues with MWI not being lit, even though there are new messages in the inbox.

Action:TeleFlex will be applying a patch to the voice systems in order to correct the issue with MWI not notifying user phones of new voicemail messages in the inbox.

Impact: During this update, users on affected voice systems will be unable to place or receive phone calls. This will require a simple restart of the voice services on select servers and should last no more than 5 minutes.

User Action Required:None necessary.

Incident Details

Subject: TeleFlex Service Advisory

Date:March 19th, 2019 - March 20th, 2019

Start Time: 03/19/19 @ 10:00 PM Central Time Zone

End Time:03/20/19 @ 4:00 AM Central Time Zone

Impact:

TeleFlex will be performing a portal upgrade. This work will occur starting at 10:00 PM CST March 19th, continuing through 4:00 AM CST March 20th.

The migration activities are designed to occur without impact the customer services and will be completed during off-peak hours.

Actions: None necessary.

Subject:TeleFlex Service Advisory

Date:March 21st, 2019 - March 22nd, 2019

Start Time: 03/21/19 @ 10:00 PM Central Time Zone

End Time:03/22/19 @ 4:00 AM Central Time Zone

Impact:

TeleFlex will be performing a portal upgrade. This work will occur starting at 10:00 PM CST March 21st, continuing through 4:00 AM CST March 22nd.

The migration activities are designed to occur without impact the customer services and will be completed during off-peak hours.

Actions:None necessary.

Christmas 2017

Saturday, December 23rd: Offices Closed, NOC/Help Desk On-Call Available

Sunday, December 24th: Offices Closed, NOC/Help Desk On-Call Available

Monday, December 25th: Offices Closed, NOC/Help Desk On-Call Available

Tuesday, December 26th: Open, Normal Business Hours

New Years 2018

Saturday, December 30th: Offices Closed, NOC/Help Desk On-Call Available

Sunday, December 31st: Offices Closed, NOC/Help Desk On-Call Available

Monday, January 1st: Offices Closed, NOC/Help Desk On-Call Available

Tuesday, January 2nd: Open, Normal Business Hours

2018 Holiday Schedule

The following holidays will be observed in the 2018 calendar year. Detailed availability information will become available as the holiday approaches.

Monday, May 28: Memorial Day

Offices Closed, NOC/Help Desk On-Call Available

Wednesday, July 4: Independence Day

Offices Closed, NOC/Help Desk On-Call Available

Monday, September 3: Labor Day

Offices Closed, NOC/Help Desk On-Call Available

Thursday, November 22: Thanksgiving Day

Offices Closed, NOC/Help Desk On-Call Available

Tuesday, December 25: Christmas Day

Offices Closed, NOC/Help Desk On-Call Available

Incident Details

Subject: TeleFlex Service Advisory

Date: January 28th @ 3:00 AM Central Time

Start Time: 01/28/19 @ 3:00 AM Central Time Zone

End Time:01/28/19 @ 6:00 AM Central Time Zone

Impact:

Our layer 2 carrier will be performing emergency maintenance to upgrade device software in order to rectify recent service stability issues at these sites.

Services at each site will experience an ~30 minute traffic interruption as device software is upgraded, within the 3 hour maintenance window.

This does not affect voice services, however, it will impact internet services for clients within the CyrusOne West facility.

Actions: None necessary.

Incident Details

Subject: TeleFlex Service Advisory

Date: January 19th, 2019 - January 21st, 2019

Start Time: 01/19/19 @ 12:00 AM Central Time Zone

End Time:01/21/19 @ 4:00 AM Central Time Zone

Impact:

TeleFlex will be performing final migrations of voice customers to our new, upgraded, architecture ad codebase. This work will occur starting at 12:00 AM CST January 19th, continuing through 4:00 AM CST January 21st.

The migration activities are designed to occur without impact the customer services and will be completed during off-peak hours.

Actions: None necessary.

You can preview our system default music on hold below. Just click on one of the music on hold files you would like to listen to in order to sample the song.

Sending an eFax

To send an eFax to a recipient, create a new email message.

In the To field, type the recipients 10 digit phone number (ex. 7132315008), followed by @netsatisfaxion.com. See the example in the picture above.

Add a subject line as you would like it to appear on the fax header page.

Attach any documents that you want to be sent. The system can support PDF, DOC, DOCX, TIFF, TIF, XLS, XLSX.

In the body of your email, write anything you want to appear on the body of the header page.

Now simply send the message as you would any other email.

Successfully Sent eFax

If your fax was successfully sent to the recipient, you should receive the confirmation shown above. You will also receive a copy of the faxed pages for your reference.

Failure on Sent eFax

If you eFax cannot be delivered, you will receive a message as the one shown above. You will see why the fax was not sent by looking next to the Error text. In the case shown above, the number was busy and was attempted to be dialed 3 times.

Receiving eFaxes

When you receive a new eFax, an email will be sent to the address that was setup with your account. Attached will be the fax you were sent in a PDF format. The name of the file reflects the caller ID of the person whom sent you the fax. The message body also indicates the caller ID of the person whom sent the fax and what number they sent the fax to.

Ticket SLA is 1 hr for non emergency and 15 mins for emergency issues.

Level 1

713-231-5005

Open a ticket by sending email to [email protected] or login at support.teleflexnetworks.com to submit a ticket.

Option 1 ONLY for emergencies.

Level 2

Kyle Olexa

[email protected]

Office: 713-231-5016

Cell: 346-218-6741

Level 3

Shawn Faas

[email protected]

Office: 713-231-5003

Level 4

Timothy Nurre

[email protected]

Office: 713-231-5002

Cell: 281-202-7378

Level 5

COO

Josh Frazier

[email protected]

Office: 713-231-5007

Cell: 281-846-5674

Level 6

CEO

Stephen Myers

[email protected]

Office: 713-231-5001

Cell: 917-806-7861

What to expect during Memorial Day

As always, 24x7 support and facility access is available around the clock, 365 days per year. For 24x7 support, call 713-231-5005 or email [email protected]. If an agent is unavailable to take your call, leave a message with:

Your name

Your company (if whitelabeler, your company and the name of the subtenant having the issue.)

Callback number

Description of the issue or question

Your call will be returned by an on-call technician within 30 minutes.

In case of emergency, please still follow the procedure above and refer to the escalations section below to contact an available agent directly to escalate immediately.

Escalations

If you need to escalate an issue during this time, please follow our Escalations guide.

Upgrade Firmware

Firmware will be needed to be upgraded in order for the trunking feature to exist as the default firmware doesn't have trunks.

Once logged into the ATAs web GUI:

1) Click on Admin

2) Click on Advanced

3) Click on Voice tab

4) Click on Provisioning

5) Be sure that Upgrade Enable is set to yes

6) Set Upgrade Rule to "tftp.teleflexnet.net/spa8000-6-1-12-XU.bin" Just a future note: "XU" versions exclude SRTP. We don't use SRTP.

7) Click the Submit All Changes button

This process will take a few minutes. Status lights 1-4 will flash randomly and go solid when complete. Refresh the page when lights are solid.

Programming

If not already:

1) Click on Admin

2) Click on Advanced

3) Click on Voice tab

4) Click on T1 tab

5) Update Display Name

6) Enter User ID

7) Enter Password

8) Update Dial Plan with "(*xx|[3469]11|0|00|[2-9]xxxxxx|1xxx[2-9]xxxxxxS0|xxxxxxxxxxxx.)"

9) Update Proxy

10) Submit All Changes

Everything else is default.

Line Trunk Groups

Click on L1 and change the Trunk Group to 1.

Do this for all other additional lines and then Submit All Changes.

Notes

After configuration the full config can be pulled off the device by changing the address to for example " http://172.30.60.218/admin/config.xml" <IP>/admin/config.xml

Copy the contents out and save it in the customer folder as CiscoBackup.xml.

This article describes the issue of an system booting from the backup root partition, after a file corruption occurs on the primary root partition. This article is targeted for SRX and EX devices at this time.

1. Problem

EX switches and SRX firewalls running Junos Release 10.4R3, or later, have added resiliency based on the "resilient dual-root partition", which if the switch detects a corruption on the primary root file system, it boots from the alternate root partition.

When this occurs, you are notified in two ways: Alarm and Warning Banner

1.1. Alarm

The following alarm message is generated:

user@switch> show chassis alarms

1 alarms currently active

Alarm time Class Description

2011-02-17 05:48:49 PST Minor Host 0 Boot from backup root

1.2. Warning

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

** **

** WARNING: THIS DEVICE HAS BOOTED FROM THE BACKUP JUNOS IMAGE **

** **

** It is possible that the primary copy of JUNOS failed to boot up **

** properly, and so this device has booted from the backup copy. **

** **

** Please re-install JUNOS to recover the primary copy in case **

** it has been corrupted. **

** **

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

2. Cause & Solution

It is likely that the file system became corrupted due to a sudden power loss, or ungraceful shutdown of the system.

Repairing the primary partition when it is corrupted:

When the primary partition detects a corrupt, the device boots from the backup partition; which then becomes the active partition. Remember that after every successive reboot, the system will try to reboot from the current active partition.

You can repair the primary partition, without any downtime. No reboot is required after running the following commands. However the Alarm and Banner will be displayed.

Note: As long as both of the partitions are healthy, there is no issue with running the switch on either of them. You only have to ensure that both the partitions are healthy, so that fail over can be done transparently between the two partitions, in case of any file corruption.

2.1. Verification

To verify if the primary partition is rebuilt, run one of the following show commands. The same commands also inform about which partition is the current active partition.

show system storage partitions

Sample output:

root> show system storage partitions

fpc0:

--------------------------------------------------------------------------

Boot Media: internal (da0)

Active Partition: da0s1a

Backup Partition: da0s2a <-- this is the backup slice

Currently booted from: backup (da0s2a) <-- shows booted from that slice

Partitions information:

Partition Size Mountpoint

s1a 184M altroot

s2a 184M /

s3d 369M /var/tmp

s3e 123M /var

s4d 62M /config

s4e unused (backup config)

3. Recovery Procedure

3.1. Copy JUNOS Image from Backup

Copy the Junos image from the backup partition to the primary partition, by using the following snapshot command:

For EX Switches:

request system snapshot media internal slice alternate

For SRX Routers:

request system snapshot slice alternate

You will see the following message as the media is copied over:

Formatting alternate root (/dev/da0s2a)...

Copying '/dev/da0s1a' to '/dev/da0s2a' .. (this may take a few minutes)

The following filesystems were archived: /

Note: This step ensures that you have consistent images on both the primary and backup partitions. This operation can take 5 to 10 minutes to complete.

3.2. Verify Partitions

The above command ensures that the alternate partition is repaired, without requiring a reboot. You can verify both the partitions by using the following command:

show system snapshot media internal

This will show the time/date stamp for both partitions, which should show the current date/time on the (primary) partition which has been restored. See sample output below:

For EX Switches:

root@ex> show system snapshot media internal

fpc0:

--------------------------------------------------------------------------

Information for snapshot on internal (/dev/da0s1a) (backup)

Creation date: Dec 17 16:58:29 2015 <-- Displays current date/time of operation in step 3.1

JUNOS version on snapshot:

jbase : ex-12.3R11.2

jkernel-ex-2200: 12.3R11.2

jcrypto-ex: 12.3R11.2

jdocs-ex: 12.3R11.2

jswitch-ex: 12.3R11.2

jpfe-ex22x: 12.3R11.2

jroute-ex: 12.3R11.2

jweb-ex: 12.3R11.2

fips-mode-arm: 12.3R11.2

Information for snapshot on internal (/dev/da0s2a) (primary)

Creation date: Dec 16 17:13:15 2015

JUNOS version on snapshot:

jbase : ex-12.3R11.2

jkernel-ex-2200: 12.3R11.2

jcrypto-ex: 12.3R11.2

jdocs-ex: 12.3R11.2

jswitch-ex: 12.3R11.2

jpfe-ex22x: 12.3R11.2

jroute-ex: 12.3R11.2

jweb-ex: 12.3R11.2

fips-mode-arm: 12.3R11.2

For SRX Routers:

root@srx> show system snapshot media internal

Information for snapshot on internal (/dev/da0s1a) (primary)

Creation date: Jan 22 23:48:47 2016 <-- Displays current date/time of operation in step 3.1

JUNOS version on snapshot:

junos : 12.1X44-D15.5-domestic

Information for snapshot on internal (/dev/da0s2a) (backup)

Creation date: Jan 1 06:08:27 2000

JUNOS version on snapshot:

junos : 12.1X44-D15.5-domestic

4. Reboot

In order to get rid of the alarm and ensure the partition has been repaired successfully, the system must be rebooted. There are 2 options to reboot given the environment the system is deployed in.

4.1. Reboot Now

If there is no risk to the network or customer, the system can be rebooted immediately. To get rid of the above alarm, use the following command to ensure that the switch boots from the primary partition:

For EX Switches:

request system reboot slice alternate media internal

For SRX Routers:

request system reboot

The system, after the above command is executed, will reboot from the primary partition. The alarm or the warning message will no longer be displayed.

4.2. Reboot Later

If the system needs to be rebooted after-hours, contact the customer and schedule the maintenance window. You may use the following command to schedule the reboot after X amount of minutes:

For EX Switches:

request system reboot slice alternate media internal in 480

For SRX Routers:

request system reboot in 480

Change the value after "in" to be the amount of minutes to reach the maintenance window scheduled with the customer. In this scenario, the system would reboot in 8 hours from the time the command is issued (60 minutes x 8 hours = 480)

5. Verify

Once the system has rebooted, run the following commands to ensure the system has booted back to the primary partition by going back to Step 2.1. Then run the following command to ensure the alarm is cleared:

show chassis alarms

You should no longer see the following alarm:

user@switch> show chassis alarms

1 alarms currently active

Alarm time Class Description

2011-02-17 05:48:49 PST Minor Host 0 Boot from backup root

Aastra 6700 Series

6731i

Featuring a 3 line LCD display, the 6731i supports up to 6 lines with call appearances, offers advanced XML capability to access custom applications and is fully interoperable with leading IP-PBX platforms.

Quick Start Guide

User Manual

Label Templates

Installation Guide

6735i

Providing dual Gigabit Ethernet ports via an integrated Gigabit Ethernet switch, the 6735i is built for todays high bandwidth network environments.

Quick Reference Guide

User Manual

Label Templates

Installation Guide

6737i

Providing impressive HD audio and support for todays high speed network through dual Gigabit Ethernet ports, the 6737i combines powerful features and flexibility in a standards based, carrier-grade advanced level expandable IP phone.

Quick Reference Guide

User Manual

Installation Guide

6739i

Featuring a 5.7 full color high resolution VGA touch screen display, the 6739i offers an intuitive graphical user interface, touch screen softkeys, full duplex wideband audio speaker and handset, built-in bluetooth interface and a USB port.

Quick Reference Guide

User Manual

Installation Guide

This guide covers the use of features available on the Aastra 6731i. Not all features may be available on your phone based on the configuration of your service. Please contact your TeleFlex representative if you would like access to additional features.

Placing a Call

Lift the handset(1), press the Linekey(13) or Speaker key(14). Dial the number from the keypad.

Answering a call

Lift the handset for handset operation or press the Linekey(13) or Speaker key(14) for hands free operation.

Ending a call

To end the call, replace the handset or press End button(11).

Redial

Press the Redial key(15) twice to call the last dialed recently dialed number. Press the (15) key once to access the list of recently dialed numbers, use to scroll through.

Muting a call

Press Mute key(19) to mute the handset, headset, or speakerphone.

Place a call on Hold

Press Hold Key(16) and hangup the phone. Retrieve the call by pressing the Hold Key again(16).

Call Transfer

Press Transfer key(12) this places the current call on hold. Dial the number of the person you want to transfer the call to. To transfer the call before the other person answers, press key before the Transfer Key(12) the receiving end answers.

Voicemail

Press Voicemail Key(6) or dial *97. At the prompt enter your 4-digit PIN code(default PIN is 9999) Once logged in, press 0 to manage your greeting and options.

This guide has been tested with latest firmware version. Be aware that different firmware revisions may have different web interface formats and functionality.

This guide is based on a new phone OR one that has been reset to factory defaults. If in doubt, reset the phone to Factory Defaults.

Supported phones are the following models: 6730i, 6731i, 6735i, 6737i, 6739i, 6751i, 6753i, 6755i, 6757i

The preferred method to configure an Aastra phone is via Provisioning. You can however follow this guide to manually configure your phone.

Identify IP & Login to Web GUI

Start up the phone and identify its IP Address using the menu key on the phone, go to the Administrator Menu option, key in your password (default password 22222 and the default we use are "31573" or "43628"). Select Network Settings followed by IP Address.

Point your browser to the IP address of the phone to access the web interface.

Enter the login credentials (default username admin; default password 22222 and the default we use are "31573" or "43628")

Advanced Settings > Global SIP

In the Basic SIP Authentication Settings section:

Set the Phone Number field to the SIP username you want to associate with this phone.

Set the Authentication Name field to the SIP username as well.

Set the Password field to the extensions SIP Password.

Check the box to enable Call Waiting.

In the Basic SIP Network Settings section:

Set the Proxy Server field and the Registrar Server field to the IP or the FQDN to sbc01.teleflexnet.net.

Set the Proxy Port field and the Registrar Port field to 5060.

Advanced Settings > Line 1

In the Basic SIP Authentication Settings section:

Set the "Screen Name" field to the full name shown for the extension.

Set the "Screen Name 2" & "Caller ID" fields to the extension number.

Set the Phone Number field to the SIP username you want to associate with this phone.

Set the Authentication Name field to the SIP username as well.

Set the Password field to the extensions SIP Password.

Basic Settings > Preferences

In the "Outgoing/Incoming Intercom Settings" section:

Set the "Type" field to Server-Side.

Set the "Prefix Code" field to *96.

Set the "Line" field to 1.

Select the check box for "Auto-Answer" and "Play Warning Tone" so they are enabled.

In the "Directed Call Pickup Settings" section:

Select the check box for "Directed Call Pickup" so it is enabled.

Set the "Directed Call Pickup by Prefix" field to *93.

Advanced Settings > Network

***THIS STEP SHOULD ONLY BE COMPLETED IF THERE IS A SEPERATE VLAN FOR THE VOICE NETWORK***

In the "VLAN" section:

Select the check box for "VLAN Enable" so it is enabled.

Set the "VLAN ID" field to the voice VLAN ID, which is usually 500.

PROBLEM DESCRIPTION

The issue is that the OpenSSL library version 1.0.1 (versions 1.0.1 to 1.0.1f) contains a securityflaw, which allows an attacker to trick the server into returning 64kB of memory from the server process memory. This can be done without having to log in or authenticate first. The reason for this is a feature called heart beat (RFC 6520) which was added to OpenSSL version 1.0.1. When the featurewas added, a flaw allowed the client to request that the server return 64kB of data. Depending on what this data contains, the attacker may gain access to user credentials or certificates.

For more information, please refer to these articles:

Critical crypto bug in OpenSSL opens two-thirds of the Web to eavesdropping

Critical crypto bug exposes Yahoo Mail, other passwords Russian roulette-style

To find out more and how to protect your devices, visit:

http://portalgb.knowledgebase.net/article.aspx?article=314301&p=4739

Determine Model / Current Firmware

To being, we must confirm the model of the Nano by consulting the device in Salsa. This is done under Supervision > ip|engine status.

In the consult window, refer to the Version line. This shows:

The current firmware version.

The model code (TAG) of the unit.

Identifying Model

Based on the model code below, you can match to the model number chart shown here. See Step 2 above.

WARNING: CHECK VERSION

The ip|engine you are upgrading MUST be on version 7.1 MINIMUM before attempting to upgrade to any 8.x version.

Upload Firmware Files to ip|engine

Enable the local FTP Daemon on the ip|engine.

SSH to the IP|Engine using username and password:

ipanema

Enable FTP Daemon

Activate the ip|engine's ftp server with the following commands:

netconfig +ftp

netconfig restart

Upload Firmware Files

Using an FTP client of your choosing (Filezilla recommended), upload the 3 firmware files needed to the ip|engine.

The pre-packaged files needed for the upgrade are located in Box within the following directory:

\Box Sync\Hardware\Ipanema\Firmware

Use the file name that corresponds with the Model you located in the above section "Identifying Model". Extract the archive and upload the 3 files extracted to

Upgrade Command

Use the ip|engine as its own ftp server, so use the upgrade command:

upgrade -s 127.0.0.1 -d / -l ipanema -p ipanema -v

You should see output similar to the following:

[ipe]$ upgrade -s 127.0.0.1 -d / -l ipanema -p ipanema -v

upgrade = running

[ VERBOSE MODE ]

Start download

Downloading ipe_n5V2_v8.1.5.4.tgz package

Download completed

Decrypt tarballs

Installing ipe_n5V2_v8.1.5.4.tgz package

[ipe]$

The ip|engine will then automatically reboot and load the new version.

Verify Version

Once the reboot is completed, you can verify the new version by connecting back to the ip|engine and running the following command:

version

In which you will see the following output to confirm the upgrade:

*** Hardware ***

Tag : 30H1

Name : n0005-256MB-F128

Rev. : XX

S/N : S2813N0219B0

*** Software ***

Global : 8.1.5

Kernel : 8.1.5.4

Cots : 8.1.5.4

Ipe : 8.1.5.4

Date : Mar 20, 2015 13:27:44

Ipanema features are performed by Ipanema appliances, virtual machines and software agents, generally located at the interface between the enterprise network (LAN) and the access router to the operator network (WAN).

There are two families of appliances: ip|engines and nano|engines, and two families of software agents: virtual|engines and Ipanema Mobile Agents (IMAs).

Application Visibility and Application Control features are also available on sites that are not equipped (no ip|engine, no nano|engine and no virtual|engine on the site), declaring tele|engines on these sites.

ip|engines: hardware devices; various models are available, with different capacities

nano|engines: hardware ultra compact devices, for small Branch Offices

tele|engines: logical service delivered through the remote collaborating ip|agents

virtual|engines: virtual machines in .vmdk format

IMAs: software agents for Windows desktops

ip|agent is the software running on ip|engines, nano|engines and virtual|engines. IMAs run some of ip|agents services (but we also call them ip|agents, by extension).

To provide the features described above, ip|agents run the following services:

for Application Visibility:

ip|true: measurement,

ip|sync: time synchronization,

for Application Control:

ip|fast: the Application Control service,

ip|coop: tele|engines cooperative control,

for WAN Optimization:

ip|xtcp: TCP acceleration,

ip|xcomp: compression (SRE and ZRE) + TCP acceleration,

ip|xapp: CIFS acceleration,

for Network Rightsizing:

smart|plan

for Dynamic WAN Selection:

smart|path

Aastra 9133i and 9112i

Press the Options hardkey

Scroll down to Phone Status and press Enter softkey

Scroll down to Network Port 1 and press Enter softkey

The IP address of your phone will be displayed if it has been set properly

Aastra 480i

Press the Options hardkey

Scroll to Phone Status and press the Show softkey

Scroll to Network Status and press the Show softkey

Press the IP Addr softkey.

The IP address of your phone will be displayed if it has been set properly

Polycom SoundPoint IP 501, 601, 550, 650

Press the Menu hard key

Scroll to Status and press the Select softkey

Scroll to Network and press the Select softkey

Scroll to TCP/IP Parameters and press the Select softkey

The IP address of your phone will be displayed if it has been set properly

Polycom SoundPoint IP 320/330

Press the Menu hard key

Select Status on the LCD display and press the checkmark hard key (in the middle of the four arrow keys)

Select Network on the LCD display and press the checkmark hard key

Select TCP/IP on the LCD display and press the checkmark hard key

Polycom SoundStation IP 4000

Press the Menu hard key

Scroll to Status and press the Select hardkey

Scroll to Platform and press the Select hardkey

Scroll to Phone and press the Select hardkey

Scroll down to show the IP address

The IP address of your phone will be displayed if it has been set properly

Cisco 7960

Press the Settings hard key

Scroll to to highlight 3. Network Configuration and press the Select softkey

Scroll to to display the IP address

The IP address of your phone will be displayed if it has been set properly

This article will go over how to access and setup your voicemail box.

How to Access Your Voicemail

You can access your mailbox, as well as shared mailboxes from both your phone at your desk; and when you are away from your office.

To access your mailbox from your phone, dial *97 on your phone or press the Messages/Voicemail button.

Enter your password, The default password is: 9999

To access a shared mailbox or to access your mailbox on another phone, dial *98.

To access your mailbox from outside the office, dial your DID and wait for your voicemail greeting. Press the * key to access the mailbox menu.

Record Your Unavailable Message

To record the message that people will hear when you are unavailable, follow these steps.

Access your mailbox using one of the methods listed in "How To Access Your Voicemail"

Dial 0 for mailbox options.

Dial 1 to record your unavailable message.

Then dial either 1 to ACCEPT the message, 2 to REVIEW the message, or 3 to RE-RECORD the message.

Record Your Busy Message

To record the message that people will hear when you are currently on the phone and cannot accept any more calls, follow these steps.

Access your mailbox using one of the methods listed in "How To Access Your Voicemail"

Dial 0 for mailbox options.

Dial 2 to record your busy message.

Then dial either 1 to ACCEPT the message, 2 to REVIEW the message, or 3 to RE-RECORD the message.

Record Your Name

To record your name that people will hear when they use the dial by name directory, follow these steps.

Access your mailbox using one of the methods listed in "How To Access Your Voicemail"

Dial 0 for mailbox options.

Dial 3 to record your name.

Then dial either 1 to ACCEPT the message, 2 to REVIEW the message, or 3 to RE-RECORD the message.

Record and Enable a Temporary Message

Access your mailbox using one of the methods listed in "How To Access Your Voicemail"

Dial 0 for mailbox options.

Dial 4 for the temporary greeting menu.

Dial 1 to record your temporary message.

Then dial either 1 to ACCEPT the message, 2 to REVIEW the message, or 3 to RE-RECORD the message.

Once you have accepted your temporary greeting, it will take presedence over your other greetings and will automatically be enabled.

To disable the greeting, follow steps 1 through 3. Then dial 2 to erase your temporary message.

Checking Your Messages

Access your mailbox using one of the methods listed in "How To Access Your Voicemail"

Dial 1 to review your messages.

Follow the guide above to navigate the messages menus.

Thanks to our awesome customer's feedback, TeleFlex has isolated and fixed a couple key issues reported. See below for more detail.

"Submit a request" button wasn't working

The "Submit a request" button at the top of the web site would not take you to the new request form. We have fixed the way the button is linked and it is now fully functional.

Font not legible in comments

The web font used to render the text for ticket comments was set to a low weight, causing the font to be un-legible. We fixed the font weight and size for an easier to read experience.

When a support representative requests for you to run a line quality test, this is the procedure that is used to gather the information.

Navigate to Pingtest.net

In your web browswer visit http://www.pingtest.net, or click on this link.

Begin Test

Click on "BEGIN TEST" toward the top of the page.

Monitor Progress

The testing modes will run in sequence once it locates the best server to process your request.

Copy Test Results Link

Put your cursor over the button labeled "DIRECT LINK". It will highlight the button and then say "COPY". Click the button once to copy a direct link to your results.

Paste Test Results Link

Go back to your ticket in the TeleFlex Support Portal, and right-click > paste the link into the comment are of the ticket. You can also paste this into an email directly to one of our support staff or at [email protected]