Version: 10.3.0 PBX Integration Technical Manual · 2021. 3. 17. · Philips Sopho IS3000 R6810.32E...

Kofax Communication ServerPBX Integration Technical ManualVersion: 10.3.0

Date: 2019-12-13

© 2019 Kofax. All rights reserved.

Kofax is a trademark of Kofax, Inc., registered in the U.S. and/or other countries. All other trademarksare the property of their respective owners. No part of this publication may be reproduced, stored, ortransmitted in any form without the prior written permission of Kofax.

Table of ContentsChapter 1: Preface...................................................................................................................................... 4Chapter 2: General PBX Requirements.................................................................................................... 5Chapter 3: Validated PBX Cross Reference.............................................................................................7Chapter 4: Validated PBX Integrations..................................................................................................... 8

Alcatel OmniPCX 4400 R3.2/R4.2/R5.0/R6.1 QSIG Integration........................................................8Test Report...............................................................................................................................8Specific Considerations/Configuration Hints............................................................................9PBX Configuration................................................................................................................. 10

Siemens Hicom 300 R2.08/Hipath 4000 R1.0 QSIG Integration..................................................... 16Test Report (Hicom 300)....................................................................................................... 16Test Report (Hipath 4000 R1.0)............................................................................................ 17Specific Considerations/Configuration Hints (Both Hicom 300/Hipath 4000)........................ 17PBX Configuration (Both Hicom 300/Hipath 4000)............................................................... 18

Nortel Meridian 1 R25.40b QSIG Integration...................................................................................26Test Report.............................................................................................................................26Specific Considerations/Configuration Hints..........................................................................27PBX Configuration................................................................................................................. 28

Philips Sopho IS3000 R6810.32E QSIG Integration....................................................................... 35Test Report.............................................................................................................................35Specific Considerations/Configuration Hints..........................................................................36PBX Configuration................................................................................................................. 37

3

Chapter 1

Preface

This manual summarizes all available PBX-related information that is necessary to perform a goodintegration with TC/Model 305 Line Server with those legacy PBX platforms that were tested and validatedby Kofax.

The General PBX Requirements chapter provides a list of the PBX features available (that may berequired for integration with Kofax products). Note that the complementary Kofax features are described indetail in the ISDN Technical Manual.

The Validated PBX Cross Reference summarizes the information which TCSP release was validated fora particular PBX feature/PBX type/PBX release. Please note that the TCSP release does not have to bean officially released package. This can happen if some code changes had to be implemented to supporta particular PBX. In this case Kofax can create an internal TCSP that supports this PBX, document itsrelease number in this manual and support this PBX officially in the next released TCSP.For the time period the PBX is supported only by an internal TCSP (but not released one) its support maybe done via module updates or even by delivering an internal TCSP for specific customer (via standardreporting mechanism).

The chapter Validated PBX Integrations provides for the PBX related configuration information and hintshow to setup the particular PBX for a required Kofax integration.

Important The Kofax Communication Server and its components formerly used the nameTOPCALL. Some screen shots and texts in this manual may still use the former name.

Disclaimer

1. PBX configurations described in this manual should be seen as examples of a working Kofax – PBXintegration. They do not replace a PBX System Manual, an experienced PBX technician and do notdescribe the meaning of all PBX parameters. They only attempt to point out those PBX parameters/settings that may be critical for a successfulKofax integration.

2. Kofax does not guarantee that any other problems not detailed in this manual would not occur.

3. Kofax recommends to implement the particular integration based on the same or newer PBXsoftware release as documented in this manual.

4. PBX functions and parameters explicitly listed in this manual may vary more or less in newer PBXsoftware releases. It is the PBX technician’s task to find out their counterparts in the newer softwarereleases.

4

Chapter 2

General PBX Requirements

There are two functionality classes:

1. Standard functionality (like fax/voice call in and out)This should work with almost every PBX type that supports appropriate protocols, no PBX integrationtesting with Kofax assistance is necessary prior to the customer installation.

2. Extended functionalityKofax guarantees to deliver working functionality according to the supported protocol specifications.But as implementations on different PBX platforms may be more or less incompatible, the PBXintegration testing with that PBX platforms that has not been tested so far is necessary to beperformed prior to the customer installation (see the „PBX Integration Program“).

PBX feature Description and Usage Supported standardprotocols

Functionality Class/PBXIntegration Procedure

Basic Call Basic in and out callfunction, necessary forboth fax and voice aswell

EuroISDN, QSIG, 1TR6,4ESS (AT&T)

StandardPBX integration tests notnecessary

Message WaitingIndication (MWI)

Indication of an incomingmessage on thetelephone’s MWI lamp

QSIG ExtendedPBX integration tests necessary

Call Transfer (CT) Switching of two callsvia the PBX for TC/Attendant, DialbyName,SimpleCTI functions


Path Replacement(PR)

Call route optimizationafter the Call Transfer,necessary for eachapplication using theCallTransfer


Call Diversion (CD) (CFU, CFNR andCFB)1

Redirecting of incomingcalls to the KCS Voiceserver, necessary forbasic TC/VoiceAccessfunctionality

EuroISDNQSIG

ExtendedPBX integration tests necessary

Advice of Charge(AOC)

Cost accounting foroutgoing fax and voicecalls

EuroISDN, 1TR6 StandardPBX integration tests notnecessary

1 CFU: Call Forward Unconditional, CFNR: Call Forward not Responding, CFB: Call Forward on Busy

5

Kofax Communication Server PBX Integration Technical Manual

PBX feature Description and Usage Supported standardprotocols

Functionality Class/PBXIntegration Procedure


6

Chapter 3

Validated PBX Cross Reference

The following tables provides for a cross-reference between tested TCSP and TCOSS module release,PBX type and tested function. The “-“ sign means that specific function is not supported/was not validatedwith specific PBX type/SW release.

1. The 1st release number in the table stands for the TCSP release that was validated

2. The 2nd one (optional, in columns) for the TCOSS module update if it was necessary for theparticular integration

TCSP release(TCOSS modulerelease)PBX Type/SW release/Access type

Protocol ValidatedFunction(*)PBX ProtocolVariant(**)

BasicCall(BC)

MWI CD CT PR AOC

Alcatel OmniPCX 4400R3.2/4.2/5.0/6.1T0 (BRI trunk)/T2 (PRItrunk)

QSIG ISO-QSIG ETSI-QSIG

7.48.00 7.65.12(only R6.0or later!)

7.48.00 7.48.00 7.48.00 -

Siemens Hicom 300 R2.08S0 (BRI trunk)/ S2 (PRItrunk)

QSIG ECMAV2PSS1V2

7.48.00 7.48.00 7.48.00 7.48.00 7.48.00 -

Meridian 1R25.40bBRI and PRI trunks

QSIG ISGF 7.50.00 7.50.00 7.50.00 7.50.00 7.50.00 -

Philips SophoIS3000 R6810.32E

QSIG realQSIG 7.55.07 7.55.07 7.55.07 7.55.07 - -

Siemens Hipath4000R1.0S0 (BRI trunk)/ S2 (PRItrunk)

QSIG ECMAV2 7.56.02 7.56.02 7.56.02 7.56.02 7.56.02

(*) For abbreviations refer to the PBX feature table.

(**) Specific PBX protocol name/variant/implementation that was setup on the PBX side.

7

Chapter 4

Validated PBX Integrations

This section describes the validated PBX integrations.

Alcatel OmniPCX 4400 R3.2/R4.2/R5.0/R6.1 QSIG IntegrationThis section describes the integration with Alcatel OmniPCX 4400 R3.2/R4.2/R5.0/R6.1 QSIG.

Test ReportDate 19.03.2003

Location Korneuburg, Austria

Tested by Norbert Bartalsky, Kofax

TCSP release 7.48.00

TCOSS module 7.48.00

PBX vendor Alcatel

PBX Type OmniPCX 4400

Protocols ETSI-QSIG and ISO-QSIG

PBX SW release(s) 3.2, 4.3 and 5.0

Tested functions BC, CD, CT, PR

TestRestrictionsProblemsOpen Questions

MWI is not supported by A4400 R3.x-R5.0, therefore not testedBut it is supported since R 6.0 and it was successfully tested with R6.1 (see “Special Considerations” below)AOC was not tested, as not supported by TC QSIGAll test cases were tested only with internal phones, as the test PBX was notconnected to the public telephone networkDuring the tests it was not possible to send messages in a loop to the owntrunk number (TC->PBX->TC)(this may have been a PBX config issue)It was not possible to send from trunk to trunk(this may have been a PBX config issue)

Summary Integration tests were successfulOmniPCX 4400 is validated to be used with KCS Server Model 305using both BRI and PRI QSIG connections as well

8


Specific Considerations/Configuration Hints1. Trunk Types

