Step by Step Adding Public Trunk Group (ISDN-PRI interface) 1.

Insert the appropriate circuit packs/media module into the available gateway slot

Note : make sure that the card is detected using the command List Configuration All. We will continue using this board address as an example for the rest of the document 2. Configure the ds1 interface

1|Page

2.1 Type add ds1 0102. Press Enter. The DS1 Circuit Pack screen appears. You must enter a specific port address for the circuit pack. 2.2 In the Name field, type the preffered name to distinguish such as Telkom Line 52x. Use this name to record useful information such as the type of trunk group associated with this circuit pack or its destination. 2.3 In the Bit Rate field, type 2.048. This is the standard for E1 lines for Telkom Indonesia. 2.4 In the Line Coding field, type hdb3. Avaya recommends you use hdb3. 2.6 In the Signaling Mode field, type isdn-pri. 2.7 In the Interface Companding field, type alaw. Also use Idle code 01010100 This is the standard for E1 lines in Indonesia. 2.8 Press Enter to save your changes.

Note: all the parameters above are common use in avaya environment involving Telkom Indonesia provider. Differ provider may using differ parameter and we strongly suggest that our field engineer do the configuration 3. Create a new signaling group

2.1 Type add signaling x.(replace the x with the available signaling number in the system) Press Enter.You must enter a specific Dchannel port address for the circuit pack (01a0117) 2.2 We will fill the Trunk Group for Channel Selection command after we create the trunk group in the next step. 2.3 Press Enter to save your changes.

2|Page

4. Create the trunk group

1. Type add trunk-group next. Press Enter. The Trunk Group screen - page 1 appears. The system assigns the next available trunk group number to this group. In our example, were adding trunk group 5. 2. In the Group Type field, type isdn. This field specifies the kind of trunk group youre creating 3. In the Group Name field, type Telkom 5x to distinguish the name This name will be displayed, along with the group number, for outgoing calls if you set the Outgoing Display? field to y. You can type any name up to 27 characters long in this field. 4. In the COR field, type 1. This field controls which users can make or receive calls over this trunk group. Assign a class of restriction thats appropriate for the COR calling permissions administered on your system. 5. In the TAC field, type 630. This field defines a unique code users can dial to access this trunk group. 6. In the Direction field, type two-way. This field defines the direction of traffic flow on this trunk group. 7. In the Night Service field, type 1234. This field assigns an extension to which calls are routed outside of business hours. 8. In the Service Type field, type tie. 9. In the Carrier Medium field, type ISDN/PRI. 10. Fill the signaling number and number of trunk members in page 5 (use the signaling number in previous step). For trunk members use the port address 01020111. Press Enter to save your changes.

3|Page

Step by Step Adding Partitioning and Routing 1. Configuring COR (Class Of Restriction)
Use this screen to establish classes of restriction (COR). Classes of restriction control call origination and termination. Your system might use only one COR or as many as necessary to control calling privileges. You can assign up to 995 different CORs. Consider the following to enhance your system security: 1. Assign a separate COR to incoming and outgoing trunk groups, then restrict calling between the two groups. 2. Limit the calling permissions as much as possible by setting appropriate Calling Party Restrictions and Facility Restriction Levels (FRLs).

Field descriptions for page 1

Access to MCT? This field refers to Malicious Call Trace. Valid entries Usage Y Enter y to allow permissions to activate a request to trace a malicious call. N Entering n prohibits this user from requesting a malicious call trace, but does not prevent this extension from appearing in the MCT History report, should this extension be the subject of a malicious call trace. Add/Remove Agent Skills Valid entries Usage y/n Enter y to allow users with this COR to add and remove skills. APLT Valid entries y/n

Usage Enter n to allow access to APLT trunk group Enhanced Private Switched Communications System (EPSCS) or Common Control Switched Arrangement (CCSA) off-net facilities.If fully restricted service is enabled, set this field to n .

4|Page

