Q-Sig Feature List
Print View
by: ianuk1974
Total views: 13
Word Count: 3498
The following lists the supported QSIG ISO features that are supported by the Mitel 3300 Release 5.0 product. For QSIG features not supported, the 3300 will not act as a transit switch. The notes below indicate functionality of a feature that is not supported by the Mitel implementation that are alternative or optional functions/implementations. Mitel describes these for the purpose of ensuring compatibility with other vendors.
|
Standard
|
Feature
|
Mitel 3300
|
|
ETS 300 012 (Ed 1)
|
Layer 1
|
X
|
|
ETS 300 402-1&2
|
Layer 2
|
X
|
|
ISO 11574, 11572
|
Audio Speech
|
X
|
|
ISO 11571
|
Numbering Plan
|
X
|
|
ISO 11582
|
Generic SS Platform (GF)
|
X
|
|
ISO 14136
|
Calling Line Identification Presentation (CLIP)
|
X
|
|
ISO 14136
|
Connected Line Identification Presentation (COLP)
|
X
|
|
ISO 14136
|
CLIP/COLP Restriction (CLIR)
|
X
|
|
ISO 13864, 13868
|
Calling Name Identification Presentation (CNIP)
|
X
|
|
ISO 13864, 13868
|
Connected Name Identification Presentation (CONP)
|
X
|
|
ISO 13864, 13868
|
CNIP/CONP Restriction (CNIR)
|
X
|
|
ISO 13872, 13873
|
Call Forwarding Unconditional (CFU)
|
X Note 1
|
|
ISO 13872, 13873
|
Call Forwarding Busy (CFB)
|
X Note 1
|
|
ISO 13872, 13873
|
Call Forwarding No Reply (CFNR)
|
X Note 1
|
|
ISO 13865, 13869
|
Call Transfer (CT)
|
X (By join)
|
|
ISO 13863, 13874
|
Path Replacement (PR)
|
X Note 2
|
|
ISO 14841, 14843
|
Call Offer (CO)
|
X Note 3
|
|
ISO 15505, 15506
|
Message Waiting (MWI)
|
X Note 4
|
|
ISO 15055, 15056
|
Transit Count (TC)
|
X
|
|
ISO 13866, 13870
|
Call Completion on No Reply (CCNR)
|
X Note 5
|
|
ISO 13866 13870
|
Call Completion Busy Subscriber (CCBS)
|
X Note 5
|
|
ISO 13866 13870
|
Call Completion No Answer (CCNA)
|
X Note 5
|
X – Supported (with notes, below)
Note 1: Does not support Interrogation a means by which to determine the call forwarding status of a remote set.
Note 2: Only support Originator Requesting Path Replace ither end may ask for the route optimization but Mitel only supports this for the originator. It is recommended that the route optimization timer on the Mitel switch be set shorter than the other side so that the Mitel switch initiates the optimization request.
Note 3: Only support without path retention path retention retains the connection between two PBX’s so that a supplementary service can be invoked without establishing a new connection. This method holds up a trunk resource and is not supported.
Note 4: Does not support MWI interrogate function a means to determine the message waiting lamp status of a remote set.
Note 5: Does not support connection and non-service retention connection retention holds up a virtual call between the two end-points. Mitel supports path reservation which ensures that resources are available when User B can accept User A’s call and service retention in that the call is compelled to complete.
|
|