Alcatel uses following abbreviations for trunks:T0 – stands for the ISDN BRI point to point trunkT2 - stands for the ISDN PRI point to point trunkNote the “S0” stands for ISDN BRI point to multipoint line (station line) that is not suitable for KCSinterconnection!

2. QSIG protocol variants ETSI and ISOThe PBX supports for two QSIG variants – ETSI and ISO – that are not compatible with each other.This can be setup by the system-wide parameter “ISO Function”:”ISO Function = True” stands for ISO-QSIG (corresponds with KCS standard QSIG config)”ISO Function = False” stands for ETSI-QSIG (setup in the UIF config line 286, pos. 8)Note that this parameter is system-wide in the PBX so it has an influence on ALL QSIG trunksconnected!

3. QSIG configuration for QSIG supplementary services (QSIG-GF) vvs. QSIG „basic call only“

In order to support QSIG supplementary services (like call diversion, …) the parameter “TrunkGroups\Q931 signal variant” MUST be set to ABC-F (which stands for Alcatel proprietary PBX protocol) andthe parameter “Protocol Type” in the associated remote network must be set to QSIG-GF.

If the parameter “TrunkGroups\Q931 signal variant” would be set to QSIG, only the QSIG basic callfunctionality would be provided (in and out call, no supplementary services).

4. Logical channel numbering with T2 access type (PRI)The parameter “TrunkGroups\LogicalChannel“ MUST be set to 1__30. This corresponds with QSIGconvention to use logical B-channel number during the B-channel allocation procedure (on the otherhand, public network ISDN protocols like EuroISDN uses the trunk timeslot number instead).Note that there is no complementary parameter on KCS side. If QSIG is setup on KCS, it alwaysuses the proper channel numbering scheme.

5. Call Transfer restriction with R 3.2Call Transfer by join “into ringing” does not work with R 3.2. Therefore the Call Transfer by join “intoconnected” must be configured on the KCS side (UIF config line 295, pos. 5 set to 02)

6. Call Hold & Call TransferThe 1st (primary call) call of the two calls to be transferred must be put on Hold prior to the transfer(UIF config line 295, pos. 6 set to 01)

7. Message waiting indication (MWI)This supplementary service has been implemented since Alcatel 4400 release 6.0 and later, and itis supported since TCSP 7.65.12. No special configuration is necessary on the A4400 side (it worksfine with the Qsig configuration described below) but it is necessary to set the PBX Model in the UIFconfiguration:

UIF config line 287, pos. 15-16 set to 00 01 (default: 00 00 stand for all other PBXs)

9


(as this PBX uses proprietary QSIG-MWI signaling and not the standard-conform one).

If also the callback button on the A4400 phones should work, the “Message Centre ID“ parameter ofthe MWI send order on the KCS side should be set to the “VoiceAccess number” (this number will bedialed after any user presses his callback button). If the “ Message Centre ID“ would be empty, MWIwould work fine, but the callback button not !

Note that if the user presses the callback button on his Alcatel telephone set (in order to listen tohis messages on the KCS server), the PBX immediately switches the MWI lamp off. If then later onthe KCS server sends the MWI OFF command (as the message has been read), its send order willpositively terminate but there will be the error text “returnResultError” in the response field as KCSattempted to switch that lamp off that has already been in the MWI OFF state.

PBX ConfigurationThis section describes the PBX configuration.

T0 Access (BRI)Alcatel OmniPCX4400 release R3.2 (R3.2-c1.706-7-au-c3s2)Alcatel OmniPCX4400 release R4.2 (R4.2-d2.101-0-au-c3s2)Alcatel OmniPCX4400 release R5.0 (R5.0Ux-d2.313-7-I-au-c3s2)This file describes the configuration of the T0 trunk TG 4 with the prefix 04.Most of the parameters have their default values: those parameters that were relevant for KCS configuration, are marked with Bold.It was generated with the R3.2, but can be used also for R4.2 and R5.0 without significant changes(1)dhs338> trkvisu alloutput of all Trunk_Groups and Links------------------------------------------------------------------- Numb | Name | Type | Var. | Node | Pfx-------------------------------------------------------------------TG 1 | ISDN-Trunk | T0 | ISDN | 1 => local | 01TG 4 | QSIG | T0 | IPNS | 1 => local | No pfxTG 8 | QSIG PRA | T2 | IPNS | 1 => local | No pfx-------------------------------------------------------------------ISO Function Parameter: True for ISO-QSIG or False for ETSI-QSIGxxxxxxxxxx Consult/Modify: Other System Param. Xxxxxxxxxxxxxxx xx Node Number (reserved) : 1 xx Instance (reserved) : 1 xx Instance (reserved) : 1 xx xx Trunk seizure via attendant + True xx No detect.of On-hook tone + True xx TrkGrp in ticket for trans.call + True xx VPN service + False xx ISVPN Node No. : 1 xx Nb Digits displayed on sets : 1 xx Melody Ringing Type : 1 xx Int.Call Ringing Cadence No : 1 xx Ext.Call Ringing Cadence No : 1 xx Executive Type Ringing Cadence No : 1 xx Prioritary Call Cadence No : 1 xx ISO Function + True x ISO-QSIGx Booking B Channel + False xx Uncontrol.Business Account Code + False xx Business Pref.With Business No. + True x

10


x Project prefix With Code + False xx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxTrunk Groups:The signaling variant must be ABC-F and NOT QSIG and the associated “remote network” must have the protocol type “QSIG-GF” (see Network Routing Table below).This is necessary for QSIG supplementary services like call diversion, call transfer etc.xxxxxxxxxx Consult/Modify: Trunk Groups xxxxxxxxxxxxxxxxxxx Node Number (reserved) : 1 xx Trunk Group Id : 4 xx xx Trunk Group Type + T0 xx Trunk Group Name : QSIG BRA xx Number Compatible With : -1 xx Remote Network : 5 x for QSIG-GFx Shared Trunk Group + False xx Special Services + Nothing xx Node number : 1 xx Transcom Trunk Group + False xx Auto.reserv.by Attendant + False xx Overflow trunk group No. : -1 xx Tone on seizure + False xx Private Trunk Group + False xx Security Patrol + False xx Q931 signal variant + ABC-F xx Number Of Digits To Send : 5 xx auto.DTMF dialing on outgoing call + NO xx Public Network Category : 0 xx DDI transcoding + False xx Can support UUS in SETUP + True xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Consult/Modify: Trunk Groups xxxxxxxxxxxxxxxxxxx xx Node Number (reserved) : 1 xx Trunk Group Id : 4 xx Instance (reserved) : 1 xx xx Trunk Group Type + T0 xx Public Network Ref. : ------ xx VG for non-existent No. + YES xx Entity Number : 0 xx Supervised by Routing + NO xx VPN Cost Limit for Incom.Calls : 0 xx Immediat Trk Listening For VPNCall + YES xx VPN TS % : 50 xx Csta Monitored + NO xx Max.% of trunks out CCD : 0 xx Ratio analog.to ISDN tax : ------ xx TS Distribution on Accesses + YES xx Quality profile for voice on IP + Profile #1 xx IP compression type + Default xx Use of volume in system + YES xx Dialling end to end + NO xx DTMF end to end signal. + NO xx Trunk group used in DISA + NO xx DISA Secret Code : -------- xx Routing To Executive + NO xx Trunk Category Id : 18 xx Nb of digits unused (ISDN) : 2 xx B Channel Choice + YES x B-chan.exclx Channels Reserved By Attend. : 0 xx Dissuasion For ACD + NO xx DTO joining + NO x

11


x Enquiry Call On B Channel + NO xx Automated Attendant + NO xx Calling party Rights category : 0 xx TS Overflow + YES xx Number To Be Added : -------- xx Trunk group used in DISA + NO xx DISA Secret Code : -------- xx Charge Calling And ADN Creation + NO xx Use Split Access + NO xx Heterogeneous Remote Network + NO xx Barring mode + Not barred xx ARS class of service : 31 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxTranslator (trunk prefix 04)xxxxxxxxx Consult/Modify: Prefix Plan xxxxxxxxxxxxxxxxxxxxxxxx xx Node Number (reserved) : 1 xx Instance (reserved) : 1 xx Number : 04 xx xx Prefix Meaning + Routing No. xx Network Number : 5 xx Node Number/ABC-F Trunk Group : 4 xx Number of Digits : 7 xx Number With Sub Address (ISDN) + NO xx Default X25 Id.pref. + NO xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxPrefix for Path Replacement:define a prefix as a local node numberfor Path Replacement (e.g. 50400 as below)xxxxxxxxx Consult/Modify: Prefix Plan xxxxxxxxxxxxxxxxxxxxxxxxxxxxx xx Node Number (reserved) : 1 xx Instance (reserved) : 1 xx Number : 50400 xx xx Prefix Meaning + Local Features xx Local Features + Pabx address in DPNSS x (*)x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx(*) With R5.0 this value is “PCX address in DPNSS”Remote network settingsxxxxxxxxx Consult/Modify: Network Routing Table xxxxxxxxxxxxxxxxxxx xx Node Number (reserved) : 1 xx Instance (reserved) : 1 xx Network Number : 5 xx xx Rank of First Digit to be Sent : 3 xx Incoming identification prefix : -------- xx Protocol Type + QSIG-GF xx Numbering Plan Descriptor Id : 11 xx ARS Route list : 0 xx Schedule number : -1 xx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxTrunk access:xxxxxxxxxx Modify: T2/T1/T0 Access xxxxxxxxxxxxxxxxxxxxxxxxxxx xx Node Number (reserved) : 1 xx Trunk Group Id : 4 xx Instance (reserved) : 1 xx Physical Address : 0-3-0 xx x

