1 © 2008 Avaya Inc. All rights reserved. Avaya IP Office 4.2 Enhancements New Product Introduction...

1© 2008 Avaya Inc. All rights reserved.

Avaya IP Office 4.2 EnhancementsAvaya IP Office 4.2 EnhancementsNew Product Introduction Team4.2 NPI


IP Office 4.2 Enhancements

Avaya OneX Mobile

Voicemail Pro UMS and Web Client Enhancements

IP 1600 Telephone

Embedded VoiceMail to Email


IP Office OneX Mobile IP Office OneX Mobile Mobile Call control


One-X Mobile for IP Office

Features, Programming and Setup

–Supported OS

–Supported Phones

–Features

– IP Office Programming

–Phone Setup

–Tips and Tricks



Supported OS

–Windows Mobile 5 (WM5 – Patch Build from E.I.)

–Windows Mobile 6 (WM6)

–Symbian (Single Mode Only)

• Firmware is dependant on phone type.

• WM 5 - issues integrating FNE into IP Office. The Patch release for trial is available from the E.I. department for Beta Trial, fixing WM 5 One X Client integration and IP Office 4.2 core integration.



Features

–A Feature Name Extension (FNE) is a number you can dial that allows you to access an Avaya IP Office feature from your cell phone.

–All FNEs MUST be associated to a DID/DDI that comes in over a IP500 Universal PRI/ E1 card.



WM6 FNE Settings

–Required settingsFNE Translation for IPO and Required Entry Data Settings.INI file (to be Administered) and copied to WM 6

One-X client

Required Entry Fill LOCATION_NAME = TestNPI;

Required Entry Fill DID_PREFIX = 219;

Required Entry Fill INTERNATIONAL_DIRECT_DIAL_PREFIX = 011;

NATIONAL_DIRECT_DIAL_PREFIX = 1;

Required Entry Fill HOME_COUNTRY_DIAL_CODE = +1;

Optional Entry Fill ARS_CODE = ;

Required Entry Fill EXTENSION_LENGTH = 5;

Required Entry Fill NATIONAL_NUMBER_LENGTH = 10;

Required Entry Fill USERS_EMERGENCY_NUMBERS = 999,911;

SETTINGS_PIN = ;

Note that the Extension Length should be equal to the maximum shortcode length E.g – Extension_Length = 7; if maximum shortcode is *5 123N #



WM6 FNE Settings–settings.ini file

This is the number you receive when you get a DID call.

If you receive 5 digits then you will put the first 3 here.

If you receive 10 then you will put the first 8

ALL entries MUST be in front of the

semi-colon.



FNE 00 - System (IPO) Dial Tone IDLE APPEARANCE SELECT = ;

FNE 01 - Steal Call ACTIVE_APPEARANCE_SELECT = ;

FNE 02 - Auto Call Back AUTO_CALL_BACK_TOGGLE = ;

Not Supported on IPO - FNE 03 DISABLE_AUTO_CALL_BACK_TOGGLE = ;

FNE 04 - Forward All Calls CALL_FORWARDING_ALL_ACTIVATION = ;

FNE 05 - Forward Busy and No Answer Calls CALL_FORWARDING_BUSY_NO_ANSWER_ACTIVATION = ;

FNE 06 - Call Forward Disable CALL_FORWARDING_DISABLE = ;

FNE 12 - Withheld CLI (To External Calls off IPO) CALLING_PARTY_NUMBER_BLOCK = ;

FNE 13 - Enable CLI (To External Calls off IPO) CALLING_PARTY_NUMBER_UNBLOCK = ;

FNE 07 - Park Call CALL_PARK = ;

FNE 10 - Directed Call Pick Up CALL_PICKUP_DIRECTED = ;

Not Supported on IPO – FNE 11 CALL_PICKUP_GROUP = ;

WM6 FNE List



WM6 FNE List

FNE 09 - Pick Up Group CALL_PICKUP_GROUP_EXTENDED = ;

FNE 08 - Call UnPark CALL_UNPARK = ;

FNE 14 - Conference Add CONFERENCE_ON_ANSWER = ;

FNE 15 - Drop Call DROP_LAST_ADDED_PARTY = ;

FNE 16 - Private Call (cannot be intruded or recorded) EXCLUSION = ;

FNE 17 - Held Appearance Select HELD_APPEARANCE_SELECT = ;

FNE 18 - Same as FNE 00 - Dial Tone Appearance (a=) IDLE_APPEARANCE_SELECT = ;

FNE 20 - Disable Twinning OFF_PBX_DISABLE = ;

FNE 19 - Enable Twinning OFF_PBX_ENABLE = ;

Not Supported on IPO – FNE 21 LAST_NUMBER_DIALLED = ;



WM6 FNE List

Not Supported on IPO – FNE 22 MALICIOUS_CALL_TRACE = ;

Not Supported on IPO – FNE 23 PRIORITY_CALL = ;

FNE 24 - DND On SEND_ALL_CALLS_ENABLE = ;

FNE 25 - DND Off SEND_ALL_CALLS_DISABLE = ;

FNE 26 - Blind Transfer TRANSFER_ON_HANGUP = ;

FNE 27 - Transfer to Voicemail TRANSFER_TO_COVERAGE = ;

FNE 29 - Call Voicemail Direct SPEECH_ACCESS_NUMBER = ;

Not Supported on IPO – FNE 30 SINGLE_DDI = ;

FNE 31 - Star Star Service NOT REQUIRED TO BE IMPLEMENTED ON IPO



WM6 settings.ini file

–Putting it together



Symbian FNE Settings

–settings.1xme file

–All non-FNE fields are mandatory except the SETTINGS_PIN field.



Symbian FNE Settings

The full DID must be entered into this field

ALL entries MUST be in front of the

semi-colon.



