Would like to thank Andy Ertle at Tier4 Industries (aertle@tier4industries.com – (303) 632-0411)
for pointing us in the direction of “Digit Manipulation” for this post.
For some of our other posts we routed calls by Area code. If receiving 10 digits those would work. But, for whatever reason, if you are inserting a “1” or “91” so you can dial from the call log.
If you are having caller ID come in and include the “1” for instance, we can strip that digit off.
There are a couple ways to route calls via caller ID. Using database routing is neat and simpler, but you need Advanced Edition, so this will not work for Server Edition. Using the “Variable Routing” action, makes this possible on Server Edition though. Not as clean as a database, but it is what it is.
Voicemail Pro can use a “Variable Routing” action, to route a call based on a variable. The variable we, obviously would use to route a call by area code, would be $CLI.
How to create a remote access menu, compliments to Kyle L Holladay, Sr. R.I.P.
1. Download and extract the pre-configured module and associated .wav files
2. Copy the .wav files to x:\Program Files\Avaya\IP Office\Voicemail Pro\VM\WAVS\yyy\Custom (where x=the drive where VMP is installed and yyy=your locale, such as enu)
3. Import the module contained in the menuRemote.mod file into your current Voicemail Pro configuration.
4. Click on the Save & Make Live icon in Voicemail Pro to save the current configuration.
Forward to Embedded VM AA after ringing a hunt group
Compliments of Kyle L Holladay, Sr, R.I.P.
In this example we will route inbound calls to a hunt group and then forward to an Embedded Voicemail Auto Attendant if unanswered after 15 seconds or immediately based on a time profile or “night service” button.
1. Create your Embedded Voicemail Auto Attendant.
2. Create a Short Code (such as *90 in the picture below) that is used to access the Auto Attendant.
3. Create a phantom user and assign it an unused extension (such as 1999 in the picture below) that will be used to forward to the Auto Attendant. On the User’s forwarding tab enable forwarding options (see image) and enter the short code you created above as the forwarding number.
The following are the Avaya recommended remote access options.
• Remote Manager: Default RAS connection to the IP Office.
• Dameware: 3rd party application supplied with each IP Office application CD and is a free install. This software needs to be installed on any PC on which the application requiring support is running. For example, if Voicemail Pro is installed on a separate PC from that of Manager, then
Dameware needs to be installed on both PCs for access to both applications.
• PC Anywhere: Third party application that is licensed to the host and client. PC Anywhere is NOT provided by or licensed through Avaya. This software needs to be installed on any PC on which the application requiring support is running. For example, if Voicemail Pro is installed on a separate PC from that of Manager, then PC Anywhere needs to be installed on both PCs for access to both applications. Avaya Technical Support will use PC Anywhere to aid in the troubleshooting of certain issues, but the business partner must provide connectivity to the site
and username and password information.
• Webex: This third party application is a client service and requires customer interaction. This application is NOT provided by or licensed through Avaya. Avaya Technical Support can also use Webex as a remote desktop client for troubleshooting and data collection. With this application, the Avaya Tier 3 engineer assigned to the trouble ticket will provide access information to an Avaya qualified BP engineer. Internet Explorer 6.0 or newer must be available to use Webex.
The Hot-Desking features of the Avaya IP office 500 system allow you to log on at any phone and that phone will then take on the features of your original phone including your extension number, any call forwarding options or pickup group settings. This can be especially useful if you sometimes work at a different location or in fact don’t have one fixed workspace. In order for you to be able to use this feature and log in to a phone you need to get your system administrator to assign you a login code. The very cool thing with IP office Hot-Desking, it doe NOT matter what the origination or destination set is going to be… Meaning, you can have an IP phone normally, but hot desk to an analog conference phone, or a 2 button digital phone.
Create a checkHours Module for all US Federal Holidays Kyle L Holladay, Sr, R.I.P. This is just a subset of the AWESOME SBC (Standard Base Config) that Kyle created for IPO/Voicemail Pro, Downloaded here..
This document will provide instruction on how to create a checkHours module that can be dropped into your Voicemail Pro call flows that will allow all US Federal Holidays as defined by 5 U.S.C 6103 plus an additional 3 custom holiday conditions. Additionally this module will allow for 4 separate office hours to accomodate multiple offices or varying hours in different departments. Here is an example of how this new checkHours module can be used to route between a day and night auto attendant. The holiday greeting is played prior to the AA greeting and should be recorded similar to “Please note our offices will be closed on Thursday and Friday in recognition of the Thanks Giving Holiday” which would be followed typically by the night menu of something similar to “Thank you for calling Acme Toy Company, you’ve reached us outside of our normal business hours…” 
IP Office AT-DEBUG Commands
Compiled by Kyle L Holladay, Sr. R.I.P.
| Command | Parameter | Definition |
| upgrade | – | Erase Code and Reboot/reload |
| reboot | – | Reboot |
| erasenvconfig | – | Erase NV config |
| eraseconfig | – | Erase config |
| qbf | – | Send Fox messages to WAN and MGR |
| call | (service) | Call the specified service |
| fecpram | – | List FCC parameter data |
| fecstats | – | List FCC traffic statistics |
| fecrmon | – | Enable/disable FCC RMON counters |
| fectrace | – | Enable/disable FCC debug tracing (needs debug build) |
| fecrestart | – | Restart FCC transmitter |
| pcmcia | – | Show current PCMCIA status |
| crc6 | – | Display CRC-6 error count |
| ti | – | Send cmd to Ti/Telogy stack |
| atmcms | – | Dump status of CM ATM lines |
| atmcfg | (lineid) | Change configuration of an ATM trunk |
| atmdump | (lineid) | Dumps configuration of an ATM trunk |
| atmdiag | (on|off) | Turn on/off the ATM diagnostic logging |
| echo | (on|off) | Turn on/off the ATM Echo cancellation if enabled in configuration |
| atm4trunks | – | Dump status of ATM4U trunks |
| atm4lin | (a|b|c|d) | Show/change status of ATM4U lines |
| dspatver | (a|b|c|d) | Report version number of ATM4U card in Slot A/B |
| dspatmem | (a|b|c|d) | Read/Write to ATM4U card in Slot A/Bs DSP memory |
| dspathpi | (a|b|c|d) | Thrash or stop HPI accesses (to DSP) for ATM4U card in Slot A-D |
| atm4usc | (a|b|c|d) | Send Vinetic Short Command to ATM4U card in Slot A-D |
| atm4urmb | (a|b|c|d) | Read Vinetic Mailbox command from ATM4U card in Slot A-D |
| atm4uwmb | (a|b|c|d) | Write Vinetic Mailbox command to ATM4U card in Slot A-D |
| atm4ucram | (a|b|c|d) | Write Vinetic CRAM Data to ATM4U card in Slot A-D |
| atm4ulow | (a|b|c|d) | Set ATM4 Vinetic processor in low power mode in Slot A-D |
| atm4uhigh | (a|b|c|d) | Set ATM4 Vinetic processor in high power mode in Slot A-D |
| use_diag_cmd | – | use diag commands |
| conferdsp | – | Read current status of Conferencing DSP |
| conferdspmem | – | Read/Write to Conferencing DSP memory |
| conferdspch | – | Compare DSP Image words against what is stored in DSP memory |
| dspt1a/b | – | Read/Write to T1 card in Slot A/B’s DSP memory |
| switchdump | – | Dump all the registers on the Ethernet Switch |
| switchport | – | configure one of the PHY ports on the switch |
| switchread | – | Read a register on the Ethernet Switch |
| switchwrite | – | Write a register on the Ethernet Switch |
| vcmread | – | Read an SPI register on VCM ethernet switch |
| vcmwrite | – | Write an SPI register on VCM ethernet switch |
| vcmport | – | configure one of the PHY ports on the VCM switch |
| phydump | – | Dump all the registers from the PHY connected to the LAN2/WAN port |
| phyread | – | Read register from PHY |
| phywrite | – | Write register on PHY |
| lanstatus | – | Display the connection status of the external LAN/WAN links |
| gnd | status reset quiesce rx rxt flush cmd token features speed | Perform G&D SmartCard commands (e.g. “gnd speed”) |
| bri | regs dsp isac lock | Perform BRI commands (e.g. “bri dsp”) |
| priu | dspver dspqueues dsptrace dspload dspmem dspmsgwr dspmsgrd dspstatus alarmsim egram | Display DSP version information Display DSP message queue information Enable/Disable DSP debug trace Load and run DSP image DSP memory edit DSP message queue test write DSP message queue test read Print DSP statistics Run alarm simulations Receiver equalizer RAM modifications |
| DVP | RDCMD RDDATA PAGE PREAD PWRITE DREAD DWRITE REVCODE MEMTEST QSAPP INIT CLOSE DOPTS POPTS DDATA PDATA CODEC RING DIAL MWAIT STATUS [C] TEST GAIN POWERETR LLC REGS PROF DPL | read a command/control register read a data register select a memory page perform a paged read perform a paged write perform a direct read perform a direct write read the revision code perform a memory test run the Legerity QuickStart application initialise the subsystem close down the subsystem display device options display port options display device data display port data set the codec law for a port cause a line to ring dial a number use the message waiting indicator display status runs a test on a port set line gains apply power to an ETR phone execute a low-level command dumps registers for a port display a profile set the DTE print level |
| ipstats | – | Dump IP/ICMP/TCP/UDP stats |
| ivm-help | – | Embedded Voicemail Commands |
| ivm-mbox-show | – | Show mailboxes |
| ivm-mbox-show | Show contents of specified mailbox | |
| ivm-mbox-clear | Clear specified mailbox | |
| ivm-msg-del | nnn dd/dd/dd hh:mm:ss | Delete specified message |
| ivm-msg-del-all | – | Delete all voicemail messages |
| ivm-flash-del-all | – | – |
| ivm-limits-max-nummsg-show | – | – |
| ivm-limits-max-nummsg-set | xxx | – |
| ivm-limits-max-mstime-show | – | – |
| ivm-limits-max-mstime-set | xxx | – |
| ivm-status-show | – | – |
| ivm-monitor-toggle | – | – |
SIP Trunking between Avaya IP Office R5 and Flowroute by
Kyle L Holladay, Sr R.I.P
In this example we will configure a SIP trunk between the Avaya IP Office and Flowroute using registration on LAN1 behind a firewall/NAT. Alternative configurations would include a static public IP or static IP behind a NAT/Firewall which will not be covered in this document.
NOTE: Flowroute claims T.38 version 0 support as of May 2009 however I have not been able to successfully negotiate any T.38 traffic at this point using version 0 at 9600bps and IP Office EI version 5.0 due to a requirement by Flowroute of information in the INVITE that the IP Office does not currently support. Thus far Flowroute’s technical support has been responsive and helpful. The call quality has been fantastic, far beyond what I have come to expect from other ITSP (over the Internet SIP providers).
SIP Trunking between Avaya IP Office R9 and Flowroute by
Kyle L Holladay, Sr R.I.P
In this example we will configure a SIP trunk between the Avaya IP Office and Flowroute using registration on LAN1 behind a firewall/NAT. Alternative configurations would include a static public IP or static IP behind a NAT/Firewall which will not be covered in this document.
NOTE: Flowroute claims T.38 version 0 support as of May 2009 however I have not been able to successfully negotiate any T.38 at this point, using version 0 at 9600bps and IP Office EI version 5.0 due to a requirement by Flowroute of information in the INVITE that the IP Office does not currently support. Thus far Flowroute’s technical support has been responsive and helpful. The call quality has been fantastic, far beyond what I have come to expect from other ITSP (over the Internet SIP providers).