Using Your APmax with the C15 - Innovative Systems - Using Your APmax with... · 2012-08-08 · 1. Introduction 1 June 2012 Innovative Systems, L.L.C. Proprietary 715000.01 Using

715000.01

APmax TM

User ManualUsing Your APmax with the C15

Issue 01 June 2012 Proprietary

June 2012 Proprietary 715000.01 Using Your APmax with the C15 User Manual

APmax TM

Using Your APmax with the C15User Manual

Publication number: 715000Document Version: 01Issue date: June 2012Security status: ProprietaryOwner: B. Aughenbaugh

© 2012 Innovative Systems, L.L.C. All rights reserved.

Information subject to change without notice.

The information disclosed herein is proprietary to Innovative Systems, L.L.C. or others and is not to be used by or disclosed to unauthorized persons without the written consent of Innovative Systems, L.L.C.. The recipient of this document shall respect the security status of the information.

715000.01 Proprietary June 2012Using Your APmax with the C15 User Manual

iv

Publication history

Date Version DCR Author ============ ====== ====== =======May 30, 2008 1

March 22, 2009 2

May 19, 2009 3 1764

June 14, 2012 4 1929 B. Aughenbaugh

1. Introduction 1

1. Introduction

1.1 General DescriptionThis document is intended to help ease configuration of the C15 to work with the APmax™ . This document is not intended as a complete guide to translations or switch provisioning. Switch provisioning should only be performed by properly qualified personnel and this guide is written with them in mind.

1.2 ApplicabilityAll examples used in this guide are for illustration purposes only. Each switch may be config-ured differently and certain aspects of the example may need to be altered for a specific switch.

1.3 SupportIf after following the suggested guidelines, you still have problems configuring your C15 to work with the APmax TM, please contact Genband Technical Support or Innovative Systems for assistance.

June 2012 Innovative Systems, L.L.C. Proprietary 715000.01 Using Your APmax with the C15 User Manual

2 1. Introduction

715000.01 Innovative Systems, L.L.C. Proprietary June 2012 Using Your APmax with the C15 User Manual

2. APmax Introduction and Installation 3

2. APmax Introduction and Installation

2.1 General InformationThe APmax TM is suitable for installation in network telecommunication facilities and in locations where the NEC applies. It is intended to provide many features. Each APmax TM unit provides:

• T1 communication channels

• SS7 interfaces

• Serial ports - RS232/RS449/V.35 capable

• Ethernet ports - for connection to the LAN, WAN, VoIP, and for inter-unit communication

The T1 trunks can be used to provide Announcements such as CLASS announcements. They also allow MF detection, DTMF detection, and voice feedback for some features. The T1 trunks are also used as an SS7 interface providing SS7 over T1. The APmax TM also supports ISUP signalling over the SS7 network, which is used to implement call-based services. Call-based services use T1 trunks to play announcements and carry telephone conversations. The SS7 interface can also be used for controlling the message waiting indicator (MWI) function.

The Ethernet channels are used for inter-unit communication in a system, and allow placing the APmax TM on a local area network (LAN). The LAN connection can be used for maintenance and control and OPM reporting. The VoIP connection supports Session Initiation Protocol (SIP) for call setup and Real-time Transport Protocol (RTP) for audio data.

2.1.1 Parts ListEach APmax TM kit is shipped with:

• 2-APmax TM units

• 2-Ethernet cables (for inter-unit communication)

• 1-Ethernet cable (for non-VoIP configuration)

• 2-sets mounting brackets (for mounting in a 19” rack) with screws

• APmax TM User Interface Software (on CD-ROM)

• APmax TM Operating Software (pre-loaded)

• APmax TM User Manual (Softcopy PDF provided on APmax TM User Interface CD-ROM)

Required items not supplied with the kit:


4 2. APmax Introduction and Installation

• 2-T1 cable assemblies

• CAT5 or similar cable to connect the APmax TM System to the computer network

• Fuse - 3A is recommended

Optional items not supplied with the kit:

• APmax TM Spare

• APmax TM User Manual, Printed

Depending on the type of APmax TM system configuration specified or the particular application(s) purchased with the system, other parts may be included and other software may be pre-loaded, in addition to what is specified here.

2.1.2 SpecificationsThe specifications listed in Table 2-1 - Specifications are per APmax TM unit.



Table 2-1

Description Specification

Physical Size (width x depth x height) 1.75”H x 17”W x 14.25”D

Weight 10.5 lbs

Physical Location Install in the Central Office (CO).

Mounting Brackets available for mounting in 19”, 23”, and 26” racks. 1 U space above and below the APmax TM system is strongly recommended.

Environmental

Operating Temperature Range

Relative Humidity

65 to 110 oF (18 to 43oC)

10-90%, non-condensing

Power Requirement

Voltage

Current

Recommended External Fuse

-42 to -56 VDC

2.0A

3.0A

Front Panel LEDs/Indicators

Power

Minor (alarm)

Major (alarm)

Critical (alarm)

Green

Amber

Amber

Red

Connections

Power and Alarm

Serial Ports

Ethernet

T1

8 Position Terminal Block

Two 25-Pin Female D-sub Connectors. (RS232/RS449/V.35 capable)

Six RJ-45 Connectors

One 37-Pin Female Connector Providing Eight DS-1’s, Two BNC Connectors (one Tx and one Rx Providing One DS-3)

Specifications

Note: For power and alarms connections, 18 AWG wire which meets UL 60950-1 requirements should be used (Belden 8899 or equivalent). For wire



terminations, ring or spade terminals such as AMP 34144 of AMP 320665 should be used.

WARNING: The intra-building port(s) of the equipment or subassembly is suitable for con-nection to intrabuilding or unexposed wiring or cabling only. The intra-building port(s) of the equipment or subassembly MUST NOT be metallically connected to interfaces that connect to the OSP or its wiring. These interfaces are designed for use as intra-building interfaces only (Type 2 or Type 4 ports as described in GR-1089-CORE, Issue 4) and require isolation from the exposed OSP cabling. The addition of Primary Protectors is not sufficient protection in order to connect these interfaces metallically to OSP wiring.

2.1.3 Rear and Front ViewsThe rear and front views of an APmax TM unit are shown in - .

Figure 2-1 Rear and Front Views

2.1.4 RedundancyAn APmax system consists of a pair of units in order to provide the redundancy necessary for telecommunications applications.

Each system contains a site-specific database. For true redundancy, the databases in each of the system’s two units are identical under normal operation conditions. If either unit should be unable to perform its function, either because of unit failure, a power failure, an SS7 link failure, or a T1 failure, the other unit will maintain service. In many cases, if one unit is removed and replaced, it will obtain the correct database from the mate unit when power is reapplied.

2.1.5 System RequirementsEach unit must be supplied with -48 VDC power. The two sets of power input connections should be tied to independent sources in order to provide redundant powering.



Each unit may be configured for SS7 communication over a T1 channel.

A personal computer running the APmax TM User Interface Software is required for configuration, administration, and maintenance of the APmax TM system.

2.1.6 Network ConfigurationEach APmax TM system ships with a set of default Administration and Call Processing IPs. The Digital Signal Processors (DSPs) reside on the Call Processing network and their IPs are also defaulted before shipment. Record the IPs used by the system on the APmax TM Configuration Sheet provided at the end of this chapter. The default IPs are as follows:

Table 2-2 Administration (OAMP) IPs

Unit 1 Unit 2

Administration 172.16.1.45 172.16.1.46

Subnet 255.255.255.0 255.255.255.0

Gateway 172.16.1.1 172.16.1.1

Table 2-3 Call Processing (VoIP) IPs

Unit 1 Unit 2

Calling Processing 172.16.4.61 172.16.4.62

Subnet 255.255.255.0 255.255.255.0

Gateway 172.16.4.1 172.16.4.1

DSP 0 172.16.4.64 172.16.4.68

DSP 1 172.16.4.65 172.16.4.69

DSP 2 172.16.4.66 172.16.4.70

DSP 3 172.16.4.67 172.16.4.71

It is required that the OAM&P (Administration) and VoIP (Call Processing) networks be located on separate physical networks. By keeping the VoIP network private quality of service is assured.



Improper configuration of the network, cabling, and IP assignment could result in loss of call processing, inability to administer the system, and subsequent loss of service.

2.1.7 Ethernet CablingThe OAM&P (Administration) network connects to the APmax TM via the OAM&P port, port 1, on the APmax TM Ethernet switch.

The tielines are used to maintain redundant databases between the units. There are two tielines, and they connect from port 5 to port 5 and port 6 to port 6.

If APmax web services such as Phone Central are to be used, the system’s Internet IPs must be configured accordingly and the WAN port, port 2, on each unit must be connected to the Internet.

The VoIP network connects to the APmax TM via the VoIP port, port 4. Whether or not the APmax TM will be used for VoIP will determine how the system should be cabled.

In addition to properly cabling the system, the Administration, Call Processing IPs, and DSP IPs must be configured accordingly. If the networks on which the APmax TM resides do not support the default IP ranges preconfigured before shipment, then the system IPs will need to be updated (see the APmax TM User Manual Chapter 4 - “Ethernet Configuration for more information.)

Note: Setting the IPs on the APmax is done by sending a broadcast query from the UI to all units within the system. When changing the APmax IPs, the PC on which the UI runs must be on the same network as the APmax TM Administration network.

2.1.7.1 Non-VoIPIf VoIP is not utilized, meaning the APmax will not be hosting external VoIP traffic, the VoIP port, port 4, on each unit must be connected to the mate unit’s VoIP port, port 4. An Ethernet cable has been provided specifically for this purpose.

This connection between units is required for administration of the system and to support multi-unit conferencing. The APmax conferencing feature utilizes VoIP, from unit to unit, to conference all parties together regardless of which unit the conference call came in on.

2.1.7.2 VoIPIf VoIP is utilized, the VoIP port, port 4, on each unit must be connected to the Call Processing network on which the APmax TM resides.



It is required that the OAM&P (Administration) and VoIP (Call Processing) networks be located on separate physical networks.

2.2 Installation Procedure2.2.1 Hardware Installation

The following details the installation and cabling of the APmax TM. It is assumed that APmax TM UI has already been installed on the OAMP PC. See the chapters entitled Installing the APmax TM UI and Getting Started in the APmax TM User Manual for further information.

2.2.1.1Record the System ID on the APmax TM Configuration Sheet provided at the end of this chapter. The System ID will be on a label on the front of the APmax TM units. Be sure to install Unit 1 and Unit 2. If a spare was purchased with the system, do not install the spare at this time.

2.2.1.2Mount the APmax TM into the desired equipment rack using four # 10 panel bolts per unit. The APmax TM should be mounted in a location such that cables and wiring reach the proper connections.

2.2.1.3Connect one end of the chassis grounding wire to a ground bus. Connect the other end to a two hole connector and then bolt one ground connection to each unit, see Figure 2-2 - Ground Connection below.

Figure 2-2 Ground Connection



2.2.1.4Connect the -48 VDC and RTN to the APmax TM using the appropriate terminals, -

Note: Do not insert the fuse until installation is complete

Figure 2-3 Terminal Connector

2.2.1.5Connect the alarm wires to the terminal strips, - .

2.2.1.6Connect the APmax TM to the OAM&P network by connecting a LAN cable to Port 1 of each unit, - .

Note: If the networks on which the APmax TM resides do not support the default IP ranges preconfigured before shipment, then the system IPs will need to be updated (see the APmax TM User Manual Chapter 4 - “Ethernet Configuration” for more information.)

Figure 2-4 Ethernet Switch



2.2.1.7Connect the tielines from unit 1 to unit 2 using the Ethernet cables provided in the kit. Connect Port 5 of unit 1 to Port 5 of unit 2. Connect Port 6 of unit 1 to Port 6 of unit 2.

2.2.1.8If VoIP will not be used, connect the additional Ethernet cable provided in the kit from Port 4 of unit 1 to Port 4 of unit 2. If VoIP will be used then connect Port 4 on each unit to the VoIP network.

Note: The VoIP network must be physically separate from the OAM&P network.

2.2.1.9Connect one T1 cable to the 37 pin connector on unit 1, Figure 2-5 - DS1 Connector. Reference Table 2-4 - T1 Cable Revision A - Pin Out Table when wiring to the APmax TM. Repeat, connecting another T1 cable to unit 2. Connecting one T1 cable to each unit and configuring them appropriately will ensure redundancy.

Figure 2-5 DS1 Connector



Table 2-4 T1 Cable Revision A - Pin Out Table

DS1 PIN WIRE COLOR SIGNAL NAME

DSI-1 37 ORG/WHT RECEIVE - RING

DS1-1 36 BLU/WHT TRANSMIT - RING

DS1-1 18 WHT/ORG RECEIVE - TIP

DS1-1 17 WHT/BLU TRANSMIT - TIP

DS1-2 34 BRN/WHT RECEIVE - RING

DS1-2 35 GRN/WHT TRANSMIT - RING

DS1-2 15 WHT/BRN RECEIVE -TIP

DS1-2 16 WHT/GRN TRANSMIT - TIP

DS1-3 14 BLU/RED RECEIVE - RING

DS1-3 13 SLT/WHT TRANSMIT - RING

DS1-3 32 RED/BLU RECEIVE - TIP

DS1-3 31 WHT/SLT TRANSMIT - TIP

DS1-4 29 GRN/RED RECEIVE - TIP

DS1-4 30 ORG/RED TRANSMIT - TIP

DS1-4 11 RED/GRN RECEIVE - RING

DS1-4 12 RED/ORG TRANSMIT - RING

DS1-5 28 SLT/RED RECEIVE - RING

DS1-5 27 BRN/RED TRANSMIT - RING

DS1-5 9 RED/SLT RECEIVE - TIP

DS1-5 8 RED/BRN TRANSMIT - TIP

DS1-6 6 ORG/BLK RECEIVE - TIP

DS1-6 7 BLU/BLK TRANSMIT - TIP

DS1-6 25 BLK/ORG RECEIVE - RING

DS1-6 26 BLK/BLU TRANSMIT - RING

DS1-7 5 BRN/BLK RECEIVE - RING

DS1-7 4 GRN/BLK TRANSMIT - RING

DS1-7 23 BLK/BRN RECEIVE - TIP



DS1-7 22 BLK/GRN TRANSMIT - TIP

DS1-8 2 BLU/YEL RECEIVE - RING

DS1-8 3 SLT/BLK TRANSMIT - RING

DS1-8 20 YEL/BLU RECEIVE - TIP

DS1-8 21 BLK/SLT TRANSMIT - TIP

- 1 DRAIN CHASSIS - GROUND

- 10 JUMPER CHASSIS - GROUND






Table 2-5 T1 Cable Revision A0 - Pin Out Table

Table 1:

DS1 Cable PIN WIRE COLOR SIGNAL NAME

DSI-1 1 37 BLU/WHT RECEIVE - RING

DS1-1 2 36 BLU/WHT TRANSMIT - RING

DS1-1 1 18 WHT/BLU RECEIVE - TIP

DS1-1 2 17 WHT/BLU TRANSMIT - TIP

DS1-2 1 34 ORG/WHT RECEIVE - RING

DS1-2 2 35 ORG/WHT TRANSMIT - RING

DS1-2 1 15 WHT/ORG RECEIVE -TIP

DS1-2 2 16 WHT/ORG TRANSMIT - TIP

DS1-3 1 14 WHT/GRN RECEIVE - RING

DS1-3 2 13 WHT/GRN TRANSMIT - RING

DS1-3 1 32 GRN/WHT RECEIVE - TIP

DS1-3 2 31 GRN/WHT TRANSMIT - TIP

DS1-4 1 29 BRN/WHT RECEIVE - TIP

DS1-4 2 30 BRN/WHT TRANSMIT - TIP

DS1-4 1 11 WHT/BRN RECEIVE - RING

DS1-4 2 12 WHT/BRN TRANSMIT - RING

DS1-5 1 28 SLT/WHT RECEIVE - RING

DS1-5 2 27 SLT/WHT TRANSMIT - RING

DS1-5 1 9 WHT/SLT RECEIVE - TIP

DS1-5 2 8 WHT/SLT TRANSMIT - TIP

DS1-6 1 6 RED/BLU RECEIVE - TIP

DS1-6 2 7 RED/BLU TRANSMIT - TIP

DS1-6 1 25 BLU/RED RECEIVE - RING

DS1-6 2 26 BLU/RED TRANSMIT - RING

DS1-7 1 5 RED/ORG RECEIVE - RING

DS1-7 2 4 RED/ORG TRANSMIT - RING

DS1-7 1 23 ORG/RED RECEIVE - TIP



2.2.2 Provisioning the APmax TM

The following details the basic provisioning necessary to add the APmax TM to the UI, configure the IPs, set the time, and configure the DS1s and SS7 links if necessary.

2.2.2.1 Install the UIIn the APmax TM User Manual, go to Chapter 2 - “Installing the APmax TM UI” and follow the steps to install the software on the PC if this has not already been done.

2.2.2.2 Add the APmax TM

2.2.2.2.1In the APmax TM User Manual, go to Chapter 3 - “Getting Started” and follow the instructions to log into the UI, create a login account, and add the APmax TM to the UI. The System ID recorded on the APmax TM Configuration Sheet will be needed. The System ID will be on a label on the front of the APmax TM units.

2.2.2.2.2Once the system has been added to the Command Center proceed to the next step.

2.2.2.3 Setting the TimeSet the time in the APmax TM using the APmax TM UI. The time must be set for the system to complete boot up. Once the time is set allow 5 minutes for boot up.

DS1-7 2 22 ORG/RED TRANSMIT - TIP

DS1-8 1 2 RED/GRN RECEIVE - RING

DS1-8 2 3 RED/GRN TRANSMIT - RING

DS1-8 1 20 GRN/RED RECEIVE - TIP

DS1-8 2 21 GRN/RED TRANSMIT - TIP

- 1 1 DRAIN CHASSIS - GROUND

- - 10 JUMPER CHASSIS - GROUND

- 2 19 DRAIN CHASSIS - GROUND



Table 1:



From the APmax TM UI, right-click on the system’s icon in the Command Center window to invoke a popup menu, and select the System Configuration | System Time Manager command. For more information on the System Time Manager window, refer to Chapter 5 - “System Time Manager” in the APmax User Manual.

2.2.2.3.1Select the System Time tab. Under Select System Time Zone set the Time Zone. Click Set AP Time. Verify the Local Time displayed under Current Time is correct.

2.2.2.3.2Select the NTP Configuration tab and set the NTP Servers. If the APmax TM is connected to the Internet, use an external NTP Server such as time.nist.gov or pools.ntp.org.

2.2.2.3.3If an internal NTP Server is available, meaning an NTP Server is available on the OAM&P network on which the APmax TM resides, add it in addition to the external servers.

2.2.2.3.4If the APmax TM is not connected to the Internet use an internal NTP server, if available.

2.2.2.3.5If no NTP Servers are available or if an NTP Server will not be used, set the NTP Server to DISABLED. Setting the NTP Servers to DISABLED allows a system to not use NTP and not report a Time Alarm.

2.2.2.3.6Click Set NTP Servers to save changes.

2.2.2.3.7If NTP will not be used to ensure the system time is correct and there are no T1 circuits connected to the system to provide clock synchronization, then the time should be manually set weekly to ensure the system is keeping accurate time. Select the System Time tab and click Set AP Time.

2.2.2.3.8Record the NTP Settings on the APmax TM Configuration Sheet at the end of this chapter. Close the window.

2.2.2.4 Ethernet ConfigurationIf the system IPs need to be changed from the system defaults see the APmax TM User Manual Chapter 4 - “Ethernet Configuration” and follow the



instructions to configure the ethernet interfaces on the APmax TM. Please note, any changes to the system IPs must be done from a PC on the OAMP network on which the APmax TM resides.

2.2.2.4.1Enter the Domain Search. Domain Search is a space-separated list of domains to use during DNS lookups when no domain is specified.

2.2.2.4.2Enter the DNS Address(es). This is the IP address of the Name Server (DNS) that should be used by this system. There are two Name Server (DNS) Address fields. The second field is optional and will be queried after the address in the first Name Server (DNS) field is queried. The values of these fields can be any valid IP address in dotted notation (i.e. 172.23.8.5).

2.2.2.4.3Close the window to save any changes.

2.2.2.4.4Record the Ethernet Configuration information on the configuration sheet available at the end of this chapter.

2.2.2.5 DS1 ConfigurationAn APmax TM with C15 Announcements is preconfigured before shipment so that it can be physically installed and powered up and will be ready to provide announcement service with no additional configuration necessary. By default DS1 1 on each unit is Enabled. Channel 1 of DS1 1 is reserved for SS7.

The APmax TM UI can be used to alter the trunk assignments if required. For further information see the APmax TM User Manual Chapter 7 - “Digital Carrier Configuration” in the APmax TM User Manual. See Chapter 8. - "Announcements" in this document for more information regarding configuration of announcements. The following assumes the default configuration will be used.

From the APmax TM UI, right-click on the system’s icon in the Command Center window to invoke a popup menu, and select the System Configuration | Trunks | Digital Carrier Configuration command. For more information on the Digital Carrier Configuration window, refer to the APmax User Manual. Any changes made from this window will take immediately.

2.2.2.5.1Verify the settings in the APmax TM match those of the switch. Please refer to Section 3.3 - "C15 Configuration Sheet" and ensure the following values match. If they do not, change the APmax TM to match.

• T1 Line Coding should match LICD.



• T1 Framing should be D4 if T1 Line Coding is AMI. It should be ESF if T1 Line Coding is B8ZS.

• Transmit LBO Mode should match DIST.

2.2.2.5.2It is suggested that a Synch Master be configured for each unit. This will ensure that the internal clocks in the APmax TM are synchronized and will not drift. Under Digital Signal Carriers highlight Unit 1 and set the Synch Master for Unit 1 to DS1 1.

2.2.2.5.3Highlight Unit 2 and set the Synch Master for Unit 2 to DS1 1. Close the window.

2.2.2.5.4Write the DS1 settings for each unit on the configuration sheet.

2.2.2.6 SS7 ConfigurationFrom the APmax TM UI, right-click on the system’s icon in the Command Center window to invoke a popup menu, and select the System Configuration | SS7 Configuration command. For more information on the SS7 Configuration window, refer to the APmax User Manual. Follow the given procedure to set the values in the APmax TM.

2.2.2.6.1Select the General tab, Local SS7 Settings, Local Point Code, enter the APmax TM point code (see Section 3.3 - "C15 Configuration Sheet").

2.2.2.6.2Select the General tab.

• Outgoing AIN Queries, AIN Point Code, enter the point code used when the APmax TM originates an AIN query, if applicable. Normally the APmax TM will be performing GTTs for this query, so the APmax TM point code would be the one entered. In AIN Translation Type, enter the translation type used when the APmax TM originates an AIN query, if applicable. The default value for this field is 204.

• Outgoing CLASS GTT Queries, Class GTT Point Code, enter the point code used when the APmax TM originates a CLASS GTT query. Normally the APmax TM will be performing GTTs for this query, so the APmax TM point code would be the one entered. In CLASS GTT Translation Type, enter the translation type used when the APmax TM originates a CLASS GTT query. The default value for this field is 251.

Note: Once these steps are complete, GTT will need to be configured to point to the AIN/CLASS SSN in the switch. The GTT entries for outgoing queries are



generally different from those for incoming queries. This will be performed in the following steps.

2.2.2.6.3Select the Linksets tab and Add a linkset. Enter the Far-end Point Code. The Far-end Point Code is the SRP/STP of the switch (see Section 3.3 - "C15 Configuration Sheet").

2.2.2.6.4Add a link to the linkset. Make sure to use the settings previously configured on the switch when setting up the links (see Section 3.3 - "C15 Configuration Sheet").

• Specify the physical connection to the APmax TM.

• Set the data rate.

• Set the SLC. The SLC is the link number of the linkset that will physically connect to the APmax TM.

2.2.2.6.5Select the Routing tab and Add a route for the SRP/STP.

• Enter the point code of the SRP/STP (see Section 3.3 - "C15 Configuration Sheet").

• Enter “SRP” as the Route Description.

• Click OK.

2.2.2.6.6Add a route for the SSP. This route will be used when configuring ISUP trunk groups.

• Enter the point code of the Switch (see Section 3.3 - "C15 Configuration Sheet").

• Enter “SSP” as the Route Description.

• Click OK.

2.2.2.6.7Select the Global Title Translation tab. GTT will need to be configured to point to the AIN/CLASS SSN in the switch (SRP).

• See Section 16.3 - "Provisioning the APmax TM" to configure GTT for CLASS.

• Repeat for AIN. Use the SSN recorded when retrieving the switch information. See Section 3.3.3 - "AIN".



2.2.2.6.8Select the AIN tab. If Seven-To-Ten Mapping, i.e. seven to ten digit expansion is desired enter the required data. See the APmax TM User Manual for more information.

2.2.2.6.9To save the SS7 Configuration information, close the window.

2.2.2.6.10Write the SS7 settings for each unit on the configuration sheet.

2.2.2.7 Verify the DS1s are In serviceFrom the APmax TM UI, right-click on the system’s icon in the Command Center window to invoke a popup menu, and select the System Surveillance | Digital Carrier Status command. For more information on the Digital Carrier Status window, refer to the APmax User Manual.

2.2.2.7.1From the DS tab, verify the DS1s are in service. If the DS1s are not in service verify the DS1s are Enabled and the settings are correct. Configuration of the DS1s may be accessed from System Configuration | Trunks | Digital Carrier Configuration.

2.2.2.7.2The DS1s should be in service if the following conditions have been met:

• The DS1 cables have been physically connected from the C15 to the APmax TM (using the T1 cable assemblies, provided optionally).

• The DS1s have been defined as described in Section 2.2.2 - "Provisioning the APmax TM".

• The DS1s have been put into service from the switch end. See Section 3.2.3 - "Return DS1s to Service" for further information.

2.2.2.8 Verify the SS7 Links are In serviceFrom the APmax TM UI, right-click on the system’s icon in the Command Center window to invoke a popup menu, and select the System Surveillance | SS7 Status command. For more information on the SS7 Status window, refer to the APmax User Manual.

2.2.2.8.1At this point, the SS7 links should be in service and the Status indicator should indicate INS:

• The SS7 cables have been physically connected from the C15 to the APmax TM (using either the T1 cable assemblies or the RS449 SS7 cables optionally supplied with the system).



• The links have been defined as described in Section 2.2.2 - "Provisioning the APmax TM".

• The links have been put into service from the switch end. SeeSection 3.2.4 - "Return SS7 Links to Service" for further information.

2.2.2.9 Clearing the AlarmsUpon power up of the APmax TM System, the CPU reset alarms will be set in each unit. There may also be alarms reporting the DS1s as SMB. If not already cleared, this should be done now.

2.2.2.9.1From the APmax TM UI, right-click on the system’s icon in the Command Center window to invoke a popup menu, and select the System Surveillance | Alarm Status command. For more information on the Alarm Status window, refer to the APmax User Manual.

2.2.2.9.2Highlight the alarms and click Cancel Alarm.

2.2.2.9.3The alarms should not return. If the DS1 alarms or SS7 alarms return, check the provisioning of the DS1s and SS7 on both the switch and the APmax TM as well as the physical cabling. Ensure the DS1s and SS7 links are INS and clear the alarms.

2.2.2.10 Services To configure the various services on the APmax TM, such as C15 Announcements, CLASS, Calling Name, Voice Mail, etc, and properly provision the C15 please refer to the applicable chapter within this document.



2.3 APmax TM Configuration Sheet2.3.1

System ID:_______________

2.3.2 NTPNTP Server(s) Unit 1: ____________________________________

NTP Server(s) Unit 2: ____________________________________

2.3.3 Ethernet ConfigurationHost Name:__________________

Domain Search:___________________________

Name Server (DNS) Address:______________________