12


x Access Type + T0 xx Access Cluster Id : -1 xx Time Slots T0 : 011 xx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxDigital access:xxxxxxxxxx Consult/Modify: Digital Access xxxxxxxx xx Node Number (reserved) : 1 xx Shelf Address : 0 xx Board Address : 3 xx T0/T2 Access No. : 0 xx xx Access Type + T0 xx Synchronisation Priority : 255 x ClkMasterx Network Mode + YES xx Max Nb Of Used B Channels : 2 xx Max_Nb_Of_Compressed_B_Channels : 0 xx TieLine Mode + NO xx Access Type S0 + YES xx Reserved1 + NO xx Reserved2 + NO xx Network Date Time Update + NO xx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

T2 Access (PRI)Alcatel OmniPCX4400 release R3.2 (R3.2-c1.706-7-au-c3s2)Alcatel OmniPCX4400 release R4.2 (R4.2-d2.101-0-au-c3s2)Alcatel OmniPCX4400 release R5.0 (R5.0Ux-d2.313-7-I-au-c3s2)This file describes the configuration of the T2 trunk TG 8 with the prefix 08.Most of the parameters have their default values: those parameters that were relevant for KCS configuration, are marked with Bold.It was generated with the R3.2, but can be used also for R4.2 and R5.0 without significant changes(1)dhs338> trkvisu alloutput of all Trunk_Groups and Links------------------------------------------------------------------- Numb | Name | Type | Var. | Node | Pfx-------------------------------------------------------------------TG 1 | ISDN-Trunk | T0 | ISDN | 1 => local | 01TG 4 | QSIG | T0 | IPNS | 1 => local | No pfxTG 8 | QSIG PRA | T2 | IPNS | 1 => local | No pfx-------------------------------------------------------------------ISO Function: True for ISO-QSIG or False for ETSI-QSIGxxxxxxxxxx Consult/Modify: Other System Param. Xxxxxxxxxxxxxxx xx Node Number (reserved) : 1 xx Instance (reserved) : 1 xx Instance (reserved) : 1 xx xx Trunk seizure via attendant + True xx No detect.of On-hook tone + True xx TrkGrp in ticket for trans.call + True xx VPN service + False xx ISVPN Node No. : 1 xx Nb Digits displayed on sets : 1 xx Melody Ringing Type : 1 xx Int.Call Ringing Cadence No : 1 xx Ext.Call Ringing Cadence No : 1 xx Executive Type Ringing Cadence No : 1 xx Prioritary Call Cadence No : 1 x

13


x ISO Function + True x ISO-QSIGx Booking B Channel + False xx Uncontrol.Business Account Code + False xx Business Pref.With Business No. + True xx Project prefix With Code + False xx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxTrunk GroupsThe signaling variant must be ABC-F and NOT QSIG and the associated “remote network” must have the protocol type “QSIG-GF” (see Network Routing Table below).This is necessary for QSIG supplementary services like call diversion, call transfer etc.xxxxxxxxxx Consult/Modify: Trunk Groups xxxxxxxxxxxxxxxxxxxxxX Node Number (reserved) : 1 xX Trunk Group Id : 8 xX xX Trunk Group Type + T2 xX Trunk Group Name : QSIG PRA xX Number Compatible With : -1 xX Remote Network : 8 x for QSIG-GFX Shared Trunk Group + False xX Special Services + Nothing xX Node number : 1 xX Transcom Trunk Group + False xX Auto.reserv.by Attendant + False xX Overflow trunk group No. : -1 xX Tone on seizure + False xX Private Trunk Group + False xX Q931 signal variant + ABC-F xX Number Of Digits To Send : 5 x DDI lengthX Channel selection type + Quantum xX auto.DTMF dialing on outgoing call + NO xX T2 Specificity + None xX Public Network Category : 0 xX DDI transcoding + False xX Can support UUS in SETUP + True xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Consult/Modify: Trunk Group xxxxxxxxxxxxxxxxxxxxxxxx xx Node Number (reserved) : 1 xx Trunk Group Id : 8 xx Instance (reserved) : 1 xx xx Trunk Group Type + T2 xx Public Network Ref. : ------ xx VG for non-existent No. + YES xx Entity Number : 0 xx Supervised by Routing + NO xx VPN Cost Limit for Incom.Calls : 0 xx Immediat Trk Listening For VPNCall + YES xx VPN TS % : 50 xx Csta Monitored + NO xx Max.% of trunks out CCD : 0 xx Ratio analog.to ISDN tax : ------ xx TS Distribution on Accesses + YES xx Quality profile for voice on IP + Profile #1 xx IP compression type + Default xx Use of volume in system + YES xx Dialling end to end + No xx DTMF end to end signal. + NO xx Trunk group used in DISA + NO xx DISA Secret Code : -------- xx Routing To Executive + NO xx Trunk Category Id : 18 x

14


x Nb of digits unused (ISDN) : 2 x prefix lengthx B Channel Choice + YES x B-chan. Excl.x Channels Reserved By Attend. : 0 xx Dissuasion For ACD + NO xx DTO joining + NO xx Enquiry Call On B Channel + NO xx Automated Attendant + NO xx Calling party Rights category : 0 xx TS Overflow + YES xx Number To Be Added : -------- xx Charge Calling And ADN Creation : No xx LogicalChannel : 1__30 x QSIG chan.numb.x Use Split Acces : No xx Heterogeneous Remote Network + NO xx Barring mode + Not barred xx ARS class of service : 31 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxTranslator (trunk prefix 08)xxxxxxxxx Consult/Modify: Prefix Plan xxxxxxxxxxxxxxxxxxxxxxxx xx Node Number (reserved) : 1 xx Instance (reserved) : 1 xx Number : 08 xx xx Prefix Meaning + Routing No. xx Network Number : 8 xx Node Number/ABC-F Trunk Group : 8 xx Number of Digits : 7 xx Number With Sub Address (ISDN) + NO xx Default X25 Id.pref. + NO xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxPrefix for Path Replacement:define a prefix as a local node numberfor Path Replacement (e.g. 50400 as below)xxxxxxxxx Consult/Modify: Prefix Plan xxxxxxxxxxxxxxxxxxxxxxxxxxxxx xx Node Number (reserved) : 1 xx Instance (reserved) : 1 xx Number : 50400 xx xx Prefix Meaning + Local Features xx Local Features + Pabx address in DPNSS x (*)x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx(*) With R5.0 this value is “PCX address in DPNSS”Remote network settingsxxxxxxxxx Consult/Modify: Network Routing Table xxxxxxxxxxxxxxxxxxx xx Node Number (reserved) : 1 xx Instance (reserved) : 1 xx Network Number : 8 xx xx Rank of First Digit to be Sent : 3 xx Incoming identification prefix : -------- xx Protocol Type + QSIG-GF xx Numbering Plan Descriptor Id : 11 xx ARS Route list : 0 xx Schedule number : -1 xx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxtrunk accessxxxxxxxxx Consult/Modify: T2/T1/T0Access xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xx Node Number (reserved) : 1 x

15


x Trunk Group Id : 8 xx Instance (reserved) : 1 xx Physical Address : 0-4-0 xx xx Access Type + T2 xx Access Cluster Id : -1 xx Time Slots T2 : 01111111111111110111111111111111 xx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxDigital accessxxxxxxxxx Consult/Modify: Digital Access xxxxxxxxxxxxxxxxxxxxxxxxxx xx Node Number (reserved) : 1 xx Shelf Address : 0 xx Board Address : 4 xx T0/T2 Access No. : 0 xx xx Access Type + T2 xx Synchronisation Priority : 255 x ClkMasterx Network Mode + YES xx Max Nb Of Used B Channels : 30 xx Max_Nb_Of_Compressed_B_Channels : 0 xx TieLine Mode + YES xx With Alarm + NO xx Reserved1 + NO xx Reserved2 + NO xx Network Date Time Update + NO xx CRC4 + YES xx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Siemens Hicom 300 R2.08/Hipath 4000 R1.0 QSIG IntegrationThis section describes the integration with Siemens Hicom 300 R2.08/Hipath 4000 R1.0 QSIG.