Symbian settings.1xme file

–Putting it together



FNE 00 - System (IPO) Dial Tone IDLE APPEARANCE SELECT = ;

FNE 01 - Steal Call ACTIVE_APPEARANCE_SELECT = ;

FNE 02 - Auto Call Back AUTO_CALL_BACK_TOGGLE = ;

Not Supported on IPO - FNE 03 DISABLE_AUTO_CALL_BACK_TOGGLE = ;

FNE 04 - Forward All Calls CALL_FORWARDING_ALL_ACTIVATION = ;

FNE 05 - Forward Busy and No Answer Calls CALL_FORWARDING_BUSY_NO_ANSWER_ACTIVATION = ;

FNE 06 - Call Forward Disable CALL_FORWARDING_DISABLE = ;

FNE 12 - Withheld CLI (To External Calls off IPO) CALLING_PARTY_NUMBER_BLOCK = ;

FNE 13 - Enable CLI (To External Calls off IPO) CALLING_PARTY_NUMBER_UNBLOCK = ;

FNE 07 - Park Call CALL_PARK = ;

FNE 10 - Directed Call Pick Up CALL_PICKUP_DIRECTED = ;

Not Supported on IPO – FNE 11 CALL_PICKUP_GROUP = ;

Symbian FNE List



Symbian FNE List

FNE 09 - Pick Up Group CALL_PICKUP_GROUP_EXTENDED = ;

FNE 08 - Call UnPark CALL_UNPARK = ;

FNE 14 - Conference Add CONFERENCE_ON_ANSWER = ;

FNE 15 - Drop Call DROP_LAST_ADDED_PARTY = ;

FNE 16 - Private Call (cannot be intruded or recorded) EXCLUSION = ;

FNE 17 - Held Appearance Select HELD_APPEARANCE_SELECT = ;

FNE 18 - Same as FNE 00 - Dial Tone Appearance (a=) IDLE_APPEARANCE_SELECT = ;

FNE 20 - Disable Twinning OFF_PBX_DISABLE = ;

FNE 19 - Enable Twinning OFF_PBX_ENABLE = ;

Not Supported on IPO – FNE 21 LAST_NUMBER_DIALLED = ;



Symbian FNE List

Not Supported on IPO – FNE 22 MALICIOUS_CALL_TRACE = ;

Not Supported on IPO – FNE 23 PRIORITY_CALL = ;

FNE 24 - DND On SEND_ALL_CALLS_ENABLE = ;

FNE 25 - DND Off SEND_ALL_CALLS_DISABLE = ;

FNE 26 - Blind Transfer TRANSFER_ON_HANGUP = ;

FNE 27 - Transfer to Voicemail TRANSFER_TO_COVERAGE = ;

FNE 29 - Call Voicemail Direct SPEECH_ACCESS_NUMBER = ;

Not Supported on IPO – FNE 30 SINGLE_DDI = ;



IP Office Programming–Requirements

• 4.2 Core

• Mobility Licensing

• Mobile twinning number assigned as Cell phone number for the user

• Available DID/DDI numbers (Equal to the number of features you wish to implement)



IP Office Programming

–Setting up your Incoming Call routes.

–Each DID/DDI must go to a Short Code.

In this case I used 777 as a primer to the Short Code




–The destination Short codes match up to the FNE feature set.




–Mobile Features- must be checked.

–Twinned Mobile number- must be filled in.

–Can have one-X Mobile client- must be checked



WM6 – one-X Client Installation

– download the One-X software to the WM 6 Cell Phone

– Copy the Settings.ini file using the necessary admin tools




– Copy the Settings.ini file using the necessary admin tools to the correct folder as instructed from the installation procedures




– from the cell phone, select Avaya One-X and from Menu, Settings, Options, Admin > Install configuration file

– navigate to the “settings.ini” file and load into the Cell phone




– Selecting the “Manage Configuration File” will allow the settings.ini file to be cross checked to ensure it has loaded correctly



Symbian – one-X Client Installation– Install the Nokia PC Suite

that comes with your phone.

–Connect your Phone.

–Click on the Install Applications button.



Symbian – one-X Client Installation–Choose the correct file and location to install the

application.

–Follow the instructions/ prompts on the phone.



Symbian – one-X Client Installation–Return to the PC Suite and

choose the File manager to move the modified settings file

to the phone.

–Open the one-X client and press Menu > Settings > Download Config File > Menu > Select File.

–Then find the settings file to enable.


4.2 Voicemail Pro UMS and Web Client Enhancements 4.2 Voicemail Pro UMS and Web Client Enhancements


NOTE - IP Office 4.2 UMS license stops the IMS integration

The UMS License will stop all previous voicemail pro “IMS” integration. IMS and UMS cannot work together.


IP Office 4.2 - Core programming IP Office Programming Enter the new UMS license for 4.2

operation of UMS and Web Client on the IP Office license.

Double Click on the License to enter the UMS Users

The UMS and Web Services work when the User “Voicemail” details are checked on.


IP Office 4.2 - Core programmingIP Office Programming

The Voicemail Code is utilised for the UMS IMAP Client integration (Outlook Integration) when setting up the IMAP Client configuration.It is also used for the Web Client integration when logging in via the browser.

The 4.2 Voicemail UMS and Web client integration both require the UMS Web Services to be checked ON.


IP Office 4.2 - Core programming4.2 Voicemail Pro Installation Wizard

The IMAP server is laid down during installation and requires no check box selection.

The Web services associated with 4.2 Voicemail Pro requires the “Web Voicemail” option checked in the installation wizard.

4.2 voicemail installs a Microsoft Access Database

supporting the web client interface


Voicemail Pro IMAP Client Set UpExample of Outlook Client configuration