Name Server (DNS) Address:______________________



Table 2-6 Administration (OAMP) IPs

Unit 1 Unit 2

Administration

Subnet

Gateway

Table 2-7 Call Processing (VoIP) IPs

Unit 1 Unit 2

Calling Processing

Subnet

Gateway

DSP 0

DSP 1

DSP 2

DSP 3

2.3.4 DS1s2.3.4.1 APmax TM Unit 1 DS1 Number:______

Synch Master Set? Circle one: Yes/No

T1 Framing:___________

T1 Line Coding:_____________

Transmit LBO Mode:_________________

2.3.4.2 APmax TM Unit 2 DS1 Number:______

Synch Master Set? Circle one: Yes/No

T1 Framing:___________



T1 Line Coding:_____________

Transmit LBO Mode:_________________

2.3.5 SS7Point Code of APmax TM (OPC):_________-________-________

AIN Point Code:_________-________-________

AIN Translation Type:________

CLASS GTT Point Code:_________-________-________

CLASS GTT Translation Type:________

Linkset Name:__________________

Linkset ID:______

Far End Point Code (C15):_________-________-________

APmax TM Unit 1 DS1 Number:______

APmax TM Unit 1 Channel Number:______

APmax TM Unit 1 Data Rate:______

APmax TM Unit 2 DS1 Number:______

APmax TM Unit 2 Channel Number:______

APmax TM Unit 2 Data Rate:______

2.3.5.0.1 RoutingSRP/STP Far End Point Code:_________-________-________

SSP Far End Point Code:_________-________-________


3. Finding Information in the C15 25

3. Finding Information in the C15

This chapter provides general information for provisioning the C15. To configure C15 Announcements, CLASS, Calling Name, Voice Mail, etc., please refer to the applicable chapter within this document.

Once the necessary information has been gathered from the switch refer to section 2. - APmax Introduction and Installation to proceed with the necessary APmax configuration.

The following information is required:

• The point code of the APmax TM

• The point code of the SSP, SRP, or STP that will be connecting to the APmax TM

• The DS1s to be used between the switch and the APmax TM

• The SNRSs, SNLSs, and SNLs to be used for SS7

3.1 Requirements and General InformationThe C15 and APmax TM must contain Generic 2.0 or greater.

Software features such as CCS7, SSP, or SRP must be present in the C15 to support features in the APmax TM.

To the C15, the APmax TM appears to have a single SCP node with x number of links. The APmax TM is intended to operate in an SS7 network with a C15 as the SSP.

Note: Innovative Systems, LLC strongly recommends that C15 translations be performed by qualified Genband personnel.

3.2 Provisioning the C15Some of the information required to properly configure the APmax TM may be found in the C15 by following the process in this section. The C15 Configuration Sheet (see 3.3) should be used as an aid in keeping track of the required information.

3.2.1 DS1 ConfigurationDS1s must be configured in order to provide CCS7/SS7 between the switch and the APmax TM. The following is an overview on how to configure the switch (see section 2.).


26 3. Finding Information in the C15

3.2.1.1From OVLY NET, add a DS1. Specify the location where:

site Base Site

pm Port Module (1-10)

pc Port Controller (1-2)

p DS1 TDM

Record the DS1 location for each APmax TM unit on the C15 Configuration Sheet.

3.2.1.2Set APPL to DTRK (the DS1 will be used as a digital trunk).

3.2.1.3DSNM is the descriptive name for the DS1. Set this to “APMAX XXXX”, XXXX being the APmax TM System ID. The System ID will be on a label on the front of the APmax TM units.

3.2.1.4LICD is the line coding to be used on this DS1. Record the LICD.

• Alternate Mark Inversion (AMI) - This is the conventional T1 Zero Code Suppression. Supports 56K data throughput.

• Bipolar 8 Zero Substitution (B8ZS)- Allows greater than 56K data transmission.

3.2.1.5The baud rates (PRAT) for the add/drop channels must match the RATE to be configured for the signaling set.

3.2.1.6SYNC asks if the interface carrier has synchronized channel banks. Set this to a NO value.

3.2.1.7FRFM asks the user for the frame format used on this DS1, SF (Superframe) or ESF (Extended Superframe). Set this to a SF value.

3.2.1.8DIST asks for the maximum line out distance value in feet for the DS1 cable from the Port Module to the first repeater. Valid values are 110, 220, 330, 440, 550, and 660. Record value.



3.2.1.9Assign the add/drop channels (ADC1 and/or ADC2) to be used for the CCS7 signaling links (SNLs). Record value.

3.2.1.10Set the PRAT, baud rate, of the SS7 channel. Record value.

If the DS1 has already been built, then query the DS1 and record the information in bold to the configuration sheet.

DS1 (NT6T08) IS 01 2 12APPL DTRKDSNM APmax 2013LICD AMIINBS YESSYNC NOFRFM SFDIST 110SLPM 40SLPO 255BPVM -6BPVP -3FRLM 3FRLO 255ADCI 1PRAT 56ADC2 UNAS

It is strongly suggested that two DS1s be setup for SS7. One DS1 hooked to APmax TM Unit 1, and the other hooked to APmax TM Unit 2. Each DS1 should have a signaling link for SS7 to provide redundancy. Record the DS1 location, SNL channel, and baud rate on the configuration sheet.

3.2.2 SS7 ConfigurationThe following is an overview on how to configure the switch for SS7 between it and the APmax TM.

3.2.2.1 Determine Point CodesThe point code of the SRP/STP can be found by doing the following. From OVLY CNFG in the C15, the command QUE CCS7 can be issued. The display should look similar to one of the following:

CCS7NODE SRP CCS7RPT DSBL NODE SSPDUAL YES RPT DSBLL3PC 010 001 000 OPC 010 001 000



The bolded lines indicate the point code needed. Record the SRP/STP point code. The point code of the switch is on the line labeled L4PC. L3PC or OPC are the SRP point code. L4PC, if present, is the SSP point code. If a L4PC line does not exist, the point code of the switch and the SRP/STP is the same. Record the SSP point code.

The point code of the APmax TM must be obtained from your SS7 provider. Record the APmax TM point code.

3.2.2.2 Add Signaling Network Route Set (SNRS)From OVLY SNET, add SNRS members (for offices performing Global Title Translations for E800, CLASS, and AIN) for the following:

3.2.2.2.1Each node to which the C15 switch has a direct CCS7 link connection. These could include the adjacent STP pair and any SP nodes in the sub-network if configured as SRP.

3.2.2.2.2ISUP trunk groups that are to be configured. The point codes of the offices at the remote end of these trunk groups must be assigned.

Add signaling network route set (SNRS) clusters and networks as deemed necessary by the SS7 provider. Cluster and/or network routing will normally be required when an SRP is configured or when CLASS feature interaction is required for a node (or nodes) to which the C15 switch has no direct CCS7 link connection or no direct ISUP trunk connection.

3.2.2.3 Add Signaling Link Sets (SNLSs)A link set must be defined for all network nodes to which the C15 switch will have a direct signaling link connection.

3.2.2.3.1From OVLY SNET, add an SNLS. Record the SNLS number.

3.2.2.3.2The SNLS RATE must match the DS1 add/drop channel to which the signaling links (SNLs) are to be attached. Set the RATE to the value recorded on the C15 Configuration Sheet (PRAT) for the respective DS1.

3.2.2.3.3The ERRC is the error correction to use for all links in the link set. Both ends of a link must be assigned the same error code and at the time of this writing basic error correction (BEC) is the only valid entry.

L4P 1 010 001 001 ENBL



3.2.2.3.4The DPC is the APmax TM point code. Use the APmax Point Code value recorded on the C15 Configuration Sheet.

3.2.2.3.5The prompt for LTYP will appears if NODE = SRP in OVLY CNFG (QUE CCS7). It specifies the Link Type for each link in the set, A-Link (ALNK) joins SSP to SRP, or SRP to STP. C-Link (CLNK) joins SRP to SRP.

If the SNLS has already been defined, then query the SNLS and verify the information in bold is correct per the steps above. From OVLY SNET, QUE SNLS (number of the assigned link set).

SNLS 8RATE 56KERRC BECDPC 010 008 001LTYP ALNK

3.2.2.4 Add Signaling Links (SNLs)3.2.2.4.1From OVLY SNET, add an SNL.

3.2.2.4.2Enter the SNLs of which the SNL is a member. Use the value recorded on the configuration sheet for the SNLs.

3.2.2.4.3Enter the Signaling Link Code (SLC) of the link. The SLC represents the numeric order of the Signaling Link in the SNLS. This SLC must match the SLC assigned to the link at the far end of the SNLS. Record this value on the configuration sheet for the proper APmax TM unit. It is suggested to use SLC 0 for Unit 1 and SLC 1 for Unit 2.

3.2.2.4.4Enter the location of the DS1 add/drop signaling channel to be used. Use the value written on the configuration sheet (ADC1) for the respective APmax TM unit and DS1.

3.2.2.4.5When defining a NEW link, the PARM prompt asks whether Level 2 parameter values are to be used for this link or whether user defined values are to be used.



3.2.2.4.6If PARM is set to USER, timers T1 through T1 will prompt for a value. Select Enter to use of the default values. The following example shows default timer values for a 56k link set rate.

3.2.2.4.7Repeat for additional links.

If the SNLs have already been defined, then query the SNLs and verify the information in bold is correct per the steps above. From OVLY SNET, QUE SNL, followed by the SNLs and SLC.

SNLS 8SLC 0DS1 IS 01 2 12 01T1 14 SECT2 11 SECT3 11 SECT4 2300 MSECT5 100 MSECT6 7 SECT7 2500 MSEC

3.2.2.5 Assign Signaling Network RoutesAssign SNRSs for each DPC. The routes are the link sets to be used in order to send CCS7 messages to the DPC. P1 and P2 are used to assign the higher-priority routes to a DPC. A1 and A2 are used to assign alternate routes of lower priority. If two link sets are assigned equal priority to a DPC (for example, P1 = link set 1, P2 = link set 2) then routing to that DPC is accomplished over the combined link set consisting of those two links sets.

3.2.2.5.1From OVLY SNET, add an SNRS.

3.2.2.5.2Set LEVL to MEM. Members represent individual network nodes and are defined within clusters. A maximum of 255 member level SNRSs can be assigned.

3.2.2.5.3Set CODE to the DPC of the SNRS, i.e. the APmax TM point code, see the configuration sheet.

3.2.2.5.4Set TRNS. This specifies the method used for sending transfer messages to signaling points when the status of a route set changes, that is, becomes available or unavailable.



• BRDC Broadcast method. Broadcast transfer messages to adjacent signaling points.

• RESP Response method. Send transfer messages to adjacent signaling points only in response to messages received from them.

3.2.2.5.5Set P1 to the SNLS of the first primary, and possibly only, route. See the configuration sheet. Set PRI2, ALT1, and ALT 2 accordingly.

If the SNRSs have already been defined, then query the SNRSs and verify the information in bold is correct per the steps above. From OVLY SNET, QUE SNRS MEM, followed by the DPC (Destination Point Code).

LEVL MEMCODE 010 008 001TRNS RESPPRI1 8PR12 UNASALT1 UNASALT2 UNAS

3.2.3 Return DS1s to ServiceBefore returning the DS1s to service, the APmax TM, to which the DS1s connect, should be installed and configured. See section 2. - APmax Introduction and Installation for information on installing and configuring the DS1s on the APmax TM.

From OVLY DED.

• RTS DS1 site, site being the (site) pm pc p.

• STAT DS1 site will return the status of the DS1.

3.2.4 Return SS7 Links to ServiceBefore returning the SS7 links to service, the APmax TM, to which the SS7 links connect, should be installed and configured. See section 2. - APmax Introduction and Installation for information on installing and configuring the DS1s on the APmax TM.

From OVLY SND.

3.2.4.1Return the links to service.

• RTS SNLS n, n being the SNLS number. This will RTS all member links for this SNLS, OR,



• RTS SNL n x, n being the SNLS number and x being the SLC number. Repeat for all links.

3.2.4.2Verify the links are in service.

• STAT SNLS n, to return the status of the member links of the SNLS and verify they are in service, OR,

• STAT SNL n x, to return the status of the link and verify it’s in service. Repeat for all links.

3.2.4.3Check the Signaling Route Set to see if its available.

• STAT SNRS pc, pc being the APmax TM point code.

• If unavailable, then unblock to make available. UBLK SNR pc PRI1

3.2.5 CLASSRefer to Chapter 16. - "CLASS Global Title Translation" for information on how to configure the switch and the APmax TM for CLASS. Please refer to section 2. - APmax Introduction and Installation to install and configure the APmax TM before provisioning CLASS.

3.2.6 Calling NameRefer to Chapter 9. - "Calling Name Delivery" for information on how to configure the switch and the APmax TM for Calling Name. Please refer to section 2. - APmax Introduction and Installation to install and configure the APmax TM before provisioning Calling Name.

3.2.7 AINThe APmax TM has the capability to provide the functionality of an AIN SCP. To provide these features, the C15 must be configured for AIN. This section will provide information on setting up AIN in the C15. For specific service related setup, refer to the applicable chapter in this document. This section assumes that the SS7 links to the APmax TM are setup and functioning.

The following has been pulled heavily from Nortel SOP 0164 through 0168, available in document NTP 297-3102-311P1, and outlines the steps necessary to configure the C15 for AIN. This document assumes that SS7 is already up and functioning on the APmax TM in which AIN services are being deployed.

Below includes some examples of output of the C15 when you are following SOP 0164 through SOP 0168. The settings may not represent the actual settings of the switch being configured.

3.2.7.1 Feature Bits/AIN TriggersThe APmax TM requires that the following feature bits be turned on:



Note: Not all features use every trigger. Certain services may only use one trigger and others may require the use of two. Future services may require the use of additional AIN triggers.

OHD YES AIN Off-Hook Delay trigger service is enabledDIG YES AIN public office dialing plan (PODP) 3 through

10-digit (DIG) trigger service is configuredTA YES AIN Termination Attempt trigger service is

enabledFCD Feature Code Trigger. This trigger is associated

with administration of the Telemarketer Call Management Service

3.2.7.2 Generic Condition RoutesThe following generic conditions need to have routes setup to handle them.

OVLY CNFG-GCON AINF 73 Asks for the Advanced Intelligent Network (AIN) final treatment route to be applied when a call–related fatal error (either protocol or application) occurs.

AIND 73 Asks for the AIN disconnect call treatment route to be applied when the SCP sends a disconnect message to the SSP to disconnect a call. The following conditions apply to AIND:

• Calls to be disconnected that have originated from a trunk are routed to AIND

• Calls that have originated from a line with the off-hook immediate trigger (OHI) station option are routed to AIND

CBSY 73 Asks for the route to be taken when the circuit requested by the SCP is no idle.

Note: Route number 73 is an example. Route numbers may vary.

It is recommended that standard announcement 66 be used for the handling of these conditions. Announcement 66 is “We're sorry, your request cannot be processed at this time, please try again later.” Point these conditions to the route that calls for announcement #066.

3.2.7.3 AIN Subsystem NumberThe AIN Subsystem Number should be declared. If this SSN is already set, do not change. The recommended value is 10. Record this value on the configuration sheet provided at the end of this chapter.

OVLY CNFG-SUBAO.1 10



3.2.7.4 LEC and LATA numbersIf the switch is in-service and processing calls these numbers are probably already set.

OVLY CNFG-SYS LEC 0110

Asks for the originating Local Exchange Carrier (LEC) number for the office. This is the carrier used for 800 queries.

LATA Asks for the originating Local Access Transport Area (LATA) number for the office.

3.2.7.5 AIN Configuration SettingsAs of Release 3.0 the APmax TM does support AIN announcements. Some of the general settings covering AIN:

OVLY CNFG-AIN MAXT 6

Asks for the maximum number of times AIN triggers can be encountered during a given call. 6 is the default.

DQTM 3 SEC Asks for the time, in milliseconds or seconds, that the C15 switch should wait for a response from the SCP. Three seconds is the default.

AATG 1006 Asks for the AIN announcement trunk group. If you are also using the APmax TM for announcements, this should be set to the same Trunk Group as your STD/CLASS announcements.

ADVS OFF MSGB 0 STRT KP

Asks for the start signal to be out pulsed to the vendor digital recorded announcement (VDRA) unit prior to out pulsing the announcement identifier. KP is the default.

STOP ST Asks for the start signal to be out pulsed to the vendor digital recorded announcement (VDRA) unit after out pulsing the announcement identifier and associated digits. ST is the default.

MSGD 5 Asks for the number of digits in the announcement identifier. Five is the default.

PATL ON Prompted if the Local Number Portability (LNP) feature is configured in the switch. Process AIN triggers after LNP query. Asks whether to process AIN triggers encountered when translating the LNP query results.

CCOD PERM Asks for the type of carrier code to accept from the AIN database. The responses reflect carrier identification code (CIC) expansion.

3.2.7.6 Feature BuffersThe large and extra-large feature buffer calculations should be completed by Genband. These should be completed by Genband at the time they turn AIN on.



3.2.7.7 Operational Measurement Collection and ReportingSetting this up is at the discretion of the phone or engineering company. No recommendations given.

OVLY OMC-OMC

3.2.7.8 Automatic Message AccountingThe billing control table for the AIN call type must be defined.

OVLY AMA-AMA CTYP AIN BTYP ALWS

Asks when billing is required for the above specified call type. Call is always billed, whether answered (ANS) or unanswered.

PRNT (YES or NO) Asks whether billing data for the call type are to be printed out on a maintenance terminal.

PRCL MTC Prompted if PRNT = YES. Asks for the output terminal class for AMA messages.

TDWN NBIL Asks for the treatment given to a call of a specified type if the AMA system is down. NBIL = Call proceeds with no billing.

TNBR NBIL Asks for treatment given a call type when an AMA record cannot be made because of no billing register being available for the call. NBIL = Call proceeds with no billing.

ANIF BUSY Asks for the route to be taken (ANI fail route) when ANIF is specified in the above failure conditions.

3.2.7.9 Call RoutingWhen an analyze route or forward call message is returned from the APmax TM, the APmax TM may tell the C15 SSP to route the call by one of the following methods:

3.2.7.9.1 Trunk Group RoutingEach trunk group parameter contains a value which the C15 switch uses as an index into the trunk group-to-route (TGR) table to obtain a C15 route number used to route the call. The ROUT should be the same as the AINF ROUT that handles the failure conditions.

OVLY AIN REQ NEW TGR RTI 00000001 ROUT 73 REQ QUE TGR RTI ROUT 00000001 73



3.2.7.9.2 Carrier RoutingNote: This is not currently used by the APmax TM to route calls. This would normally already be configured in a switch that is in-service.

The C15 switch validates the carrier against a carrier table, inserts the prefix 10XXX or 101XXXX in front of the called party (either original or SCP specified), and then uses translations to route the call.

EQA (CARR) If not already declared, assign the inter–LATA carrier access code to be used.

CNFG (SYS) If not already declared, assign the local exchange carrier (LEC) number.

CNFG (AIN) Specify whether the C15 switch uses 3–digit or 4–digit carrier identification codes (CIC), or permits the use of 4–digit carrier codes that begin with the digits, 0, 5, or 6.

TRNS (PRFX) If not already declared, set up the prefix translator with either the 10XXX or the 101XXXX prefixes for 3–digit or 4–digit inter–LATA carrier access code dialing, respectively.

3.2.7.9.3 Called Party RoutingNote: This would normally already be configured in a switch that is in service. This is the normal method used by the current AIN services to route calls.

The C15 switch inserts the proper prefix (that is, 1+, 0+, etc.) based on the nature of the number of the called party and then uses normal translations to route the call using the called party ID parameter. The dialable number translator must be set up for called party routing if 1+ dialing for intra–LATA destinations is not handled by normal translations.

Note: If the CLASS feature, Automatic Recall (AR) is configured, the following information should already be set up.

AREA (HDD) Indicate for each HNPA the foreign NPAs and their office codes for which digit deletion is required, and the corresponding number of digits to delete.

ROUT (TR) Define the toll region to be declared in the following step.

ROUT (DEST) Determine the dialable number screen translator associated with each destination.

THGP (THGP) Determine the dialable number screen (DNS) translator associated with each thousands group.

HUNT (EBS) Determine the dialable number screen translator associated with each EBS group.



3.2.7.10 Escape Code ListFor APmax TM services that may use the OHI or OHD triggers it is necessary to add certain numbers to the escape code list. Numbers on this list will not encounter an AIN trigger. Numbers on this list should include 911 and possibly the phone number of the business office.

OVLY AIN REQ NEW TYP ESCL ESCD 911

TRNS (DNS) Set up the DNS translator for each appropriate destination, EBS group, and thousands group. Set up screening translator for calls that originate outside of an EBS group.



3.3 C15 Configuration Sheet3.3.1 DS1s

3.3.1.1 APmax Unit 11). DS1 Location:_________________

a. Line coding (LICD):____________

b. Line build out (DIST):____________

c. SNL channel (ADC1):____________

d. Baud Rate (PRAT):____________

3.3.1.2 APmax Unit 21). DS1 connected to APmax TM Unit 2 (location):_________________

a. Line coding (LICD):____________

b. Line build out (DIST):____________

c. SNL channel (ADC1):____________

d. Baud Rate (PRAT):____________

3.3.2 SS71). Point Code of SRP/STP: ________ - ________ - ________

2). Point Code of SSP: ________ - ________ - ________

3). Point Code of APmax TM (DPC): ________ - ________ - ________

4). SNLS:____________

5). APmax TM Unit 1 SLC:____________

6). APmax TM Unit 2 SLC:____________

3.3.3 AIN1). Subsystem Number:_________

2). Trunk Group:_________ Connected To:__________________


4. Automated Configuration Service 39

4. Automated Configuration Service

4.1 General DescriptionSIP phones or User Agents (UAs) support a complex set of feature settings and upgrading options beyond the basic SIP service settings. Modifying these feature settings can have a dramatic effect upon the observed Quality of Service (QoS) and impact network efficiency and reliability. Each device manufacturer provides regular firmware releases to resolve known issues and provide new features. This, however, introduces the potential of incompatibilities between supported firmware releases and customer installed upgrades. Because a typical subscriber will not likely possess the requisite skills to provision and manage the complexities of SIP feature settings and their interactions, a managed network approach becomes necessary.

A managed network approach ensures the overall QoS and an acceptable customer experience. A key component of this approach is an Automated Configuration Service (ACS). ACS provides a central provisioning interface to the deployed SIP devices on the customer premises and the common network element from which the subscriber’s devices obtain their individual configuration settings and firmware revisions. The service provider staff provisions the station’s settings is the central ACS using the APmax User Interface (UI) and the subscriber’s SIP device pulls their settings from the ACS when necessary.

4.2 APmax Add SIP Phone This step can happen any time prior to providing the phone to the customer.

4.2.1Manually using the APmax UI, right-click on the APmax System Icon/ System Configuration/SIP ACS/ Configuration command.

4.2.2Within the Inventory tab, select the Add button at the bottom of the window. An Add Phone to Inventory window will appear.


40 4. Automated Configuration Service

Figure 4-1 Add Phone to Inventory Window

4.2.3Select the Device Type or enter the UPC number. Enter the MAC Address and select the Accept button.

If available, these numbers may be entered using a hand-held scanner.

Figure 4-2 SIP ACS Configuration

4.2.4 Import Existing Phones Into InventoryExisting SIP phones may also be imported to the inventory from a file.

4.2.4.1Select the Import button within the SIP ACS Configuration add-on window. An Import Phones Into Inventory window will appear.

4.2.4.2You may import a file to enter all phone inventory. Copy the two columns (MAC Address and Device Type UPC) from a created spreadsheet file, and then select the Paste button.



Figure 4-3 Import Phones Into Inventory Window

4.3 Add Phone Service OptionsSetup the CPK for the SIP location in the C15. Notice the UID is unused6059962897, and the PSWD is 9962897. The “unused” will be populated by the APmax, and the technician will enter the “6059962897” and the “9962897” when prompted by the IVR when initially plugging the SIP phone into the network.

REQ #OVLY CPK DMO000 CPK REQ QUE GWL GWE 2 130 GWL (SIP) GWE 2 130 UID UNUSED6059960119 HIDX 1 PSWD 9960119 RINT UNAS AUTH UNAS BIND 1



Setup the STN for the device

STN DN 605 996 0119 LOC (SIP) GWE 2130 OPT 1FR EMR 0 RTP 0 PRES 0288 CFB CFD MD 1 CND CNAM

4.4 Add Subscriber and ACS Service in APmaxThe APmax ACS settings may be configured prior to any SIP stations being distributed to subscribers/technicians. If the telco decides not to do this, the Subscriber Management/Service entry will auto-subscribe and configure for the subscriber on initial call from the SIP phone during provisioning. This section will show you how to manually add a Subscriber with the ACS service if telco decides to configure in APmax first.

4.4.1Open the Subscriber Management window. There is several ways to do this, so refer to the APmax User Manual to identify how to open. Select the Add button in the Subscribers pane.

4.4.2Select the Add button in the Subscribers Management add-on. An Add New Subscriber window will appear.

Figure 4-4 Add New Subscriber Window

4.4.3Populate the fields, and select SIP ACS as the value in the Service field. Select the OK button. An Add SIP ACS Subscriber window will appear.

URI [email protected] BRND UNKNOWN



Figure 4-5 Add SIP ACS Subscriber Window

4.4.4Populate the device for this subscriber with the Type or UPC and also the MAC Address of the device that will go to this subscriber. Select the OK button. The Subscriber Management window will appear with a SIP ACS branch under the subscriber location.

4.5 DHCP Server Setup for the Device RequestOperation of some features of this service requires a properly configured DHCP server that the SIP device queries to obtain the TFTP address of the APmax. Network connectivity from the APmax to the SIP device being used and the available network switch is also required.

A DHCP server is used to provide the SIP device with the IP address of the APmax TFTP server. The DHCP server must be configured to provide the TFTP address using Option 66 or Option 160. Specific device models may have options that are mutually exclusive of one another. These options must be set according to the Vendor Identification String in the DHCP query.

When a device is initially powered on, a DHCP server is queried to obtain an IP address. This IP address is either provided by the network or by a customer premises router. At the same time the IP address is provided, the address (or DNS name) of the APmax ACS TFTP server is provided to the SIP device. If a DNS name is provided the provider’s DNS server is then queried to obtain the IP address of the APmax ACS TFTP server.

4.5.1Setup the DHCP server to use the APmax Call Processor IP address as TFTP address.

Example: DHCPD Configuration File

The following is an example of a DHCPD configuration file:

## Sample configuration file for ISC dhcpd for Debian



## Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as# configuration file instead of this file.## $Id: dhcpd.conf,v 1.1.1.1 2002/05/21 00:07:44 peloy Exp $## The ddns-updates-style parameter controls whether or not the server will# attempt to do a DNS update when a lease is confirmed. We default to the# behavior of the version 2 packages ('none', since DHCP v2 didn't# have support for DDNS.)ddns-update-style none;# option definitions common to all supported networks...option domain-name "innsys.innovsys.com";option domain-name-servers 172.23.8.5,172.23.8.7;default-lease-time 600;max-lease-time 7200;# Define Custom Optionsoption option-150 code 150 = ip-address;option option-160 code 160 = text;# If this DHCP server is the official DHCP server for the local# network, the authoritative directive should be uncommented.authoritative;# Use this to send dhcp log messages to a different log file (you also# have to hack syslog.conf to complete the redirection).log-facility local7;class "Polycom"{#match if substring (hardware,0,10) = "1:00:04:f2";match if substring (option vendor-class-identifier,7,7) = "Polycom";option option-160 "tftp://192.168.111.253";}class "LG-Nortel"{match if substring (option vendor-class-identifier,0,9) = "LG-Nortel";}# class "cisco7961"# {# match if substring (option vendor-class-identifier,0,36) = "Cisco Systems, Inc. IP Phone CP-7961";# option tftp-server-name “10.10.10.1″;# }Appendix B DHCPD Configuration File 83July 2011 Innovative Systems, L.L.C. Proprietary SD1334.02Automated Configuration Service Service Descriptionsubnet 192.168.111.0 netmask 255.255.255.0 {option subnet-mask 255.255.255.0;option broadcast-address 192.168.111.255;option routers 192.168.111.254;range 192.168.111.2 192.168.111.200;option tftp-server-name "192.168.111.253";#option option-150 192.168.111.1;option time-offset -21600; # Central time zone offsetoption ntp-servers 192.168.111.1;}