Test Report (Hicom 300)Date 21.03.2003

Location Vienna, Austria




PBX vendor Siemens

PBX Type HICOM 300

Protocols QSIG (protocol variants ECMAV2 and PSS1V2)

PBX SW release(s) 2.08

Tested functions BC, CD, CT, PR, MWI

16



AOC was not tested, as not supported by TC QSIGPath Replacement after CT does not work if switchboard is involved in oneof the two calls to be transferredThis is a general Hicom 300 restrictionThe PBX “Hold music” did not work if the (primary) caller was calling fromthe digital comfort Optiset telephone and invoked the Call Transfer (themessage “please wait/bitte warten” was shown on his display but silenceuntil the second call was answered). This problem didn’t occur with neithera/b nor standard digital Optiset telephones.This may be a problem with tested Hicom 300 SW release

Summary Integration tests were successfulHicom 300 is validated to be used with KCS Server Model 305 usingboth BRI and PRI QSIG connections as well

Test Report (Hipath 4000 R1.0)Date 1.04.2004





QSIG Module 2.1

PBX vendor Siemens

PBX Type HIPATH4000

Protocols QSIG (protocol variant ECMAV2)

PBX SW release(s) 1.0

Tested functions BC, CD, CT, PR, MWI


AOC was not tested, as not supported by TC QSIGPath Replacement after CT does not work if switchboard is involved in oneof the two calls to be transferred

This is a general Hicom 300/Hipath4000 restriction

Summary Integration tests were successfulHicom 4000 is validated to be used with KCS Server Model 305 usingboth BRI and PRI QSIG connections as well

Specific Considerations/Configuration Hints (Both Hicom 300/Hipath 4000)1. Trunk Types

Siemens uses following abbreviations for trunks:S0 – stands for the ISDN BRI point to point trunkS2 - stands for the ISDN PRI point to point trunk

17


2. QSIG protocol variantsThe PBX supports three QSIG variants – ECMAV1, ECMAV2 and PSS1V2, but only ECMAV2 wasvalidated. The protocol variant is the trunk-related parameter.However, the PSS1V2 should work, too.ECMAV2 and PSS1V2 are compatible with KCS standard ISO-QSIG config (setup in the UIF configline 286, pos. 8).

3. Configuring Message Waiting Indication (MWI)Unique „Message Centre ID“ parameter must be configured per each Voice Server in the HICOM300 PBX (and must be also entered within the MWI On/Off events on the KCS side). In theHIPATH4000 PBX this parameter is optional, but recommended to be used anyway.

4. Call Hold & Call TransferThe 1st (primary call) call of the two calls to be transferred must be put on Hold prior to the transferwith HICOM 300 PBX (UIF config line 295, pos. 6 set to 01). The Hold needn’t be used withHIPATH4000, but it is recommended anyway in order to activate proper Hold on music in the PBX.

PBX Configuration (Both Hicom 300/Hipath 4000)This section describes the PBX configuration for Hicom 300/Hipath 4000.

MWI ConfigurationConfigure a route for the Voicemail server:ADD-RICHT:MODE=PM,IDX=<n>,SAN=<MsgCentreID>,NAME=”TOPCALL”,STYPE=OTHER

<n> is the number of the VoiceMail server, 1, 2, 3, …

<MsgCentreID> is the same parameter as used with KCS send order for MWI ON/OFF, it is recommendedto use the KCS VoiceAccess number for it but incl. trunk prefix if defined in the PBX (for example, theVoice Access number is 999, the trunk prefix is 731, the MsgCentreID=731999).

Once MWI was activated using particular MsgCentreID it must be deactivated using the sameMsgCentreID. Further, if the user presses the Phone Mail button on his telephone, the PBX may call (ifconfigured for this) automatically the number given by the MsgCentreID (and this is the reason why theusage of KCS Voice Access number is recommended – user may automatically proceed to listen of hisVoice Mails by pressing a single button).

In the following example 4 Voice Mail servers were configured for QSIG trunks with prefixes 731, 746, 747and 79.AB-RICHT:PM;H500: AMO RICHT GESTARTET ------------------------------------------------------------------- | IDX | SAN | NAME | ------------------------------------------------------------------- | 1 | 731999 | TOPCALL | | 2 | 746999 | TOPCALL 2 | | 3 | 747999 | TOPCALL 3 | | 4 | 79699 | | -------------------------------------------------------------------

18


Note• The SANs are dialable numbers that are really dialled when MWI is executed. So, there must be

classic RICHT/LODR/LDAT/LDPLN set that leads to the tie-line connecting the KCS server andHicom300/Hipath4000.

• If the KCS server should be integrated with Hipath4000, it must be taken into account that everyOptiset/Optipoint must be explicitly assigned to the VoiceMail server. To do this, parameter PMIDXmust correspond to IDX in AMO RICHT, type PM (see the example below).

• If the MWI functionality is desired also for cordless phones called CMIs, following patches must beapplied:• For Hipath4000 1.0: MSC08733 and MSC09242 (for PMIDX)• For Hicom 300: no patches needed (as there is no PMIDX)

MWI Configuration Example (for the Hipath4000 Network)Assume a network of two HIPATH4000 nodes PBX2 and PBX3. The KCS server is connected directly withthe PBX3 node via S2m, while PBX 2 and PBX 3 are interconnected through Siemens proprietary Cornet-N protocol.

The KCS trunk prefix is 70, the KCS Voice access number 4000 (so the KCS Voice access number maybe reached by dialing 704000 from both extensions 2000 and 3000 as well). The MessageCentreID is704000. With this configuration, KCS server is able to control MWI indicators on both extension 2000 and3000:

Example for PBX3 which is directly connected to the KCS server: <reg-tdcsu:1-2-25-1;REG-TDCSU:1-2-25-1;H500: AMO TDCSU STARTEDADD-TDCSU:NEW ,1-02-025-1,150,77,0,0,77,1,1," ",0,ECMAV2,1,,NONE,,,,GDTR,N,TIE,NONE,N,0,,00,0,,,,31,MANY,400,0,1,1,EMPTY,150,5,N,

19


,,,,,16,8,1,10,,EC&G711&G729OPT,"",40,CIR,Y,S2CONN, 1&&30 ,N,1,9,0,0,0,0,0 ;AMO-TDCSU-111 DIGITAL TRUNKSREGENERATE COMPLETED; <dis-tdcsu:1-2-25-1;DIS-TDCSU:1-2-25-1;H500: AMO TDCSU STARTED +------------------------ DIGITAL TRUNK (FORMAT=L) -------------------------+ | DEV = S2CONN PEN = 1-02-025-1 TGRP = 40 | |---------------------------------------------------------------------------| | PROTVAR = ECMAV2 INS = N SRCHMODE = CIR | | COTNO = 150 COPNO = 77 DPLN = 0 | | ITR = 0 COS = 77 LCOSV = 1 | | LCOSD = 1 CCT = DESTNO = 0 | | SEGMENT = 1 DEDSCC = DEDSVC = NONE | | FACILITY = DITIDX = SRTIDX = | | TRTBL = GDTR SIDANI = N ATNTYP = TIE | | CBMATTR = NONE NWMUXTIM = 10 TCHARG = N | | SUPPRESS = 0 DGTPR = CHIMAP = N | | ISDNIP = 00 ISDNNP = 0 | | PNPL2P = PNPL1P = PNPAC = | | TRACOUNT = 31 SATCOUNT = MANY NNO = 400 | | ALARMNO = 0 FIDX = 1 CARRIER = 1 | | ZONE = EMPTY COTX = 150 FWDX = 5 | | DOMTYPE = DOMAINNO = TPROFNO = | | INIGHT = CCHDL = | | UUSCCX = 16 UUSCCY = 8 FNIDX = 1 | | CLASSMRK = EC & G711 & G729OPT SRCGRP = | | TCCID = | |---------------------------------------------------------------------------| | BCNEG = N BCGR = 1 LWPAR = 9 | | LWPP = 0 LWLT = 0 LWPS = 0 | | LWR1 = 0 LWR2 = 0 | | SVCDOM = | | BCHAN = 1 && 30 | | | +---------------------------------------------------------------------------+ AMOUNT OF B-CHANNELS IN THIS DISPLAY-OUTPUT: 30AMO-TDCSU-111 DIGITAL TRUNKSDISPLAY COMPLETED; <dis-cot:150;DIS-COT:150;H500: AMO COT STARTED COT: 150 INFO: DEVICE: INDEP SOURCE: DB PARAMETER: RECALL IF USER HANGS UP IN CONSULTATION CALL RCL TRUNK SIGNALING ANSWER ANS KNOCKING OVERRIDE POSSIBLE KNOR CALL EXTEND FOR BUSY, RING OR CALL STATE CEBC NETWORKWIDE CALL FORWARDING PERMITTED FWDN NETWORKWIDE FORWARDING NO-ANSWER FNAN DON'T RELEASE CALL TO BUSY HUNT GROUP BSHT END-OF-DIAL FOR BLOCK IS SET BLOC SEND NO NODE NUMBER TO PARTNER LWNC ACTIVATE TRANSIT COUNTER ADMINISTRATION FOR S0/S2 LINE ATRS CONNECTION TO ROUTE OPTIMIZATION NODE ROPT INCOMING CIRCUIT FROM SYSTEM WITHOUT LCR NLCR TSC-SIGNALING FOR NETWORKWIDE FEATURES (MANDATORY) TSCS USE DEFAULT NODE NUMBER OF LINE DFNN INCOMING CIRCUIT FROM SYSTEM WITHOUT LCR (DATA) NLRD