Example instructions as to how the Outlook Client will connect to the IMAP server. The Outlook Client provides the capability for the desktop application to connect to an IMAP Server (Voicemail Pro 4.2)The option can be configured from the Outlook Toolbar under ‘Tools’, ‘Options’, ‘Mail Setup’, ‘Email Accounts’.


Voicemail Pro IMAP Client Set UpWhen adding the IMAP Server to Outlook, check ‘add a new e-mail account’ option and select next.

On the Server Type page check the IMAP option and select next


Voicemail Pro IMAP Client Set UpThe Internet E-Mail Settings screen which requires the IMAP server information to be entered.

Voicemail Pro fully qualified domain name

Domain name and email address

Exchange Server fully qualified domain name

IP Office User Name and Voicemail Code


Voicemail Pro IMAP Client Set UpSelecting Next to move on to the next screen presents you with a successful connection.


IP Office 4.2 - Voicemail Pro UMS – Operating on Outlook

New messages will be populated in the new Inbox created for the IMAP Client as programmed above. Messages are synchronised and will remove the telephone message waiting light when opened.

New Messages will be presented with a closed envelope.

Priority Messages will be presented with a leading exclamation mark.

Read Messages will be presented with an open envelope.


IP Office 4.2 - VM Pro Enhancements

The URL is http://”voicemail server name”/voicemail

4.2 Web Client require the User to login with their User name and voicemail password

Click on “Login” to enter Web client

4.2 Voicemail Pro Browser Web Client


IP Office 4.2 - VM Pro Enhancements4.2 Voicemail Pro Browser Web Client

Log out / sign out button

New voice messages have sealed Envelope Icon

Change password option

Click on the Loudspeaker to Listen



Messages can be played via the Handset or Media Player

Media Player will display the slide incrementing whilst playing the message

Saved Messages will be marked with the disk Icon.

Saved messages can still be deleted when marking the message with the Delete option



Messages can be forwarded to other users on the SCN


IP Office 4.2 IP 1600 Telephone IP Office 4.2 IP 1600 Telephone


IP Office 4.2 - IP 1600 Handset Association to Core

IP 1603

IP 1608

IP 1616

When initially taking the IP 1600 telephone out of the box, the phone will need to run through a process of upgrades and downloads to establish operation with the associated IP Office

This Process can take up to 6 minutes. This can be quite disconcerting and could lead to an engineer “pulling the plug” on the phone, assuming that it does not work.

This slide show instructs on the set up requirements when using the IP Office as a DHCP server to associate IP addresses and load necessary firmware to the phone.

Please take note of the following. This should avoid any confusion when installing IP 1600 series telephones to the network.

The IP 1600 handset, similar to other Avaya IP handsets within the company portfolio can be statically programmed if required to associate static IP address, mask etc.


IP Office 4.2 - IP 1600 Handset Association to CoreIP Office Programming

The IP 1600 telephones are the first IP Office handset that uses HTTP and not TFTP to load operation software.

The IP Office platform acts as a HTTP to TFTP protocol converter.

When associating the IP 1600 range to the IP Office using DHCP, the “Number Of DHCP IP Addresses is greyed out.

This is due to the associated addresses being available from the non-contiguous IP range available to program in the “Advanced” tab



When selecting the “Advanced” tab there are 8 non contiguous pools available to program.

The pool range is associated to the Avaya IP Phones only. When selecting this option, the DHCP server is greyed out as seen on the previous slide.

IP 4600 series, 5600 series and 1600 series telephones are supported using this new 4.2 feature.



The IP 1600 telephones are the first IP Office handset that uses HTTP and not TFTP to load operation software.

The IP Office platform acts as a HTTP to TFTP protocol converter.

The TFTP Server address must be the server running the IP Office Manager or other dedicated TFTP servers where the necessary IP 1600 files are loaded.

The HTTP Server IP Address must be the address of the IP Office as programmed in LAN 1.



The required IP 1600 series handset files loaded with Manager


IP Office 4.2 - IP 1600 Handset Association to Core IP Office SysMon Set Up

Setting the SysMon settings will show the activity of file transfer when plugging in the IP 1600 telephone.