4.6 APmax TFTP ServerThe SIP device then queries the APmax TFTP Server and provides its MAC and IP address.The device will also request basic phone configuration and



firmware for itself. The APmax will upgrade the firmware and the basic phone configuration for the device. This will allow the SIP device to connect with the APmax server by dialing the configured SIP ACS IVR access number.

4.7The installer can now access the service by dialing the configured SIP ACS IVR access number.

OVLY ROUT DMO000 ROUT REQ QUE ROUT 500 ROUT 500 Route number ALTR CBSY Alternate route TYPE SIP Type of route RTNM APMAX 9070 Route name UPGR NONE Upgrade route to route TRYP EAS Type of SIP call CTYP NONE Type of AMA call carried byt the route LNPB NO Asks if this ROUT’s CTYP should be used for

billing purposes. For an LNP call should the call be routed to a different route due to an LNP trigger?

TG 500 APMAX 9070 TG that serves the route CHG YES Is there charging supervision on this route? COS NONE Type of Class of Service tone that is applied upon

answer from destination. DEL 0 Specifies the number of leading digits other than

prefix digits, that are deleted before outpulsing. APFX NONE Prefix to be added for outpulsing PGNC NO Peg the call as non-completing REQ

#OVLY TG DMO000 TG REQ QUE TG 500 TGTP ? INC OUT 2WAY [0-8184|FULL] TGTP 2WAY Trunk Group Type TYP TG NUM 500 TGTP 2WAY Trunk Group Type TGNM APMAX 9070 Trunk Group Name MG NO SIGT SIP Signaling Type



STSI 0 HNPA 605 RC 0 RTP 0 TRNL PRFX Type of Translator PRFX 0 Number of the translator APFX NONE Prefix to be added TRFC NONE Class of traffic incoming over the trunk group 4XCD NO ACKA NO Alarm Checking Access TYPC NOCO Coin Type NXX UNKN NXX of the trunk group LATA 640 Originating LATA of the end office served by this

trunk group CMCT NO TGID NONE Trunk group ID entered into the User ID

parameter when any trigger is encountered by a call originating on a trunk in this trunk group

SIT NO Shared Interoffice Trigger CNAR NO Connecting Network Access Recording LRN NONE Location Routing Number TNDM NO For billing purposes - Is call connected to a far-

end office by way of Access Tandem Switch? LDAT NO DTSI 0 TRFC NONE EOAT NO ATIC NO CMCO NO TGMU NO HOST 172.23.11.63 NUSR APMAX 9070 NPSW PASSWORD IP 172.23.11.63 PORT 5060 PROT UDP T38F NO SBC NO CODC G711 PKSZ 20 SS DSBL DIGT BOTH AUTH NO INV + YES CLIM 48 ITIM 5 KLHI NO



4.8The service will prompt the isntaller to assign the SIP device an account code and phone number. The SIP ACS IVR service will then provision the SIP account setting in the C15. This will be a query and verifacation for the device for the username and password.

The SIP ACS service will use the Switch Interface Configuration service to communicate with the C15.

4.8.1To configure the Switch Interface Configuration, right-click on the APmax blue system icon and select System Configuration | Switch Interface Configuration.

Figure 4-6 Switch Interface Configuration Window

4.8.2Select the Add button in the Select a Configuration section of the Switch Interface Configuration add-on. An Add Switch Configuration window will appear (see Figure 4-7).

SVID NO CPBY 0 STAT INS REQ



Figure 4-7 Add Switch Configuration

4.8.3Populate the Description, Switch Address, and Billing E-mail Address of the Add Switch Configuration window. Select the OK button.

4.8.4Select the Mapping tab to configure the information from the APmax to the switch.



Figure 4-8 Mapping Tab

4.8.5Select the Add button and an Add Number to IP Address Mapping window will appear (see Figure 4-9).

Figure 4-9 Add Number to IP Address Mapping Window

4.8.6Within the Add Number to IP Address Mapping window, enter the required fields and select the OK button. The SIP ACS IVR service will then force a reboot of the SIP device.



4.9 SIP Registration with the C15When the SIP device reboots, it will send a request again to the APmax TFTP server to obtain an IP address. The ACS service will then return the “real” phone configuration to the device. The device will then register with the C15 using the new phone configurations. The SIP device may now be provisioned with specific settings using the Subscriber Management user interface and the ACS Web Portal options.

4.10 Adding a SIP Device in the C154.10.1 Add Lines to the C15

OVLY CPKREQ NEW GWL GWE 2 111 "6059962878" "9962878" UNAS UNAS 1 REQ NEW GWL GWE 2 112 "6059962879" "9962879" UNAS UNAS 1

4.10.2 Set the User ID for all SIP Stations4.10.2.1

OVLY DNQUE STN 996 2880DN 605 996 2880LOC (SIP) GWE 2 113OPT 1FR EMR 0 RTP 0 PRES 0288 MD 1 CND CNAMOVLY CPKQUE GWLGWL GWE 2 113GWL (SIP) GWE 2 113UID 6059962880HIDX 1PSWD 9962880RINT UNASAUTH UNASBIND 1URI [email protected] UNKNOWN

Query the Line



4.10.2.2 Change the UID for the Line

CHG GWLGWL (SIP) GWE 2 113UID “UNUSED6059962880”PSWD “9962880”RINT NO CHANGE JUST PRESS ENTERAUTH NO CHANGE JUST PRESS ENTERBIND NO CHANGE JUST PRESS ENTER

4.10.2.3 Verify Changes to the Line

QUE GWLGWL GWE 2 113GWL (SIP) GWE 2 113UID UNUSED6059962880HIDX 1PSWD 9962880RINT UNASAUTH UNASBIND 1URI [email protected] UNKNOWN




5. Automated Call Distributor 69

5. Automated Call Distributor

5.1 General DescriptionThe APmax™ Automated Call Distributor (ACD) service provides a call management platform to support inbound and outbound customer care calls and telemarketing services. The service provides a telephone operator enhanced capabilities to better manage inbound call traffic intended for customer care staff. Tools are provided to assist the operator in managing pools of available agents and then assessing their proficiency.

The service functionality is optimized for use with the Innovative Systems eLation ™ billing system. Optionally, the customer care stations may be SIP devices that connect directly to the APmax server.

5.2 Accessing the ACD ServiceThe service will be encountered by forwarding the access number to a route and a trunk group

5.2.1 Route Setup for the ACD Access Number REQ **** # ovly route OAMP003 # ovly rout DMO000 ROUT REQ que rout 301

ROUT 301 ALTR OVFL TYPE ISUP RTNM APMAX ACD 9071 UPGR NONE ITYP IEAS CTYP NONE LNPB NO TG 301 APMAX 9071 ACD DTSI 0 CHG YES COS NONE DEL 0 APFX NONE ID DFLT FANI NO PGNC YES REQ **** # ovly tg DMO000 TG


70 5. Automated Call Distributor

REQ que tg 301 2way TYP TG NUM 301 TGTP 2WAY TGNM APMAX 9071 ACD MG NO SIGT ISUP BDRT 56 OPCX 1 DPC 010 010 010 INBS NO AUUS NO AATP NO PKTP DTRK SITE BASE TGDP ELOC CNFS NO SNTC YES ITXF 2010 IRXF 2010 COIN NOCO STSI 92 HNPA 605 RC 7 RTP 0 TRNL PRFX PRFX 0 APFX NONE TRFC NONE 4XCD NO ACKA NO TYPC NOCO NXX UNKN LATA 640 CMCT NO TNS NO TGID NONE SIT NO CNAR NO LRN NONE TNDM NO LDAT NO UNUM REL NCKT REL CONG REL NORT REL TMPF REL NRSC REL DNCH REL DOOO REL CREJ REL PERR REL XRER REL BUSY REL OTXF 2010 ORXF 2010 CINT 1 GDTI 768 MSEC GLAR NONE IDLE MOST


5. Automated Call Distributor 71

SYNC NO 2RID YES EOAT NO OSNC NO ATIC NO 4XCD NO CMCO NO HOPI NO CIP NO SPN YES JIP NO BCAP DFLT OCNP YES RNP YES RIP YES CHNP YES TGMU NO TRK MTCH 01 01 03 02 IDLE CIC 1 MTCH 01 01 03 04 IDLE CIC 3 MTCH 01 01 03 05 IDLE CIC 4 MTCH 01 01 03 06 IDLE CIC 5 MTCH 01 01 03 07 IDLE CIC 6 MTCH 01 01 03 08 IDLE CIC 7 MTCH 01 01 03 09 IDLE CIC 8 MTCH 01 01 03 10 IDLE CIC 9 MTCH 01 01 03 11 IDLE CIC 10 MTCH 01 01 03 12 IDLE CIC 11

Note: Partial trunk list output. To specify # trunks to output enter 0-8184 after TGTP. To see complete trunk list use `FULL` option. Please wait for TG totals.

#TKS 92 IDLE 90 CPBY 2 OOS 0 REQ OAMP021 #717

5.2.2 Setting up AIN for ACD**** # ovly ain

DMO000 AIN

REQ que slhr SLHR 36 SLHR GTT1 TRN1 GTT2 TRN2 GTSC 036 010 010 010 186 NONE 000 CLED

REQ que adsc 36 SLHR ADMINISTRATIVE STATE CODES: 036 OHI OFF OHD OFF PRI OFF SIT OFF BRI OFF FCD OFF CDP OFF DIG OFF N11 OFF AFR OFF TA ON LNP OFF

REQ


72 5. Automated Call Distributor

5.2.3 Setting up DN’s for ACDSetup for Forwarding access numbers to ISUP trunk group for Auto Attendant Route properly.

LOGI ADMN MTC DMO TRAF DEBG LIT # ovly dn DMO000 DN REQ que dn 990 7090 DN 990 7090 ROUT RTE 250 APMAX VM 9063

REQ que stn 990 7083 STN DN 990 7083 LOC (SIP) GWE 9000 OPT 1FR EMR 0 RTP 0 EBS 0 MD 3 CND CNAM PRK DPRK TA CFWY 36 DND


6. Call Logging Portal 73

6. Call Logging Portal

6.1 General DescriptionThe Call Logging Portal Service utilizes an ability of the C15 to send a User Datagram Protocol (UDP) packet containing call detail information each time a station subscribing to the Call Logging (CLGS) feature makes or receives a call.

The Call Logging Portal Service listens for those packets, processes them, and generates call records which are stored on the APmax TM system. At the predesignated process time, the service builds a comma-separated value (CSV) file of the call records. This CSV file is then sent to the subscriber via e-mail.

This chapter will assist in the switch setup for the Call Logging Portal Service.

6.2 Switch Setup6.2.1 Feature Bits

If the following feature options are not available options please contact Genband so the feature(s) can be enabled on your switch. Feature bits that are required for Basic Conferencing are as follows:

IBSR YES Integrated Billing Storage and Retrieval (IBSR) feature must be enabled.

CLGS YES Call Logs feature must be enabled

6.2.2 AMA SettingsThe BTYP (bill type) must be set to ALWS (always) for SLUS (Subscriber Line Usage Study) and TSLS (Terminating Subscriber Line Usage Study) in overlay AMA:

OVLY AMA-SLUS BTYP ALWSOVLY AMA-TSLSBTYP ALWS

6.2.3 CLGS SettingsThe switch ADDR must be set to the IP address of Administrative Processor of APmax TM Unit 1. The PORT must be set to 32567. Record this information on the configuration sheet pro-vided at the end of this chapter.

OVLY CNFG-CLGS ADDR 172.23.8.187 PORT 32567


74 6. Call Logging Portal

6.2.4 Station ProvisioningThe Call Logging Portal subscriber’s DN must have the CLGS line option assigned as well as SLUS.

STN DN 996 1604 LOC IS LCE 01 1 09 23 OPT 1FR EMR 0 NRML SLUS RTP 0 CND CNAM CLGS

6.3 APmax TM Configuration6.3.1 Package Deployment

APmax packages contain the tables and files necessary to provision features for APmax systems.

When a package is deployed, the contents of the package are copied to the appropriate locations

on the system. Depending on the type of APmax TM system configuration specified or the particular application(s) purchased with the system the software may be pre-loaded.

If the service packages have not been installed, reference the APmax TM User Manual for information on Package Management including how to deploy packages to your system or contact Innovative Systems Support.

6.3.2 Call Logging Portal SettingsFrom the APmax TM UI, right-click on the system icon in the Command Center window to invoke a popup menu, and select the System Configuration | Call Logging Portal Settings. For more information on the Call Logging Portal Settings add-on, refer to the Call Logging Portal Service Description.

6.3.2.1Verify the Listen Port is the same as the Port previously configured on the switch.

Figure 6-1 Call Logging Portal Settings

6.3.2.2The File Process Time is the time of day the call logs will be sent to the subscribers.


6. Call Logging Portal 75

6.3.2.3Close the window.

6.3.3 Subscriber ManagementPlease refer to the Call Logging Portal Service Description for information regarding entrance of new subscribers and subscriber management. Please refer to the APmax User Manual for information regarding configuration of Internet Access Settings and Phone Central.


76 6. Call Logging Portal

6.4 Call Logging Portal Configuration Sheet6.4.1

Address:____________________

6.4.2Port:____________


7. Screen Pop 77

7. Screen Pop

7.1 General DescriptionThe Screen Pop feature is an extension to the Calling Name Delivery Database Service that allows Caller ID information to be sent to middleware devices for display on the televisions of subscribers. If the subscriber uses the Phone Central Caller ID feature, see the Calling Name Service Description for more information, a message is sent to the Phone Central update system.

This service will provide the mechanism for video system operators to provide Caller ID information on subscriber’s television screens and web portal accounts. In addition, normal Caller ID information will be provided to the subscriber’s telephone.

This chapter will assist in the switch setup for the Screen Pop Service. Areas of coverage in this chapter will be setup of AIN and station provisioning. This chapter assumes that the SS7 links and Calling Name Delivery have already been setup between the switch and the APmax TM and are functioning.

7.2 Switch Setup7.2.1 Service Logic Host Route (SLHR)

Each AIN service is assigned a Service Logic Host Route. The SLHR is created in OVLY AIN. Record the SLHR number and TRN1 on the configuration sheet at the end of this chapter.

OVLY AIN REQ NEW SLHR SLHR 3 Number of the SLHR GTT1 010 008 001 The Point Code of the APmax™ TRN1 182 This is the Translation Table to be used by the GTT1

node to obtain SCCP routing information. GTT2 NONE GTSC CLED Source of the GTT info that is sent to the STP to route

the message to an SCP application. SRCE is used with originating services.

7.2.2 Administrative State CodeIt is necessary to set the AIN triggers specific to the Screen Pop Service. Screen Pop uses the Termination Attempt (TA) trigger. The TA trigger is assigned in the Administrative State Code (ADSC) SLHR for the Screen Pop Service. SLHR must be set to ON.

OVLY AIN


78 7. Screen Pop

7.2.3 Directory Number ProvisioningThe Single Number subscriber’s DN must have the TA trigger assigned to it (OVLY DN - ADO) in order to route the call to the service to begin the Single Number Service. The AIN option TA CFWY 5 will be added to the subscriber’s station.

STN DN 996 1004 LOC IS LCE 01 1 08 04 OPT LSC 1FR EMR 0 NRML RTP 0 PRES 0288 CFB CFD CND CNAM TA CFWY 3






7.3.1.1 Calling Name Configuration7.3.1.1.1From the APmax TM UI, right-click on the system’s icon in the Command Center window to invoke a popup menu, and select the System Configuration

REQ CHG TYP ADSC SLHR 3 OHI OFF OHD OFF SIT OFF FCD OFF CDP OFF DIG OFF N11 OFF TA ON LNP OFF


7. Screen Pop 79

| Calling Names command. For more information on the Calling Names window, refer to the Calling Name Service Description.

7.3.1.1.2In the Configuration tab set Video Screen Pop Allowed to “Yes” so calling names can be delivered using the Video Screen Pop feature.

7.3.1.1.3Select the Screen Pop tab. Enter the SSN. Close the window.

7.3.1.1.4To complete configuration of the service, Subscriber Mapping, NPA-NXXs, and IP Delivery Servers must be added. Internet Access must be setup on the APmax TM and web portal installed on the subscriber’s PC. Please reference the Calling Name Service Description for further information regarding the Calling Name add-ons. Please reference the APmax User Manual for information regarding Internet Access and web portal. Click Add.

7.3.1.2 Global Title Translations7.3.1.2.1From the APmax TM UI, right-click on the system’s icon in the Command Center window to invoke a popup menu, and select the System Configuration | SS7 Configuration command. Select the Global Title Translation tab.

7.3.1.2.2Under Global Title Table, enter the Map Number, Global Address (an entry must be made for each NPANXX or thousands group), Function Selector, Primary Route (point code of the APmax TM i.e. Local Point Code), and Alternate Route if applicable.

7.3.1.2.3Under Translation Type Table, enter the Translation Type (set to the same value as the SSN- in our example this is 182), Subsystem Number (set to the same value as the SSN- in our example this is 182), Map Number (use the Map Number configured under Global Title Table), and Expansion Route if applicable.

7.3.1.2.4Close the window to save all changes.

7.3.2 Subscriber ManagementPlease refer to the Calling Name Service Description for information regarding entrance of new subscribers and subscriber management. Please refer to the APmax User Manual for information regarding configuration of Internet Access Settings and web portal.


80 7. Screen Pop

7.4 Screen Pop Configuration Sheet7.4.1 AIN

7.4.1.1SLHR: ___________

7.4.1.2SSN (TRN1):___________


8. Announcements 81

8. Announcements

8.1 General DescriptionThe APmax TM supports STD/CLASS, ANA, CNA, and AIN announcements. To ease configuration, the APmax TM comes preconfigured from the factory to provide STD/CLASS, ANA, and CNA announcments. For most telephone companies, this configuration will be adequate. In most cases when the APmax TM is replacing an existing announcement machine, this configuration provides a compatible replacement that works with the existing switch configuration. Table 1 shows the default configuration of the APmax TM. See the C15 Announcements Service Description for further information regarding this service and the APmax TM.

The default trunk settings apply to both units and are as follows:

Table 8-1

DS1 Number

DS1

Channels

Trunk Group

Service Annc. Number Length

KP Digit ST Digit

1 2-9 1 Std/CLASS

3 NONE ST2P

1 2-9 1 AIN 5 KP ST

1 10-11 2 CNA 3 KP ST

1 12 3 ANA 3 KP ST

Default Trunk Settings

The APmax TM has three trunk groups assigned in the default configuration. These trunk groups span both units to provide redundant announcements. Std/CLASS announcements and AIN announcements should share a trunk group to more efficiently utilize the resources available. The default configuration has DS1 1 on each unit set to Enabled. Channel 1 in each DS1 has been reserved for SS7. The Number of Repeats for STD/CLASS is defaulted to 0. The Number of Repeats for ANA and CNA is defaulted to 2. The Number of Repeats for AIN is defaulted to 1. The default CNA announcement is 406, “We're sorry, you have reached a number that has been disconnected or is no longer in service. If you feel you have reached this recording in error, please check the number and try your call again.”

8.2 Trunk GroupsTo properly configure the C15 for announcements, three trunk groups must be configured. From the switch, trunk groups are defined in OVLY TG.


82 8. Announcements

8.2.1 DS1 ConfigurationThe DS1s connected to the APmax TM will be similar to the following, with the settings in bold that have to match your DS1s. From OVLY NET.

DS1 (NT6T08) IS 01 2 12APPL DTRKDSNM APMax 2013LICD AMIINBS YESSYNC NOFRFM SFDIST 110SLPM 40SLPO 255BPVM -6BPVO -3FRLM 3FRLO 255ADC1 1PRAT 56ADC2 UNAS

8.2.2 STD/CLASS Trunk GroupThe Trunk Group used by the CLASS Announcements is defined in OVLY CNFG. You can view this by:

REQ QUE CLAS

CLAS CATG 1006 APMAX 2013 STD CLASS#TO 3#ERR 2FLSH NOCOT2 NOCOTO 7 SECEDIT 2CLIC ANNCACRC CFRMACRT NUMBGTT1 010 008 001TRN1 251GTT2 NONE


8. Announcements 83

The following is a common configuration for the STD/CLASS Trunk Group. Note that the actual TG number may be different in your configuration.

TYP TGNUM 1006TGTP OUTTGNM APMAX 2013 STD CLASSMG NOMOH NOSIGT INB64NC NOPKTP DTRKSITE BASEESB NOTGDP ELOCRMB YESSTPL WINKTRNS MFSDTM 5 SECGDTI 128 MSECIDLE MOSTDTSI 0SYNC NOTRFC NONEANI NOEOAT NOATIC NOHIT 8 SEC4XCD NOTGMU NO

Note: Trunks will be assigned in section 8.5 - Trunks.


84 8. Announcements

8.2.3 CNA Trunk GroupThe following is a common configuration for the CNA Trunk Group. Note that the actual TG number may be different in your configuration.

TYP TGNUM 1007TGTP OUTTGNM APMAX 2013 CNAMG NOMOH NOSIGT INB64NC NOPKTP DTRKSITE BASEESB NOTGDP ELOCRMB YESSTPL WINKTRNS MFSDTM 5 SECGDTI 256 MSECIDLE MOSTDTSI 0SYNC NOTRFC NONEANI NOEOAT NOATIC NOHIT 768 MSEC4XCD NOTGMU NO



8. Announcements 85

8.2.4 ANA Trunk GroupThe following is a common configuration for the ANA Trunk Group. Note that the actual TG number may be different in your configuration.

TYP TGNUM 1008TGTP OUTTGNM APMAX 2013 ANAMG NOMOH NOSIGT INB64NC NOPKTP DTRKSITE BASEESB NOTGDP ELOCRMB YESSTPL WINKTRNS MFSDTM 5 SECGDTI 256 MSECIDLE MOSTDTSI 0SYNC NOTRFC NONEANI YESASTR OFHKATMO DROP2RID NOEOAT NOATIC NOHIT 8 SEC4XCD NOTGMU NO


8.3 RoutesTo properly configure the C15 for announcements, routes must be defined for CNA, ANA, and VDRA announcements. Routes are defined in OVLY ROUT.

8.3.1 CNA RouteThe following is a common configuration for the CNA route. Note that the actual route number may be different in your configuration.


86 8. Announcements

ROUT 1007ALTR OVFLTYPE EASRTNM APMAX 2013 CNAUPGR NONECTYP NONELNPB NOTG 1007 APMAX 2013 CNACHG NOOPR NOSDCN NOCOCOS NONEDEL 0APFX NONECNTL ETHROVLP NOPGNC YES

CNA TG Number

8.3.2 ANA RouteThe following is a common configuration for the ANA route. Note that the actual route number may be different in your configuration.

ROUT 1008ALTR BUSYTYPE TSPSRTNM APMAX 2013 ANAUPGR NONECTYP NONETG 1008 APMAX 2013 ANACHG YESOPR NOSDCN NOCOCOS NONEDEL 0APFX NONEKCLD KPSCLD STKCLG KPSCLG ST#ANI 1ID 6CNTL ETHROVLP NOHNPA NO

CNA TG Number


8. Announcements 87

8.3.3 VDRA RoutesThe following is a list of common VDRA routes.

Note: The route numbers, trunk group numbers and/or message numbers may be different in your configuration.

Table 8-2

ROUT 401ALTR OVFL TYPE VDRA STRT NONERTNM UNASSTOP ST2PMSG 401 TG 1006DTSI 0 CHG NO CNT 2 TIME OVFL

ROUT 402 ALTR OVFL TYPE VDRA STRT NONERTNM UNASSTOP ST2PMSG 402 TG 1006 DTSI 0 CHG NO CNT 2 TIME OVFL

ROUT 403 ALTR OVFL TYPE VDRA STRT NONERTNM UNASSTOP ST2PMSG 403 TG 1006DTSI 0 CHG NO CNT 2 TIME OVFL


















VDRA Routes

8.4 Generic ConditionsTo properly configure the C15 for announcements, the appropriate actions should be defined for each generic condition requiring an announcement. Generic conditions are defined in OVLY CNFG (GCON).


88 8. Announcements

8.4.1 CNA Generic conditionTo properly configure CNA the generic conditions DNIC and DNCH should be configured to use the CNA route. Note that route numbers may be different in your configuration.

DNIC 1007 DNCH 1007

8.4.2 Generic conditions that use a VDRAMany generic conditions can be sent to a VDRA route. The following are examples of some GCONs that are sent to VDRA routes. Note that the actual route numbers may be different in your configuration.

PRDI 406BDIG 403PMSG 404N11R 411VCCO 407VCDN 406ZERR 411NOCO 410DTTO 404RGTO 404REV1 415DNT 407IRST 411950R 411TSUS 406IWTD 407DACK 407DLER 405DDST 40710XX 412AD1I 411IRAI 412IERI 421INLI 412950I 412CARF 413FGAR 411VCXX 412SCR 416CLAS 417FGBR 412FNAL 418ACRJ 419AINF 417


8. Announcements 89

8.5 TrunksOnce the trunk groups are configured and routes are set up, trunks need to be added to the trunk groups. This is done in OVLY TRK. Below is an example of the trunks configured for STD/CLASS, CNA, and ANA.

Table 8-3

DTRK IS 2 01 2 12 02 TKTP OUT TG 1006 APMAX 2013

STD CLASSCG NONE


STD CLASSCG NONE


STD CLASSCG NONE


STD CLASSCG NONE


STD CLASSCG NONE


STD CLASSCG NONE


STD CLASSCG NONE


STD CLASSCG NONE

DTRK IS 2 01 2 12 10TKTP OUT TG 1007 APMAX 2013 CNACG NONE

DTRK IS 2 01 2 12 11TKTP OUT TG 1007 APMAX 2013 CNACG NONE

DTRK IS 2 01 2 12 12TKTP OUT TG 1008 APMAX 2013 ANACG NONE

Trunk Configuration

8.6 STD/CLASS Tandem Announcement SetupThe APmax may be shared as an STD/CLASS announcement system for C15 switches within the telephone company’s network. In order to achieve this, the SSO and the HSO must be configured to tandem the trunks.

Verify setup of the CRTM entry in OVLY CNFG in the HSO.

OVLY CNFG DSCT 4 SEC

Set to four seconds or more.


90 8. Announcements

Figure 8-1


8. Announcements 91

8.6.1 SSO Trunk Group SetupThe SSO trunk group is a outgoing trunk group. The following is the trunk group setup for the SSO:

OVLY TGREQ NEWTYP TGNUM 1006TGTP OUTSIGT INB64NC NOPKTP DTRKSITE BASETGDP ELOCRMB YESSTPL IMDITRNS MFSDTM 768 MSECGDTI 768 MSECIDLE MOSTDTSI 0SYNC NOANI NOEOAT NOATIC NOHIT 10 SEC4XCD NO

8.6.2 HSO Tandem Setup8.6.2.1 Incoming Trunk GroupAn incoming trunk group must be configured in the HSO. This will get the information into the HSO. The configuration of the trunk group will allow for


92 8. Announcements

routing the requested announcement to the APmax. The following is the setup of the incoming trunk group:

TYP TGNUM 71TGTP INCSIGT INBPKTP DTRKSITE BASETGDP ELOCRMB YESFLSH NOSTPL NODGCOIN NOCOSTSI 0HNPA 515RC 7RTP 0CNTL ETHRVERT NOTRNL PRFXPRFX 15APFX NONETRFC NONE4XCD NOACKA NOLATA 632BCAP 3AUTGID NONETNDM NO

Area specfic NPA PRFX will be configured in the next step.

8.6.2.2 Routing Announcement Request to APmaxThe incoming trunk group identified the request to go to PRFX 15. Configuring the PRFX translator which will select the rout to the APmax.

OVLY TRNSQUE PRFX 15

ORIG PRFX 15 ACTV TIME N/APRFX 15 BRTE 499


8. Announcements 93

8.6.2.3 Route to APmaxSetup the route for the announcement request to get to the APmax.

OVLY ROUT REQ NEW ROUT ROUT 499 ALTR OVFL TYPE ICP UPGR NONE CYTP NONE TG 1006 DTSI 0 CHG YES OPR NO SDCN NOCO COS NONE RGBK NO CNTL ETHR PGNC NO

8.6.2.4 Trunk Group Outgoing to APmaxThis is the trunk group determined earlier for STD/CLASS announcements (see section 8.2.2 - STD/CLASS Trunk Group).


94 8. Announcements

OVLY TGTYP TGNUM 1006TGTP OUTTGNM APMAX 2013 STD CLASSMG NOMOH NOSIGT INB64NC NOPKTP DTRKSITE BASEESB NOTGDP ELOCRMB YESSTPL WINKTRNS MFSDTM 5 SECGDTI 128 MSECIDLE MOSTDTSI 0SYNC NOTRFC NONEANI NOEOAT NOATIC NOHIT 8 SEC4XCD NOTGMU NO

8.7 Hunt Group QueuingHunt Groups now have the option to implement queues. If provisioned, customers calling a busy hunt group will be put in a queue where they will hear a combination of announcements and music while waiting for an idle hunt group member. Ringback and silence may be substituted for music. The GUI was enhanced to support Hunt Group provisioning (see SOP 0259 for provisioning instructions).

297-3102-311P21 SOP 0259

8.7.1 Configure Queuing for a Directory Number Hunt (DNH) group Source ActionCNFG (FEAT) Verify that Hunt Group Queuing is configured.

SOP 0090 If required, assign trunks and trunk groups to be used for the first and second Hunt Group Queuing announcements.


8. Announcements 95

Note: Ensure the VDRA unit has the latest announcement set which includes the Hunt Group Queuing announcements (078 and 079).

Note: This is from the NTP. I think it should be announcements 077 and 078.

SOP 0212 If Music on Hold (MOH) is desired, assign trunks and trunk groups to be used for MOH. HUNT (DNH) Define the DNH group with QUEU = YES using OAMP HUNT or CS1500 GUI.

(Ref. C15 Online Help Guide for Directory Number Hunt Groups).

8.7.2 297-3102-105 Hunt Group QueuingNormally only one pass through the hunt group is made, and if an idle member is not found, the incoming call is routed to the defined overflow treatment for the group. The Hunt Group Queuing feature allows an incoming call to a busy hunt group to be placed in waiting queue. While enqueued, the caller receives an alternating Vendor Digital Recorded Announcement (VDRA) and Music on Hold (MOH) or tone in the following sequence:

1. An initial VDRA announcement informing the caller that all attendants are busy and that the customer should wait on the line for the next available attendant.

2. MOH, ringback tone, or comfort noise (TDM lines)/silence (VoIP lines) for a configurable time period.

3. A "reminder" announcement asking the caller to continue holding.

4. Alternate between (2) and (3) until the call is answered or the caller hangs up.

When a hunt group member becomes idle, the enqueued call re-hunts the group. If an idle hunt group member is found, the caller is removed from the hunt group queue and receives ringback tone. If an idle member is not found, the call remains enqueued for another cycle. The call continues to re-hunt in this manner until the call successfully terminates to an idle hunt group member or the caller goes on-hook.

Hunt Group Queuing can also be used for calls that would normally overflow from the CFGDA NEXT feature. If up to five idle hunt group members with Call Forward Don’t Answer (CFD) activated have been hunted and CFD ringing timeouts have occurred on each one, the call may be queued instead of overflowed, if configured in OAMP HUNT (DNH).

Calls may be transferred to a hunt group queue using the switch-based UTF (User Transfer) or SIP client-based call transfer functionality. When a call is transferred to a hunt group queue using UTF, any in-queue treatment


96 8. Announcements

(announcement, music, or tone) currently being delivered to the party performing the UTF is transferred in progress to the transferee. For a SIP attended transfer to a hunt group queue; however, at the time of the transfer, the original call is removed from the queue and the transferred call is re-queued, due to SIP transfer functionality. In this case, the transferee always receives in-queue treatment beginning with the initial VDRA announcement.

8.7.3 CNFG (FEAT) Note: (Note: Hunt Group Queuing is an available feature)

# OVLY CNFGDMO000 CNFGREQ que featFEATLTA NO MTST YESFEATURE MAX CURRVOIP STATIONS: 00100 00024VOIP TRUNKS: 00100 00000kVOIP CENTREX LINES: 00100 00000HUNT GROUP QUEUES: 00020 00001REQ

8.7.4 297-3102-311P2 Hunt (DNH)QUEU Prompted if REQ = NEW or CHG and hunt group queues have been acquired for the office. Asks if this hunt group enqueues waiting calls until an idle group member can be found.

YES Waiting calls are enqueued.

NO Waiting calls are not enqueued.

Note: If QUEU has previously been set to YES, it can only be changed to NO if no calls are currently in the queue.

MAXQ Prompted if QUEU = YES. Asks for the maximum number of calls that may be enqueued while waiting far an idle hunt group member. Calls reaching a busy hunt group beyond this maximum are handled as specified by the OVFL setting (n(nn) 2 to 255 calls).

Note: It is recommended that MAXQ be set to approximately the same size as the hunt group as an initial setting.

Note: If MAXQ is decreased below the number of calls currently in the queue, calls remain in the queue until they have been processed or abandoned, but no new calls are added to the queue until the number of calls in the queue decreases below the new MAXQ size.


8. Announcements 97

Table 8-4

RATG Prompted if QUEU= YES Identifies a previously defined outgoing Vendor Digital Recorded Announcement (VDRA) trunk group to provide announcements for waiting calls enqueued for the hunt group. n(nnn) 1 to 2047

ANN1 Prompted if QUEU = YES Identifies the initial VDRA announcement number provided to waiting calls enqueued for the hunt group. n(nnnn) 0 through 9 for 1-digit message numbers; 00 through 99 for 2-digit message numbers; 000 through 999 for 3-digit message numbers; 0000 through 9999 for 4-digit message numbers; 00000 through 99999 for 5- digit message numbers.

ANN2 Prompted if QUEU = YES Identifies the "reminder" (continuation) VDRA announcement number provided to waiting calls enqueued for the hunt group. n(nnnn) 0 through 9 for 1-digit message numbers; 00 through 99 for 2-digit message numbers; 000 through 999 for 3-digit message numbers; 0000 through 9999 for 4-digit message numbers; 00000 through 99999 for 5- digit message numbers.

IATM Prompted if QUEU = YES Asks for the inter-announcement interval in seconds (n(nn) 2 through 150 seconds).

STRT Prompted if QUEU = YES Asks for the start signal to be outpulsed to the VDRA unit prior to outpulsing the announcement identifier.

KP

KPP

KP2P

KP3P

NONE No start signal.


98 8. Announcements

STOP Prompted if QUEU = YES Asks for the stop signal to be outpulsed to the VDRA unit after outpulsing the announcement identifier.

ST

STP

ST2P

ST3P

NONE No stop signal.

MOH Prompted if QUEU = YES Identifies the digital trunk to serve as the Music on Hold music source for any waiting calls enqueued for the hunt group. (site) pm pc p c Location of the trunk circuit providing MOH. RGBK Ringback tone is provided to enqueued callers in lieu of MOH. NONE Comfort noise is provided to TDM enqueued callers in lieu of MOH. VOIP devices will receive quiet from the C15.


8. Announcements 99

8.8 CNA/ANA Tandem Announcements SetupThe APmax may also be used to share the Change Number Announcements (CNA) and the Automatic Number Announcement (ANA) for C15 switches with the telephone company’s network. In order to achieve this, the SSO and the HSO must be configured to tandem the trunks to deliver them from the APmax to the HSO, to the SSO.

These two announcement sets are going to be configured in a similar manner to get from the SSO to the HSO. An APFX will be added to the request to identify it with the corresponding service. Once the request has made it to the HSO, then the they will be steered toward their respective trunk group to deliver the announcement.

8.8.1 Flow of the CNA/ANA Tandem Announcement SetupIn the SSO, send the CNA and the ANA to a route in order to reach the TG. This route setup will add an APFX to the flow that will be used at the HSO to identify what announcement is being requested.

8.8.1.1 SSO configuration for CNA

OVLY CNFG>>GCONSDS1 IS 01 2 12 01T1 14 SECT2 11 SECT3 11 SECT4 2300 MSECT5 100 MSECT6 7 SECT7 2500 MSECAPFX 035 This will identify the call as a CNA. This will

be screened in the HSO in a PRFX translator.

ID DFLTFANI NOPGNC NO

8.8.1.2 SSO Configuration for ANA

OVLY DN ICP DN 996 9000ICPT ROUTROUT 243


100 8. Announcements

8.8.1.3 TG Configuration in the SSOThe trunk group for the CNA and the ANA announcement is an EAS TG that may also be used for tandeming the voice mail announcements to the HSO. If using the Innovative Systems voice mail system, then voice mail can be routed to the same trunk group to get to the HSO.

OVLY ROUT NEW ROUT 243ALTR OVFLTYPE ISUPUPGR IEASCTYP NONETG 246CHG NOCOS NONEDEL 0APFX 036 This will identify the call as a ANA. This will

be screened in the HSO in a PRFX translator.

ID DFLTFANI NOPGNC NO

OVLY TG NUM 246TGTP 2WAYBDRT 56DPC xxx xxx xxx This is the HSO Point Code.INBS YESAUUS NOAATP NOPKTP DTRKSITE BASETGDP ELOCCNFS YESITXF 1780IRXF 2010COIN NOCOSTSI 0HNPA 605RC 0RTP 0CNTL CLNGVERF NOTRNL PRFX


8. Announcements 101

The configuration in the SSO is completed.

8.8.2 HSO Configuration for the CNA/ANA Tandem AnnouncementsSince the HSO has its own configuration for the CNA and the ANA announcements, the information coming from the SSO will need to be directed to the same route and trunk groups that the HSO is using for these announcements.

PRFX 6ADDR HNPAAPFX NONETRFC NONE4XCD NOACKA NOLATA 000TNS YESTGID NONEUNUM RELNCKT RELCONG RELNORT RELTMPF RELNRSC RELDNCH RELDOOO RELCREJ RELPERR RELOTXF 2010ORXF 1780CINT 10GDTI 768 MSECGLAR DFLTIDLE MOSTDTSI 0SYNC NO2RID NOEOAT NOATIC NO4XCD NOHOPI NOCIP NOBCAP DFLTOCNP NORNP NORIP NOCHNP NO



8.8.2.1 HSO 2-Way ISUP TG from the SSO

OVLY TG NUM 246TGTP 2WAYSIGT 56BDRT 56DPC XXX XXX XXX This is the point code of the SSO.INBS YESAUUS NOAATP NOPKTP DTRKSITE BASETGDP ELOCCNFS YESITXF 1780IRXF 2010COIN NOCOSTSI 0HNPA 515RC 7RTP 0CNTL CLNGRTP 0CNTL CLNGTRNL PRFXPRFX 6 This is the screen where the call will

checked to see what prefix we added to the from of this call.

APFX NONETRFC NONE4XCD NOACKA NOLATA 000TNS YESTGID NONETNDM NOUNUM RELNCKT RELCONG RELNORT RELTMPF RELNRSC RELDNCH RELDOOO RELCREJ REL



8.8.2.2 PRFX 6

OVLY TRNLPRFX 6 DIG 0 DIG 3 DIG 5 ABS 3 ROUT 245 CNA PRFX from SSOPRFX 6 DIG 0 DIG 3 DIG 6 ABS 3 ROUT 244 ANA PRFX from SSO

8.8.2.3 CNA and ANA Routes in the HSO

PERR RELXRER RELBUSY RELOTXF 1780ORXF 2010CINT 10GDTI 768 MSECGLAR DFLTIDLE MOSTSYNC NOTRFC NONE2RID NOEOAT NOATIC NO4XCD NOHOPI NOCIP NOBCAP DFLTOCNP NORNP NORIP NOCHNP NO

OVLY ROUT (CNA)ROUT 245ALTR OVLYTYPE EASUPGR NONECTYP NONETG 245DTSI 0CHG NOOPR NOSDCN NOCOCOS NONEDEL 0



8.8.2.4 CNA and ANA Trunk Groups in the HSO

APFX NONECNTL ETHROVLP NOPGNC NO

OVLY ROUT (ANA)ROUT 244ALTR OVLYTYPE TSPSUPGR NONECTYP NONETG 244DTSI 0CHG NOOPR NOSDCN NOCOCOS NONEDEL 0APFX NONEKCLD KPSCLD STKCLG KPSCLG ST#ANI 1CNTL ETHROVLP NOHNPA YES

OVLY TG (CNA)TYP TGNUM 245TGTP OUTSIGT INB64NC NOPKTP DTRKSITE BASETGDP ELOCRMB YESSTPL WINKTRNS MFSDTM 5 SECGDTI 768 MSECIDLE MOST



DTSI 11SYNC NOANI NOEOAT NOATIC NOHI 5 SEC4XCD NO

OVLY TG (ANA)TYP TGNUM 244TGTP OUTSIGT INB64NC NOPKTP DTRKSITE BASETGDP ELOCRMB YESSTPL WINKTRNS MFSDTM 1024 MSECGDTI 256 MSECIDLE MOSTDTSI 11SYNC NOANI YESASTR OFHKATMO DROP2RID NOEOAT NOATIC NOHIT 5 SEC4XCD NO




9. Calling Name Delivery 107

9. Calling Name Delivery

9.1 General DescriptionThe APmax TM can be configured to function as a calling name database. This chapter assumes that the SS7 links to the APmax TM are setup and functioning.

A configuration sheet has been provided at the end of this chapter and should be used as an aid in keeping track of the required information. The following information will be retrieved and recorded:

• The translation table number and subsystem number for Calling Name

• The expansion GTT point codes for Calling Name (if required)

9.2 Switch SetupThe settings in the C15 that affect calling name delivery are outlined. The examples used here may not exactly match the settings in your switch.

If the C15 has previously been provisioned for one or more of the features provided by the APmax TM, the following process may be used to determine the specific values for your configuration. Some of the items listed in the following examples may not be present in the C15. If this is the case, see the applicable chapter that details provisioning and configuration for the feature or service.

9.2.1 Feature BitsThe CNAM feature bit must be turned on in order for to assign the CNAM option to a phone. If the CNAM feature is not an available option please contact Genband so the feature can be enabled on your switch.

9.2.2 Display SettingsThe DISP option on OVLY CNFG must be configured for your switch. The Translation Type should match the APmax TM.

OVLY CNFG - DISPDISPNQTM 6UNCH NOILAT YESBQPN YESGTT1 010 008 001 Asks for the Point Code of the Global Title

Translator. This should be set to the PC of the APmax TM.


108 9. Calling Name Delivery

Write the CNAM TT on the configuration sheet.

9.2.3 Sub System NumberThe Subsystem number for CNAM in the switch must match what is in the APmax TM.

OVLY CNFG - SUBCNAM 232

Write the CNAM SSN on the configuration sheet.

9.3 Entering Service DataThis section describes how to provision the APmax TM so that it can properly translate received SS7 messages that require GTT. See the APmax TM User Manual for more information on configuring GTT on the APmax TM.

9.3.1 Access ControlThe switches, that may dip the APmax TM for calling name information must be defined in the APmax TM. The APmax TM UI can be used to enter the data. A short summary of the process is given here. For more information, see the APmax TM User Manual and the Calling Name Service Description.

9.3.1.1 Calling Name Configuration9.3.1.1.1From the APmax TM UI, right-click on the system’s icon in the Command Center window to invoke a popup menu, and select the System Configuration | Calling Names command. For more information on the Calling Names window, refer to the Calling Name Service Description.

9.3.1.1.2In the Configuration tab, SSN, enter the SSN See the configuration sheet at the end of this chapter for the SSN value to use.

TRN1 5 Asks for the Translations Type to be sent to the Global Title Translator. This is normally 5.

GTT2 NONEDBAS LOCLGTC1 NONEGTL1 NONEARD "AUTOMATIC RECALL"ACBD "AUTOMATIC CALL BACK"MBSD YESCANA NO



9.3.1.1.3Click Add. Enter the Point Code Originating Point Code of the switch originating the calling name lookup. This OPC can be specified to the network, cluster, or member level.

9.3.1.1.4Select the Expansion Type to be used. Set to “Targus” if lookups through TARGUSinfo links are allowed. Set to “SS7” if SS7 Expansion is allowed. Set to “No” if neither TARGUSinfo lookups or SS7 Expansion is allowed.

9.3.1.1.5Set City/State Expansion Allowed to “Yes” if lookups through the APmax TM’s City/State system are allowed. Set to “No” if lookups through the APmax TM’s City/State system are not allowed.

9.3.1.1.6Set Video Screen Pop Allowed to “Yes” if calling names will be delivered using the Video Screen Pop feature. See Chapter 7. - "Screen Pop" for further information on how to configure this feature. Be advised, if either this or Return IP to APmax TM is set to “Yes” then responses will be sent back to the APmax TM.

9.3.1.1.7Set Return IP to APmax TM “Yes” if the expansion responses should be sent back to the APmax TM which will forward the response to the switch. Set to “No” if the expansion responses should be sent directly to an APmax TM or the switch over the SS7 network.

9.3.1.1.8The Name Not Found Action is the action to take when a calling number is not found in the APmax’s local calling name database. The choices for this action are listed below:



Table 9-1

Return Error Return an error to the requesting switch.

Extended Lookup

(No Error)

Do an extended calling name lookup through one of the APmax’s extended lookup mechanisms (i.e., TARGUSinfo links or City/State) and do not log an error.

Extended Lookup (Log Error)

Do an extended calling name lookup through one of the APmax’s extended lookup mechanisms (i.e., TARGUSinfo links or City/State) and do not log an error.

System Default Use the system default “Name Not Found” action.

9.3.1.1.9The SS7 Expansion Point Code is the expansion point code that will be used if lookups through an expansion point code are enabled for this OPC. This field will be disabled if the Expansion Type is not set to SS7. Note: If SS7 Expansion will be used a route to the destination point code (usually the APmax TM) must be added, see Section 2.2.2.6 - "SS7 Configuration" or the APmax TM User Manual for information on adding routes.

9.3.1.1.10The SS7 Translation Type is the translation type that will be used if lookups through an expansion point code are enabled for this OPC. This field will be disabled if the Expansion Type is not set to SS7.

9.3.1.1.11At the lower left corner of the window, Restrict Calling Name Database Access. This selection box may be set to Yes or No. If it is set to Yes, it means that only switches with point codes listed in the OPC list will be allowed to access the APmax’s calling name subsystem. Requests from any other switch (originating point code) will be rejected with an error indication. If the selection box is set to No, any switch can access the APmax’s calling name subsystem regardless of whether or not the switch’s point code is in the OPC list. Requests from switches with point codes not in the OPC list will attempt a lookup using the City/State system (other extended lookup systems are disabled) if the name is not found.

9.3.1.1.12Close the window.



9.3.1.2 Global Title TranslationsIf SS7 Expansion will be used a GTT entry with the Primary Route set to the expansion point code/route must be added.

9.3.1.2.1From the APmax TM UI, right-click on the system’s icon in the Command Center window to invoke a popup menu, and select the System Configuration | SS7 Configuration command. Select the Global Title Translation tab.

9.3.1.2.2Under Global Title Table, enter the Map Number, Global Address (an entry must be made for each NPANXX or thousands group), Function Selector, Primary Route (point code of the APmax TM i.e. Local Point Code), and Alternate Route if applicable. The point code should be provided by the SS7 provider.

9.3.1.2.3Under Translation Type Table, enter the Translation Type (normally 5), Subsystem Number (normally 232), Map Number (use the Map Number configured under Global Title Table), and set the Expansion Route (point code of the APmax TM i.e. Local Point Code).


9.3.2 Enter Calling Name informationUse the APmax TM UI to import a list of calling names or enter single calling names. A short summary of this process is provided here. See the Calling Name Service Description for additional information.

9.3.2.1From the APmax TM UI, right-click on the system’s icon in the Command Center window to invoke a popup menu, and select the System Configuration | Calling Names command.

9.3.2.2Select the Calling Names tab. Click Add to add a single calling name.

9.3.2.3Click Import to import a file containing calling names. The required input file format is outlined in the Calling Names Service Description.



9.4 Calling Name Configuration Sheet9.4.1

Calling Name Subsystem Number: _________

9.4.2Calling Name Translation Table Number: _______

9.4.3Point Code for NAME Expansion GTT 1: ________ - ________ - ________

9.4.4Point Code for NAME Expansion GTT 2: ________ - ________ - ________


10. Voice Mail/Unified Messaging 113

10. Voice Mail/Unified Messaging

10.1 General DescriptionThis is a Voice Mail/Unified Messaging Service for residential and small business subscribers. It provides voicemail functionality with the ability to record custom greetings, multiple voice mailboxes per line, Internet delivery of voicemail messages (optional), time zone settings for each subscriber, pager or cell phone notification of new messages, reply to messages, and sending or forwarding messages to a mailbox or distribution list.

The service utilizes the forward on busy and forward on no answer features of the telephone switch to route incoming calls to the APmax TM over an ISUP trunk group. If Simplified Message Desk Interface (SMDI) is available, the service has the ability to turn on and off the Message Waiting Indication (MWI) for the customer. In addition, the service can optionally provide MWI over SS7 and e-mail delivery of Voice Mail messages. The service may be configured on a customer-by-customer basis to share a voice mailbox among multiple stations or to have multiple voice mailboxes attached to a common directory number (DN). The service supports Spanish or English prompts on a subscriber-by-subscriber basis.

This chapter will assist in the switch setup for the Voice Mail/Unified Messaging Service. Areas of coverage in this chapter include:

• Section 10.2 - Call Flow

• Section 10.3 - Switch Setup

• Section 10.4 - APmax TM Configuration

• Section 10.5 - Voice Mail Configuration Sheet

This chapter assumes that the DS1s and SS7 links have already been setup between the switch and the APmax TM and are functioning properly.

10.2 Call FlowFigure 10-1 Voice Mail/Unified Messaging Call Flow


114 10. Voice Mail/Unified Messaging


Note: If the following feature options are not available options please contact Genband so the feature(s) can be enabled on your switch.

Feature bits that are required for Voice Mail are as follows:

MDSI YES Enables SMDI over Signaling System 7 (SS7)CFBD YES Enables Call Forward Busy Don’t AnswerISUP YES ISUP capabilities are required

The following feature bits are optional.

MWIL YES Message Waiting Indicator LightMDT YES Enables Teen Line with Voice Mail

10.3.2 System ConfigurationAt the end of the Voice Mail message, the message information is given to the subscriber. The message information includes the time, date, and the ten digit number from the caller. The following system configuration is required for this ten digit number to be available for the Voice Mail/Unified Messaging Service.

OVLY CNFG - SYS CFPR NO Call Forward Privacy must be set to NO

10.3.3 Message Waiting IndicationThe APmax TM supports the message waiting indicator light and the message waiting stutter dial tone. There are two options in which to provide these features. The APmax TM can activate these features on the switch either over a Serial Data Interface, or over SS7 interface. When configuring SMDI with the C15, the SS7 interface will be utilized.

10.3.3.1 SMDI over SS7As previously noted, in order to provide SMDI over SS7, the feature bit MDSI must be turned on. To configure the Message Storage and Retrieval for the switch, enter the following and record the values on the configuration sheet.

OVLY CNFG REQ NEW MSR MSR 1 Asks for the MSR index number MDID 0000000000 Asks for the message storage and retrieval ID MDDN 6059966245 Asks for the MSR switch directory number. The

6059966245 represents the administration number for the switch. This number is also configured in the Voice Mail Administration Add-on in the APmax TM UI.



A subsystem number for this function must be configured in the switch. It is recommended that the subsystem number 11 be used for this function.

OVLY CNFG REQ CHG SUB MDSI 11

Record the MDSI value on the configuration sheet. Voice Mail stations on this switch will need to have the station option MD 1 to align the Voice Mail/Unified Messaging Service to turn on the stutter dial tone.

10.3.4 Trunk GroupThe Voice Mail/Unified Messaging Service needs an ISUP trunk group originating from the switch. In this example, TG 250 2WAY ISUP TG is used to get voicemail messages from the switch to the APmax. The APmax supports two-way trunking, therefore the APmax will use this same trunk group for the out-dial features.

Actual trunk group number may be different in your configuration. Normally the trunks used for the Voice Mail/Unified Messaging Service should be divided evenly between the two system units. Record the trunk group number on the configuration sheet.

OVLY TGTYP TGNUM 250 Trunk Group NumberTGTP 2WAY Trunk Group TypeTGNM APMAX 2013 VM Trunk Group NameMG NOSIGT ISUP Signaling TypeBDRT 56OPCX 1DPC 010 008 001 APmax Point CodeINBS NOAUUS NO Accept User to User Information signaling messages

for the inter-exchange carrierAATP NO Accept Access Transport Parameter signaling

messages from the inter-exchange carrierPKTP DTRKSITE BASETGDP ELOCCNFS NOSNTC YESITXF 2010 Frequency to be transmitted to the incoming trunk

when a continuity test is being performedIRXF 1780 Frequency to be transmitted to the incoming trunk

when a continuity test is being performed



COIN NOCO (This prompt will not be received if SIGT = ISUP)STSI 0HNPA 605RC 7RTP 0TRNL PRFX Type of TranslatorPRFX 0 Number of the TranslatorAPFX NONE Prefix to be addedTRFC NONE Class of traffic incoming over the TG4XCD NOACKA NO Alarm Checking AccessTYPC NOCO Coin TypeNXX UNKN NXX of the TGLATA 640 Originating LATA of the end office served by this TGCMCT NOTNS NO Accept call containing the Transit Netword Selection in

the IAMTGID NONE TG ID entered into the User ID parameter when any

trigger is encountered by a call originating on a trunk in this TG

SIT NO Shared Interoffice TriggerCNAR NO Connecting Netword Access RecordingLRN NONE Location Routing NumberTNDM NO (For billing purposes) Call connected to a far-end office

by way of Access Tandem SwitchLDAT NOUNUM RELNCKT RELCONG RELNORT RELTMPF RELNRSC RELDNCH RELDOOO RELCREJ RELPERR RELXRER RELBUSY RELOTXF 1780ORXF 2010CINT 1GDTI 768 MSECGLAR NONE If this TG controls in glare. Glare condition exsts when

both ends of a 2-way call are seized simultaneously.IDLE MOST DTSI 0SYNC NO



10.3.5 Trunk ProvisioningOnce the trunk group has been configured, trunks will need to be added to the trunk group. Record the trunks and their Circuit Identification Codes (CICs) on the configuration sheet.

OVLY TRK

REQ NEW DTRK DTRK IS 01 2 12 17TKTP 2WAY Trunk TypeTG 250 Trunk Group NumberCG NONE Carrier Group to which digital trunk is assignedCIC 117 Circuit Identification Code associated with trunkCGRP UNAS Number of the circuit group to which the Trunk Group

belongsSATL NO Trunk is a satellite circuit

