IP Office Platform
  Carroll Communications Home
  Avaya IP Office
  Avaya IP Office 406 r2
  Avaya IP Office 412
  IP Office Telephones
  Voice Mail Pro
  Phone Manager Pro
  IP Office Manager
  IP Office Soft Console
  Avaya Conferencing
  Compact Business Center
  Short Codes
  Data Networking
  IP Office Expansion Modules
  IP Office Licenses
  Centrales Telefonicas
  Voice over IP Phone Systems
  IP Office 403

Avaya Business Phone Systems

Telecommunications Consulting
 
Control Unit
Extension Form Overview
Extension | Extn
Extension | Analog
Extension | VoIP
Extension | IP DECT
User Form Overview
User | User
User | Voicemail
User | DND| Short Codes
User | Source Numbers
User | Telephony
User | Forwarding
User | Dial In
User | Voice Recording
User | Coverage
User | Button Programming
User | Twinning | Menu Programming
User | T3 Options
User | Phone Manager Options
Hunt Group Overview
Hunt Group | Hunt Group
Hunt Group | Voicemail
Hunt Group | Fallback
Hunt Group | Queuing| Voice Recording
Short Code | Short Code
Service Settings Form Overview
Service | Service
Service | Bandwidth
Service | IP
Service | Autoconnect
Service | Quota
Service | PPP
Service | Fallback| Dial In
RAS Form Overview
RAS | PPP
Incoming Call Route Overview
Incoming Call Route | Standard
WAN Port Overview
WAN Port | Frame Relay
WAN Port | DLCIs
WAN Port | Advanced
Directory | Directory Entry
Time Profile Overview
Firewall Profile Form Overview
Firewall | Custom
IP Route Overview
IP Route | IP Route
RIP Dynamic Routing
Least Cost Routing Overview
Least Cost Routing | LCR| Main Route
Least Cost Routing | Alternate Route
Account Code Overview
Account Code | Voice Recording
License | License
Tunnel
Tunnel | Tunnel (L2TP)
Tunnel | L2TP (L2TP)
Tunnel | PPP (L2TP)
Tunnel | Main (IPSec)
Tunnel | IKE Policies (IPSec)
Tunnel | IPSec Policies (IPSec)
Logical LAN
Wireless Overview
Wireless | Security
User Restrictions Overview
User Rights Overview
User Rights | User
User Rights | Short Codes| Telephony
User Rights | Button/Menu Programming
User Rights | Phone Manager
User Rights | Twinning| Membership
Auto Attendant Overview
Auto Attendant | Auto Attendant
Auto Attendant | Actions
Overview of Authorization Code
E911 System Overview
E911 System | E911 System
E911 System | Zones
 
IP Office Manager Pt.1
IP Office Manager Pt.3
about us | phone equipment | t1 lines | partner phone systems | site map | contact us

Avaya IP Office

The Avaya IP Office platform is the ultimate in converged voice and data technology. IP Office brings a combination of voice and data applications formerly reserved for only the largest corporations. Cutting edge customer service with easy to use tools is now available to the smallest of businesses.

   
   

Incoming Call Route | Standard

Incoming call routes are used to match call received with destinations. Routes can be based on the incoming line group, the type of call, incoming digits or the caller's ICLID. If a range of MSN/DID numbers has been issued, this form can be populated using the MSN Configuration tool (see MSN Configuration).

  • Default Blank Call Routes
    By default the configuration contains two incoming calls routes; one set for Any Voice calls (including analog modem) and one for Any Data calls. Whilst the destination of these default routes can be changed it is strongly recommended that they are not deleted.

    • Deleting the default call routes, may cause busy tone to be returned to any incoming external call that does not match another incoming call route.

    • Setting any route to a blank destination field, may cause the incoming number to be matched against system short codes for a match. This may lead to the call being rerouted off-switch.

  • Calls received on S0 trunks and PRI E1 trunks set to QSIG operation do not use incoming call routes. Routing for these is based on incoming number received as if dialed on-switch. Line short codes on those trunks can be used to modify the incoming digits.

  • If there is no matching incoming call route for a call, matching is attempted against system short codes and finally against voicemail nodes before the call is dropped.

 