20


CONTROLLED TRUNK AND LINE SELECTION CTLS RESERVED ELEMENT R252 NO TONE NTONAMO-COT -111 CLASS OF TRUNK FOR CALL PROCESSINGDISPLAY COMPLETED; <dis-cop:77;DIS-COP:77;H500: AMO COP STARTED COP: 77 INFO: DEVICE: INDEP SOURCE: DB PARAMETER: CO TRUNK ACCESS: TRUNK ACCESS TA TOLL ACCESS: TRUNK ACCESS TAAMO-COP -111 CLASS OF PARAMETER FOR DEVICE HANDLERDISPLAY COMPLETED; <dis-cossu:cos,77;DIS-COSSU:COS,77;H500: AMO COSSU STARTED +------+-----------------+---------------+-----------------+ | COS | VOICE | FAX | DTE | +------+-----------------+---------------+-----------------+ | 77 |> | | | TA | TA | TA | | | TNOTCR | TNOTCR | TNOTCR | | | | BASIC | BASIC | | | | | | +------+-----------------+---------------+-----------------+AMO-COSSU-111 CLASSES OF SERVICEDISPLAY COMPLETED; <

Every extension (for Hipath4000 only) being served by the KCS server must have MB in its COS and MBbutton configured:CHA-SBCTU:STNO=<…>,PMIDX=1; /* FOR HIPATH-4000 ONLY */ADD-RICHT:PM,1,,,704000, "TOPCALL",OTHER;ADD-RICHT:LRTENEW,70,ALL,"TOPCALL ", 40,400,YES,,FIX,DIGITS,"DTMF:",PP300;ADD-LODR:70,,,,NPI,UNKNOWN ,UNKNOWN ;ADD-LODR:70,,,,ECHO,2;ADD-LODR:70,,,,END;ADD-LDAT:70,ALL,1,,40,70,1;ADD-WABE:70,,,TIE;ADD-LDPLN:70-XXXX,,70,,1,,,,N;

Example for PBX2 which is not directly connected to the KCS server:

Every extension being served by the server must have MB in its COS and MB button configured.CHA-SBCTU:STNO=<…>,PMIDX=1; /* FOR HIPATH-4000 ONLY */ADD-RICHT:PM,1,,,704000, "TOPCALL",OTHER;ADD-RICHT:LRTENEW,70,ALL,"TOPCALL ", 30,400,YES,,FIX,DIGITS,"DTMF:",PP300;ADD-LODR:70,,,,NPI,UNKNOWN ,UNKNOWN ;ADD-LODR:70,,,,ECHO,1;ADD-LODR:70,,,,ECHO,2;ADD-LODR:70,,,,END;ADD-LDAT:70,ALL,1,,30,70,1;ADD-WABE:70,,,TIE;ADD-LDPLN:70-XXXX,,70,,1,,,,N;

21


Call Transfer and Path Replacement (Route Optimization)Call Transfer needs the COT parameter CEBC (UELM in German installations).

Activate the Path Replacement (route-optimization):AMO ZAND: branch ALLDATA, NODECD=<nodeNr>AMO WABE: <nodeNr>, .. EIGENKZAMO RICHT: ROUTOPT=YESAMO TDCSU: <cotNr>: AMO COT: ROPTAMO ZAND: branch ALLDATA, ROUTOPTD=N,ROUTOPTP=N

<nodeNr> is the own NodeCD number, e.g. 3020

<cotNr> is the COT number of the QSIG trunk

The own nodeCD number is a prerequisite for the PBX to perform the Path Replacement after the CallTransfer.

Example of configuration with own node number “3020”:ABFRAGEN-ZAND:DATENALL;H500: AMO ZAND GESTARTET ALLGEMEINE SYSTEM-DATEN: ======================== UMLEGEN = UEBERG , HINWEIS = NEIN, BERERH = FBKW , FREITON = NEIN, UMLVERH = NEIN, ENACHT = NEIN, NACHTBER = FBKW , VBZAUL = NEIN, HALTETON = MUSIK , ANATESIG = TON , DRPANZ = 10, AWTON = JA , KONFAMT = JA , RWSAMT = NEIN, DATANZFO = TTMM, LANDKZ = 1 , WANRBEG = NEIN, MELODIE = 1, FANGKZ = , CPBLOWL = 80 , CPBUPPL = 100, DURCHZL = NEIN, PREDIA = JA , SIUSPKZ = 1, AMTRUF = NEIN, COEXN = 0 , ANZRR = 5 , SEVDIG = NEIN, KNNR = 1 , DISPMODE = MODE1, KNOTENKZ = 3020 , ROUTOPTE = NEIN, ROUTOPTS = NEIN, CALLOFF = NEIN, PARARUF = NEIN, DRZIELP = JA , ONEPARTY = NEIN, MELDVER = NEIN, RWSAMTB = NEIN, VAMTAMT = JA , WAKOZIVO = NEIN, ANSAMT = NEIN, ROEDEAKT = NEIN, WAMAKELN = NEIN, AULPRUEF = NEIN, HTONSAAO = NEIN, NAWAVERZ = NEIN, VERMANKL = NEIN, AUFSMZST = JA , AUFSSA = NEIN, AKNASTAS = JA , WAUEBSAO = NEIN, GESPNAUF = NEIN;AMO-ZAND -222 ZENTRALE ANLAGENDATENABFRAGEN DURCHGEFUEHRT; <AB-WABE:ALLG,3020;H500: AMO WABE GESTARTET ------------------------------------------------------------------------------ | WAHLBEWERTUNG GUELTIG FUER ALLE WABE-GRUPPEN | ------------------------------------------------------------------------------ | | VERKEHRSSITUATION | | VORLEIST/RUFUM | | RUFNUMMER | 1 11111 11112 22| KENNZAHL | DNI/ZUSATZINFO | | |0 12345 67890 12345 67890 12| PUNKT | *=EIGENER KNOTEN | ------------------------------------------------------------------------------ | 3020 |. .**** ***** **... ..... ..| EIGENKZ | | ------------------------------------------------------------------------------AMO-WABE -222 WAHLBEWERTUNG

22


ABFRAGEN DURCHGEFUEHRT; <

Note With some installations a problem may occur while transferring calls from KCS Server to thePSTN (e.g. someone uses TC/Dialer and lets his local extension be transferred to a mobile number).In such a case the Hicom300/Hipath4000 informs the public network on the activated call transfer, butit may occasionally happen that this communication between Hicom300/Hipath4000 and CO (centraloffice) does not work properly and as a consequence, the calls towards KCS are disconnected (a facilitymessage with an empty facility information element is sent to KCS and this leads to protocol error anddisconnection).

If such a situation following patches may be helpful:• For Hipath4000 1.0: MSC07365• For Hicom300 3.0: MSC03893

(The Siemens technician should verify the exact patch number necessary for the particular release).

Call Diversion ConfigurationThe “Rerouteing” network routing algorithm should be configured for the QSIG trunk for all three types ofcall diversions (CFU, CFB and CFNR) by setting following two trunk (“COT”) parameters:• AULN and RWSN (for German configurations)• FWDN and FNAN (for English configurations)

S0 Access (BRI) and S2 Access (PRI) ConfigurationThe configuration for both trunk types (S0-BRI and S2-PRI) is almost the same: the only difference is theparameter:• GERAETETYP=S0VERB (for S0)• GERAETETYP=S2VERB (for S2)

COT Parameters:• PROTVAR=ECMAV2,SEGMENT=1

In the following example the S0 (BRI) trunk with the prefix 731 is configured for Call Transfer and RouteOptimization (the Path Replacement has been activated):AB-LDPLN:RNR,731;H500: AMO LDPLN GESTARTET +----------------------------------------------------------+ | RNR 731 ---> | +-------+--------------------------------------------------+ | LWMNR | LWM | +-------+--------------------------------------------------+ | 276 | 731-X | +-------+--------------------------------------------------+AMO-LDPLN-222 EINRICHTEN WAEHLMUSTERPLAN FUER LCRABFRAGEN DURCHGEFUEHRT; <AB-LDPLN:LWM,276;H500: AMO LDPLN GESTARTET +--------------+------------------------------------------+ | | | | LWMNR : 276 | LWM : 731-X |