10.3.6 Route SetupThe following is the configuration for the Voice Mail route (the actual route number may be different in your configuration). This route will be used to

TRFC NONE2RID YESEOAT NOOSNC NOATIC NO4XCD NOCMCO NOHOPI NOCIP NOSPN YESJIP NOBCAP DFLTOCNP YESRNP YESRIP YESCHNP YESTGMU NOTRK IS 01 2 12 17 IDLE CIC 117 IS 01 2 12 18 IDLE CIC 118 IS 01 2 12 19 IDLE CIC 119 IS 01 2 12 20 IDLE CIC 120 IS 02 2 12 17 IDLE CIC 217 IS 02 2 02 18 IDLE CIC 218 IS 02 2 02 19 IDLE CIC 219 IS 02 2 02 20 IDLE CIC 220



forward calls to the Voice Mail/Unified Messaging Service. Record the route number on the configuration sheet.

OVLY ROUTROUT 250 Route numberALTR CBSY Alternate routeTYPE ISUP Type of routeTRNM APMAX 2013 VM Route nameUPGR NONE Upgrade route to route ISDN calls if all trunks are busyITYP IEAS Type of ISUP callCTYP NONE Type of AMA call carried by the routeLNPB NO Asks if this ROUT’s CTYP should be used for billing

purposes for an LNP call should the call be routed to a different route due to an LNP trigger

TG 250 TG that serves the routeCHG YES Is there charging supervision on this routeCOS NONE Type of Class Of Service tone that is applied upon

answer from a destinationDEL 0 Specifies the number of leading digits other than prefix

digits, that are deleted before outpulsingAPFX NONE Prefix to be added for outpulsingID DFLT Identity digitsFANI YES FANI codes should be sent over this routePGNC NO Peg the call as non-completing

10.3.7 Station ProvisioningThe subscriber stations will need to be provisioned in order to forward calls to the Voice Mail/Unified Messaging Service. Options will be assigned to the station, and then the call will be forwarded to a Voice Mail directory number.

10.3.7.1 Intercept DNThe DN that the CFB and the CFD are forwarded to, must point to the route that is set up to direct the call to Voice Mail on the APmax TM. It must also be an unassigned DN. The intercept DN used in this example is 996 6245 (MAIL). Record the intercept DN on the configuration sheet.

REQ ICP DN 996 6245ICPT ROUT Intercept TypeROUT 250 The route the intercepted calls will take

10.3.7.2 Assigning Station Options10.3.7.2.1 Forwarding Voice Mail to the APmax TM

The subscriber station must contain two station options in order for the station to access Voice Mail. The CFB option will forward the call when the called station is busy. The CFD option will forward the call when the called station is



not answered after a pre-programmed amount of rings. The following options must be entered to the subscribers station:

OVLY DN REQ ADO STN 996 1302 OPT CFB CFD

When a call to a Voice Mail customer encounters a busy or no answer, the call is forwarded to the intercept number. The call is then routed to the APmax TM. The following commands will forward the call to the selected intercept DN.

REQ ACT STN 996 1302 OPT CFB FWTO 9966245 Voice Mail route DN (6245 = MAIL)

REQ ACT STN 996 1302 OPT CFD FWTO 9966245 R4 R4 Forwards to VM after 4 rings (Default is 2)

10.3.7.2.2 Message Waiting IndicatorsIn order to activate the Message Waiting Indicator (MWI), the option Message Desk (MD) should be added to the station. To deliver a light on the station, the feature bit MWIL must be assigned for the switch and the option MWIL assigned to the station.

The following is the station configuration for MD and MWIL if the SMDI is over SS7 on a switch with the feature bit MDSI:

OVLY DN REQ ADO STN 996 1302 OPT MWIL MD 1 The 1 is the MSR index number assigned in the switch

Note: An MSR table index of 0 is used for subscribers using the SMDI feature. An index of 1 - 255 indicates that the MDSI feature is being used to provide Message Desk service. Indexes 1 - 255 must be previously assigned in Overlay CNFG (MSR)

The MWI may be provisioned as a Stutter Dial Tone (STDT) heard by the subscriber when they go off hook. The default configuration of the C15 is to provide continuous stutter dial tone. This can be changed.

OVLY CNFG REQ CHG CP Call Processing TYP STDT 2SEC 2 seconds of STDT followed by normal dial tone



To suppress the stutter dial tone assign the option SIDT (Suppress Intermittent Dial Tone) to the subscribers station.

OVLY DNREQ ADO STN 996 1302OPT SIDT Suppress Stutter Dial Tone

Refer to Figure 10-2 for an example configuration of a subscriber line and to view the Voice Mail Service flow.

Figure 10-2 Subscriber Line with Voice Mail Service

In this example (refer to Figure 10-2), station 996 1302 has been assigned the required options for the Voice Mail/Unified Messaging Service, CFB, and CFD. The forwarding options have both been set to forward to the intercept number (996 6245). The station has also been assigned the required options for a MWI, MD, and MWIL.

When a call is placed to station 996 1302 and the call is unanswered or busy, the switch forwards the call to the intercept number (996 MAIL) and is then routed to the APmax.

The Voice Mail/Unified Messaging Service looks for the Redirecting Number (996 1302) or the Original Called Party (dependent on service settings) to determine the proper voice mailbox to access.

Once the mailbox has been found, the service plays the custom greeting or system greeting to the caller and a message can be left in the subscriber’s mailbox.

Since the subscriber has been assigned the MD and MWIL options, a MWI or stutter dial tone will now be present on their phone indicating a message in their voice mailbox if a message is left.



10.3.8 Teen Service With Voice MailNote: If the TEEN feature option is not available please contact Genband so the feature can be enabled on your switch. This option is required to configure the following.

The Teen and Voice Mail/Unified Messaging services may be provisioned three ways. The incoming call may be forwarded to the shared subscriber mailbox number, Teen subscriber mailbox number, or not forwarded to Voice Mail at all.

REQ ADO STN 996 1302OPT TEEN 996 1312 0 Call Forward Mode (CFM) set to 0. All incoming calls

to the Teen DN, when applicable, will forward Voice Mail to the shared subscribers mailbox number.

REQ ADO STN 996 1302OPT TEEN 996 1312 3 CFM set to 3. All incoming calls to the Teens DN, when

applicable, will forward Voice Mail to the teens subscriber mailbox number.

REQ ADO STN 996 1302OPT TEEN 996 1312 1 CFM set to 1. The switch will not to forward the

incoming call to the Teen DN, to Voice Mail.

To allow the Teen DN to share a mailbox with the subscriber, the Teen DN must be assigned to the subscriber’s mailbox as an associated number. Associated numbers are additional phone numbers from which the subscriber can check and receive voicemail. Associated numbers are assigned through the APmax TM UI.

Refer to Figure 10-3 for an example configuration of Teen Line and the Voice Mail Service Flow.

Figure 10-3 Teen Line with Voice Mail Service

Station 996 1302, (refer to Figure 10-3), has CFB and CFD both forwarding to the intercept number (996 MAIL) and also has a Teen Line (996 1312). The CFM has been set to 3.

10.3.8.1A call is placed to 996 1312, the Teen Line. The Teen Line goes unanswered or is busy so the call is forwarded by the switch to the intercept number thus routing the call to the APmax TM.



10.3.8.2The Voice Mail Service looks for the Redirecting Number (996 1302) or the Original Called Party (dependent on service settings) to determine the proper voice mailbox to access. If the Teen Line has not been assigned its own voice mailbox the service plays an announcement and disconnects the call. If the Teen Line has been assigned a mailbox or is sharing a mailbox with the subscriber, the service is encountered and a message may be left.

10.3.8.3Since MD and MWIL have been assigned to the subscriber’s station, a stutter dial tone or MWIL will be present for the Teen Line if a message has been left.

Again, if the parameters for CFD and CFB are changed from forwarding to the intercept number then the subscribers ability to forward to the Voice Mail Service will be affected as well as the Teen Line’s ability to forward to the Voice Mail Service.

10.3.9 Hunt Group with Voice MailCFD must be assigned to all stations within the hunt group and set to forward to the designated intercept number. A single shared mailbox should be assigned to all stations in the hunt group. (The main DN of the hunt group is the suggested voice mailbox number.)

All calls that encounter no answer will be forwarded to the main DN’s voice mailbox. This is accomplished by assigning all other stations within the hunt group to the shared mailbox as associated numbers. The creation of mailboxes and associated numbers is done through the APmax TM UI. Sub-mailboxes may be assigned accordingly.

When all lines belonging to the hunt group ring busy, the Voice Mail Service will be encountered only when the overflow of the hunt group has been set to ROUT (route). The route specified must be the same route that the Voice Mail Service calls will be forwarded on. Section 10.3.6 - "Route Setup".

OVLY CNFG TYP DNH HTGP 1 IWT NO FGA NO LNPT NO SRCH FRST OVFL ROUT ROUT RTE 250 Route specified is the Voice Mail Service Route DN 996 1000 996 1001 996 1002



10.3.10 Centrex ConfigurationWhen the EBS group GPDN 6059956120 is created, the calls can be identified as the main number, however, when Voice Mail is dialed it is still identified as 6120 rather than the Centrex line number.

OVLY DN STN 996 1000 DNH 1 FRST ADO STN 996 1000 OPT CFD FWTO 9966245

STN 996 1001 DNH 1 996 1000 ADO STN 996 1001 OPT CFD FWTO 9966245

STN 996 1001 DNH 1 996 1000ADO STN 996 1002OPT CFDFWTO 9966245

REQ QUE EBS 0

TYP EBSEBSG 0HDMP DFLTMDMP DFLTNDMP DFLTIHCN NOSTS 3VSTS VCDNLANG ENGLMD YESMSRI 3SUPR NOPREF 0DNS 10DAT 3DCBI NOPRES 9900PRS2 9900PRS3 9900GIWL NOCTO NOLNPT NOIP NORDSP NO



The Voice Mail System option (VMS OPT) indicates that this RCFA is used to forward voice mail subscribers to the voice mail system. When this option is assigned to an RCFA, the calling party number sent to the Voice Mail system will be the EBS member DN and not its group DN (assigned in HUNT (EBS)).

Note: To access Voice Mail systems using CCS7 signaling, a RCFA with the VMS option must be used to ensure the correct calling party number is delivered to the voice mail system.

By adding the RCFA with the VMS OPT, the Centrex line dials the 7091 number to access the Voice Mail ID with their correct phone number.

PKTM 12PRRT 12MOH NONEPAUD RGBKPRNG NOCFTO NONEAFWD NOCPTM 12CRRT 12CAUD RGBKCRNG NOMDR NONESNND NOPND NOGPNM “INNOVATIVE SYS”FNPR NOCDP NOGPDN 605 995 6120OUT 0 SBN:NONEINC 02WAY 0 SBN:NONEPRIM 1WAY

REQ QUE RCFADN 990 7091RCFADN 990 7091RDN 9907090OPT 1FR RTP 0 EMR 0 MAX 255 VMS

REQ

REQ QUE DN 990 7090

DN 990 7090



10.3.11 Tandem Configuration of the Voice Mail ServiceIn the case of a tandem configuration of the Voice Mail Service, the provisioning of ISUP trunks in not only the HSO but the SSO is required. Your current configurations will determine the TG parameters and routing. Refer to Section 10.3.5 - "Trunk Provisioning" for configuration examples. See Figure 10-4 for an example of the Voice Mail Service Flow.

Figure 10-4 Tandem Connection with Voice Mail Service

Figure 10-4 shows an example of both an HSO and SSO and the routing of the Voice Mail/Unified Messaging Service. The station 995 1402 has been assigned all options necessary for proper activation of the Voice Mail/Unified Messaging Service.

10.3.11.1When a call is placed to station 995 1402 and the call is unanswered or busy, the switch forwards the call to the intercept number (996 MAIL) and is thus routed to the APmax TM through the HSO tandem trunks.

10.3.11.2The Voice Mail Service looks for the Redirecting Number (996 1402) or the Original Called Party (dependent on service settings) to determine the proper voice mailbox to access.

10.3.11.3Once the mailbox has been found, the service plays the custom greeting or system greeting to the caller and a message can be left in the subscriber’s mailbox.

10.3.11.4Since the subscriber has been assigned the MD and MWIL options, a MWI or stutter dial tone will now be present on their phone if a message has been left in their voice mailbox.

ROUT RTE 250 APMAX VM 9063








10.4.2 TrunkingVoice Mail requires configuration of an in-bound trunk group on the APmax TM. If any of the outbound call features (Daily Notification, Reply To Phone) are to be used, then an outbound trunk group is also required. The following example utilizes a two-way trunk group so both inbound and outbound calls may be received and placed.

10.4.2.1 Trunk ProvisioningThe following assumes the SS7 links, linksets/routes, and DS1s have been cabled and configured from the switch to the APmax TM.

10.4.2.1.1From the APmax TM UI, right-click on the system’s icon in the Command Center window to invoke a popup menu, and select the System Configuration | Trunks | Trunk Configuration command. For more information on the Trunk Configuration window, refer to the APmax User Manual.

10.4.2.1.2Click Add. Enter the Trunk Group #, Signaling Type, Trunk Group Name, Direction, and Far-end Name. If possible, use the same trunk group number as the switch. The Far-end Name will be the SS7 Route, specifically the SSP, configured previously. See Section 2.2.2.6 - "SS7 Configuration". When finished, click OK.



Figure 10-5 Enter Trunk Group Info

10.4.2.1.3Highlight the trunk group you just created and verify that the Trunk Group Settings | General Settings match the settings on the switch.

Figure 10-6 Trunk Group Settings

10.4.2.1.4Click on the Trunk Members tab and click Add.

10.4.2.1.5In the left-hand column, Available Trunks, highlight the trunks to add to the trunk group. Once highlighted, click Add. Enter the appropriate CIC for each trunk. Once complete, click OK, and close the window.



10.4.2.2 Verify the Trunks are In serviceVerify the trunks are in-service. From the APmax TM UI, right-click on the system’s icon in the Command Center window to invoke a popup menu, and select the System Surveillance | Digital Carrier Status command. For more information on the Digital Carrier Status window, refer to the APmax User Manual.

10.4.2.2.1From the Trunks tab, verify the trunks are in service. If the trunks are not in service verify the DS1s are Enabled and the settings are correct. Configuration of the DS1s may be accessed from System Configuration | Trunks | Digital Carrier Configuration.

10.4.2.2.2The trunks should be in service if the following conditions have been met:

• The DS1 cables have been physically connected from the C15 to the APmax TM (using the T1 cable assemblies, provided optionally), are properly defined, and enabled. See Section 2.2.2 - "Provisioning the APmax TM".

• The trunks CICs are provisioned to match those in the switch.

• The trunk group settings between the switch and the APmax TM match.

• The trunks have been put into service from the switch end.

10.4.3 Voice Mail AdministrationThe following section explains how to setup the administration portion of the Voice Mail Service on the APmax TM. Before administration from the Voice Mail add-ons can occur, you must first define the Subscriber Mapping.

From the APmax TM UI, right-click on the APmax TM UI icon in the Command Center window to invoke a popup menu, and select the Subscriber System Map command. For more information on the Subscriber System Map window, refer to the APmax TM User Manual.

10.4.3.1Select Add.

10.4.3.2Enter the NPA-NXX of the Voice Mail subscribers that will reside on your APmax TM.

10.4.3.3Select your APmax system.

10.4.3.4Select Voicemail.



10.4.3.5Select OK.

10.4.3.6Repeat for any additional NPA-NXXs that should be mapped to Voice Mail on your system. Close the window.

10.4.3.7 Intercept DNThe intercept number previously defined in the switch should be defined in the APmax TM. From the APmax TM UI, right-click on the services icon in the Command Center window to invoke a popup menu, and select the Voice Mail | Administration command. For more information on the Voice Mail Administration add-on, refer to the Voice Mail Service Description.

10.4.3.7.1Click on the Voice Mail Access tab. Ensure the system name in the left-hand column of the window shows the APmax TM system you are configuring.

10.4.3.7.2Under Administrative Numbers, click Add.

10.4.3.7.3When prompted, enter the intercept number. Click OK. Repeat for any additional intercept/administration numbers.


10.4.3.8 Outdial FeaturesIf any outgoing call features will be used, then the outbound trunk group number must be defined in the APmax TM.

From the APmax TM UI, right-click on the services icon in the Command Center window to invoke a popup menu, and select the Voice Mail | Administration command. For more information on the Voice Mail Administration add-on, refer to the Voice Mail Service Description.

10.4.3.8.1Click on the Voice Mail Configuration tab. Ensure the system name in the left-hand column of the window shows the APmax TM system you are configuring.

10.4.3.8.2Under Outgoing Trunk Groups, click Add. Enter the Address to map to an outgoing trunk group. This address may be zero digits in length (indicating that all numbers are mapped to the trunk group), a 6-digit NPA-NXX, a 7-digit number (i.e., 605-555-5), or a 10-digit directory number.



10.4.3.8.3Select the Trunk Group Voice Mail should use for outbound calls. Select OK.


10.4.4 Message Waiting IndicationThe APmax TM comes preconfigured with default notification centers, one of which is an SS7 Notification Center.

From the APmax TM UI, right-click on the system icon in the Command Center window to invoke a popup menu, and select the System Configuration | Notification Center Management command. For more information on the Notification Center Management window, refer to the Voice Mail Service Description. The following shows an example SS7 Notification Center.

Figure 10-7 SS7 Notification Center

10.4.4.1The Point Code is the point code of the SSP defined previously.

10.4.4.2The Subsystem Number should match the MDSI defined in the switch. Again, it is recommended that the subsystem number of 11 be used for this function.



10.4.4.3The MSR DN must match the MDDN previously configured on the switch.

10.4.5 Subscriber ManagementPlease refer to the Voice Mail Service Description for information regarding entrance of new subscribers and subscriber management.



10.5 Voice Mail Configuration Sheet10.5.1 Message Waiting Indication

10.5.1.1MSR:___________________________________________

10.5.1.2MDID:__________________________________________

10.5.1.3MDDN:______________________________________

10.5.1.4MSDI (Subsystem Number):_________________________

10.5.2 Trunking10.5.2.1Route:___________________________________________

10.5.2.2Trunk Group:______________________________________

10.5.2.3 Trunks

Table 10-1

Trunk CIC

10.5.3Intercept DN:______________________


11. Basic Conferencing Service 133

11. Basic Conferencing Service

11.1 General DescriptionThe Basic Conferencing service allows for quality conferencing calling with zero administration. It functions on a first-come, first-serve basis.

This chapter will assist in the switch setup for the Basic Conferencing service. Areas of coverage in this chapter will be switch setup for routes and trunks, and intercept DN provisioning. This chapter assumes that the DS1s and SS7 links have already been setup between the switch and the APmax TM and are functioning.

11.2 Call FlowFigure 11-1 Basic Conference Service Flow

INTERCEPT DN ROUTE2WAY ISUP TRUNK

GROUP APmax


If the following feature options are not available, please contact Genband so the feature(s) can be enabled on your switch. Feature bits that are required for Basic Conferencing are as follows:

ISUP YES ISUP Capabilities are required

11.3.2 Trunk GroupThe Basic Conferencing service needs a dedicated incoming ISUP trunk group from the switch. The APmax TM will receive incoming calls from this trunk group. In this documentation, 125 2WAY ISUP TG is used to get the call from the switch to the APmax TM. This trunk group is configured to connect to both units in order to provide redundancy.


134 11. Basic Conferencing Service

Note: The actual TG number may be different in your configuration. Record the trunk group number on the configuration sheet (see 11.5).

OVLY TG TYP TG NUM 125 Trunk Group Number TGTP 2WAY Trunk Group Type TGNM APMAX 2013 BC Trunk Group Name MG NO SIGT ISUP Signaling Type BDRT 56 OPCX 1 DPC 010 008 001 APmax™ Point Code INBS NO AUUS NO Accept User to User Information signalling messages

for the inter-exchange carrier. AATP NO Accept Access Transport Parameter signaling

messages from the inter-exchange carrier. PKTP DTRK SITE BASE TGDP ELOC CNFS NO SNTC YES ITXF 2010 Frequency to be transmitted to the incoming trunk

when a continuity test is being performed. IRXF 1780 Frequency to be received for the incoming trunk when

a continuity test is being performed. COIN NOCO (Will not receive this prompt if SIGT = ISUP) STSI 0 HNPA 605 RC 7 RTP 0 TRNL PRFX Translator Type PRFX 0 Translator Number APFX NONE Prefix to be added TRFC NONE 4XCD NO ACKA NO Alarm Checking Access TYPC NOCO Coin Type NXX UNKN NXX of the TG LATA 640 Originating LATA of the end office served by this TG CMCT NO TNS NO Accept call containing the Transit Network Selection in

the IAM TGID NONE TGID entered into the User ID parameter when any

trigger is encountered by a call originating on a trunk in this TG.



SIT NO Shared Interoffice Trigger CNAR NO Connecting Network Access Recording LRN NONE Location Routing Number TNDM NO For billing purposes - Is call connected to a far-end

office by way of Access Tandem Switch LDAT NO UNUM REL NCKT REL CONG REL NORT REL TMPF REL NRSC REL DNCH REL DOOO REL CREJ REL PERR REL XRER REL BUSY REL OTXF 1780 ORXF 2010 CINT 1 GDTI 768 MSEC GLAR NONE If this TG controls in glare. Glare condition exists when

both ends of a 2-way call are seized simultaneously. IDLE MOST DTSI 0 SYNC NO TRFC NONE 2RID YES EOTAT NO OSNC NO ATIC NO 4XCD NO CMDO NO HOPI NO CIP NO SPN YES JIP NO BCAP DFLT OCNP YES RNP YES RIP YES CHNP YES TGMU NO TRK IS 01 2 12 21 IDLE CIC 121 IS 01 2 12 22 IDLE CIC 122 IS 01 2 12 23 IDLE CIC 123



11.3.3 Trunk ProvisioningOnce the trunk group is configured, trunks need to be added to the trunk group. This is done in OVLY TRK. Below is an example for setting up trunks. Record the trunks and their CICs on the configuration sheet.

OVLY TRK DTRK IS 01 2 12 21 TKTP 2WAY Trunk Type TG 125 Trunk Group Number CG NONE Carrier Group to which digital trunk is assigned CIC 121 Circuit Identification Code associated with trunk CGRP UNAS Number of the circuit group to which the Trunk Group

belongs SATL NO Trunk is a Satellite Circuit

11.3.4 Route SetupThe following is the configuration for the Basic Conferencing route. Note that the actual route number may be different in your configuration. This route will be used to forward calls to the Basic Conferencing Service. Record the route number on the configuration sheet.

OVLY ROUT ROUT 125 Route Number ALTR CBSY Alternate Route TYPE ISUP Type of Route RTNM APMAX 2013 BC Route Name UPGR NONE Upgrade route to route ISDN calls if an all-trunks-busy

condition ITYP IEAS Type of ISUP call CTYP NONE Type of AMA call carried by the route TG 125 TG that serves the route CHG YES Is there charging supervision on this route COS NONE Type of Class of Service tone that is applied upon

answer from a destination. DEL 0 Specifies the number of leading digits other than prefix

digits, that are deleted before outpulsing. APFX NONE Prefix to be added for outpulsing ID DFLT Identitiy digits FANI YES FANI codes should be sent over this route PGNC NO Peg the call as non-completing

IS 01 2 12 24 IDLE CIC 124 IS 02 2 12 21 IDLE CIC 221 IS 02 2 02 22 IDLE CIC 222 IS 02 2 02 23 IDLE CIC 223 IS 02 2 02 24 IDLE CIC 224



11.3.5 Intercept DNThe DN that the attendees call must point to the route that is set up to direct the call to Basic Conferencing on the APmax TM. It must also be an unassigned DN. The intercept DN used in this example is 996 2665. Record the intercept DN on the configuration sheet.

REQ ICP DN 996 2665 ICPT ROUT Intercept Type ROUT 125 The route the intercepted call will take






11.4.2 TrunkingBasic Conferencing requires configuration of an in-bound trunk group on the APmax TM. The following example utilizes a two-way trunk group.



11.4.2.1.2Click Add. Enter the Trunk Group #, Signaling Type, Trunk Group Name, Direction, and Far-end Name. If possible, use the same trunk group number as the switch. The Far-end Name will be the SS7 Route, specifically the SSP, configured previously (see 2.2.2.6). When finished, select the OK button.













• The DS1 cables have been physically connected from the C15 to the APmax TM (using the T1 cable assemblies, provided optionally), are properly defined, and enabled. See Section 2.2.2 - "Provisioning the APmax TM".




11.4.3 Intercept DNThe intercept number previously defined in the switch must be also be defined in the APmax TM. From the APmax TM UI, right-click on the system icon in the Command Center window to invoke a popup menu, and select the System Configuration | Service Access Map command.

11.4.3.1Expand the BasicConferencing tree. Under BasicConferencing highlight “Call Start event when:”.



Figure 11-4 Service Access Map

11.4.3.2Click Add Group. Populate the window as shown. Please note, your Access Address is your intercept DN and may differ from the example provided. If a 10-digit number will not be delivered to the APmax TM, change the Syntax Type to Freeform. This will allow you to enter a seven-digit number.

Figure 11-5 Add Group



11.4.3.3Click Add. Click OK.

11.4.3.4The Service Access Map should look similar to the following:

Figure 11-6 Service Access Map Complete




11.5 Basic Conferencing Configuration Sheet11.5.1 Trunking

11.5.1.1Route:_________

11.5.1.2Trunk Group:_________

11.5.1.3 Trunks

Table 11-1

Trunk CIC

11.5.2Intercept DN:______________________


12. On-Demand Conferencing Plus Service 143

12. On-Demand Conferencing Plus Service

12.1 General DescriptionConference Calling is experiencing significant growth and becoming the preferred method to communicate information and conduct meetings remotely. Its popularity is increasing because it is a convenient and inexpensive alternative to meetings and business travel. Businesses of all types are discovering that conference calling is an effective business tool.

With the On-Demand Conferencing Plus Service from Innovative Systems, your company can now provide a quality conference service to businesses and organizations in your local service area, and beyond. The minutes of use generated by the On-Demand Conferencing Plus Service will increase revenue from service charges and terminating access revenue.

The On-Demand Conferencing Plus Service enables the subscriber to manage and conduct their conferences without the Telco's assistance. Summary (EMI) and Detailed (XML) billing records are generated for the conferences to enable accurate billing, and several pricing parameters can be configured for each conference subscriber.

These services are further distinguished with the option to manage and view conferences over the Internet using the web portal. Subscribers can manage multiple aspects of the conference from their web portal account. This online, real-time conference manager allows your company to differentiate its service from that provided by any competitors.

This chapter will assist in the switch setup for the On-Demand Conferencing Plus Service. Areas of coverage in this chapter will be switch setup for routes and trunks and intercept DN provisioning. This chapter assumes that the DS1s and SS7 links have already been setup between the switch and the APmax TM and are functioning.


144 12. On-Demand Conferencing Plus Service

12.2 Call Flow12.2.1 Incoming

Figure 12-1 Conference Service Flow

800 NumberDirect Dial

INTERCEPT DNROUTE

2WAY ISUP TRUNKGROUP APmax

12.2.2 OutgoingSee Chapter 19. - "Integrated Web Portal" for the call flow of Conferencing Out-dial and Click-to-Call.


If the following feature options are not available options please contact Genband so the feature(s) can be enabled on your switch. Feature bits that are required for Conferencing are as follows:

ISUP YES ISUP Capabilities are required

If Integrated Web Portal features such as Click-to-Call will be used, the following bit is required to support Release Link Trunking (RLT) and Barge-In:

SNTC YES IService Node Trunk Control

