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 Telephone 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 Overview

Incoming call routes are used to determine the destination of voice and data calls received by the IP Office. Determining which incoming call route is used is based on the call matching number of criteria. In order of priority, these are:

 The bearer capability indicated, if any, with the call. For example voice, data, video.

  • The incoming line group ID of the trunk or trunk channel on which the call was received.

  • The incoming number received with the call.

  • The incoming sub address received with the call.

  • The incoming caller ID of the call.  

 

Each incoming route can include a fallback destination for when the primary destination is busy. It can also include a time profile which control when the primary destination is used. Outside the time profile calls are redirected to a night service destination.

On IP Office systems where a large number incoming call routes need to be setup for DID numbers, the MSN/DID Configuration tool can be used. Select Tools | MSN Configuration.  

 

 

Incoming Call Routing Examples

Example: Simple DID Routing
In this example, the customer has subscribed to receive three-digit DID in the range 200 to 299 which matches the range of their extension numbers.

Line Group

Incoming Number

Destination

0

*

.

0

blank

Main

The entry * matches any incoming number. The destination . takes the incoming number and uses it as the destination. This allows a single incoming route to be used for a range of numbers.

 

Example: Area Code Matching
Suppose the customer want to attempt to route all calls where the ICLID is in the same area code, for this example 732 .

Line Group

Incoming Number

Incoming Caller ID

Destination

0

*

732

LocalSales

0

blank

blank

Main

The 732 reads any ICLID received from left-to-right for a leading match on 732, the required area code. Those calls are routed to a group called LocalSales while all other calls are route to the group Main.

 

Example: Incoming Numbers
For this example, the customer has subscribes to receive two 2-digit DID numbers. They want calls on one routed to a Sales hunt group and calls on the other to a Services hunt group. Other calls should use the normal default route to hunt group Main.

The following incoming call routes were added to the configuration to achieve this:

Line Group

Incoming Number

Destination

0

77

Sales

0

88

Services

0

blank

Main

Note that the incoming numbers could have been entered as the full dialed number, for example 7325551177 and 7325551188 respectively. The result would still remain the same as incoming number matching is by default performed on the right hand digits.  

Right-hand matching gets complicated when the number of incoming digits is greater than the number of digits specified in the Incoming Number field. Consider the example below for when the incoming number digits 77 are received. The entries 677 and 77 have the same number of matching digit places and no non-matching places. However the 77 entry is the shorter match and so is used by the IP Office.

Line Group

Incoming Number

Destination

0

677

Support

0

77

Sales

0

7

Services

0

blank

Main

In the following example the 677 entry is used as the match for 77 as it has more matching digits than the 7 entry and no non-matching digits.

Line Group

Incoming Number

Destination

0

677

Support

0

7

Services

0

blank

Main

If this case the digits 777 are received. The 677 entry had a non-matching digit, so it isn't a match. The entry 7 is used as it has one matching digit and no non-matching digits.  

Line Group

Incoming Number

Destination

0

677

Support

0

7

Services

0

blank

Main

 

Outgoing Caller ID Matching

In cases where a particular Incoming Number is routed to a specific user, the IP Office will attempt to use that Incoming Number as the user's caller ID when they make outgoing calls. This requires that the Incoming Number is a full number suitable for user as outgoing caller ID and acceptable to the line provider.

When the case above is applicable, the character i can also be added to the Incoming Number field. This character does not affect the incoming call routing. However when the same Incoming Number is used for an outgoing caller ID, the calling party number plan is set to ISDN and the type is set to National. This option may be required by some network providers.

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.