23


| | IPS : 22 | +--------------+------+------+------++------+------+------+ | | WABE | LRTG | LBER || WABE | LRTG | LBER | | +------+------+------++------+------+------+ | | 0 | 15 | 1 || 8 | 15 | 1 | | | 1 | 15 | 1 || 9 | 15 | 1 | | | 2 | 15 | 1 || 10 | 15 | 1 | | | 3 | 15 | 1 || 11 | 15 | 1 | | | 4 | 15 | 1 || 12 | 15 | 1 | | | 5 | 15 | 1 || 13 | 15 | 1 | | | 6 | 15 | 1 || 14 | 15 | 1 | | | 7 | 15 | 1 || 15 | 15 | 1 | +--------------+------+------+------++------+------+------+AMO-LDPLN-222 EINRICHTEN WAEHLMUSTERPLAN FUER LCRABFRAGEN DURCHGEFUEHRT; <TYP =LRTG =LDIENST =AB-LDAT:,15,;H500: AMO LDAT GESTARTET +--------------------------------------------------------------------------+ | LRTG = 15 LDPLN NAME = S0-VERB KZ 731 DIENST = ALLE | | TYP = LCR ZKNNR-RICHTUNG = 105 | +-------+-------+-------+-----+-----+----------+------------+----+---------+ | | | | | | ZEITBAND | CARRIER |BAND| | |LRTGEL | LWERT | BUNUM | LWR |LBER | ABCDEFGH | ZONE | BR | LATTR | +-------+-------+-------+-----+-----+----------+------------+----+---------+ | 1 | 1 | 15 | 2 | 1 | ******** | 1 LEER | 1 | GEBAKT | +-------+-------+-------+-----+-----+----------+------------+----+---------+AMO-LDAT -222 LCR-RICHTUNGENABFRAGEN DURCHGEFUEHRT; <ART =LRTG =LDIENST =AB-RICHT:LRTG,15,;H500: AMO RICHT GESTARTET ----------------------------------------------------------------- | LRTG = 15 NAME = S0-VERB KZ 731 DIENST = ALLE | | ZKNNR = 105 | | ROUTOPT = JA REROUT = NEIN VLVER = NEIN UMLVER = NEIN | | MFV: UMS=FIX ANZ=OHNE TEXT= PULS=PP300 | | RTGNR = 12 BUGS = LIN MAINGROUP = 12 | ----------------------------------------------------------------- | BUNUM = 15 LDAT S0 - QUER KZ 731 SUBGROUP = 16 | -----------------------------------------------------------------AMO-RICHT-222 RICHTUNGABFRAGEN DURCHGEFUEHRT; <LAGE1 =AB-TDCSU:1-1-61-1;H500: AMO TDCSU GESTARTET +---------------------------------------------------------------------------+ | GER = S0VERB LAGE = 1-01-061-1 | |---------------------------------------------------------------------------| | COTNR = 120 COPNR = 130 WABE = 0 | | VBZ = 15 COS = 42 LCOSS = 7 | | LCOSD = 7 SATZNR = ZLNR = 0 | | PROTVAR = ECMAV2 SEGMENT = 1 TCHARG = N | | ANZUNT = 0 ZIVO = CHIMAP = N | | ISDNCC = ISDNAC = ISDNLC = | | ISDNIP = ISDNNP = | | PNPL2C = PNPL1C = PNPLC = |

24


| PNPL2P = PNPL1P = | | TRACOUNT = 31 SATCOUNT = VIELE KNNR = 105 | | ALARMNR = 0 FIDX = 1 CARRIER = 1 | | ZONE = LEER COTX = 121 AULX = 5 | | DOMTYP = DOMAINNR = TPROFNR = | | ENACHT = | |---------------------------------------------------------------------------| | INBETR = J BUNR = 15 SUCHART = ZYK | | MASTER = J SMD = J CNTRNR = 0 | | BKVER = N | +---------------------------------------------------------------------------+ ANZAHL DER B-KANAELE IN DIESER AUSGABE: 2AMO-TDCSU-222 DIGITALE SAETZEABFRAGEN DURCHGEFUEHRT; <AB-LODR:2;H500: AMO LODR GESTARTET +-------------------------------------------------------+ | LWR LWRELPOS LWREL PARAMETER | +--------+----------------------------------------------+ | 2 | 1 ECHOFELD 2 | | | 2 ENDE | +--------+----------------------------------------------+H03: DIE NAECHSTE FREIE LWR IST 6AMO-LODR -222 ADMINISTRATION VON LCR-WAHLREGELNABFRAGEN DURCHGEFUEHRT; <AB-BUEND:15;H500: AMO BUEND GESTARTET+------------------------------------------------------------------------------+| BUENDELNUMMER : 15 BUENDELNAME: S0 - QUER KZ 731 MAX-ANZAHL: 2 || UNTERGR.NUMMER: 16 GERAETETYP : S0VERB ANZFANG : 0 || RESERVIERT : N SUCHART : ZYKLISCH ANZACD : * || MINDESTENS EINER RICHTUNG ZUGEORDNET || FOLGENDE SATZLAGEN (LTG-LTU-BAUGRUPPE-SATZNUMMER) SIND ZUGEORDNET: |+------------------------------------------------------------------------------+| 1- 1- 61-1 B-CHL: 1 | 1- 1- 61-1 B-CHL: 2 | : |+------------------------------------------------------------------------------+AMO-BUEND-222 BUENDELABFRAGEN DURCHGEFUEHRT; <AB-COT:120;H500: AMO COT GESTARTET COT: 120 PARAMETER: ANRUF BEI EINHAENGEN IN RUECKFRAGE AERF UMLEITEN AMTSGESPRAECH UASE MELDEN VON DER LEITUNG MVLT UEBERGABE IM BESETZT-, RUF- ODER GESPRAECHSZUSTAND UELM QUERLEITUNG QUER ANRUFUMLEITUNG NETZWEIT ERLAUBT AULN RUFWEITERSCHALTUNG NETZWEIT ERLAUBT RWSN AMTSWAEHLTONEINSPEISUNG BEI GEHENDEN AMTSBELEGUNGEN AWTE LEITUNG OHNE KNOTENNUMMER LOKN LEITUNG FUEHRT ZU KNOTEN MIT ROUTE OPTIMIERUNG ROPT KOMMENDE LEITUNG VON ANLAGE OHNE LCR OLCR TSC-SIGNALISIERUNG DER EXTERNEN BRIEFKASTENMELDUNGEN TSCS LEITUNG SENDET BETRAEGE AN URSPRUNGSKNOTEN LTMB VOREINGESTELLE KNOTENNUMMER DER LEITUNG VERWENDEN VKNN KOMMENDE LEITUNG VON ANLAGE OHNE LCR (DATEN) OLRD KEIN TON KTONAMO-COT -222 CLASS OF TRUNKABFRAGEN DURCHGEFUEHRT; <

25


DTMF Generation on Optiset/Optipoint SetsIt is typically not possible to generate DTMF tones after the Optiset/Optipoint has been called from theKCS Server, e.g. by TC/Dialer (in other words, Optiset/Optipoint has received an incoming call).

DTMF generation may be enabled by the following command for such cases:DIS-WABE:GEN,,,,DTMFCONV;*# …………………DTMFCONV

Now after the user has answered an incoming call on his Optiset/Optipoint set, he may press *# to enablegenerating of DTMF for this call.

In order to enable generating DTMF tones for each incoming call without typing any enabling sequencelike *#, the installation of a specific Hicom/Hipath patch may be necessary.

Note This problem does not occur if Optiset/Optipoint originates the call.

Nortel Meridian 1 R25.40b QSIG IntegrationThis section describes the integration with Nortel Meridian 1 R25.40b QSIG.






PBX vendor Nortel

PBX Type Meridian 1 (Option 11C)

Protocols ETSI-QSIG and ISO-QSIG

PBX SW release(s) 25.40b, with patch p16326B1 (this patch was only necessary for CT+PRfunctionality for the BRI access)

Tested functions BC, MWI, CD, CT, PR

26



AOC was not tested, as not supported by TC QSIGPath Replacement after CT does not work if switchboard is involved in oneof the two calls to be transferredThis is a general Meridian 1 restrictionDuring the Call Transfer the primary call could not be put on HOLD thereforethe CT without HOLD must be used for this PBXMeridian 1 performs the Path Replacement as late as about 7-8 secondsafter successful Call Transfer by joinIn order to shorten this time, following patches may be applied on theMeridian side: P18933_1 and P18812_1Succession 3.0 problemhere was a problem that MWI was not working using Meridian’s successor“Succession 3.0”, applying the patch nr. 18305 solved the problem