12.3.2 Trunk GroupThe On-Demand Conferencing Plus Service needs a dedicated two-way ISUP trunk group from the switch. The APmax TM will receive incoming calls from this trunk group and make outgoing calls with this trunk group. In this documentation, the following TG is used to get the call from the switch to the APmax TM. This trunk group is configured to connect to both units to provide redundancy.

Note: The actual TG number may be different in your configuration.



Record the trunk group number on the configuration sheet found at the end of this chapter.

OVLY TG TYP TG NUM 150 Trunk Group Number TGTP 2WAY Trunk Group Type TGNM APMAX 2013 ODC Trunk Group Name MG NO SIGT ISUP Signaling Type BDRT 56 OPCX 1 DPC 010 008 001 APmax™ Point Code INBS NO AUUS NO Accept User to User Information signaling messages

for the inter-exchange carrier. AATP NO Accept Access Transport Parameter signaling

messages from the inter-exchange carrier PKTP DTRK SITE BASE TGDP ELOC CNFS NO SNTC YES ITXF 2010 Frequency to be transmitted to the incoming trunk

when a continuity test is being performed. IRXF 1780 Frequency to be received for the incoming trunk when

a continuity test is being performed COIN NOCO (Will not receive this prompt if SIGT = ISUP) STSI 0 HNPA 605 RC 7 RTP 0 TRNL PRFX Translator Type PRFX 0 Translator Number APFX NONE Prefix to be added TRFC NONE Class of traffic incoming over the TG 4XCD NO ACKA NO Alarm Checking Access TYPC NOCO Coin Type NXX UNKN NXX of the TG LATA 640 Originating LATA of the end office served by this TG CMCT NO TNS NO Accept call containing the Transit Network Selection in

the IAM



TGID NONE TG ID entered into the User ID parameter when any trigger is encountered by a call originating on a trunk in this TG.

SIT NO Shared Interoffice Trigger CNAR NO Connecting Network Access Recording LRN NONE Location Routing Number TNDM NO For billing purposes - Is call connected to far-end office

by way of Access Tandem Switch. LDAT NO UNUM REL NCKT REL CONG REL NORT REL TMPF REL NRSC REL DNCH REL DOOO REL CREJ REL PERR REL XRER REL BUSY REL OTXF 1780 ORXF 2010 CINT 1 GDTI 768 MSEC GLAR NONE If this TG controls in glare. Glare condition exists when

both ends of a 2-way call are seized simultaneously. IDLE MOST DTSI 0 SYNC NO TRFC NONE 2RID YES EOAT NO OSNC NO ATIC NO 4XCD NO CMCO NO HOPI NO CIP NO SPN YES JIP NO BCAP DFLT OCNP YES RNP YES RIP YES CHNP YES TGMU NO



12.3.3 Trunk ProvisioningOnce the trunk group is configured, trunks need to be added to the trunk group. This is done in OVLY TRK. Below is an example for setting up trunks. Record the trunks and their CICs on the configuration sheet found at the end of this chapter.

OVLY TRK DTRK IS 01 3 12 21 TKTP 2WAY Trunk Type TG 150 Trunk Group Number CG NONE Carrier Group to which digital trunk is assigned CIC 121 Circuit Identification Code associated with trunk CGRP UNAS Number of the circuit group to which the TG belongs SATL NO Trunks is a Satellite Circuit

12.3.4 Route SetupThe following is the configuration for the On-Demand Conferencing route. Note that the actual route number may be different in your configuration. This route will be used to forward calls to the On-Demand Conferencing Plus Service. Record the route number on the configuration sheet found at the end of this chapter.

TRK IS 01 3 12 01 IDLE CIC 111 IS 01 3 12 02 IDLE CIC 112 IS 01 3 12 03 IDLE CIC 112 IS 01 3 12 04 IDLE CIC 112 IS 02 3 12 01 IDLE CIC 112 IS 02 3 02 02 IDLE CIC 112 IS 02 3 02 03 IDLE CIC 112 IS 02 3 02 04 IDLE CIC 112

OVLY ROUT ROUT 150 Route Number ALTR CBSY Alternate Route TYPE ISUP Type of Route RTNM APMAX 2013 ODC Route Name UPGR NONE Upgrade route to route ISDN calls if an all-trunks-busy

condition arises ITYP IEAS Type of ISUP call CTYP NONE Type of AMA call carried by the route TG 125 TG that serves the route CHG YES Is there charging supervision on this route COS NONE Type of Class of Service tone that is applied upon


digits that are deleted before outpulsing. APFX NONE Prefix to be added for outpulsing



12.3.5 Intercept DNThe On-Demand Conferencing Plus Access Number that the attendees call must point to the route that is set up to direct the call to Conferencing on the APmax TM. It must also be an unassigned DN. If a toll free number will be provided, it is expected that the switch will translate the number before forwarding the call to the APmax TM. Be sure that any intercept numbers that should route the On-Demand Conferencing route do.

The intercept DN used in this example is 996 2665. Record the intercept DN(s) on the configuration sheet provided at the end of this chapter.

REQ ICP DN 996 2664 ICPT ROUT Intercept TypeROUT 125 The route the intercepted calls will take

12.3.6 Barge-InBarge-In requires a call to be established within the APmax TM prior to the “move” of a call from the switch to the APmax TM (see section 19.).

At least one two-way trunk group must be provisioned per APmax TM unit to support use of the Barge In feature. Each two-way trunk group must contain at least two trunks.

Note: These TGs are in addition to the two-way trunk group configured for On-Demand Conferencing.

It is suggested that there be three TGs total on the switch (one for normal operation, two for barge-in) and three TGs on the APmax TM. Having three TGs guarantees that the Barge-In TGs and assigned trunks will be used exclusively for the Barge-In calls inbound to the APmax TM.

One barge-in trunk group will contain trunks only connected to APmax TM Unit 1 to ensure calls on this TG route to Unit 1. The other barge-in trunk group will contain trunks only connected to APmax TM Unit 2 to ensure calls on this TG route to Unit 2 (see 12.3.2).

Each barge-in TG should contain at least two trunks (see 12.3.3). Each barge-in trunk group requires a route. This route shall route the call to the appropriate TG (see section 12.3.4).

The switch will intercept the barge-in call based on the called number. This requires two intercept numbers be defined in the switch. Calls to these Call Back Numbers shall be intercepted and routed to the proper unit (see 12.5.2).

ID DFLT Identity digits FANI YES FANI codes should be sent over this route PGNC NO Peg the call as non-completing



Please record these values on the configuration sheet provided at the end of this chapter.



When a package is deployed, the contents of the package are copied to the appropriate locations on the system. Depending on the type of APmax TM system configuration specified or the particular application(s) purchased with the system the software may be pre-loaded.


12.4.2 TrunkingOn-Demand Conferencing Plus requires configuration of a two-way trunk group on the APmax TM. The following example utilizes a two-way trunk group.



12.4.2.1.2Click Add. Enter the Trunk Group #, Signaling Type, Trunk Group Name, Direction, and Far-end Name. If possible, use the same trunk group number as the switch. The Far-end Name will be the SS7 Route, specifically the SSP, configured previously (see 2.2.2.6). When finished, click OK.





Note: If supported in the switch, ensure that RLT is set to the appropriate switch type. For the C15 set this to DMS10.


12.4.2.1.4Click on the Trunk Members tab and select the Add button.







• The DS1 cables have been physically connected from the C15 to the APmax TM (using the T1 cable assemblies, provided optionally), are properly defined, and enabled (see section 2.2.2).




12.4.3 On-Demand AdministrationThe following section explains how to setup the administration portion of the On-Demand Conferencing Plus Service on the APmax TM. Before administration from the On-Demand Conferencing add-ons can occur, you must first define the Subscriber Mapping.

From the APmax TM UI, right-click on the APmax TM UI icon in the Command Center window to invoke a popup menu, and select the Subscriber System Map command. For more information on the Subscriber System Map window, refer to the APmax TM User Manual.

12.4.3.1Select the Add button.

12.4.3.2Enter the NPA-NXX of the Voice Mail subscribers that will reside on your APmax TM.



12.4.3.3Select your AP System.

12.4.3.4Select the Service, in this case select OnDemandConferencing.

12.4.3.5Click OK.

12.4.3.6Repeat for any additional NPA-NXXs that should be mapped to On-Demand Conferencing on your system.

12.4.3.7 Intercept DNThe intercept number previously defined in the switch to access the On-Demand Conferencing Service must be also be defined in the APmax TM. From the APmax TM UI, right-click on the services icon in the Command Center window to invoke a popup menu, and select the On-Demand Conferencing | Administration command. For more information on the On-Demand Conferencing Administration add-on, refer to the On-Demand Conferencing Plus Service Description.

12.4.3.7.1Click on the On-Demand Access Numbers tab. Ensure the system name in the left-hand column of the window shows the APmax TM system you are configuring.

12.4.3.7.2Under Direct Dial click Add.

12.4.3.7.3When prompted, enter the intercept number that subscribers may direct dial to reach the service. Select the OK button. Repeat for any additional direct dial numbers.

12.4.3.7.4If applicable, under Toll Free Translation select the Add button.

12.4.3.7.5When prompted, enter the toll free number as well as the translated number, i.e. the number the switch will translate the toll free number to. Select OK. Repeat for any additional toll free numbers.

12.4.3.8 Out Dial SettingsTo utilize Conferencing Out-dial and Click-to-Call at least one Outgoing or Two-Way Trunk Group must be defined. From the APmax TM UI, right-click on the services icon in the Command Center window to invoke a popup menu,



and select the On-Demand Conferencing | Administration command. For more information on the On-Demand Conferencing Administration add-on, refer to the On-Demand Conferencing Plus Service Description.

12.4.3.8.1Select the Out Dial Settings tab. Ensure the system name in the left-hand column of the window shows the APmax TM system you are configuring.

12.4.3.8.2Under Outgoing Trunk Groups click the Add button.

12.4.3.8.3When prompted, enter the Address. This subscriber address may be an NPA-NXX, 0 (all numbers), 7, or 10 digits. Outgoing calls that match this address will select this trunk group.

12.4.3.8.4From the drop-down, select the outgoing trunk group to which the entered address will be mapped. Select the OK button. Repeat for any additional addresses.

12.4.3.9To support Click-to-Call, Barge-In should be configured. Refer the configuration sheet at the end of this chapter for the values to be entered.

12.4.3.9.1Select the Out Dial Settings tab. Ensure the system name in the left-hand column of the window shows the APmax TM system you are configuring.

12.4.3.9.2Under Barge In Numbers select the Add button.

12.4.3.9.3When prompted, enter the Unit that should listen for the barge-in number. Barge-in numbers must be configured for each unit for barge-in to work properly.

12.4.3.9.4Enter the Call Back Number. This is the 10-digit number dialed for barge-in. This number must be intercepted in the switch and routed to the appropriate unit. Select the OK button.

12.4.4 Subscriber ManagementPlease refer to the On-Demand Conferencing Plus Service Description for information regarding entrance of new subscribers and subscriber management.



12.5 On-Demand Conferencing Configuration Sheet12.5.1 Trunking

12.5.1.1Route:_________

12.5.1.2Trunk Group:_________ RLT Set________ Used for Outdial________

12.5.1.3 Trunks

Table 12-1

Trunk CIC

12.5.2 Intercept DN(s)12.5.2.1Direct Dial: ______________________

12.5.2.2Toll Free: ______________________

12.5.2.3Translated Number: ______________________



12.5.3 Barge In

Table 12-2

Unit APmax TG Switch TG Route Intercept Number

Table 12-3

APmax TG Switch TG Trunk CIC




13. Switch Service Control 157

13. Switch Service Control

13.1 General DescriptionThis service provides a web based interface for subscribers of SLE (Screening List Editing) services and speed calling, through which they may administer their service settings.

It can provide the subscriber with the status of their service(s) (active/inactive), the number of DNs (public and private) in the screening list associated with the service, and the entries in their screening lists and speed calling lists.

It also allows the subscriber to change the status of their service(s), add numbers to their screening list(s), update their forwarding DN (in the case of SCF), update their speed calling list, or delete entries from their screening list(s).

The features that this service administers are the Screen List Editing features (SCR-Selective Call Rejection, SDR-Selective Distinctive Ringing/Call Waiting, SCF-Selective Call Forwarding, SCA-Selective Call Acceptance, and SRNG-Simultaneous Ringing), the SSC (Short list Speed Calling), LSC (Long list Speed Calling), and Group Speed Dialing features, as well as Convenience Dialing.

This chapter will assist in the switch setup for the Switch Service Control Service. Areas of coverage in this chapter will be setup of AIN and station provisioning. This chapter assumes that the SS7 links have already been setup between the switch and the APmax TM and are functioning.


If the following feature options are not available options please contact Genband so the feature(s) can be enabled on your switch. Features that are required for Switch Service Control are as follows:

WEBF YES Web Based Feature control is enabled SCR YES Selective Call Rejection SDR YES Selective Distinctive Ringing/Call Waiting SCF YES Selective Call Forwarding SCA YES Selective Call Acceptance SRNG YES Simultaneous Ringing SSC YES Short List Speed Calling LSC YES Long List Speed Calling GSCC YES Group Speed Calling CVDC YES Convenience Dialing


158 13. Switch Service Control

13.2.2 Directory Number ProvisioningThe Switch Service Control subscriber’s DN must have the SLE line options assigned to it (OVLY DN - ADO) in order to administer the features relating to the line option.

Please note, use of the GSCC line option requires the subscribing station be a member of an EBS group. Use of the CVDC line option requires the subscribing station be a member of an IBS group. Please refer to Genband documentation for information regarding configuration and setup of EBS and IBS groups.

The following are example stations assigned the SLE options.

STNDN 996 1301LOC IS LCE 01 1 08 07

OPT SSC 1FR EMR 0 NRML RTP 0 PRES 0123 CFB CFD MD 1 CND SCA 10 SCF 10 RG SCR 10 SDR 10 MWIL CNAM SRNG

STNDN 996 1304LOC IS LCE 01 1 09 00

OPT 1FR EMR 0 DGT NRML RTP 0 EBS 1 GSCC 20 CND SCA 32 SCF 32 RG SCR 32 SDR 32 CNAM SRNG

STNDN 996 1305LOC IS LCE 01 1 08 11

OPT 1FR EMR 0 DGT NRML RTP 0 PRES 0288 CVDC IBS 1 MEM 3 MD 1 CND MWIL CNAM



When a package is deployed, the contents of the package are copied to the appropriate locations on the system. Depending on the type of APmax TM system configuration specified or the particular application(s) purchased with the system the software may be pre-loaded.




13.3.2 Outgoing AIN QueriesThe APmax TM will make outgoing AIN queries to the switch. For this to work the AIN Point Code and Translation Type must be configured on the APmax TM. If this value was not configured previously, see Section 2.2.2.6 - "SS7 Configuration", then it must be configured now.

13.3.2.1From the APmax TM UI, right-click on the system’s icon in the Command Center window to invoke a popup menu, and select the System Configuration | SS7 Configuration command. Select the General tab.

13.3.2.2Under Outgoing AIN Queries, enter the AIN Point Code. The suggested value is make this point code the same as the Local Point Code of the APmax TM. Write this value on the configuration sheet provided at the end of this chapter.

13.3.2.3Under AIN Translation Type, enter the TT value. The suggested value is 204. Write this value in Section 2.3 - "APmax TM Configuration Sheet".

13.3.2.4Close the window to save the changes.

13.3.3 Global Title TranslationsThe APmax must be equipped with the appropriate GTT entries to route queries to and from this service.

13.3.3.1From the APmax TM UI, right-click on the system’s icon in the Command Center window to invoke a popup menu, and select the System Configuration | SS7 Configuration command. Select the Global Title Translation tab.

13.3.3.2Under Global Title Table, enter the Map Number, Global Address (an entry must be made for each NPANXX or thousands group), Function Selector, Primary Route (point code of the APmax TM i.e. Local Point Code), and Alternate Route if applicable.

13.3.3.3Under Translation Type Table, enter the Translation Type (see Section 2.3 - "APmax TM Configuration Sheet", AIN Translation Type), Subsystem Number (the switch’s AIN SSN, see Section 3.2.7.3 - "AIN Subsystem Number" and Section 3.3 - "C15 Configuration Sheet"), Map Number (use the Map Number of the Global Title entry you just created), and Expansion Route if applicable.



13.3.3.4Close the window to save the changes.

13.3.4 Service Access MapThe AIN Translation Type previously defined on the APmax TM must also be set in the Service Access Map. From the APmax TM UI, right-click on the system icon in the Command Center window to invoke a popup menu, and select the System Configuration | Service Access Map command.

13.3.4.1Expand the ScreenListEdit tree. Under ScreenListEdit highlight “Tcap Response event when:”.

Figure 13-1 Service Access Map

13.3.4.2Click Add Group. Populate the window as shown. Please note, the Event needs to be set to Tcap Response. Set the Address Type to SSN. Set the Syntax Type to Freeform. Set the Access Address to the AIN Translation Type previously configured on the APmax TM.



Figure 13-2 Add Group - TCAP Response


13.3.4.4Click Add Group. Populate the window as shown. Please note, the Event needs to be set to Tcap Query. Set the Address Type to SSN. Set the Syntax Type to Freeform. Set the Access Address to the AIN Translation Type previously configured on the APmax TM.



Figure 13-3 Add Group - TCAP Query


13.3.4.6The Service Access Map should look similar to the following:



Figure 13-4 Service Access Map Complete


13.3.5 Subscriber ManagementPlease refer to the Switch Service Control Service Description for information regarding entrance of new subscribers and subscriber management. Please refer to the APmax User Manual for information regarding configuration of Internet Access Settings and web portal.

13.4 Switch Service Control Configuration SheetInformation for this service should be available on Section 3.3 - "C15 Configuration Sheet" and Section 2.3 - "APmax TM Configuration Sheet".




14. Terminating Call Management 165

14. Terminating Call Management

14.1 General DescriptionThe Terminating Call Management (TCM) service provides the subscriber with the ability to screen callers prior to terminating the call at the subscribers line. This service screens out telemarketers, polling services, auto dialers and other nuisance callers. TCM gives the subscriber control over who and when calls get delivered to their phone.

This service integrates a “Do-Not-Disturb” (DND) feature that allows a subscriber to define a time period during which incoming (terminating) calls can be restricted. Incoming calls can be completed even when restricted if the calling party inputs a specific override code.

The TCM/DND Service allows the subscriber to use a feature code or phone number to access an administrative menu from which they can add or remove a specific number, block the last calling number (subject to service settings), remove all numbers from the blocked list, add a caller to the known list or turn the service on and off. In addition, the subscriber may dial another feature code to simply block the last calling number.

This service includes a service provider option to return the Answer Indicator in the AIN message. This results in the SSP returning answer supervision for the call.

This service is self-subscribing. If a trigger is received for a DN that is not in the table, and the service has been configured as such, the service will automatically add that subscriber. This makes adding new subscribers as easy as adding the Termination Attempt (TA) trigger to the station and feature code access to the station.

The service of an AIN announcement machine is required. The APmax, configured with the Announcement system, is capable of providing the required announcements. All announcement files needed by the APmax announcement system are provided with this service. The service is equally capable if announcements are provided by switch-based mechanisms.

This chapter will assist in the switch setup for the Terminating Call Management Service. Areas of coverage in this chapter will be setup of AIN, setup of routes and trunks, and station provisioning. This chapter assumes that the DS1s and SS7 links have already been setup between the switch and the APmax TM and are functioning. Please refer to the Terminating Call Management Service Description for more information.


166 14. Terminating Call Management

14.2 Call FlowThis service is activated by reception of an AIN trigger from the switch. This trigger is either a Termination Attempt (TA) trigger when a call attempts to terminate to a subscribed line or a Feature Code (FCD) trigger when a subscriber dials a feature code or a 10-Digit Administration (DIG) provisioned in the switch. Otherwise, the service will return an Application Error with an error type of Unexpected Communication to the SSP

When the AIN trigger is received by the service, it first determines if the AIN trigger is one of the expected types. If the trigger type is not TA, FCD or DIG, the service will return an Application Error message to the switch with an error type of Unexpected Message.

If a TA trigger is received, the service must then determine whether to process the call using DND or TCM. If DND is enabled for the subscriber and the call occurs during the DND time, then the APmax TM will request an announcement to let the caller know “the number you are calling is not accepting calls”. If the calling party knows the override code, then they would enter the code and the call process will continue.

If DND is not enabled for the subscriber or is enabled and the call does not occur during the DND time, then the call will encounter TCM. Whether the call is blocked or allowed is determined by service settings.

If the service receives an FCD trigger the value of the dialed feature code is then checked against provisioned values in the APmax TM configuration table. If the dialed feature code does not match either the APmax TM value for Administration or Block Last Number feature codes, the service will return an Application Error with an error type of Unexpected Communication to the SSP.

If the service receives a 10-Digit Administration (DIG), it will be accepted for Administration Access.

14.3 Switch Setup14.3.1 Service Logic Host Route (SLHR)

Each AIN service is assigned a Service Logic Host Route. The TCM service will require two SLHR’s. One will be for the TCM/DND service, and the other SLHR will need to be created to allow the subscriber to administer their service using the FCD trigger. The SLHR’s are created in OVLY AIN. Record the SLHR numbers and TRN1 on the configuration sheet at the end of this chapter.

OVLY AIN REQ NEW SLHR SLHR 10 Number of the SLHR



14.3.2 Administrative State CodeIt is necessary to set the AIN triggers specific to the TCM/DND service. The service uses the Termination Attempt (TA) trigger. The TA trigger in the Administrative State Code (ADSC) for the SLHR must be changed to ON. This service also uses the uses the Feature Code (FCD) trigger and the 10-Digit Administration (DIG) triggers. The features TA, FCD, and DIG must be set to YES for your switch.

GTT1 010 008 001 The Point Code of the APmax TRN1 183 This is the Translation Table to be used by the GTT1

node to obtain SCCP routing information GTT2 NONE GTSC CLED Source of the GTT info that is sent to the STP to route

the message to an SCP application. CLED is used with terminating services.

OVLY AIN REQ NEW SLHR SLHR 15 Number of the SLHR GTT1 010 008 001 The Point Code of the APmax TRN1 183 This is the Translation Table to be used by the GTT1

node to obtain SCCP routing information GTT2 NONE GTSC SRCE Source of the GTT information that is sent to the STP

to route the message to an SCP application. SRCE is used with originating services.

OVLY AIN REQ CHG TYP ADSC SLHR 10 OHI OFF OHD OFF SIT OFF FCD OFF CDP OFF DIG ON The DIG trigger is used to administer the service N11 OFF TA ON TA trigger is now turned on LNP OFF

REQ CHG TYP ADSC SLHR 15 OHI OFF SIT OFF FCD ON The FCD trigger is used to administer the service CDP OFF



14.3.3 Assigning an Administration DNSubscribers to this service have the opportunity to change their service settings by dialing an administrative number. The DIG trigger is used to assign this number. The DIG DN is an unassigned number in the switch. It is recommended that the DIG DN is a 10-Digit number. The administration number is assigned to the same SLHR on which the TA trigger is enabled. Record the Administration DN on the configuration sheet at the end of this chapter.

OVLY AIN REQ NEW DIG SLHR 10 This is the SLHR assigned to the service DN 6059967003 It is recommended that the DIG DN has a reference to

the SLHR. In this case, the 10 at the end of the DN refers this DIG to SLHR 10.

14.3.4 Directory Number ProvisioningThe directory number subscribing to the TCM/DND service, needs to have the AIN trigger options assigned. Use OVLY DN to assign the option.

OVLY AIN REQ ADO STN 996 1302 OPT TA CFWN 10 FCD 15 The TA CFWN 10 is the option for the service. The

FCD 15 is the trigger which allows the subscriber to make an originating call to the service to manage the services. The 10 and the 15 indicate what SLHR the service is assigned on the switch.

14.3.5 Feature Code TranslationsIn order for the *95 and *96 to make it to the APmax TM for the TCM service administration, translation in the switch will need to be setup. The following is the PRFX translation for the * 95 and *96. The PFCD indicates to go to the SLHR for the FCD 15 indicated from the station. Record the Administration and Block Last Number feature codes on the configuration sheet at the end of this chapter.

OVLY TRNS PRFX 1 ASTR Y DIG 9 TMS 2 N OCTO N DIG 5 FCD N PRFX 0 PRFX 1 ASTR Y DIG 9 TMS 2 N OCTO N DIG 5 FCD Y PFCD IMED PRFX 1 ASTR Y DIG 9 TMS 2 N OCTO N DIG 6 SAME 5

DIG OFF N11 OFF TA OFF LNP OFF








14.4.2 AnnouncementsThe service of an AIN announcement machine is required. The APmax TM, configured with the Announcement system, is capable of providing the required announcements. All announcement files needed by the APmax announcement system are provided with this service. The service is equally capable if announcements are provided by switch-based mechanisms. The APmax TM AIN trunk settings are highlighted in Chapter 8. - "Announcements". See Section 3.2.7 - "AIN" in Chapter 3. - "Finding Information in the C15" for the AIN settings relating to the C15.

14.4.3 TCM/DND ConfigurationThe following section explains how to setup the TCM/DND Service on the APmax TM.

14.4.3.1 ConfigurationFrom the APmax TM UI, right-click on the system icon in the Command Center window to invoke a popup menu, and select the System Configuration | Terminating Call Management Configuration command. For more information on the Terminating Call Management Configuration add-on, refer to the Terminating Call Management Service Description.

14.4.3.1.1Under General, set Answer Supervision to Yes, unless desired otherwise.

14.4.3.1.2Set the Administration Feature Code and Block Last Number Feature Code as entered on the configuration sheet.



14.4.3.1.3Under Termination Attempt and Administration Feature SSN enter the SSN(s) as entered on the configuration sheet.

14.4.3.1.4When finished, close the window.

14.4.3.2 Global Title TranslationsThe APmax must be equipped with the appropriate GTT entries to route queries to this service.



14.4.3.2.3Under Translation Type Table, enter the Translation Type (set to the same value as the SSN- in our examples this is 183), Subsystem Number (in our examples this is 183), Map Number (use the Map Number configured under Global Title Table), and Expansion Route if applicable.


14.4.3.3 CLASS GTTVerify that CLASS GTT is configured. See Chapter 16. - "CLASS Global Title Translation" for more information.

14.4.4 Subscriber ManagementPlease refer to the Terminating Call Management Service Description for information regarding entrance of new subscribers and subscriber management.



14.5 TCM and DND Configuration Sheet14.5.1 AIN

14.5.1.1TA and DIG SLHR: ___________

14.5.1.2SSN (TRN1):___________

14.5.1.3FCD SLHR: ___________

14.5.1.4SSN (TRN1):___________

14.5.2Administration Number:______________________

14.5.3 Feature Codes14.5.3.1Administration Feature Code:______

14.5.3.2Block Last Number Feature Code:______




15. UCM Single Number Service 173

15. UCM Single Number Service

15.1 General DescriptionCustomers no longer need to be at home to receive a call. In fact, they can be almost anywhere. With the Innovative Systems Universal Call Management (UCM) Single Number Service, customers determine how to manage incoming calls using up to six different phone numbers to 'Find' them. This service is ideal for real estate agents, small business owners, or anyone who's always 'on the go'.

Once they receive a call, they don’t have to stay in one place to keep the conversation going. Calls from this service may be transferred between phones in the phone list by simply pressing the star key followed by the transfer digit. This allows ‘on the go’ customers to be mobile when they need to be.

In the event the customer could not be reached, the UCM Service has the added ability of forwarding calls directly to the Voice Mail Service running on the APmax TM. This feature is available to anyone that subscribes to APmax TM Voice Mail and Single Number. Best of all it does not require forwarding the call to Voice Mail through the switch. The call is handed from one service to another right in the APmax TM, meaning no additional trunks are used.

Additionally, those customers that subscribe to both APmax TM services can customize their UCM Service by recording their name in their Voice Mail mailbox. Their recorded name will be played as a part of the “searching for” announcement voiced by the UCM Service.