822781mS Interface Tx: v=LAN1 LAN Ethernet Header info - dst=00073b93a17b src=00e007026f78 len=566 IP Header info - Dst=135.64.181.53 Src=135.64.181.227 vl=0x45 tos=0x00 len=552 id=0xe886 ttl=99 flg=0x00 off=0x0000 pcol=6(TCP) sum=0xf3af TCP Header info - DstPort=33692 SrcPort=80(World Wide Web-HTTP) Seq=2015282689 Ack=3370584895 Code=0x18 (PSH ACK ) Offset=80 Window=4369 Sum=0xa054 Urgent=0 0000 74 6f 20 33 32 20 41 53 43 49 49 20 0d 0a 23 23 to 32 ASCII ..## 0010 20 20 20 63 68 61 72 61 63 74 65 72 73 2e 20 20 characters. 0020 46 69 6c 65 6e 61 6d 65 20 6d 75 73 74 20 65 6e Filename must en 0030 64 20 69 6e 20 2e 78 6d 6c 0d 0a 23 23 20 53 45 d in .xml..## SE 0040 54 20 53 59 53 54 45 4d 5f 4c 41 4e 47 55 41 47 T SYSTEM_LANGUAG 0050 45 20 4d 6c 73 5f 53 70 61 72 6b 5f 45 6e 67 6c E Mls_Spark_Engl 0060 69 73 68 2e 78 6d 6c 0d 0a 23 23 0d 0a 23 23 20 ish.xml..##..## 0070 49 6e 73 74 61 6c 6c 65 64 20 4c 61 6e 67 75 61 Installed Langua 0080 67 65 73 0d 0a 23 23 20 20 20 53 70 65 63 69 66 ges..## Specif 0090 69 65 73 20 74 68 65 20 6c 61 6e 67 75 61 67 65 ies the language 00a0 20 66 69 6c 65 73 20 74 6f 20 62 65 20 69 6e 73 files to be ins 00b0 74 61 6c 6c 65 64 2f 64 6f 77 6e 6c 6f 61 64 65 talled/downloade 00c0 64 0d 0a 23 23 20 20 20 74 6f 20 74 68 65 20 70 d..## to the p 00d0 68 6f 6e 65 2e 20 20 46 69 6c 65 6e 61 6d 65 73 hone. Filenames 00e0 20 6d 61 79 20 62 65 20 66 75 6c 6c 20 55 52 4c may be full URL 00f0 2c 20 72 65 6c 61 74 69 76 65 0d 0a 23 23 20 20 , relative..## 0100 20 70 61 74 68 6e 61 6d 65 2c 20 6f 72 20 66 69 pathname, or fi 0110 6c 65 6e 61 6d 65 2e 20 28 30 20 74 6f 20 31 30 lename. (0 to 10 0120 39 36 20 41 53 43 49 49 20 63 68 61 72 61 63 74 96 ASCII charact 0130 65 72 73 2c 20 0d 0a 23 23 20 20 20 69 6e 63 6c ers, ..## incl 0140 75 64 69 6e 67 20 63 6f 6d 6d 61 73 29 2e 20 46 uding commas). F 0150 69 6c 65 6e 61 6d 65 73 20 6d 75 73 74 20 65 6e ilenames must en 0160 64 20 69 6e 20 2e 78 6d 6c 2e 0d 0a 23 23 20 53 d in .xml...## S 0170 45 54 20 4c 41 4e 47 55 41 47 45 53 20 4d 6c 73 ET LANGUAGES Mls 0180 5f 53 70 61 72 6b 5f 47 65 72 6d 61 6e 2e 78 6d _Spark_German.xm 0190 6c 2c 4d 6c 73 5f 53 70 61 72 6b 5f 50 61 72 69 l,Mls_Spark_Pari 01a0 73 69 61 6e 46 72 65 6e 63 68 2e 78 6d 6c 2c 4d sianFrench.xml,M 01b0 6c 73 5f 53 70 61 72 6b 5f 4c 61 74 69 6e 41 6d ls_Spark_LatinAm 01c0 65 72 69 63 61 6e 53 70 61 6e 69 73 68 2e 78 6d ericanSpanish.xm 01d0 6c 0d 0a 23 23 0d 0a 23 23 20 43 61 6c 6c 20 50 l..##..## Call P 01e0 72 6f 67 72 65 73 73 20 54 6f 6e 65 20 43 6f 75 rogress Tone Cou 01f0 6e 74 72 79 ntry

Dst -IP Pool Address associated to IP 1600 telephone Src - IP address of the IP Office “Router” as programmed in “Advanced”

Start Time


When the IP 1600 handset first starts its loading process the file transfers can be observed. The display shows the following during the loading process in order

16xx upgrade

46xx upgrade

46xxsettings.txt

1603b1030vs.bin (Note 1603/1608/1616 depending on phone type)

DO NOT UNPLUG – UPDATING

Telephone RESTARTS

Boot ha1603d071217vs.bin (Note 1603/1608/1616 depending on phone type)

16xx upgrade

46xx upgrade

46xx settings.txt

Save to Flash

Telephone RESTARTS