Summary Integration tests were successfulMeridian 1 is validated to be used with KCS Server Model 305 usingboth BRI and PRI QSIG connections as wellSuccesion 3.0 was not validated, but it is known that it works with thesame configuration as described here for Meridian 1 assuming thepatch 18305 has been applied


Abbreviations BRI and PRI are used for basic and primary rate trunk

2. QSIG protocol variantsMeridian 1 supports two QSIG protocol variants – ISO and ETSI – that are not compatible with eachother. The protocol variant is the trunk-related parameter.Both ISO-QSIG variant (Meridian parameter IFC=ISGF) and ETSI-QSIG (Meridian parameterIFC=ESGF) are compatible with KCS ISO-QSIG and ETSI-QSIG configurations (setup in the UIFconfig line 286, pos. 8)It is recommended to use the ISO-QSIG protocol variant on both sides (default QSIGconfiguration on KCS side).Note that Meridian 1 differs between QSIG-BC (“basic call”) and QSIG-GF (“generic functionalprotocol”). For a KCS Voice integration QSIG-GF is necessary.

3. Configuring Message Waiting Indication (MWI)No „Message Centre ID“ parameter needs to be setup in the PBX, it is recommended to generateMWI orders on KCS side with empty „Message Centre ID” parameter.

4. Call Hold & Call TransferMeridian 1 supports Call Transfer by join “into ringing”, but 1st (primary call) call of the two calls to betransferred must not be put on Hold prior to the transfer as Meridian does not support remote Holdnotification (UIF config line 295, pos. 5 set to 01 and pos. 6 set to 00).

5. Network algorithm “Rerouteing” for Call diversions not supportedMeridian 1 supports only the “Forward Switching” algorithm to perform call diversions via QSIG trunk(in the case KCS places an outgoing call to a Meridian 1 extension that is being forwarded to otherextension, Meridian 1 establishes at first the 2nd call and then joins both calls together. On the other

27


hand, with “Rerouteing” Meridian 1 would only instruct KCS to disconnect the call to the 1st extensionand establish the 2nd call to the other).The only drawback resulting from this limitation is that KCS would not be able to optimize loopsduring complex Call Transfer & Call Diversion scenarios.For example, the caller would be transferred by the TC/Attendant function to an extension that isforwarded to the KCS server again – such a call would occupy 3 lines. But if the PBX would supportRerouteing method, KCS would switch the caller to the desired mailbox internally while occupyingonly one line).

6. Meridian 1 “Options” and relevant SW releases for QSIGThere are several possible “options” of Meridian 1 PBX – like 11C, 51C, 61C and 81C. The Meridian 1 “option” only characterizes particular hardware and line capacity (number ofprocessors, lines etc.) but has no impact on specific features as the software releases are the samefor all options.In the following see the approximate QSIG development through different Meridian 1 releases:• Rel 22.xx – QSIG-BC implemented• Rel 23.47 – QSIG-GF, Call Diversions (“redirecting number”), Path Replacement• Rel 24.25 – Call Transfer• Rel 25.40 - MWI

PBX ConfigurationThis section describes the PBX configuration.

BRI Access RouteBRI Route:LD:16TYPE RDBCUST 00DMODROUT 11 * route number, to be defined by PBX adminDES ISO_QSIG * only descriptionTKTP TIENPID_TBL_NUM 0ESN NORPA NOCNVT NOSAT NORCLS EXTDTRK YESDGTP BRI * basic rate accessIFC ISGF * ISO QSIG-GF (ESGF would indicate ETSI-QSIG-GF, but not recommended)CLID OPT0SIDE NET * Meridian is the Master (Network side)CNEG NOOVLR YES * Overlap receiving, can be also NODIDD 0OVLS YES * Overlap sending, can be also NOOVLT 0MBGA NOPGPN 1 * remote capabilities PRI-Path replacement, DV3I-Call Diversions, * CTI-Call Transfer, QMWI-Message waiting; the trailing “I” stands for

28


* “Integer” coding (on the other hand, trailing “O” would indicate “ObjectID” * coding – e.g. QMWO – but don’t use it !)RCAP COLP NDI CCBI CCNI PRI DV3I CTI QMWIPR_TRIGS DIV 15 1 * Path Replacement triggers CNG 15 1 CON 15 1 CTR 15 1 * Call Transfer trigger (15 attempts in 1 min. intervals) * note that patch p16326B1 has to be used for this trigger * to work properly via BRI !PR_RTN NOISDN YES MODE PRA * confusing, but this parameter was really set to PRA for BRI trunk … PNI 00000 NCNA NO NCRD NO CHTY BCH INAC NO CPFXS YES DAPC NO INTC NODSEL VODPTYP DTTAUTO NODNIS NODCDR NOICOG IAOSRCH LINTRMB YESSTEPACOD 8811TCPP NOTARGBILN NOOABSINSTIDC NODCNO 0 *NDNO 0DEXT NOSIGO STDSTYP SDATMFC NOICIS YESOGIS YESTIMR ICF 512 OGF 512 EOD 13952 DSI 34944 NRD 10112 DDL 70 ODT 4096 RGV 640 GTO 896 GTI 896 SFB 3 IENB 5 TFD 0 VSS 0 VGD 6SST 5 0DTD NOSCDT NO2 DT NO

29


NEDC ETHFEDC ETHCPDC NODLTN NOHOLD 02 02 40SEIZ 02 02SVFL 02 02DRNG NOCDR NONATL YESSSLCFWR NOIDOP NOVRAT NOMUS NOPANS YESMANO NOFRL 0 0FRL 1 0FRL 2 0FRL 3 0FRL 4 0FRL 5 0FRL 6 0FRL 7 0OHQ NOOHQT 00CBQ NOAUTH NOTTBL 0ATAN NOOHTD NOPLEV 2OPR NOALRM NOART 0PECL NODCTI 0TIDY 8811 11SGRP 0AACR NOLD:27TN 4 0 0 3APPL BRIE ISDN_MCNT 300CUST 0CTYP SILCMISP 3MODE NTTKTP TIECLOK NOPDCA 2ROUT 11 * route numberT302 15T310 120B1 MEMB 1 TGAR 0 NCOS 0 CLS UNR APNB2 MEMB 2 TGAR 0 NCOS 0

30


CLS UNR APNDATE 3 JUN 2003

PRI Access RoutePRI Route:LD:16TYPE RDBCUST 00DMODROUT 10 * route number, to be defined by PBX adminDESTKTP TIENPID_TBL_NUM 0ESN NORPA NOCNVT NOSAT NORCLS EXTDTRK YESBRIP NODGTP PRI2 * PRI2- E1 PRI, PRI – T1 PRI accessISDN YES MODE PRA IFC ISGF * ISO QSIG-GF (ESGF for ETSI-QSIG-GF, but not recommended for KCS !) SBN NO PNI 00000 NCNA NO NCRD NO CTYP UKWN INAC NO ISAR NO CPFXS YES DAPC NO INTC NODSEL VODPTYP DTTAUTO NODNIS NODCDR NOICOG IAOSRCH LINTRMB YESSTEPACOD 8810TCPP NOTARGBILN NOOABSINSTIDC NODCNO 0 *NDNO 0DEXT NOSIGO STDMFC NOICIS YESOGIS YESTIMR ICF 512 OGF 512 EOD 13952 NRD 10112 DDL 70

31


ODT 4096 RGV 640 GTO 896 GTI 896 SFB 3 NBS 2048 NBL 4096 IENB 5 TFD 0 VSS 0 VGD 6DTD NOSCDT NO2 DT NODRNG NOCDR NONATL YESSSLCFWR NOIDOP NOVRAT NOMUS NOPANS YESFRL 0 0FRL 1 0FRL 2 0FRL 3 0FRL 4 0FRL 5 0FRL 6 0FRL 7 0OHQ NOOHQT 00CBQ NOAUTH NOTTBL 0ATAN NOPLEV 2OPR NOALRM NOART 0PECL NODCTI 0TIDY 8810 10SGRP 0AACR NOLD:14DES ISGFTN 002 01TYPE TIECDEN SDCUST 0TRK PRI2PDCA 2PCML A * A- A-law encoding, MU-u-law encodingNCOS 0RTMB 10 1 * route number and member numberB-CHANNEL SIGNALINGTGAR 0AST NOIAPG 0CLS UNR DIP CND WTA LPR APN THFD XREP BARD P10 VNLPRI : DCH

32