Administration of this service is easy, as it may be configured from Phone Central or by using the APmax TM UI.

This chapter will assist in the switch setup for the UCM Service. Areas of coverage in this chapter will be setup of AIN, setup of routes and trunks, and station provisioning. This chapter assumes that the DS1s and SS7 links have already been setup between the switch and the APmax TM and are functioning.

15.2 Call FlowCalls terminating to a UCM Service subscriber line will encounter an AIN Termination Attempt (TA) trigger. This trigger will activate the service. If the Called Party ID in the TA trigger is a subscriber to the service, then the UCM Single Number Service determines if the subscriber is also subscribed to the Terminating Call Management (TCM) service. If yes then the call is handed off internally to the TCM service for call screening. If the TCM service permits the call to continue then the service forwards the call to the administration number configured for the service. The switch intercepts this number and routes it back to the APmax for further processing.


174 15. UCM Single Number Service

Once the call reaches the APmax the service returns an Address Complete Message (ACM). The service looks at the Redirection Number in the IAM and, if valid, will try to find the subscriber based on that DN. If the Redirection Number is not valid, the service will use the Original Called Number as the subscriber DN.

Once the subscriber DN has been found, the service makes outbound calls, number of and sequence in which the calls are placed is determined by the settings.


If the following feature options are not available options please contact Genband so the feature(s) can be enabled on your switch. Features that are required for the UCM Service are as follows:

TA YES AIN Termination Attempt trigger service is enabled ISUP YES ISUP Capabilities are required SNTC YES Service Node Trunk Control

15.3.2 Service Logic Host Route (SLHR)Each AIN service is assigned a Service Logic Host Route. The SLHR is created in OVLY AIN. Record the SLHR number and TRN1 on the configuration sheet at the end of this chapter.

OVLY AIN REQ NEW SLHR SLHR 9 SLHR Number GTT1 010 008 001 APmax™ Point Code TRN1 190 This is the Translation Table to be used by the GTT1

node to obtain SCCP routing information GTT2 NONE GTSC CLED Source of the GTT information that is sent to the STP

to route the message to an SCP application. CLED is used with terminating services.

15.3.3 Administrative State CodeIt is necessary to set the AIN triggers specific to the UCM Service. Single Number uses the Termination Attempt (TA) trigger. The TA trigger is assigned in the Administrative State Code (ADSC) SLHR for the UCM Service. SLHR must be set to ON.

OVLY AIN REQ NEW CHG TYP ADSC SLHR 9



15.3.4 Trunk GroupThe UCM Service needs an incoming and outgoing ISUP trunk group. In this documentation, the following TG 175 2WAY ISUP TG is used.

Note that the actual trunk group number may be different in your configuration. Normally the trunks used for the UCM Service should be evenly split between the two APmax TM units. Record the trunk group number on the configuration sheet found at the end of this chapter.

OHI OFF OHD OFF SIT OFF FCD OFF CDP OFF DIG OFF N11 OFF TA ON LNP OFF

OVLY TG TYP TG NUM 175 Trunk Group Number TGTP 2WAY Trunk Group Type TGNM APMAX 2013 SNS Trunk Group Name MG NO SIGT ISUP Signaling Type BDRT 56 OPCX 1 DPC 010 008 001 APmax™ Point Code INBS NO AUUS NO Accept User to User Information signalling

messages for the inter-exchange carrier. AATP NO Accept Access Transport Parameter

signalling messages from the inter-exchange carrier.

PKTP DTRK SITE BASE TGDP ELOC CNFS NO SNTC YES ITXF 2010 Frequency to be transmitted to the incoming

trunk when a continuity test is being performed.

IRXF 1780 Frequency to be received for the incoming trunk when a continuity test is being performed.

COIN NOCO (Will not receive this prompt if SIGT = ISUP)



STSI 0 HNPA 605 RC 7 RTP 0 TRNL PRFX Translator Type PRFX 0 Translator Number APFX NONE Prefix to be added TRFC NONE Class of traffic incoming over the TG 4XCD NO ACKA NO Alarm Checking Access TYPC NOCO Coin Type NXX UNKN NXX of the TG LATA 640 Originating LATA of the end office served by

this TG CMCT NO TNS NO Accept call containing the Transit Network

Selection in the IAM. TGID NONE TG ID entered into the User ID parameter

when any trigger is encountered by a call originating on a trunk in this TG.

SIT NO Shared Interoffice Trigger CNAR NO Connecting Network Access Recording LRN NONE Location Routing Number TNDM NO For billing purposes: Is call connected to a far-

end office by way of Access Tandem Switch. LDAT NO UNUM REL NCKT REL CONG REL NORT REL TMPF REL NRSC REL DNCH REL DOOO REL CREJ REL PERR REL XRER REL BUSY REL OTXF 1780 ORXF 2010 CINT 1 GDTI 768 MSEC GLAR NONE If this TG controls in glare. Glare condition

exists when both ends of a 2-way are seized simultaneously.

IDLE MOST DTSI 0



15.3.5 Trunk ProvisioningNow that the trunk group has been configured, trunks will need to be added to the trunk group. Record the trunks and their CICs on the configuration sheet found at the end of this chapter.

OVLY TRK REQ NEW DTRK DTRK IS 01 3 12 05 TKTP 2WAY Trunk Type TG 175 Trunk Group Number CG NONE Carrier Group to which digital trunk is

assigned CIC 115 Circuit Identification Code associated with

trunk CGRP UNAS Number of the circuit group to which the Trunk

Group belongs. SATL NO Trunk is a Satellite Circuit

SYNC NO TRFC NONE 2RID YES EOAT NO OSNC NO ATIC NO 4XCD NO CMCO NO HOPI NO CIP NO SPN YES JIP NO BCAP DFLT OCNP YES RNP YES RIP YES CHNP YES TGMU NO TRK IS 01 3 12 05 IDLE CIC 115 IS 01 3 12 06 IDLE CIC 116 IS 01 3 12 07 IDLE CIC 117 IS 01 3 12 08 IDLE CIC 118 IS 02 3 12 05 IDLE CIC 215 IS 02 3 02 06 IDLE CIC 216 IS 02 3 02 07 IDLE CIC 217 IS 02 3 02 08 IDLE CIC 218



15.3.6 Route SetupThe following is the configuration for the Single Number route. Note that the actual route number may be different in your configuration. This route will be used to forward calls to the UCM Service. Record the route number on the configuration sheet found at the end of this chapter.

OVLY ROUT ROUT 175 Route Number ALTR CBSY Alternate Route TYPE ISUP Route Type RTNM APMAX 2013 SNS Route Name UPGR NONE Upgrade route to route ISDN calls if an all-trunks-busy

condition arises ITYP IEAS Type of ISUP call CTYP NONE Type of AMA call carried by the route LNPB NO Should this ROUT’s CTYP should be used for billing

purposes for a LNP call? Should the call be routed to a different route due to an LNP trigger.

TG 250 TG that serves the route CHG YES Is there charging supervision on this route COS NONE Type of Class of Service tone that is applied upon


digits that are deleted before outpulsing. APFX NONE Prefix to be added for outpulsing ID DFLT Identity digits FANI YES FANI codes should be sent over this route PGNC NO Peg the call as non-completing

15.3.7 Station Provisioning15.3.7.1 Directory Number ProvisioningThe Single Number subscriber’s DN must have the TA trigger assigned to it (OVLY DN - ADO) in order to route the call to the service to begin the UCM Service. The AIN option TA CFWY 9 will be added to the subscriber’s station.

STN DN 996 1604 LOC LCE 01 1 09 26 OPT 1FR EMR 0 DGT NRML RTP 0 SCA 20 TA CFWY 9

15.3.7.2 Intercept NumberThe intercept number for the service must be configured. This number will be used by the service to route the calls back to the APmax TM. This number is intercepted in the CS 1500 and routed to the new route.

DN 996 1450 Number the UCM Service uses to place calls ROUT RTE 175








15.4.2 TrunkingThe UCM Service requires configuration of in-bound and out bound trunks to the APmax TM. The following example utilizes a two-way trunk group.





Note: If supported in the switch, ensure that RLT is set to the appropriate switch type. For the CS 1500 set this to DMS10.








• The DS1 cables have been physically connected from the CS 1500 to the APmax TM (using the T1 cable assemblies, provided optionally), are properly defined, and enabled. See Section 2.2.2 - "Provisioning the APmax TM".




15.4.3 UCM Single Number ConfigurationThe following section explains how to setup the UCM Service on the APmax TM.

15.4.3.1 Configuration and Outgoing Trunk GroupsFrom the APmax TM UI, right-click on the system icon in the Command Center window to invoke a popup menu, and select the System Configuration | Universal Call Management Configuration command. For more information on the UCM Configuration add-on, refer to the UCM Single Number Service Description.

15.4.3.1.1Select SSN. Enter the SSN previously configured.

15.4.3.1.2Under Forward Numbers click Add. Enter the NPA-NXX and its associated Forward Number. Click OK. Repeat for any additional NPA-NXX’s.



15.4.3.1.3Under Outgoing Trunk Groups, click Add. Enter the Address. This address may be an NPA-NXX, 0 (all numbers), 7, or 10 digits. From the drop-down, select the outgoing trunk group to which the entered address will be mapped. Click OK. Repeat for any additional addresses.





15.4.3.2.3Under Translation Type Table, enter the Translation Type (set to the same value as the SSN- in our example this is 190), Subsystem Number (in our example this is 190), Map Number (use the Map Number configured under Global Title Table), and Expansion Route if applicable.


15.4.4 Subscriber ManagementPlease refer to the UCM Single Number Service Description for information regarding entrance of new subscribers and subscriber management.



15.5 UCM Single Number Configuration Sheet15.5.1 AIN

15.5.1.1SLHR: ___________

15.5.1.2SSN (TRN1):___________

15.5.2 Trunking15.5.2.1Route:_________

15.5.2.2Trunk Group:_________

15.5.2.3 Trunks

Table 2:

Trunk CIC

15.5.3Intercept DN:______________________


16. CLASS Global Title Translation 183

16. CLASS Global Title Translation

16.1 General DescriptionThe following details configuration of the C15 and the APmax TM to provide GTT for CLASS. This chapter assumes that the SS7 links to the APmax TM are setup and functioning.

A configuration sheet has been provided at the end of this chapter and should be used as an aid in keeping track of the required information. The following information will be retrieved and recorded:

• The translation table number and subsystem number for CLASS,

• The expansion GTT point codes for CLASS. The expansion point code is the point code of the STP that provides additional GTT beyond that configured in the APmax TM (if required).

16.2 Switch SetupThe settings in the C15 that affect CLASS are outlined. The examples used here may not exactly match the settings in your switch.

If the C15 has previously been provisioned for one or more of the features provided by the APmax TM, the following process may be used to determine the specific values for your configuration. Some of the items listed in the following examples may not be present in the C15. If this is the case, see the applicable chapter that details provisioning and configuration for the feature or service.

16.2.1 Subsystem NumberThe subsystem numbers (SSN) for the different subsystems can be found by issuing the command QUE SUB in OVLY CNFG. The C15 should respond with something similar to the following:

SUBSCMG 1SCMG 1CNAM 232LDMG 6E8S1 254E8S2 254E8S3 254E8S4 254E8S5 254


184 16. CLASS Global Title Translation

Note: The SSN to be used for each feature should be determined by the SS7 System Administrator. Although somewhat arbitrarily provided, the SSN values shown above are standardized values for intercompany use.

The CLASS subsystem number is on the line that starts with CLAS. Write the CLASS SSN number on the configuration sheet. In almost all cases, the standard value is 251.

16.2.2 Translation TableNext, determine the translation table numbers for the CLASS subsystem.

The CLASS translation table number can be found by issuing the command QUE CLAS in OVLY CNFG. The display should look similar to the following:

CLASCATG 1006 APMAX 2013 STD CLASS#TO 3#ERR 2FLSH NOCOT2 NOEDIT 2CLIC ANNCACRC CFRMACRT NUMBGTT1 010 008 001 Asks for the Point Code of the Global Title Translator.

This should be set to the PC of the APmax TM.TRN1 251 Asks for the Translations Type to be sent to the Global

Title Translator. This is normally 251.GTT2 NONE

Write the CLASS TT on the configuration sheet.

Note: The translation table (TT) to be used for each feature should be determined by the SS7 Administrator. Although somewhat arbitrarily provided, the TT value shown is a standardized value for intercompany use.

E8S6 254E8S7 254E8S8 254A0.1 10MDSI 11



Expansion GTT capability for CLASS is provided in the APmax TM, but does not need to be used. If expansion GTT is to be used, the point codes will need to be found from your SS7 provider. Write the point codes for CLASS expansion on the configuration sheet.

Now that all of the information has been found and entered on the configuration sheet, the C15 and the APmax TM can be configured.

16.2.3 Provisioning the C15The following information must be provisioned in the C15. If not already provisioned, follow the steps below to enter the information in the C15.

16.2.3.1Start the overlay in the C15.

OVLY CNFG <enter>

16.2.3.2Enter the CLASS information. The CLASS translation table number will need to be known as well.

CHG CLAS <enter>

16.2.3.2.1Press enter until the prompt displays GTT1.

16.2.3.2.2Enter the point code of the APmax TM (see the APmax TM configuration sheet).

16.2.3.2.3Press enter until the prompt displays TRN1.

16.2.3.2.4Enter the translation table number for CLASS (see the configuration sheet at the end of this chapter).

16.2.3.2.5Press enter until the data entry is finished.

16.2.3.3Set the Subsystem Numbers.

16.2.3.3.1CHG SUB <enter>

16.2.3.3.2Press enter until the prompt displays CLASS.



16.2.3.3.3Enter the subsystem number for CLASS (see the configuration sheet at the end of this chapter).

16.2.3.3.4Press enter until the data entry is finished.

Now that these values are provisioned in the C15, they also need to be set in the APmax TM.

16.3 Provisioning the APmax TM

If required, the CLASS Global Title Translation table may be entered into the APmax TM at this time. This requires the user to know all of the NPANXXs that will be serviced and the point code of the switch that will service them. The APmax TM UI can be used to enter the data. A short summary of the process is given here. For more information, see the APmax TM User Manual.

From the APmax TM UI, right-click on the system’s icon in the Command Center window to invoke a popup menu, and select the System Configuration | SS7 Configuration command. For more information on the SS7 Configuration window, refer to the APmax User Manual.

16.3.1Select the Global Title Translation tab. Within that tab select the Global Titles & Translation Types tab. Under Global Title Table click Add.

16.3.2At this point, set the Map Number, Global Address, Function Selector, Primary Route, and if applicable, Alternate Route. The point code should be provided by the SS7 provider. Repeat for each additional CLASS GTT entry.

16.3.3Under Translation Type Table, click Add. Set the Translation Type, Subsystem Number, Map Number, and Expansion Route (if applicable). See the configuration sheet at the end of this chapter for the SSN and TT values to use.

16.3.4When done, close the window to save the changes.



16.4 CLASS Configuration Sheet16.4.1

CLASS Subsystem Number:_________

16.4.2CLASS Translation Table Number: _________

16.4.3Point Code for CLASS Expansion GTT 1: ________ - ________ - ________

16.4.4Point Code for CLASS Expansion GTT 2: ________ - ________ - ________




17. Notify Plus 189

17. Notify Plus

17.1 General DescriptionThe APmax TM Notify Plus Service provides an outgoing voice message delivery capability that is ideal for automating the tedious task of calling multiple numbers to deliver the same message. Whether the message is a non-payment notice, a pending service disruption or simply a reminder of an upcoming PTA meeting the Notify Plus service is ideal for getting the message delivered.

By simply configuring a list of numbers to call, providing a recorded announcement and selecting a few calling options the service will begin calling and delivering the message. At each stage the administrator and subscriber can see the current status of the job including the number of successful deliveries, failures and remaining calls. When the job is complete the subscriber may receive a report by e-mail informing them of the final status of the calls made.

The administrator has full control over the jobs being scheduled by subscribers including the ability to limit trunk utilization and permitted calling times. The administrator may also start, pause or even cancel any subscriber jobs as required.

This chapter will assist in the switch setup for the Notify Plus Service. Areas of coverage in this chapter will be setup of AIN, setup of trunks, and station provisioning. This chapter assumes that the DS1s and SS7 links have already been setup between the switch and the APmax TM and are functioning.

17.2 Call FlowWhen a Notify Plus job is scheduled to begin the service initiates calls to one or more Destination Numbers (DNs) from a list administered by the subscriber. When a called party answers the call a previously recorded announcement is played. If the service detects a “beep” from an answering machine (or voice mail service) the announcement is restarted at the beginning to ensure that the full message is left in the subscribers message service or answering machine.

A Notify Plus subscriber must have a AIN Termination Attempt (TA) trigger assigned to a subscriber number. The subscriber line to which the TA trigger is assigned may not have any other service that also requires a TA trigger. Use of this trigger requires the assignment of one Service Logic Host Route. This Service Logic Host Route can not be used by other services.

Outgoing calls made by the service will be initially placed to this subscriber line. When the service encounters the TA trigger the call will be redirected


190 17. Notify Plus

using the AIN Forward Call message to the actual destination (the DN in the phone list). Handling the call in this manner allows the service to support toll calling, as the carrier assigned to the subscriber’s station is utilized when the calls are forwarded from the subscriber’s station.

The service will place simultaneous calls to numbers configured in the call list using a configured number of trunks and during a configured window of time. Calls that go unanswered are rescheduled for later delivery up to a configured maximum number of attempts. Calls rescheduled in this manner are spaced out over the time available in the schedule for completion. These trunks are assigned to jobs on a first come first serve basis. The service provider must ensure that a sufficient number of trunks are available and configured for the expected demand for the service. The service also supports configuring a separate Caller Id number to be used when placing calls.


If the following feature options are not available options please contact Genband so the feature(s) can be enabled on your switch. Features that are required for the Notify Plus Service are as follows:

TA YES AIN Termination Attempt trigger service is enabled ISUP YES ISUP Capabilities are required

17.3.2 Service Logic Host Route (SLHR)Each AIN service is assigned a Service Logic Host Route. The SLHR is created in OVLY AIN. Record the SLHR number and TRN1 on the configuration sheet at the end of this chapter.

OVLY AIN REQ NEW SLHR SLHR 7 SLHR Number GTT1 010 008 001 APmax™ Point Code TRN1 193 This is the Translation Table to be used by the GTT1

node to obtain SCCP routing information GTT2 NONE GTSC CLED Source of the GTT information that is sent to the STP


17.3.3 Administrative State CodeIt is necessary to set the AIN triggers specific to the Notify Plus Service. Notify Plus uses the Termination Attempt (TA) trigger. The TA trigger is


17. Notify Plus 191

assigned in the Administrative State Code (ADSC) SLHR for the Notify Plus Service. SLHR must be set to ON.

OVLY AIN REQ CHG TYP ADSC SLHR 7 OHI OFF OHD OFF SIT OFF FCD OFF CDP OFF DIG OFF N11 OFF TA ON LNP OFF

17.3.4 Trunk GroupThe Notify Plus Service needs an outgoing ISUP trunk group. In this documentation, the following TG 375 2WAY ISUP TG is used.

Note that the actual trunk group number may be different in your configuration. Normally the trunks used for the Notify Plus Service should be evenly split between the two APmax TM units. Record the trunk group number on the configuration sheet found at the end of this chapter.

OVLY TG TYP TG NUM 375 Trunk Group Number TGTP 2WAY Trunk Group Type TGTP APMAX 2013 NP Trunk Group Name MG NO SIGT ISUP Signaling Type BDRT 56 OPCX 1 DPC 010 008 001 APmax™ Point Code INBS NO AUUS NO Accept User to User Information signalling

messages for the inter-exchange carrier. AATP NO Accept Access Transport Parameter

signalling messages from the inter-exchange carrier.

PKTP DTRK SITE BASE TGDP ELOC CNFS NO SNTC YES


192 17. Notify Plus

ITXF 2010 Frequency to be transmitted to the incoming trunk when a continuity test is being performed.


COIN NOCO (Will not receive this prompt if SIGT = ISUP) STSI 0 HNPA 605 RC 7 RTP 0 TRNL PRFX Translator Type PRFX 0 Translator Number APFX NONE Prefix to be added TRFC NONE Class of traffic incoming over the TG 4XCD NO ACKA NO Alarm Checking Access TYPC NOCO Coin Type NXX UNKN NXX of the TG LATA 640 Originating LATA of the end office served by


Selection in the IAM TGID NONE TG ID entered into the User ID parameter



end office by way of Access Tandem Switch LDAT NO UNUM REL NCKT REL CONG REL NORT REL TMPF REL NRSC REL DNCH REL DOOO REL CREJ REL PERR REL XRER REL BUSY REL OTXF 1780 ORXF 2010


17. Notify Plus 193

17.3.5 Trunk ProvisioningNow that the trunk group has been configured, trunks will need to be added to the trunk group. Record the trunks and their CICs on the configuration sheet found at the end of this chapter.

CINT 1 GDTI 768 MSEC GLAR NONE If this TG controls in glare. Glare condition

exists when both ends of a 2-way call are seized simultaneously.

IDLE MOST DTSI 0 SYNC NO TRFC NONE 2RID YES EOAT NO OSNC NO ATIC NO 4XCD NO CMCO NO HOPI NO CIP NO SPN YES JIP NO BCAP DFLT OCNP YES RNP YES RIP YES CHNP YES TGMU NO TRK IS 01 3 12 05 IDLE CIC 115 IS 01 3 12 06 IDLE CIC 116 IS 01 3 12 07 IDLE CIC 117 IS 01 3 12 08 IDLE CIC 118 IS 02 3 12 05 IDLE CIC 215 IS 02 3 02 06 IDLE CIC 216 IS 02 3 02 07 IDLE CIC 217 IS 02 3 02 08 IDLE CIC 218

OVLY TRK REQ NEW DTRK DTRK IS 01 3 12 05 TKTP 2WAY Trunk Type TG 375 Trunk Group Number CG NONE Carrier Group to which digital trunk is assigned CIC 115 Circuit Identification Code associated with trunk


194 17. Notify Plus

17.3.6 Station Provisioning17.3.6.1 Directory Number ProvisioningThe Notify Plus subscriber’s DN must have the TA trigger assigned to it (OVLY DN - ADO). Outgoing calls made by the service will be initially placed to this subscriber line. When the service encounters the TA trigger the call will be redirected using the AIN Forward Call message to the actual destination (the DN in the phone list). The AIN option TA CFWY 7 will be added to the subscriber’s station.

STN DN 996 1604 LOC LCE 01 1 09 26 OPT 1FR EMR 0 DGT NRML RTP 0 PRES 0123 SCA 20 TA CFWY 7






CGRP UNAS Number of the circuit group to which the Trunk Group belongs.

SATL NO Trunk is a Satellite Circuit CTYP NONE Type of AMA call carried by the route LNPB NO Should this ROUT’s CTYP be used for billing

purposes? Should a LNP call be routed to a different route due to an LNP trigger?

TG 375 TG that serves the route CHG YES Is there charging supervision on this route COS NONE Type of Class of Service tone that is applied upon


digits that are delted before outpulsing. APFX NONE Prefix to be added for outpulsing ID DFLT Identity digits FANI YES FANI codes should be sent over this route PGNC NO Peg the call as non-completing


17. Notify Plus 195

17.4.2 TrunkingThe Notify Plus Service requires configuration of out bound trunks from the APmax TM. The following example utilizes a two-way trunk group.










196 17. Notify Plus






17.4.3 Notify Plus ConfigurationThe following section explains how to setup the Notify Plus Service on the APmax TM.

17.4.3.1 Configuration and Outgoing Trunk GroupsFrom the APmax TM UI, right-click on the system icon in the Command Center window to invoke a popup menu, and select the System Configuration | Notify Configuration command. For more information on the Notify Plus Configuration add-on, refer to the Notify Plus Service Description.

17.4.3.1.1Select SSN. Enter the SSN previously configured.

17.4.3.1.2Under Outgoing Trunk Groups, click Add. Enter the Address. This address may be an NPA-NXX, 0 (all numbers), 7, or 10 digits. From the drop-down, select the outgoing trunk group to which the entered address will be mapped. Click OK. Repeat for any additional addresses.




17.4.3.2.2Under Global Title Table, enter the Map Number, Global Address (an entry must be made for each NPANXX or thousands group), Function Selector,


17. Notify Plus 197

Primary Route (point code of the APmax TM i.e. Local Point Code), and Alternate Route if applicable.

17.4.3.2.3Under Translation Type Table, enter the Translation Type (set to the same value as the SSN- in our example this is 193), Subsystem Number (in our example this is 193), Map Number (use the Map Number configured under Global Title Table), and Expansion Route if applicable.


17.4.4 Subscriber ManagementPlease refer to the Notify Plus Service Description for information regarding entrance of new subscribers and subscriber management.


198 17. Notify Plus

17.5 Notify Plus Configuration Sheet17.5.1 AIN

17.5.1.1SLHR: ___________

17.5.1.2SSN (TRN1):___________

17.5.2 Trunking17.5.2.1Trunk Group:_________

17.5.2.2 Trunks

Table 17-1

Trunk CIC


18. Weather Plus Service 199

18. Weather Plus Service

18.1 General DescriptionThe Weather Plus Service Allows the office-wide availability of a Weather Service Announcement. Subscribers dial a 7 or 10-digit number or a feature code to access the service. See the Weather Plus Service Description for more information.

This chapter will assist in the switch setup for the Weather Plus Service. Areas of coverage in this chapter will be switch setup for routes and trunks, and intercept DN provisioning. This chapter assumes that the DS1s and SS7 links have already been setup between the switch and the APmax TM and are functioning.

18.2 Call FlowWhen a user dials the Weather Access Number the service first checks its database to determine if a valid "before" weather custom announcement is available. If one is it is played. Next, the weather announcement is played; voicing the current weather conditions. After the weather announcement is complete the service database is checked for an available "after" recorded custom announcement to play. If there is one it is played.

When a subscriber dials the Advertiser Access Number the subscriber will be asked to enter a unique subscriber identification number and a personal identification number (PIN). From the main menu the subscriber can record and review their custom announcement, stop or allow playing of the recorded message, and change their PIN number.


200 18. Weather Plus Service

Figure 18-1 Weather Plus Service Flow

INTERCEPT DN ROUTE2WAY ISUP TRUNK

GROUP APmax


If the following feature options are not available options please contact Genband so the feature(s) can be enabled on your switch. Feature bits that are required for Basic Conferencing are as follows:

ISUP YES ISUP Capabilities are required18.3.2 Trunk Group

The Conference Service needs a dedicated incoming ISUP trunk group from the switch. The APmax TM will receive incoming calls from this trunk group. In this documentation, the following TG 125 2WAY ISUP TG is used to get the call from the switch to the APmax TM. This trunk group is configured to connect to both units to provide redundancy. Note that the actual TG number may be different in your configuration. Record the trunk group number on the configuration sheet found at the end of this chapter.

OVLY TG TYP TG NUM 300 Trunk Group Number TGTP 2WAY Trunk Group Type TGNM APMAX 2013 WP Trunk Group Name MG NO SIGT ISUP Signaling Type BDRT 56 OPCX 1 DPC 010 008 001 APmax™ Point Code INBS NO AUUS NO Accept User to User Information signalling

messages for the inter-exchange carrier.



AATP NO Accept Access Transport Parameter signalling messages from the inter-exchange carrier.

PKTP DTRK SITE BASE TGDP ELOC CNFS NO SNTC YES ITXF 2010 Frequency to be transmitted to the incoming

trunk when a continuity test is being performed.