Automatic Charge Display Shows the cost of an active outgoing call using Periodic Pulse Metering (PPM) or ISDN Advice of Charge (AOC) on Digital Communications Protocol (DCP) or Avaya BRI stations. Not available in the U.S Valid entries Usage Displays call charges during and at the end of the call. Y Call charges can be seen if users press the disp-chrg button before the call drops. N Called Party Restriction Valid entries Usage Blocks the calling party from receiving incoming exchange network calls, attendant originated calls, and Inward attendant completed calls. Blocks the called party from receiving all calls except for those originated or extended by the attendant. Manual Blocks the called party from receiving public network calls. Attendant calls are allowed to go through to the Public called party as well as attendant-assisted calls if the Restriction Override field in the public restricted stations COR is attd or all . Blocks the called party from receiving any calls at any time. Termination No called party restrictions. None Calling Party Restriction This field determines the level of calling restriction associated with this COR. Note: To enhance system security, limit calling permissions as much as possible. Valid entries Usage Blocks the calling party from originating a call from the facility at any time. The party can only receive calls. A Origination telephone with this COR can initiate Remote Access calls, if the COR of the barrier code allows it. Blocks the calling party from calling outside the private network. Users can dial other users on the same server Outward running Avaya Communication Manager or within a private network. To enhance security, Avaya recommends that you use outward restrictions when practical. Blocks the calling party from making ARS and trunk access calls from a facility assigned the COR to certain toll All-toll areas as defined in the Dialed String field on the Toll Analysis screen. The Dialed String field must be marked as being associated with the systems Toll List. The call completes if the facilitys COR also is associated with an Unrestricted Call List and whose Dialed String field also matches the dialed number. Blocks the calling party from making trunk access calls from the facility assigned the COR to certain toll areas as Tac-toll defined in the Dialed String field on the Toll Analysis screen. The Dialed String field must be marked as being associated with the systems Toll List. The call completes if the facilitys COR also is associated with an Unrestricted Call List and whose Dialed String field also matches the dialed number. No calling party restrictions. None Can Be a Service Observer If you want an observer to observe users, set the users CORs to y on the observers COR Service Observing Permission table. ! SECURITY ALERT: The use of Service Observing features might be subject to federal, state, or local laws, rules, or regulations; or require the consent of one or both of the parties to SE CU RI TY ALER T:the conversation. Customers should familiarize themselves with and comply with all applicable laws, rules, and regulations before using these features. Note: You cannot enter y in the previous two fields unless Service Observing (Basic) is enabled on the System Parameters customer-Options (Optional Features) Valid entries Usage Enter y if users with this COR can service observe other users. y/n Can Be Picked Up By Directed Call Pickup Valid entries Usage Enter y to allow this Stations or EAS agents calls to be y/n picked up by using the Directed Call Pickup Up feature. Before you can set this field to y , you must set Directed Call Pickup on the Feature-Related System Parameters screen to y. Can Be Service Observed Note that this field allows or denies service observing for not only physical extensions, but also for logical agent IDs and VDNs. If you want an observer to observe users, set the users CORs to y on the observers COR Service Observing Permission table Valid entries Usage Enter y if users with this COR can be service observed. y/n

5|Page