LD:17ADAN DCH 10 CTYP MSDL CARD 02 PORT 1 DES iso_qsig * only description USR PRI DCHL 2 OTBF 127 PARM RS422 DTE DRAT 64KC CLOK EXT IFC ISGF * ISO QSIG-GF (ESGF for ETSI-QSIG-GF, but not recommended for KCS !) PINX_CUST 0 ISDN_MCNT 300 CLID OPT0 CO_TYPE STD SIDE NET * Meridian is the Master (Network side) CNEG 1 RLS ID ** QCHID NO * Logical B-channel numbering used (B1…B30), YES would indicate using of * QSIG non-conform timeslot numb. (1..15, 17..31), not recommended for KCS !) * This parameter is relevant only for E1 PRI, not for T1 PRI ! RCAP COLP NDI CCBI CCNI PRI DV3I CTI QMWI *remote capabilities – see BRI configuration PR_TRIGS DIV 15 1 * Path Replacement triggers CNG 15 1 CON 15 1 CTR2 15 1 * Call Transfer trigger (15 attempts in 1 min. intervals) PR_RTN NO MBGA NO OVLR YES DIDD 0 OVLS YES OVLT 0 T310 120 T200 3 T203 10 N200 3 N201 260 K 7

Special Considerations for Path ReplacementPath Replacement (route-optimization) after Call Transfer is configured in corresponding BRI or PRI route(see Path replacement triggers).

But there is still “own node number” (PINX_DN parameter) in the customer data that identifies ownnode in the PBX network and that must be set to any valid value so that Meridian would initiate PathReplacement at all.LD 15:TYPE NET_DATACUST 00OPT RTDAC2FNP YESISDN YES PNI 2222 PINX_DN 8800 * Meridian PINX number MBG 0

33


BSGC 65535 PFX1 PFX2 HLOC LSC RCNT 5 PSTN NO TNDM 15 PCMC 15 SATD 1 OCLI NOTIDM NODASCROPT NRO * this is only for DPNSS, irrelevant for QSIGDITI YESTRNX YESEXTT YESFTOP FRESAPAD 0 0VNR NONIT 8NAS ATCL NONAS ACTV NOFOPT 2CNDNCNATCNIP YESDMWM NOMWNS NO

Special Considerations for Message Waiting and Call Diversions1. There is no need to setup any “Message CentreID” parameter for the MWI function, it is not

supported by Meridian PBX. Send orders on KCS for MWI should have the “Message CentreID”parameter empty (even though it seems to work with any “Message CentreID” parameter).

2. It is necessary to enable MWI indication on the telephone set.

3. It is possible to program the Voice Mail button on the telephone to reach the Voice Server after theMWI lamp has been switched on.

4. It is necessary to enable different call forward types on the telephone set.

See an example of the Meridian 1 setup for an extension “1002” with MWI and call forwards (CFU, CFBand CFNR) enabled:LD:15DES TESTTN 005 0 00 03TYPE 2616CDEN 8DCUST 0AOM 0FDN 006645045929 * The destination for CFNRTGAR 0LDN NONCOS 0SGRP 0RNPG 1SCI 0SSULNRS 16

34


XLST 2SCPWSFLT NOCAC_MFC 0 * MWA–enable MWI, FNA–enable CFNR, HTA–enable CFB, CFXA–enable CFU to ext. numberCLS UNR FBA WTA LPR PUA MTD FNA HTA ADD HFD MWA LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1 POD DSX VMD CMSD SLKD CCSD SWD LNA CNDA CFTD SFA MRD DDV CNID CDCA MSID DAPA BFED RCBD ICDD CDMD MCTD CLBD AUTU GPUD DPUD DNDA CFXA ARHD CLTD ASCD CPFA CPTA ABDD DELD CFHD FICD NAID BUZZ AGRD MOAD UDI RCC HBTD AHD IPND DDGA NAMA MIND PRSD NRWD NRCD NROD DRDD EXR0 USRD ULAD RTDD RBDD RBHD PGND OCBD FLXD FTTC DNDY DNO3 MCBN FDSD NOVDCPND_LANG ENGRCO 0HUNT 006645045929 * The destination for CFBLHK 0PLEV 02ASTIAPG 0AACS NOITNA NODGRPMLWU_LANG 0DNDR 0KEY 00 SCR 1002 0 MARP CPND CPND_LANG ROMAN NAME Nebenstelle 1002 XPLN 27 DISPLAY_FMT FIRST,LAST 01 TRN 02 AO6 03 CFW 16 92999 * The destination for CFU 04 RGA 05 06 MWK 91999 * Voice Server access number 07 08 EOVR 09 10 11 12 13 14 15DATE 4 JUN 2003

Philips Sopho IS3000 R6810.32E QSIG IntegrationThis section describes the integration with Philips Sopho IS3000 R6810.32E QSIG.


35






PBX vendor Philips

PBX Type Sopho IS3000

Protocols realQSIG

PBX SW release(s) 6810.32E, PROM release 140.32.4

Tested functions BC, MWI, CD, CT, PR


AOC was not tested, as not supported by TC QSIGPath Replacement after CT does not work (Sopho does not trigger PR aftersuccessful CT by join)During the Call Transfer the primary call could not be put on HOLD, thePBX obviously does not support call HOLD, therefore the CT without HOLDshould be used for this PBX

Summary Integration tests were successfulMeridian 1 is validated to be used with KCS Server Model 305 usingboth BRI and PRI QSIG connections as well


Abbreviations BRI and PRI are used for basic and primary rate trunk

2. QSIG protocol variantsSopho supports two QSIG protocol variants – QSIG and “real QSIG”. The QSIG comprises only thebasic call functionality, the “real QSIG” comprises basic call and supplementary services as well.Therefore “real QSIG” is recommended to be used for KCS integration.The “real QSIG” corresponds with the ISO-QSIG protocol variant (default QSIG configuration onKCS side).

3. Configuring Message Waiting Indication (MWI)No explicit configuration is necessary for MWI for Sopho, the PBX does not support the „MessageCentre ID“ parameter. It is recommended to generate MWI orders on KCS side with empty „MessageCentre ID” parameter.

4. Call Hold & Call TransferMeridian 1 supports Call Transfer by join “into ringing”, but 1st (primary call) call of the two calls tobe transferred need not be put on Hold prior to the transfer as Sopho does not support remote Holdnotification (UIF config line 295, pos. 5 set to 01 and pos. 6 set to 00).

5. Path Replacement (PR) after Call Transfer does not work (no route optimization)

6. Network algorithm “Rerouteing” for Call diversions not supportedMeridian 1 supports only the “Forward Switching” algorithm to perform call diversions via QSIG trunk(in the case KCS places an outgoing call to a Sopho extension that is being forwarded to otherextension, Sopho establishes at first the 2nd call and then joins both calls together. On the other

36


hand, with “Rerouteing” Meridian 1 would only instruct KCS to disconnect the call to the 1st extensionand establish the 2nd call to the other).

7. Sopho Models and relevant SW releases for QSIGThere are several possible models of Sopho PBX that depict using of particular hardware and linecapacity (processor type, number of processors, lines etc.) but has no impact on specific features asthe software releases are the same for all models:Small models are: IS3000, 3010, 3030, 3050 and the current SW release is 6810.32ELarge models are: IS3070, 3090 and the current SW release is 9810.32E(the leading 6xxx or 9xxx stand more or less only for model type)

PBX ConfigurationPHILIPS SOPHO iS3000 Projecting DataSettings for "Real QSIG" - Route:<dirout:30 ROUTE UNIT BSPT GEN-OPTS GEN-TONE CV CC-TABLE 30 1 - 00100100000000550550 0 - INC-OPTS TONE-AND-DDI-OPTS TREE A-QUEUE OVE SCNE 10100000000 000722222 0 16 - - OUT-OPTS ATF 001100 0NO INCOMING DIGIT CONV. ON THIS ROUTE (USE DIDGCO FOR OUTGOING DIGIT CONV.) SEQ BUNDLE 0 30EXECUTEDSettings for "Real QSIG" - Bundle:<dibndl:30;BUNDLE BSPT ROUTE UNIT DIR-AND-NEG OPTIONS CON-AND-SIG-TYPE ALL-CALLS 30 - 30 1 2 2 0000000000000000 4 20 - *** 20 = A-Side (recommended) *** 21 = B-Side Board Parameter:Primary rate (PRI): Signalling Group: 5d21 (NNN) *** network side layer 3-1 (recommended) 5D20 (UUU) *** user side layer 3-1 (for info only !)Basic rate (BRI): Signalling Group: 5c21 (NNN) *** network side layer 3-1 (recommended) 5c20 (UUU) *** user side layer 3-1 (for info only !)Special considerations in the Network Parameter Block (MNPB):In the MNPB change byte 35 from 0 to 1 meaning: 1 stands for logical B channel numbering on PRI (1…30) 0 would stand for timeslot B channel numbering on PRI (1…15, 17…31)In the MNPB the byte 24 must have value 1 (PRI_CRC4_Multiframing)As for Path replacement (PR) the Option 83 must be TrueDTU – Prom release >= 140.32.4

37

Version: 10.3.0 PBX Integration Technical Manual · 2021. 3. 17. · Philips Sopho IS3000 R6810.32E...

Documents

Transcript of Version: 10.3.0 PBX Integration Technical Manual · 2021. 3. 17. · Philips Sopho IS3000 R6810.32E...