Settings

Action

Operator Rights View

Mergeable

 

System

Level

Administrator

Manager

Operator

 

SOE

2.1

View

Pre-3.2

3.2

 

IP403

3.0DT

Edit

 

IP406 V1

3.0

New

 

IP406 V2

3.1

Delete

 

IP412

3.2

  • Bearer Capability
    The type of call selected from the list of standard bearer capabilities:
    Any, Any Voice, Any Data, Speech, Audio 3K1, Data 56K, Data 64K, Data V110, Video.

  • Line Group ID: Default = 0, Range = 0 to 99999.
    Matches against the Incoming Line Group to which the trunk receiving the call belongs.

  • Incoming Number
    Matches to the digits presented by the line provider. A blank entry matches all calls that do not match other entries. By default this is a right-to-left match.

    • – : Using a- in front of the number causes a left-to-right match.

    • * : Use a * to match any number for which a more specific match doesn't exist.

      • Combining * in the Incoming Number field and . in the Destination field allow a single incoming call route to direct a range of incoming numbers which match internal destinations.

    • X or x : Use X's to enter a single digit wild card character. For example -91XXXXXXXXXXX will only match when 13 digits, starting with 91, are received. N, n and ? cannot be used.

    • i : The i character does not affect the incoming number matching. It is used for Outgoing Caller ID Matching, see below.

  • Incoming Sub Address: Default = Blank
    Matches any sub address component sent with the incoming call. If this field is left blank, it matches all calls.

  • Incoming CLI
    Enter a number to match the caller's ICLID provided with the call. This field is matched left-to-right. Number options are:

    • Full telephone number.

    • Partial telephone number, for example just the area code.

    • ! : Matches calls where the ICLID was withheld.

    • ? : for number unavailable.

    • Blank for all.

    • To match on just the Incoming Caller ID, use a * in the Incoming Number field and leave the Incoming Sub Address blank.

  • Destination
    Select the destination for the call from the list box. This contains all available extensions, users, groups, RAS services and voicemail. System short codes and dialing numbers can be entered manually. Once the incoming call is matched the call is passed to that destination.

    • Drop-Down List Options
      The following options appear in the drop-down in the following order:

      • Voicemail allows remote mailbox access with Embedded Voicemail, Voicemail Lite and Voicemail Pro. Callers are asked to enter the extension ID of the mailbox required and then the mailbox access code.

      • User Names

      • Hunt Groups Names

      • AA:Name directs calls to an Embedded Voicemail auto-attendant services.

    • Manually Entered Options
      The following options can be entered manually into the field.

      • VM:Name Directs calls to the matching start point in Voicemail Pro.

      • A . matches the Incoming Number field. This can be used even when a * (match all) or X wildcards are being used in the Incoming Number field.

      • A # matches all X wildcards in the Incoming Number field. For example, if the Incoming Number was -91XXXXXXXXXXX, the Destination would be XXXXXXXXXXX.

      • Text and number strings entered here are passed through to system short codes.

  • Locale
    This option specifies the language prompts, if available, that voicemail should use for the call if it is directed to voicemail.

  • Priority: Default = 1, Range = 1 (lowest) to 3 (highest).  
    This setting allows calls to be assigned a priority. In situations where calls are queued, high priority calls are placed before calls of a lower priority. Internal calls are always assigned priority 1. Note that using priority is not recommended for destinations where queue ETA and position messages are being provided by Voicemail Pro.

  • Fallback Extension: Default = Blank
    Defines an alternate destination which should be used when the current destination, set in the Destination or Night Service Destination field, cannot be obtained. For example if the primary destination is a hunt group returning busy and without queuing or voicemail.

  • Night Service Profile: Default = Blank
    A time profile during which the Night Service Destination should be used rather than the Destination.

  • Night Service Destination: Default = Blank
    Set the destination to be used during periods defined by the Night Service Profile. The same range of values can be used as for the Destination field

 

avaya business partner | voice mail | avaya one x quick edition | new jersey phone systems | vm pro | contact us
PO BOX 186 Spring Lake, New Jersey 07762
1-800-429-0077 ::: 732-280-3200
Copyright 2006 CarrollCommunications.com All Rights Reserved.