Nitsuko 124i/384i Software Manual
Have a look at the manual Nitsuko 124i/384i Software Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 57 Nitsuko manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
Programming (Cont’d) ➣ (384i Only) 0005 - Extension Circuit Type Assign circuit type 2 for keysets with DCI. Assign circuit type 4 for 3DCI module. ➣0007 - System Report Port Setup If the SMDR printer will also be used for system reports, enter the SMDR DCI software port number as the system report port number. ➣0008 - Alarm Report Port Setup If the SMDR printer will also be used for alarm reports, enter the SMDR DCI software port number as the alarm report port number. ➣0130 - Date Format for SMDR and System Reports Set the date format for SMDR (0=American, 1=European or 2=Japanese). ➣0404 - SMDR Options, Item 1: Omit (Mask) Digits Enter the number of digits (1-24) you want SMDR to block (i.e., X out). Enter 0 not to block any digits. ➣0404 - SMDR Options, Item 2: Minimum Number of SMDR Digits Enter the minimum number of digits a user must dial (1-24) before the system includes a call on the SMDR report. Enter 0 to include all outgoing calls, regardless of the number of digits dialed. ➣0404 - SMDR Options, Item 3: SMDR Printer Output Port Enter the software port number of the DCI assigned to the SMDR printer. ➣0404 - SMDR Options, Item 4: Minimum Call Duration Enter the minimum duration of a call (1-65535) that will print on the SMDR report. Enter 0 to have calls of any duration print. ➣0404 - SMDR Options, Item 5: Minimum Ringing Time Enter how long an unanswered call must ring (1-65535) before SMDR logs it as No Answer). Enter 0 to allow all No Answer calls to print. ➣0404 - SMDR Options, Item 6: Print Item 1 (Toll Restricted Call) Enter 1 if you want the SMDR report to include calls blocked by Toll Restriction. Enter 0 to exclude blocked calls. ➣0404 - SMDR Options, Item 6: Print Item 2 (Extension Calls) If system is behind a PBX, enter 1 to have SMDR include all calls to the PBX. Enter 0 to have SMDR in- clude only calls dialed using PBX trunk access code. ➣0404 - SMDR Options, Item 6: Print Item 3 (Extension Data Call) Enter 1 if you want the SMDR report to include internal data calls. Enter 0 if you want the SMDR report to exclude internal data calls. ➣0404 - SMDR Options, Item 6: Print Item 4 (Daily Summary), Print Item 5 (Weekly Summary) and Print Item 6 (Monthly Summary) Enter 1 to enable a summary report. Enter 0 to disable a summary report. The daily report prints every day at midnight. The weekly report prints every Sunday night at midnight. The monthly report prints at midnight on the last day of the month. ➣0404- SMDR Options, Item 6, Print Item 8 (Incoming Calls) Enter 0 if you want the SMDR report to include incoming calls. Enter 1 if you want the SMDR report to exclude incoming calls. ➣0404 - SMDR Options, Item 6, Print Item 9 (Print Name or Number) Enter 0 if you want the SMDR report to include the extension’s name. Enter 1 if you want the SMDR re- port to include the extension’s number. ➣0503 - DCI Extension Number Assign an unused extension number (e.g., 500) to the DCI port assigned to SMDR. ➣0901 - Basic Trunk Port Setup (Part A), Item 13: SMDR Print Out For each trunk, enter 0 if trunk’s calls should appear on SMDR report. Enter 1 if trunk’s calls should not appear on SMDR report. ➣1008 - Basic Extension Port Setup (Part B), Item 1: SMDR Printout For each extension, enter 1 if extension’s calls should appear on SMDR report. Enter 0 if extension’s calls should not appear on SMDR report. Features N-Z Station Message Detail Recording 92000SWG08 Issue 1-0FEATURES 481
Programming (Cont’d) ➣ 1201 - DCI Setup, Type 1, Item 1, Register 65 Set the DCI communications parameters to match the SMDR device. ➣1202 - DCI Port Type Set this option to 1 if SMDR device is serial. Set this option to 2 if SMDR device is Centronics parallel. ➣1206 - Initialize DCI Initialize the DCI port selected for SMDR. Related Features PBX Compatibility To use the PBX Call Reporting option, program system for behind PBX operation. Traffic Management Report (TMS) Traffic Management Reports and SMDR should not use the sameDCI port. Tr a n s f e r The extension that initially answers or places a call owns the SMDR record for the call. For example, if extension 318 transfers a trunk call to extension 320, the SMDR record assigns the entire call to exten- sion 318. Extension 320 does not show on the SMDR record as part of the transferred call. Year 2000 Compliance The SMDR page and summary banners show four digis for the year (e.g., 2001). Operation Once installed and programmed, SMDR operation is automatic. Features N-Z Station Message Detail Recording 482 FEATURES92000SWG08 Issue 1-0
T1 Trunking (with ANI/DNIS Compatibility) Description 124i Available — Basic T1 capabilities require EXCPRU version 2.18 or higher. T1 DID and tie lines require a DTDU PCB. 384i Available — Customizing the CODEC Gain Types requires system software 3.04 or higher. - ANI/DNIS Compatibility requires EXCPRU 2.18 or higher. It is not available in Base software.- ANI/DNIS Compatibility requires system software 3.06.02 or higher. - ANI/DNIS routing to the VAU Automated Attendant requires EXCPRU 4.02 or higher. Routing by trunk to a specific VAU messages is also available with EXCPRU 4.02 or higher.- ANI/DNIS routing to the VAU Automated Attendant (page 493) requires system software 3.06.09 or higher. Routing by trunk to a specific VAU message requires system software 3.07.10 or higher. - Enhanced Answer Supervision for T1 tie trunks requires Base 2.13, EXCPRU 2.18 or higher. See page 844.- Enhanced Answer Supervision for T1 tie trunks requires system software 3.05.15 or higher. See page 844. - Voice Mail Caller ID with ANI/DNIS requires EXCPRU version 2.18 or higher.- Voice Mail Caller ID with ANI/DNIS requires system software 3.06.14 or higher. The T1/PRI Interface PCB gives the system T1 trunking capability. This PCB uses a single universal slot and provides up to 24 trunk circuits. In additional to providing digital-quality trunking, the T1/PRI Interface PCB al- lows you to have maximum trunking capability with fewer PCBs. This in turn makes more universal slots avail- able for other functions. You can program each T1/PRI PCB for any combination of the following trunks: •CO loop start •CO ground start •Direct Inward Dialing1 •Tie lines2 When installed in 384i, the T1/PRI Interface PCB uses the first block of 24 consecutive trunks. For example, if you have an ATRU PCB installed for trunks 1-8, the T1/PRI Interface PCB will automatically use trunks 9-32. If you have ATRU PCBs installed for trunks 1-8 and 17-24, the T1/PRI PCB will use trunks 25-48. The T1/PRI In- terface cannot use trunks 9-16 (even if available) since they are not part of a consecutive block of 24 trunks. Features N-Z T1 Trunking (with ANI/DNIS Compatibility) 92000SWG08 Issue 1-0FEATURES 483 1 Bidirectional DID trunks are currently not supported.2 Two-wire (four-lead) type 1 tie lines (FIC TL11M) only.
Description (Cont’d) ANI/DNIS Compatibility The system is compatible with telco’s T1 Automatic Number Identification (ANI) and Dialed Number Informa- tion Service (DNIS) services. A complement to Caller ID service, ANI/DNIS Compatibility provides: •Selectable Receive Format You can set up the system for compatibility with any combination of ANI, DNIS and Dialed Number (Address) data provided by the telco. •Flexible Routing Based on the data received, the system can route the incoming ANI/DNIS call to: – An extension – An ACD or Voice Mail master extension number – The VAU Automated Attendant and play a VAU message to the caller (requires 384i system software 3.06.09 or higher - 124i system requires EXCPRU 4.03 or higher). Refer to page 493 for the specifics. – A Department Group pilot number – A trunk Ring Group •Route According to DID Translation Table or Separate ANI/DNIS Routing Tables •ANI/DNIS Data Displayed as Caller ID Data •Data Error and Unanswered Call Handling If a call can’t be completed, send it to a predetermined Ring Group or play supervisory tones to the caller. •Voice Mail Caller ID NVM-Series Voice Mail can use ANI/DNIS information to identify the outside caller that left a message in a user’s mailbox. When the message recipient presses TI after hearing a message, they hear the time the message was sent and the outside telephone number of the message sender. Conditions (A.) T1 Trunking requires a T1/PRI Interface PCB and a customer-provided CSU/DSU to interface with the telco. Consult your sales representative and the system Hardware Manual for additional details. (B.) ANI/DNIS Compatibility requires the use of system DTMF receivers on CDTU A/B PCBs. When all receivers are busy, the incoming ANI/DNIS call waits for a receiver to become available. (C.) The ANI/DNIS/Address data received from the telco can be up to 10 digits long. If the system re- ceives more than 10 digits, it interprets the data as an error and handles the call according to the set- ting in 2404 - ANI/DNIS Service Options, Item 8: Routing on ANI/DNIS Error. Default Setting Disabled. Features N-Z T1 Trunking (with ANI/DNIS Compatibility) 484 FEATURES92000SWG08 Issue 1-0
Programming
Start
Are the T1 trunks
loop start or gound
start?In 2601, enter 0 for each
loop start trunk.In 2601, enter 1 for each
ground start trunk.
Should the T1/PRI
Interface PCB use
internal or external
(telco) clock?In 2602, enter 2 for
each PCB.
Loop startGround start
InternalExternal
Do the T1/PRI Interface
PCBs timing
parameters match the
requirements of the
telco?
In 0136, change the
T1 Trunk Timers.In 0136, do not
change the T1
Trunk Timers.
Go to 0009 Item 10 to
test T1 circuits.Yes
Check 0901 Items 14-17 for
compatibility with the
connected telco service.
Is the T1 Trunks
gain (amplification)
adequate?In 0901 Item 3,
assign a different
CODEC Gain Type.
Stop
NoYes
No
No
Does T1 Trunk use
ANI/DNIS services?
Yes
Yes
No
Note: All other trunk programming
must also be done.
If required, customize the
CODEC Gain Type transmit and
receive levels in 0117.
Continued
on
following
page.
Do you want to test the
T1 trunk circuits?
In 2602, enter 1 for
each PCB.
Features N-Z
T1 Trunking (with ANI/DNIS Compatibility)
92000SWG08 Issue 1-0FEATURES 485
Programming (Cont’d) Additional Programming for ANI/DNIS Continued from previous page. (384i Only)Are any DTMF receivers reserved for DTMF reception?IN 0303, reserve at least one CDTU DTMF receiver for DTMF reception (entry 2). In 0901:14-17, assign service type 6 to all ANI/DNIS T1 trunks.In 0905, group ANI/ DNIS trunks into Trunk Groups as required. Are the ANI/DNIS Service Options set up?In 2404, review the data for each item and configure the service options (1-15). In 0924, assign ANI/ DNIS Service Options (1-15) to trunks. Stop ANI/DNIS trunks must be immediate start or wink start T1 trunks with E&M signaling. Do you want ANI/ DNIS to route to the VAU Automated Attendant?Continued on next page. No Yes No Yes Yes NoIf using the Caller ID Table, youll use programs 2401 and 2402. If using the DID Table, youll use programs 1805, 1806 and 1808. Under the Programming heading in the text, check: 0136: T1 Trunk Timers and 0901: Additional ANI/DNIS Recommended Settings In 2301, enter 1 for wink start signaling. Features N-Z T1 Trunking (with ANI/DNIS Compatibility) 486 FEATURES92000SWG08 Issue 1-0
Programming (Cont’d) ANI/DNIS Routing to the VAU Automated Attendant Continued from previous page. Do you want to route to the Automated Attendant using the Caller ID Table, the DID Table or directly? Should VAU routing be based on the number dialed, or the number dialed and the incoming trunk used? Caller ID In the name portion of 2402, enter 882 + VAU message (01-16).Number Dialed In the name portion of 2402, enter 127 (384i) or 15 (124i).Number Dialed & Trunk In 2205, enter the VAU message (01-16) for each trunk. In 1803, enter 127 (384i) or 15 (for 124i) for each trunk. In 2404:3, enter 1. In 2404:4, enter 0. In 2404:7, define which portion of the Caller ID table (programmed in 2402) ANI/DNIS will use. Stop Continued on next page.Continued on next page.DID TableDirectly Features N-Z T1 Trunking (with ANI/DNIS Compatibility) 92000SWG08 Issue 1-0FEATURES 487
Programming (Cont’d) Continued from previous page. Do you want to route to the Automated Attendant using the DID Table or directly?In 2205, enter the VAU message (01- 16) for each trunk. Directly In 2404:3, enter 0 to bypass the routing tables. Should VAU routing be based on the number dialed, or the number dialed and the incoming trunk used? DID Table In the TRF portion of 1806, enter 882 + VAU message (01-16).Number DialedIn the TRF portion of 1806, enter 882 + VAU message (01-16).Number Dialed & Trunk In 2205, enter the VAU message (01- 16) for each trunk. In 1803, enter 127 (384i) or 15 (124i) for each trunk. In 2403:3, enter 1. In 2404:4, enter 2. Stop Features N-Z T1 Trunking (with ANI/DNIS Compatibility) 488 FEATURES92000SWG08 Issue 1-0
Programming (Cont’d) ➣ 0009 - Loop Back Testing, Item 10: T1 Test Once installed, use this program to test the T1 trunks. ➣0117 - Trunk CODEC Gain Type Settings Customize the transmit and receive levels of the CODEC Gain Types assigned in 0901 Item 3. ➣0136 - T1 Trunk Timers Set various T1 trunk timers for compatibility with the local telco. For ANI/DNIS, the following settings in Program 0136 are recommended: •Item 59: Clock Select = 2 (External - provided by Central Office) •Item 60: Distance Between PCB and SCU = 0 •Item 61: Frame Type = 1 (D3/D4) •Item 62: Zero Suppression = 2 (AMI/ZCS) ➣0303 - DTMF and Dial Tone Detection Setup For ANI/DNIS, reserve at least one CTDU DTMF receiver for DTMF reception (entry 2). •Use the following as a guide when allocating DTMF receivers (i.e., DTU blocks): - In light traffic sites, allocate one DTMF receiver for every 10 devices that use them. - In heavy traffic sites, allocate one DTMF receiver for every five devices that use them. ➣0901 - Basic Trunk Port Setup (Part A), Item 3: CODEC Gain Type Assign a CODEC Gain Type to each trunk. This sets the amount of gain (amplification) for the selected trunk. Customize the Gain Type transmit and receive levels in 0117. ➣0901 - Basic Trunk Port Setup (Part A), Items 14-17: Trunk Service Type For each T1 trunk, set the Trunk Service Type to match the telco’s connected T1 service. For each T1 trunk that should support ANI/DNIS service, enter 6. (ANI/DNIS trunks must be immediate start or wink start T1 trunks with E&M signaling.) ➣0901 - Basic Trunk Port Setup (Part A): Additonal ANI/DNIS Recommended Settings For ANI/DNIS, the following additional settings in Program 0901 are recommended: •Item 1: Signaling Type (DP/DTMF) = 2 (DTMF) •Item 2: Ring Detect Type = 1 (Immediate) •Item 5: Flash Type = 0 (Open Loop Flash) •Item 6: Flash for Time Flash or Disconnect = 0 (Timed Flash) •Items 7-10: Behind PBX = 0 (Stand alone) •Item 11: Dial Tone Detection for Manually Dialed Calls = 1 (Outgoing calls allowed) •Item 18: Outgoing Calls = 1 (Allowed) •Item 25: Tie Line Dial Tone (Immediate Start) = 1 (Enabled) •Item 26: Tie Line Dial Tone (Wink Start) = 1 (Enabled) •Item 27: DID Signaling Type = 1 (DTMF) ➣0905 - Trunk Groups For ANI/DNIS, place all your ANI/DNIS trunks in Trunk Groups as required. ➣0924 - ANI/DNIS Service Option Number Assignment For each ANI/DNIS trunk, assign a Service Option Number (1-115) for each Night Service mode. You define ANI/DNIS Service Option Numbers in 2404. ➣2301 - DID/E&M Start Signaling For each ANI/DNIS trunk, set the start signaling mode to 1 (wink start). ➣2404 - ANI/DNIS Service Options For each ANI/DNIS Service Option (1-15), program the option data from the table below. Features N-Z T1 Trunking (with ANI/DNIS Compatibility) 92000SWG08 Issue 1-0FEATURES 489
Programming (Cont’d) Program - 2404 ANI/DNIS Service Options Option Description Range Default Item 1ANI/DNIS Receive Format Use this option to specify the format of the ANI/DNIS data received from the telco. Make sure your entry is compatible with the service the telco provides. (The character * indicates a delimiter.) 0 = Address (called number without delimiters) 1 = *ANI* 1 2 = *DNIS* 3 = *ANI*Address*1 4 = *ANI*DNIS*1 5 = *DNIS*ANI*1 1 Select one of these options for Voice Mail Caller ID.0-5 0 (Address) Item 2Delimiter Dial Code This option defines the character telco uses as a delimiter (see entries 1-9 in Item 1 above). Valid entries are 0-9, # and *.0-9, # and * * Item 3Routing Search Criteria (Data Source) This option specifies the source of the data the system uses to route incoming ANI/DNIS calls. The choices are: 0 = No Routing. The system assumes an error has occurred and routes according to the setting in Item 8. 1 = Routes on Received DNIS or Address Data. The data source is the received DNIS or address data. This option requires that Item 1 be 0 or 2-5. 2 = Routes on Received ANI Data. The data source is the received ANI data. This option requires that Item 1 be 1 or 3-5. 0-2 0 (No routing) Features N-Z T1 Trunking (with ANI/DNIS Compatibility) 490 FEATURES92000SWG08 Issue 1-0