Can Change Coverage Valid entries Usage Enter y to allow station users with this COR to select one of two previously administered coverage paths or to y/n activate, change, or deactivate call forward all calls or call forward busy/dont answer from any on-site or off-site location. Can Use Directed Call Pickup Valid entries Usage Enter y to allow the station, attendant, or EAS agent to pick up calls using the Directed Call Pickup feature. Set y/n Directed Call Pickup on the Feature-Related System Parameters screen to y to set this field to y . COR Description Valid entries Usage Up to 35 Enter a description of the COR that indicates how you use it. If you make characters this as clear as possible (for example, Customer Service, Finance Department), it will be easier to remember which COR to assign when you add users. COR Number This is a display-only field when the screen is accessed via an administration command such as change or display . Displays the COR number. Direct Agent Calling Valid entries Usage If this is y , users can dial an ACD agents extension directly, rather than anyone in the agent pool. If the system y/n is in Night Service, the call routes to the Night Service extension. If the extension with this COR belongs to an agent, the agent can receive calls directly. Facility Access Trunk Test An associated feature button ( trk-ac-alm ) status lamp lights when a successful test attempt occurs. Pressing one of the alarm buttons (ten maximum) when its associated status lamp is lit turns off all lamps on all buttons whether the access is still in progress or has completed Valid entries Usage Enter y to allow users with this COR to perform Facility Access Trunk Tests. y/n Forced Entry of Account Codes FEAC must be enabled on the System Parameters Customer-Options (Optional Features) screen and on the CDR System Parameters screen. Note: If a COR requiring entry of account codes is assigned a VDN, the route to commands executed by the associated vector will not be successful. No t Valid entries Usage Enter y to indicate that an account code must be dialed when making outgoing trunk calls. If this is y , y/n any telephone assigned the associated COR must dial an account code before making an outgoing call. If you set this to y for a COR assigned to a trunk group, users must dial account codes before calling out over that trunk group. This might be useful for trunks used in international calls, and those that are more expensive. If a call is being routed by ARS, account code checking is not done on the COR. FRL Valid entries 0 to 7

Usage Enter an originating FRL number. AAR and/or ARS features use this entry to determine call access to an outgoing trunk group. Outgoing call routing is determined by a comparison of the FRLs in the AAR/ARS Routing Pattern and the FRL associated with the COR of the call originator (typically, a telephone user). An originating FRL of 0 has the least calling privileges. To enhance system security, assign the lowest possible FRL.

Fully Restricted Service Note: If this field is enabled, the APLT field must be n . Valid entries Usage When y entered for a given COR, stations assigned that COR will not have access to the public network for y/n either incoming or outgoing calls.

6|Page

Group II Category For MFC This field always controls categories for Russian signaling trunks. It can control categories for R2-MFC signaling trunks, depending on the value of the Use COR for Calling Party Category field on the Multifrequency-Signaling-Related System Parameters screen. The Calling Party Category digit administered in this field is included as part of the ANI information sent to the Central Office on request using R2-MFC signaling Valid entries Usage 1 to 10 Enter the value you want the server running Avaya Communication Manager to send as the Calling and/or Called Party Category for telephones or trunks that use this COR. Group Controlled Restriction A display-only field that determines if the current COR is under controlled restriction. This field can help troubleshoot problems by first checking its value. Valid entries Usage indicates the COR is controlled restricted Active indicates the COR is not controlled restricted Inactive Hear System Music on Hold Valid entries Usage Enter y to allow the Music on Hold feature to be activated by a telephone. y/n Hear VDN of Origin Announcement Valid entries Usage Enter y if users with this COR can receive VDN of Origin messages. y/n MF ANI Prefix Defines the prefix to apply to an extension number when ANI is sent to the CO. This overrides any ANI prefix administered on the Multifrequency Signaling screen. This does not apply when ANI is tandemed through the Communication Manager server on tandem calls. This field also applies to the ANI for the server when the originating side is a trunk and there was no ANI. Valid entries Usage 1 to 7 digits or blank If you want the entire number to display on the receiving end, enter all digits except the extension number. Partitioned Group Number This field appears only if AAR/ARS Partitioning is y and Time of Day Routing is n on the System Parameters CustomerOptions (Optional Features) screen. Valid entries Usage 1 to 8 Enter the AAR/ARS partitioned group number associated with this COR. PASTE (Display PBX Data on telephone) Valid entries Usage Enter y to download all lists. Enter n to disallow the PASTE feature. y/n Priority Queuing Valid entries Usage Enter y to allow the telephone users calls to be placed ahead of non-priority calls in a hunt group queue Y If you do not use Automatic Call Distribution (ACD is not enabled on the System Parameters CustomerN Options (Optional Features) screen), this field must be n . Restricted Call List This list can be used whether the COR is toll restricted. The Restricted Call List (RCL) has priority over the Toll Analysis Unrestricted Call List (UCL). A call attempt from a facility assigned a COR (with RCL field set to y ), whose dialed digit string is on the Toll Analysis screen and is marked as being associated with the RCL, will be denied. Valid entries Usage Enter y to specify that this COR will have access to the systems Restricted Call List y/n