COIN NOCO (Will not receive this prompt if SIGT = ISUP) STSI 0 HNPA 605 RC 7 RTP 0 TRNL PRFX Translator Type PRFX 0 Translator Number APFX NONE Prefix to be added TRFC NONE Class of traffic incoming over the TG 4XCD NO ACKA NO Alarm Checking Access TYPC NOCO Coin Type NXX UNKN NXX of the TG LATA 640 Originating LATA of the end office served by


Selection in the IAM. TGID NONE TG ID entered into the User ID parameter



end office by way of Access Tandem Switch. LDAT NO UNUM REL NCKT REL CONG REL NORT REL TMPF REL NRSC REL



18.3.3 Trunk ProvisioningOnce the trunk group is configured, trunks need to be added to the trunk group. This is done in OVLY TRK. Below is an example for setting up trunks. Record

DNCH REL DOOO REL CREJ REL PERR REL XRER REL BUSY REL OTXF 1780 ORXF 2010 CINT 1 GDTI 768 MSEC GLAR NONE If this TG controls in glare. Glare condition

exists when both ends of a 2-way are seized simultaneously.

IDLE MOST DTSI 0 SYNC NO TRFC NONE 2RID YES EOAT NO OSNC NO ATIC NO 4XCD NO CMCO NO HOPI NO CIP NO SPN YES JIP NO BCAP DFLT OCNP YES RNP YES RIP YES CHNP YES TGMU NO TRK IS 01 2 12 21 IDLE CIC 121 IS 01 2 12 22 IDLE CIC 122 IS 01 2 12 23 IDLE CIC 123 IS 01 2 12 24 IDLE CIC 124 IS 02 2 12 21 IDLE CIC 221 IS 02 2 02 22 IDLE CIC 222 IS 02 2 02 23 IDLE CIC 223 IS 02 2 02 24 IDLE CIC 224



the trunks and their CICs on the configuration sheet found at the end of this chapter.

OVLY TRK DTRK IS 01 2 12 21 TKTP 2WAY Trunk Type TG 300 Trunk Group Number CG NONE Carrier Group to which digital trunk is assigned CIC 121 Circuit Identification Code associated with trunk CGRP UNAS Number of the circuit group to which the Trunk Group

belongs SATL NO Trunk is a Satellite Circuit

18.3.4 Route SetupThe following is the configuration for the Basic Conferencing route. Note that the actual route number may be different in your configuration. This route will be used to forward calls to the Basic Conferencing Service. Record the route number on the configuration sheet found at the end of this chapter.

OVLY ROUT ROUT 300 Route Number ALTR CBSY Alternate Route TYPE ISUP Type of Route RTNM APMAX 2013 WP Route Name UPGR NONE Upgrade route to route ISDN calls if an all-trunks-busy

condition arises ITYP IEAS Type of ISUP call CTYP NONE Type of AMA call carried by the route TG 300 TG that serves the route CHG YES Is there charging supervision on this route? COS NONE Type of Class of Service tone that is applied upon

answer from a destination DEL 0 Specifies the number of leading digits other than prefix

digits that are deleted before outpulsing. APFX NONE Prefix to be added for outpulsing. ID DFLT Identity digits FANI YES FANI codes should be sent over this route PGNC NO Peg the call as non-completing

18.3.5 Intercept DNAt least two intercept DNs must be configured on the switch. One so users can hear the weather, Weather Access Number. One for administration purposes, Advertiser Access Number. The DNs that the users call must point to the route that is set up to direct the call to Weather Plus Service on the APmax TM. They must also be unassigned DNs. The intercept DNs used in this example are 996



9328 and 996 9329. Record the intercept DNs on the configuration sheet provided at the end of this chapter.

REQ ICP DN 996 9328 ICPT ROUT Intercept Type ROUT 300 The route the intercepted calls will take REQ ICP DN 996 9329 ICPT ROUT Intercept Type ROUT 300 The route the intercepted calls will take






18.4.2 TrunkingWeather Service Plus requires configuration of an in-bound trunk group on the APmax TM. The following example utilizes a two-way trunk group.



18.4.2.1.2Click Add. Enter the Trunk Group #, Signaling Type, Trunk Group Name, Direction, and Far-end Name. If possible, use the same trunk group number as the switch. The Far-end Name will be the SS7 Route, specifically the SSP,



configured previously. See Section 2.2.2.6 - "SS7 Configuration". When finished, click OK.





18.4.2.2.1From the Trunks tab, verify the trunks are in service. If the trunks are not in service verify the DS1s are Enabled and the settings are correct. Configuration of the DS1s may be accessed from System Configuration | Trunks | Digital Carrier Configuration. The trunks should be in service if the following conditions have been met:





18.4.3 Intercept DNsThe intercept number previously defined in the switch must be also be defined in the APmax TM. From the APmax TM UI, right-click on the system icon in the Command Center window to invoke a popup menu, and select the System Configuration | Weather Service Plus command. For m ore information see the Weather Plus Service Description.



18.4.3.1 Advertiser Access Number18.4.3.1.1Select the Advertiser Configuration tab.

18.4.3.1.2Under Access Number, click Add.

18.4.3.1.3Enter the Description, intercept number defined on the switch, and Weather Announcement. Click OK.

18.4.3.2 Weather Access Number18.4.3.2.1Select the Carousel Configuration tab.

18.4.3.2.2Under Carousels, click Add.

18.4.3.2.3Enter the intercept number defined on the switch. Click OK.



18.5 Weather Plus Configuration Sheet18.5.1 Trunking

18.5.1.1Route:_________

18.5.1.2Trunk Group:_________

18.5.1.3 Trunks

Table 18-1

Trunk CIC

18.5.2Advertiser Access Number:______________________

18.5.3Weather Access Number:______________________




19. Integrated Web Portal 209

19. Integrated Web Portal

19.1 General DescriptionThe Web Portal Service provides the ability to control and configure enhanced services provided by the Innovative Systems APmax TM over the Internet. The primary purpose is to allow end-user service subscribers to view and change their service settings via a user-friendly web-browser-based interface.

The Web Portal Service provides web-browser-based user interfaces for many enhanced services on the Innovative Systems APmax TM. Any enhanced service subscriber who is Internet Access-enabled will be able to login to the Web Portal and will have access to some basic Web Portal Service interfaces. The Service Description documents associated with specific enhanced services will provide more details on the Web Portal Service interfaces available to the subscribers of each particular service.

Subscription to Integrated Web Portal provides features additional to those available in basic Web Portal.

The following services must be installed on the APmax system on which the subscriber record is located to use Integrated Web Portal:

• Voice Mail

• On-Demand Conferencing Plus

• Call Logging

• Web Portal

Areas of coverage in this chapter will be setup of AIN, setup of trunks, and station provisioning. This chapter assumes that the DS1s and SS7 links have already been setup between the switch and the APmax TM and are functioning. It is also assumed that subscribers can access the Integrated Web Portal Service.

This chapter will assist in the switch setup required for those features exclusively available with the Integrated Web Portal Service. At the time of this writing these are Real-Time Call Logging, Click-to-Call, and Conferencing Out-Dial.

19.2 Real-Time Call LoggingThe APmax TM provides Real-Time Call Logging that may be viewed using the Integrated Web Portal browser. RT Call Logging requires a TA trigger and an OHD trigger be placed on the subscriber’s line. The TA trigger is shared with Click-to-Call and Conferencing Out-dial. The OHD on the subscriber line results in the switch sending an AIN message to the APmax TM for any


210 19. Integrated Web Portal

originating traffic from the subscriber line. These messages allow the APmax TM to create a log of the subscriber’s originating calls. The TA trigger on the subscriber line results in the switch sending an AIN message to the APmax TM for any traffic terminating to the subscriber line. These messages allow the APmax TM to create a log of the subscriber’s terminating calls.

This service is compatible with and complemented by the Terminating Call Management Service (TCM/DND), Universal Call Manager (UCM) Single Number Service, Voice Mail, and On-Demand Conferencing Plus Service. If a subscriber has TCM/DND and/or UCM Single Number Service they can also have RT Call Logging as these services can share the same TA trigger.

However, it is suggested that a separate SHLR (TA trigger) be configured for RT Call Logging to allow customers who do not have TCM/DND or UCM to use the Real Time Call Logging feature provided with Integrated Web Portal.

19.3 Click-to-CallClick-to-Call requires a TA trigger be placed on the subscriber’s line. This trigger is shared with Real Time Call Logging and Conferencing Out-dial. Click-to-Call is deployed as a part of the On-Demand Conferencing Plus Service. To use this feature the subscriber must login to the Web Portal Service. See the Web Portal Service Description for more information.

Click-to-Call allows Integrated Web Portal subscribers to dial a phone number listed in their recent calls list or contacts list simply by pressing the Call button. When the Call button is pressed, a call is made to the subscriber and the number they wish to call. When the subscriber answers their line, a call is placed to the number they wish to call. Once that line answers, the APmax TM uses Release Link Trunking (RLT) to release the call to the switch if RLT has been configured. The following section explains in detail the call flow of Click-to-Call.

19.3.1 Call FlowThe APmax TM makes a call to the subscriber phone number aka the line assigned the TA trigger. The APmax TM receives the TA trigger, identifies this is a Click-to-Call based on call parameters in the SS7 message, and forwards the call to the actual destination i.e. the subscriber number. Again, the APmax TM receives the TA trigger, identifies that this is a Click-to-Call, and waits for the subscriber to answer the call. Once answered, the service places a call to the subscriber’s line, which, again, encounters the TA trigger. The APmax TM recognizes this is, again, a Click-to-Call and forwards the call to the actual destination. Forwarding the call from the subscriber line ensures the call (if toll) is billed properly.

If the default call number, as defined in Quick Settings on the Web Portal page, is a number other than the subscriber number (line assigned the TA trigger)



then the service will initiate a call to the subscriber line, intercept the TA trigger, and forward the call to the chosen default call number. Default call numbers are numbers associated with the subscriber number and are defined in the Subscriber Management add-on Address Info tab. See the APmax TM User Manual for more information. Once the station answers, the APmax TM will place another call to the subscriber line, intercept the TA trigger, and forward the call to the actual destination. After a successful Click-to-Call, the call will be released to the switch.

If the subscriber initiates a Click-to-Call while a call is in progress on their line, the APmax TM will Barge-In on the subscriber’s call, moving the call from the switch to the APmax TM. The third party will be conferenced into the call creating a three-way call. As this is now a three-way call, it is no longer considered a Click-to-Call. It is considered a Conference call. As such, this call will remain in the APmax TM and will be handled as a Conference call. RLT will not be performed.

19.3.2 ConfigurationOutbound calls utilize the outbound trunk group configured for the On-Demand Conferencing Plus service. Whether or not Release Link Trunking (RLT) is performed is determined by APmax TM trunk group settings. Additional configuration is required if Barge-In will be used to move calls from the switch to the APmax TM. Barge-In should be configured to serve the case where the subscriber line already has a call in progress and wishes to join a third-party to the call.

19.4 Conferencing Out-dialConferencing Out-dial requires a TA trigger be placed on the subscriber’s line. This trigger is shared with Real Time Call Logging and Click-to-Call. This service is deployed as a part of the On-Demand Conferencing Plus Service. To use this feature the subscriber must login to the Web Portal Service. See the Web Portal Service Description for more information.

An attendee must be present in the Conference before the Call Manager interface will display. From the Call Manager interface click Settings. Type in the 10-digit number in the Add Participant field. See the On-Demand Conferencing Plus Service Description for more information regarding the Call Manager interface.

A call will be placed to the participant and they will join the Conference call. The following section explains in detail the call flow of Conferencing Out-dial.

19.4.1 Call FlowThe APmax TM makes a call to the subscriber phone number aka the line assigned the TA trigger. The APmax TM receives the TA trigger, identifies this



is a Conferencing Out-dial call based on call parameters in the SS7 message, and forwards the call to the actual destination i.e. participant number. Forwarding the call from the subscriber line ensures the call (if toll) is billed properly.

Please note, the outgoing call is joined to the conference as soon as it is placed. All attendees will hear the ring back, etc, resulting from the call.

The RLT and Barge-in features are not utilized on Conference calls.

19.4.2 ConfigurationOutbound calls utilize the outbound trunk group configured for the On-Demand Conferencing Plus service.


If the following feature options are not available options please contact Genband so the feature(s) can be enabled on your switch. Features that are required for the Integrated Web Portal Service are as follows:

TA YES AIN Termination Attempt trigger service is enabled OHD YES AIN Off Hook Delay trigger service is enabled ISUP YES ISUP Capabilities are required SNTC YES Service Node Trunk Control

19.5.2 Service Logic Host Route (SLHR)

Two SLHRs are required for these services. The SLHRs are created in OVLY AIN. Record the SLHR numbers and TRN1s on the configuration sheet at the end of this chapter.

OVLY AIN REQ NEW SLHR SLHR 5 Number of the SLHR GTT1 010 008 001 APmax Point Code TRN1 191 This is the Translation Table to be used by the GTT1

node to obtain SCCP routing information. GTT2 NONE GTSC CLED Source of the GTT information that is sent to the STP


OVLY AIN REQ NEW SLHR SLHR 6 Number of the SLHR GTT1 010 008 001 The Point Code of the APmax



19.5.3 Administrative State CodeIn the switch, turn on the AIN triggers specific to the Integrated Web Portal Service. Integrated Web Portal features use the Termination Attempt (TA) trigger and the Off Hook Delay (OHD) trigger. These triggers must be set to ON in their respective SLHRs.

OVLY AIN REQ CHG TYP ADSC SLHR 5 OHI OFF OHD OFF SIT OFF FCD OFF CDP OFF DIG OFF N11 OFF TA ON LNP OFF

OVLY AIN REQ CHG TYP ADSC SLHR 6 OHI OFF OHD ON SIT OFF FCD OFF CDP OFF DIG OFF N11 OFF TA OFF LNP OFF

19.5.4 Station ProvisioningThe Integrated Web Portal subscriber’s DN must have the TA and OHD triggers assigned to it (OVLY DN - ADO).

TRN1 191 This is the Translation Table to be used by the GTT1 node to obtain SCCP routing information.

GTT2 NONEGTSC SRCE Source of the GTT info that is sent to the STP to route

the message to an SCP application. SRCE is used with originating services.

STN DN 996 1604



19.5.5 TrunkingPlease refer to Chapter 12. - "On-Demand Conferencing Plus Service" for more information regarding trunking and configuration of Release Link Trunking (RLT) and Barge-In for both the switch and the APmax TM.






19.6.2 ConfigurationThe following section explains how to setup the Integrated Web Portal Service on the APmax TM.

19.6.2.1 Service Access MapFrom the APmax TM UI, right-click on the system icon in the Command Center window to invoke a popup menu, and select the System Configuration | Service Access Map command. For more information, refer to the APmax TM User Manual.

19.6.2.1.1Expand the AinForwarding tree. Under AinForwarding highlight “Tcap Query event when:”.

19.6.2.1.2Click Add Group. Populate the window as shown. Please note, the Event needs to be set to Tcap Query and Routing Index must be set to 250. Set the Address Type to SSN. Set the Syntax Type to Freeform. Set the Access Address to the SSN.

LOC LCE 01 1 09 26 OPT 1FR EMR 0 DGT NRML RTP 0 OHD 6 TA CFWY 5



Figure 19-1 Add Group - TCAP Query

19.6.2.1.3Click OK. Close the window to save the changes.




19.6.2.2.3Under Translation Type Table, enter the Translation Type (set to the same value as the SSN- in our example this is 191), Subsystem Number (in our



example this is 191), Map Number (use the Map Number configured under Global Title Table), and Expansion Route if applicable.


19.6.3 TrunkingPlease refer to Chapter 12. - "On-Demand Conferencing Plus Service" for more information regarding trunking and configuration of Release Link Trunking (RLT) and Barge-In for both the switch and the APmax TM.

19.6.4 Subscriber ManagementPlease refer to the Web Portal Service Description for information regarding entrance of new subscribers and subscriber management. The Service Description documents associated with specific enhanced services will provide more details on the Web Portal Service interfaces available to the subscribers of each particular service.



19.7 Integrated Web Portal Configuration Sheet19.7.1 AIN

19.7.1.1TA SLHR: ___________

19.7.1.2SSN (TRN1):___________

19.7.1.3OHD SLHR: ___________

19.7.1.4SSN (TRN1):___________




20. Originating Call Management 219

20. Originating Call Management

20.1 General DescriptionThis service is an combination of the functionality of the Account Code Billing, Budget Toll, and Originating Call Manager services previously available from Innovative Systems, L.L.C.

Stations subscribing to this service will be assigned an AIN station option to perform the Off Hook Delay trigger upon call origination. This trigger will activate the service in the APmax TM. This is an originating service only.

The service is self-subscribing. If the service receives a query from the switch and does not have a record for the subscriber, the service will add the subscriber with an Originating Call Manager feature set using default values and a PIN of 0000. The PIN can be changed over the phone or through the Web Portal interface. If something other than the defaults are desired, the configuration for that subscriber must be changed through the web portal interface or the APmax TM UI.

The service of an AIN announcement machine is required. The APmax TM, configured with the Announcement system, is capable of providing the required announcements. All announcement files needed by the APmax TM announcement system are provided with this service. The service is equally capable if announcements are provided by switch-based mechanisms.

This chapter will assist in the switch setup for the Originating Call Management Service. Areas of coverage in this chapter will be setup of AIN, setup of routes and trunks (if applicable), and station provisioning. Please refer to the Originating Call Management Service Description for more information.

Be advised, this service uses the APmax TM Is Toll service to determine the toll status of a call and, so, installation of the Is Toll service is required as is configuration of Toll Call Management (see APmax User Manual for more information on Toll Call Management).

20.2 Call Flow20.2.1 Account Code

The Account Code Plus Service is used to allow account code information to be included with the subscriber’s bills. The account code information is entered by the subscribers when placing most toll calls. The account code is verified against a predefined list of account codes that are valid for that subscriber. When a customer with this feature makes a call, the directory number queries the APmax TM to determine if the call is a toll call. If a toll call, then the APmax TM will stop the call process and request an announcement to


220 20. Originating Call Management

enter an account code. The APmax TM will then verify the account code. Once verified, the call process is continued and billing information is generated.

20.2.2 Budget TollThis feature allows telephone companies to limit toll usage of specific stations to a fixed number of minutes. Calls will be timed using AIN methods by the APmax TM. A subscriber to this feature will be allocated a number of minutes of toll service. If budget toll operation is not desired, the subscriber can be assigned “infinite minutes” thus disabling this feature.

If the subscriber has more than 90 seconds remaining and barge in is enabled, the APmax TM will allow the call to be routed and the switch will route the call to its destination. If there are less than 90 seconds remaining and barge in enabled, the APmax TM will play an appropriate announcement and the call will be disconnected. When barge-in is enabled, calls in progress will be disconnected when time expires.

Regardless of the barge-in status, if the subscriber has used all available minutes, the APmax TM will play an appropriate announcement and the call will be disconnected. An announcement indicating the number of minutes remaining will be provided to the caller when toll calls are originated with less than 100 minutes remaining.

In order to use this feature, the SNTC (Service Node Trunk Control) Feature Bit is required on the switch.

20.2.3 Originating Call ManagementOriginating Call Management allows subscribers to control originating calls. When a customer with this service makes a call, the APmax TM verifies if the call is allowed or blocked. If blocked, then an announcement will be generated that indicates that the call is not allowed on this phone. A PIN may be entered to continue the call process.


If the following feature options are not available options please contact Genband so the feature(s) can be enabled on your switch. Features that are required for the OCM Service are as follows:

OHD YES AIN Off Hook Delay trigger service is enabled. DIG YES AIN 10-Digit Administration trigger service is enabled. ISUP YES ISUP Capabilities are required for barge in. SNTC YES Service Node Trunk Control is required for barge in.



20.3.2 Create Service Logic Host Route (SLHR)Each AIN service is assigned a Service Logic Host Route (SLHR). The SLHR is created in OVLY AIN. Record the SLHR numbers and TRN1 on the configuration sheet at the end of this chapter.

OVLY AIN REQ NEW SLHR SLHR 13 SLHR Number GTT1 010 001 008 APmax Point Code TRN1 173 This is the Translation Table to be used by the GTT1

node to obtain SCCP routing information

GTT2 NONE GTSC SRCE Source of the GTT information that is sent to the STP

to route the message to an SCP application. SRCE is used with originating services.

20.3.3 Administrative State CodeIt is necessary to set the AIN triggers specific to the OCM service. The OCM uses the Off Hook Delay (OHD) and the 10-Digit Administration (DIG) triggers. The OHD and DIG triggers are in the Administrative State Code (ADSC) for the OCM SLHR must be changed to ON.

OVLY AIN REQ CHG TYP ADSC SLHR 13 OHI OFF OHD ON The OHD trigger stops the call process and sends

query to AP SIT OFF FCD OFF CDP OFF DIG ON The DIG trigger is used to allow subscribers to call an

administration number to change their PIN or to obtain how many minutes of unused toll remain (if applicable).

N11 OFF TA OFF LNP OFF

20.3.4 Assigning an Administration DN for OCMThe DIG trigger is used to assign the administration number. The DIG DN is an unassigned number in the switch. It is recommended that the DIG DN is a 10-Digit number. The administration number is assigned to a SLHR for the



OCM service. Record the Administration DN on the configuration sheet at the end of this chapter.

OVLY AIN REQ NEW DIG SLHR 13 This is the SLHR assigned to the OCM service DN 6059967013 It is recommended that the DIG DN has a reference to

the SLHR. In this case, the 13 at the end of the DN refers this DIG to SLHR 13.

20.3.5 Directory Number ProvisioningThe directory number subscribing to the OCM service needs to have the AIN trigger option assigned. Use OVLY DN to assign the option.

OVLY DN REQ ADO STN 996 1302 OPT OHD 13 The 13 at the end of the option indicates what SLHR

the service is assigned on the switch.

20.3.6 Barge-InBarge-In requires a call to be established within the APmax TM prior to the “move” of a call from the switch to the APmax TM.

At least one two-way trunk group must be provisioned per APmax TM unit to support use of the Barge In feature. Each two-way trunk group must contain at least two trunks.

Note: These TGs are in addition to the two-way trunk group configured for On-Demand Conferencing.

It is suggested that there be two TGs on the switch and two TGs on the APmax TM. These TGs should be used exclusively for the Barge-In calls.

One barge-in trunk group will contain trunks only connected to APmax TM Unit 1 to ensure calls on this TG route to Unit 1. The other barge-in trunk group will contain trunks only connected to APmax TM Unit 2 to ensure calls on this TG route to Unit 2 (see 12.3.2). Each barge-in TG should contain at least two trunks (see 12.3.3).

Each barge-in trunk group requires a route. This route shall route the call to the appropriate TG (see 12.3.4).

The switch will intercept the barge-in call based on the called number. This requires two intercept numbers be defined in the switch. Calls to these Barge In DNs shall be intercepted and routed to the proper unit (see 12.5.2).



Please record these values on the configuration sheet provided at the end of this chapter.


APmax packages contain the tables and files necessary to provision features for APmax systems. When a package is deployed, the contents of the package are copied to the appropriate locations on the system. Depending on the type of APmax TM system configuration specified or the particular application(s) purchased with the system the software may be pre-loaded.

Be advised, this service uses the APmax TM Is Toll service to determine the toll status of a call and, so, installation of the Is Toll service is required as is configuration of Toll Call Management. Please refer to the APmax User Manual for more information on Toll Call Management.


20.4.2 AnnouncementsThe service of an AIN announcement machine is required. The APmax TM, configured with the Announcement system, is capable of providing the required announcements. All announcement files needed by the APmax announcement system are provided with this service. The service is equally capable if announcements are provided by switch-based mechanisms. The APmax TM AIN trunk settings are highlighted in section 8. (see section 3.2.7).

20.4.3 OCM ConfigurationFrom the APmax TM UI, right-click on the system icon in the Command Center window to invoke a popup menu, and select the System Configuration | OCM Configuration command. For more information on the OCM Configuration add-on, refer to the Originating Call Management Service Description.

20.4.3.1Under OCM Properties, set Auto Allow Subscriber to Yes, unless desired otherwise.

20.4.3.2Set Allow Barge In to Yes, unless desired otherwise, and proceed to the following sub-steps. If set to No, skip to the next step.

20.4.3.2.1Enter the Barge-In DN for Unit 1.



20.4.3.2.2Enter the Barge-In DN for Unit 2.

20.4.3.2.3Under Outgoing Trunk Groups, click Add. Enter the appropriate Address and Trunk Group. These settings are required to utilize Barge-In.

20.4.3.3Under AIN Configuration, enter the SSN as entered on the configuration sheet.

20.4.3.4When finished, close the window.




20.4.3.5.3Under Translation Type Table, enter the Translation Type (set to the same value as the SSN- in our examples this is 173), Subsystem Number (in our examples this is 173), Map Number (use the Map Number configured under Global Title Table), and Expansion Route if applicable.


20.4.3.6 CLASS GTTVerify that CLASS GTT is configured (see section 16. for more information).

20.4.4 Subscriber ManagementPlease refer to the Originating Call Management Service Description for information regarding entrance of new subscribers and subscriber management.



20.5 OCM Configuration Sheet20.5.1 AIN

20.5.1.1OHD and DIG SLHR: ___________

20.5.1.2SSN (TRN1):___________

20.5.2Administration Number:______________________

20.5.3 Barge In

Table 20-1

Unit APmax TG Switch TG Route Intercept Number

Table 20-2

APmax TG Switch TG Trunk CIC




227

List Of Terms

APAC APmax TM Administration Center. The SMS system for the APmax TM.

CLASS Custom Local Area Signaling Services (CLASS is a Service Mark of Bellcore)

GTT Global Title Translation

NA Not Applicable

OPC Originating Point Code

SCP Service Control Point. An SS7 Database

SLHR Service Logic Host Route

SLP Service Logic Program. The program which implements AIN Services

SMS Service Management System

SSP Service Switching Point - A switch with SS7

TCAP Transaction Capabilities Application Part. The application level communication protocol used on SS7


228 List Of Terms

715000.01 Proprietary June 2012 Using Your APmax with the C15 User Manual

229

Bibliography

Genband. C15 Compact Softswitch Data Modification Manual - Part 1 of 2. 297-3102-903P1.Version 7.02. March 2011.

Genband. C15 Compact Softswitch Data Modification Manual - Part 2 of 2. 297-3102-311P2. Version 7.02. March 2011.

Genband. C15 Compact Softswitch Maintenance Diagnostic Input Manual. 297-3102-506. Version 7.02. March 2011.

Innovative Systems, L.L.C., APmax User Manual Release 4.0 Document 715010

Innovative Systems, L.L.C., Automated Call Distributor Service Description Document SD1335

Innovative Systems, L.L.C., Automated Configuration Service Service Description Document SD1334

Innovative Systems, L.L.C., C15 Announcements 3.0 Service Description Document SD1200

Innovative Systems, L.L.C., Calling Name 4.0 Service Description Document SD1300

Innovative Systems, L.L.C., Voice Mail/Unified Messaging 5.0 Service Description Document SD1090

Innovative Systems, L.L.C., Basic Conferencing Service Description Document SD1010

Innovative Systems, L.L.C., On-Demand Conferencing Plus Service Description Document SD1100


230 Bibliography

Innovative Systems, L.L.C., Call Logging Portal Service Description Document SD1160

Innovative Systems, L.L.C., Switch Service Control 3.0 Service Description Document SD1250

Innovative Systems, L.L.C., Terminating Call Management Service Description Document SD1150

Innovative Systems, L.L.C., UCM Single Number Service Service Description Document SD1170

715000.01 Proprietary June 2012 Using Your APmax with the C15 User Manual

231


232


Documents

Using Your APmax with the C15 - Innovative Systems - Using Your APmax with... · 2012-08-08 · 1. Introduction 1 June 2012 Innovative Systems, L.L.C. Proprietary 715000.01 Using