Boot ha1603d071217vs.bin (Note 1603/1608/1616 depending on phone type

16xx upgrade

46xx settings.txt

Enter Number



879664mS Interface Rx: v=LAN1 LAN Ethernet Header info - dst=00e007026f78 src=00073b93a17b len=324 IP Header info - Dst=135.64.181.227 Src=135.64.181.53 vl=0x45 tos=0x88 len=310 id=0x00a1 ttl=64 flg=0x00 off=0x0000 pcol=17(UDP) sum=0xfef4 UDP Header info - DstPort=1719(H.323Ras) SrcPort=49301 Len=290 Sum=0xf237 0000 03 20 00 01 06 00 08 91 4a 00 02 00 0a 60 86 48 . ......J....`.H 0010 01 86 f8 72 04 02 01 03 85 01 40 00 87 40 b5 35 ...r......@[email protected] 0020 c0 95 02 00 01 01 80 b8 86 12 b1 00 80 b1 01 90 ................ 0030 00 0a 60 86 48 01 86 fc 0b 01 06 02 00 04 00 05 ..`.H........... 0040 37 b8 86 a4 94 35 4c 5b 55 db 1e 02 df df 6d 52 7....5L[U.....mR 0050 ac b3 aa 11 14 bf cb 06 47 3e c4 2e e2 a6 f0 ca ........G>...... 0060 3d 01 b3 6f fe 9e 20 9c 0e 1a cf 23 fa f4 b8 eb =..o.. ....#.... 0070 82 e8 74 fd 42 79 bb 6a f5 56 c8 10 9e 50 61 87 ..t.By.j.V...Pa. 0080 33 5e a3 2c ec 41 51 bd 0b c4 63 ca d2 1c 42 58 3^.,.AQ...c...BX 0090 e5 0d 46 16 01 66 b8 2f fa fe 39 7a 88 68 a4 f5 ..F..f./..9z.h.. 00a0 ef df 8e 7f 49 2f 68 3c 6f c3 a5 f6 a7 bd a7 06 ....I/h<o....... 00b0 2b 01 70 ce cb a4 33 bd b0 37 1f 3e 81 f1 29 00 +.p...3..7.>..). 00c0 00 00 00 06 20 19 02 20 02 00 04 00 00 00 26 20 .... .. ......& 00d0 01 00 0c 03 ba 00 00 79 6f 00 00 7e 05 00 00 0f .......yo..~.... 00e0 02 18 10 0b 0a 60 86 48 01 86 fc 0b 01 06 02 11 .....`.H........ 00f0 02 05 2b 0e 03 02 06 09 60 86 48 01 86 fc 0b 01 ..+.....`.H..... 0100 03 18 10 01 48 09 60 86 48 01 86 fc 0b 01 0a 00 ....H.`.H....... 0110 02 00 00 0a 00 00 0b 00 00 0c .......... 879665mS H323Evt: Recv GRQ from 8740b535 879665mS H323Evt: e_H225_AliasAddress_dialedDigits alias 879665mS H323Evt: found number <8553> 879665mS H323Evt: GRQ --- Auto-create extn for 8553 879666mS PRN: CallSystem::CreateH323Extn No Config for VoIP extn 8553 Adding 879666mS PRN: CallSystem::CreateH323Extn CfgExtn "8553" not found, create a new one

Note the time stamp to associate the user number to the IP 1600 handset

822781ms start time (from previous slide)879666ms end time (associating number)

= 56885ms

= approximately 6 minutes file transfer and loading time




25 February 2008 11:36:01 : Validating configuration...25 February 2008 11:36:01 : Ready

25 February 2008 11:38:00 : Recieved TFTP request for 16xxupgrade.txt.http from 10.39.243.1625 February 2008 11:38:00 : Sent 13% of 16xxupgrade.txt.http25 February 2008 11:38:00 : Sent 26% of 16xxupgrade.txt.http25 February 2008 11:38:00 : Sent 40% of 16xxupgrade.txt.http25 February 2008 11:38:00 : Sent 53% of 16xxupgrade.txt.http25 February 2008 11:38:00 : Sent 67% of 16xxupgrade.txt.http25 February 2008 11:38:00 : Sent 80% of 16xxupgrade.txt.http25 February 2008 11:38:00 : Sent 93% of 16xxupgrade.txt.http

25 February 2008 11:38:00 : Sent 100% of 16xxupgrade.txt.http25 February 2008 11:38:04 : Recieved TFTP request for 46xxsettings.txt.http from 10.39.243.16

25 February 2008 11:38:04 : Sent 5% of 46xxsettings.txt.http25 February 2008 11:38:04 : Sent 10% of 46xxsettings.txt.http25 February 2008 11:38:04 : Sent 15% of 46xxsettings.txt.http25 February 2008 11:38:04 : Sent 20% of 46xxsettings.txt.http25 February 2008 11:38:05 : Sent 25% of 46xxsettings.txt.http25 February 2008 11:38:05 : Sent 30% of 46xxsettings.txt.http25 February 2008 11:38:05 : Sent 35% of 46xxsettings.txt.http25 February 2008 11:38:05 : Sent 40% of 46xxsettings.txt.http25 February 2008 11:38:05 : Sent 45% of 46xxsettings.txt.http25 February 2008 11:38:05 : Sent 50% of 46xxsettings.txt.http25 February 2008 11:38:05 : Sent 55% of 46xxsettings.txt.http25 February 2008 11:38:05 : Sent 60% of 46xxsettings.txt.http25 February 2008 11:38:05 : Sent 65% of 46xxsettings.txt.http25 February 2008 11:38:05 : Sent 70% of 46xxsettings.txt.http25 February 2008 11:38:05 : Sent 75% of 46xxsettings.txt.http25 February 2008 11:38:05 : Sent 80% of 46xxsettings.txt.http25 February 2008 11:38:05 : Sent 85% of 46xxsettings.txt.http25 February 2008 11:38:05 : Sent 90% of 46xxsettings.txt.http25 February 2008 11:38:05 : Sent 95% of 46xxsettings.txt.http

25 February 2008 11:38:05 : Sent 100% of 46xxsettings.txt.http

TFTP Log IP 1600 Firmware Download



25 February 2008 11:38:25 : Recieved TFTP request for hb1616b1030vs.bin.http from 10.39.243.1625 February 2008 11:38:26 : Sent 5% of hb1616b1030vs.bin.http

25 February 2008 11:38:27 : Sent 10% of hb1616b1030vs.bin.http25 February 2008 11:38:28 : Sent 15% of hb1616b1030vs.bin.http25 February 2008 11:38:29 : Sent 20% of hb1616b1030vs.bin.http25 February 2008 11:38:30 : Sent 25% of hb1616b1030vs.bin.http25 February 2008 11:38:31 : Sent 30% of hb1616b1030vs.bin.http25 February 2008 11:38:32 : Sent 35% of hb1616b1030vs.bin.http25 February 2008 11:38:33 : Sent 40% of hb1616b1030vs.bin.http25 February 2008 11:38:34 : Sent 45% of hb1616b1030vs.bin.http25 February 2008 11:38:35 : Sent 50% of hb1616b1030vs.bin.http25 February 2008 11:38:36 : Sent 55% of hb1616b1030vs.bin.http25 February 2008 11:38:37 : Sent 60% of hb1616b1030vs.bin.http25 February 2008 11:38:38 : Sent 65% of hb1616b1030vs.bin.http25 February 2008 11:38:39 : Sent 70% of hb1616b1030vs.bin.http25 February 2008 11:38:40 : Sent 75% of hb1616b1030vs.bin.http25 February 2008 11:38:41 : Sent 80% of hb1616b1030vs.bin.http25 February 2008 11:38:42 : Sent 85% of hb1616b1030vs.bin.http25 February 2008 11:38:43 : Sent 90% of hb1616b1030vs.bin.http25 February 2008 11:38:44 : Sent 95% of hb1616b1030vs.bin.http

25 February 2008 11:38:45 : Sent 100% of hb1616b1030vs.bin.http25 February 2008 11:40:29 : Recieved TFTP request for 16xxupgrade.txt.http from 10.39.243.16

25 February 2008 11:40:29 : Sent 13% of 16xxupgrade.txt.http25 February 2008 11:40:29 : Sent 26% of 16xxupgrade.txt.http25 February 2008 11:40:29 : Sent 40% of 16xxupgrade.txt.http25 February 2008 11:40:29 : Sent 53% of 16xxupgrade.txt.http25 February 2008 11:40:29 : Sent 67% of 16xxupgrade.txt.http25 February 2008 11:40:29 : Sent 80% of 16xxupgrade.txt.http25 February 2008 11:40:29 : Sent 93% of 16xxupgrade.txt.http

25 February 2008 11:40:29 : Sent 100% of 16xxupgrade.txt.http




25 February 2008 11:40:33 : Recieved TFTP request for 46xxsettings.txt.http from 10.39.243.1625 February 2008 11:40:33 : Sent 5% of 46xxsettings.txt.http

25 February 2008 11:40:33 : Sent 10% of 46xxsettings.txt.http25 February 2008 11:40:33 : Sent 15% of 46xxsettings.txt.http25 February 2008 11:40:33 : Sent 20% of 46xxsettings.txt.http25 February 2008 11:40:33 : Sent 25% of 46xxsettings.txt.http25 February 2008 11:40:33 : Sent 30% of 46xxsettings.txt.http25 February 2008 11:40:33 : Sent 35% of 46xxsettings.txt.http25 February 2008 11:40:33 : Sent 40% of 46xxsettings.txt.http25 February 2008 11:40:33 : Sent 45% of 46xxsettings.txt.http25 February 2008 11:40:33 : Sent 50% of 46xxsettings.txt.http25 February 2008 11:40:33 : Sent 55% of 46xxsettings.txt.http25 February 2008 11:40:33 : Sent 60% of 46xxsettings.txt.http25 February 2008 11:40:33 : Sent 65% of 46xxsettings.txt.http25 February 2008 11:40:33 : Sent 70% of 46xxsettings.txt.http25 February 2008 11:40:33 : Sent 75% of 46xxsettings.txt.http25 February 2008 11:40:34 : Sent 80% of 46xxsettings.txt.http25 February 2008 11:40:34 : Sent 85% of 46xxsettings.txt.http25 February 2008 11:40:34 : Sent 90% of 46xxsettings.txt.http25 February 2008 11:40:34 : Sent 95% of 46xxsettings.txt.http





25 February 2008 11:40:53 : Recieved TFTP request for ha1616d071217vs.bin.http from 10.39.243.1625 February 2008 11:40:54 : Sent 5% of ha1616d071217vs.bin.http

25 February 2008 11:40:55 : Sent 10% of ha1616d071217vs.bin.http25 February 2008 11:40:57 : Sent 15% of ha1616d071217vs.bin.http25 February 2008 11:40:58 : Sent 20% of ha1616d071217vs.bin.http25 February 2008 11:40:59 : Sent 25% of ha1616d071217vs.bin.http25 February 2008 11:41:00 : Sent 30% of ha1616d071217vs.bin.http25 February 2008 11:41:01 : Sent 35% of ha1616d071217vs.bin.http25 February 2008 11:41:02 : Sent 40% of ha1616d071217vs.bin.http25 February 2008 11:41:03 : Sent 45% of ha1616d071217vs.bin.http25 February 2008 11:41:04 : Sent 50% of ha1616d071217vs.bin.http25 February 2008 11:41:05 : Sent 55% of ha1616d071217vs.bin.http25 February 2008 11:41:06 : Sent 60% of ha1616d071217vs.bin.http25 February 2008 11:41:07 : Sent 65% of ha1616d071217vs.bin.http25 February 2008 11:41:08 : Sent 70% of ha1616d071217vs.bin.http25 February 2008 11:41:09 : Sent 75% of ha1616d071217vs.bin.http25 February 2008 11:41:10 : Sent 80% of ha1616d071217vs.bin.http25 February 2008 11:41:11 : Sent 85% of ha1616d071217vs.bin.http25 February 2008 11:41:13 : Sent 90% of ha1616d071217vs.bin.http25 February 2008 11:41:14 : Sent 95% of ha1616d071217vs.bin.http

25 February 2008 11:41:15 : Sent 100% of ha1616d071217vs.bin.http25 February 2008 11:43:00 : Recieved TFTP request for 16xxupgrade.txt.http from 10.39.243.16

25 February 2008 11:43:00 : Sent 13% of 16xxupgrade.txt.http25 February 2008 11:43:00 : Sent 26% of 16xxupgrade.txt.http25 February 2008 11:43:00 : Sent 40% of 16xxupgrade.txt.http25 February 2008 11:43:00 : Sent 53% of 16xxupgrade.txt.http25 February 2008 11:43:00 : Sent 67% of 16xxupgrade.txt.http25 February 2008 11:43:00 : Sent 80% of 16xxupgrade.txt.http25 February 2008 11:43:00 : Sent 93% of 16xxupgrade.txt.http

25 February 2008 11:43:00 : Sent 100% of 16xxupgrade.txt.http




25 February 2008 11:43:04 : Recieved TFTP request for 46xxsettings.txt.http from 10.39.243.1625 February 2008 11:43:04 : Sent 5% of 46xxsettings.txt.http

25 February 2008 11:43:04 : Sent 10% of 46xxsettings.txt.http25 February 2008 11:43:04 : Sent 15% of 46xxsettings.txt.http25 February 2008 11:43:04 : Sent 20% of 46xxsettings.txt.http25 February 2008 11:43:05 : Sent 25% of 46xxsettings.txt.http25 February 2008 11:43:05 : Sent 30% of 46xxsettings.txt.http25 February 2008 11:43:05 : Sent 35% of 46xxsettings.txt.http25 February 2008 11:43:05 : Sent 40% of 46xxsettings.txt.http25 February 2008 11:43:05 : Sent 45% of 46xxsettings.txt.http25 February 2008 11:43:05 : Sent 50% of 46xxsettings.txt.http25 February 2008 11:43:05 : Sent 55% of 46xxsettings.txt.http25 February 2008 11:43:05 : Sent 60% of 46xxsettings.txt.http25 February 2008 11:43:05 : Sent 65% of 46xxsettings.txt.http25 February 2008 11:43:05 : Sent 70% of 46xxsettings.txt.http25 February 2008 11:43:05 : Sent 75% of 46xxsettings.txt.http25 February 2008 11:43:05 : Sent 80% of 46xxsettings.txt.http25 February 2008 11:43:05 : Sent 85% of 46xxsettings.txt.http25 February 2008 11:43:05 : Sent 90% of 46xxsettings.txt.http25 February 2008 11:43:05 : Sent 95% of 46xxsettings.txt.http




IP Office Manager allows the conversion of the necessary files required for Avaya IP 1600 telephones to load from an independent TFTP Server. When the files have been converted they will be seen with an extension of HTTPThese files can then be copied to the TFTP server as identified with the IP address associated to the TFTP server within Manager programming. These files do not effect the original files.

Select the HTTP Encode

Select the required file to convert.

When converted the manager shows the successful conversion.

1.

2.

3.

IP Office 4.2 - HTTP Encode


IP Office 4.2 - IP 1600 Handset Association to Core Required Files For TFTP Servers

The files seen in this display will now require copying to the independent TFTP/HTTP Server



The programming of TFTP Server IP Address is that of the network address of the server.

The programming of the IP Office can be seen below to support an independent TFTP server whilst utilising the IP Office switchas the HTTP/TFTP converter

The programming of HTTP Server IP Address is that of the IP Office address



Statically programming the IP 1600 handset

When the display shows “Press * to Program”

Press * Enter the static IP Address of the handset, or leave as 0.0.0.0 to receive DHCP offer. Enter Mask of the network Enter the Router IP address Enter the File Server IP address (This is the IP address of the IP Office) Enter the Call Server IP address (This is the IP address of the IP Office)

NOTE – If the Router IP address is incorrect, the IP 1600 will show “Finding Router . . . “ . When it resets, the Router and Call Server IP address are defaulted to 0.0.0.0

The 1600 telephone will run through the download and upgrade procedure as detailed in the above slides. When the handset has finished loading all the necessary files and updated to flash, it will prompt to request the number. When entered, the DIR and Features should be seen on the 1608 and 1616 handset.


IP Office 4.2 IP 1600 Telephone BackupIP Office 4.2 IP 1600 Telephone Backup


IP Office 4.2

16xx Sets – Procedure to enable network backup and restore


16xx Sets – OverviewThe 1600 Series IP Telephones support the HTTP client to back up and restore the user-specific data

indicated in the next slide. For backup, the telephone creates a file with all the user-specific data if a backup file location is specified in system parameter BRURI in the 46xxsettings.txt file.

The file is sent to the server by an HTTP PUT message, with appropriate success or failure confirmation.

For restore, the file is requested from the server by an HTTP GET message.

Note:A directory path and/or a port number can be included in BRURI as specified in IETF RFCs 2396 and 3986.

HTTP authentication is supported for both backup and restore operations. The authentication credentials are stored in re-programmable, non-volatile memory, which is not overwritten when new telephone software is downloaded. If HTTP authentication fails, the user is prompted to enter new credentials.

More detailed information can be found under chapter 7 in the document :– “Avaya one-X™– Deskphone Value Edition– 1600 Series IP Telephones– Administrator Guide– Release 1.0

This document can be found on the support.avaya.com website under 16xx Telephones


16xx Sets – Script File Changes

################# BACKUP/RESTORE SETTINGS #################### Backup and Restore URI## URI used for HTTP backup and retrieval of user data.## Specify HTTP server and directory path to backup file. ## Do not specify backup file name. ## BRURI is not supported on 96xx or 16cc SIP phones. SET BRURI http://192.168.254.220##

As shown above, in the 46xxsettings.txt text file, remove the ## in front of the entry SET BRURI http://192.168.254.220 and set the IP address of the HTTP server, in our example we are using an MS IIS Server, this is a simplistic guide and may require further configuration and security administration to get working on a customer network.

http://192.168.254.220/


16xx Sets – Create a backup folderA folder must be configured to store the 16xx

backup files.

In our example, we navigate to C:\\Inetpub\wwwroot

Right click and select new folder, rename the folder to a suitable name i.e. “backup”

It may be advisable to allow sharing and allow Read/Write access to Anonymous users using the Sharing a Permissions sections of the folder properties.


16xx Sets – IIS ConfigurationFor this example, we are using an MS IIS Server :-

1. Open the IIS Manager by navigating through Control Panel/Administrative Tools or from the Run command line type “C:\WINDOWS\system32\intetsrv\iis.msc

2. Select the “Default Web Site” from the tree, right click and select properties

3. Enter the IP Address of the PC’s HTTP Server, usually the single IP Address of the PC allocated by the network administrator.

4. For diagnostic purposes, enable logging, under the logging properies select the C:\\Inetpub\wwwroot\backup folder.

5. Go to the next slide


16xx Sets – IIS Configuration1. In Default Web Site Properties, go to the Directory Security Tab.

2. Click the Edit box in the Authentication and access control section.

3. Enable Anonymous Access

4. Enter a valid PC account user name and password – Usually the IUSR_PC NAME account



16xx Sets – IIS Configuration1. Click into Home Directory

2. Click the “A directory located on this computer” button

3. Enter the path of the backup folder

4. Allow Read/Write permissions to the folder



16xx Sets – IIS ConfigurationImportant – it will not work unless you do this :

1. If you have IIS 6.0, go into Web Service Extensions from the main tree and Allow “WebDAV”

2. When finished configuring IIS, select Default Web Site from the main tree and right click mon the icon, select the Stop to stop the service, then right click again and select Start


16xx Backup folderWhen the 16xx set is restarted, or you initiate a

Backup from the set’s “Advanced” menu – you will see a text file – in the example image the file is 202_16xxdata.txt – backed up by the extension number 202.

You can also see a 4620 backup file in the folder, this is also enabled in the 46xxsettings.txt file using the setting :

46xx Automatic Backup/Restore Settings

##

SET RESTORESTAT 1

You can see in the example image a backup file from a 4620 extension number 201 – filename 201_4620data.txt


16xx Sets – Backup Text file contentA 16xx backup text file for extension 202 incorporates the following information – left is a summary as shown in the 16xx Administration Guide :

202_16xxdata.txt

Redial=1

Call Timer=1

Visual Alerting=0

Call Log Active=1

Log Bridged Calls=1

Log Line Calls=1

Log Calls Answered by Others=0

Audio Path=0

Personalized Ring=0

Handset AGC=1

Headset AGC=1

Speaker AGC=1

Error Tone=1

Button Clicks=1

Display Language=English


16xx Sets – Tracing

The only reliable way to trace a HTTP backup is by using a Wireshark or similar application on the IIS Server or via a Hub port – below demonstrates a typical packet incorporating the PUT command and the filename 202_16xxdata.txt


16xx Sets – TracingThe image below demonstrates a typical packet showing the Restore of the backup file 202_16xxdata.txt to the handset with a GET command


IP Office 4.2IP Office 4.2Embedded VoiceMail to Email


OverviewIP Office 4.2 supports the ability to send an e-mail containing notification or the complete voicemail message from the Embedded Voicemail when using IP 406v2 and IP 500 units only. Not Small Office Edition.

Where the option to move or copy messages to e-mail is selected the Embedded Voicemail message is converted to the same WAV format as supported by Voicemail Pro/Lite (16bit Linear PCM, Mono, 8 kHz sample rate).

Settings this feature utilises the existing User Voicemail features announce, copy or move to e-mail, e-mail address.

Visual Voice allows these options to be changed when Embedded VM is configured and the user has an e-mail address configured and the system SMTP settings have been set.

The Embedded TUI is enhanced to add the e-mail options; this will remain compatible with the Voicemail Lite/Pro in IP Office mode. The TUI options are

"To direct all messages to email press *01”

“To send email notifications press *02”,

“To turn off email functions press *03"

The un-voiced *00 option to enable copying voicemail to e-mail has also be added.

The body text of the e-mail message is the same as Voicemail Lite/Pro being available in all the same languages as the prompts.


Core Programming

First step is to enable the Embedded Voicemail option in the System Tab


Core Programming

The next step is to configure the SMTP account settings – typically most SMTP Servers do not require authentication for SMPT, you need to consult with the IT personnel. If an account is required, check the “Server requires authentication” checkbox and configure the username and password.


Core Programming

The User must be configured to have Voicemail On

Voicemail to email address must be configured, usually to the users business email address to receive email alerts. Select the option required for email alerts and whether the User will require a copy of the voicemail message sent as a .wav file – see the Manager help text for an explanation of the options.


Email receipt in Outlook

When a Voicemail is left for a User, an alert will be sent over SMTP to the corresponding email address already configured in that user. It will show the Senders Address, the Calling party (201), Called party and the Time/Date.

If a .wav file has been sent, it will be viewed as an attachment which can be played using a desktop audio player.


SMTP Servers

SMTP must be enabled in the Email Server, in the examples that follow, there are typical configuration settings using the Default SMTP Server on 192.168.254.220

The image to the right is from Exchange 2003 and found in the Exchange manager, find the Default SMTP Server, right click for properties


SMTP Server

Most SMTP Servers are configured to allow Anonymous Access, in other words, you do not need an account to send an email message.

In Manager, System, SMTP, you configure an email sender of your choice, ie [email protected], it would is sensible to use the correct domain name as potentially could cause problems with message delivery if configured to a different domain.

mailto:[email protected]


SMTP Server

The “Relay Restrictions” if not enabled to allow all computers can be a common cause of SMTP email from applications not to work.


Check SMTP is working

You can check if SMTP is configured and working on the email Server by making a simple test.

Open a command line on a PC

Type : C:\telnet 192.168.254.220 25 (you can use the server PC name) <CR> Response : 220 avaya-vuff4byog.brad.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.395 9 ready at Tue, 8 Apr 2008 13:45:57 +0100 –

220 = The Server is ready

avaya-vuff4byog.brad.com = The Server PC name

Microsoft ESMTP MAIL Service, Version: 6.0.3790.395 9 ready at Tue, 8 Apr 2008 13:45:57 +0100 – = SMTP Server type and version, confirming time, date and Daylight saving status.

Type : helo <CR>

Response : 250 avaya-vuff4byog.brad.com Hello [192.168.254.221]

This will show that there is SMTP configured on the server.


SysMon

– Using the SysMon/Call/EmbeddedVoicemail/Email filter, you can track the status of the message sent over email


System Monitor – Using the Interface Filters, you can see the IP packets sent and the email notification embedded, also transmission of the .wav file can be observed. SMTP packets will show a destination port 25.


Wireshark – Packet capture in Wireshark will show all SMTP traffic to and from the IPOffice, check for Port 25 SMTP packets.


Date post:	14-Dec-2015
Category:	Documents
Upload:	peyton-schultz
View:	221 times
Download:	5 times

1 © 2008 Avaya Inc. All rights reserved. Avaya IP Office 4.2 Enhancements New Product Introduction...

Documents