7|Page

Restriction Override Allows the specified users to bypass restriction on conference, transfer or call forwarding operations. Valid entries Usage A telephone with a COR that is inward restricted cannot receive public network, attendant-originated, or Attendant attendant-extended calls. Enter attendant to give your attendants the ability to override this restriction. Enter all if you want all of the users with this COR to override inward restrictions. All Enter none if you do not want any users of this COR to bypass the restrictions. None Send ANI for MFE Only applicable for Spain. Valid for 2/6 signaling, but not 2/5 signaling. The following field appears only if Expert Agent Selection (EAS) is enabled on the Feature-Related System-Parameters screen. Valid entries Usage Enter y to enable Automatic Number Identification (ANI). When the value is y , Avaya Communication Y Manager sends the calling partys number to the public or IBERCOM network so that charges will be broken down by line. If this value is n , charges are not itemized by line, and your company will receive a single bill for the total N number of calls made (block charging). Time of Day Chart Appears only if Time of Day field is enabled on the System Parameters Customer-Options (Optional Features) screen. Valid entries Usage 1 to 8 Enter the AAR/ARS time-of-day-chart number associated with this COR. Unrestricted Call List Any entry on the Toll Analysis screen with an X in the Toll List column is restricted, meaning that the system blocks any attempt to complete a call containing the Dialed String. However, this field overrides that restriction.For example, if the Toll Analysis screen shows a Dialed String entry of 538 and there is an X in the Toll List column, the 538 number is restricted. To override this restriction, in the Toll Analysis screen, enter X in the 5 column under the Unrestricted Call List heading. In the Class of Restriction screen, in this field, enter 5 to complete the restriction override. Valid entries Usage 1 to 10 or blank Appears when Calling Party Restriction is all-toll or tac-toll . This field allows a user to complete a toll call with "restricted" dialed digits. This field is associated with the Dialed String field on the Toll Analysis screen. An Unrestricted Call List number is denoted on that screen.

8|Page

2. Configuring Time-Of-Day
Time of Day Routing lets you redirect calls to coverage paths according to the time of day and day of the week. You need to define the coverage paths you want to use before you define the time of day coverage plan. You can route calls based on the least expensive route according to the time of day and day of the week the call is made. You can also deny outgoing long-distance calls after business hours to help prevent toll fraud. Time of Day Routing applies to all AAR or ARS outgoing calls and trunks used for call forwarding to external numbers.

Note: use the command change time-of-day x (where x is related with the Time of Day Chart in COR page 1). Pay attention to PGN# since this will be reffered in next step (partioning) Hereby are an example to make it more clear. Example For this example, assume the following: Jim is the user at extension 1234. Extension 1234 is assigned a COR of 2. COR 2 is assigned a Time of Day Plan Number of 1. The Time of Day Routing Plan 1 is administered as shown in the example above. When Jim comes into work on Monday morning at 8:30 and makes an ARS call (dials the ARSaccess code followed by the number of the person he is calling), the system checks the Time of Day Plan Number assigned to Jims COR. Because Jim has a COR of 2 with Time of Day Plan Number 1, the system uses Time of Day Routing Plan 1 to route the call. According to Time of Day Routing Plan 1, calls made between 8:00 a.m. and 11:59 a.m. route according to the route pattern set up on PGN 1. If Jim makes a call between 12:00 p.m. and 1:00 p.m. on Monday, the Time of Day Routing Plan 1 is used again. However, this time the call is routed according to PGN 2.

9|Page

3. Configuring Partition Route Table

Use this table to identify routing for partition groups associated with an ARS analysis entry.

PGN 1 (through PGN 8) Enter the routing for each partition group associated with each route index number. Valid entries Usage 1 to 640 Specifies the route pattern used to route the call r1 to r32 Specifies the remote home numbering plan area table used to route the call node Designates node number routing deny Blocks the call

10 | P a g e