Howto:How To Configure QSIG Interworking, V5: Difference between revisions
(Related Articles points to v6 article) |
m (→Applies To) |
||
Line 57: | Line 57: | ||
Build 5806 and later | Build 5806 and later | ||
* for a V6 version of this article see [[#Related Articles|Related Articles]] | |||
==More Information== | ==More Information== |
Revision as of 10:21, 9 September 2009
QSIG Interworking is a feature of the innovaphone PBX in conjunction with the innovaphone gateway.
The feature allows to translate H.323 supplementary services into QSIG supplementary services and vice-versa.
The following table lists the features, respectively the QSIG supplementary services that can be interworked:
Feature | Standard | Messages |
Name Display | ECMA-164 | CallingName,calledName,connectedName |
Call Completion
- To busy subscriber (CCBS) - With no reply |
ECMA-186 | CcnrRequest,ccbsRequest,ccCancel,
ccExecpossible,ccPathReserve,ccRingout |
A subset of Call Transfer (actually name Display) | ECMA-178 | CallTransferComplete |
A subset of Call Diversion | ECMA-174 | CheckRestriction,callRerouting,
divertingLegInformation1,..2,..3 |
In order to use QSIG Interworking…
- the protocol at the affected ISDN interface must be configured to QSIG ECMA 2.
- The checkmark Interworking (QSIG) must be activated at the voice routes (actually at the maps), that lead from the gateway into the PBX.
Don’t forget to activate the checkmark at the opposite routes (from the PBX towards the gateway).
However this applies only for routes that are supposed to provide QSIG Interworking.
- The gateway must not be used to modify or to patch called party number numbers (CDPN) and/or calling party numbers (CGPN).
If this limitation is not regarded, Call Completion and Call Diversion cannot be interworked.
Applies To
This information applies to
- Innovaphone gateways and PBXs
Build 5806 and later
- for a V6 version of this article see Related Articles
More Information
System Requirements
Firmware version 5.01
- The informations, given within this document, were tested and verified against a Siemens Hicom 300 E PBX. They are expected to be applicable to PBXs of other manufacturers, as well.
- It is recommended to configure the protocol QSIG ECMA II on all involved interworking devices.
Hicom 150: It turned out that a Hicom 150 had to be configured to ISO QSIG
Hicom 300 E: Configure to ECMAv2
Installation
Configuration
There are two recommended ways of configuration
- By means of the location object
- By means of the _EXTERN_ user
By Location Object
If different numbering plans with different prefixes do exist in the network, then this method must be applied.
The location object is a PBX object. It allows to configure a numbering-prefix in order to keep apart different dialing plans/numbering plans.
If a modification of a CDPN or a CDPN becomes necessary this task is automatically being accomplished by the location object.
The procedure is to simply configure one location object for each QSIG PINX that exists in the network.
By EXTERN User
If just a single numbering plan exists and some users reside in the QSIG world while others reside in the IP world, then this method may be applied.
The EXTERN user is a built-in PBX object. It is supposed to get calls for numbers that the PBX does not know. It provides an easy method to route those calls from the PBX into the gateway without modifying the CDPN or the CGPN.
Known Problems
German Umlaute may not be interworkable between the H.323 network and the QSIG network. This limitation depends on the capability of your QSIG PINX.
The interworking option must not be used if two or more QSIG-based ISDN PBXs shall be interconnected. Interworking is solely for passing calls between a QSIG based PBX and an H.323/H.450-based system such as the innovaphone PBX.