Table of Contents
Advertisement
18-10 MAUUI over RELEASE MESSAGE for NCAUUI
Forward Clearing Two Switch Scenario 2
The following figure shows how the originating user clears an NCAUUI call
using a Q.931 DISConnect message or a Q.931 RELease message before an
NCAUUI call is connected. A UUI request is included in the message, but
the UUI request is not delivered to the terminating MWC DMS-250, and the
billing field, UUIE_COUNT, is not incremented for this message.
The terminating user then sends a Q.931 CONNect message to the
terminating MWC DMS-250 switch. A UUI request is included in the
message and it is delivered to the originating MWC DMS-250. The billing
field, UUI_COUNT, is incremented at the terminating MWC DMS-250
switch. When the originating DMS-250 receives the Connection Confirm
(CC) message, it sends the SCCP RLSD message to the terminating MWC
DMS-250 switch to release the call since the originating MWC DMS-250
switch releases the call.
Figure 18-9
Forward Clearing Two Switch Scenario 2
Originating PBX
SETUP
(NCAUUI and MAUUI Request)
DISConnect/RELease
(MAUUI)
Release Complete
297-2521-106 Standard 23.01 March 2001
Originating MCI DMS–250
CR (MAUUI)
Connection Request
CC (MAUUI)
Connection Confirm
RLSD
RLC
Billing Record should have:
TP7Q = 0
UUS_TYPE = 0
UUI_COUNT = 1
Terminating MCI DMS–250
(NCAUUI and MAUUI Request)
CONNect (MAUUI)
Release
RELease COMPlete
Billing Record should have:
TP7Q = 0
UUS_TYPE = 0
UUI_COUNT = 2
Terminating PBX
SETUP
Advertisement
Table of Contents
