190 likes | 206 Views
Version 1.7 Features. Business Enabled Communications. Contents. Version 1.7 Features CCR Without DISA CCR Reroute Destination Rerouting From Voice Mail Forwarding Queued Hunt Call Pick-Up ICLID Call Routing Exception Brib Clock Port Selection SIP User ID & Contact
E N D
Version 1.7 Features Business Enabled Communications
Contents • Version 1.7 Features • CCR Without DISA • CCR Reroute Destination • Rerouting From Voice Mail Forwarding • Queued Hunt Call Pick-Up • ICLID Call Routing Exception • Brib Clock Port Selection • SIP User ID & Contact • Authorization Code Table
CCR Without DISA Previously, DISA is enabled by default when CCR is activated. From Version 1.7, DISA can be enabled or disabled for each CCR digit. In CCR table (PGM 260), there’s a new field called “DISA” and you can set it ON/OFF.
CCR Without DISA There can be four cases for CCR without DISA [Example] Case 1) If the caller dials ‘1’, system performs “Digit Analysis” immediately and routes the call if the analysis is successful. Case 2) If the caller dials ‘2’, system plays “Invalid” prompt immediately and performs the retry of CCR service. Case 3) If the caller dials ‘3’, system waits for another digit input. - If the caller doesn’t dial any more digit, the call goes to station 1000. - Otherwise, system performs “Digit Analysis” and call-routing. Case 4) If the caller dials ‘4’, system immediately routes the call to station 1000.
CCR Reroute Destination When CCR feature is used, CO call can be rerouted if the destination doesn’t answer or cannot answer the call. In CCR table (PGM 260), there’s a new field called “System Reroute Table Index”. If “System Reroute Table Index” is programmed (1-100), CCR rerouting is performed based on “System Reroute Table” (PGM 244). Otherwise, CCR rerouting follows “Incoming CO Alternative Destination” (PGM 169).
CCR Reroute Destination System Reroute Table (PGM 244) Error Cases Destinations
Rerouting From Voice Mail Forwarding Calls to a voicemail-forwarded station can be rerouted 1. Call comes in to a station forwarded to voicemail 2. Caller hears the greeting of the called partyand dials ‘0’ to request call rerouting Reroute Destination – Station– Station Group– ACD Group– Attendant– Networking Station The reroute destination can be set as follows 1. From the station : [Tran/PGM] + ‘7’ + ‘7’ 2. In Web Admin : [PGM 147] – Index 1
Queued Hunt Call Pick-Up Calls queued for a station group (Normal, ACD, Attendant) can be picked up Calls in Waiting Queue Station Group ACD Group Attendant Group • A station dials {Direct Call Pick Up} feature code (ex. ‘7’) • And station group, ACD group number or {Attendant Call} feature code is dialed • The oldest queued caller is connected to station.
ICLID Call Routing Exception All the calls with CLI 031 will be routed to station group 620 Caller ID 031 – xxxx - xxxx Group 620 ICLID Table (PGM 262) Alternative CO Ring Table (PGM 181)
ICLID Call Routing Exception How can a fax call with CLI 031 be routed to fax machine? Fax machine sends a fax data Caller ID 031 – xxxx - xxxx Group 620 Station 2000 ICLID Table should allow for Exceptional cases
ICLID Call Routing Exception • Exception table index is programmed in PGM 262 • ICLID exception table contains the dialed digit for exception. ICLID Table (PGM 262) 1 1. ICLID Exception Matched If the caller gives a call to 2000, the call goes to station 2000 (FAX). 2000 2. ICLID Exception Un-Matched If the caller calls a station other than 2000, the call goes to group 620. ICLID Exception Table (PGM 267)
ICLID Call Routing Exception ICLID Procedure • If exception is disabled, ICLID routing. • Otherwise, system waits for dialed digits. ICLID exception Enabled Disabled
ICLID Call Routing Exception DID Procedure ICLID exception Un-Matched Matched • If exception is matched, the call follows DID flow. • Otherwise, system performs ICLID routing.
ISDN BRI Clock Control BRIB Clock Port Selection • iPECS-MG can use the clock from BRIB as main system clock when select the ports on BRIB to use clock. PGM 300 PGM 301 • BRIB should be configured in PGM 301. • NOT USE for All BRIB ports in PGM 300 = No Priority in PGM 301
SIP Account Basic SIP User ID • Many SIP accounts can register by 1 CO Group, but only one SIP account can be used for authentication. • The first account of User ID used for this authentication.
SIP Account Added SIP User ID • Each STA can select SIP account at PGM 131 - F10 SIP User ID Index. This ‘SIP User ID Index’ match index of ‘SIP CO User ID Table’. - STA SIP ID Index: 2, CO Group SIP ID Index: 1 Finding STA SIP ID, has index 2, then use this index for SIP account - STA SIP ID Index: not assign, CO Group SIP ID Index: 1 Finding STA SIP ID, fail and find CO Group SIP ID, has index 1, then use this index for account - STA SIP ID Index: 2, CO Group SIP ID Index: not assign Finding STA SIP ID, has index 2, then use this index for SIP account - STA SIP ID Index: not assign, CO Group SIP ID Index: not assign Finding STA SIP ID, fail and find CO group SIP ID, fail then not use SIP account
SIP Account Added SIP User ID • If want to use many SIP accounts in one STA, add DN to STA and assign SIP account to each DN. • When make call, select DN and make call will support different SIP account in one STA.
SIP Account Edit CONTACT field • If not use ‘Contact’, all is same with previous methods of making CONTACT field. • If have some value(ex.35319022280), this value always used for CONTACT field not considering STA or CO Group selection. • - This ‘Contact’ field used when making all SIP message(REGISTER, INVITE, 200, 180, 183, ACK.. etc). When make call, select DN and make call will support different SIP account in one STA.
Authorization Code Authorization Code • “Authorization Code” means Extension Number + Password. • Authorization codes are required when an extension user changes or recovers the class of service (COS) of the extension, forwards off-net calls, places CO calls or places calls using LCR, and when an off-net user uses the DISA trunk. • - To access the CO line which requires authorization, you need to enter the authorization code. • If an off-net user accesses the internal system through the DISA trunk, he or she must enter the authorization code in order to use the DISA-related system features.