2012A Toshiba UCS IPedge Training UCS Website July 2012 IPedge Version 1.1 Calvin Lee
Agenda IPT Survivability IPT Auto Config T.38 Fax EC RAID 1 EM RAID 5 Hard Drive Redundancy Follow Me Enhancement
IPedge Version 1.1
IPT Survivability The Toshiba IPedge system achieves survivability by combining technologies from IPedge Net multi-route programming, IP Mobility and SIP Trunking. By combining these technologies, the Toshiba IP telephones are able to survive by automatically connecting to a secondary IPedge system and still maintain station-to-station calling, inter-node calling, outbound dialing, and access to voicemail resources and Call Manager. Incoming call routing can be achieved by having the service provider manually re-route all the incoming calls to the secondary IPedge system
IPT Survivability Node 10 Primary Server Node 11 Secondary Server IPT switches the connection to Secondary Server when the following occurs. When IPT detects the alive of the Primary Server, IPT returns to Primary Server connection (1) IPT cannot connect to Primay Server (2) IPT cannot detect Keept Alive packet between Primary Server and IPT IP Phone
IPT Survivability
IPT Survivability If the IPT connects to the secondary (fail-over) server and the user wishes to register to the primary server, use one of the following: a) Remove then, apply IPT power to cause an IPT reboot. b) Disconnect the LAN cable from the IPT, wait 30 seconds then, connect the cable to cause a keep-alive failure. c) Manually reset the IPT (9-line LCD IPTs only) d) Keep-alive failure is no keep alive packet from the server for 20 seconds.
IPT Survivability Features CIX Survivability IPedge Phase 1.0 (Basic Survivability) Automatic Failover Supported Supported Supported Automatic Failback Not-Supported Supported but will failback as soon as it detects the Primary server is operational Speech Path Survivability Automatic Routing Configuration Not Supported Supported Supported Not Supported Not-Supported Supported IPT Supported Supported Supported SoftIPT Supported Supported Supported Voice Assistant N/A N/A N/A Call Manager N/A N/A Phase 1.2 IPedge Phase 1.1 (General Survivability ) Supported and will only failback when it detects the IP phones are IDLE
IPT Survivability Survivability Matrix This table and the example in the figure shown below demonstrate IPT Survivability when, in this example, the Primary Server fails
IPT Survivability CAPACITY The number of IPTs using the survivability feature in one IPedge Server is 1000 The number of IPTs using the survivability feature in one IPedge network is 6000. The maximum number of servers in one IPedge network is 128. Note: This feature requires an endpoint license for each survivability primary and secondary servers AVAILABILITY RESTRICTION The survivability feature is available for: > IPT Telephones > SoftIPT Does not apply to SIP Telephones, telephones via gateways, trunks, IPedge trunks or, SLT, Door Phones and Pagaing via gateways
IPT Survivability License A license is required on the secondary server for each survivable station. The licenses are:
IPT Survivability Assign Member Node 1. Login to Enterprise Manager on the IPedge server that you want to be a member of an enterprise. Use the IP address of the server to access Enterprise Manager on that node. 2. Select Administration > Enterprise > Server Management. 3. Click on the Member Server radio button. 4. Enter the Primary Server IP address. 5. Enter the Community Name you assigned to this member server earlier. 6. Click on the Save icon. 7. The server will stop accepting commands.
IPT Survivability
IPT Survivability Add Member Node 1. Login to the primary node Enterprise Manager. 2. Select Administration > Enterprise > Servers. The first time you enter this screen the Server Name list will be empty. 3. Click on the Add icon. 4. Enter the Server Name, IP Address and Community Name of the member node to be added. 5. Click on Detect Server Information. The System Type, Version and Mac Address information will be displayed. 6. Enter location and any other useful information into the Description box. 7. Click on the Save icon. 8. Click on the Search icon to display the server list.
IPT Survivability
IPT Survivability Attach Member Node 1. If the server list is not displayed select Administration > Enterprise> Servers. 2. Click to check-mark the member server to attach. 3. Click on the Attach icon. 4. The primary node will start the database synchronization process. This can take several seconds to a few minutes. The Database Status indicator will change to green when complete. Click on the Reload icon to refresh the status display. Note: The database synchronization can take several minutes. 5. You can Add and Attach other member nodes while the database sync process is running. When the database synchronization is done the node is connected.
IPT Survivability
IPT Survivability Assigning Survivable Station 1. Select Station > Station Assignment. 2. Check the Station to be programmed. 3. Click on Edit icon. 4. Check-mark the Survival Station check box. 5. Select the Survivability Secondary Server (the fail-over server) from the pull-down list. 6. Click on Save icon. The station will be created in the secondary server automatically. If the DN already exists in the secondary server an error message will be displayed. The station will not be created on the primary server.
IPT Survivability
IPT Survivability Displaying Survivable Stations 1. Select Station > Survivability. 2. Select the server to display. The list of survivable stations on the selected server will display. 3. Select the Primary/Secondary Destinations tab. The list of possible secondary servers for the selected primary will display. 4. Select the Configuration Conflicts tab. 5. Select the Configuration Conflict Category. Click on the Detect Conflicts icon. Any conflicts detected will be displayed.
IPT Survivability
IPT Survivability Adding Secondary Server IP Address on Survivable Stations 1. Select Station > IPT Auto Config. 2. Enter the Primary & Secondary server IP addres 3. Click Submit
IPT Auto Config The IPT Auto Config feature automatically performs the IPT station configuration functions that otherwise requires manual entry at the station location. The manual process requires that each station be connected and then configured using the IPT keypad. With IPT Auto Config there is an ease of initial intallation and maintenance. if the Primary Server IP has to be changed for a large group of IPTs, this can now be accomplished with a single configuration change on the server and the change can be propagated to all IPTs at once.
IPT Auto Config Prerequisites All of the following perquisites must be completed before the IPT is connected to the network IPT with IPT Auto Config is connected to IPedge only and not CIX IP Telephones must be at firmware level: 5Kx-M2M3 (or later) IP Telephone must be set to factory default (new, out of the box or reset to factory default)
IPT Auto Config Current IPT Deployment: N Phones = At least N times ( 3+6+9+Hold + Phone Configuration)
IPT Auto Config New IPT Deployment Model: 1. Configuration for each phone done/saved on IPedge (done via GeM) 2. DHCP Server points IPT to IPedge server for configuration 3. IPT downloads configuration, saves it and uses it on subsequent restarts 4. NO MORE 3+6+9+HOLD
IPT Auto Config Configuration: 1. Goto Station=>IPT Auto Config 2. Enter the Primary and Secondary Server IP Address 3. Click Submit
IPT Auto Config Auto Config Parameter Default Values
T.38 Fax T.38 is a Fax communication protocol for an IP network. Converts Fax signaling used in an analog subscriber network into IP messages. T.38 requires both ends of the connection (i.e. SIP trunk provider and IPedge) to participate in the T.38 transmission. Addresses common IP line disruptions (i.e. jitter, packet loss) that can interrupt a fax transmission. T.38 is a superior and more reliable method of fax over IP compared to sending fax signals over G.711 (aka fax pass through). In a pure SIP environment (SIP trunks and stations only) no additional gateways or other hardware is required. No programming required. Detect automatically.
T.38 Fax SIP Trunking LAN G3 Fax FXS Gateway
EC RAID 1 Toshiba's I-EC-1A server has the ability to be upgraded to support RAID1 hard drive redundancy. Offered as an Upgrade Kit only for I-EC-1A Kit will include 250GB Hard Drive, pre-installed in RAID drive drawer with labels to identify drives RAID Controller is embedded in motherboard Upgrade process requires re-image of drives to properly install all necessary software drivers RAID drives cannot be hot swapped at this time System must be re-started in order to recognize the new drive RAID drive cannister/drawer DOES support hot swap.
EC RAID 1 WebMin > IPedge > RAID
EC RAID 1
EC RAID 1 Status for RAID device Unsetting Clean Degraded Recovering : RAID is not configured yet : Both HDDs are working correctly and both are synchronized correctly : Two HDDs are not synchronized due to HDD failure or HDD replacement : The HDD is rebuilding Status for physical device configuring RAID Normal Failed Removed Recovering : Working correctly : HDD failure : HDD was replaced, but not synchronized yet. HDD does not exist physically : HDD synchronizing
EC RAID 1 Removing a failed Drive on EC 1) WebMin > IPedge > RAID 2) Click on /dev/sdx1 or /dev/sdx1 (or sdx2). Webmin will select the whole drive.
Removing a failed Drive on EC 3) Select Remove and click Ok. EC RAID 1 4) When the status shows the drive is Removed you can physically remove the HDD from the server.
EC RAID 1 Adding a new Drive on EC 1) Click on the physical device to be added 2) Select Add from the drop down then click on Ok 3) The IPedge system will start the recovery process. This will take hours to finish.
EM RAID 5 Hard Drive Redundancy Toshiba is now offering a second option for hard drive redundancy on their IPedge EM server. Currently, all EM servers ship with RAID1 redundancy, but now EM servers can support RAID5 redundancy.
EM RAID 5 Hard Drive Redundancy Functional Description With RAID5 a total of four hard drives are used to ensure 24/7 operation. Three of the four drives run online and are configured in RAID5 with striping, with the fourth drive set up as a hot spare. If one of the 3 online drives fails, the hot spare drive immediately begins to prepare to take over as an online drive. When the failed drive is replaced, it becomes the new hot spare. New EM Server Model This new model of EM server ships factory configured with a RAID controller card and four 300 gigabyte SAS hard drives. All necessary drivers for RAID5 functionality are also pre-installed in the factory software image. Technicians need only power up the system and begin programming as normal. Due to the complexity of the assembly and configuring of the server for RAID5, Toshiba will not be offering a field upgrade kit for existing EM servers.
EM RAID 5 Hard Drive Redundancy
EM RAID 5 Hard Drive Redundancy WebMin > IPedge > RAID 5
EM RAID 5 Hard Drive Redundancy
EM RAID 5 Hard Drive Redundancy
EM RAID 5 Hard Drive Redundancy
EM RAID 5 Hard Drive Redundancy
EM RAID 5 Hard Drive Redundancy
Follow Me Enhancement The new enhancements of the Follow Me feature provides simultaneous ring through IPedge Net Server. Follow Me feature control button on the phone User can now assign the button for Follow Me feature and activate and deactivate the feature from the button on the IP Telephone to easily change the operation when users are in the office or on the road. Hand-off When the user take the call from the cell phone and return to the office, the call can be easily handed off to the desktop phone by pressing the same button.
Follow Me Enhancement Status Indication The button has the LED to show the status of the Follow Me feature as shown below.
Follow Me Enhancement System Requirement Follow Me enhancement requires the Net Server to be running. IPedge built-in Net Server is required to take advantage of the enhancement. License Requirement When IPedge built-in Net Server is used, the system has the necessary license, and no additional license is required to use the enhancement. Software Requirement New enhancements require the IPedge system software 1.1.208
Follow Me Enhancement Voice Mail Resource Requirement Follow Me, requires two voice resources while the call is active. The following table shows a typical requirement for the voice resource (I-MSG-CH). Please note that the resource requirement depends on the number of destinations, talk time, and voice mail traffic.
Follw Me Enhancement IPedge Messaging / Net Server PSTN Simultaneous Ring Mobile Phone IP Phone
Follow Me Enhancement 1) Specify the Net Server IP address (use 127.0.0.1 for IPedge) 2) Net Server port (default is 8767). 3) Use the voice mail pilot number as Net Server User / Password / Extension. 4) Specify 80(default) for the Handoff application.
Follow Me Enhancement 5) Assign Follow Me feature on IP telephone flexible buttons. This button is used to activate / deactivate the Follow Me feature and hand-off the call
Follow Me Enhancement 6) Check NetServer Monitor box for Net Server integration in the mailbox email setting menu.
Follow Me Enhancement 7) The administrator can enable or disable the follow Me to Remote Destination button in IPedge Messaging 8) Item 7) has the same effect as the Follow Me button on the phone. If the feature is disabled from this menu, the Follow Me button on the phone turns off.
Follow Me Enhancement 9) Setup Personal Schedule from the mail box menu. The user can specify the sequential ring or simultaneous ring as well as scheduled based, caller ID based call control.