Howto:QSIG Interworking Interoperability Ericsson MD110: Difference between revisions
Jump to navigation
Jump to search
m (New page: right ==Product name== QSIG Interworking Interoperability List, Ericsson MD110 ==Applies to== This information applies to * PBX and Gateways with V6 * E...) |
(No difference)
|
Revision as of 10:37, 18 June 2007
Product name
QSIG Interworking Interoperability List, Ericsson MD110
Applies to
This information applies to
- PBX and Gateways with V6
- Ericsson MD110 with Firmware BC12 SP5 and higher
More Information
Innovaphone QSIG Interworking translates H.323 supplementary services into QSIG supplementary services and vice-versa. This article discusses the interoperability with a distinct 3rd party product.
System Requirements
- Innovaphone ISDN protocol settings must be set to ECMA2
- MD110 ISDN protocol setting must be set to ECMA2
Standards
- Ecma-164 (QSIG-NA), Name Identification/Name Display
- Ecma-174 (QSIG-CF) Call Diversion
- Ecma-178 (QSIG-CT) Call Transfer
- Ecma-186 (QSIG-CC) Call Completion
- Ecma-176 (QSIG-PR), Path Replacement
Limitations
QSIG-CC
- Innovaphone only supports call completion with connection retention.
- Innovaphone only supports call completion without path reservation.
List of Interworked Operations
- The Standard refers to a paper listed in the Standard section from above.
- The Operation column refers to an explicit message exchange within such a standard.
- The Active column tells, whether innovapahone supports this message outbound, i.e. whether innovaphone can invoke the service actively.
- The Passive column informs about inbound support for a message exchange.
| Standard | Operation | Active | Passive | Notes |
|---|---|---|---|---|
| QSIG-NA | ||||
| CallingName | Yes | Yes | ||
| Called Name | Yes | Yes | ||
| ConnectedName | Yes | Yes | ||
| BusyName | Yes | Yes | ||
| QSIG-CF | ||||
| CheckRestriction | No | Yes | ||
| CallRerouting | Yes | Yes | ||
| DivertingLegInformation1 | Yes | Yes | ||
| DivertingLegInformation2 | Yes | Yes | ||
| DivertingLegInformation3 | Yes | Yes | ||
| QSIG-CT | ||||
| CallTransferComplete | Yes | Yes | ||
| QSIG-CC | ||||
| CcnrRequest | Yes | Yes | ||
| CcCancel | Yes | Yes | ||
| CcPathReserve | No | Yes | ||
| CcRingout | Yes | Yes | ||
| CcbsRequest | Yes | Yes | ||
| QSIG-PR | ||||
| PathReplacePropose | No | n.a. | For trombone connection |
Known Problems
A CGPN.Out Map must be configured at the ISDN Interface towards the MD110, in order to turn CGPNs, belonging to a private-numbering-plan into CGPNs, belonging to an unknown-numbering-plan. Without this configuration step Call Completion will likely be failing (see following Screenshot).
