Note: Descriptions are shown in the official language in which they were submitted.
CA 02279845 1999-OS-17
DEMANDES OU BREVETS VOLUMiNEUX
1.A PRESENTS PART1E DE CETTE DEMANDS OU CE BREVET
COMPREND PLUS D'UN TOME.
CECI EST LE TOME ~ DE
NOTE: Pour les tomes additionels, veuiilez contacter !e Bureau canadien des
brevets
fr
JUMBO APPI~ICATIONS/PATEI11TS I
THIS SECT10N OF THE APPLICATION/PATENT CONTAINS MORE
THIS IS VOLUME .!i OF
NOTE. For additional volumes ~piease contact'the Canadian Patent OffPcE
CA 02279845 1999-OS-17
wo ~r~oso rcT~smnm4
(i) Attributes
Access Level Type Name Description
protected VOOperator* m-pOperator A pointer to the logged in
video operator
VOCalIObjMgr* rn-pCallMgr Pointer to the call object
manager
VOScheduleWnd* m_pScheduleWnd A pointer to the schedule
window
s (ii) Constructors)
VOVideoWatchVwQ;
(iii) Methods
void OnDial(); dials the number in the destination edit box.
to
void OnTransfer(); transfers the current call to a number. This will initially
display a dialog
box where the user enters the number top which the call is to be transferred.
void OnAnswer(); is called when the Answer buttan is clicked.
void OnForward(); is called when the forward button is clicked. All the call
will be
forwarded to the forwarding number provided.
void OnMute(); is called when the mute button is clicked. Turns the mute
on/off.
void OnHangup(); is called when the hang-up button is clicked. Hangs up the
current call.
void OnHold(); is called when the hold button is clicked. Puts the current
call on hold.
301
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/Z1174
void OnPickup(); is called when the pickup button is clicked. Picks up the
call on hold.
void OnPrivacy(); is called when the privacy button is clicked. Turns the
privacy on or off.
void OnPlayMovie(); is called when the Play button is clicked. This will
display a dialog
box with a list of movies to choose from. Once a movie is selected, the movie
will be played.
void OnRecordCallQ; is called when the record button is clicked.
1 o void OnJoinToConferenceQ; is called when the Join Conf button is clicked.
This will
display the list of active conferences and sites OR playback sessions. The
operator will select
the site corresponding to the current call and the call will be joined to the
conference.
void WatchVideo(BOOL selection);
~5 Return Value: returns a non-zero value if successful. zero otherwise
selection parameter: specifies what to watch.
selection = VDOWATCH CONFERENCE displays the video from the site/MCU selected
for watching __
selection = VDOWATCH SELF displays the output of the video operator's camera
2o selection = VDOWATCH CALL displays video from the call selected from the
listbox
provided in the video watch window OR the video from the incoming call, if
any.
Call the void WatchVideo function to select the video stream to watch.
25 void OnDisplayCallsWindow(); is called when the 'Calls' button is clicked.
void OnSelfViewQ; is called when the 'SelfView' check box is checked or
unchecked.
When the self view is checked, the video operator's camera output is displayed
in a separate
small window.
void OnLocalVolume(); is called when the local volume slide bar position is
changed. This
will adjust the local volume.
302
CA 02279845 1999-OS-17
WO ~ -- PGT/US97I~1174
void OnRemoteVolume(); is called when the remote volume slide bar position is
changed.
This will adjust the remote volume signal.
b) Media Control Class Description
( 1 ) VOMediaControl
Class VOMediaControl
Base Class VOObject
Inheritance Type public
Friend Classes -
(a) Attribz~tes
Access Level Type Name Description
protected struct m-portInfo This structure is used to
MtsLinkPortInfo communicate with the
MCP
(b) Constr~uctor(s)
VOMediaControl();
(c) Methoc~c
public void SetVolume(short rightVolume, short leftVolume);
rightVolume parameter: an integer between 0 - 1000.
ieftVolume parameter: an integer between 0 - 1000.
' public void SetVolume sets the volume control.
public short GetVolume(short channel);
' 20 Return Value: returns the volume for the specified channel
303
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/Z1174
channel parameter: set channel = PORT CHANNEL RIGHT for the right volume
setting,
and set channel = PORT CHANNEL LEFT for the left volume setting.
public short GetVolume returns the current volume for the specified channel
public void SetSelfView(long flags);
flags parameter: sets the properties of the self view. The valid flag values
are:
SELFVIEW ON Displays the self view;
SELFVIEW OFF Hides the self view; and
SELFVIEW MIRRORED Mirrors the self view.
public void SetSelfView sets the self view properties.
public long GetSeIfView();
Return Value: returns the self view settings
The public long GetSelfView function returns the self view settings which can
be used to find
out if the self view is visible or hidden, or if it is mirrored.
2o public void SetSelfViewSize(short size);
size parameter: one of the predefined sizes for the self view
public void SetSelfViewSize sets the size of the self view window. The valid
values are
FULL CIF, HALF CIF and QUARTER CIF.
public short GetSelfViewSize();
Return Value: returns Current self view size.
The public short GetSelfViewSize function returns the current self view window
size. The
3o values will be one of the predef ned sized. See SetSelfViewSize for the
description of the
sizes.
public void SetAutoGain(BOOL autoGain = TRUE);
304
CA 02279845 1999-OS-17
PCT/US97/21174 -
autoGain parameter: should be TRUE to enable auto gain, FALSE to disable
The public void SetAutoGain function enables or disables the auto gain
depending on the
autoGain value.
public BOOL GetAutoGainQ;
Return Value: returns The current auto gain setting.
The public BOOL GetAutoGain function returns the current auto gain setting.
TRUE if auto
i o gain is on, FALSE otherwise.
public void SetEchoCancellation (boot bCancel);
bCancel parameter: if bCancel is TRUE cancellatian is enabled; if FALSE
cancellation is
disabled.
public void SetEchoCancellation enables or disables echo cancellation.
public BOOL GetEchoCancellation U;
Return Value: returns the current echo cancellation state.
--_
public BOOL GetEchoCancellation gets the current state of the current echo
cancellation.
public short GetVideoMode(short mode = MODE RX);
Return Value: returns the video mode
mode parameter: indicates receive or transmit mode.
public short GetVideoMode gets the audio mode for receive or transmit,
depending on the
value of mode. mode = MODE RX for receive mode and MODE TX for transmit.
3o public short GetAudioMode(short mode = MODE RX);
Return Value: returns the audio mode
mode parameter: indicates receive or transmit mode.
305
CA 02279845 1999-OS-17
WO 98/23080 - PCT/US97/Z1174
public short GetAudioMode gets the audio mode for receive or transmit,
depending on the
value of mode. mode = MODE RX for receive mode and MODE TX for transmit.
public void SetVideoWnd(HWND hWnd);
hWnd parameter: pointer to the window where the video is to be dispiayed.
The public void SetVideoWnd function displays the video in the window
identified by hWnd.
public HWND GetVideoWndQ;
Return Value: returns the window handle in which the video is being displayed.
If no
window is set, NULL is returned.
The public HWND GetVideoWnd function is called to retrieve the window handle
in which
the video is being displayed. ,
public void MakeVideoWndResizeabie(BOOL bResize = TRUE);
bResize parameter: if bResize is TRUE, the video window is resizeable; if
FALSE, it is not
resizeable.
2o The public void MakeVideoWndResizeable function makes the video window
resizable with
bResize = TRUE. To make the window fixed size, make bResize FALSE.
public BOOL IsVideoWndResizeableQ;
Return Value: returns TRUE if the video window is resizeable, FALSE otherwise.
Call the public BOOL IsVideoWndResizeable function to determine if the video
window is
resizeable.
F. Video Operator Shared Database
1. Database Schema
Figure 107 shows a database schema for the video operator shared database (see
40214
Figure 98). In one embodiment, the database contains the following tables.
CONFERENCE
306
CA 02279845 1999-OS-17
WO 98J23084 PCTIL1S97IZ1174
41104 lists details about a scheduled conference, PARTICIPANT 41105 lists the
participants
of conferences, and CONF PARTICIPANT 41108 contains the keys from the
CONFERENCE 41104 and PARTICIPANT 41105 tables, which are used to determine the
participants in any given conference. MCU 41102 contains the characteristics
of different
MCU's from various suppliers, and MCUPORT 41106 contains the MCU
identification
number from the MCU 41102 table as well as the ports of the MCU used by the
participants
to connect to a conference. VOPERATOR lists video operator attributes; VOTYPES
lists all
the types (e.g., protocols, bandwidths) used to define a conference or
participant; and
VOTYPEVALUES 41107 lists the values for each of the defined types.
to
Each video operator record in the VDO OPERATOR 41101 table contains a unique
identification number in its ID field, which number may appear in the
CONFERENCE 41104
table's operatorID field, assigning each video operator to particular
conferences profiled in
the CONFERENCE 41104 table. Each conference record in the CONFERENCE 41104
table, in turn, contains a unique identification number in its ID field, which
number may
appear in the CONF_PARTICIPANT 41108 table's conflD field. Similarly; each
participant
record in the PARTICIPANT 41105 table contains a unique identification number
in its ID
field, which number may appear in the CONF_PARTICIPANT 41108 table's
participantID
field. Finally, each MCU record in the MCU 41102 table contains a unique
identification
2o number in its ID field, which number may appear in the MCUPORT 41106
table's mcuID
field, identifying the set of MCU ports associated with the MCU. Each MCU port
record in
the MCUPORT 41106 table, in turn, contains a unique identification number in
its ID field)
which number may appear in the CONF PARTICIPANT 41108 table's mcuPortID field.
Within the CONF PARTICIPANT 41108 table, the conflD, participantID, and
mcuPortID
values are used as cross-referencing keys to define a particular conference
with a given
conference profile, a set of participants, and an MCU port.
In addition, each VOType record in the VOTYPE 41103 table contains a unique
identification number in its ID field, which number rnay appear in the
VOTYPEVALUES
41107 table's typeID field, identifying a set of values associated with the
VOType.
307
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
G. Video Operator Console Graphical User Interface Windows
1. Main Console Window
Figure 108 shows one embodiment of the Main Console window 41201 as it would
appear on
a Video Operator Terminal [1 Figure 96], showing possible placements of a
Schedule
window 41202, a Conference window 41203, a Video Watch window 41204 and a
Console
Output window 41205. The Main Console window 41201 enables the video operator
to
manage video conferences.
2. Schedule Window
1o Figure 109 shows one embodiment of the Schedule window 41202, which
displays all the
conferences 41305 and playback sessions 41306 to be handled by the current
video operator
for the next 8 hours. In one embodiment, the list is updated upon application
startup, at 15
minute intervals, and every time a conference ends.
The Schedule window will have two scrolled text areas - one area for
conferences 41301, and
the other for sites 41302 participating in the selected conference. If a
conference name is
double-clicked, the appropriate Conference Window [41203 Figures 108, 110]
will appear.
3. Conference Window
2o Figure 110 shows one embodiment of the Conference window 41203, which is
displayed
when the operator selects a conference or playback session in the Schedule
window 41202.
The display of the Conference Window 41203 is dependent on whether a
Conference or a
Playback Session has been selected from the Schedule Window 41202. Only one
conference
window is displayed at a time. When a new conference window is opened, the
existing one is
hidden. While a Conference Window is hidden, the status of the conference and
connections
are still monitored. Figure 110 shows a Conference Session 41401. The
Conference window
41203 displays the list of conference Participants 41415 and radio buttons to
selectively
operate on individual connections, including call setup, viewing, playback and
recording.
Information about the conference such as the duration, start time, end time,
playback and
recording status, and conference type are displayed at the bottom of the
window. If the
operator double clicks inside the Conference Window 41203 where there is no
action
308
CA 02279845 1999-OS-17
wo oso pc~rrtJS9~m ma
associated with the clicking location, the Properties Box [41701 Figure 113]
is displayed with
the conference settings.
A conference is ended by pressing the End Conference button. This will
disconnect all calls
associated with the conference.
The Conference Window 41203 displays the connections in the conference and
their
connection status 41417, including any free MCU Port slots reserved for a not
yet joined
connection 41421. Each Connection listing contains a radio button 41422, the
participant site
~o name 41423 and status lights 41418-41420. The status of the two calls and
the join are
monitored and displayed with the site name in the Conference window 41203. The
status
squares 41418-41420 are colored boxes, with different colors representing
different call
statuses (e.g., no call, call in progress, active call, or active call that
has been disconnected).
The Conference Window 41203 provides buttons to click 41417 that define the
sequence in
which a participant site gets connected to an MCU Port site, routed through
the video
operator. Other features available from this part of the window are watching
the video input
from a call, recording video input from either call, and making a normal video
call to the
participant site or to the MCU.
The color of the arrows 41424 represents the status of each call. The color of
the arrows is
also duplicated in the status lights 41418-41420 in the list of connections.
If there is a Playback Connection 41425 associated with the Conference, only
one Call is
necessary to an MCU Port site. The normal Participant Site call setup
interface will be
inaccessible, and the Join control 41405 will become the Start and Stop switch
for playback.
Free MCU ports can be reached only when an MCU Port call for a defined
Connection is
inactive (or disconnected). This allows the operator to join a conference as
if the operator
were a participant. This is done by selecting the Connection with the free MCU
port call.
When connected, the operator can inform the rest of the participants that the
operator is
attempting to contact or restore a connection.
309
CA 02279845 1999-OS-17
WO 98/23080 PCT/ITS97/21174
There are some functional limitations that the Conference Window 41203 will
reflect. The
Conference Window 41203 should not allow access to functions that cannot be
performed,
for example:
~ The video operator can only view one call at a time.
~ The video operator can record any call at any time with software
unidirectional decoder.
~ Playback connection selection changes the call setup buttons appropriately.
~ The video operator can participate in a conference only when a MCU port call
is inactive.
~ The video operator can talk to participant site only when the participant is
disconnected.
To clarify, a simple connection setup using the Conference Window proceeds as
follows. By
pressing the Call button near the participant site box 41402, the operator
calls Adam (or,
alternatively, Adam may call the operator), and then the operator places the
call on Hold
41407. By pressing the Call button near the MCU Port site box 41403, the
operator calls the
t 5 MCU and then places the call on Hold 41408. By pressing the Join button
41405, the two
calls are joined. In another embodiment, this can be an automated rather than
a manual
process. Adam and the MCU are now connected as H.320 video call. All three
arrows 41424
will be green.
20 4. Video Watch Window
Figure 111 shows one embodiment of the Video Watch window 41204, which
displays the
H.320 input from a selected call of a conference connection or a separate
incoming or
outgoing call. The Video Watch window 41204 also has controls for making
normal calls
41512 and media control such as audio control 41509-41510.
The Video Watch window is the display for the unidirectional H.320 decode of
the video
output of a selected call. By default, the MCU call of the first active site
will be displayed.
To watch any other call, the appropriate View button must be pressed in the
Conference
Windows. The video and audio controls for this window such as volume control
41509-
41510, picture size 41511, etc., are managed from the Video Control Panel.
310
CA 02279845 1999-OS-17
PCT/US97/21174
When the operator chooses to make a normal H.320 video call (point to point),
to a site or an
available slot in an active conference, the Video Watch window 41204 is used
for viewing
the video. A small self view video window should appear nearby when the
operator selects
the Self View button 41506.
5. Console Output Window
Figure 112 shows one embodiment of the Console Output window 41205
which displays all error messages and alerts 41601 " The window is scrollable
so that the
video operator can see all errors that have occurred in the current session.
These messages
to are also logged to a text file for future reference.
6. Properties Dialog Box
Figure 113 shows a Properties dialog box 41701. Dialog boxes are windows that
are
transitional and only displayed temporarily. They are usually used for
entering data or
1 s displaying information that requires immediate attention. This will be a
modeless dialog box
displaying the properties of a particular conference or site. There will be
only one such
window open at any time. If the user focuses on another Conference Window or
Connection
Window, the same dialog box is updated with the appropriate properties. Figure
113 pictures
the properties associated with a particular site, including the site
coordinator 41702, the site
- 2o phone number 41703, the time 41704, connection type 41705 and terminal
type 41706. A
Close button 41707 closes the Properties dialog box 41701.
XVII. WORLD WIDE WEB (WWW) BROWSER CAPABILITIES
A. User Interface
25 The graphical user interface is designed such that only a single IP
connection from the
workstation to the server is required. This single IP connection supports both
the Internet
connection between the W W W Browser and the W W W Site, and the messaging
connection
between the PC Client and the universal inbox (i.e., Message Center). The PC
Client interface
is integrated with the W W W Browser interface such that both components can
exist on the
3o same workstation and share a single IP connection without causing conflicts
between the two
applications.
311
CA 02279845 1999-OS-17
WO 98/23080 ' PCTIUS97/21174
WWW Browser access is supported from any of the commercially available WWW
Browser
interfaces:
~ Microsoft Internet Explorer;
~ Netscape Navigator (1.2, 2.X); or
~ Spyglass Mosaic.
In addition, the WWW Browser interface is optimized to support Windows 95;
however,
Windows 3.1 and Windows 3.11 are supported as well.
to The WWW Browser interface detects the display characteristics of the user's
workstation (or
terminal) and adapts the presentation to support the display settings of the
workstation. The
presentation optimized around a 640x480 pixel display but is also capable of
taking
advantage of enhanced resolution and display qualities of 800x600 (and
greater) monitors.
To improve performance, the user is able to select between 'minimal graphics'
or 'full
graphics' presentation. The WWW browser will detect whether a user has
selected 'minimal
graphics' or 'full graphics' and send only the appropriate graphics files.
B. Performance
2o Response time for downloading of information from the W W W Site or the
Personal Home
Page to the user's workstation or terminal meets the following benchmarks.
Workstation Configuration:
~ Processor: 486DX - 33 MHz;
~ Memory: 12 MB;
~ Monitor: VGA, Super VGA, or XGA;
~ Access: Dialup; _
~ Windows 95;
~ Presentation Option: Full Graphics; and
~ Peripherals: Audio Card, Audio Player Software, 14.4 Kbps Modem.
312
CA 02279845 1999-OS-17
WO 98/23080 PGT/US97IZ1174
ALUE
etrieve and Personal Home0 sec 0 sec
Pages.
ime is measured from when
the
. - ser selects the Bookmark
until the
Status Bar reads, "Document:
Done".
etrieve W W W screens 5 sec (text 15 sec (text
other than only) only)
ome Pages. Time is measured
from
r r
hen the user selects the
hypertext
15 sec (scheduling30 sec (scheduling
ink or tab until the Status
Bar reads,
Green) screen)
'Document: Done".
hart playing a voicemail message.. Time 10 sec 15 sec
s measured from when the users selects
he voicemail message in the Message
enter until the streaming audio file
>tarts playing on the user's workstation.
After a screen or page has been downloaded from the W W W Site to the
workstation, the
cursor is pre-positioned onto the first required field or field that can be
updated.
C. Personal Home Page
The system provides subscribers the ability to establish a Personal Home Page
which
provides a vehicle for people to communicate with or schedule meetings with
the subscriber.
A person accessing a subscriber's Personal Home Page is referred to as the
guest and the user
~o that 'owns' the Personal Home Page is referred to as the subscriber.
' Guest-access to Personal Home Pages will support the following features:
' ~ Create and send a text-based pager message through networkMCI Paging;
~ Create and send an email message to the email (MCI Mail or internetMCI)
account; and
313
CA 02279845 1999-OS-17
PCT/I1S97/21174
~ Access the subscriber's calendar to schedule a meeting.
Messages generated through the subscriber's Personal Home Page are directed to
the
subscriber's networkMCI or SkyTel Pager, or MCI email account.
Email messages composed by guests will:
~ Present the subscriber's name, not the subscriber's email address, in the
email header;
~ Provide a field in the email header for the:
-Sender's name (required field),
-Sender's email address (optional field), and
to -Subject (optional field).
Guests 'request' appointments on a subscriber's Personal Home Page.
~ Requested appointments on a subscriber's Personal Home Page will be prefaced
with "(R)".
~ Approved appointments will be prefaced with "(A)".
Subscribers are responsible for routinely checking their calendars and
approving "(A)" or
deleting requested appointments, and initiating the necessary follow-up
communications to
the requesting party. Approved appointments will be prefaced by "(A)".
Security Requirements
Calendar access from the Personal Home Page is designed to support two-levels
of security:
~ No PIN Access:
-Times Only, or
-Times & Events;
~ PIN Access:
-Times Only; or
-Times & Events.
314
CA 02279845 1999-OS-17
wo rc~rrtrs9~nm4
1. Storage Requirements
The system stores and maintains past and future appointments in the following
manner:
~ Current month plus past six months of historical calendar appointments
~ Current month plus next twelve months of future calendar appointments.
A subscriber is provided the option to download the contents of the months
appointments that
are scheduled to be overwritten in the database. The calendar information that
will be
' downloaded to the subscriber is in a comma delimited or DBF format and
capable of being
imported into Microsoft Schedule+, ACT or Ascend.
l0 2. On Screen Help Text
On screen help text provides guest and subscriber icon access to field
specific "Help"
instructions to operate within the Personal Home Page. The Help Text must
provide
information describing:
~ How to Send the subscriber a text-based pager message from the Personal Home
Page
~ 5 through networkMCI Paging;
~ How to Send the subscriber an email message from the Personal Home Page to
an MCI
email account;
~ How to Access and update a subscriber's Calendar;
~ How to Locate a user's Personal Home Page; and
20 ~ How to Order your own Personal Home Page through MCI.
3. Personal Home Page Directary
The provides the guest the ability to access to a Personal Home Page directory
through the
existing MCI Home Page. This directory allows the guest to search all
established Personal
25 Home Page accounts for a specific Personal Home Page address, by specifying
Last Name
(required); First Name (optional), Organization (optional), State (optional)
and/or Zip Code
' (optional). Results from the Personal Home Page directory search return the
following
315
CA 02279845 1999-OS-17
PCT/ITS97/21174
information: Last Name, First Name, Middle Initial, Organization, City, State
and Zip Code.
Although City is not requested in search criteria it is provided in search
results.
Another means for a guest to locate a Personal Home Page is through the W W W
Browser.
Many WWW Browsers have built in search capabilities for 'Net Directory.'
Users' Personal
Home Pages are listed within the directories of Internet addresses presented
by the WWW
Browser. The benefit to conducting your search from the MCI Home Page is that
only
Personal Home Pages are indexed (and searched). Conducting the search through
the W W W
Browser menu option will not limit the search to Personal Home Pages and
therefore will
conduct a search through a larger list of URLs. In addition, guests have the
capability to enter
the specific URL (i.e., Open Location) for the Personal Home Page rather than
performing a
search. This is especially important for those subscribers that have their
Personal Home Page
"unlisted" in the directory.
4. Control Bar
A Control Bar is presented at the bottom of the Personal Home Page. The
Control Bar is
presented after the guest has selected Personal Home Pages from the MCI Home
Page. The
Control Bar provides the guest access to the following features:
~ Help Text
~ MCI Home Page
~ Personal Home Page Directory
~ Feedback.
5. Home Page
The Home Page is the point of entry for the subscriber to perform message
retrieval and
exercise profile management from a WWW Browser. The Home Page is designed to
provide
the user easy access to the Message Center or Profile Management.
316
CA 02279845 1999-OS-17
_ W~ PCT/I1S97/Z1174 -
6. Security Requirements
Access to the Message Center or Profile Management is limited to authorized
users. Users
are prompted to enter their User ID and Password t>efore accessing the Message
Center or
Profile Management. After three unsuccessful attempts, the user is blocked
from accessing
the Message Center or Profile Management and a WARNING message advises the
subscriber
to contact the MCI Customer Support Group. The account is deactivated until an
MCI
Customer Support representative restores the account. After the account is
restored, the
subscriber is required to update his or her Password.
1 o A successful logon to the Message Center enables the user to access
Profile Management
without being challenged for another (i.e., the same) User ID and Password.
The same is also
true for users that successfully access Profile Management - they are allowed
to access the
Message Center without being challenged for another (i.e., the same) User ID
and Password.
Passwords are valid for one month. Users are prompted to update their password
if it has
expired. Updates to passwords require the user to enter the expired password,
and the new
password twice.
7. On Screen Help Text
Provide the subscriber icon access to field specific "Help" instructions to
operate within the
2o Home Page. The Heip Text provides information describing:
~ How to Access Message Center;
~ How to Access Profile Management;
~ How to Access the MCI Home Page;
~ How to Access Personal Home Pages; -
~ How to Send (i.e. Create or Forward) Messages through Message Center;
~ How to File Messages through Message Center;
~ How to Update the directlineMCI Profile;
~ How to Update the Information Services Profile;
317
CA 02279845 1999-OS-17
WO 98/23080 - PCT/US97/21174
~ How to Update their Personal Home Page;
~ How to Provide Feedback on the Home Page; and
~ How to Order the User's Guide.
Control Bar
A Control Bar is presented at the bottom of the Home Page. The Control Bar
provides the
guest access to the following features:
~ Help Text;
~ MCI Home Page;
~ Personal Home Page Directory; and
t o ~ Feedback.
8. Prof le Management
In addition to the On-Screen Help Text and Control Bar discussed above, the
Profile
Management screen presents a Title Bar. The Title Bar provides the subscriber
easy access to
the Profile Management components and quick access to the Message Center.
Access to the
~ 5 Profile Management components is provided through the use of tabs which
will include:
~ directlineMCI;
~ Information Services;
~ Personal Home Page;
~ List Management; and
20 ~ Message Handling.
The directlineMCI tab includes additional tabs for the underlying components
of
directlineMCI which are:
~ Voicemail;
~ FAXmail;
25 ~ Paging.
The directlineMCI Profile Management system provides subscribers a Profile
Management
page from which account profile information can be manipulated to:
318
CA 02279845 1999-OS-17
PCT1U$97/21174
~ Create new directlineMCI profiles and assign names to the profile;
~ Update existing directlineMCI profiles;
~ Support the rules-based logic of creating and updating directlineMCI
profiles (e.g., selection
' of only one call routing option, like voicemail, invokes override routing to
voicemail; and
updates made in one screen ripple through all affected screens, like paging
notification);
~ Enable a directlineMCI number;
~ Enable and define override routing number;
~ Enable and define FollowMe routing; and
~ Define RNA parameters for each number in the directlineMCI FollowMe routing
sequence
~ o ~Enable and define final routing (formerly called alternate routing) to:
-Voicemail and pager,
-Voicemail only,
-Pager only, and
-Final message;
t 5 ~ Invoke menu routing if two or more of the call routing options
(FollowMe, voicemail,
faxmail or pager) are enabled;
~ Enable voicemail;
~ Enable faxmail;
~ Enable paging;
20 ~ Define the default number for faxmail delivery;
~ Activate paging notification for voicemail;
~ Activate paging notification for faxmail;
~ Define schedules to activate/deactivate different directlineMCI profiles;
~ Provide guest option to classify voicemails for urgent delivery;
25 ~ Configure the time zone for all message types that will be used to
identify the time a
message is received;
- ~ Define call screening parameters for:
319
CA 02279845 1999-OS-17
PCT/US97/Z1174
-Name and ANI,
-ANI only, and
-Name only; and
~ Enable or disabling park and page.
s
9. Information Services Profile Management
Information Services Profile Management provides subscribers the ability to
select the
information source, delivery mechanism (voicemail, pager, email) and the
delivery frequency
depending upon the information source and content. Specifically, the
subscriber has the
to ability configure any of the following information sources:
~ Stock Quotes and Financial News; and
~ Headline News.
Stock Quotes and Financial News provides the subscriber the following:
~ Business News Headlines;
15 ~ Stock Quotes (delay less than or equal to 10 minutes);
~ Stock Market Reports (hourly, AM/PM or CQB);
~ Currency and Bond Reports (hourly, AM/PM or COB);
~ Precious Metal Reports (hourly, AM/PM or COB); and
~ Commodities Reports (hourly, AM/PM or COB).
Business News Headlines are delivered via email once per day. Reports (Stock
Market,
Currency and Bond, Precious Metal and Commodities) are delivered at the
interval specified
by the subscriber. Hourly reports require that email message is time stamped
at 10 minutes
after the hour. AM/PM reports require that one email message is transmitted in
the morning
(11:10 am ET) and one email message is transmitted in the evening (5:10 PM
ET), with COB
reports transmitted at 5:10 PM ET.
320
CA 02279845 1999-OS-17
WO Pt'j'T/US97/21174
The content of the Stock Market Report contains:
~ Stock or mutual fund ticker symbol;
~ Stock or mutual fund opening price;
~ Stock or mutual fund closing price;
~ Last recorded bid price for the stock or mutual fund;
~ Last recorded ask price for the stock or mutual fund;
~ Stock or mutual fund's 52-week high; and
~ Stock or mutual fund 52-week low.
to Stock Quotes and Financial News also provide the subscriber the ability to
select from a list
of available stocks and.mutual funds and define criteria whereby a voicemail
or text-based
page is provided. The definable criteria are referred to as 'trigger points'
and can be any or all
of the following conditions:
~ Stock or mutual fund reaches a 52-week high value;
t s ~ Stock or mutual fund reaches a 52-week low value;
~ Stock or mutual fund reaches a user-defined high point; and
~ Stock or mutual fund reaches a user-defined low-point.
After a 'trigger point' condition has been satisfied, a message (voicemail or
text-based pager)
2o is transmitted within 1 minute to the subscriber. Voicemail messages are
directed to the
subscriber's mailbox defined in the user's directlineMCI account. The
information content
for Stock Quotes and Financial News is no older-than 10-minutes old.
10. Personal Home Page Profile Management
' 25 Personal Home Page Profile Management provides subscribers the ability to
customize their
. Personal Home Page and define how guests can communicate with them (email or
text-based
321
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/Z1174
pager). In addition, Profile Management also enables subscribers to control
guest access to
their calendar. Specifically, the subscriber is able to:
~ Establish and maintain a greeting message;
~ Establish and maintain a contact information (i.e., address information};
~ Establish and maintain a personal calendar;
~ Enable or disable guest access to paging, email or calendar;
~ Control guest access to calendar by defining PINs for standard or privileged
access; and
~ Incorporate an approved subscriber submitted graphic, such as a personal
photo or corporate
logo, on a predefined location on the Personal Home Page.
Upon creation of the Personal Home Page, the contact information is populated
with the
subscriber's delivery address information. The subscriber has the capability
to update that
address information contained within the contact information.
1 I . List Management
15 List Management provides the subscriber the ability to create and update
lists. Profile
Management provides subscribers the ability to define lists accessible through
the Message
Center for message distribution. In one embodiment, list management is
centralized such that
Fax Broadcast list management capabilities are integrated with directlineMCI
list
management capabilities to provide a single database of lists. In an alternate
embodiment,
2o the two list management systems are separate, so the user may access either
database for lists.
Lists are maintained through an interface similar to an address book on the PC
Client
whereby subscriber are able to add or remove names to lists. Associated with
each person's
name are the email address, faxmail address (i.e., ANI), voicemail address
(i.e., ANI}, and
25 pager number. As messages populate the Message Center inbox (i.e.,
universal inbox), the
address book is updated with the source address of the associated message
type.
322
CA 02279845 1999-OS-17
wo 9sr~so rcr~rs9~nma
When a subscriber chooses to create a distribution list, she is prompted to
select a name, type
and identifier name for the list. All created lists are available in
alphabetical order by name.
The type of the list (voice, fax, email, page) accompanies the list name. In
addition, list
identif ers may consist of alphabetic characters.
~ 5
The subscriber is then prompted for recipient names and addresses to create a
distribution list.
The subscriber is able to access his address book for recipient information.
The subscriber is
not be restricted to record the same address types in his list; if a list is
created with a fax type,
the subscriber is able to include ANI, email and paging addresses in the list.
The subscriber is
able to manage his distribution lists with create, review, delete, edit (add
and delete
recipients) and rename capabilities.
When the user chooses to modify a list through the WWW Browser interface, she
is
prompted to select the address type (voice, fax, fax, paging, email) and a
list of the user's
15 distribution lists should be provided for that address type. The user is
also able to enter the
List Name to locate it. Users are able to modify lists through create, review,
edit (add and
remove recipients), delete and rename commands.
Whenever a subscriber modifies a list with a recipient addition, removal or
address change,
2o she is able to make the modification a global change. For example, a user
changes the voice
mailbox address for Mr. Brown in one list. she is able to make this a global
change, changing
that address for Mr. Brown in all of his distribution lists. While the
subscriber is able to
create and modify distribution lists through the ARL1 and VRU in addition to
the PC,
enhanced list maintenance capabilities are supported through the WWW Browser
interface.
' The subscriber is able to search and sort lists by name or by the different
address fields. For
example, a user is able to search for all lists containing 'DOLE' by using the
*DOLE*
command within the search function. In addition, users are able to search
lists using any of
the address fields. For example, a user could search based on a recipient
number, 'to' name or
zip code. A user is able to sort lists by list names, identifiers and types or
by any address
field.
323
CA 02279845 1999-OS-17
WO 98/23080 PCTlUS97/21174
In addition to search capabilities, the distribution list software enables the
user to copy and
create sub-lists from existing distribution list records. The user is able to
import and export
recipient data from external database structures.
The capability to share lists among users and upload lists to a host also
exists.
12. Global Message Handling
Global Message Handling provides subscribers the ability to define the message
types that
1 o will appear in the "universal inbox" or accessed through the Message
Center. The following
message types are selectable:
~ directlineMCI voicemail;
~ directlineMCI faxmail;
~ networkMCI and SkyTel Paging; and
IS ~ Email from an MCI email account (i.e., MCI Mail or internetMCI).
If a subscriber is not enrolled in a specific service then that option will be
grayed-out and
therefore not selectable within Global Message Handling. Any updates to Global
Message
Handling result in a real-time update to the Message Center. An example is
that a subscriber
2o may choose to allow voicemail messages to appear in the Message Center. The
Message
Center automatically retrieves all voicemail message objects that exist within
the voicemail
database.
D. Message Center
The Message Center functions as the "universal inbox" for retrieving and
manipulating
25 message objects. The "universal inbox" consists of folders containing
messages addressed to
the user. Access to the Message Center is supported from all W W W Browsers,
but content
contained in the "universal inbox" only presents the following message types:
~ Voicemail: addressed to user's directlineMCI account;
324
CA 02279845 1999-OS-17
PCT/US97/21174
~ EmaiI: addressed to the user's MCI email (i.e., MCI Mail or internetMCI)
account;
~ FAXmail: addressed to the user's directlineMCI account; and
~ Paging: addressed to the user's networkMCI Paging account (or SkyTel Paging
account).
s In addition to the On-Screen Help Text and Control :Bar discussed in the
previous sections,
the Message Center screen presents a Title Bar. The Title Bar provides the
subscriber easy
access to the Message Center functions and quick access to Profile Management.
The
Message Center functions that are supported through. the Title Bar are:
~ File: lists user's defined folders and allows user to select folder;
to ~ Create: compose a new email message;
~ Forward: voicemails will be forwarded as email attachments;
~ Search: provide ability to search based on message type, sender's name or
address, subject
or date/time; and
~ Save: allows users to save messages to a folder on the universal inbox, to a
file on the
~ 5 workstation or to a diskette.
When composing or forwarding messages through the Message Center, the user has
the
ability to send a message as either an email or a faxrr~ail. The only
limitation is that
voicemails may only be forwarded as voicemails or as email attachments. All
other message
2o types may be interchanged such that emails may be forwarded to a fax
machine, or pager
messages may be forwarded as an email text message. Messages that are sent out
as faxmail
messages are generated in a G3 format, and support distribution to Fax
Broadcast lists.
The presentation layout of the Message Center is consistent with the
presentation layout of
25 the PC Client such that they have the same look and feel. The Message
Center is designed to
present a Message Header Frame and a Message Preview Frame, similar to the
presentation
that is supported by nMB v3.x. The user will have the ability to dynamically
re-size the
height of the Message Header Frame- and the Message Preview Frame. The Message
Header
Frame will display the following envelope information:
325
CA 02279845 1999-OS-17
wo 9sn~oso rc~r~rs9~nma
~ Message type (email, voice, fax, page);
~ Sender's name, ANI or email address; -
~ Subject;
~ Date/time; and
~ Message size.
The Message Preview Frame displays the initial lines of the body of the email
message, the
initial lines of the first page of the faxmail message, the pager message, or
instructions on
how to play the voicemail message. Playing of voicemail messages through an
WWW
1 o Browser is supported as a streaming audio capability such that the
subscriber is not required
to download the audio file to their workstation before playing it. The
streaming audio is
initiated after the user has selected (single ieft-mouse click) on the
voicemail header in the
Message Header Frame. Displaying of faxmail messages is initiated immediately
after the
user has selected (single left-mouse click) on the faxmail header in the
Message Header
Frame.
The Message Center also allows the subscriber to use distribution lists that
have been created
in Profile Management. The distribution lists support sending messages across
different
message types.
2o In addition to the basic message retrieval and message distribution, the
Message Center
supports the creation and maintenance of message folders (or directories)
within the universal
inbox. Initially users are limited to the following folders:
~ Draft: retains all saved messages that have NOT been sent;
~ Inbox: retains all messages received by the "universal inbox" and it will be
the default
folder presented when the user accesses Message Center;
~ Sent: retains all messages that have been sent; and
~ Trash: retains for 7 days all messages marked for delete. Subscribers will
eventually be
able to create (and rename) folders (and folders within folders).
326
CA 02279845 1999-OS-17
WO 98/Z30>30 PCT/US97/Z1174
1. Storage Requirements
Initially, users are allotted a limited amount of storage space for
directlineMCI voicemail and
directlineMCI faxmail. Pager recall messages and email messages are not
limited based upon
_ amount of storage space consumed, but rather the date/time stamp of the
message received.
Ultimately, storage requirements will be enforced based upon a common
measurement unit,
like days. This will provide users an easier approach to knowing when messages
will be
deleted from the database, and when guests will be prevented from depositing a
message
(voicemail, faxmail) to their "universal inbox". To support this, the
following are storage
requirements for messages retained in the inbox:
i o ~ directlineMCI voicemail: 60 minutes;
~ directlirieMCI faxmail: 50 pages;
~ networkMCI pages: 99 hours; and
~ Email: 6 months.
The subscriber is provided the option to download the messages that are
scheduled to be
overwritten in the database except for messages that: are retained in the
trash folder.
E. PC Client Capabilities
1. User Interface
The PC Client interface supports subscribers that want to operate in a store &
forward
environment. These users want to download messages to either manipulate or
store locally.
The PC Client is not designed to support Profile Management and the PC Client
interface
.. only presents messages (voicemail, faxmail, email, text-page). Access to
Profile Management
capabilities only is available through the ARU interface or the WWW Browser
interface. The
PC Client interface is integrated with the WWW Browser interface such that
both
components can exist on the same workstation and share a single IP connection.
327
CA 02279845 1999-OS-17
WO 98/Z3080 PCT/US97/21174
The PC Client interface is optimized to support Windows 95; however, Windows
3.1 is
supported as well.
The graphical user interface is designed to present a Message Header Window
and a Message
Preview Window, similar to the presentation that is supported by nMB v3.x and
is supported
by the WWW Browser. The user has the ability to dynamically re-size the height
of the
Message Header Window and the Message Preview Window. The Message Header
Window
displays the following envelope information:
~ Message type (email, voice, fax, page);
~ Sender's name, ANI or email address;
~ Subject;
~ Date/time; and
~ Message size.
The Message Preview Window displays the initial lines of the body of email
messages or
pager messages, or instructions on how to display the faxmail message or play
the voicemail
message. Playing of voicemail messages from the PC Client requires an audio
card be present
on the PC. Displaying of faxmail messages invokes the faxmail reader within
the PC Client.
The Message Center also allows the user to use distribution lists that have
been created in
2o Profile Management. The distribution lists support sending messages across
different
message types.
2. Security
User authentication between the PC Client and the server is negotiated during
the dial-up
logon session. Security is supported such that the User ID and Password
information is
imbedded in the information that is passed between the PC Client and server
when
establishing the interface. Subscribers are not required to manually enter
their User ID and
Password. In addition, updates made to the password are communicated to the PC
Client.
328
CA 02279845 1999-OS-17
WO 98/23080 PCT1U897/211'74 -
3. Message Retrieval
Message Retrieval provides subscribers the ability to selectively retrieve
voicemail, faxmail,
pages and email messages that reside in the "universal inbox". Message types
that are
displayed or played from the PC Client include:
~ directlineMCI voicemail;
~ directlineMCI faxmail;
~ networkMCI paging; and
~ Email from an MCI email account;
~ o The PC Client initiates a single communication session to retrieve all
message types from the
"universal inbox". This single communication session is able to access the
upstream
databases containing voicemails, faxmails, emails and pages.
The PC Client also is able to perform selective message retrieval such that
the user may is
able to:
~ Retrieve all messages;
~ Retrieve full text (or body) for selected message header(s);
~ Retrieve messages based upon editable search criteria:
-priority messages;
-email messages;
-pager messages;
-faxmail messages (complete or header only);
' -voicemail messages (complete or header only);
-sender name, address or ANI;
-date/time stamp on message; and
-message size.
329
CA 02279845 1999-OS-17
wo 9sr~3oso - rc~rrtrs9~nma
Header-only faxmail messages retrieved from the "universal inbox" are retained
in the
"universal inbox" until the message body is retrieved. Voicemail messages are
retained in the
"universal inbox" until the subscriber accesses the "universal inbox" via the
WWW Browser
(i.e., Message Center) or ARU and deletes the message. Messages retrieved from
the
"universal inbox" are moved to the desktop folder.
In addition, the PC Client is able to support background and scheduled polling
such that users
are able to perform message manipulation (create, edit, delete, forward, save,
etc.) while the
to PC Client is retrieving messages.
4. Message, Manipulation
Message Manipulation provides subscribers the ability to perform many standard
messaging
client actions, like:
~ Compose (or create) email, faxmail or pager messages;
~ Forward all message types;
~ Save;
~ Edit;
~ Delete;
~ Distribute;
~ Attach;
~ Search; and
~ Display or play messages.
F. Order Entry Requirements
directlineMCI or networkMCI Business customers are provided additional
interface options
to perform profile management and message management functions. Both
directlineMCI and
networkMCI Business customers are automatically provided accounts to access
the features
330
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21I74 -
and functions available through the different interface types. The ability to
provide accounts
to networkMCI Business customers is also supported; however not all networkMCI
Business
customers are provided accounts. Order entry is flexible enough to generate
accounts for
networkMCI Business customers, as needed.
Order entry is designed such that directlineMCI customers or networkMCI
Business
customers are automatically provided access to the additional interface types
and services
provided in the system. For example, a customer that orders directlineMCI (or
networkMCI
Business) is provided an account to access the Home Page for Profile
Management or
yo Message Center. Checks are in place to prevent a customer from being
configured with two
accounts - one from directlineMCI and one from networkMCI Business. In order
to
accomplish this, integration between the two order entry procedures is
established.
An integrated approach to order entry requires a single interface. The
interface integrates
order entry capabilities such that the order entry appears to be housed in one
order entry
system and does not require the order entry administrator to establish
independent logon
sessions to multiple order entry systems. This integrated order entry
interface supports a
consistent order entry methodology for all of the services and is capable of
pulling --
information from the necessary order entry systems. In addition, the interface
supports the
2o capability to see the services associated with the user's existing
application.
The specific requirements of the integrated order interface system are:
~ Automated feeds to define an MCI email (MCI Mail or internetMCI) account;
~ Automated feeds to define a networkMCI paging account(or SkyTel Paging)
account;
~ Automated feeds to define a directlineMCraccount;
~ Automated feeds to enable Fax Broadcast capabilities;
. ~ Ability to manually enter MCI email account, networkMCI paging account or
directlineMCI account information;
~ Ability to enable or disable access to inbound information services; and
331
CA 02279845 1999-OS-17
WU 98/23080 - PCT/US97/2l174
~ Ability to enable or disable access to outbound information services.
These abilities give order entry administrators the flexibility to add a user
based upon
preexisting MCI service (email, paging) directlineMCI) account information.
Alternatively,
the order administrator may add a user while specifying the underlying
services.
The order entry systems provide the necessary customer account and service
information to
the downstream billing systems. They also track the initial customer order and
all subsequent
updates so that MCI can avoid sending duplicate platform software (i.e., PC
Client) and
t0 documentation (i.e., User Guide). In addition, order entry processes enable
an administrator
to obtain the following information:
~ Record customer delivery and name:
-support USA and Canadian addresses, and
-provide ability to prevent delivery to P.O. boxes;
~ Record customer's billing address, phone number and contact name;
~ Record the order date and all subsequent updates;
~ Record the name, phone number and division of the Account Representative
that submitted
the order;
~ Record or obtain the user's directlineMCI number;
~ Record or obtain the user's networkMCI paging PIN;
~ Record or obtain the user's MCI email account ID;
~ Generate a daily Fulfillment Report that is electronically sent to
fulfillment house; and
~ Generate a daily Report that tracks:
-number of orders received;
-number of orders to create networkMCI Paging (or SkyTel Paging) account;
-number of orders to create MCI email account, and
-number of orders to create a directlineMCI account.
332
CA 02279845 1999-OS-17
PCT/US97/21174
Personal home pages can be ordered for a customer. The customer delivery
information
recorded during order entry is the default address information that is
presented from the
user's Personal Home Page. In addition, the order entry processes support the
installation of
and charging for special graphics.
' The capability to turn existing feature/functionality 'on' and 'off for a
specific service exists.
Features that can be managed by the user are identified within the order entry
systems. These
features are then activated for management within the user's directory
account.
There are real-time access capabilities between order entry systems and the
user's directory
account. This account houses all of the user's services, product
feature/functionality, and
account information, whether user-managed or not. Those items that are not
identified as
user-managed are not accessible through the user's interface.
1. Provisioning and Fulfillment
Access requirements have been defined in terms of inbound access to the system
and
outbound access from the system. Inbound access includes the methods through
which a user
or a caller may access the system. Outbound access includes the methods
through which
2o users are handled by the system in accordance with a preferred embodiment.
Internet support
exists for both inbound and outbound processing.
The following components may provide inbound access:
~ directlineMCI: 800/BXX;
~ MCIMaiI: 800/BXX, email addresses;
~ networkMCI ~agmg: 800/8XX; and
~ internetMCI mail: 800/8XX, POP3 email address.
' The following components have been identified for outbound access:
~ directlineMCI:Diall;
~ Fax Broadcast: 800/8XX, local;
333
CA 02279845 1999-OS-17
WO 98/223080 PCT/US97/21174
~ MCI Mail: 800/BXX, email address; and
~ internetMCI mail: 800/BXX, POP3 email address.
G. Traffic Systems
Traffic is supported according to current MCI procedures.
H. Pricing
Initially, the features are priced according to the existing pricing structure
defined for the
underlying components. In addition, taxing and discounting capabilities are
supported for the
to underlying components as they are currently being supported. Discounting is
also supported
for customers that subscribe to multiple services.
I. Billing
The billing system:
~ Supports charges for directlineMCI enhanced services (voicemail, faxmail,
both);
~ Supports charges for peak and off peak rates;
~ Supports discounts for multiple services (directlineMCI, networkMCI
Business,
networkMCI Paging, networkMCI Cellular) which will vary based upon number of
services;
~ Supports ability to suppress networkMCI Cellular charges for directlineMCI
calls
(originating and terminating);
~ Supports charges for monthly fees sensitive to directlineMCI usage;
~ Supports promotions in the form of free minutes based on directlineMCI
usage;
~ Supports charges for Personal Home Pages;
~ Supports ability to suppress charges for Personal Home Pages; and
~ . Supports SCA Pricing.
In one embodiment, the billing system supports the current invoicing
procedures that exist for _
each of the underlying components. In an alternative embodiment, the billing
provides a
3o consolidated invoice that includes all of the underlying components. In
addition to invoicing,
334
_ CA 02279845 1999-OS-17
_ WO ~PGT/US97/Z1174
directed billing is supported for all of the underlying components that are
currently
supporting directed billing.
XVIII. DIRECTLINE MCI
The following is a description of the architecture of the directline MCI
system, as modified
for use with the system. This document covers the general data and call flows
in the
directlineMCI platform, and documents the network and hardware architecture
necessary to
support those flows. Billing flows in the downstream systems are covered at a
very high
level. Order Entry (OE) flows in the upstream systems are covered at a very
high Level.
Certain portions of the directlineMCI architecture reuse existing components
(e.g. the Audio
Response Unit (ARU)). Those portions of the directlineMCI architecture which
are new are
covered in more detail.
A. Overview
In addition to billing, order entry, and alarming, the directlineMCI system is
made up of
three major components, as shown in Figure 43:
~ ARU (Audio Response Unit) 502
~ VFP (Voice Fax Platform) 504
~ DDS (Data Distribution Service) 506
2o The subsections below describe each of the major components at a high
level.
Figure 43 shows the high-level relationships between the major system
components.
1. The ARU (Audio Response Unit) 502
The ARU 502 handles all initial inbound calls for directlineMCI. Some features
(such as find
me/foliow me) are implemented entirely on the ARU. Inbound faxes are tone-
detected by the
ARU and extended to the VFP 504. Menuing provided by the ARU can be used to
request
access to the voicemail/faxmail features, in which case the call is also
extended to the VFP.
2. The VFP (Voice Fax Platform] 504
The VFP provides the menuing for the voicemail/faxmail features as well as
outbound fax
and voice forwarding and pager notifications. The VFP is also the central data
store for the
customized subscriber prompts which are played and recorded by the ARU 502.
335
CA 02279845 1999-OS-17
PCT/US97/211?4
3. The DDS (Data Distribution Service) 506
The DDS is a central data repository for OE profiles and Billing Details
Records (BDRs). ,
OE profiles are deposited with DDS, which is responsible for distributing the
profiles to all of
the appropriate systems. DDS 506 collects BDRs and ships them to the
downstream billing
systems.
B. Rationale
The requirement for the directlineMCI service is to integrate a variety of
service components
into a single service accessed by a single 800 number. A number of these
service
to components had been previously developed on the ISN ARU platform. The
services not
present in the ARU were mailbox services and fax services. The ARU 502 of the
system 500
incorporates a voicemail/faxmail platform purchased from Texas Instruments
(TI). Portions
of that software are ported to run on DEC Alpha machines for performance,
reliability, and
scalability. Another requirement for the directlineMCI implementation is
integration with the
t 5 mainstream (existing MCI) billing and order entry systems. The DDS
provides the inbound
and outbound interfaces between directlineMCI and the mainstream order entry
systems.
C. Detail
Figure 43 shows the relationships between the major system components. The OE
system
20 508 generates subscriber profiles which are downloaded via DDS 506 to the
ARU 502 and
the Voice Fax Platform (VFP) 504. BDRs generated by the ARU 502 and VFP 504
are fed to
the billing systems 510 via DDS 506. The ARU 502 handles all inbound calls. If
faxtone is
detected, or if a voicemail/faxmail feature is requested, the call is extended
from the ARU
502 to the VFP 504. For mailbox status (e.g. " You have three messages"), the
ARU 502
25 queries the VFP 504 for status and plays the prompt.
Subscribers' customized prompts are stored on the VFP 504. When the ARU plays
the
customized prompt, or records a new prompt, the prompt is accessed on the VFP
504.
Alarms from the ARU 502 and VFP 504 are sent to the Local Support Element
(LSE).
336
CA 02279845 1999-OS-17
wo 9sn~so rc~rrtrs9~nma
1. Call Flow Architecture 520
The call flow architecture for directlineMCI is shown in Figure 44. The top
part of the figure
shows the network 522 connectivity used to transport the calls. The bottom
part of the figure
( shows the call direction for different call types. The subsections below
provide the text
description to accompany the figure.
~ 2. Network Connectivity
All inbound ISN calls are received at an Automatic Call Distributor (ACD) 524
connected to
the MCI network 522. The Access Control Point (ACP) receives notice of an
inbound call
1o from the Integrated Services Network Application Processor (ISNAP) 526,
which is the
control/data interface to the ACD 524. The Network Audio System (NAS) plays
and records
voice under the control of the ACP via a T1 interface to the ACD. In the
United States, a
digital multiplexing system is employed in which a :first level of multiplexed
transmission,
known as T1, combines 24 digitized voice channels over a four-wire cable (one-
pair of wires
~ 5 for "send" signals and one pair of wires for "receive" signals). The
conventional bit format
on the Tl carrier is known as DS 1 (i.e., first level multiplexed digital
service or digital signal
format), which consists of consecutive frames, each frame having 24 PCM voice
channels (or
DSO channels) of eight bits each. Each frame has an additional framing bit for
control
purposes, for a total of 193 bits per frame. The T1 transmission rate is 8000
frames per
2o second or 1.544 megabits per second (Mbps). The frames are assembled for T1
transmission
using a technique known as time division multiplexing (TDM), in which each DSO
channel is
assigned one of 24 sequential time slots within a frame, each time slot
containing an 8-bit
word.
25 Transmission through the network of local, regional and long distance
service providers
involves sophisticated call processing through various switches and hierarchy
of multiplexed
carriers. At the pinnacle of conventional high-speed transmission is the
synchronous optical
network (SONET), which utilizes fiber-optic media and is capable of
transmission rates in the
gigabit range (in excess of one-billion bits per second). After passing
through the network,
3o the higher level multiplexed carriers are demultiplexed ("demuxed") back
down to individual
DSO lines, decoded and coupled to individual subscriber telephones.
337
CA 02279845 1999-OS-17
WO ~PGT/US97/21174
Typicaily, multiple signals are multipexed over a single line. For example,
DS3 transmission
is typically carried by a coaxial cable and combines twenty-eight DS 1 signals
at 44.736 _
Mbps. An OC3 optical fiber carrier, which is at a low level in the optical
hierarchy,
combines three DS3 signals at 155.52 Mbps, providing a capacity for 2016
individual voice
channels in a single fiber-optic cable. SONET transmissions carried by optical
fiber are
capable of even higher transmission rates.
The NAS/ACP combination is referred to as the ARU 502. If the ARU 502
determines that a
call must be extended to the VFP 504, it dials out to the VFP 504. The VFP
media servers
~ o are connected to the MCI network 522 via T1. Data transfer from the ARU
502 to the VFP
504 is accomplished via is Dual Tone Multi-Frequency (DTMF) on each call. -
3. Call Flow
The call scenarios shown in Figure 44 are detailed below. At the start of any
of the inbound
calls, the ARU 502 has already received the call and performed an application
select to
determine whether the call is a directlineMCI call or not.
a) Inbound FAX:
An inbound FAX call is delivered to the ARU 502. The ARU performs a faxtone
detect and
2o extends the call to the VFP 504. Account number and mode are delivered to
the VFP
utilizing DTMF signaling.
b) Inbound Voice, ARU only:
An inbound voice call is made in either subscriber or guest mode, and only
those features
which use the ARU 502 are accessed. The ARU determines mode (subscriber or
guest). In
subscriber mode, the ARU queries the VFP 504 to determine the number of
messages. No
additional network accesses are made.
338
CA 02279845 1999-OS-17
WO ~ PCT/US97I21174
c) Inbound/Outbound Voice, ARU only:
A call is made to the ARU 502, and either pager notification or find me/follow
me features
are accessed. The ARU 502 dials out via the ACD 524 to the outside number.
d) Inbound Voice, VFP features:
A call is made to the ARU 502, and the call is extended to the VFP 504.
Account number
and mode (subscriber or guest} are sent to the VFP via DTMF. The guest modes
are:
1. Deposit voicemail.
2. Deposit fax mail.
3. Collect fax mail.
The subscriber modes are:
1. Retrieve or send mail.
2. Maintain broadcast lists.
3. Modify mailbox name recording.
The VFP 504 continues prompting the userduring the VFP session.
e) Outbound Fax/Voice/Pager, VFP only:
For FAX ar voice delivery or pager notification, the VFP dials out on the MCI
network 522
directly.
fj Reoriginate/Takeback:
While an inbound subscriber call is connected to the VFP 504, the user may
return to the
top level of the ARU 502 directlineMCI menus by pressing the pound key for two
seconds.
The network 522 takes the call back from the VFP 504 and reorginates the call
to the ARU
' 25 502.
4. Data Flow Architecture
Figure 45 depicts the primary data flows in the directlineMCI architecture
520:
339
CA 02279845 1999-OS-17
WO 98/Z30&1 PCT/US97/21174
OE records (customer profiles) are entered in an upstream system and are
downloaded at 530
to the DDS mainframe 532. The DDS mainframe downloads the OE records to the
Network
Information Distributed Services (KIDS) servers 534 on the ARU/ACP and the
VFP/Executive Server 536. These downloads are done via the ISN token ring
network 538.
On the executive server 536, the OE records are stored in the local Executive
Server database
(not shown).
BDRs are cut by both the Executive Server 536 and the ACP 540. These BDRs are
stored in
an Operator Network Center (ONC) server 542 and are uploaded to the DDS
mainframe 532.
t0 The uploads from the ONC servers 542 to the DDS mainframe are done via the
ISN token
ring network 538.
The ARU 502 prompts subscribers with their number of voicemail/faxmail
messages. The
number of messages a subscriber has is obtained from the VFP 504 by the ACP
540 over the
t5 ISNAP Ethernet 544. Note that the ACPs 540 may be at any of the ISN sites.
The user-recorded ad hoc prompts played by the NAS 546 are stored on the VFP
504 and are
played over the network on demand by the NAS 546. The NFS protocol 548 is used
over the
ISNAP Local Area Network (LAN) 544 and Wide Area network (WAN) 550.
D. Voice Fax Platform (YFP) 504 Detailed Architecture
1. Overview
Figure 46 shows the hardware components of the Voice Fax Portion 504 of the
directlineMCI
system for the first embodiment. The main components in this system are:
The TI MultiServe 4000 media server 560.
The DEC 8200 executive servers 536.
The Cabletron MMAC+ hubs 562.
The AiphaStation 200 console manager and terminal servers 564.
The Bay Networks 5000 hubs 566.
340
CA 02279845 1999-OS-17
WO ~~ w PCT/US97/21174
In another embodiment, the Cabletron hubs will be removed from the
configuration, and the
Bay Networks hubs will then carry all the network traffic.
2. Rationale
The TI MultiServe 4000 560 was selected by MCI for the voicemail/faxmail
portion of the
directlineMCI platform. The MultiServe 4000 is a fairly slow 68040 machine on
a fairly
slow Nubus backplane. The 68040/Nubus machine:c are used by TI as both media
servers (T 1
interface, DSPs for voice and fax) and also for the executive server (database
and object
storage). Although this hardware is adequate for media server use, it was
inadequate as an
o executive server to serve hundreds or even thousands of gigabytes of voice
and fax data and
thousands of media server ports. Additionally, there is no clustering (for
either performance
or redundancy) available for the media server hardware. Thus, the executive
server portion
of the TI implementation was ported by MCI to run on a DEC Alpha 8200 cluster
536,
described below. This clustering provides both failover and loadsharing (thus
scalability).
l5 Likewise, the gigabytes that must be moved from the high speed 8200
platforms must be
moved across a network to the TI media servers. Cabletron Hubs 562 with both
Fiber
Distribution Data Interface (FDDI) and switched IObT connectivity provide the
backbone for
the implementation. Each media server 560 is attached to a redundant pair of
switched
Ethernet ports. Because each port is a switched port, each media server gets a
dedicated
20 l OMb of bandwidth to the hub. The 8200 servers 536 each need a large
network pipe to
serve the many smaller l OMb Ethernet pipes. For the first embodiment, the
FDDI interfaces
568 will be used. However, traffic projections show that the necessary traffic
will exceed
FDDI capacity by several times, so an embodiment in accordance with a
preferred
embodiment will use higher speed networking technology such as ATM. The hub
562
25 configuration is fully redundant.
The AlphaStation 200 workstation 564 is needed for operations support. The
AIphaStation
200 provides console management via DEC's Polycenter Console Manager for each
of the
directlineMCI VFP 504 components. It also runs the DEC Polycenter Performance
Analyzer
3o software. The performance analyzer software collects and analyzes data from
the 8200s for
tuning purposes.
341
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97IZ1174
3. Detail
Figure 47 shows the production installation of the VFP 504 at the production
site.
Notes about Figure 47 and its relationship to Figure 46:
The DEC Alpha 8200s 536 are in a failover configuration. The center rack is a
shared disk
array.
The TI MultiServe 4000 560 is actually compound of four separate media servers
in a single
cabinet. The diagrams after this one show each "quadrant" (one of the four
media servers in a
MultiServe 4000) as a separate entity. Four each of the 16 FGD T 1 s are
connected to each
~ o quadrant.
The AlphaStation 200 workstation 564 and the terminal servers are used to
provide console
and system management. The Cabietron hubs 562 provide the network between the
media
servers 5b0 and the executive servers 536.
is
The Bay Networks hubs 566 provide the network between the VFP 504 and the
network
routers 569.
a) Internal Hardware Network
2o Figure 48 shows the VFP internal hardware/network architecture:
General notes about Figures 47-49:
The left DEC 8200 machine 536 is shown with all of its ATM and FDDI
connections 570
drawn in. The right DEC 8200 is shown with its Ethernet connections 572 drawn
in. In
actual deployment, both machines have all of the ATM, FDDI, token ring, and
Ethernet
25 connections 570 and 572 shown.
The Cabletron hubs 562 show fewer connections into ports than actually occur
because each
8200 536 is drawn with only half its network connectivity. Also, only one of
the four media
servers 560 is shown connected to the Ethernet ports. In fact, there is a
transceiver and two
Ethernet connects for each media server.
The Bay Hubs 566 are not shown in Figure 48. They are shown in Figure 49,
directlineMCI
VFP External LAN Network Connectivity.
342
CA 02279845 1999-OS-17
wo os0 rc~r~rsr~m ma -
Starting from the top of Figure 48 of the DEC 8200s 536:
The top unit contains three 4GB drives 574 for operating system, swap, etc.
The system CD
drive 576 is also located here. This unit is controlled by the Single-Ended
Small Computer
Systems Interface (SCSI) ("SES" on the diagram) interface 578 from the main
system 579.
The tape stacker 580 is a 140GB tape unit with a single drive and a 10 tape
stack. This unit is
controlled from a Fast-Wide SCSI ("FWS" on the diagram) interface 582 from the
main
system 579.
The main system unit 579 utilizes three of five available slots. Slot 1 has
the main CPU card
584. This card has one 300MHz CPU and can be upgraded to two CPUs. Slot 2 has
a
512MB memory card 586. This card can be upgraded to 2GB, or another memory
card can
be added. System maximum memory is 4GB.
Slots 3 and 4 are empty, but may be used for additional CPU, memory, or I/O
boards. Slot 5
has the main I/O card 588. This card has eight I/O interfaces:
One Fast-Wide SCSI interface 582 controls the tape stacker.
Two Fast-Wide SCSI interfaces 590-592 are unused.
2o The Single-Ended SCSI interface 578 controls the local system drives.
The FDDI interface 594 connects to one of the hubs.
The PCI slot 596 connects to a PCI expansion chassis 598.
One port is a l ObaseT Ethernet card 600 that is connected to the
corresponding card in the
other 8200 536 via a private thinnet Ethernet. This network is required for
one of the system
failover heartbeats.
An embodiment utilizes nine of the ten available slats in the PCI/EISA
expansion chassis
598. Slots 1 and 2 have disk adapters 602. Each disk adapter 602 is connected
to a RAID
disk controller 604 that has another disk controller 604 (on the other
machine) chained, which
3o in turn is connected to a disk controller 604 on that machine. Thus, each
of the 8200
machines 536 has two disk controllers 604 attached off of each disk adapter
602. This is the
primary clustering mechanism, since either machine can control all of the
disks located in
343
CA 02279845 1999-OS-17
PCT/US97/21174
Figure 48 beneath the PCI chassis 598. Slot 3 has a Prestoserve board 606.
This is a
Network File Server (NFS) accelerator.
Slot 4 has an FDDI board 608. This FDDI connection is made to the hub other
than the
FDDI connection made from main slot 5 above.
Slots 5 and 6 have ATM boards 610. It has a 1 ObaseT Ethernet card 612 that is
connected to
the corresponding card in the other 8200 536 via a private thinnet Ethernet.
This network is
required for one of the system failover heartbeats. Slot 10 is empty.
~o The two units beneath the PCI chassis are Redundant Array of Inexpensive
Disks (RAID)
disk controllers 604. Each disk controller 604 is on a SCSI chain with two
disk controllers
604 in the middle and a disk adapter 602 (one per machine) on each end. Thus
there are two
chains, each with two disk controllers 604 and two disk adapters 602. This is
the connectivity
to the main system 579. Each disk controller 604 supports six single-ended
SCSI chains. In
this configuration, each of the two chains has one disk controller with two
SES connections,
and one disk controller with three connections. Each chain has five sets 614
(or "drawers") of
disk drives as pictured in the center rack. Note the redundant power supply in
the drawer with
the RAID Disk Controller.
2o The Cabletron MMAC+ hubs 562 (Figure 47) are configured in a redundant
pair. Both the
8200s 536 and the TI media servers 560 connect to both hubs 562, and the two
hubs 562 are
also connected to each other. Starting from the left side of the hubs: The
FDDI concentrator
card 616 provides an eight port FDDI ring. Each 8200 has one connection into
the FDDI
card 616 on each hub 562. The 24 port Ethernet card 618 provides connectivity
to the TI
media servers 560. Each media server 560 connects into one Ethernet port 618
on each hub.
There are eight empty slots 620 in each hub which can be used for additional
FDDI, ATM, or
Ethernet expansion.
There are four TI media servers 560 mounted in a single rack called a
"MultiServe 4000".
3o Each media server in the rack is identical. Starting from the top unit, and
then proceeding left
to right for the main slots: The top unit 622 is a drawer that contains two 1
GB disk drives,
and a removable/hot-insertable tape drive. There are two tape drives that can
be shared
among the four media servers. The left seven boards 624 labeled "DSP xxx" are
TI MPB
344
CA 02279845 1999-OS-17
wo 9sn~oso rcT~s9~nma
boards which can each support six incoming or fifteen outgoing channels, as
labeled. These
boards 624 are grouped together into three sets. There is a right group of
three boards, a
middle group of three boards, and a single board on the left. Each group has
one T 1. The T 1
terminates at the interface marked "TIM". This is the master TI interface. TI
channels may
be shared by the set of boards delimited by the master/slave T 1 boards, and
chained together
by the bridge modules. The rightmost board 626 is the main CPU/IO board. This
board
supports an SCSI interface 628 to the disk drawer, an Ethernet connection 630
to a special
transceiver 632, and a serial port for the console (not shown).
1 o The transceiver 632 to the right of the CPU/IO board connects to Ethernet
ports on each of
the two main hubs 562. The transceiver senses if one of its Ethernet
connections has failed,
and routes traffic to the other port.
b) External Hardware/Network Connections
~ 5 Figure 49 shows the hardware and network connections from the V FP 504 to
the external
network. Notes about Figure 49: Each 8200 536 is connected onto the ISN token
ring 640
through the Bay Hubs for DDS access over SNA and BDR access over IP. A pair of
terminal
servers 642 has a connection to the console port of each machine and hub. A
DEC
AlphaStation 200 564 runs console manager software to access the ports
connected to the
2o terminal servers 642. The DECNIS routers are all on an FDDI ring 568
(Figure 46),
connected between the Bay Hubs 566 and the two DEC 8200s 536.
The Bay Hubs 566 connect the VFP system 504 to the external network through
the seven
routers 644 shown.
E. Voice~stribution Detailed Architecture
I . Overview
Voice Distribution refers to the portion of the architecture in which the NAS
546 (Figure 45)
reads and writes the subscriber's ad hoc prompts across the LAN or WAN from/to
the VFP
504 using the NFS protocol.
345
CA 02279845 1999-OS-17
PCT/US97/21174
2. Rationale
In one embodiment, voice distribution is implemented by placing a server at
each ISN site
and replicating the data via complex batch processes from each server to every
other server.
The "Large Object Management" (LOM) project defines a network-based approach.
It was
decided to use the directIineMCI VFP 504 as the network-based central object
store for the
NAS 546 to read and write customer prompts.
Figure 50 shows a network architecture to support Voice distribution traffic
in accordance
i o with a preferred embodiment. Figure 52A depicts a configuration of the
Data Management
Zone 5105 of the present invention. The Data Management Zone (DMZ) is a
firewall
between Internet dial-in platforms (although not the actual Internet itself)
and the ISN
production networks. Its purpose is to provide dial-in access to data for ISN
customers while
maintaining security for the ISN network as well as privacy and integrity of
customer data in
a production ISN network.
The DMZ permits a customer to receive periodically generated data, such as DDS
data down
feeds from a mainframe database. Such data is periodically extracted from the
database and
placed in a user account directory on a secure File Transfer Protocol (FTP}
host for
2o subsequent retrieval by a customer.
Data access for customers is through dedicated ports at dial-in gateways,
which are owned,
operated and maintained by the Internet provider. Dial-in user authentication
is through the
use one time passwords via secure identification cards, as is more fully
described below. The
cards are distributed and administered by Internet provider personnel.
The DMZ provides a screened subnet firewall that uses a packet filtering muter
to screen
traffic from the outside unsecured network and the internal private network.
Only selected
packets are authorized through the router, and other packets are blocked. The
use of multiple
3o firewalling techniques ensures that no single point of failure or error in
DMZ configuration
puts the ISN production network at risk.
346
CA 02279845 1999-OS-17
WO PCT/US97/Z11'74
The DMZ 5105 is intended to conform to several security standards. First,
individuals who
are not authorized employees cannot be allowed access to internal production
networks.
Therefore IP connectivity through the gateway is not allowed. Second, access
and use of
DMZ services is restricted to authenticated and authorized users for specific
purposes.
Therefore all other utilities and services normally found on a general purpose
machine are
disabled. Third, use of DMZ services and facilities must be carefully
monitored to detect
problems encountered by authorized users and to detect potentially fraudulent
activity.
The centerpiece of the DMZ is the DMZ Bastion host 5110. Bastion host 5110
runs an FTP
1 o server daemon that implements a modified FTP protocol, as will be
described in further detail
below. Bastion host 5110 is a highly secured machine used as the interface to
the outside
world. Bastion host 5110 allows only restricted access from the outside world.
It typically
acts as an application-level gateway to interior hosts in ISN 5115, to which
it provides access
via proxy services. Generally, critical information is not placed on Bastion
host 5110, so
t 5 that, even if the host is compromised, no access is made to critical data
without additional
integrity compromise at the ISN 5115.
Bastion host 5110 is connected to both interior and exterior users as shown in
Figure 52A.
Bastion host 5115 may be a UNIX-based computer such as an IBM RS/6000 model
580
2o running the AIX operating system.
An interior user is a user connected to the ISN production token ring 5115.
Token ring 5115
is connected to an interior packet filter 5120 such as a Cisco model 4500
modular router.
Packet filter 5120 is connected to token ring LAN 5125, which in turn is
connected to bastion
25 host 5110. Token ring LAN 5125 is a dedicated token ring that is isolated
from all
components other than bastion host 5110 and interior packet filter 5120,
thereby preventing
any access to bastion host 5110 through token ring LAN 5125 except as allowed
by packet
filter 5120.
3o Exterior users connect through exterior packet filter 5130, such as a Cisco
model 4500
modular router. Packet filter 5130 is connected to bastion host 5110 through
an isolated
Ethernet LAN segment 5135. Ethernet LAN segment 5135 is a dedicated segment
that is
isolated from all components other than bastion host 5110 and extelyor packet
filter 5130.
347
CA 02279845 1999-OS-17
PCT/US97I21174
Because of the configuration, no user can access bastion host 5110 except
through interior
packet filter 5120 or exterior packet filter 5130.
Figure 52A depicts the DMZ 5105 in connection with dial-in environment 5205.
In dial-in
environment 5205, the customer PC 5210 is connected to public switched
telephone network
(PSTN) 5220 through the use of modem 5215. Modem bank 5230 assigns a modem to
answer incoming calls from PSTN 5220. Modem bank 5230 comprises a set of high-
speed
modems 5233 such as U.S Robotics V.34 Kbps modems. Incoming calls are
authenticated by
authentication server 5235. Authentication server 5235 may be implemented
using a server
~ o such as the Radius/Keystone server running on a Sun Sparcstation model 20.
The Bastion host 5110 resides within a firewall, but is logically outside both
the ISN 5115
and the gateway site 5205.
Following authentication, the selected modem 5233 is connected to incoming
call router 5240
using Point-to-Point Protocol (PPP). PPP is a protocol that provides a
standard method of
transporting mufti-protocol datagrams over point-to-point links. PPP is
designed for simple
links that transport packets between two peers. These links provide full-
duplex simultaneous
bi-directional operation, and are assumed to deliver packets in order. PPP
provides a common
2o solution for easy connection of a wide variety of hosts, bridges and
routers). PPP is fully
described in RFC 1661: The Point-to-Point Protocol (PPP), W. Simpson, Ed.
(1994) ("RFC
1661 "), the disclosure of which is hereby incorporated by reference.
Incoming call router 5240 selectively routes incoming requests to the exterior
packet filter
5130 of DMZ 5105 over a communications link such as Tl line 5250, which is
connected to
exterior packet filter 5130 via a channel service unit (not shown). Incoming
call router 5240
may be implemented using, for example, a Cisco 7000 series multiprotocol
router. Incoming
call router 5240 is optionally connected to Internet 5280. However, router
5240 is
configured to block traffic from Internet 5280 to Exterior packet filter 5130,
and to block
3o traffic from exterior packet filter 5130 to Internet 5280, thereby
disallowing access to DMZ
5105 from Internet 5280.
- 348
CA 02279845 1999-OS-17
wo ~n3o~o rcTi~rs~nma
Bastion host 5110 runs a File Transfer Protocol (FTP) server daemon that
implements a
modified FTP protocol based on release 2.2 of the wu ftpd FTP daemon, from
Washington
University. Except as noted herein, the FTP protocol is compliant with RFC
76~; File
Transrer Protocol, by J. Postel (June I 980) ("RFC 765"), the disclosure of
which is hereby
incorporated by reference. RFC 765 describes a known protocol for transmission
of files
Y
using a TCP/IP-based telnet connection, in which the server responds to user-
initiated
commands to send or receive files, or to provide status information. The DMZ
FTP
' implementation excludes the send command (which is used to send a file from
a remote user
to an FTP server, and any other FTP command that transfers files to the FTP
host. A
o restricted subset of commands including the get (or recv), help, Is, and
guit commands are
supported.
The get command is used to transfer a file from host server 5110 to remote
user 5210. The
recv command is a synonym for get. The help command provides terse online
documentation
for the commands supported by host server 5110. T'he is command provides a
list of the files
in the current directory of the server, or of a directory specified by the
user. The quit
command terminates an FTP session. Optionally, the cd command, which specifies
a named
directory as the current directory, and the pwd command, to display the name
of the current
directory, may be implemented.
By disallowing send and other commands that transfer files to the server, a
potential intruder
is prevented from transfernng a "Trojan horse" type of computer program that
may be used
to compromise system security. As an additional benefit, the unidirectional
data flow
prevents a user from inadvertently deleting or overwriting one of his files
resident on the
Bastion server.
When the FTP daemon initiates a user session, it uses the UNIX chroot(2)
service to specify
the root of the user's directory tree as the apparent root of the filesystem
that the user sees.
This restricts the user from visibility to UNIX system directories such as
/etc and /bin, and
3o from visibility to other users' directories, while permitting the desired
visibility and access to
the files within the user's own directory tree. To further assure a secured
environment, the
FTP daemon executes at the user-id ("uid") of the user level, rather than as
root, and allows
access only to authorized users communicating from a set of predetermined IP
addresses
349
CA 02279845 1999-OS-17
wo 9sn3oso rcr~s9~nma
known to be authorized. In particular, the standard non-authenticated accounts
of anonymous
and guest are disabled.
In order to further secure Bastion server 5110, a number of daemons that are
ordinarily
started by the UNIX Internet server process inetd are disabled. The disables
daemons are
those that are either not needed for Bastion server operation, or that are
known to have
security exposures. These daemons include rcp, rlogin, rlogind, rsh, rshd,
tftp, and tftpd.
These daemons are disabled by removing or commenting out their entries in the
AIX
/etc/inetd.conf file. The /etc/inetd.conf file provides a list of servers that
are invoked by
o inetd when it receives an Internet request over a socket. By removing or
commenting out the
corresponding entry, the daemon is prevented from executing in response to a
received -
request.
As a further assurance of security a number of daemons and utilities are
disallowed from
execution by changing their associated file permissions to mark them as non-
executable (e.g.,
having a file mode of 000). This is performed by a DMZ Utility Disabler (DUD)
routine that
executes at boot time. The DUD routine marks as non-executable the above-
identified files
(rcp, rlogin, rlogind, rsh, rshd, tftp, and tftpc~, as well as a number of
other daemons and
utilities not ordinarily invoked by inetd. This set of daemons and utilities
includes sendmail,
2o gated, routed, fingerd, rexecd, uucpd, bootpd, and talkd. In addition, DUD
disables the telnet
and ftp clients to prevent an intruder from executing those clients to access
an interior host in
the event of a break-in. The telnet and ftp clients may be temporarily marked
as executable
during system maintenance activities.
Bastion host 5110 has IP forwarding disabled. This ensures that IP traffic
cannot cross the
DMZ isolated subnet 5115 by using Bastion host 5110 as a router.
The limited level of ftp service provided by Bastion server 5110 provides a
secure ftp session
but makes it difficult to perform typical system maintenance. In order to
perform system
3o maintenance, maintenance personnel must connect to Bastion host 5110 from
an interior host
within ISN 5115 using a telnet client. The FTP client program in Bastion is
then changed
from non-executable (e.g., 000) to executable {e.g., 400), using the AIX chmod
command.
Maintenance personnel may then execute the ftp client program to connect to a
desired host
350
CA 02279845 1999-OS-17
WO ~ PCT/US97121174
on ISN 5115. During this procedure, control of transfers is therefore from
within Bastion
host 5110 via the FTP client program executing within that host, rather than
from a client
outside of the host. At the end of a maintenance session the FTP session is
terminated, and
_ the chmod command is executed again to revert the ftp client program to a
non-executable
state (e.g., 000), after which the ISN-initiated telnet session may be
terminated.
To provide .logging, Bastion server 5110 implements a TCP daemon wrapper, such
as the
TCPwrappers suite from Wietse Venema. The TCf wrapper directs inetd to run a
small
wrapper program rather than the named daemon. The wrapper program logs the
client host
o name or address and performs some additional checks, then executes the
desired server
program on behalf of inetd. After termination of the server program, the
wrapper is removed
from memory. The wrapper programs have no interaction with the client user or
with the
client process, and do not interact with the server application. This provides
two major
advantages. First, the wrappers are application-independent, so that the same
program can
protect many kinds of network services. Second, the lack of interaction means
that the
wrappers are invisible from outside.
The wrapper programs are active only when the initial contact between client
and server is
established. Therefore, there is no added overhead in the client-server
session after the
2o wrapper has performed its logging functions. The wrapper programs send
their logging
information to the syslog daemon, syslogd. The disposition of the wrapper logs
is determined
by the syslog configuration file, usually /etc/syslog.conf.
Dial-in access is provided through dial-in environment 5105. The use of
authentication
server 5235 provides for authentication of users to prevent access from users
that are not
authorized to access the DMZ. The authentication method implemented uses a one-
time
password scheme. All internal systems and network elements are protected with
one-time
password generator token cards, such as the SecurID secure identification
token cards
produced by Security Dynamics, using an internally developed authentication
client/server
mechanism called Keystone. Keystone clients are installed on each element that
receive
authentication requests from users. Those requests are then securely submitted
to the
Keystone Servers deployed throughout the network.
351
CA 02279845 1999-OS-17
WO 98IZ3080 PCT/i1S97/21174
Each user is assigned a credit card sized secure identification card with a
liquid crystal
display on the front. The display displays a pseudo-randomly generated six-
digit number that
changes every 60 seconds. For an employee to gain access to a Keystone
protected system,
the user must enter their individually assigned PIN number followed by the
number currently
displayed on the secure identification card. Such authentication prevents
unauthorized access
that employ the use of programs that attempt to "sniff' or intercept
passwords, or Trojan
horse programs designed to capture passwords from users.
Authentication information collected by the Keystone clients is encrypted with
an RSA and
1 o DES encryption key, and is dispatched to one of many Keystone Servers. The
Keystone
Servers evaluates the information to verify the user's PIN and the access code
that should be
displayed on that user's card at that moment. After the system verif es that
both factors for
that user where entered correctly, the authorized user is granted access to
the system, or
resource requested.
In order to assure security from the point of entry of the external network,
no external
gateway machine has a general access account and all provide controlled
access. Each
gateway machine ensures that all gateway services generate logging
information, and~ach
external gateway machine maintains an audit trail of connections to the
gateway. All of the
2o external gateway machines have all non-essential services disconnected.
The authentication server 5235 serves as a front end to all remote access dial
up, and is
programmed to disallow pass-through. All network authentication mechanisms
provide for
logging of unsuccessful access attempts. Preferably, the logs generated are
reviewed daily by
designated security personnel.
Figure 53 depicts a flow diagram showing the fax tone detection methodology.
In step 5305,
the fax tone detection system allocates a null linked-list; that is, a linked
list having no
entries. In step 5310, the fax tone detection system starts the asynchronous
routine
3o auCheckForFaxAsync 5315. The auCheckForFaxAsync routine 5315 is an
asynchronous
program that executes concurrently with the main line program, and rather than
synchronously returning control to the calling program. The auCheckForFax
routine
evaluates the tone of the incoming call to see whether the call is originated
by a facsimile
352
CA 02279845 1999-OS-17
PCTlUS97/21174
machine, and generates an auCheckForFax response 5318 if and when a facsimile
tone is
detected.
After starting auCheckForFaxAsync routine 5315, control proceeds to step 5320.
In step
5320, the fax tone detection system adds an entry to the linked list allocated
in step 5305.
The added entry represents a unique identifier associated with the message
being processed.
In step 5330, the fax tone detection system starts the asynchronous routine
auPlayFileAsync
5335. The auPlayFileAsync routine 5335 is an asynchronous program that
executes
concurrently with the main line program, rather than synchronously returning
control to the
1 o calling program. The auPlayFileAsync routine 5335 accesses previously
stored digitally
recorded sound files and plays them to the originating caller. The sound files
played may be
used, for example, to instruct the originating caller on sequences of key
presses that may be
used to perform particular functions, e.g., to record a message, to retrieve a
list of previously
recorded messages, etc.
In step 5340, the fax tone detection system starts the asynchronous routine
auInputDataAsync
5340. The auInputDataAsync routine 5340 is an asynchronous program that
executes
concurrently with the main line program, rather than synchronously returning
control to the
calling program. The auInputDataAsync routine 5340 monitors the originating
call to detect
2o key presses by the user, in order to invoke the routines to execute the
tasks associated with a
particular key press sequence.
As has been noted, the auCheckForFaxAsync routine 5315 executes concurrently
with the
main program, and generates a auCheckForFax response 5318 if and when a
facsimile tone is
detected. In step 5350, the fax tone detection system checks to see whether an
auCheckForFax response 5318 response has been received. If a response has been
received,
this indicates that the originating call is a facsimile transmission, and the
fax tone detection
system extends the incoming call to Voice/Fax processor (VFP) 5380. If no
auCheckForFax
response 5318 is received within a predetermined time (e.g., 7 seconds), the
fax tone
3o detection system concludes that the originator of thf: call is not a
facsimile device, and
terminates the auCheckForFaxAsync routine 5315. In an implementation, it may
be
preferable to implement this check through an asynchronous interruption-
handling process.
In such an implementation, an execution-time routine may be set up to gain
control when an
353
CA 02279845 1999-OS-17
wo 98/23080 PCT/US97/21174
auCheckForFax response 5318 event occurs. This may be implemented using, for
example)
the C++ catch construct to define an exception handler to handle an
auCheckForFax response
5318 event.
Following the decision in step 5350, the fax tone detection system in step
5360 waits for the
next incoming call.
Figures 54A through 54E depict a flow diagram showing the VFP Completion
process for fax
and voice mailboxes. As depicted in Figure 54A, the VFP completion routine in
step 5401
1 o searches the database for a record corresponding to the addressed mailbox.
In step 5405, the
VFP completion routine checks to see if a mailbox record was successfully
retrieved. If no
mailbox record was found, in step 5407, the VFP completion routine generates a
VCS alarm
indicating that the desired mailbox record was not found. Because the mailbox
record was
not found, the VFP completion processor will be unable to test the attributes
of the mailbox
~ 5 address. However, regardless of whether the mailbox record is found;
control proceeds to
step 5409. In step 5409, the VFP completion processor tests the contents of
the mailbox
record, if any, to determine whether the addressed mailbox is full. If the
addressed mailbox
is full, in step 5410, the VFP completion routine plays an error message
indicating that the
addressed mailbox is at capacity and is unable to store additional messages,
and exits in step
20 5412.
In step 5414, the VFP completion processor obtains the mode of the VFP call.
The mode is
derived from the dial string provided by the originating caller, and is stored
in the
enCurrentNum field of the pstCall l State structure. The dial string has the
following format:
char number[10]; /* 10-digit 8xx number dialed by user */
char asterisk; /* constant '*' */
char mode; /* 1-byte mode */
3o char octothorp; /* constant '#' */
The mode has one of the following values:
354
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
1 guest voicemaiI
2 guest fax with voice annotation
3 guest fax without voice annotation
4 user voice/fax retrieval
5 user list maintenance
6 user recording of mailbox
In step 5416, the VFP completion processor retrieves the route number
associated with the
addressed mailbox from the database. In step 5418, the route number is passed
to the SIS
layer.
As depicted in Figure 54B, execution continues with step 5420. In step 5420,
the VFP
completion processor initialized an answer supervision flag that is used to
determine whether
t5 the VFP is accepting transfer of the call. In step 5422, the VFP completion
processor calls
the SisCollectCall routine to process the call. If the call is unsuccessful,
Step 5424 causes the
SisCollectCall invocation of step 5422 to be repeated up to a predetermined
number of
retries.
2o In step 5426, the VFP completion processor obtains a predetermined timer
expiration value
from the otto.cfg file. The timer expiration value is set to the amount of
time in which, if an
answer is not received, the VFP completion processor may conclude that the VFP
is not
currently reachable. In step 5428, the VFP completion processor sets the timer
according to
the value from step 5426. In step 5430, the VFP completion processor check to
see whether
25 answer supervision occurred prior to the expiration of the timer set in
step 5424. If so,
control proceeds to step 5430 to transfer control to the VFP.
Figure 54C depicts the operation of transferring control to the VFP in
response to an
affirmative decision in step 5430. In step 5440, any pending timers set in
step 5428 are
3o canceled. In step 5442, the VFP completion processor calls routine
sisOnHoldTerm() to put
the VFP on hold. In step 5444, the VFP completion processor calls routine
sisOffHoldOrig()
to take the originating call off hold.
355
CA 02279845 1999-OS-17
WO 98/23080 - PGT/US97/Z1174
In step 5446, the VFP completion processor plays a previously stored digitally
recorded
sound file, instructing the originating caller to wait during the process of
transferring the call
to the VFP. In step 5448, the VFP completion processor calls routine
sisOnHoldOrig() to put
the originating call back on hold. In step 5450, the VFP completion processor
calls routine
sisOffHoldTerm to take the VFP off hold. In step 5452, the VFP completion
processor calls
the auPlayDigits routine, passing to it as a parameter, a string comprising
the addressed
mailbox numbers an asterisk ('*') to indicate a field separation, the mode,
and an octothorp
('#') to indicate the end of the command string.
to In step 5454, the VFP completion processor obtains a timeout value
AckTimeout and an
interdigit delay value from the otto.cfg file. The AckTimeout value is used to
determine the
amount of time before the VFP completion processor determines that no response
is
forthcoming from the VFP. The interdigit delay value is used to time the
delays between
audio signals sent that represent telephone keypad presses. In step 5456, the
VFP completion
~ 5 processor calls the InputData routine to obtain a response from the VFP.
Following steps 5440 through 5456, or following a negative decision in step
5430, control
proceeds to step 5460, as shown in Figure 54D. In step 5460, the VFP
completion processor
requests a response from the VFP. In step 5462, the VFP completion processor
waits for the
2o VFP response or for a timer set in step 5428 to expire. In step 5464, if
the VFP has
responded, the.VFP completion processor proceeds to step 5446.
In step 5446, the VFP completion system checks the VFP response and writes the
appropriate
BDR term status record. The response indicates the acknowledgment from the TI
platform.
25 A response of '00' indicates success, and the VFP completion processor
writes a
BDR-STAT_NORMAL indicator. A response of 'O1' indicates the VFP did not
receive the
key to the addressed mailbox, and the VFP completion processor writes a
BDR STAT_DUNE TI NO DIGITS indicator. A response of '02' indicates that the
VFP
timed out while collecting the key, and the VFP completion processor writes a
3o BDR STAT DLINE TI FORMAT indicator. A response of- _ _ _ "03' indicates
that the
addressed mailbox was not found, and the VFP completion processor writes a
BDR STAT DUNE TI-MAILBOX indicator. If no response was received, a
356
CA 02279845 1999-OS-17
WO 98/Z3~0 PCT/US97J21174
BDR STAT DUNE TI NO RSP indicator is written. Following the BDR indicator,
control proceeds to step 5480 as shown in Figure 54E.
If no answer was received from the VFP, the timer set in step 5428 has
expired, and control
passes to step 5468. In step 5468 the VFP completion processor gives a VCS
alarm
w
indicating that the VFP did not answer. In step 5470, the VFP completion
processor calls
routine sisReleaseTerm() to disconnect the call to the VFP. In step 5472, the
VCS
completion processor calls routine sisOffHoldOrig to take the originating call
off of hold. In
step 5474, the VFP completion processor calls tiCancelTimers to cancel all
outstanding
to timers that have not yet been canceled. In step 5476, the VFP completion
processor plays a
previously stored digitally recorded sound file, reporting to the originating
caller that the VFP
completion processor was unable to connect to the VFP.
After either step 5476 or step 5466 (depending on the decision in step 5464),
control proceeds
to step 5480, as shown in Figure 54E. In step 5480, the VFP completion
processor checks to
see if the originating caller is a subscribed user. If so, control passes to
step 5482. In step
5484, the VFP completion processor checks to see if the originating caller is
a guest user. If
so, control passes to step 5482. Step 5482 then returns the originating caller
to the menu
from which the caller initiated the VFP request. If the originating caller is
neither a
2o subscribed user nor a guest, control passes to step 5486. In step 5486, the
originating caller is
assumed to be a fax call, and the call is disconnected.
Figures 55A and 55B depict the operation of the Pager Termination processor.
In step 5510,
the pager termination processor calls the GetCallback routine to obtain the
telephone number
that will be used to identify the caller, and that will be displayed on the
paging device to
identify the number to be called back by the pager subscriber. The GetCallback
routine is
describe in detail below with respect to Figure 56.
In step 5515, the pager termination processor checks to see if a telephone
number was
3o returned by the GetCallback. If no number was returned, in step 5520 the
pager termination
processor indicates that the call should be ended, and in step 5522 provides
the caller with a
menu to select another service.
357
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97l21174 -
If a number was returned, the addressed pagers PIN is obtained from the
database in step
5530. The pager termination processor constructs a pager dial string
comprising the pager
PIN retrieved in step 5530 and the callback number obtained in step 5510. In
step 5532, the
pager termination processor obtains the pager's type and routing information
is obtained from
the database. In step 5534, the pager termination processor checks the
configuration file to
obtain a pager parse string that defines the parameters for pagers of the type
addressed. In
step 5536, the pager termination processor checks to see whether the requested
pager parse
string was successfully retrieved. If not, in step 5538 the pager termination
processor
indicates that the page could not be performed by setting the BDR term status
to
BDR STAT PAGER NOT FOUND, and in step 5540 provides the caller with a menu to
select another service.
If the pager parse string was successfully retrieved, the pager termination
processor proceeds
to step 5550 as shown in Figure 55B. In step 5550, the pager termination
processor calls the
~ 5 pager subsystem, passing to it the route number, the dial string, and the
pager parse string. In
step 5552) the pager termination processor checks the return code from the
pager subsystem.
If the page was successfully completed, the pager termination processor, in
step 5554 plays a
digitally prerecorded message to the caller, informing the caller that the
page has been
successfully sent. In step 5556 the enEndCallStatus field is updated to mark
the pager call -
2o complete. In step 5558, the transfer status is marked as blank, indicating
that there is no need
to transfer the caller, and in step 5560, the pager termination processor
presents the user with
a menu permitting it to select another service or to end the call.
If the page was not successfully completed, the pager termination processor
checks in step
25 5570 whether the caller had disconnected during the page attempt. If the
caller had
disconnected, the pager termination processor in step 5575 checks to see
whether the page
had been sent prior to the disconnection. If the page was sent despite the
disconnect, the
pager termination processor in step 5580 indicates a normal ending to the page
request in step
5580 and sets the status as complete in step 5582. In step 5584, the pager
termination
3o processor presents the user with a menu permitting it to select another
service or to end the
call.
358
CA 02279845 1999-OS-17
WO PCT/US97/21174
If the page was not sent the pager termination processor indicates an abnormal
ending to the
page request in step 5586 and indicates a caller disconnect in step 5588. In
step 5590, the
pager termination processor presents the user with a menu permitting it to
select another
service or to end the call.
If the caller has not disconnected, the pager termination processor sets a
code indicating the
reason for the failure in step 5572. The failure types include
BDR_STAT_PAGER ROUTE NUM (for an invalid route number);
BDR STAT_PAGER CRIT ERROR (for a failure in the originating call);
t o BDR STAT_PAGER TIMEOUT (for the failure of the pager to acknowledge the
call within
a predetermined timeout time interval); BDR STA7 =PAGER DIGITS HOLD (for the
failure of the pager subsystem to play the digits corresponding to the pager
address);
BDR_STST_PAGER DISC (for a premature disconnect of the paging subsystem); and
BDR_STAT PAGER NOT FOUND (for an invalid parse string).
~5
In step 5592 the pager termination processor posts the error code selected in
step 5572 to the
BDR. In step 5582, the pager termination processor plays a prerecorded digital
sound file
indicating that the page could not be sent. In step 5595 the enEndCallStatus
field is updated
to mark the pager call complete. In step 5597, the transfer status is marked
as blank,
2o indicating that there is no need to transfer the caller, and in step 5599,
the pager termination
processor presents the user with a menu permitting it to select another
service or to end the
call.
Figure 56 depicts the GetCallback routine called from the pager termination
processor in step
25 5510. In step 5610 the GetCallback routine obtains constants that define
the applicable start
and interdigit delays from the otto.cfg file. In step 5615, the GetCallback
routine plays a
prerecorded digital sound file prompting the caller to provide a callback
telephone number,
by pressing the applicable keypad keys, followed by an octothorp ('#'). In
step 5620, the
GetCallback routine reads the number entered by the caller. In step 5625 the
data received is
3o placed in the BDR. In step 5630, the GetCallback routine checks to see if
the number entered
was terminated by a '#' character. If so, the GetCallback routine returns
success in step
5635. If not, the GetCallback routine, in step 5640, sees if the retry count
has been exceeded.
If the retry count has not been exceeded, execution repeats from step 5615. If
the retry count
359
CA 02279845 1999-OS-17
WO 98/23080 PGTIUS97/21174
has been exceeded, in step 5650, the GetCallback routine plays a prerecorded
digital message
indicating that the number was not successfully received, and in step Sb60
returns an error
condition to the calling program.
The following description sets forth a user interface for user-management of
directlineMCI
profile items currently accessed via ARU (DTMF) and Customer Service. These
items
include:
(De)Activate Account
Find-Me Routing
- Schedules
- 3-Number Sequence
- First, Second, Third Numbers and Ring-No-Answer Timeouts
Pager OnlOff
Override Routing
Final (Alternate) Routing
Caller Screening
Pager Notification of Voicemail Messages
Pager Notification of Faxmail Messages
Speed Dial Numbers
The following table lists the fields that the directlineMCI customer is able
to update via
DTMF. This list does not include all fields in the service, only those that
are used by the
directlineMCI application.
Primary Termination
Primary Time-out Value - _
secondary Termination
~econdaryTime-out Value
tertiary Termination
TertiaryTime-out Value
350
CA 02279845 1999-OS-17
WO 983050 PCT/US97/21174
Override Routing
Override Time-out Value
Alternate Routing
Alternate Time-out Value
PIN Flags, specifically:
Bit 10 Schedule 1
Bit 11 Schedule 2
Bit 1 S Page on
Vmail
Bit 16 Page on Fax
StateVFlags, specifically:
Bit 3 Account
Available
Bit 13 Pager On/Off
Bit 14 Find-Me
On/Off
Bit 15 Voicemail
On/Off
Bit 16 Fax On/Off
Call Screening State
Default Fax Number -
Speed Dial # 1
Speed Dial #2
Speed Dial #3
Speed Dial #4
Speed Dial #5
Speed Dial #6
Speed Dial #7
Speed Dial #8
Speed Dial #9
A user will access his directlineMCI profile via
http:/www.mci.services.com/directline.
Upon entry of a valid Account ID and Passcode, the user's Routing Screen witl
be presented.
361
CA 02279845 1999-OS-17
WO 98/23080 PCT/ITS97/21174
The user may click on tabs to move from one screen to another. If a user
returns to a screens
that's been updated during that session, the screen will be displayed as it
was when he last
left it, i.e. any updates he's submitted will be reflected in the data. If,
however, a user logs
off, or times out, when next he logs into his profile management screens, the
data displayed
will be from a new query into the 800PIN_1 Call database. Updates made within
the last 15
minutes may not have reached the NIDS databases serving the Web Server, so the
data may
not reflect any recent updates.
The following items will appear in the index frame, and will act as links to
their associated
Web screens. When a user 'clicks' on one of these items, the associated screen
will be
displayed in the text frame. -
Call Routing
Guest Menu
Override Routing
Speed Dial Numbers
Voicemail
Faxmail
Call Screening
In addition, a LOGOFF button will appear at the bottom of the index frame.
Clicking on this
button will result in immediate token expiration, and the user will be
returned to the login
screen.
F. Login Screen
Figure 57 shows a user login screen 700 for access to online profile
management.
directlineMCI Number 702
The account ID will be the directlineMCI customer's 10-digit access number, of
the format
8xx xxx xxxx. This number, concatenated with a PIN of '0000', will be the key
into the
1 Call database, which contains the customer profile data.
The user will not be allowed a successful login if the Program flag (PIN flag
4) is set to 'N'.
If a login attempt is made on such an account. the Login Error screen will be
displayed.
362
CA 02279845 1999-OS-17
WO 9g/Z3pg0 PGT/US9'7/21174
Passcode 704
The passcode will be the same as that used to access user options via the ARU
interface. It is
a six-character numeric string. The user's entry will not be echoed in this
field; an asterisk
' 5 (*} will be displayed for each character entered.
Statas message
directlineMCI Number: "Enter your directlineMCI number."
Passcode: "Enter your passcode."
1o
G. Call Routing Screen
Figure 58 shows a call routing screen 710, used to set or change a user's call
routing
instructions.
15 "Accept Calls" Section 712
The user can specify whether calls are accepted at 712 on her account by
selecting the
appropriate radio button 714 or 7I6. These buttons <:orrespond directly to the
Account
Available flag (State flags, bit 3) in the customer's directline record:
Radio Buttons~Account Available
flag
Accept Calls Y
Do Not Accept N
Calls
"Choose from the selections below" Section 718
The user specifies whether the guest caller should receive a Guest Menu, or
Override Routing
treatment. This selection will indicate whether the data in the Guest Menu or
Override
Routing screen is applicable.
363
CA 02279845 1999-OS-17
WO 98/23080 PGT/US97/21174
The customer's Override Termination will be populated as follows, according to
the user's
selection:
'4ffex Guests...' pvei~ide
itadio -
Buttons . . . Termination
Guest Menu 00
No Menu - Override 08* (default
Routing voicemail)
"When I cannot be reached..." Section 720
A user specifies call treatment for those calls for which he was unable to be
reached . The
Alternate Termination in the customer record is updated as follows:
Radio Buttons . . Alternate
. .. :: .; , ., :y . Terniiz~ation
. . ':
Voicemail 08
Pager 07
Voicemail or Pager 09
- Caller
Choice
Final Message OS
Status messages
Depending on the choices made by the user, the following status messages are
provided to the
user for each selection identified below:
Do Not Accept Calls: "No calls will be accepted on your directlineMCI Number."
Accept Calls: "Calls will be accepted on your directlineMCI Number."
~ 5 Guest Menu: "Lets callers select how they want to contact you." -
No Menu - Override Routing: "Routes callers to a specific destination selected
by you.''
Voicemail: "Callers will be asked to leave a voicemail."
Pager: "Callers will be prompted to send you a page."
Voicemail or Pager: "Callers can choose to leave you a voicemail or send you a
page."
2o Closing Message: "Callers will hear a message asking them to try their call
later."
364
CA 02279845 1999-OS-17
WO 98I23t180 - PCT/US97/21174
H. Guest Menu Co»ftguration Scree»
When Override Routing has been disabled, i.e., when Guest Menu has been
selected, a Guest
Menu will be presented to the guest caller. The user has the ability to
configure his Guest
Menu using a guest menu configuration screen 730 (Figure 59) to the following
extent:
"Fi»d Me Routing" Checkbox 732
In this phase, Find-Me Routing cannot be de-selected. The check box will be
checked
based on the Find-Me Flag (PIN Flags, bit 9, and the option greyed out.
If the subscriber enters a 'leading 1' for a domestic number, it will be
stripped from
t o the number, and only the NPA-Nxx-xxxx will be stored in the database.
When programming his 3--Number Sequence numbers, the subscriber may select the
number of rings, from 1 to 6, the system should allow before a Ring-no-Answer
decision is
made. The number of rings will be stored in the database in terms of seconds;
the formula for
calculating seconds will be: 6 *Ring~Limit. The default, if no value is
entered, is 3 rings, or
t 5 18 seconds. When reading from the database, from I) to 8 seconds will
translate to 1 ring. A
number of seconds greater than 8 will be divided by six, with the result
rounded to determine
the number of rings, up to a maximum of 16.
Updates to the customer's record will be as follows:
Radio Buttonsgched~e ll2 p.y Secondary . ~ 'Tertiary
_ 'flags . Termination Tezm~nation aniiTezmination
~ and ~. and
T'uneout v' "Timeout Timeout
... .
Schedules Both Y no change no change no change
3-Number Both N 1st entered 2nd entered 3rd entered
Sequence number* * number* * and number* *
and and
timeout timeout timeout
20 **Domestic/international termination will be validated as described in
Appendix A.
"Leave a Voicemail " Checkbox 734
In this phase,Voicemail cannot be de-selected. The check box will be checked
based
on the Vmail Flag (PIN Flags, bit 3), and the option grayed out.
"Send a Fax " Checkbox 736
365
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
In this phase, Fax cannot be de-selected. The check box will be checked based
on the
Fax Termination Flag (PIN Flags, bit 13), and the option greyed out.
"Send a Page " Checkbox 738
The user can specify whether callers will be offered the paging option by
toggling the box
labeled Send me a Page. This box corresponds directly to the Pager On/Off flag
(State flags,
bit 13) in the customer's directline record:
Page Qhe~kbox Rager OnlOff
flag
Checked Y
Unchecked N
Status messages
Find Me Routing: "Allows callers to try to 'find you' wherever you are."
Schedule Routing: "Routes callers based on your schedule."
Three Number...: "Allows callers to locate you through the three numbers."
1 st #, 2nd #, 3rd #: "Enter telephone number."
~ 5 1 st~ 2nd 3rd Ring Limit: "Enter the number of times to ring at this
number."
Leave a Voicemail: "Allows callers to leave you a voicemail."
Send a Fax: "Allows callers to send you a fax."
Send a Page: "Allows callers to send you a page."
I. Override Routing Screen
2o Figure b0 shows an override routing screen 740, which allows a user to
route all calls to a
selected destination. When a user selects to route all his calls to a specific
destination,
bypassing presentation of the guest menu 730 of Figure S9, the Override
Termination in the
customer record will be updated as follows:
Buttons ~ Termination
Guest Menu selected 00
Voicemail ~ 08
366
CA 02279845 1999-OS-17
wo 9sn~uso rcn~rsg~mm4 -
Pager 07
Find-Me 06
Telephone number Entered number**
When this option is initially selected from the Profiles screen, there will be
no Override
Routing setting in the user's customer record. The default setting, when this
screen is
s presented, will be Voicemail) if available, Find-Me if Voicemail is not
available.
Status messages
Find Me Routing: "Allows callers to only try to 'find you' wherever you are."
Schedule Routing: "Routes callers based on your schedule."
Three Number...: "Allows callers to locate you through the three numbers."
I st #, 2nd #, 3rd #: "Enter telephone number."
I st~ 2nd 3rd Ring Limit: "Enter the number of times to ring at this number"
Voicemail: "Callers will be prompted to leave you a voicemail only."
Send a Page: "Callers will be prompted to send you a page only."
~ 5 Temporary Override Number: "caller will only be routed to this number you
select."
Telephone Number Ring Limit: "Enter the number of times to ring at this
number"
J. Speed Dial Screen
2o Figure 61 shows a speed dial numbers screen 744. A user may update his nine
(9) Speed Dial
numbers via the Web interface. Speed Dial numbers labeled 1 through 9 on the
Web page
correspond with the same Speed Dial numbers in the customer's record. Domestic
and
international termination will be validated as described below.
25 Status messaees
1 - 9: "Enter speed dial number <1 - 9>."
367
CA 02279845 1999-OS-17
WO 98/23080 - PCTIUS97/Z1174
Figure 62 shows a voicemail screen 750.
"Receive Voicemail Messages" Checkbox 752
"Page me when I receive" Checkbox
"Page me when I receive a new voicemail message" Checkbox 754. This box
corresponds
s directly to the Page on Vmail flag (PIN flags, bit I S) in the customer's
directline record:
Pager IV~titi Page ~on
ration , V~sii
Checkbox flag
Unchecked N
Checked Y
Status messages
Receive voicemail...: "Callers will be able to leave you a voicemail message."
1 o Page me each time. . . : "You will be paged when you receive a voicemail
message."
Figure 63 shows a faxmail screen 760.
"My primary Fax number is" Field 762
1 s "Receive Faxmaii Messages" Checkbox 7b4
Profile management of this item is shown as it appears on the Faxmail Screen.
"Page me when I receive" Checkbox 766
This item appears as a "Page me when I receive a new voicemail message"
Checkbox 766.
This box corresponds directly to the Page on Fax flag (PIN flags, bit 16) in
the customer's
2o directline record:
'Parker Notifir,~:tioapage:on Fax
-. flag
Checkbox
Unchecked N
Checked y
368
CA 02279845 1999-OS-17
WO 98123050 PCT/US97/Z1I74
Status messages
Receive fax...: "Callers will be able to send you a fax."
Page me each time...: "You will be paged when you receive a fax."
" 5
Figure 64 shows a call screening screen 770. A user may elect to screen his
calls by caller
name, originating number or both name and number. The Call Screening State in
the
customer record will be updated as follows:
CaI~ SGt~~ri$ R8d14-~B1#~OI1SC~ SCI's
. ~
Checkbox: , ,. , :;, :State:: ~ ~
~ ' . ..
Unchecked n/a 00
Checked Number Only 02
Name Only 01
Name and 03
Number
to
Status messages
Allow me to screen...: "Activating this feature allows you to screen your
calls."
Name only: "Caller's name will be presented to answering party."
Telephone number: "Caller's telephone number will be presented to answering
party"
t 5 Name and Telephone: "Caller's name and telephone number will be presented
to answering
party.,
Figures 65-67 show supplemental screens 780, 782 and 784 used with user
profile
management.
2o Login Error screen 780
This error screen is presented when a login attempt has failed due to an
invalid account
number, passcode, or a hostile IP address. This is also the screen that is
displayed when a
user's token has expired and he's required to login again.
Update Successful screen 782
369
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174 -
This screen is presented when an update has been successfully completed. The
'blank' will
be filled in with: 'Call Routing options have ', 'Guest Menu options have ',
'Override
Routing has ', 'Speed Dial Numbers have ', 'Voicemail options have', 'Faxmail
options
have', and 'Call Screening option has '.
Update Failed screen 784
This screen will be presented when a user has attempted to enter one or more
invalid
terminating number(s), or to update his account with a blank First number. The
account will
not be updated until corrections are made and all numbers are successfully
validated.
In the various screens of the user interface, profile options are 'grayed
out', indicating that
the option is not available from the screen, based on the following flag
settings:
Green
Login Screen Login Program (Follow-Me) Flag
Profile Screen Accept Calls Avail Programming Flag
Final Routing to Find-Me Fiag AND
Voicemail
Voicemail Flag
Final Routing to Find-Me Flag AND
Pager
Pager Termination Flag
Final Routing to Find-Me Flag AND
Voicemail
or Pager Voicemail Flag AND
Pager Termination Flag
Guest Menu Schedules Find-Me AND
Schedule 1 Trans populated AND
Schedule 2 Trans populated
Three-Number SequenceFind-Me AND
Domestic Termination Flag OR
International Termination
( 1 st, 2nd, 3rd)
Domestic Termination Flag OR
International Termination Flag
a page Pager Termination Flag
370
CA 02279845 1999-OS-17
WO 98/?~080 PCT/US97/21174
Override Routing Schedules Find-Me Flag AND
Schedule 1 Trans populated
AND
Schedule 2 Trans populated
Three-Number SequenceFind-Me AND
Domestic Termination Flag
OR
International Termination
Number ( 1 st, 2nd, Find-Me Flag AND
3rd)
Domestic Termination Flag
OR
International Termination
Flag
Pager Pager Termination Flag
Telephone Number Find-Me Flag AND
Domestic Termination Flag
OR
International Termination
Speed Dial Numbers 1 - 9 Speed Dial Programming
AND
Domestic Completion Flag
OR
International Completion
Flag
Voicemail screen Page me when I receive...Voicemai! Flag AND
Pager Termination Flag
Faxmail screen Page me when I receive...Fax Termination Flag AND
Pager Termination Flag
Call Screening Allow me to screen...Call Screening Programming
For some of the profile options described above, validation checks are made as
follows:
International numbers, with the exception of North American Dialing Plan
(NADP)
numbers, must be prefaced with 'Ol 1', or will not be accepted for
programming.
976 blocking will be implemented as follows:
The International Blocking database will be queried, using Category 000, Type
002, ,
and the programmed NPA, looking for a pattern match, to ensure that the
programmed
r number is not a blocked Information/Adult Services number. If a match is
found,
programming to that number will not be allowed.
Country Set blocking will be implemented as follows:
371
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/Z1174
- The Country Set of the directlineMCI Property record will be validated
against the
Country Code of the programmed number. If the terminating country is blocked
the
directlineMCI Country Set, programming to that number will not be allowed.
Programming Routing
If the programmed Perform the following validation
number is: checks
Domestic Domestic Flag
976 Blocking
NADP Domestic Flag
976 Blocking
Cset Blocking using Term
PCC, Auth
Cset
International International Flag
Cset Blocking using Term
CC, Auth
Cset
372
CA 02279845 1999-OS-17
wo ~3oso rcr~s9~nma
Programming Speed Dial Numbers
If the programmed Perform the following validation
number is: checks
' Domestic Domestic Comp Flag
976 Blocking
NADP Domestic Comp Flag
976 Blocking
Cset Blocking using Term
PCC, Auth
Cset
International International Comp Flag
Cset Blocking using Term
CC, Auth
Cset
Figure 68 is a flow chart showing how the validation for user entered speed
dial numbers is
s carried out. The same flow chart is applicable to validation of entries by a
guest on the guest
screen when a call is made to a user by a non-subscri'~ber.
The integrated switching system and packet transmission network of this
invention allows the
w provision of an improved feature set for users. directlineMCI is a single-
number access
personal number, with features including Find-Me functionality, voicemail,
paging, and fax
store and forward services. A subscriber, or user, is asked for profile
information, which is
entered into his customer record in the directlineMCI database on the ISN
mainframe. The
product's feature set includes:
Personal Greeting: The user has the option of recording a personal greeting to
be played to
is his guest callers. If a user records a personal greeting, it replaces the
'Welcome to
directlineMCI' default greeting.
Guest Menu: The Guest Menu is defined by which features the user has
subscribed to. A
guest caller to a 'fully loaded' account will be presented options to Speak to
or Page the user,
Send a Fax, or Leave a Voicemail Message.
373
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
3- Number Sequence for Find-Me functionality: The system attempts to reach the
user at
three numbers, trying the First (Primary) number, then the Second(ary), then
the Third
(Tertiary) number. If no answer is received at any of these numbers, the call
is treated as
prescribed in Alternate Routing.
2-Level Schedule for Find-Me functionality: The system attempts to reach the
user at two
numbers, using current date/day/time information to query his schedules.
Attempts are made
to a number from the user's Schedule 1, then Schedule 2; if no answer is
received, Alternate
Routing defines the treatment.
Alternate Routing allows the user to prescribe the treatment of a guest caller
who chose to
reach him, but no answer was received at any of the attempted numbers. Options
for
Alternate Routing include Voicemail, Pager, a Guest's choice of Voicemail or
Pager, or a
Closing Message, asking the caller to try his call again at a later time.
Override Routing allows the user to disable the presentation of the Guest
Menu, and prescribe
a single treatment for all guest callers. Options include completion to a
telephone number,
the user's defined Find-Me sequence, Voicemail, or Pager.
Default Routing is the treatment of a guest caller who, when presented the
Guest Menu, does
not respond after three prompts. Default Routing options include a transfer to
the Operator,
2o completion to a telephone number, the Find-Me sequence, or Voicemail.
Call Screening allows the user to define whether or not he wishes callers to
be announced
before being connected. Options include no call screening, or having the
caller identified by
name, originating telephone number, or both name and number.
2s The 'Place a Call' option in the user's menu allows him to make a call, and
have it charged to
his directlineMCI account.
Voice/Faxmail: Both voice and fax messages can be stored for later retrieval
by the user.
The user may opt to be notified when new voice and/or fax messages are
deposited into his
mailbox.
The Voice / Fax Platform (VFP) has been integrated into the Intelligent
Services Network
(ISN), to allow the ISN applications to query its databases, and billing
records to be cut
directly from the VFP.
374
CA 02279845 1999-OS-17
WO 98/23080 PG"T/US9?/211?4
Among the changes to the original directlineMCI product are the following
items:
375
CA 02279845 1999-OS-17
WO 98/23080 PCT/I1S97/21174
Find-Me Routing
Find-Me Routing now has two options, selectable by the subscriber: the 3-
number sequence
currently implemented, or the 2-level schedule option. The schedule option is
implemented
such that the subscriber's Schedule 1 translation will be treated as the
primary termination,
and his Schedule 2 translation will be treated as the secondary termination.
Find-Me Routing
is described in more detail in the CaII Flow diagrams and ARU Impacts
sections.
Default Routing
Default Routing is the prescribed action the application takes when a caller
does not respond
to Guest Menu prompts. Options for Default Routing include a telephone number,
voicemail,
Find-Me routing, and Operator transfer.
Voice/Fax Message Information
When a subscriber accesses the user menu, the application provides mailbox
status
information, including the number of new voice or fax messages, and if his
mailbox is full.
The application launches a query to the VFP database to obtain this
information.
t 5 Speed Dial
In addition to the ability to complete a call to a telephone number entered
real-time, the
subscriber is now able to complete to programmed Speed Dial numbers. These 9
Speed Dial
numbers will be user-programmable via DTMF.
2o K ARU CALL FLOWS
Figs. 69A through 69AI depict automated response unit (ARU) call flow charts
showing
software implementation of the directline MCI product described above, and are
useful for a
further understanding of the invention.
25 Fig. 69A depicts the starting point for processing of an ARU call. As a
call initiates, it is
assumed to be a guest call. If the account to which the call is directed is
not currently online,
the ARU in Step 69010 plays a message indicating that calls cannot be accepted
for the
account, and in Step 69012 disconnects the call. If the ARU detects a fax tone
on the
376
CA 02279845 1999-OS-17
WO 98J23080 - PCT/US97J21174
incoming call, the ARU in Step 69014 performs the ARU Xfer to Voice/Fax Guest
Fax
without Annotation routine, which is described below with respect to Fig. 69L.
If no fax tone
is detected, the ARU in Step 69018 performs the ARU Play Greeting routine,
which is
described below with respect to Fig. 69L. The ARL;~ then checks to see whether
the
subscriber has indicated an override for incoming calls. If so, in Step 69020
the ARU
performs the ARU Find Me routine, specifying a parameter of "Override." The
ARU Find
Me routine is described below with respect to Figs. 69E and 69F. If override
has not been
specif ed, the ARU in Step 69022 performs the ARI:~ Guest Menu routine, which
is described
below with respect to Fig. 69D.
Fig. 69B depicts the ARU Play Greeting routine. If a custom greeting has been
recorded, the
ARU plays the custom greeting in Step 69030. Otherwise, the ARU plays a
generic
prerecorded greeting in Step 69032.
Fig. 69C depicts the ARU Play Temp Greeting routine. If a temporary greeting
has been
recorded, the ARU plays the temporary greeting in Step 69034. If a custom
greeting has been
recorded, the ARU plays the custom greeting in Step 69036. Otherwise, the ARU
plays a
generic prerecorded greeting in Step 69038.
2o Fig. 69D depicts the ARU Guest Menu routine. In Step 69040, the ARU
presents an audible
menu to the caller. In the example shown, item ' 1' corresponds to a request
to speak to a
subscriber; item '2' corresponds to a request to leave a voice mail message
for a subscriber;
item '3' corresponds to a request to send a fax to a subscriber; and item '4'
corresponds to a
request to page a subscriber. In addition, a subscriber may enter his or her
passcode to gain
access to the ARU as a subscriber.
If the caller requests to speak to a subscriber, the ARU checks the schedule
flags associated
with the caller's profile. If the subscriber's profile indicates routing by
schedule, the ARU in
Step 69042 performs the Find Me routine of Fig. 69E and 69F, using "Sched 1 "
as the
3o parameter. If the subscriber's profile does not indicate routing by
schedule, the ARU in Step
69044 performs the ARU Find Me routine using "First" as the parameter. The ARU
Find Me
routine is discussed in further detail below with respect to Figs. 69E and
69F.
377
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
If the caller requests to leave a voice mail message, the ARU checks to see
whether the
subscriber's mailbox is full. If the mailbox is full, a recorded message is
played and the
caller is returned to the guest menu. If the mailbox is not full, a recorded
message is played
advising the caller to hold while he is transferred to the ARU Voicemail
routine in Step
69046.
If the caller requests to send a fax, the ARU checks to see whether the
subscriber's mailbox is
full. If the mailbox is full, a recorded message is played and the caller is
returned to the guest
menu. If the mailbox is not full, a recorded message is played advising the
caller to hold
while he is transferred to the voice/fax routine in Step 69048.
If the caller requests to page the subscriber, the ARU in Step 69050 performs
the ARU Send
Page routine, which is described with respect to Fig. 69M, below.
t 5 If the caller enters a valid passcode, the ARU in Step b9052 performs the
ARU User Call
routine, which is described with respect to Fig. 69P, below.
Figs. 69E and 69F depict the operation of the ARU Find Me routine. As shown in
Step
69060, the ARU Find me routine takes a single parameter Term_Slot, which is
set by the
2o caller and used by the ARU performing the ARU Find Me routine to choose
among
alternative courses of action. If Term-Slot is set to "Find Me", this
indicates that the ARU is
to use the default method of determining the subscriber's current number. This
value may be
set, for example, for override or default processing. If the subscriber's
profile includes
schedule flags, the ARU performs the ARU Find Me routine using the "Schedt"
parameter as
25 shown in Step 69062; if not, the ARU performs the ARU Find Me routine using
the first
telephone number in the list of numbers for the subscriber, as shown in Step
69061.
If Term Slot is set to "Voicemail," the ARU plays a message to the caller that
the subscriber
has requested that the caller leave a voice mail message. If the subscriber's
mailbox is not
3o full, the ARU in Step 69064 performs the ARU Xfer to Voice/Fax Guest Voice
routine,
depicted in Fig. 69K. That routine returns if unsuccessful, in which case a
message is played
indicating that the caller should try the call later, and the caller is
disconnected. Likewise, if
378
CA 02279845 1999-OS-17
WO _ PCT/US97I21174
the subscriber's mailbox is full, the ARU plays messages indicating that the
mailbox is full
and that the caller should try the call later, and the caller is disconnected.
If Term_Slot is set to "Pager," the ARU plays a message to the caller that the
subscriber has
requested that the caller leave a request to page the subscriber. The ARU then
performs the
ARU Send Page routine, which is described with respect'to Fig. 69M, below.
That routine
returns if unsuccessful, in which case a message is played indicating that the
caller should try
the call later, and the caller is disconnected.
If Term Slot is set to any POTS ("Plain Old Telephone Service") value (such as
Schedl,
Sched2, First, Second, or Third), the POTS value indicates that the subscriber
has specified
that incoming calls be sent using the standard telephone system, and the ARU
has been
directed to use the particular scheduled or selected telephone number. In Step
69070, the
ARU performs the ARU Record Name routine to acquire a digital recording of the
caller's
15 identification. The ARU Record Name routine is described in detail with
respect to Fig. 69H,
below. The ARU plays an appropriate message for the caller (e.g., "Please hold
while I try to
reach your party" on the first attempt, and "I am still trying to reach your
party; please
continue to hold" for subsequent attempts). In Step 69071, the ARU places the
caller on hold
and launches the call to the selected telephone number. If the call is
answered by an
2o individual, the ARU in Step 69072 performs the ARU Connect Call routine,
discussed below
with respect to Fig. 69I. If the line is busy, the ARU in Step 69074 performs
the ARU
Alternate Routing routine of Fig. 69N. If the ARU detects an answering
machine, it checks
to see whether the subscriber has requested that the ARU roll over to the next
alternative
number upon encountering an answering machine. If not, the ARU connects the
call.
25 Otherwise, the ARU selects the next number in rotation to call and re-
performs the ARU Find
Me routine using the newly-selected number.
If there is neither a live answer, a line busy signal, nor an answering
machine answer, then if
Term_Slot is set to "Operator," the ARU performs the ARU Guest Xfer to MOTC
routine,
3o described below with respect to Fig. 6.9M, to transfer the call to the
operator. Otherwise, the
ARU selects the next telephone number, if any, and re-invokes the ARU Find Me
routine
with the new number. If no more numbers to check remain, the ARU in Step 69084
performs
the ARU Alternate Routing routine of Fig. 69N.
379
CA 02279845 1999-OS-17
WO 98/Z3080 PCT/US97I21174
Fig. 69G depicts the ARU Record Name routine. This routine is used to record
the name of
the caller if the subscriber has specified call screening, either by name or
by name and ANI.
If the subscriber has specified call screening, the ARU checks to see whether
the caller's
name has been recorded on a previous pass. If not, the caller is prompted to
supply a name,
and the audible response is recorded in Step 69090. If the subscriber has not
specified either
form of call screening, the ARU Record Name routine returns without recording
the caller's
name.
1 o Fig. 69H depicts the ARU Guest Xfer to MOTC routine. This routine plays a
prerecorded
message asking the caller to hold, and then transfers the call to the operator
in Step 69092.
Fig. 69I depicts the ARU Connect Call routine. If operator assistance is
required to complete
the call, the ARU performs the ARU Guest Xfer to MOTC routine of Fig. 83H. If
the
t 5 subscriber has not requested call screening, the call is connected to the
subscriber. If the
subscriber has selected call screening, the ARU plays a set of informational
messages to the
subscriber. The ARU plays "You have a call from," followed by a message
identifying the
caller, depending on the options chosen by the subscriber and whether a caller
name had been
recorded. If the name is not recorded, the identifying message 69106 gives
only the ANI
2o from which the call was placed. If a name was recorded, the identifying
message includes the
name as in Step 69107 if the subscriber has requested screening by name, or
the name and
ANI as in Step 69108 if the subscriber has selected screening by name and ANI.
After
prompting the subscriber with the identifying information, the ARU in Step
69110 performs
the ARU Gain Acceptance routine depicted in Fig. 69J.
Fig. 69J depicts the ARU Gain Acceptance routine called from Step 69110. The
ARU
checks whether the subscriber has an available mailbox that is not full. If
so, the ARU
prompts the subscriber to indicate whether to take the call or to have the
call directed to voice
mail. If the mailbox is full or not available, the ARU prompts the subscriber
whether to take
3o the call or direct the caller to call back later. If the subscriber
indicates that he will take the
call (e.g., by pressing '1'), the ARU connects the call in Step 69124.
Otherwise, the ARU
acknowledges the refusal with an appropriate informational message (e.g.,
"Your caller will
be asked to leave a voice mail message" or "Your caller will be asked to try
again later,"
380
CA 02279845 1999-OS-17
WO 98/Z3080 PCT/US97I21174
depending on the condition of the mailbox determined in Step 69120). The ARU
disconnects
the subscriber and takes the calling party off hold. The ARU plays a recording
to the calling
party indicating that it was unable to reach the subscriber and optionally
prompting the caller
to leave a voice mail message. If no mailbox is available, the caller is
disconnected. If a
non-full mailbox is available, the ARU in Step 69128 performs the ARU Xfer to
Voice/Fax
Guest Voice routine of Fig. 69K. Following this routine, the ARU plays a
message asking
the caller to call back later, and disconnects.
Fig. 69K depicts the ARU Xfer to Voice/Fax Guest Voice routine, which connects
the caller
l0 to the VFP to leave a voice mail message. The ARU attempts to acquire a
handshake with
the VFP. If the handshake is successful, the ARU connects the call in Step
69130. If
unsuccessful, the ARU plays an error message in Step 69132 and exits. Fig. 69L
depicts the
ARU Xfer to Voice/Fax Guest Fax w/ or w/out Annotation routine, which connects
the caller
to the VFP to transmit a fax. The ARU attempts to acquire a handshake with the
VFP. If the
handshake is successful, the ARU connects the call in Step 69140. If
unsuccessful, the ARU
plays an error message in Step 69142 and exits. The routines of Figs. 68K and
69L are
similar except for the service requested of the VFP and the contents of the
error message
played to the caller.
2o Fig. 69M depicts the ARU Send Page routine, which initiates a call to the
subscriber's paging
service. In Step 69150 the ARU prompts the caller to enter the telephone
number that should
be provided to the addressed pager. This prompt is repeated up to three times
until a callback
number is received. If no callback number after three prompts, the ARU
performs the-ARU
Guest Xfer to MOTC routine, which transfers the caller to the operator. This
permits a caller
without DTMF-enabled equipment by which to enter .a callback to provide the
number to an
operator who can enter it on his or her behalf. In Step 69158, the ARU plays a
recording to
the caller, enabling the caller to correct a number entered in error, or to
confirm that the
correct number has been entered. In Step 69160, the ARU places a call to the
subscriber's
paging service, using the data provided by the caller to indicate to the
paging service the
3o number to be displayed on the pager. If the call to the paging service is
successful, the ARU
plays a message indicating success in Step 69164 and disconnects in Step
69166. If the calf
to the paging service is unsuccessful, the ARU in Step 69162 plays a message
indicating the
381
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174 -
failure and returns, whereupon the ARU may optionally present the caller with
additional
options.
Fig. 69N depicts the ARU Alternate Routing routine. The ARU performs this
routine to
route calls that cannot be routed to the subscriber. If the subscriber has
indicated that such
unrouted calls are to be routed to his or her paging service, the ARU in Step
69170 plays a
recording indicating that the caller may send a page. The ARU then in Step
69172 performs
the ARU Send Page routine that has been described with respect to Fig. 69M. If
the page
was unsuccessful, the ARU plays a message indicating the failure and
disconnects the caller
in Step 69174. If the subscriber has indicated that unrouted calls are to be
routed to voice
mail, the ARU in Step 69173 plays a recording indicating that the caller may
leave a voice
mail message. If the subscriber's mailbox is not full, the ARU performs the
ARU Xfer to
Voice/Fax Guest Voice routine. If that routine returns, the attempt to leave
the voice mail
was unsuccessful, and the ARU plays a message indicating the failure and
disconnects the ._
caller in Step 69184. If the mailbox is full, the ARU plays a recording
informing the caller of
that condition and then disconnects the caller in Step 69184. If the
subscriber has indicated a
"guest option," the ARU in Step 69180 performs the ARU Alternate Routing Guest
Option
routine of Fig. 690; otherwise the ARU disconnects the caller in Step 69182.
2o Fig. 690 depicts the ARU Alternate Routing Guest Option routine. This
routine permits the
guest to select whether to leave a voice mail or send a page is the subscriber
is unreachable.
The ARU in Step 69190 presents the caller with a menu of available routing
options, here, ' I'
to leave a voice mail, and '2' to send a page. If the caller request to send a
page, then the
ARU in Step 69200 performs the ARU Send Page routine of Fig. 69M. If the Send
Page
routine fails, the ARU plays a diagnostic recording to the caller and
disconnects the caller in
Step 69202. If the caller requests to leave a voice mail, the ARU checks to
see whether the
subscriber mailbox is full. If the mailbox is not full, the ARU performs the
ARU Xfer to
Voice/Fax Guest Voice routine of Fig. 69K. If the routine returns, that
indicates that it was
not successful. In that case, or if the mailbox was full, the ARU plays a
prerecorded message
3o indicating that the voicemail could not be sent, and in Step 69195 prompts
the caller to
indicate whether he would like to send a page instead. If the caller selects
an option to send a
page, the ARU performs the ARU Send Page routing in Step 69200, as if the
caller had
382
CA 02279845 1999-OS-17
WO 98/230130 ' PCT/US97/21174
initially selected that option. If the ARU Send Page routine is not
successful, the ARU plays
a diagnostic message and disconnects the caller in Step 69202.
Fig. 69P depicts the main menu for the ARU User Call routine for processing a
call from a
subscriber. This routine is performed as Step 69052 in the ARU Guest Menu
routine as
depicted in Fig. 69D, if the caller enters a valid passcode. After playing an
introductory
welcome greeting, the ARU checks to see if the subscriber's mailbox is full.
If the mailbox is
full, the ARU plays a message informing the subscriber of this condition in
Step 69300.
After playing this warning, or if the mailbox is not fill, the ARU in Step
69302 plays a status
to recording informing the subscriber of the number of new voicemail messages
and fax
messages stored for the subscriber.
In Step 69304, the ARU plays a menu for the subscriber. In the example shown,
item ' 1'
corresponds to a request to change call routing; item '2' corresponds to a
request to send or
t 5 retrieve mai l; item '3' corresponds to a request to place a call; item
'4' corresponds to a
request for the administration menu; and item '0' corresponds to a request to
be transferred to
customer service.
If the subscriber selects the option to change call routing, the ARU in Step
69310 performs
2o the ARU Change Routing routine, described below with respect to Fig. 69T.
If the subscriber
selects the option to send and retrieve mail, the ARU plays a prerecorded
message asking the
subscriber to hold and then in Step 69312 performs the ARU Xfer to Voice/Fax
Subscriber
Send/Retrieve routine, described with respect to Fig. 69Q, below. If the
subscriber selects
the option to place a call, the ARU in Step 69314 presents the subscriber with
a menu
25 querying the type of call desired to be placed. If the subscriber responds
with an international
or domestic telephone number, or with a previously specified speed-dial number
corresponding to an international or domestic_telephone number, the ARU in
Step 69316
connects the call. If the subscriber requests operator assistance, the ARU in
Step 69318
performs the ARU User Xfer to MOTC routine to transfer the subscriber to the
operator. If
3o the subscriber cancels the call request, the ARU returns to Step 69304. If,
from the main
menu presented in Step 69304, the ARU performs the Administration routine,
described
below with respect to Fig. 69P. If the subscriber requests customer service,
the ARU
performs the ARU User Xfer to Customer Service routine of Fig. 69AH, described
below.
383
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
Fig. 69Q depicts the ARU Xfer to Voice/Fax Subscriber Send/Receive routine,
which
connects the subscriber to the VFP to send and retrieve voice mail messages.
The ARU
attempts to acquire a handshake with the VFP. If the handshake is successful,
the ARU
connects the call in Step 69330. If unsuccessful, the ARU plays an error
message in Step
69332 and exits.
Fig. 69R depicts the ARU Xfer to Voice/Fax Subscriber Send/Receive routine,
which
connects the subscriber to the VFP to manage the subscriber's distribution
lists. The ARU
attempts to acquire a handshake with the VFP. If the handshake is successful,
the ARU
connects the call in Step 69340. If unsuccessful, the ARU plays an error
message in Step
69342 and exits.
Fig. 69S depicts the ARU Xfer to Voice/Fax Subscriber Record Name routine,
which
connects the subscriber to the VFP to record the name that will be used in VFP-
originated
messages identifying the subscriber. The ARU attempts to acquire a handshake
with the VFP.
If the handshake is successful, the ARU connects the call in Step 69350. If
unsuccessful, the
ARU plays an error message in Step 69352 and exits. The routines of Figs. b9Q,
69R, and
69S are similar except for the service requested of the VFP and the contents
of the error
2o message played to the subscriber.
Fig. 69T depicts the ARU Change Routing routine, by which the subscriber
modifies the
routing options associated with his or her service. In Step 69390, the ARU
presents a menu
of options to the subscriber. If the subscriber selects the option for Find-Me
routing, the
ARU performs the ARU Change Find-Me Routing routine, described below with
respect to
Fig. 69U. If the subscriber selects the option for Override routing, the ARU
in Step 69400
plays a message indicating the subscriber's present overnde routing setting
and in Step 69404
presents the subscriber with a menu to select a new option. If the subscriber
selects a change
in option, the ARU performs, as Step 69408, the ARU Program routine to set the
override
option as specified, by passing the parameters of "override" and the selected
option. If the
subscriber selects the "Cancel" option, the ARU returns to Step 69390.
384
CA 02279845 1999-OS-17
wo 9sn3oso rc~r~s9~nm4
If, from the ARU Change Routing menu of Step 69390 the subscriber selects the
"Alternate
Routing" option, the ARU in Step 69409 plays a message indicating the
subscriber's present
alternate routing setting and in Step 69410 presents the subscriber with a
menu to select a
new option. If the subscriber selects a change in option, the ARU performs, as
Step 69414,
the ARU Program routine to set the alternate option as specified, by passing
the parameters of
"alternate" and the selected option. If the subscriber selects the "Cancel"
option, the ARU
returns to Step 69390.
If, from the Change Routing menu of Step 69390, the subscriber selects the
"cancel and
1 o return" option, the ARU in Step 69412 returns to the user menu of Fig.
69P.
Fig. 69U depicts the ARU Change Find-Me Routing routine. In Step 69420, the
ARU checks
to see whether the subscriber's Find-Me routing is by schedule. If not, in
Step 69422, the
ARU plays a message indicating that the routing is set to attempt three
successive telephone
~ 5 numbers, and in Step 69424 performs the ARU Change 3-Number Sequence
routine, which is
described below with respect to Fig. 69V. If the subscriber's Find-me routing
is by schedule,
the ARU in Step 69426 plays a message indicating that the subscriber's Find-Me
routing is
currently set by schedule, and in Step 69428 presents the subscriber with a
Change Schedule
Routing menu. If the subscriber selects the option to change to 3-Number
routing, the ARU
zo in Step 69430 plays a-message that the routing is set to 3-Number sequence
and in Step
69432 performs the ARU Change 3-number Sequence routine of Fig. 69V. If the
subscriber
selects the Save and Continue option, the ARU in Step 69434 plays a message
that the
subscriber's Find-Me routing is set to routing by schedule, and in Step 69436
performs the
ARU Change Routing routine. Step 69436 and the ARU Change Routing routine are
also
25 performed if the subscriber selects the option to cancel and return.
Fig. 69V depicts the ARU Change 3-Number Sequence routine, which permits the
subscriber
to alter contents and order of the three alternate numbers used by the ARU
Find-Me routine
of Fig. 69E and 69F. In Step 69440, the ARU presents the subscriber with a
menu of
30 options. If the subscriber selects an option to change one of the three
telephone numbers, the
ARU in Step 69442 plays a recorded message indicating the current setting for
the number,
and then in Step 69444 performs the Program routine, passing to the routine a
parameter
identifying the number to be changed and indicating the POTS number to which
it is to be
385
CA 02279845 1999-OS-17
WO 98/23080 ' PCT/US97/Z1174
changed. The ARU then returns to Step 69440. If the subscriber selects an
option to review
the current settings, the ARU in Step 69446 plays a series of messages
disclosing the settings
for each of the three numbers. The ARU then returns to Step 69440.
If the subscriber selects an option to change the schedule routing, the ARU in
Step 69450
checks whether the subscriber is eligible for schedule routing. If so, in Step
69454 the ARU
plays a message indicating that the Find-Me routing is set to the subscriber's
schedule and in
Step 69456 toggles the schedule setting to enable it. After toggling the
setting, the ARU in
Step 69450 returns to the ARU Change Routing routine of Fig. 69T. If schedule
routing is
not an option for this subscriber, the ARU plays a diagnostic message
indicating that
schedule routing is not available and that the subscriber may contact Customer
Service to
obtain the option. The ARU then returns to Step 69440.
If the subscriber selects an option indicating cancel and return, the ARU
returns to the ARU
t 5 Change Routing routine of Fig. 69T.
Fig. 69W depicts the ARU Administration routine. In Step 69460, the ARU
provides the
subscriber with a menu of options. In the example shown, item ' 1 '
corresponds to a request
to maintain the subscriber's broadcast or speed-dial lists; item '2'
corresponds to a request to
2o record a greeting; and item '3' corresponds to a request to activate or
deactivate features. If
the subscriber requests list maintenance the ARU, in Step 69462 presents the
subscriber with
a menu of options. If the subscriber selects an option to maintain his or her
broadcast lists,
the ARU in Step 69464 performs the ARU Xfer to Voice/Fax Subscriber
Distribution Lists
routine of Fig. 69R. After performing that routine, the ARU in Step 69468
performs the
25 ARU Lists routine of Fig. 69W. If the subscriber selects the option to
maintain the speed-dial
list, the ARU in Step 69470 performs the ARU Change Speed-Dial Numbers routine
of Fig.
69X. If the subscriber selects an option to cancel and return, the ARU returns
to Step 69460.
If, in response to the menu presented in Step 69460, the subscriber selects an
option to record
3o greetings, the ARU in Step 69474 presents the subscriber with a menu of
options. In the
example depicted, item ' 1 ' corresponds to a request to modify the
subscriber's welcome
message; item '2' corresponds to a request to modify the name associated with
subscriber's
mailbox. If the subscriber selects the option to modify the welcome message,
the ARU in
386
CA 02279845 1999-OS-17
WO 983080 PCT/US97/21I74
Step 69476 performs the ARU Play Greeting routine of Fig. 69B to play the
current welcome
message, and in Step 69478 performs the ARU Change Greeting routine of Fig.
69Y. If the
subscriber selects an option to modify the mailbox name, the ARU plays a
message
requesting the subscriber to hold and in Step 69480 perform the ARU Xfer to
Voice/Fax
Subscriber Mailbox Name routine, described previously with respect to Fig.
69S. After
performing this routine, the ARU returns to Step 69474. If the subscriber) in
response to the
menu presented in Step 69474, indicates that the request to modify greetings
should be
canceled (e.g., by pressing the asterisk button), the ARU returns to Step
69460.
If, in response to the menu presented in Step 69460, the subscriber selects an
option to
activate or deactivate features, the ARU in Step 69484 performs the ARU
Feature Activation
routine, which is described below with respect to Fig. 69Z. If the subscriber
instead indicates
that the request to modify greetings should be canceled (e.g., by pressing the
asterisk button),
the ARU returns to the ARU User Menu routine, which is depicted as Step 69304
in Fig. 69P.
Fig. 69X depicts the ARU Change Speed Dial Numbers routine. In Step 69490, the
ARU
provides the subscriber with a menu of options corresponding to particular
speed dial
numbers. For example, item ' 1' corresponds to the first speed dial number,
item "2' -
corresponds to the second speed-dial number, etc., through item '9', which
corresponds to the
2o ninth speed-dial number. When the subscriber selects one of these options,
the ARU in Step
69492 plays a message indicating the current setting for the selected speed-
dial number. In
Step 69494, the ARU performs the ARU Program routine, described below with
respect to
Fig. 69AA, specifying parameters of "Spd_Dial n" to indicate the speed dial
number to being
programmed (where n is replaced by a digit corresponding to the number of the
addressed
speed dial button) and the POTS number to which the specified speed dial
number is to be
set. The ARU then returns to Step 69490. If the subscriber selects an option
(indicated in the
example as an asterisk) to cancel the Change Speed Dial Numbers request, the
ARU returns
to Step 69462 as depicted in Fig. 69W.
y 3o Fig. 69Y depicts the ARU Change Greeting routine. In Step 69500, the ARU
presents a
menu to the subscriber corresponding to available options. For example, item
'1' corresponds
to a request to record a custom greeting, and item '2' corresponds to a
request to use the
standard system greeting. If the subscriber selects the option to record a
custom greeting, the
387
CA 02279845 1999-OS-17
wo 9snn~oso Pcr~s9~nma
ARU in Step 69502 presents a menu of options related to the customized
greetings. In the
example shown, item ' 1 ' corresponds to a request to review the present
contents of the
subscriber's custom greeting and item '2' corresponds to a request to replace
the currently
recorded custom greeting with a new recorded custom greeting. The octothorp
('#')
corresponds to a request to save the contents of the greetings, and the
asterisk ('*')
corresponds to a request to cancel and return.
If the subscriber selects an option to review the present contents of the
subscriber's custom
greeting, the ARU in Step 69504 performs the ARU Play Temp Greeting routine,
previously
described with respect to Fig. 69C, and returns to Step 69502. If the
subscriber selects an
option to replace the currently recorded custom greeting with a new recorded
custom -
greeting, the ARU in Step 69506 prompts the subscriber to begin recording the
new greeting
and in Step 69506 records the new greeting. After recording the greeting, the
ARU returns to
Step 69502. After recording a greeting, a subscriber may request that the
newly recorded
~ s greeting be saved. If the subscriber selects saving the greeting, the ARU
in Step 69510 saves
the recorded greeting to disk, overwriting the previous contents of the
greeting file, and in
Step 69514 plays a message indicating that the new greeting has been stored.
After storing
the greeting, the ARU performs the ARU Administration routine previously
described with
respect to Fig. 69W. If, in response to the menu presented by the ARU in Step
69502, the
2o subscriber cancels the request to modify greetings, the ARU in Step 69518
performs the ARU
Greetings routine, previously described with respect to Fig. 69W.
If, in response to the menu presented in Step 69500, the subscriber selects an
option to use
the system greeting (i.e., a default greeting that does not identify the
subscriber), then the
25 ARU in Step 69520 erases any previously-recorded greeting and in Step 69522
plays a
prerecorded message that callers will now hear the system greeting instead of
a personalized
greeting. The ARU then returns in Step 69525 to the ARU Administration
routine,
previously described with respect to Fig. 69W. The ARU also returns in Step
69525 if the
subscriber selects an option to cancel and return.
Fig. 69Z depicts the ARU Feature Activation routine. In Step 69530, the ARU
presents a
menu to the subscriber corresponding to available options. For example, item
'1'
corresponds to a request to set the Call Screening option: item '2'
corresponds to a request to
388
CA 02279845 1999-OS-17
WO 98/23050 PCT/US97/21174
activate or deactivate a pager recipient; option '3' corresponds to an request
to set pager
notification; and option '4' corresponds to a request to activate or
deactivate an account. If
the subscriber selects the call screening option, the ARU in Step 69532 plays
a recording
indicating the current setting of the call screening option. In Step 69534,
the ARU presents
the subscriber with a list of options relating to call screening. In this
example, item '1'
corresponds to a request to select screening by ANI (telephone number) only;
item '2'
corresponds to a request to select screening by name only; item '3'
corresponds to select
screening by both AM and name; and item '4' corresponds to a request to turn
call screening
off completely. If the subscriber selects one of these options, the ARU in
Step 69536
I o performs the ARU Program routine, described below with respect to Fig.
69AA, passing it a
first parameter to indicate that the screening option is desired to be
altered, and a second
parameter indicating the value to which the option should be set. Following
Step 69536, the
ARU returns to Step 69530. Likewise, if the subscriber selects a cancel and
return option in
Step 69534, the ARU returns to Step 69530.
If the subscriber selects an option to activate or deactivate a pager, the ARU
in Step 69538
plays a recorded message indicating the new status of the pager notification
option. In Step
69540, the ARU toggles the current status of the pager option (i.e., enables
the option if it is
currently disabled, or disables the option on if it is currently enabled).
After the toggle, the
2o ARU returns to Step 69530.
If the subscriber selects the pager notification option, the ARU in Step 69542
plays a
recording indicating the current setting of the call screening option. In Step
69544, the ARU
presents the subscriber with a list of options relating to pager notification.
In this example,
item '1' corresponds to a request to select notification by pager only of
incoming voicemails;
item '2' corresponds to a request to select notification by pager only of
incoming faxes; item
'3' corresponds to select request to select notification by pager both for
incoming voicemails
and for incoming faxes; and item '4' corresponds to a request to turn call
pager notification
completely. If the subscriber selects one of these options, the ARU in Step
69546 performs
3o the ARU Program routine, described below with respect to Fig. 69AA, passing
it a first
parameter to indicate that the pager notification option is desired to be
altered, and a second
parameter indicating the value to which the option should be set. Following
Step 69546, the
389
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
ARU returns to Step 69530. Likewise, if the subscriber selects a cancel and
return option in
Step 69544, the ARU returns to Step 69530.
If the subscriber selects an option in Step 69530 to activate or deactivate
his or her account,
the ARU in Step 69550 plays a recorded message indicating the new account
status. In Step
69552, the ARU toggles the current status of the account option (i.e.,
activates the option if it
is currently deactivated, or deactivates the option on if it is currently
activated). After the
toggle, the ARU returns to Step 69530.
1 o If the subscriber in Step 69530 selects the cancel and return option, the
ARU returns to the
ARU Administration routine, described above with respect to Fig. 69W.
Fig. 69AA depicts the ARU Program routine, which is performed by the ARU to
set options
selected by the subscriber. As shown in Step 69560, the Program routine takes
as input two
15 parameters: Term Slot, which identifies the option whose value is being
altered, and Term,
whose value indicates the value to which the option addressed by Term_Slot is
being set. In
Step 69562, the ARU checks the type of value specified in Term. If the term
value is a POTS
identifier (i.e. a telephone number, such as a telephone number being
programmed into a
speed-dial number, as in Step 69494 in Fig. 69X), the ARU in Step 69564
prompts the
2o subscriber to enter a POTS number. If the subscriber enters a domestic or
international
number, or an option (' 1' in the example shown) to erase a previously stored
POTS value, the
ARU in Step 69566 plays a message indicating the new setting to which the
addressed slot
will be changed. In Step 69568, the ARU prompts the subscriber to correct the
number by
reentering a new number, to confirm the request, or to cancel the request. If
the subscriber
25 selects the option to correct the number, the ARU returns to Step 69564. If
the subscriber
confirms the request, the ARU in Step 69570 stores the Term parameter value as
the variable
addressed by the Term Slot parameter. If the subscriber cancels the request,
the ARU returns
to the calling routine in Step 69572. The ARU also returns to the calling
routine in Step
69572 if the subscriber selects a cancel option when prompted for a POTS
number in Step
30 ' 69564.
If the Term value is not a POTS identifier, the ARU in Step 69580 plays a
message that
informs the subscriber that the addressed option is about to be changed. In
Step 69582, the
390
CA 02279845 1999-OS-17
WO 98/230510 - PCT/US97/21174
ARU prompts the subscriber to confirm or cancel the request. If the subscriber
opts to
confirm the request, the ARU in Step 69584 stores the Term parameter value as
the variable
addressed by the Term_Slot parameter and returns to the calling routine in
Step 69572. If the
subscriber cancels the request, the ARU returns to the calling routine in Step
69572 without
storing the value.
Fig. 69AI depicts the ARU User Xfer to Customer Service routine. In Step
69592, the ARU
plays a prerecorded message to the subscriber asking the subscriber to hold.
In Step 69594,
the ARU then transfers the subscriber to customer service.
Fig. 69AB depicts the ARU Validate Guest Entry routine. This routine is used
by the ARU to
determine whether an attempt by a guest to use the VFl' guest facilities is
valid. The ARU
permits up to 3 attempts for the guest to enter his or her identification
information. For the first
two invalid attempts, the ARU, in Step 69610, returns a status that the guest
entry was invalid.
~ 5 On a third attempt, the ARU in Step 69615 performs the ARU Find-Me routine
of Figs. 69E and
69F. If a guest entry was received, the ARU in Step 69617 checks to see
whether a guest entry
was one of the available choices on the applicable menu. If not, the ARU in
Step 69620 plays a
recorded message that the guest entry option is not available. If this is the
third invalid entry, the
ARU in Step 69624 performs the ARU Guest Xfer to MTOC routine of Fig. 69H. If
it is the
2o first or second invalid entry, the routine in Step 69622 returns with an
indication that the guest
entry was invalid. If the ARU determines in Step 69617 that the guest entry
was a proper menu
option, it returns a valid status in Step 69626.
Fig. 69AC depicts the ARU Validate User Entry routine, which is used by the
ARU to validate
25 an attempt by a subscriber to use subscriber services of the VFP. If no
user entry is received, the
ARU in Step 69630 plays a diagnostic message that no entry was received. If an
entry was
received, the ARU checks in Step 69634 whether the menu to which the
subscriber was
responding includes an option for user entry. If so, the .ARU returns a valid
status in Step 69636.
If not, the ARU in Step 69638 plays a diagnostic message that that option is
not available. If
3o either no entry was received or the entry was not valid for the menu, the
ARU in Step 69632
checks to see whether this is the third failure to specify subscriber
information. If so, the ARU
in Step 69640 performs the ARU User Xfer to Customer Service routine of Fig
89AI. If this is
the first or second failed entry, the ARU returns an invalid status in Step
69642.
391
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97I21174
Fig. 69AD depicts the ARU Validate Passcode Entry routine, which is used by
the ARU to
authenticate a passcode entered by a subscriber. In Step 69650, the ARU checks
to see whether
the passcode enters matches the passcode for the specific subscriber. If so,
in Step 69652 the
ARU returns with a valid status. If the entry is not valid, the ARU in Step
69654 plays a
recorded message that the entry is not valid. The ARU allows two attempts to
specify a valid
passcode. In Step 69656, the ARU checks to see whether this is the second
attempt to enter a
passcode. If this is the second attempt, the ARU in Step 69660 performs the
ARU User Xfer to
Customer Service routine, which is described above with respect to Fig. 69AI.
If this is not the
1 o second-failure, the ARU in Step 69658 prompts the subscriber to enter a
valid passcode and
returns to Step 69650.
Fig. 69AE depicts the ARU Validate Completion routine, used by the ARU to
validate the entry
of a valid telephone number. In Step 69670 the ARU checks to see whether a
valid user entry
~ 5 had been received. If not, the ARU checks to see if this is the third
invalid entry attempted. If
not, the ARU in Step 69672 returns an indicator that no valid entry was
received. If this is the
third attempt, in Step 69674, the ARU plays a message and in Step 69676
performs the ARU
Xfer User to MTOC routine, which is described above with respect to Fig. 69H.
2o If a valid user entry was received, the ARU checks to see whether a
telephone number entered
begins with "011." If so, the ARU in Step 69680 performs the ARU Validate
International
Completion routine of Fig. 69AF. In Step 69682, the ARU checks to see whether
the domestic
terms flag has been set by the subscriber. If not, the ARU in Step 69684 plays
a diagnostic
message that domestic calls are not available, and proceeds to Step 69671. In
Step 69686, the
25 ARU checks to see whether a ten-digit number was entered, and in Step 69688
checks to see
whether a valid MPA-Nxx number was entered. If number entered was not a ten-
digit valid
MPA-Nxx number, the ARU in Step 69690 plays a diagnostic message and proceeds
to Step
69671. In Step 69690, the ARU checks to see whether NADP blocking is effective
for this
subscriber, and in Step 69692, the ARU checks to see whether 976 blocking is
effective for this
30 subscriber. If either blocking is effective, the ARU in Step 69694 plays a
diagnostic message
indicating that calls to the addressed number are blocked and proceeds to Step
69671.
Otherwise, the ARU in Step 69696 returns with a status that the number entered
is valid.
392
CA 02279845 1999-OS-17
WO 98/23080 PCT/I1S97/21174
Fig. 69AF depicts the ARU Validate International Completion routine. In Step
69700, the
ARU checks to see whether the subscriber is configured to place international
calls. If not,
the ARU plays a diagnostic message in Step 69702. In Step 69704, the ARU
checks to see
whether the number entered is syntactically valid as an international dialing
number. If not,
the ARU in Step 69706 plays a diagnostic message. In Step 69708, the ARU
checks to see
whether Cset blocking will block the specified number. If so, the ARU in Step
69710 plays a
diagnostic message. If no error conditions were found, the ARU returns a valid
status in Step
69712. If errors were found the ARU in Step 69713 returns an invalid status.
If three failed
attempts have been made to enter a number, the ARU plays a status message in
Step 69714
to and transfers the subscriber to the operator in Step 69716.
Fig. 69AG depicts the ARU Validate POTS Programming routine, used by the ARU
to ensure
that only a valid telephone number is stored for use by call routing. In Step
69720 the ARU
checks to see whether a valid user entry had been received. If not, the ARU
checks to see if this
15 is the third invalid entry attempted. If not, the ARU in Step 69722 returns
an indicator that no
valid entry was received. If this is the third attempt, in Step 69676 performs
the ARU User Xfer
to Customer Service routine, which is described above with respect to Fig.
69AI.
If a valid user entry was received, the ARU checks to see whether a telephone
number entered
2o begins with "0I 1." If so, the ARU in Step 69730 performs the ARU Validate
International
Completion routine of Fig. 69AF. In Step 69732, the ARU checks to see whether
the domestic
terms flag has been set by the subscriber. If not, the ARU in Step 69734 plays
a diagnostic
message that domestic calls are not available, and proceeds to Step 69721. In
Step 69736, the
ARU checks to see whether a ten-digit number was entered, and in Step 69738
checks to see
25 whether a valid MPA-Nxx number was entered. If neither was entered, the ARU
in Step 69740
plays a diagnostic message and proceeds to Step 69721. In Step 6975(1, the ARU
checks to see
whether 976 blocking is effective for this subscriber. If'so, the ARU in Step
69754 plays a
diagnostic message indicating that calls to the addressed number are blocked
and proceedsto
Step 69721. Otherwise, the ARU in Step 69756 returns with a status that the
number entered is
3o valid.
Fig. 69AH depicts the ARU Validate International Programming routine used by
the ARU to
assure that only a valid telephone number is stored for use by call routing.
In Step 69760, the
393
CA 02279845 1999-OS-17
WO 98/Z3080 PCT/US97/21174 -
ARU checks to see whether the subscriber is configured to place international
calls. If not,
the ARU plays a diagnostic message in Step 69762. In Step 69764, the ARU
checks to see
whether the number entered is syntactically valid as an international dialing
number. If not,
the ARU in Step 69766 plays a diagnostic message. In Step 69768, the ARU
checks to see
whether Cset blocking will block the specified number. If so, the ARU in Step
69770 plays a
diagnostic message. If no error conditions were found, the ARU returns a valid
status in Step
69772. If errors were found, the ARU in Step 69773 returns an invalid status.
If three failed
attempts have been made to enter a number, the ARU plays a status message in
Step 69774
and transfers the subscriber to the operator in Step 69776.
Figs. 70A through 70S depict automated console call flow charts showing
software
implementation of the directline MCI product described above and are useful
for a further
understanding of the invention. A console call flow differs from an ARU call
flow in that the
console, while automated, is manned by an individual who may act in response
to requests -,
I S made by a caller. This permits a caller without DTMF-enabled equipment to
utilize the
product. DTMF data provided by the caller will be processed, but the
availability of a human
operator permits many of the available operations to be performed without the
use of DTMF
input. Data may be provided by the caller by directly entering it on a keypad,
if any, or it
may be entered by the human operator in accordance with voice responses
provided by the
2o caller. -
Fig. 70A depicts the starting point for processing of an automated console
call into an
account. As a call initiates, it is assumed to be a guest call. If the account
is not currently
online, the automated console in Step 70010 plays a message indicating that
calls cannot be
25 accepted for the account. Unless the caller indicates to the operator that
he has a passcode,
the console in Step 70012 disconnects the call. If the caller provides the
operator with a
passcode, the operator in Step 70014 initiates the Console Validate Passcode
routine, which
is described below with respect to Fig. 74K.
3o If the account is currently online, the console checks to see whether the
subscriber has
indicated an override for incoming calls. If so, the console routes the call
to the operator in
Step 70018. If the caller is generating a fax tone, the console in Step 70024
performs the
Console Fax Tone Detected routine, described below with respect to Fig. 705.
If the caller
394
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
provides the operator with a passcode, the operator in Step 70026 initiates
the Console
Validate Passcode routine, which is described below with respect to Fig. 70K.
Otherwise, the
call is processed as an incoming call for the subscriber, and the console in
Step 70020
performs the Console Find Me routine, which is described below with respect to
Fig. 70BC.
The console supplies the ''override" parameter to the Console Find Me routine
invocation.
If override has not been specified, the console in Step 70030 presents an
audible menu to the
caller. In the example shown, item '1' corresponds to a request to speak to a
subscriber; item
'2' corresponds to a request to leave a voice mail message for a subscriber;
item '3'
corresponds to a request to send a fax to a subscriber:; and item '4'
corresponds to a request to
page a subscriber. In_addition, a subscriber may provide his or her passcode
to gain access to
the console as a subscriber.
If the caller requests to speak to a subscriber, the console in Step 70032
checks the schedule
~ 5 flags associated with the caller's profile. If the subscriber's profile
indicates a schedule, the
console in Step 69034 performs the Console Find Me routine of Figs. 70B and
70C, using
"Sched 1" as the parameter. If the subscriber's profile does not indicate a
schedule, the
console in Step 69036 performs the Console Find Me routine using "First" as
the parameter.
The Console Find Me routine is discussed in further detail with respect to
Figs. 70B and 70C,
2o below.
If the caller requests to leave a voice mail message, the console in Step
70040 performs the
Console Xfer to Voice/Fax Guest routine, described below with respect to Fig.
70E. If the
caller requests to send a fax, the console in Step 70042 performs the Console
Xfer to
25 Voice/Fax Guest w/ or w/out Annotation routine, describe below with respect
to Fig. 70F.
After performing this routine, the console returns to the guest menu in Step
70030. If the
caller requests to leave a voice mail message, the console in Step 70040
performs the Console
Send Page routine, described below with respect to Fig. 70G. After performing
any of the
routines of Steps 70040, 70042 or 70044, the console returns to the guest menu
in Step
30 70030.
If the caller provides a passcode, the console in Step '70046 performs the
Console Validate
Passcode routine, which is described with respect to Fig. 70K, below. If the
console detects a
395
CA 02279845 1999-OS-17
WO 98123080 PCT/US97/21I74 -
fax tone on the incoming call, the console in Step 70048 performs the Console
Fax Tone
Detected routine, which is described below with respect to Fig. 705.
Figs. 70B and 70C depict the operation of the Console Find Me routine. As
shown in Step
70060, the Console Find Me routine takes a single parameter Term_Slot, which
is set by the
caller and used by the console to choose among alternative courses of action.
If Term Slot is
set to "Find Me", this indicates that the console is to use the default method
of determining
the subscriber's current number. This value may be set, for example, for
overnde or default
processing. If the subscriber's profile includes schedule flags, the console
performs the
o Console Find Me routine using the Sched 1 parameter as shown in Step 70062;
if not, the
console performs the Find Me routine using the first telephone number in the
list of numbers
for the subscriber, as shown in Step 70061.
If Term_Slot is set to "Voicemail," the console plays a message to the caller
that the
subscriber has requested that the caller leave a voice mail message, and in
Step 70074
performs the Console Xfer to Voice/Fax Guest Voice routine, as depicted in
Fig. 70E. That
routine returns if unsuccessful, in which case a message is played indicating
that the caller
should try the call later, and the caller is disconnected in Step 70075.
2o If Term_Slot is set to "Pager," the console plays-a message to the caller
that the subscriber
has requested that the caller leave a request to page the subscriber. The
console then
performs the Console Send Page routine, which is described with respect to
Fig. 70G, below.
That routine returns if unsuccessful, in which case a message is played
indicating that the
caller should try the call later, and the caller is disconnected in Step
70066.
If Term_Slot is set to any POTS value (such as Schedl, Sched2, First, Second,
or Third) that
indicates that the subscriber has specified that incoming calls are to be sent
using the standard
telephone system, and the console has been directed to use the particular
scheduled or
selected telephone number. In Step 70070, the console performs the Console
Record Name
3o routine to acquire a digital recording of the caller's identification. The
Console Record Name
routine is described in detail with respect to Fig. 70H, below. The console in
Steps 70073
and 70075 plays an appropriate message for the caller (e.g., "Please hold
while I try to reach
396
CA 02279845 1999-OS-17
WO 98/Z3080 PCT/US97/21174
your party" on the first attempt, and "I am still trying to reach your party;
please continue to
hold" for subsequent attempts). _
If the call is answered by an individual, the console in Step 70072 performs
the Console
s Connect Call routine, which is discussed below with respect to Fig. 70D, to
connect the
caller. If the call is answered by an answering machine, the console in Step
70090 checks to
see whether the subscriber has requested that the console roll over to the
next alternative
number upon encountering an answering machine. If not, the console in Step
70094 connects
the call. If the subscriber has selected rollover, the console selects the
next number in rotation
to call and re-performs the Console Find Me routine using the newly-selected
number, as
shown in steps 70081, 70082 and 70083. -
If the line called is busy, or if no more numbers to check remain, the console
in Step 70074
performs the Console Alternate Routing routine of Fig. 70I.
Is
Fig. 70D depicts the Console Connect Call routine. I f the subscriber has not
requested call
screening, the console in Step 70100 connects the call to the subscriber. If
the subscriber has
selected call screening, the console in Step 70104 plays an informational
message to the
subscriber, identifying the caller by name and by ANI, if available. If the
subscriber opts to
2o take the call, the console in Step 70106 takes the caller off hold and in
Step 70108 plays a
message indicating that the call is being connected, which it performs in Step
70110. If the
subscriber declines to take the call, the console in Step 70114 takes the
caller off hold and in
Step 70118 plays a recording to the calling party indicating that it was
unable to reach the
subscriber and optionally prompting the caller to leave a voice mail message.
If no mailbox
2s is available, the console in Step 70119 plays a diagnostic message and
disconnects the caller
in Step 70120. If a mailbox is available and able to receive messages, the
console in Step
70128 performs the Console Xfer to VoicelFax Guest Voice routine of Fig. 70E.
After this
routine has been performed, the console in Step 70119 plays a message asking
the caller to
call back later, and disconnects in Step 70120.
Fig. 70S depicts the Console Fax Tone Detected routine. In Step 70130, the
console attempts
to acquire a handshake with the VFP. If the handshake is successful, the
console connects the
397
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
call in Step 70132. If unsuccessful, the console disconnects the caller in
Step 69132 and
exits.
Fig. 70E depicts the Console Xfer to Voice/Fax Guest Voice routine, which
connects the
s caller to the VFP to leave a voice mail message. The console plays a status
message in Step
70140 and checks to see whether the subscriber's mailbox is full in Step
70142. If the
mailbox is full, the console plays a diagnostic message in Step 70144 and
returns. If the
mailbox is not full, the console attempts to acquire a handshake with the VFP.
If the
handshake is successful, the console connects the call in Step 70146. If
unsuccessful, the
console plays an error message in Step 70148 and returns.
Fig. 70F depicts the Console Xfer to Voice/Fax Guest Fax w/ or w/out
Annotation routine,
which connects the caller to the VFP to transmit a fax. The console plays a
status message in
Step 70150 and checks to see whether the subscriber's mailbox is full in Step
70152. If the
1 s mailbox is full, the console plays a diagnostic message in Step 70154 and
returns. If the
mailbox is not full, the console attempts to acquire a handshake with the VFP.
If the
handshake is successful, the console connects the call in Step 70156. If
unsuccessful, the
console plays an error message in Step 70148 and returns. The routines of
Figs. 70E and 70F
are similar except for the service requested of the VFP and the contents of
the error message
2o played to the caller.
Fig. 70G depicts the Console Send Page routine, which initiates a call to the
subscriber's
paging service. In Step 70160 the console prompts the caller to provide the
telephone
number that should be provided to the addressed pager. In Step 70162, the
console plays a
2s status recording to the caller, asking him or her to hold while the page is
sent. If the page is
successfully sent, the console in Step 70164 plays a status message indicating
that the page
has been sent and in Step 70165 disconnects the call. If the call to the
paging service is
unsuccessful, the console in Step 70166 plays a message indicating the failure
and returns,
enabling the console to present the caller with additional options.
Fig. 70H depicts the Console Record Name routine. This routine is used to
record the name
of the caller if the subscriber has specified call screening, either by name
or by name and
ANI. If the subscriber has specified call screening by name of by name and
ANI, the console
398
CA 02279845 1999-OS-17
WO 98/23080 PCT/ITS97/21174
in Step 70170 prompts the caller to supply a name, and records the audible
response. If a fax
tone is detected during the recording process, the console in Step 70172
performs the Console
Fax Tone Detected routine; otherwise, the routine returns.
Fig. 70I depicts the Console Alternate Routing routine. The console performs
this routine to
route calls that cannot be routed to the subscriber. If the subscriber has
indicated that such
unrouted calls are to be routed to his or her paging service, the console in
Step 70180 plays a
recording indicating that the caller may send a page. If the caller elects to
send a page, the
console in Step 70182 performs the Console Send Page routine that has been
described with
to respect to Fig. 70G. If the page was unsuccessful, the console in Step
70185 plays a message
indicating the failure and disconnects the caller in Step 70184. If the
subscriber has indicated
that unrouted calls are to be routed to voice mail, the console in Step 70183
plays a recorded
message indicating that the caller may leave a voice mail message. If the
caller elects to
leave a voicemail, the console in Step 70186 performs the Console Xfer to
Voice/Fax Guest
Voice routine that has been described with respect to :Eig. 70E. If the
voicemail was
unsuccessful, the console in Step 70185 plays a message indicating the failure
and
disconnects the caller in Step 70184.
If the subscriber has indicated a "guest option," the console in Step 69190
performs the
2o Console Alternate Routing Guest Option routine of Fig. 70J; otherwise the
console plays a
diagnostic message in Step 69192 and disconnects the caller in Step 69194.
Fig. 70J depicts the Console Alternate Routing Guest Option routine. This
routine permits
the guest to select whether to leave a voice mail or send a page if the
subscriber is
unreachable. The console in Step 70200 presents the caller with a menu of
available routing
options; here, either to leave a voice mail or to send a page. If the caller
requests to send a
voice mail, then the console in Step 70202 performs the Console Xfer to
Voice/Fax Guest
Voice routine of Fig. 70E. If that routine returns a return code indicative of
an unsuccessful
event, then the console plays a prerecorded message indicating that the
voicemail could not
3o be sent, and in Step 70204 prompts the caller to indicate whether he would
like to send a page
instead. If the caller, in response to either the prompt of Step 70200 or the
prompt of Step
70204, requests to send a page, the console in Step 70206 performs the Console
Send Page
routine of Fig. 70G. If the Console Send Page routines returns (indicating the
page could not
399
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97rI1174
be sent), or if the caller declines to send a page in response to the prompt
of Step 70204, the
console plays a diagnostic message in Step 70208 and disconnects the caller in
Step 70209. -
Fig. 70K depicts the Console Validate Passcode Entry routine, which is used by
the console to
authenticate a passcode provided by a subscriber. In Step 70220, the caller is
prompted for a
passcode. In Step 70224, the console checks to see whether the passcode
provided matches the
passcode for the specific subscriber. If so, in Step 70226 the console
performs the Console User
Call routine, described below with respect to Fig. 70L. The console allows two
attempts to
specify a valid passcode. In Step 70228, the console checks to see whether
this is the second
failed attempt to provide a passcode. If this is the second attempt, the
console in Step 70232
informs the caller that the passcode is not valid, and offers to connect the
caller to customer
service. If the caller elects not to be connected to customer service, the
caller is disconnected in
Step 70234. If this is the first failed attempt, the console in Step 70230
prompts the subscriber
to provide a valid passcode and returns to Step 70224.
is
Fig. 70L depicts the Console User Call routine. In Step 70240, the console
checks to see
whether the subscriber's mailbox is full. If so, in Step 70242, the console
plays a warning
message to the subscriber. Regardless of whether the mailbox is full, the
console in Step
70244 plays a status message for the subscriber informing the subscriber of
the number of
2o voicemail messages and faxes in the mailbox. On Step 70246, the console
provides a menu
of options to the subscriber. In the example shown, option '1' corresponds to
a request to
send or retrieve mail; '2' corresponds to a request to place a call; and '3'
corresponds to a
request to exit. If the subscriber selects the option to send or retrieve
mail, the console in
Step 70248 plays a hold message and then performs the Console Xfer to
Voice/Fax
25 Subscriber Send/Retrieve routine of Fig. 70M. After that routine has
completed, the console
again returns to Step 70246. If the subscriber selects an option to place a
call, the console
performs the Console Outbound Calling routine, which is described below with
respect to
Fig. 70N. If the subscriber selects the Exit Programming option, the console
disconnects the
call.
Fig. 70M depicts the Console Xfer to Voice/Fax Subscriber Send/Receive
routine, which
connects the subscriber to the VFP to send and retrieve voice mail messages.
The console
attempts to acquire a handshake with the VFP. If the handshake is successful,
the console
400
CA 02279845 1999-OS-17
WO 983080 PCT/US97/2I174
connects the call in Step 70250. If unsuccessful, the console plays an error
message in Step
70252 and exits.
Fig. 70N depicts the Console Outbound Calling routine, by which a subscriber
may place an
outgoing call. In Step 70260, the console checks to see whether the subscriber
is configured
to place international calls. If so, the console in Step 70262 enables the
international call key,
enabling non-domestic calls to be made. In Step 70264, the subscriber is
prompted for a
telephone number. The console connects the subscriber to the outgoing call in
Step 70268.
Fig. 700 depicts the Console Validate Guest Entry routine. This routine is
used by the console
to determine whether an attempt by a guest to use the VFP guest facilities is
valid. The console
in Step 70270 checks to see whether a guest entry was one of the available
choices on the
applicable menu. If not, the entry is not accepted, and the console maintains
the same menu, as
shown in Step 70272. If guest entry is a proper menu option, the console
returns a valid status in
I5 Step 70274.
Fig. 70P depicts the Console Validate User Entry routine, which is used by the
console to
validate an attempt by a subscriber to use subscriber services of the VFP. The
console in Step
70280 checks to see whether user entry is one of the available choices on the
applicable menu.
2o If not, the entry is not accepted, and the console maintains the same menu,
as shown in Step
70282. If user entry is a proper menu option, the console returns a valid
status in Step 70284.
Fig. 70Q depicts the Console Validate Completion routine, used by the console
to validate the
entry of a valid telephone number. In Step 70292, the console checks to see
whether the
25 domestic terms flag has been set by the subscriber. If not, the console in
Step 70294 plays a
diagnostic message that domestic calls are not available, and in Step 70310
returns with an
indication that the number provided is not valid. In Step 70296, the console
checks to see
whether a ten-digit number was provided, and in Step 70298 checks to see
whether a valid
MPA-Nxx number was provided. If number provided was not a ten-digit valid MPA-
Nxx
3o number, was provided, the console in Step 70302 plays a diagnostic message
and in Step 70310
returns with an indication that the number provided is not valid. In Step
70304, the console
checks to see whether NADP blocking is effective for this subscriber, and in
Step 70306, checks
to see whether 976 blocking is effective for this subscriber. If either form
of blocking is
401
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/Z1174
effective, the console in Step 70308 plays a diagnostic message indicating
that calls to the
addressed number are blocked and in Step 70310 returns with an indication that
the number
provided is not valid. Otherwise, the console in Step 70312 returns with a
status that the number -
provided is valid.
Fig. 70R depicts the Console Validate International Completion routine. In
Step 70322, the
console checks to see whether the subscriber is configured to place
international calls. If not,
the console plays a diagnostic message in Step 70324 and in Step 70340 returns
with an
indication that the number provided is not valid. In Step 70326, the console
checks to see
to whether the number begins with the "011" prefix indicating an international
number, and in
Step 70327, the console checks to see whether the number provided is
syntactically valid as
an international dialing number. If the number does not begin with "011" or is
not
syntactically valid, the console in Step 70328 plays a diagnostic message and
in Step 70340
returns with an indication that the number provided is not valid.
is
In Step 70330, the console checks to see whether Cset blocking will block the
specified
number. If so, the console in Step 70332 plays a diagnostic message. If no
error conditions
were found, the console returns a valid status in Step 70334.
2o Implementation of the improved directline MCI product as described above
has the following
impacts on billing procedures. -
directlineMCI domestic Bill Type: 1 s
directlineMCI international Bill Type: 115
402
CA 02279845 1999-OS-17
WO 98/23080 - PCT/US97J21174
directlineMCI Call Types:
Call Call Description
Type
52 Transfer to Customer Service
138 User Call Completion
139 User Administration Call
140 Guest termination to programmed number
141 Guest termination to voicemail
142 Guest termination to billing number
(and defaults,
see below)
143 Pager termination
144 Message delivery
145 Guest termination to Fax
146 Guest termination to Inactive Account
147 User termination to voice i fax mail
178 Op Assist User Call Completion
179 Op Assist Guest Termination to programmed
number
336 Op Assist Guest Termination to Billing
number
337 Op Assist Guest Termination to voicemail
338 Op Assist Guest Termination to Pager
339 Op Assist Guest Termination to Fax
340 Op Assist User Termination to voice/fax
platform
Billing Detail Records and OSR's for billing, and SCAI messaging for
reorigination, are
populated as follows for the various directlineMCI Call Types:
Bill Type 1 I S is not applicable for BDR's generated by the VFP (Call Types
144); because
all these calls are originated at the VFP, they are all be billed as
domestically originated,
using Bill Type 15.
403
CA 02279845 1999-OS-17
WO 98/23080 PCT/LTS97/21174
Billable Call? N
Bill Type: I S OR I 15
Call Type: 146
Terminating Number: Blank
Billing Number Account number*
+
0000
Originating NumberOriginating
ANI
Termination Method02
Termination Status00**
Miscellaneous Account number
1
Miscellaneous
2
Miscellaneous
3
OSR-Only Flag N
OSR Entry Code 08
SCAI OIR Flag n/a
SCAI BNOA n/a
Account number refers to the user's
800/8xx access number
** Termination Status is suggested; other
values may be more appropriate
404
CA 02279845 1999-OS-17
WO ~~~ PCT/US97/21174 -
Billable Call N console
Billable Calt N
Bill Type: 15 OR 115
Call Type: 140 OR i42 Bill Type: 15 OR 115
Terminating : Blank Call Type: 179 OR 336
Number
Billing Number Account number Terminating : Blank
+ Number
0000 Billing Number Account number
+
Originating Originating 0000
Number ANI
Termination O1 Originating Originating
Method Number ANI
Termination 262 Termination O1
Status Method
Miscellaneous Account number Termination 262
1 Status
Miscellaneous Miscellaneous Account number
2 1
Miscellaneous Miscellaneous
3 2
OSR-Only Flag N Miscellaneous
3
OSR-Only Flag N
OSR Entry Code 08
OSR Entry Code 08
SCAI OIR Flag n/a --
SCAI BNOA n/a -SCAI OIR Flag n/a
SCAI BNOA n/a
A Guest
Disconnect
BDR
may
have
a
different
Call
Type,
depending
on at
what
point
in the
call
flow
the
disconnect
came
fi
405
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
Billable Call N Console
Billable Call N
Bill Type: 15 OR 115
Call Type: 141 Bill Type: I S OR I 15
Terminating : Blank Call Type: 337
Number
Billing Number Account number Terminating : Blank
+ Number
0000 Billing Number Account number
+
Originating Originating ANI 0000
Number
Termination O1 Originating Originating
Method Number ANI
Termination 262 Termination 01
Status Method
Miscellaneous Account number Termination 262
1 Status
Miscellaneous Miscellaneous Account number
2 1
Miscellaneous , Miscellaneous
3 2
OSR-Only Flag N Miscellaneous
3
OSR-Only Flag N
OSR Entry Code 08
OSR Entry Code 08
SCAI OIR Flag n/a
SCAI BNOA n/a SCAI OIR Flag n/a
SCAI BNOA n/a
406
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
Billable Call N ~ ~ console
Billable Call N
Bill Type: 15 OR 115
Call Type: 145 Bill Type: 15 OR 115
Terminating Number:Blank Call Type: 339
Billing Number Account number Terminating Number:
+ Blank
0000 Billing Number Account number
- +
Originating NumberOriginating 0000
ANI
Termination MethodO1 Originating NumberOriginating
ANI
Termination Status262 Termination MethodO1
Miscellaneous Account number Termination Status262
I
Miscellaneous Miscellaneous Account number
2 1
Miscellaneous Miscellaneous
3 2
OSR-Only Flag N Miscellaneous
3
OSR-Only Flag N
OSR Entry Code 08
OSR Entry Code 08
SCAI OIR Flag n/a
SCAI BNOA n/a SCAI OIR Flag n/a
SCAI BNOA n/a
407
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174 -
Billable Call N Console
BilIabIe Call N
Bill Type: 15 OR I 15
Call Type: 140 OR 142 Bill Type: 15 OR 11 S
Terminating Number: Blank Call Type: 179 OR 336
Billing Number Account number Terminating_Number: Blank
+
0000 Billing Number Account number
+
Originating NumberOriginating ANI 0000
Termination MethodO1 Originating Originating ANI
Number
Termination Status262 Termination O1
Method
Miscellaneous Account number Termination 262
1 Status
Miscellaneous Miscellaneous Account number
2 1
Miscellaneous Miscellaneous --
3 2
OSR-Only Flag N Miscellaneous
3
OSR-Only Flag N
OSR Entry Code 08
OSR Entry Code 08
SCAI OIR Flag n/a -
SCAI BNOA n/a -SCAI OIR Flag n/a
SCAI BNOA n/a
408
CA 02279845 1999-OS-17
wo 9srs3oso rcr~rs9~r~ma
Billable Call? N ~C_onsole --
Bi:llable Call? N
Bill Type: 15 OR 115
Call Type: 145 Bill Type: 15 OR 115
Terminating Number: Fax Routing Call Type: 339
Number Terminating Number: Fax Routing
Billing Number Account number Number
+
0000 Billing Number Account number
+
Originating Number Originating 0000
ANI
Termination Method 03 Originating Number Originating
ANI-
Termination Status 257 Termination Method 03
Miscellaneous 1 Account number Termination Status 257
Miscellaneous 2 Miscellaneous 1 Account number
Miscellaneous 3 Miscellaneous 2
OSR-Only Flag N Miscellaneous 3
OSR-Only Flag N
OSR Entry Code 08
OSR Entry Code 08
SCAI OIR Flag N
SCAI BNOA 7C SC'.AI OIR Flag N
SC:AI BNOA 7C
409
CA 02279845 1999-OS-17
WO 98/230 PCT/US97/21174
ciuest termW atoon to fax - Normal Guest termination to Fax - Normal
Billable Call? Y - Match/Merge Console
Billable Call? Y - Match/Merge
Bill Type: 15 OR 115
Call Type: 145 Bill Type: 15 OR 115
Terminating : Fax Routing Call Type: 339
Number
Number Terminating : Fax Routing
Number
Billing Number Account number Number
+
0000 Billing Number Account number
+
Originating Originating ANI 0000
Number
Termination 00 Originating Originating ANI
Method Number
Termination 257 Termination 00
Status Method
Miscellaneous Account number Termination 257
I Status
Miscellaneous Miscellaneous Account number
2 1
Miscellaneous Miscellaneous
3 2
OSR-Only Flag N Miscellaneous
3
OSR-Only Flag N
OSR Entry Code 90
OSR Entry Code 90
SCAI OIR Flag N
SCAI BNOA 7C SCAI OIR Flag N
SCAI BNOA 7C
410
CA 02279845 1999-OS-17
wo ~sn~oso rcrms~r~m4
Billable Call? Y - Match/Merge Billable Call? Y - MatchlMerge--
Bill Type: I S OR 115 Bill Type: 15 OR 115
Call Type: 141 Call Type: 337
Terminating Number: Voicemail Terminating Number: Voicemail
Routing Routing
Number Number
Billing Number Account number Billing Number Account number
+ +
0000 0000
Originating Number Originating Originating Number Originating
ANI ANI
Termination Method 00 Termination Method 00 -
Termination Status 257 Termination Status 257
Miscellaneous 1 Account number Miscellaneous 1 Account number
Miscellaneous 2 Miscellaneous 2
Miscellaneous 3 Miscellaneous 3
OSR-Only Flag N OSR-Only Flag N
OSR Entry Code 90 OSR Entry Code 90
SCAI OIR Flag N SC'.AI OIR Flag N
SCAI BNOA 7C SC'.AI BNOA 7C
411
CA 02279845 1999-OS-17
WO ~' PCT/US97/21174
Billable Call ? N ~ ~ Billable Call ? N
Bill Type: 15 OR 115 BiII Type: 15 OR 115
Call Type: 140 OR 142 Call Type: 179 OR 336
Terminating Terminating
Number: Blank Number: Blank
Billing NumberAccount number Billing Number Account number
+ +
0000 0000
Originating Originating ANI Originating Originating ANI
Number Number
Termination 02 Termination 02
Method Method
Termination 00 Termination 00
Status Status
Miscellaneous Account number Miscellaneous Account number
1 1
Miscellaneous Miscellaneous
2 2
Miscellaneous Miscellaneous
3 3
OSR-Only Flag N OSR-Only Flag N
OSR Entry Code 08 I I OSR Entry Code 08
SCAI OIR Flag n/a SCAI OIR Flag n/a
SCAI BNOA n/a SCAI BNOA n/a
412
CA 02279845 1999-OS-17
WO 98/"13080 PCT1I1S97/21174
Guest Term to Closin Message Guest Term to Closin~Message
- -
Voicemail handshake failure Voicemail handshake failure
(Console)
' Billable Call ? N Billable Call ? N
Bill Type: 15 OR 115 Bill Type: 15 OR I 15
Call Type: 14I Call Type: 337
Terminating Number: Blank Terminating Number: Blank
Billing Number Account number Billing Number Account number
+ +
0000 0000
Originating Number Originating Originating Number Originating
ANI ANI
Termination Method 02 Termination Method 02
Termination Status 00 Termination Status 00
Miscellaneous 1 Account number Miscellaneous 1 Account number
Miscellaneous 2 Miscellaneous 2
Miscellaneous 3 Miscellaneous 3
OSR-Only Flag N OSR-Only Flag N
OSR Entry Code 08 OSR Entry Code 08
SCAI OIR Flag n/a SC'AI OIR Flag n/a
SCAI BNOA n/a SCAI BNOA n/a
413
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
handshake failure handshake failure (Console)
Billable Call ? N Billable Call ? N
Bill Type: 15 OR 115 Bill Type: 15 OR 115
Call Type: 145 Call Type: 339
Terminating Terminating : Blank
Number: Blank Number
Billing Number Account number Billing Number Account number
+ +
0000 0000
Originating Originating ANI Originating Originating
Number Number ANI
Termination 02 Termination 02
Method Method
Termination 00 Termination 00
Status Status
Miscellaneous Account number Miscellaneous Account number
1 1
Miscellaneous Miscellaneous
2 2
Miscellaneous Miscellaneous
3 3
OSR-Only Flag N OSR-Only Flag N
OSR Entry Code 08 ~ ~ OSR Entry Code 08 __
SCAI OIR Flag n/a SCAI OIR Flag n/a
SCAI BNOA n/a SCAI BNOA n/a
414
CA 02279845 1999-OS-17
WU 98/23080 - PCT/US97IZ1174
Billable Call? Y - Match/Merge ~ ' Billable Call? Y - Match/Merge
Bill Type: 15 OR 115 Bill Type: 15 OR 11 S
Call Type: 142 Call Type: 336
Terminating : Billing number Terminating : Billing
Number Number number
Billing Number Account number Billing Number Account number
+ +
0000 0000
Originating Originating ANI Originating Originating
Number Number ANI
Termination 00 Termination 00
Method Method
Termination 257 Termination 257
Status Status
Miscellaneous Account number Miscellaneous Account number
1 I
Miscellaneous Miscellaneous '
2 2
Miscellaneous , Miscellaneous
3 3
OSR-Only Flag N OSR-Only Flag N
OSR Entry Code 90 ~ ' OSR Entry Code 90
SCAI OIR Flag N SCAI OIR Flag N
SCAI BNOA 7C SC'AI BNOA 7C
415
CA 02279845 1999-OS-17
W0 98/23080 PCT/US97/21174
Billable Call? Y - Match/Merge Console
Billable Call? Y - Match/Merge
Bill Type: 15 OR 1 I S
Call Type: 140 Bill Type: I S OR 115
Terminating Number: Programmed Call Type: 179
number
Billing Number Account number Terminating Number: Programmed
+
0000 number
Originating Number Originating Billing Number Account number
ANI +
Termination Method 00 0000
Termination Status 257 Originating Number Originating
ANI
,
Miscellaneous 1 Account number Termination Method 00
Miscellaneous 2 Termination Status 257
Miscellaneous 3 Miscellaneous 1 Account number
OSR-Only Flag N Miscellaneous 2
Miscellaneous 3
OSR Entry Code 90 OSR-Only Flag N
SCAI OIR Flag N OSR Entry Code 90
SCAI BNOA 7C
SCAI OIR Flag N
SCAI BNOA 7C
416
CA 02279845 1999-OS-17
WO gg~3pgp PCT/US97/21174 -
Billable Call? N
Bill Type: 15 OR 115
Call Type: - 140 OR 142
Terminating Transfer Routing
Number:
Number
Billing Number Account number
+
0000
Originating Originating ANI
Number
Termination 03
Method
Termination 257
Status
Miscellaneous Account number
1
Miscellaneous
2
Miscellaneous
3
OSR-Only Flag N
OSR Entry Code 08
SCAI OIR Flag N -
SCAI BNOA 7C
41'7
CA 02279845 1999-OS-17
WO 98/23080 _ P~~/pS97/Z1i74
I Billable Call? Y - BDR Only I I Billable Call? Y - BDR Only
Bill Type: 15 OR 115 Bill Type: 15 OR I 1
S
Call Type: 143 Call Type: 338
Terminating Terminating
Number: Pager Number: Pager
Routing Routing
Number Number
Billing Number Account number Billing Number Account number
+ . +
0000 0000
Originating Originating ANI Originating Originating
Number Number ANI
Termination 00 Termination 00
Method Method
Termination 257 Termination 257
Status Status
Miscellaneous Account number Miscellaneous Account number
1 1
Miscellaneous Miscellaneous
2 2
Miscellaneous Callback number Miscellaneous Callback number
3 3
OSR-Only Flag N OSR-Only Flag N
OSR Entry Code 08 OSR Entry Code 08
SCAI OIR Flag n/a SCAI OIR Flag n/a
SCAI BNOA n/a SCAI BNOA n/a
418
CA 02279845 1999-OS-17
WO 98/23080 PCT/US9?/211?4
User termination to voicemail User termination to voicemail
- messaee - messa~ze
retrieval retrieval ~Console~
Billable Call? Y - Match/Merge Billable Call? Y - Match/Merge
Bill Type: 15 OR 115 Bill Type: I S-OR I 15
Call Type: 147 Call Type: 340
Terminating Number: Voicemail Terminating Number: Voicemail
Routing Routing
Number Number
Billing Number Account number Billing Number Account number
+ +
0000 0(100
Originating Number -Originating Originating Number Originating
ANI ANI
Termination Method 00 Termination Method 00
Termination Status 257 Termination Status 257
Miscellaneous 1 Account number Miscellaneous 1 Account number
Miscellaneous 2 Miscellaneous 2
Miscellaneous 3 Miscellaneous 3
OSR-Only Flag N OSR-Only Flag N
OSR Entry Code 80 OSR Entry Code 80
SCAI OIR Flag Y SC:AI OIR Flag Y
SCAI BNOA 7C SC:AI BNOA 7C
419
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174 -
administration call
Billable Call? N
Bill Type: 1 S OR 11 S
Call Type: 147
Terminating : Voicemail Routing
Number
Number
Billing Number Account number
+
0000
Originating Originating ANI
Number
Termination 03
Method
Termination 257
Status
Miscellaneous Account number
1
Miscellaneous
2
Miscellaneous
3
OSR-Only Fiag N
OSR Entry Code 08 ~ -
SCAI OIR Flag Y
SCAI BNOA 7C
420
CA 02279845 1999-O5-17
wo 9sn3oso rcTrt~s9~mma
Billable Call? Y - Match/Merge ( I Killable Call? Y - Match/Merge
Bill Type: 15 OR 115 Bill Type: 15 OR 115
Call Type: 138 Call Type: 178
Terminating Customer Terminating Customer
Number: Number:
Input/Speed Input/Speed
Dial ANI Dial ANI
Billing Number Account number Billing Number Account number
+ +
0000 0000
Originating Originating ANI Griginating Originating
Number Number ANI
Termination 00 Termination 00
Method Method
Termination 257 Termination 257
Status Status
Miscellaneous Account number Miscellaneous Account number
1 I
Miscellaneous Miscellaneous
2 2
Miscellaneous Miscellaneous
3 3
OSR-Only Flag N OSR-Only Flag N
OSR Entry Code 80 ~ ~ GSR Entry Code 80
SCAI OIR Flag Y SCAI OIR Flag Y
SCAI BNOA 7C SCAI BNOA 7C
421
CA 02279845 1999-OS-17
PCT/ITS97/21174
Billable Call? N
Bill Type: 15 OR 115
Call Type: 139 _
Terminating : Blank
Number
Billing Number Account number
+
0000
Originating Originating ANI
Number
Termination 08
Method
Termination 257
Status
Miscellaneous Account number
1
Miscellaneous Programmed
2
information
Miscellaneous
3
OSR-Only Flag N
OSR Entry Code 08
SCAI OIR Flag n/a
SCAI BNOA n/a
422
CA 02279845 1999-OS-17
WO ~~ PCT/US97/211'14
Subscriber Disconnect - proQrammin~ Subscriber Disconnect - No choice
or at User
no choice at User Menu Menu (Console)
Billable Call? N Billable Call? N
Bill Type: I S OR 115 Bill Type: 15 OR I I S
Call Type: 139 Call Type: 340
Terminating Number: Biank Terminating Number: Blank
Billing Number Account number Billing Number Account number
+ +
0000 0000
Originating Number Originating Originating Number Originating
ANI ANI
Termination Method O1 Termination Method O1
Termination Status 262 Termination Status 262
Miscellaneous 1 Account number Miscellaneous 1 Account number
Miscellaneous 2 Programmed Miscellaneous 2 Programmed
information information
Miscellaneous 3 Miscellaneous 3
OSR-Only Flag N OSR-Only Flag N
OSR Entry Code 08 OSR Entry Code 08
SCAI OIR Flag n/a SCAI OIR Flag n/a
SCAI BNOA n/a SCAI BNOA n/a
423
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
Billable Call? N Console
Billable Call? N
Bill Type: 15 OR 1 I S
Call Type: 138 Bill Type: 15 OR 115
Terminating Number: Blank Call Type: 178
Billing Number Account number Terminating
+ Number: Blank
0000 Billing Number Account number
+
Originating NumberOriginating ANI 0000
Termination MethodO1 Originating Originating
Number ANI
Termination Status262 Termination O1
Method
Miscellaneous Account number Termination 262
I Status
Miscellaneous Programmed Miscellaneous Account number
2 1
information Miscellaneous Programmed
2
Miscellaneous information
3
OSR-Only Flag N Miscellaneous
3
OSR-Only Flag N
OSR Entry Code 08
OSR Entry Code 08
SCAI OIR Flag n/a
SCAI BNOA n/a SCAI OIR Flag n/a
SCAI BNOA n/a
424
CA 02279845 1999-OS-17
WO 98/23080 PCT/I1S97/21174
Billable Call? N B illable Call? N
Bill Type: 70 Bill Type: 15 OR 115
Call Type: 52 Call Type: 138
Terminating Number: Transfer Terminating Number: Transfer
Routing Routing
Number Number
Billing Number Account number Billing Number Account number
+ +
0000 OIJ00
Originating Number Originating Originating Number Originating
ANI ANI
Termination Method 03 Termination Method 03
Termination Status 257 Termination Status 257
Miscellaneous 1 Account number Miscellaneous 1 Account number
Miscellaneous 2 Miscellaneous 2
Miscellaneous 3 Miscellaneous 3
OSR-Only Flag N OSR-Only Flag N
OSR Entry Code 08 OSR Entry Code 08
SCAI OIR Flag N SCAI OIR Flag N
SCAI BNOA 7C SCAI BNOA 7C
The following are the new directlineMCI scripts for the automated response
unit (ARU),
referencing the corresponding call flow diagram on which they appear:
Call IV ARU Text
Flow Number Script
Diagram Number
All 73300011 Press 1.
73300022 Press 2.
73300033 Press 3.
425
CA 02279845 1999-OS-17
wo 9sn3oso rcr~rs9~nma
73300044 Press 4.
73300055 Press 5.
73300066 Press 6.
73300077 Press 7.
73300088 Press 8.
73300099 Press 9.
733001010 Press 0.
733001 11 Press *.
I
7330012I2 Press #.
1 7330101I01 I'm sorry, calls are not being accepted
at this time.
2 7330201201 Welcome to directlineMCI!
3 7330301301 To speak to your party ...
7330302302 To leave a voicemail message ...
7330303303 To send a fax ...
7330304304 To send a page ...
7330306306 Please hold while I transfer you to voicemail.
7330307307 I'm sorry, your party's mailbox is full
7330308308 Please hold to send a fax.
4 7330401401 Your party has requested that you leave
a voicemail message.
7330403403 Your party has requested that you send a
page.
7330404404 Please hold while I try to reach your party.
7330405405 am still trying to reach your party. Please
I continue to hold
7330406406 am unable to reach your party at this time.
I
6 7330408408 May I please have your name?
7330409409 Please hold while I transfer you to the
operator.
7 7330701701 You have a call from ...
7330702702 .. at ...
7330703703 .. an undetermined location.
7330704704 .. an international location.
8 7330801801 To accept the call ...
426
CA 02279845 1999-OS-17
PCT/US97/21174
7330802802 To send your caller to voicemail ...
7330803803 To have your caller try again later . ..
7330805805 Your caller will be asked to leave a voicemail
message.
7330806806 Your caller will be asked to try again later.
7330807807 I'm sorry, your caller has disconnected.
7330809809 Please try your call again later.
9 7330901901 I'm sorry, I am unable to access voicemail
at this time.
7330902902 I'm sorry, I am unable to access faxmail
at this time.
73310011001 Please enter your call-back number, followed
by the # sign.
73310021002 .. will be sent
73310031003 To re-enter your call-back number ...
73310041004 To continue ...
73310061006 No entry was received.
73310071007 Thank you. Your page has been sent.
73310081008 I'm sorry, I am unable to complete your
page.
73311011101 I was not able to reach your party.
11 73311021102 Please hold to send a page or try your call
again later.
12 73312071207 To send a page, press 1; or, please try
your call again later.
13 73313011301 Welcome to User Programming!
73313021302 Your mailbox is full. Please delete your
saved messages.
73313031303 You have ...
73313041304 .. new voicemail and , ..
73313051305 .. new fax messages.
73313061306 .. no ...
73313071307 To change your call routing ...
73313081308 To send or retrieve mail ...
73313091309 To place a call ...
73313101310 For account maintenance ...
73313111311 To reach customer service from any menu
...
427
CA 02279845 1999-OS-17
PCT/US97/21174
73313131313 Please hold to retrieve your voice and fax
messages.
73313141314 For a domestic call) enter the area code
and number.
73313151315 For an international call, enter 0 1 i and
the number.
73313161316 Please enter the phone or speed-dial number,
followed by the #
sign.
73313171317 For operator assistance
14 73314011401 I'm sorry, I am unable to access your voice/fax
mailbox at this
time.
73314031403 I'm sorry, I am unable to access your distribution
lists at this
time.
73314041404 I'm sorry, I am unable to record your mailbox
name at this time.
15 73315011501 To change Find-Me routing ...
733 1502 To change override routing . ..
i 502
73315031503 To change final routing ...
73315041504 To cancel and return to the previous menu
...
73315071507 Override routing is currently set to ...
73315081508 .. voicemail.
73315091509 .. pager.
73315101510 .. your Find-Me sequence.
73315121 S Your override routing is currently turned
12 off.
73315131513 To set override routing to a telephone number
...
73315141514 To set override routing to voicemail ...
73315151515 To set override routing to your pager ...
73315161516 To set override routing to your Find-Me
sequence ...
7331 1517 To turn off override routing ...
S 17
73315191519 Your final routing is currently set to ...
73315201520 .. the voicemail or pager option.
73315231523 .. a closing message.
73315251525 To set finalrouting to the voicemail or
pager option ...
73315261526 To set finalrouting to your voicemail ...
~ I
428
CA 02279845 1999-OS-17
WO 98/Z30S0 PCT/US97/21174 -
73315271527 To set finalrouting to your pager ...
73315281528 To set finalrouting to a closing message
...
16 73316011601 Your Find-Me routing is set to your schedule.
73316021602 Your Find-Me routing is set to your three-number
sequence.
73316041604 To change to your three-number sequence
...
73316061606 To save and continue ...
17 73317011701 To change your first number ...
73317021702 To change your second number ...
73317031703 To change your third number ...
7331 1704 To review all three numbers ...
704
73317051705 To change to schedule routing .. ,
73317081708 Your first number is set to ...
73317091709 Your second number is set to ...
73317101710 Your third number is set to ...
73317111711 Your second number is currently not programmed.
73317121712 Your third number is currently not programmed.
73317131713 You do not have a schedule set up at this
time. Please contact
customer service.
18 73318011801 To create or update your lists.
73318021802 To record your greeting or mailbox name
...
73318031803 To activate or deactivate features ...
73318061806 For broadcast lists ...
73318071807 For speed-dial numbers ...
73318081808 Please hold to update broadcast lists.
73318091809 For your personal greeting ...
73318101810 For your mailbox name ...
73318111811 Please hold to record your mailbox name.
73318121812 Your current greeting; is ...
19 73319011901 To change speed-dial number ...
73319111911 Speed-dial number ...
429
CA 02279845 1999-OS-17
WO 98/23080 - PCT/US97/Zll'74
73319121912 .. is set to ...
73319131913 .. is currently not programmed.
73319141914 To record a new greeting ...
73319151915 To use the system greeting ...
73319161916 Begin recording after the tone.
73319171917 To review your greeting ...
73319181918 To re-record your greeting ...
73319211921 Your callers will now hear the system greeting.
73319221922 Your new greeting has been saved.
20 73340004000 To set caller-screening ...
733400 4001 To activate or deactivate your pager ..
i .
73340024002 To set pager notification ...
73340034003 To activate or deactivate your account ...
73340054005 Caller-screening is set to ...
73340064006 Caller-screening is currently turned off.
73340074007 .. number only.
73340084008 .. name only.
73340094009 .. name and number.
73340104010 To set caller-screening to number only ...
73340114011 To set caller=screening to name only ...
73340124012 To set caller-screening to name and number
...
73340134013 To turn off caller-screening ...
733401 4015 Your callers will be given the option to
S page you.
73340164016 Your callers will not be given the option
to page you.
73340174017 Your account has been activated.
73340184018 Your account has been deactivated.
73340194019 You are currently being paged for ...
73340204020 .. new voicemail messages.
73340214021 .. new fax messages.
73340224022 .. new voicemail and fax messages.
73340234023 Pager notification is currently turned off.
1
430
CA 02279845 1999-OS-17
PCT/US97/21174
73340244024 To be paged for voicemail messages ...
73340254025 To be paged for fax messages ...
73340264026 To be paged for voice: and fax messages
...
73340274027 To turn off pager notification ...
21 73341014101 For a domestic number, enter the area code
and number.
73341024102 For an international number, enter 0 1 1
and the number.
73341034103 To erase this number ...
73341054105 To re-enter the number ...
73341074107 Your override routing; will be deactivated.
73341084108 Your override routing will be changed to
...
7334111411 Please hold for customer service.
I
73341124112 Your finalrouting will be changed to ...
73341164116 Your first number will be changed to ...
73341174117 Your second number will be erased.
73341184I Your second number will be changed to ...
18
73341194I Your third number will be erased.
19
73341204120 Your third number will be changed to ...
73341214121 This speed-dial number will be erased.
73341224122 This speed-dial number will be changed to
...
73341234123 Your caller-screening will be turned off.
73341244124 Your caller-screening will be changed to
... -
73341284128 Your pager notificatian will be turned off.
73341294129 You will be paged for ...
22 7330309309 That option is not available.
23 7330102102 That entry is invalid.
7330103103 Please re-enter your passcode. -
24 73344014401 I'm sorry, domestic calls are not available.
73344034403 I'm sorry, calls to that number are blocked.
25 73325012501 I'm sorry, international calls are not available.
26 73326012601 I'm sorry, you may not program a domestic
number.
431
CA 02279845 1999-OS-17
WO 98/23080 PCT/US9~/21174 -
32701 2701 ~I'm sorry, you may not program an i
The following are the new directlineMCI scripts for the Console Application:
Call Console Text
Flow Script
DiagramNumber
1 14160 Welcome to directlineMCI
Calls are not currently being accepted on
this account
{Courtes, Close}
22008 MCIOperator!
How may I help you reach your party?
22005 MCIOperator!
{Press User Prog if caller is account owner}
2 22033 Your party has requested that you leave
a voicemail message;
please hold
{ Procedure Cal l }
22034 Your party has requestedthat you send a
page
{ Procedure Cal l }
22037 Please try your call agair~iater
{Courtesy Close}
3 22031 Please hold while I try to reach your party-
{ Procedure Call }
15848 MCIOperator!
Please hold while I try to reach your party
{ Proc Call }
15844 am still trying to reach your party; please
I continue to hold
{ Proc Call }
432
CA 02279845 1999-OS-17
PCT/US97/21174
15849 MCIOperator!
I am still trying to reach your party; please
continue to hold
{Proc Call}
33000 {Press YES if answered, BUSY if busy, NO
if no answer after 4-
5 rings, ANS MACH for Answer Machine.
4 22036 This is the MCI Operator.
You have a call from NAME and/or ANI; would
you like to
speak to your caller?
15845 I'm sorry, I'm unable to reach your party
at this time
{ Proc Call }
22032 Thank you; your call is connected
{Proc Call}
7115 Please hold while I transfer you to voicemail
{Proc Call}
22900 I'm sorry, your party's voice mailbox is
full
{ Procedure Call }
22104 'm sorry, I'm unable to access voicemail
I at this time
{Procedure Call}
22340 Please hold to send a fax
{Procedure Call}
22105 'm sorry, I'm unable to access faxmail at
I this time
{ Procedure Call }
6 15865 What callback number would you like to send?
15866 MCIOperator!
What callback number would you like to send?
22375 ease hold while your page is sent
--
{Procedure Call}
15863 Your page has been sent. Thank you!
{Disconnect}
15693 'm sorry; I'm unable to complete your page
I
{ Procedure Call }
433
CA 02279845 1999-OS-17
WO 98/Z3080 PGT/US97/211'14
22035 What is your name, please?
7 15860 I'm sorry, I'm unable to reach your party
at this time; would you
like to send a page?
22040 Would you like to send a page?
15842 I'm sorry, I'm unable to reach your party
at this time; please try
your call again later
{Courtesy}
8 22038 I'm sorry, I'm unable to reach your party
at this time; would you
like to leave a voicemail message, or send
a page?
9 22003 May I please have your passcode?
22102 Please repeat your passcode
22017 I'm sorry; that is not a valid passcode
{Offer Customer Service or disconnect}
22901 Your mailbox is full; please delete your
saved messages
{ Procedure Call }
22902 You have X new voicemail and Y new fax messages
{ Procedure Call }
22400 How may I help you?
22904 Please 'hold for your voice and fax messages_
{Procedure Call}
11 22905 I'm sorry; I'm unable to access your voice
/ fax mailbox
{ Procedure Call }
22906 What number do you wish to dial?
{Enter number or 1-digit Speed Dial number}
22908 MCIOperator!
What number do you wish to dial? -
{Enter number of 1-digit Speed Dial number}
22907 Thank you; please hold while your call is
connected
{ Procedure Cal l }
13 15063 'm sorry; domestic termination are not available
I
{Procedure Call}
434
CA 02279845 1999-OS-17
w° rc°r~rs~nma
15053 I'm sorry ; that is not a valid domestic
number
{ Procedure Call }
15057 I'm sorry; calls to that number are blocked
{Procedure Call}
14 15061 I'm sorry; international termination are
not available
{Procedure Call}
15051 I'm sorry ; that is not a valid in(ernational
number
{Procedure Call}
16001 (Press GEN ASST to process a No D-Dial Call1
ARU impacts are described in detail below, as well as in the call flow
diagrams.
User input
In general, throughout the call flow, at every opportunity for user/caller
input, the possibility
of response delay is minimized as much as possible. Following are some
examples:
During 'guest' portion of the call, the subscriber may enter '*', at which
time the NIDS
Audio Server (NAS) begins to collect 6 passcode digits, applying an inter-
digit timeout.
During playing of the Guest Menu, a single key pressed results in an immediate
response,
unless the key pressed is the '*' key, at which point the NAS collects six
passcode digits
_ ~ 0 During playing of any User Menu, a single key pressed results in an
immediate response,
except in the Outbound Call menu. Because a domestic telephone number, an
international
telephone number, or a Speed Dial number can be entered here, the system
allows the user to
press '#', which indicates the end of dialed digits. The '#' is accepted
whether it's entered
following a single digit entry or a string of digits, i.e. a telephone number.
At any place in the call flow where the user is able to enter a domestic or
international
number, the '#' key must be accepted to indicate the end of dialed digits.
This includes
- during programming of the First, Second or Third Find-Me numbers, Override
Routing to
POTS and Speed Dial numbers.
435
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
Where possible. the ability for the user to 'power dial' is built into the
call flow-. This means
that , in the event that multiple keys are pressed, scripting is bypassed and
the appropriate
menu is reached.
One access method is supported for directlineMCI in this embodiment: 800/8xx
number
access, with no PIN. The PIN field in the database is defaulted to 0000.
Billed Number Screening (Fraud) Validation
All directlineMCI calls received are subject to a Billed Number Screening
validation, to
verify that the number has not been tagged as a Fraud risk. The lookup is into
Category S,
Type 0; the flag checked is the Credit Card (Hot) flag. In the event that the
number has been
'shut down', i.e. the Hot flag is set to 'Y', the application treats the call
as an off line
account, but does not allow a subscriber to access programming options.
WorldPhone
Callers are able to access the directlineMCI platform via WorldPhone. In a
preferred
embodiment, these calls arrive at the directline platform with a pseudo-ANI in
the
~ 5 Originating Number field of the SCAI message. This pseudo-ANI is
associated with the
specific Feature Group A (FGA) circuit on which the WorldPhone call extension
was
launched. In another embodiment, the true originating country information is
forwarded to
the directline platform; the Originating Number field is populated with the 3-
digit Country
Code.
2o In a preferred embodiment, the WorldPhone-originated directline call is
billed as follows:
Calls originating via WorldPhone, and arriving at the directline platform with
a pseudo-ANI
as the origination, are billed as domestic, using Bill Type 15. The
Originating Number field
in the BDR is the FGA pseudo-ANI.
In another embodiment, the call is billed as follows:
25 The ARU and Console implement code to identify whether the Originating
Number field _
contains a pseudo-ANI or true origination information. If the true Country
Code origination
information is provided, the application refers to its configuration files,
where a WorIdPhone
pseudo-ANI is an optional entry. The existence of this item in the
configuration file indicates
to the application how the call should be billed.
436
CA 02279845 1999-OS-17
WO 9~'Z30~80 PCT/pS97/21174
If the application finds a WorldPhone pseudo-ANI in its config file, the call
is billed as
domestic, using Bill Type I5. The Calling Number in the BDR is set to that
WorldPhone
pseudo-ANI, and the application instructs the bridging switch to change its
Originating
Number to that same pseudo-ANI.
If the application does not find the WorIdPhone pseudo-ANI in its config file,
the call is
billed as international, using Bill Type 1 I S, and the Originating Number
information is
retained in the switch record. The BDR is populated with a 10-digit string: '
191 ' + 3-digit
Country Code + '0000'.
Guest call routing is prescribed by the directlineMC1 subscriber in several
ways, as described
in the following paragraphs:
Blocking checks for guest termination, based on origination, are included
below.
Call Routing
Two options are provided to the user in defining Call Routing: the Find-Me
sequence, and
~ 5 the Schedule sequence. With the exception of Schedule definition, the user
has the ability to
define Call Routing via DTMF.
3-Number Find-Me Sequence
If the user has chosen the Find-Me sequence for his C'.all Routing, the
application launches a
call to the user's Primary (First) programmed number. If a live answer is
received, the guest
2o caller is connected with the answering party. Call screening, described
below, may be
active, in which case the answering party must actively a;:cept the call
before it is connected.
If the line at the First number is busy, the call is routed to the user's
programmed Alternate
Routing, described below. If no answer is detected after a configurable time,
the application
launches a call to the user's Secondary (Second) programmed number.
2s Answer treatment at the Second number is the same as for a call attempt to
the First number
with no answer resulting in a call attempt to the user's Tertiary (Third)
number. Answer
treatment at the Third number is the same, with no answer resulting in
Alternate Routing.
If, at any point in this calling sequence, a termination slot is not
programmed, the application
skips that number in the sequence, and proceed to the next number, or
Alternate Routing.
437
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
For any programmed international termination, the application looks up the
terminating
country code in the Country Code tables. If the Direct Dial Country flag is
set to 'Y' for that _
country, the ARU transfers the call to the manual console (TTC =1 e) for
processing.
2-Level Schedule Sequence
s If the user has chosen the Schedule sequence for his Call Routing, the
application takes the
Schedule 1 Trans and Schedule 2 Trans fields to use as keys into the 800
Translation database
to retrieve schedule information. From the user's two schedule translations,
and using the
current day and time, the First and Second Schedule numbers are determined.
A call is launched to the First Schedule number, and answer treatment is as
described in the
Find-Me sequence, with no answer resulting in a call attempt to the Second
Schedule number.
Answer treatment at the Second Schedule number is the same, with no answer
resulting in
Alternate Routing.
Again, if at any point in the Schedule calling sequence, a tewminating number
cannot be
found, the application skips that slot in the sequence, and proceeds to the
next number, or
~ s Alternate Routing.
The user's schedule is set up during Order Entry, and is not user-updatable
via DTMF. At
Order Entry, the user is asked to define his schedule by Date, Day of Week,
Time of Day (in
30 minute increments), and by Time Zone.
Override Routing
2o The option is available, via DTMF, for the user to disable the presentation
of the Guest Menu
by prescribing specific routing for all guest callers. Via Override Routing,
the user is able to:
route callers to a single telephone number, have callers leave a voicemail
message, have
callers page him, or route callers through his programmed Call Routing (Find-
Me or
Schedule).
2s If the user has programmed Override Routing to route to a telephone number,
no answer at
that number results in Alternate Routing treatment.
Alternate Routing
Alternate Routing allows the user to define, via DTMF, the treatment of a
caller for whom an
attempt to reach the subscriber has been made, but no answer was received.
Alternate
438
CA 02279845 1999-OS-17
WO 98/080 PCT/US97/21174
Routing options include Voicemail, Pager, Closing Message, or the Guest Option
of
Voicemail or Pager. The default for Alternate Routing, if not programmed, is
the playing of
- the Closing Message.
- - Default Routing
The user is able to prescribe at Order Entry the treatment for a caller who,
when presented the
Guest Menu, does not respond after two attempts. The Default Routing options
are: a
transfer to the Operator (TTC = 67), where the Guest menu is presented again,
a telephone
number, with no answer resulting in Alternate Routing, Voicemail, or Call
Routing (Find-Me
or Schedule). The default for Default Routing, if it's not programmed, is the
Operator
to transfer.
Call Screening
The user may choose to have Call Screening invoked, to announce all guest
callers. Call
Screening options include pre-programming of Name Only, ANI Only, Name and
ANI, and
No Call Screening. The user has the ability to program Call Screening via
DTMF.
~5
When Name Only or Name and ANI screening is programmed, the caller's name is
recorded
If the caller does not respond to the prompt, and nothing is recorded, the
system will default
to ANI Only screening. When an answer is received at a terminating telephone
number, the
caller's Name and/or ANI is played and the answering party is asked to accept
or reject the
2o call. If the call is accepted, the caller is connected. If Caller Screening
includes ANI
screening, and the originating number is a Country Code, the scripts '... an
international
location' will be played in place of the ANI.
If the call is rejected, or no response is received from the answering party,
the caller is asked
to leave a voicemail message, or the Closing Message; is played, if the user
has not subscribed
25 to Voicemail.
Timeout Parameters
Timeout values are defined, in seconds, in the directlineMCI database for the
following
termination:
439
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
For this termination: Use this timeout
value:
First Find-Me Primary Timeout
Second Find-Me Secondary
Timeout
Third Find-Me Tertiary Timeout
Schedule 1 Primary Timeout
Schedule 2 Secondary
Timeout
Override Routing, if Override Timeout
telephone
number
Default Routing, if Default Timeout
telephone
number
These timeout values are defaulted to 25 (seconds), but the user is allowed to
change them
via Customer Service.
Call Connection times
Call connection delays, when a guest call to a programmed termination is
completed, are
minimized as much as possible.
Answer detection
For all call attempts to a telephone number, treatment on detection of an
answering machine
is defined by the Roll on Machine Detect flag (State flag, bit 9). If this
flag is set to 'N', the
1 o caller is connected to the answering machine . If the flag is set to 'Y',
the application routes
to the next number in the calling sequence or Alternate Routing.
Current answer detection performance on the ISN is as follows: The NAS
correctly detects a
live answer at 99% reliability; a machine is correctly detected at 67%
reliability.
For any Answer Detection responses not addressed specifically in this
requirement, Fast-
Busy for example, treatment is as described for a No Answer condition.
440
CA 02279845 1999-OS-17
PGT/US97/21174 -
Prosrammed Number Validation
The user has the ability to program a telephone number in his First, Second,
and Third Find-
Me numbers, and Override Routing. Before a number is accepted for programming,
the
application makes the following validation checks:
Domestic numbers
The Domestic Terms flag (PIN bit 1 ) is examined to ensure that the user is
authorized to
program a domestic number
The International Blocking database is queried, using Category 000, Type 002,
and the
programmed NPA, looking for a pattern match, to ensure that the programmed
number is not
a blocked Information/Adult Services number.
The Exchange Master is examined to determine whether the termination is an
NADP number.
If so, Country Set blocking is applied. The Pseudo-Country Code (PCC)
associated with the
programmed number is validated against the Country Set found in the
directlineMCI Property
Record. If that PCC is blocked, programming to that number is not allowed.
International numbers.
The International Terms flag (PIN bit 2) is examined 1:o ensure that the user
is authorized to
program a international number.
The Country Set from the directlineMCI Property Record is retrieved, and the
application
verifies that the programmed Country Code is not blocked for that Country Set.
Blocking checks for programming guest termination are included below.
The Call Flow diagram depicts the various situations for which a transfer to
the Voice/Fax
Platform (VFP) is necessary. A transfer is implemented using the routing
number in the
Voicemail Route Number field of the customer record.
- In order to 'mask' some of the delay in call extension to the VFP) the call
is extended before
the 'please hold' script is played to the caller. Call extension delay is
reduced additionally by
removing inter-digit timeouts, as described previously. After launching a call
and playing the
441
CA 02279845 1999-OS-17
WO 98/23080 - PCTlUS97/21174
script, the application awaits answer detection, at which time the user's
directlineMCI access
number (800/8xx number) is out-pulsed to the VFP, followed by a '*', then a
single mode
digit, which indicates to the VFP the type of transfer to process, followed by
a '#'. The mode
indicator is one of the values, described in the table that follows. To ensure
that the
information has been received and validated by the VFP, the application awaits
th;, playing of
two DTMF '00' tones from the VFP, then the caller is connected.
Mode Transfer type
indicator
1 Guest voicemail
2 Guest fax with voice
annotation
3 Guest fax without
annotation
4 User voice/fax retrieval
5 User list maintenance
6 User recording of mailbox
name
A VFP transfer attempt is considered failed if two handshake attempts have
failed. If a Guest
a 0 transfer to voice or faxmail fails during Override, Default, or Alternate
Routing, the guest
caller is asked to try his call again later. If a Guest transfer fails on a
Guest Menu choice, the
menu will be presented again. If a user transfer to voice or faxmail fails, a
script will be
played, informing the user of the failure, and the user is returned to the
previous menu.
A guest fax transfer without annotation occurs when, at the outset of the
call, fax tone is
detected. Fax tone detection is independent of the presentation of the welcome
message, so -
the length of the greeting has no effects on the reliable detection of fax
tones.
442
CA 02279845 1999-OS-17
WO 98/23080 PGT/US9'1/21174 -
When a user accesses User Programming, the application presents the count of
new voicemail
messages, new fax messages, and a full mailbox me;>sage, if applicable. The
application
queries this information from the VFP via the VFP 'Trans Service.
The user also has the ability to define, via DTMF, whether he would like a
pager notification
of new voice and fax messages. Pager notification options are: Voicemail
notification, Fax
notification, notification of both Voicemail and Fax, and No notif cation.
Pager notification
settings are stored in the Page on Vmail flag (PIN bil: 15) and Page on Fax
flag (PIN bit 16).
Paging
The option to page the subscriber is one of the choices presented at the guest
menu. In
addition, the guest may be asked to send a page, according to the user's
programmed
Override or Alternate Routing.
In sending a page, the application requests the callback number from the
caller. The user's
customer record contains the following information used in processing the
page: the Pager
Access Number, used in launching the call to the pager company, the user's
Pager PIN, and
the Pager Type, which points to a configurable dial string for communicating
the page
2o information. The dial string provides the timeout value for waiting for
answer detection, the
delay following answer detection, the number of PIN' digits to DTMF, and any
termination
characters needed, for example '#'.
If a caller disconnects after entering a callback number, the page is
completed and billed.
Pager types supported are as follows:
w Page ~ Pager Pager dial string Pager Access
r ~ Company Number
Type
443
CA 02279845 1999-OS-17
WO 98123080 - PCT/(TS97/21174
1 SkyTel/MTeI A 180T32R7D#ED 6019609560
2 AirTouch A180T32R7D#ED 6019609560
3 Mobile MediaA I 80T32R7D#ED6019609560
4 AirSignal/McCA 180T32R7D#ED 6019609560
aw #
American A180T32R7D#ED 6019609560
Paging #
6 Mobile Comm A180T136R6T18E 8009464646*
T32
7 MCIPage A180T136R7T18E 8006247243*
T32
8 MCI Word A180T136R7T18E 8006247243*
T32
* 800-access numbers will be routed via the DAP-looparound at the brid~ins
switches.
The user has the ability to enable/disable the presentation of pager as a
guest menu option.
When pager is disabled, it is not presented at the Guest Menu, nor is it
presented to the user
5 in programming Override or Alternate Routing. The Guest Option of Voicemail
or Pager
also is removed from Alternate Routing programming choices. If Override
Routing is set to
Pager, and pager has been turned off, the call is handled as if Override were
not populated. If
Alternate Routing is set to Pager, and pager has been turned off the caller is
routed to
voicemail, if he has it, or the closing message is presented. These are the
default treatments
1o for Override and Alternate Routing. The Pager On/Off flag (State bit 13) is
where the
pager's enabled/disabled status is stored.
In addition to the pager enable/disable ability, the user can define pager
notification options,
as described in the Voicemail/Faxmail section of this description. The VFP
performs pages
~ 5 for notif cation of new voice and fax messages, and supports those pager
types supported by
the ISN. The status Pager On/Off flag has no impact on pager notification; the
user is
444
CA 02279845 1999-OS-17
WO ~~ PCT/US97/21174
required to set Pager Notification to No Notification, in order to receive no
notification of
new messages.
Outbound Dialing
The user has the ability to make a call, billing the call to his directlineMCI
account. This
option is presented at the Main User Programming menu. Outbound calling
options include:
Domestic termination, dependent on the Domestic Completion flag (State bit 4),
International
termination, dependent on the International Compilations flag (State bit 5),
and programmed
Speed Dial termination, dependent on the Speed Dial Completion flag (State bit
6).
1o
For any requested international completion, the application looks up the
terminating country
code in the Country Code tables. If the Direct Dial Country flag is set to 'Y'
for that
country, the ARU transfers the call to the manual console (TTC =9d) for
processing.
The following validation checks are made before a call is completed for a
subscriber:
Domestic numbers
The Domestic Compilations flag must be set to 'Y'
2o The International Blocking database is queried, using Category 000, Type
002, and the
programmed NPA, looking for a pattern match, to ensure that the programmed
number is not
a blocked Information/Adult Services number.
The Exchange Master is examined to determine whether the termination is an
NANP number.
If so, Country Set blocking is applied using the Country Set found in the
directline AuthCode
Property record. In the case of a subscriber calling in from an international
location, the
Country Sets from both the Property Record of the originating country and from
the
directlineMCI Property Record are retrieved, and the application verif es that
the PCC is not
blocked for either Country Set. The Property Record for an originating country
is looked up
using ' 191 '+3-digit Country Code+' 0000' as key into the Property Record
database.
445
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
International numbers
The International Compilations flag must be set to 'Y'
The Country Set from the directlineMCI Property Record is retrieved, and the
application
verifies that the destination Country Code is not blocked for that Country
Set. In the case of
an international origination, the Country Sets from both the Property Record
of the
originating country and from the directlineMCI Property Record are retrieved,
and the
application verifies that the destination Country Code is not blocked for
either Country Set.
t o Blocking checks for user call compilations, based on origination, and for
programming Speed °
Dial numbers, are included below.
Reori~ination
A caller may reoriginate from a call completion, either to the VFP or a
telephone number, by
~ 5 pressing the # key for 2 seconds. The switch verifies that reorigination
is permitted for that
call, and if so, it delivers the caller back to the ISN.
The status of a reoriginating caller is derived from the value in the Val Stat
field of the BDR
of the original call. The following table defines possible values for that
field and what each
value indicates:
zo
Val StatCaller Disposition of Reoriginatabl
Original
Value Type Call e?
200 Subscriber Call Completion Y
201 Subscriber Voice Mail Y
202 Subscriber Fax * n/a
100 Guest Off Line N
101 Guest Primary N
102 Guest Secondary N
103 Guest Tertiary N
104 Guest Override N
105 Guest Closing Message N
112 Guest Voice Mail N
446
CA 02279845 1999-OS-17
PCT/US97l211'14
113 Guest Pager N
114 Guest Fax N -
* Unused - Currently there is no differentiation
between subscriber access to voice mail and
subscriber access to fax mail; it will be indicated
with a Val Stat of 201
Additionally, # Reorigination is made available to the subscriber from
completion to the
voice mail/fax mail platform. This is done with two changes to the data
populated in the
switch record (OSR), as indicated in the Billing section.
Subscriber reorigination
A subscriber reorigination is identified as such via the Val Stat field of the
original call, and
the User Programming menu is presented. A subscriber who has completed to the
voice/faxmail platform or to a telephone number is allowed to reoriginate.
Console Impact
t o Console impacts are described in detail in the .following sections, as
well as in the call flow
diagrams.
ARU Transfers
The Console receives transfers from the ARU for the following reasons.
Treatment for these
transfers is indicated in the Console call flow diagrams.
TTC ~ Transfer Reason Text
1 a I Guest call completion requiring Operator 'Guest call requires Operator
assistance assistance'
64 Third non-entry at pager callback number prompt 'Pager callback number not
entered
properly'
67 Request or timeout at Guest Menu 'Requested transfer or time-out at Main
menu'
9d Subscriber call completion requiring Operator 'Subscriber call requires
Operator
assistance assistance'
447
CA 02279845 1999-05-17
PCT/US97/21174
Access Method
Refer to the Access Method section in ARU Impacts.
Direct Calling
Refer to the Direct Calling section in ARU Impacts., with the following
exception:
Default Routing
Default Routing does not have an impact on the Console, except when it's been
programmed
or defaulted to Operator Transfer. In this case, the call will be handled as a
new call, with the
Guest Menu presented.
Voicemail / Faxmail
Refer to the Voicemail/Faxmail section in ARU Impacts.
Pa in
Refer to the Paging section in ARU Impacts.
Outbound Dialing
Refer to the Outbound Dialing section in ARU Impacts.
Reorigination
Refer to the Reorigination section in ARU Impacts.
Flag Dependencies
Flag dependencies are shown in the following table:
Diagra Menu Menu Item Dependencies
m
3 Guest Menu -- Leave a voicemail VMaiI Flag
-
message
Send a fax Fax Termination Flag
Send a page Pager Termination Flag AND
Pager On/Off Flag
(Passcode) Program (Follow-Me) Flag
448
CA 02279845 1999-OS-17
WO g ~~ PCT/tJS97/21174
13 User Main Menu Change Call Routing,Find-Me Flag AND
(Domestic TerminationsFlag
OR .
International Termination
Flag OR
Vmail Flag OR
Pager Termination Flag)
Send / Retrieve VMail Flag OR
Mail
Fax Termination Flag
Place a Call Domestic Completion Flag
OR
International Completion
Flag OR
Speed Dial Completion
Flag
Administration Vmail Flag OR
Fax Termination Flag
OR
Speed Dial Programming
Flag OR
Greeting Recording OR
Call Screening Programming
Flag
OR
Pager Termination Flag
OR
Avail Programming Flag
--
Place a Call Speed Dial Number Speed Dial Compilations
Flag
Domestic Number Domestic Compilations
Flag
International NumberInternational Compilations
Flag
1 S Change Routing Find-Me Routing Domestic TerminationsFlag
OR
International Termination
Flag
Override Routing Domestic TerminationsFlag
OR
International Termination
Flag OR
Vmail Flag OR
Pager Termination Flag
- Alternate Routing Vmail Flag OR
Pager Termination Flag
Overnde RoutingPOTS Domestic Termination
is Flag OR
International Termination
Flae
449
CA 02279845 1999-OS-17
WO 9 8/23080 PCT/US97/21174
Pager Pager Termination Flag
Find-Me Domestic TerminationsFlag OR
International Termination Flag
Alternate RoutingGuest Option Vmaii Flag AND
Pager Termination Flag
Voicemail Vmail Flag
Pager Pager Termination Flag
17 Change 3-NumberFirst Number Domestic TerminationsFlag OR
Sequence International Termination Flag
Second Number Domestic TerminationsFlag OR
International Termination Flag
Third Number Domestic TerminationsFlag OR
International Termination Flag
Change to Schedule Schedule 1 Flag AND
Routing Schedule 2 Flag
18 Administration List Maintenance VMail Flag OR
Fax Termination Flag OR
Speed Dial Programming Flag
Record Greetings Greeting Recording Flag OR
Vmail Flag OR
Fax Termination Flag
Activate / DeactivateCall Screening Programming
Flag
Features OR
Pager Termination Flag OR
VMail Flag OR
Fax Termination Flag OR
Avail Programming Flag
Lists Broadcast Lists VMail Flag OR
Fax Termination Flag
Speed Dial Lists Speed Dial Programming Flag
Greetings Welcome Greeting Recording Flag
L.
450
CA 02279845 1999-OS-17
PCT/US97/211~4
Mailbox Name VMail Flag OR
Fax Termination Flag
20 Feature ActivationCall Screening Call Screening Programming
Flag
_ Activate / DeactivatesPager Termination Flag
Pager
Pager Notification Pager Termination Flag
Options AND
(VMail Flag OR Fax Termination
Flag)
Activate / DeactivateAvailable Programming Flag
Account
Pager NotificationVoicemail Only VMail Flag
Fax Only Fax Termination Flag
Voicemail and Fax VMail Flag AND
Fax Termination Flag
21 Program Domestic number Domestic Flag
International numberInternational Flag
Blocking Checks
This description does not include flags checks; it discusses Country Set,
'Adult Services'
(976), and Inter-NANP Blocking. Where needed, a default ANI Property record is
used for
Country Set Blocking.
976 blocking is implemented as follows:
The International Blocking database is queried, using Category 000, Type 002,
, and
the programmed NPA, looking for a pattern match, to ensure that the programmed
number is
1 o not a blocked InformationlAdult Services number. If a match is found, the
call/programming
is not allowed.
Inter-NANP blocking is implemented as follows:
The Exchange Master is examined to determine whether the termination is an
NANP
number. If so, the Intra-NANP flag is checked to see if it's set to 'Y'. If it
is, the Intra-
Country flag for the originating number is checked. If the Intra-Country flag
for the
originating number is also set to 'Y', the call is biocked. If not, the call
is allowed. In short,
451
CA 02279845 1999-OS-17
wo 98n3oso rcrrtJS~nma
if the Intra-Country flags of both the originating and terminating numbers are
'Y', the call is
blocked; if either one is set to 'N', the call is allowed.
Country Set blocking is implemented as follows:
The Country Sets) of the directlineMCI Property record, and possibly the
originating .
ANI/country; as indicated below, are validated against the Country Code of the
termination:
If the terminating country is blocked in any of the Country Sets, the call is
blocked.
Guest Call Completion
TerminationG
OriginationBDomestic NANP international
Domestic Inter-NANP Inter-NANP (Allow) Cset Blocking using
Term
(Allow) Cset Blocking using CC, Orig ANI* & Auth
Term
PCC, Orig ANI & Auth Csets
Csets
NANP Inter-NANP Inter-NANP (Block) Cset Blocking using
Term
(Allow) CC, Orig ANI & Auth
Csets
InternationalAllow Cset Blocking using Cset Blocking using
Term Term
PCC, Orig CC and AuthCC, Orig CC and Auth
Csets Csets
User Call Completion
OriginationB ~ Domestic NANP .International
Domestic Domestic Comp Domestic Comp Flag International Comp Flag
Flag Inter-NANP (Allow) Cset Blocking using Term
Inter-NANP 976 Blocking CC, Orig ANI & Auth
(Allow) Cset Blocking using Term Csets
976 Blocking PCC, Orig ANI & Auth
Csets
452
CA 02279845 1999-OS-17
PCT/US97121174
NANP Domestic Comp Flag International Comp
Domestic Flag
Comp
Flag Inter-NANPInter-NANP (Block) Cset Blocking using
Term
(Allow) 976 Blockini; CC, Orig ANI & Auth
976 Blocking Csets
InternationalDomestic CompDomestic Comp Flag International Comp
Flag
Flag 976 976 Blocking Cset Blocking using
Term
Blocking Cset Blocking using CC, Orig CC and
Term Auth
PCC, Orig CC and Csets
Auth
Csets
Programming Routing
TerminationG
OriginationBDomestic NANP International
N/A Domestic Flag Domestic Flag International Flag
976 Blocking 976 Blocking Cset Blocking using
Term
Cset Blocking using Term CC, Auth Cset
PCC, Auth Cset
ProErammin~ Speed Dial Numbers
TerminationG
OriginationBDomestic NANP International
N/A Domestic Domestic Cornp Flag International Comp
Comp Flag
Flag 976 Blocking Cset Blocking using
Term
976 BlockingCset Blocking, using CC, Auth Cset
Term
PCC) Auth Cset
XIX. INTERNET FAX
A. Introduction
A large percentage of calls on the PSTN are Fax calls. These calls send
digital information
encoded and modulated for analog transmission to the phone company's central
office (CO).
453
CA 02279845 1999-OS-17
WO. 98/23080 PCT/US97/211'74
At the CO the analogue signal is digitized for continuous transmission across
the PSTN at 64
Kbps. At the destination CO the digital signal is converted to analogue for
transmission to
the recipient Fax machine. Continuous transmission of international Fax
traffic results in
high utilization of scarce transmission capacity and incurs the high cost of
international direct
dial phone service.
B. Details
Currently, there is an increased interest in sending fax and voice over the
Internet. In the
past, facsimiles tended to be on the periphery of the network and did not
utilize the
1 o intelligence inherent in the Internet. A preferred embodiment
transparently routes faxes over
the Internet rather than tying up the telephone network. A network subsidized
with
appropriate logic can sense a fax call by sensing tones on the line. Then, the
call can be
directed to another piece of hardware or software that would then perform a
fax over the
Internet. The network performs routing by utilizing the destination fax
machines phone
~ 5 number as an address. Then, by accessing the DAP, the appropriate gateway
can be selected
to route the call to the appropriate destination based on the phone number.
This is
accomplished by sending a routing request to the DAP. The DAP selects the
destination
gateway by one of several methods. One method may be by point of origin. That
is, by table
lookup a particular point of origin is assigned a particular destination
gateway. Another
2o method could be by a load balancing technique. The network logic can
transparently detect
normal telephone network activities and transmit them over the Internet
without affecting
their integrity. One embodiment employs a double dialing scenario similar to
the current
telephone credit card. The first number is utilized to designate how the call
was to be routed,
while the second telephone number is used to route the call to the destination
address tike any
25 other telephone call once the appropriate gateway was identified.
The detailed logic associated with the alternative routing of faxes on the
Internet is
accomplished by monitoring calls on trunk groups. Typically, a company or
other
organization will purchase capacity on a trunk line that can be utilized
exclusively to service
3o the requirements of the organization. The trunk group of a preferred
embodiment is modified
with appropriate sensing hardware which can be a hybrid network, such as, or
including a
Digital Signal Processor (DSP) to divert faxes destined for predetermined
carriers over a data
454
CA 02279845 1999-OS-17
PCT/US97/21174 -
network such as an Internet or an X.25 network instead of the public switched
network. The
monitoring of the calls coming into a specific trunk group is performed
transparently.
The trunk group comes into a bridging switch which diverts calls to an
intelligent network.
The intelligent network detects if the call is being directed to a particular
country or city that
is targeted for special routing treatment over the Internet or another data
network instead of
the PSTN. If the call is not targeted for one of the country or city codes of
interest the call is
routed normally across the PSTN to its destination.
1 o Dropping down one more level of detail, when the call comes into an MCI
switch, the switch
launches a DAP query requesting a route for the call. The DAP analyzes the
call based on
the number dialed and other profile information, and routes the call to a fax
done detection
system. The fax tone detection system listens for fax CNG tone and if it
detects a CHG tone,
then a second phone call is placed to a fax Internet gateway. When the fax
Internet gateway
~ 5 answers, the first and second call are bridged together at a bridging
switch.
The required modification is to screen incoming calls by destination, For
predetermined
target destinations, the intelligent network holds the call for additional
processing. This is
accomplished according to a preferred embodiment illustrated in Figure 52B. In
that figure, an
20 originating user's fax machine F 1, i s connected via'switch 5260 to the
phone line. Switch 5260
connects the call via switch 5261 and places a routing request to the DAP 5262
for routing data
query purposes. The DAP is connected to a routing database such as a Long Term
Regulatory
Routing Database. The trunk is also connected to appropriate logic, only the
Fax Tone Detector
(FTD) is shown, at 5263. That logic includes logic to route fax calls destined
for predetermined
25 countries to a fax gateway 5264 via switches 5261and 5265 to an alternate
data network 5266 to
a fax gateway 5267 in the predetermined country. For countries other than the
predetermined
country, the switch 5261 will send the call by vyay of the PSTN.
Operation of the above embodiment of Figure 52B is seen with respect to the
flow chart of
3o Figure 52C. At step 5270 of the flow chart, the originating switch 5261 of
Figure 52B receives
the call. The call can be from a telephone, a PC, a fax machine F 1, or other
suitable device.
Using the destination information associated with the call, the DAP is queried
via Switch 5261
at step 5271. The DAP looks up the routing information and a decision is made
at step 5273
455
CA 02279845 1999-OS-17
WO 98/23080 - PCT/US97/21174
whether the destination is one of the predetermined countries, cities, or
other locations of
interest. If not, the call is handled through normal routing as in step 5274.
If the call is for a predetermineddestination of interest it is routed to the
FTP as in step 5275.
s The FTP then determines whether this call is a fax call at step 5276. This
may be done by
attempting to detect a CNG tone by well known means. In one method of
accomplishing this a
timer can be used. If a CNG tone is not detected within a specified time
period the call is
assumed not to be a fax call. It is then released and bridged through normal
routing over the
PSTN as at step 5277. If a CNG tone is detected, the call is released and
bridged to fax gateway
5264 as at step 5278, the call is collected and the fax is transmitted over
the alternate data
network 5266 over which it is sent to fax gateway 5267 and then on to fax
machine F2 at the
destination point.
This may have further routing vii a domain name that may have several
countries. The
~ s Domain Name Server will distribute calls amongst several destinations via
a lookup table. A
gateway will be located in a destination country and a TCP/IP session is set
up with the
gateway for control purposes. The data may be passed TCP or UDP based on the
particular
network characteristics. In any case, the dialed digits are passed to the
origin gateway which
forwards the digits to the destination gateway where the phone number is
dialed.
The destination gateway then dials the destination number and engages a fax
machine at the
other end. The system utilizes two pairs of fax modems to convert a telephony
signal to
packets and back. Fax modems like any other modems negotiate for baud rate,
but they do it
each time a page is transmitted. Each side specifies its capabilities and they
negotiate what
2s speed they can support. First) start the transfer of fax information, then
an ACK is
transmitted after each page and finally the baud rate is renegotiated at 300
baud (LCD).
Finally, the messages are received at the distant modem and the packet is
repackaged as a fax
package. At the end of every page, there is a renegotiating of baud rate based
on error rate,
and, if there are too many errors, the faxes will renegotiate to a lower speed
before resending
3o and/or retransmitting the page.
456
CA 02279845 1999-OS-17
WO 98/2,3880 PCT/US97/21I74
In accordance with a preferred embodiment, the system detects that the
destination telephone
circuit has been connected before transmitting fax information. The overhead
associated with
this processing requires the following detriments to normal fax processing.
- 1 ) Increased postdial delay; and
2) Actual transmission of the fax may take five percent longer.
XX. INTERNET SWITCH TECHNOLOGY
A. An Embodiment
The problem with current switched networks is that when you have a LEC
connected via
legislated feature group D trunks, providing inexpensive access is difficult
because access
charges are dictated by the LEC. Therefore, if the Internet access is provided
via a service
which utilizes feature group D trunks, the cost passed on to the consumer is
exorbitant. If the
feature group D trunks are bypassed, and a dedicated network is provided, ie.,
the LEC is
connected directly to a modem pool which provides access to the Internet, a
second tier of
problems arises. These problems include: scalability, survivability and
inefficiency of
design. Further, a modem would be necessary for each DSO purchased from the
LEC. All of
these problems are solved by the architecture discussed below.
Scalability is addressed by the CBLs described in Figure 1C because the modem
pool can be
adjusted to meet the network traffic requirements. The CBLs can be adjusted to
meet the
2o requirements of the particular community of interest. In a dedicated
network, a one-to-one
relationship exists between CBLs and entries in a modem pool. Then, if a modem
fails, the
ability to service users is directly affected by the ability to utilize
modems. By eliminating
the direct correlation between the modem pools and the CBLs, the DAP can map
calls to
dynamic resources obtained through the network wherever they reside. This
design is more
efficient than any current architecture. A detailed discussion of this
architecture ensues
below.
The third problem which was overcome by a preferred embodiment was a direct
result of
solving the previous two problems. A method for routing a call in the network
was required
3o when only an origination indication is provided by a LEC. An embodiment
incorporating the
functionality of a hotline provides a solution to this problem. When an
origination is detected
457
CA 02279845 1999-OS-17
WO 98/23080 PCTJUS97/2I174
on an incoming trunk (circuit) for which the hotline functionality is enabled,
a database
lookup is performed as an internal process of a switch's routing database.
This database
lookup results in a preliminary dialing plan (i.e. a 7 or 10 digit number)
that will be used to
determine the destination of the call. The hotline function resides in the
switch, but it was not
integrated into routing capability which exploited the DAP and allowed a
switch to formulate
a DAL procedure request without any calling information (ADF transaction) to
the DAP.
The request is transmitted over an X.25 protocol link, a local area network,
an Optical
Connection Three (OC3) ATM network, a frame relay, SMDS or other communication
link
to the DAP for processing. The DAP performs additional database lookups to
determine the
0 appropriate destination (in this case, it would be the Switch ID (SWID) and
Terminating
Trunk Group (TTG) that corresponds with the trunk connection to the Modem
Pool). The
hotline is a foundation in the design that overcame the problems described
above.
Figure 71 depicts a typical customer configuration of a hybrid network for
carrying private
network services, such as VNET, Vision or other media while providing local
dial access,
private dialing plans over shared or dedicated access. The combination of the
FDDI LAN
10201, the transaction servers 10205, and the communication servers 10215 and
10225 are
collectively referred to as a DAP. A local area network such as Fiber
Distributed Data
2o Interface (FDDI) LAN 10201 is used to connect various communication
devices. In the
configuration depicted, Transaction Server (TS) 10205 is connected to the LAN
10201.
Telephony switches such as switch 10210 and switch 10220 are connected to LAN
10201
through Communication Servers (CS) 10215 and 10225, respectively. In the
example shown,
CS 10225 communicates with the switches utilizing a protocol termed
Application Data Field
(ADF) 10245. Gateway 10230 connects to the LAN 10201 and provides
communication
between the Customer Access Processor (CAP}. The CAP 10235 is typically a
microprocessor such as the Intel Pentium, RISC or Motorola 68xxx family. The
DAP would
send a transaction query to the CAP. The CAP performs a database lookup to
return routing
instruction based upon, for example, the status of how many operators are
available at a
3o particular customer service center. The CAP returns a response that
indicates how a call should
be routed based upon that database lookup. The DAP uses that information
basically as an
extension of its own database. The DAP would then interpret the information
received from
- 458
CA 02279845 1999-OS-17
PCT/US97I21174
the CAP 10235 and translate it into routing information that the switch
requires to.route the call
to where the customer required.
Figure 72 depicts the operation of DAPs 10240, individually labeled as DAPS
10241. 10242
and 10243. Routing and customer profile information is entered into the order
entry system
10235 after validation and the information is routed to the Service Control
Manager (SCM)
10230. SCM 10320 sends the routing and customer profile information to each of
the DAPS
in the network.
For example, if a problem arises with Windows95, a customer would call I-800-
FIX-WIN95.
The call enters the network at Originating Switch 10350 which would initiate a
transaction to a
DAP 10241-3 querying for appropriate routing information for the call. The
queried DAP
recognizes the number, creates a transaction and routes it to the appropriate
gateway 10230 that
is connected to the appropriate CAP 10235 (in this case the CAP as.~ociated
with the Microsoft
t 5 company). The CAP 10235 receives the transaction and determines that the
customer service
center in New York is swamped, but the customer service center in California
is not very busy
(time of day could account for the reason in this case). The CAP 10235 would
send a response
back to the queried DAP 10241-3 (via the gateway 10230) indicating that this
particular
1-800-FIX-WIN95 call should be routed to the California customer service
center. The selected
2o DAP 10241-3 translates the transaction information into a specific Switch
ID (SWID) and a
specific Terminating Trunk Group (TTG) that corresponds to the route out of
the MCI network
necessary to arrive at the California customer service center. The selected
DAP 10241-3
transmits this response information to the originating switch 10350 which
routes the original
call to 1-800-FIX-WIN95 to the correct Terminating switch 10351, as indicated
in the DAP
25 response via the SWID.
The terminating switch 10351 then determines the correct Terminating Trunk
Group (TTG}
utilizing information transmitted via SS7 network created from a parameter in
the original DAP
response, and routes the call to the California customer service center. When
a call is routed
3o through a switch, it is passed via a Direct Access Line' (DAL) connection
such as DAL 10386
to the customer PBX 10387 which delivers the call to the target telephone
10361.
459
CA 02279845 1999-OS-17
wo ~~oso rc~rrtJS9~nm~4
Figure 73 depicts the process by which a telephone connects to a release link
trunk for I -800
call processing. A telephone such as telephone 10410 is connected to local
exchange carrier
(LEC) 10415. The user of telephone 10410 uses the telephone keypad to enter a
1-800
number, which causes LEC 10415 to route the call to MCI Originating switch
10420. In
order to process the 1-800 request, switch 10420 must communicate with ISN
10480. Switch
10420 therefore connects the call to bridging switch 10440, which is connected
to Intelligent
Service Network 10480 via a release link trunk 10490. Bridging switch 10440
passes the
DAP request with the I-800 information to ISN 10480, which passes it to the
addressed DAP
10241. DAP 10241 examines the 1-800 request and selects the appropriate
release link trunk
t o 10490, which it connects to MCI D switch 10420, which in turn is connected
to the LEC
10415 which is ultimately connected to telephone 10410, thereby completing the
call. ANI
is a standard term in the industry that refers to Automatic Number
Identification (ANI). ANI
can be used to complete the call. This is the information that the MCI network
receives from
the LEC To identify where the call originated from. In simple terms, it would
be your home
t 5 phone number if you originated the call. It could also be the payphone
number that a credit
card caller originated from, so it is not always used to determine to whom to
bill the call.
A similar process may be used to connect telephone 10450 through LEC 10455 to
a switch
10460 utilizing a bridging switch 10440 to bridge the call to the release link
trunk 10490
2o through ISN 10480.
Figure 74 depicts the customer side of a DAP procedure request. In the home
and small
office environment, devices such as modem 10510, telephone 10515 and fax 10510
are
plugged into a standard RJl 1 jack 10520, which is connected to the local
exchange Garner.
25 Local exchange carrier 10525 connects to switch 10530 via common business
lines 10527.
In a large office environment, an office equipped with a PBX 10540 may connect
to switch
10530 via dedicated access line (DAL) 10547, without the involvement of the
local carrier.
Switch 10530 issues DAL procedure request to DAP 10560, which selects routing
10570 for
the call, as will be more fully described with respect to Figure 75.
Figure 75 depicts operation of the switch 10530 to select a particular number
or "hotline" for
a caller. Switch 10530 accepts an incoming call from CBL 10527 or DAL 10547,
and
contacts DAP 10560 for instructions on routing the call. DAP 10560 returns
routing
- 460
CA 02279845 1999-OS-17
w° ~ar23oso rc~rrt~s9~nm7a
information encoded in the form of a pseudo-telephone number. The pseudo
telephone
number has the same format as an ordinary telephone number but instead encodes
a 3-digit
switch identifier (SWID) and a file number of a file that identifies a desired
Terminating
Trunk Group (TTG) . Switch 10530 contacts the switch 10610 identified by the S
WID and
passes to it the file number. Switch 10610 uses the TTG to select the
appropriate modem
pool 10620 to complete the connection. The modem pool in turn provides an
Internet
Protocol (IP) connection 10630 to such services as authentication service
10640 and to Basic
Internet Protocol Platform (BIPP) 10650. The BIPP 1065.0 is composed of packet
switches,
such as ATM switches, that transfer IP packets from one node to another.
Authentication
service 10640 optionally performs security functions to authenticate the
calling party and to
prevent unauthorized access to the Internet. It may also be used to formulate
billing
information necessary to ensure proper reconciliation for customers that
access the Internet
via the TTG hotline. The provision of this hotline function enables routing of
the call
through switches 10530 and 10610 without the use of expensive FGD links such
as the FGD
t 5 10380 depicted in Figure 72.
Figure 76 depicts the operation of a gateway for selectively routing telephone
calls through
the Internet. Terminal switch 10710 connects to an ARU 10720 to request
routing -
information. ARU 10720 interrogates the properties of the call to determine
whether it is a
2o candidate for Internet routing. If the call is a modem call, the call is
routed to modem pool
10730. From modem pool 10730, the call may then tie routed to Basic Internet
Protocol
Platform 10750 to provide Internet access to the modem call. The modem call is
optionally
authenticated by authentication service 10760. If the call is a fax call, the
call is routed to
modem pool 10730. From modem pool 10730, the call may then be routed to Basic
Internet
25 Protocol Platform 10750 and from there to fax gateway 10770. As with a
modem call, a fax
call is optionally authenticated by authentication service 10760.
If the call to be routed is a voice call, ARU 10720 waits for the user to dial
a calling card
number and a destination telephone number. ARU 10720 interrogates the
destination number
3o to determine whether the destination telephone is an international call or
a domestic call.
Domestic calls are returned to the termination switch 10710 for conventional
routing.
International calls are encoded as data by providing the analog voice signal
to coder/decoder
461
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
(or "codec") 10725. Codec 10725, having encoded the signal as digital data
then routes the
call through modem pool 10730 and Basic Internet Protocol Platform 10750.
In an alternate embodiment, when the call is delivered to the ISN by the
network switch, an
s SS7 ISUP message is routed to the resident ISN switch. That switch is called
a DMS-ACD.
ACD stands for Automatic Call Distributor. The ACD takes an incoming SS7 ISUP
message
and converts it to SCAI (Switch/ComputerApplication Interface). On the
opposite side of the
ACD is a device called an ISN-AP {Intelligent Services Network - Adjunct
Processor). SCAI
is the language spoken between the ACD and the ISN-AP. So, there are two
interfaces: on the
to inbound side from the network to the ACD a SS7 ISUP, and on the outbound
side from the
ACD to the ISN-AP a SCAI. These are simply two different signaling protocols.
When the call arrives at the ACD from the network, the ACD doesn't
automatically know
where to route the call. The ACD receives its instructions from the ISN-AP. To
do that, the
15 ACD takes the ISUP
signaling parameters received from the network and converts them to SCAI
protocol format
and sends a SCAI message to the ISN-AP.
Specifically, the SCAI message is called DV Call Received (DV means
Data/Voice. When
2o the ISN-AP receives this message it looks at the Called Party Number (CPN)
field within the
SCAI message and, based on that number, determines where in the ISN the ACD
should route
the call. When the ISN-AP has made the decision, the ISN-AP builds a
DV Call Received_RR{a response to the previous message -- RR means Return
Result).
Within the RR message are instructions to the ACD regarding the. ACD port to
which the call
25 should be terminated.
For this service, the ACD is instructed to terminate the call to the ACD ports
connected to the
ARU 10720. When the call arrives at the ARU 10720, there are two things that
can happen:
1 ) If the caller has dialed the access number from an:
3o a)telephone or
b)fax machine,
that caller will hear a voice prompt that says "Press 1 for voice, or press 2
for fax."
_. 462
CA 02279845 1999-OS-17
W0 98123080 PCTIUS97/21174
2) If the caller has dialed the access number using a 1'C modem, that caller
likely won't hear
any announcement. What will happen is that a ARU timer will expire. Expiration
of that timer
indicates to the ARU that this call is from a modem.
The call flow for these scenarios can be confusing, so let's consider them one
at a time.
If a caller has called from a telephone, then at the ARL710720 voice prompt,
the caller will
press 1 (for voice service). At that time, the ARU 10720 will collect further
information about
the caller. This feature is a modified version of existing calling card
services that telephone
companies offer today. The ARU 10720 first collects the card number, then
collects the
number the caller wishes to terminate to. After capturing this information,
the ARU 10720
sends the data across the ISN Local Area Network (LAN) to a validation data
base. In addition
to verifying the calling card number, the data base also ensures that the
terminating number is
within the allowed dialing plan for the card holder.
I5
Once the card information is verified, the ARU 10720 will then determine if
the terminating
number is domestic or international. If the terminating number is domestic,
the ARU 10720
will release the call from the ISN back into the voice network where the call
will be routed to
its intended destination. If the terminating number is international, the call
will be routed to a
2o device called a CODEC (COde DECode) resident at a 1BIPP site. The purpose
of the CODEC
is to convert the voice signal to data for routing over the Internet using
UDP/IP.
In an alternate embodiment, if the caller has called from a fax machine, at
the ARU 10720
voice prompt, the caller will press 2 indicative of a request for fax service.
At that time, the
25 ARU 10720 will route the call to a fax platform that is a guaranteed fax
service 10770 for those
who don't have the time or patience to wait for a terminating fax number to
become available,
or for those who need assistance delivering an international fax. An
embodiment collects
information about the caller and terminating number, then instructs the caller
to begin the send
process. The fax service 10770 captures the fax and stores it for delivery at
a later time.
If a caller has dialed via a PC modem, then at the ARU 10720 voice prompt, the
caller will
likely not hear any announcement. This is intended. It is possible that the
caller may hear the
ARU 10720 announcement via the PC speaker or modem, but the caller is unable
to make an
463
__
CA 02279845 1999-OS-17
W~p 9813080 PCTIUS97/21174
entry at the ARU 10720 and will ultimately time-out (as described above),
indicating to the
ARU 10720 that this call originated from a PC modem. The ARU 10720 releases
the call back.
into the network for termination to a Modem Pool (MP) 10730 at one of MCI's
BIPP 10780
sites.
Figure 77 depicts the operation of the ARU of Figure 76 deployed in a
centralized
architecture. Telephone 10810 communicates through local exchange 10820 to
switch
10710. Switch 10710 connects through bridge switch 10830 to Intelligent
Services Network
(ISN) 10840 to ARU 10720. ARU 10720 controls the call routing either directly
to the
o modem pool 10730, via codec 10725 to the BIPP 10750 or to a fax server.
Figure 78 depicts the operation of the ARU of Figure 77 deployed in a
distributed
architecture. Telephone 10910 communicates through local exchange 10920 to
switch
10710. Switch 10710 connects through bridge switch 10930 to intelligent
service network
~ 5 10840 to ARU 10720. ARU 10720 operates under control of voice response
unit 10950,
connected through switch 10911 and bridge switch 10930 to control the call
routing either
through switch 10912 to modem pool 10730, or via a codec. The ARU must be
placed in the
ISN, but the other pieces (i.e., ARUs 10850 and 10950, modem pool 10730 and
codec 14725)
may be placed anywhere in the network.
Figure 79A and 79B depict the operation of sample applications for Internet
call routing.
Figure 79A depicts a sample application for customer service. Intranet
computer 11010
connects to the Internet 11020 as described above, and thereby connects to a
server computer
11025. Server computer 11025, through designation of an Internet resource,
such as a
packing shipping service provider 11030, via a Uniform Resource Locator
permits a user of
Intranet computer 11010 to query the provider 11030. Through internal
functions shown as
11032, provider 11030 may provide in response to user interactions such
resources as a full
motion video display 11035 from its customer service department, or direct
interactive
conversations with a customer service representative 11037.
Figure 79B depicts a number of applications for caller-initiated consumer
transactions. A
consumer calling a predetermined number 11040 (such as 555-IMCI, 555-PAGE or
555-
RNET) may be routed to a particular transaction processor through the use of
common
464
CA 02279845 1999-OS-17
PL~YUS9fil21t<74
business line (CBL) 11050. CBL 11050 connects to switch 11060. Switch 11060
calls DAP
11065, which analyzes the incoming call using Automatic Number Identification
(ANI) to
determine the identity of the caller. Based on the identity of the caller in
combination with
the number called, DAP 11065 directs switch 11060 to direct calls to 555-IMCI,
for example,
to Data Network Interface (DNI) 11070. DNI 11070 serves as an interface
between the
. switch network and a database host 11075 capable of processing point-of sale
debit and
~ credit card transactions. In addition to routing the call based on the
target telephone number,
the ANI data is used to identify the caller to the database host 11075.
Similarly, a call to S55-
PAGE may be routed to the PBX of a paging service company 11080, and the ANI
data used
to to select a particular paging service 11085 offered by the company.
Finally, calls to ~~5-
RNET may be used to provide connection to the Basic Internet Protocol Platform
11090, as
previously described.
Figure 80 illustrates a configuration of a switching network offering voice
mail and voice
t 5 response unit services, as well as interconnection into a service
provider, in accordance with a
preferred embodiment. Telephones 11111 and 11112 enter the network via
switches 11120
and 11121 respectively, Switch 11121, in addition to offering network entry to
telephone
11112, provides an intermediate link for switch 11120. Switch 11125 provides
interconnection for switch 11121, as well as accepting direct input such as
PBXs 11130.
2o Switch 11125 provides connections to voice response unit server 11140 and
to voice mail
server 11145. In addition, switch 11125 connects to service provider server
11150 through
Dial Access Line 11155. Service provider 11150 further routes incoming calls
according to
service requested and authenticity to paging service 11060 or to email service
11070 using
BIPP 11075 connected through modem pool 11076.
25 B. Another Embodiment
Figure 81 illustrates an inbound shared Automated Call Distributor (ACD) call
with data
sharing through a database in accordance with a preferred embodiment. A dial-
up Internet
user 12000 uses a computer modem to dial a telephone number. The telephone
call is routed
from the RBOC/LEC Switch 12002 to MCI Switch 1 12004. MCI Switch 1 12004
queries
~3o the Network Control System (NCS) 12020 to ask for a route for the given
ANI and dialed
telephone number. The NCS 12020 returns a terminating address, instructing MCI
Switch 1
12004 to route the call to a trunk group on MCI Switch 2 12006.
465
CA 02279845 1999-OS-17
WO X8/23080 PCT/US97/21174
MCI Switch 2 12006 completes the call to the Internet Access Device 12008. The
modem in
the dial-up user's computer 12000 and the Internet Access Device 12008
establish a data
session, and data packets are exchanged according to the Point to Point
Protocol (PPP). From
the Internet Access Device 12008, PPP packets are translated to Internet
Protocol (IP) packets -
and sent on the Internet, represented by 12026. Similarly, the Internet Access
Device 12008
receives IP packets from the Internet 12026 and sends them to the dial-up user
12000.
Before packets are allowed to pass freely through the Internet Access Device
12008, the dial-
to up user-12000 is authenticated. This is done using the username/password
method, or the
challenge/response method.
In the username/password method, the Internet Access Device 12008 prompts the
dial-up
user 12000 to enter a user name. The dial-up user 12000 types a user name into
the
t 5 computer, and the user name is transported from the dial-up user 12000 to
the Internet Access
Device 12008. The Internet Access Device 12008 then prompts the dial-up user
12000 to
enter a password. The dial-up user 12000 types a password into the computer,
and the
password is transported from the dial-up user 12000 to the Internet Access
Device 12008.
Once the user name and password are received, the Internet Access Device 12008
sends an
2o authentication request, containing the user name and password, to the
Authentication Server
12014. The Authentication Server 12014 checks the user name/password against a
database
of valid user name/password pairs. If the entered user name/password are in
the database, the
Authentication Server 12014 sends an "user authenticated" message back to the
Internet
Access Device 12008. If the entered user name/password are not in the
database, the
25 Authentication Server 12014 sends a "user not authenticated" message back
to the Internet
Access Device 12008.
In the challenge/response method, the Internet Access Device 12008 prompts the
dial-up user
12000 to enter a user name. The dial-up user 12000 types a user name into the
computer, and
3o the user name is transported from the dial-up user 12000 to the Internet
Access Device
12008. The Internet Access Device 12008 then prompts the dial-up user 12000 to
with a
challenge, which is a sequence of digits. The dial-up user 12000 computes a
response to the
challenge by entering the challenge digits and a shared secret key into
response-generation
466
CA 02279845 1999-OS-17
PCT/US97/ZI174 -
program. The shared secret key is known only to the dial-up user 12000 and~the
Authentication Server 12014. The dial-up user 12000 types in the computed
response, and
the response is transported from the dial-up user 12000 to the Internet Access
Device 12008.
The Internet Access Device 12008 sends an authentication message, containing
the user
name, the challenge, and the response, to the Authentication Server 12014. The
Authentication Server reads the user name, finds the shared secret key for
that user name, and
uses the shared secret key and the challenge digits to compute the response.
The computed
response is compared to the response given by the dial-up user 12000. If the
responses
match, a "user authenticated" message is sent from the Authentication Server
12014 to the
Internet Access Device 12008. If the responses do not match, a "user not
authenticated"
message is sent from the Authentication Server 12014 to the Internet Access
Device 12008.
Whether the user name/password or challenge/response methods of authentication
are used,
the rest of this description assumes a "user authenticated" message is sent
from the
Authentication Server 12014 to the Internet Access Device 12008, and IP packet
communication is allowed to flow freely through the Internet Access Device
12008.
The dial-up user 12000 starts a web browser and browses web pages from the
Corporate Web
Server 12024. The Corporate Web Server 12024 records the web pages viewed by
the dial
2o up user 12000 in the Call Center Server 12028 using a unique identifier.
The dial-up user
12000 may also submit information to the Corporate Web Server 12024 by filling
out
Hypertext Markup Language (HTML) forms and submitting the information to the
Corporate
Web Server 12024. The Corporate Web Server 12024 deposits this information in
the Call
Center Server 12028 using the same unique identifier.
The dial-up user 12000 browses another web page, upon which an icon is
displayed along
with text indicating that the user can talk to an agent by clicking on the
icon. Clicking on the
icon results in a download of a Multipart Internet Mail Extensions (MIME) file
from the
Corporate Web Server 12024 to the dial-up user's 12000 web browser. The MIME
file
3o contains an alphanumeric string identifying the destination for a resulting
phone call, called a
user-identifier. The browser invokes a helper application or browser plug-in
to handle the
file of the designated MIME type. The helper application reads the MIME file,
and launches
a query with the MIME file contents from the dial-up user 12000 to the
Directory Server
467
CA 02279845 1999-OS-17
WO 98/23080 - PCT/US97/21174
12012. The Directory Server 12012 translates the alphanumeric string from the
MIME file
into the destination IP Address of the destination Internet Telephony Gateway
12018, and
sends a message containing the IP Address back to the dial-up user's 12000
helper
application. The helper application then launches an Internet telephony call
to the Internet
s Telephony Gateway's 12018 IP Address, providing to the Internet Telephony
Gateway 12018 -
the alphanumeric string from the MIME file, as a part of the call setup.
The Internet Telephony Gateway 12018 translates the given alphanumeric string
into a
destination telephone number, and dials the destination telephone number on
it's telephone
network interface to MCI Switch 2 12006. MCI Switch 2 12006 queries the NCS
12020 with
the dialed telephone number, requesting routing instructions. The NCS 12020
determines the
appropriate route and sends routing instructions back to MCI Switch 2 12006 to
route the call
to a particular trunk group on MCI Switch 1 12004. The call is routed to MCI
Switch 1
12004, and then the call is completed to the Automated Call Distributor (ACD)
12022. When
~ s the ACD 12022 answers the call, the Internet Telephony Gateway 12018
completes a
constant audio path between the ACD 12022 and the Dial-up user 12000, with the
audio from
the ACD to the Internet Telephony Gateway being circuit-switched PCM audio,
and the
audio from the Internet Telephony Gateway to the Dial-up user being packetized
encoded
digital audio, using any audio codec.
When the call is delivered to the ACD 12022, the unique record identifier is
delivered to the
ACD via telephone network signaling mechanisms. When an agent in the call
center 12026
receives the call, the unique record identifier is displayed for the agent,
and the call
information entered by the dial-up user 12000 is retrieved from the Call
Center Server 12028.
-
XXI. BILLING
Another embodiment in accordance with this invention relates generally to
telecommunication networks, and more specifically, to switches of a
telecommunication
network that generate call records using a flexible and expandable record
format and
3o generates a unique call identifier for each telephone call that traverses
the network.
A typical telecommunication network comprises multiple telecommunication
switches
468
CA 02279845 1999-OS-17
WO 98J23080 PCT/I1S97/21174
located throughout a geographical area. When a user makes a call, the call may
be routed
through one or more switches before reaching its destination.
Figure 82 illustrates an exemplary telecommunications system 30102 across the
United
States. For purposes of illustration, a caller 30104 places a call from Los
Angeles, California
to a party 30112 located in New York City, New York. Such a call is typically
transmitted
across three (3) switches: the Los Angeles, California switch 30106; the
Chicago, Illinois
switch 30108; and the New York City, New York switch 30110. In this scenario,
the
originating switch is the Los Angeles, California switch 30106, and the
terminating switch is
the New York City, New York switch 30110.
Each of the switches, 30106-30110, is connected to two (2) or more Data Access
Points
(DAP) 30116-30120, for instance a primary DAP 30116-30120 and a backup DAP
30116-
30120. A DAP 30116-30120 is a facility that receives requests for information
from the
switches 30106-30110, processes the requests, and returns the requested
information back to
the requesting switch 30106-30110. The switches 30106-30110 use information
from the
DAPs 30116-30120 to process calls through the network.
When a call passes through one of the switches, 30106-30110, that switch
creates a call
2o record. The call record contains information on the call, including but not
limited to: routing,
billing, call features, and trouble shooting information. After the call is
terminated, each
switch 30106-30110 that processed the call completes the associated call
record. The
switches 30106-30110 combine multiple call records into a billing block.
2s When a switch 30106-30110 fills the billing block, the switch 30106-30110
sends the billing
block to a billing center 30114. Thus, the billing center 30114 receives one
billing block
from each switch 30106-30110 that handled the call, which in this case would
be three billing
blocks. The billing center 30114 searches each billing block and retrieves the
call record
associated with the call, thereby retrieving one call record per switch 30106-
30110 that
3o handled the call. The billing center 30114 then uses one or more of the
retrieved call records
to generate a billing entry. The billing center 30114 is also connected to
each DAP 30116-
30120 to retrieve information regarding a switch 30106-30110 or call record.
469
CA 02279845 1999-OS-17
PCT/US97/21174 -
To better understand the invention, it is useful to describe some additional
terminology
relating to a telecommunication network. A telephone call comes into a switch
on a
transmission line referred to as the originating port, or trunk. The
originating port is one of
many transmission lines coming into the switch from the same location of
origin. This group
of ports is the originating trunk group. After processing an incoming call,
the switch
transmits the call to a destination location, which may be another switch, a
local exchange
carrier, or a private branch exchange. The call is transmitted over a
transmission line referred
to as the terminating port, or trunk. Similar to the originating port, the
terminating port is one
of a group of ports going from the switch to the same destination. This group
of ports is the
I o terminating trunk group.
Contemporary telecommunication networks provide customers with the capability
of using
the general public network as well as the capabiiity of defining a custom
virtual network
(VNet). With a VNet, a customer deFnes a private dialing plan, including plan
telephone -
t 5 numbers. A VNet customer is not limited to the default telephone numbers
allocated to a
public telecommunication system dedicated to a specific geographic region, but
can define
custom telephone numbers.
Upon processing a telephone call, a switch must generate a call record large
enough to
2o contain all of the needed information on a call. The call record, however,
must not be so
large that the typical call results in the majority of the record fields in
the call record to be
unused. In such a case, storing such call records results in large amounts of
wasted storage,
and transmitting such a call record causes unnecessary transmissions.
2s One solution for creating and processing call records is to implement a
fixed length call
record format, such as a 32-word call record. A word is two (2) bytes, or
sixteen ( 16) bits. A
fixed length record format, however, cannot expand when new call features are
implemented.
More importantly, fixed call record formats cannot handle expanded data fields
as the
telecommunications network becomes more complex with new features and
telephone
30 numbers.
Contemporary fixed length record formats include time point fields recording
local time in
three (3) second increments where local switch time represents the time of day
at a switch.
470
CA 02279845 1999-OS-17
wo 9sn3aso _ rcrrtrssr~nma
The timepoint fields are used by the network switches, billing center, and
other_network
subsystems. Each subsystem, however, may require the time period for a
different use and in
a different format, such as in an epoch time format. Epoch time is the number
of one ( 1 )
second increments since a particular date and time in history. For example,
the billing center
requires epoch time for its billing records whereas switch reports and error
logs require local
switch time.
A problem also arises when using only local switch time in that there is no
accommodation
for time changes due to daylight savings time. In addition, each subsystem may
require a
finer granularity of precision than the current three (3) second increments.
By providing only
local switch time at three (3) second increments, the switches have passed the
burden of
translating the time into a usable format to the network subsystems. The fixed
record format
cannot accommodate the various time period requirements because it only
contains the time
periods in local switch time at a low level of precision. Because of its fixed
nature, the fixed
15 record format cannot expand to include different time formats, nor to
include a finer
granularity of precision, such as a one ( 1 ) second increment.
Therefore, there is a need for switches of a telecommunications network to
store call record
information in a flexible and expandable format. There is a further need to
provide time
2o point fields with one (1) second granularity in a flexible format that
easily and efficiently
responds to daylight savings time and time zone changes.
There is also a need to match all of the call records associated with a
specific telephone call.
For example, for proper billing and cost control, it is~ necessary for the
billing center to match
25 the originating switch's call record to the terminating switch's call
record. Also, for
troubleshooting and security purposes, it may be necessary to trace a specific
telephone call
through the network with ease in order to isolate problem areas.
Therefore, there is a need for switches of a telecommunications network to
uniquely identify
30 each telephone call that traverses the network, thereby uniquely
identifying all of the call
records associated with a specific telephone call.
471
CA 02279845 1999-OS-17
WO 98/23U80 PCT/US97/21174
A. An Embodiment
1. Call Record Format
An embodiment solves the problem of providing a flexible and expandable call
record format
by implementing both a small and a large call record format. In particular,
the embodiment
implements a default 32-word call record format, plus an expanded 64-word call
record
format. An embodiment uses a 32-word call record format for the typical
telephone call,
which comprises the majority of all telephone calls, and uses a 64-word call
record format
when additional information is needed regarding the call. This implementation
provides the
flexibility needed to efficiently manage varying data requirements of a given
call record.
1 o New call features can _be developed and easily incorporated into the
variable call record
format of the present invention.
This embodiment also records timepoints in the epoch time format. The
embodiment records
the origination time of a call in epoch time format, and the remaining
timepoints are offsets,
or the number of seconds, from that origination time. This embodiment solves
the problems
associated with converting to and from daylight savings time because daylight
savings time is
a local time offset and does not affect the epoch time. Furthermore, the
timepoints in epoch
time format require less space in the call record than they do in local switch
time format.
2o The epoch time format may represent coordinated universal time (UTC), as
determined at
Greenwich, England, which has a time zone of zero (0) local switch time, or
any other time.
Epoch time is only a format and does not dictate that UTC must be used. The
billing time
and the local switch time may be in UTC or local time, and the local switch
time may not
necessarily be the same time that is used for billing. Therefore, the switch
must keep billing
time and local switch time separate in order to prevent the problems that
occur during
daylight savings time changes.
2. Network Call Identifier
This embodiment solves the problem of uniquely identifying each telephone call
and all of
3o the call records associated with a specific telephone call by providing a
unique identifier to
each call record. It generates a network call identifier (NCID) that is
assigned to each call
_ 472
CA 02279845 1999-OS-17
WO 98/23080 PGT/US97/21174
record at the point of call origination, that is, the originating switch
generates an NCID for
each telephone call. The NCID accompanies the associated telephone call
through the
telecommunications network to the termination point at the terminating switch.
Therefore, at
any point of a telephone call in the network, the associated NCID identifies
the point and
time of origin of the telephone call. Each switch through which the telephone
call passes
records the NCID in the call record associated with the call. The NCID is
small enough to fit
in a 32-word call record, thereby reducing the data throughput and storage.
The NCID
provides the billing center and other network subsystems with the ability to
match originating
and terminating call records for a specific telephone call.
This embodiment also provides the switch capability of discarding a received
NCID and
generating a new NCID. A switch discards a received NCID if the NCID format is
invalid or
unreliable) thereby ensuring a valid unique identifier to be associated with
each call going
through the network. For instance, an NCID may be unreliable if generated by
third party
t 5 switches in the telecommunications network.
This embodiment relates to switches of a telecommunication network that
generate call
records using a flexible and expandable record format. The call record formats
includea-
small (preferably 32-word) and a large (preferably 64-word) expanded format.
It would be
2o readily apparent to one skilled in the relevant art to implement a small
and large record
format of different sizes.
The embodiment also relates to switches of a telecommunication network that
generate a
unique NCID for each telephone call traversing the network. The NCID provides
a
25 mechanism for matching all of the call records associated with a specific
telephone call. It
would be readily apparent to one skilled in the relevant art to implement a
call record
identifier of a different format.
The chosen embodiment is computer software executing within a computer system.
Figure
30 83 shows an exemplary computer system. The computer system 30202 includes
one or more
processors, such as a processor 30204. The processor 30204 is connected to a
communication bus 30206.
473
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
The computer system 30202 also includes a main memory 30208, preferably random
access
memory (RAM), and a secondary memory 30210. The secondary memory 30210
includes,
for example, a hard disk drive 30212 and/or a removable storage drive 30214,
representing a
floppy disk drive, a magnetic tape drive, a compact disk drive, etc. The
removable storage
drive 30214 reads from and/or writes to a removable storage unit 30216 in a
well known
manner.
Removable storage unit 30216, also called a program storage device or a
computer program
product, represents a floppy disk. magnetic tape, compact disk, etc. The
removable storage
1 o unit 30216 includes a computer usable storage medium having therein stored
computer
software and/or data.
Computer programs (also called computer control logic) are stored in main
memory 30208
and/or the secondary memory 30210. Such computer programs, when executed,
enable the
~ 5 computer system 30202 to perform the functions of the present invention as
discussed herein.
In particular, the computer programs, when executed, enable the processor
30204 to perform
the functions of the present invention. Accordingly, such computer programs
represent
controllers of the computer system 30202.
- 2o B. /Another Embodiment)
Another embodiment is directed to a computer program product comprising a
computer
readable medium having control logic (computer software) stored therein. The
control logic,
when executed by the processor 30204, causes the processor 30204 to perform
the functions
as described herein.
Another embodiment is implemented primarily in hardware using, for example, a
hardware
state machine. Implementation of the hardware state machine so as to perform
the functions
described herein will be apparent to persons skilled in the relevant arts.
1. Call Record Format
This embodiment provides the switches of a telecommunication network with nine
(9)
474
CA 02279845 1999-OS-17
PCT/US971Z1174
different record formats. These records include : Call Detail Record (CDR),
Expanded Call
Detail Record (ECDR), Private Network Record (PNR), Expanded Private Network
Record -
(EPNR), Operator Service Record (OSR), Expanded Operator Service Record
{EOSR},
Private Operator Service Record (POSR), Expanded Private Operator Service
Record
(EPOSR), and Switch Event Record (SER). Each record is 32 words in length, and
the
expanded version of each record is b4 words in length.
Example embodiments of the nine (9) call record formats discussed herein are
further
described in Figures 82-86. The embodiments of the call records of the present
invention
comprise both 32-word and 64-word call record formats. It would be apparent to
one skilled
in the relevant art to develop alternative embodiments for call records
comprising a different
number of words and different field definitions. Table 301 of the Appendix
contains an
example embodiment of the CDR and PNR call record formats. Figure 84 shows a
graphical
representation of the CDR and PNR call record formats. Table 302 of the
Appendix contains
15 an example embodiment of the ECDR and EPNR call record formats. Figures 85A
and 85B
show a graphical representation of the ECDR and EPNR call record formats.
Table 303 of
the Appendix contains an example embodiment of the OSR and POSR call record
formats.
Figure 86 shows a graphical representation of the OSR and POSR call record
format. Table
304 of the Appendix contains an example embodiment of the EOSR and EPOSR call
record
2o formats. Figures 87(A) and 87(B) show a graphical representation of the
EOSR and EPOSR
call record formats. Table 305 of the Appendix contains an embodiment of the
SER record
format. Figure 88 shows a graphical representation of the SER record format.
The CDR and PNR, and thereby the ECDR and EPNR, are standard call record
formats and
25 contain information regarding a typical telephone call as it passes through
a switch. The
CDR is used for a non-VNET customer, whereas the PNR is used for a VNET
customer and
is generated at switches that originate VNET calls. T'he fields of these two
records are
identical except for some field-specific information described below.
3o The OSR and POSR, and thereby the EOSR and EPOSR, contain information
regarding a
telephone call requiring operator assistance and are generated at switches or
systems actually
equipped with operator positions. A switch completes an OSR for a non- VNET
customer
and completes a POSR for a private VNET customer. These records are only
generated at
475
CA 02279845 1999-OS-17
WO 98/23080 PCT/ITS97/21174
switches or systems that have the capability of performing operator services
or network audio
response system (MARS) functions. The formats of the two (2) records are
identical except
for some field-specific information described below.
A SER is reserved for special events such as the passage of each hour mark,
time changes,
system recoveries, and at the end of a billing block. The SER record format is
also described
in more detail below.
Figures 89(A) and 89(B) collectively illustrate the logic that a switch uses
to determine when
to use an expanded version of a record format. A call 30202 comes into a
switch 30106-
30110 (called the current switch for reference purposes; the current switch is
the switch that
is currently processing the call), at which time that switch 30106-30110
determines what call
record and what call record format (small/default or large/expanded) to use
for the call's
30802 call record. In this regard, the switch 30106-30110 makes nine (9)
checks for each call
30802 that it receives. The switch 30106-30110 uses an expanded record for a
call 30802
15 that passes any check as well as for a call 30802 that passes any
combination of checks.
The first check 30804 determines if the call is involved in a direct
termination overflow
(DTO) at the current switch 30106-30110. For example, a DTO occurs when a
customer
makes a telephone call 30802 to an 30800 number and the original destination
of the 800
2o number is busy. If the original destination is busy, the switch overflows
the telephone call
30802 to a new destination. In this case, the switch must record the
originally attempted
destination, the final destination of the telephone call 30802. and the number
of times of
overflow. Therefore, if the call 30802 is involved in a DTO, the switch 30106-
30110 must
complete an expanded record (ECDR, EPNR, EOSR, EPOSR) 30816.
The second check 30806 made on a call 30802 by a switch 30106-30110 determines
if the
calling location of the call 30802 is greater than ten ( 10) digits. The
calling location is the
telephone number of the location from where the call 30802 originated. Such an
example is
an international call which comprises at least eleven (11 ) digits. If the
calling location is
greater than ten ( 10) digits, the switch records the telephone number of the
calling location in
an expanded record (ECDR, EPNR, EOSR, EPOSR} 30816.
A switch 30106-30110 makes a third check 30808 on a call 30802 to determine if
the
476
CA 02279845 1999-OS-17
WO 98/23080 - PCT/US97/21174
destination address is greater than seventeen ( 17) digits. The destination
address is the
number of the called location and may be a telephone number or trunk group. If
the
destination is greater than seventeen ( 17) digits) the switch records the
destination in an
expanded record (ECDR, EPNR, EOSR, EPOSR) 30816.
A switch 30106-30110 makes a fourth check 30810 on a call 30802 to determine
if the pre-
translated digits field is used with an operated assisted service call. The
pre-translated digits
are the numbers of the call 30802 as dialed by a caller if the call 30202 must
be translated to
another number within the network. Therefore, when a caller uses an operator
service, the
to switch 30106-30110 records the dialed numbers in expanded record (EOSR,
EPOSR) 30816.
In a fifth check 30812 on a call 30802, a switch 30106-30110 determines if the
pre-translated
digits of a call 30802 as dialed by a caller without operator assistance has
more than ten ( 10)
digits. If there are more than ten ( 10) pre-translated digits, the switch
30106-30110 records
the dialed numbers in expanded record (ECDR, EPNR) 30816.
In a sixth check 30814 on a call 30802, a switch 30106-30110 determines if
more than
twenty-two (22) digits, including supplemental data, are recorded in the
Authorization Code
field of the call record. The Authorization Code field indicates a party who
gets billed for
2o the call, such as the calling location or a credit card call. If the data
entry requires more than
twenty-two. (22) digits, the switch 30106-30110 records the billing
information in an
expanded record (ECDR, EPNR, EOSR, EPOSR) 30816.
In a seventh check 30820 on a call 30802, a switch 30106-30110 determines if
the call 30802
is a wideband call. A wideband call is one that requires multiple transmission
lines, or
channels. For example, a typical video call requires six (6) transmission
channels : one ( 1 )
for voice and five (5) for the video transmission. The more transmission
channels used
during a wideband call results in a better quality of reception. Contemporary
telecommunication systems currently provide up to twenty-four (24) channels.
Therefore, to
3o indicate which, and how many, of the twenty-four channels is used during a
wideband call,
the switch records the channel information in an expanded record (ECDR, EPNR)
30828.
In an eighth check 30822 on a call 30802, a switch 30106-30110 determines if
the time and
477
CA 02279845 1999-OS-17
wo ~3oso rc~rrt~s~~nma
charges feature was used by an operator. The time and charges feature is
typically used in a
hotel scenario when a hotel guest makes a telephone call using the operator's
assistance and
charges the call 30802 to her room. After the call 30802 has completed, the
operator informs
_ the hotel guest of the charge, or cost, of the call 30802. If the time and
charges feature was
used with a call 30802, the switch 30106-30110 records the hotel guest's name
and room
number in an expanded record (EOSR, EPOSR) 30832.
The ninth, and final, check 30824 made on a call 30802 by a switch 30106-30110
determines
if the call 30802 is an enhanced voice service/network audio response system
(EVS/NARS)
o call. An EVS/NARS is an audio menu system in which a customer makes
selections in
response to an automated menu via her telephone key pad. Such a system
includes a NARS
switch on which the audio menu system resides. Therefore, during an EVS/NARS
call
30802, the NARS switch 30106-30110 records the customer's menu selections in
an
expanded record (EOSR, EPOSR) 30832.
is
If none of the checks 30804-30824 return a positive result, then the switch
30106-30110 uses
the default record format (OSR, POSR) 30830.
Once the checks have been made on a call, a switch generates and completes the
appropriate
call record. Call record data is recorded in binary and Telephone Binary Coded
Decimal
20 (TBCD) format. TBCD format is illustrated below:
0000 = TBCD-Null
0001 = digit 1
0010 = digit 2
0011 = digit 3
25 0100 = digit 4
O 1 O I = digit 5
0110 = digit 6
Ol 11 = digit 7
1000 = digit 8
30 1001 = digit 9
1010 = digit 0
1011 = special digit 1 (DTMF digit A)
1100 = special digit 2 (DTMF digit B)
478
CA 02279845 1999-OS-17
WO PCT/US97/21174 -
1101 = special digit 3 (DTMF digit C)
1110 = special digit 4 (DTMF digit D)
11 I 1 = special digit 5 (Not Used)
All TBCD digit fields must be filled with TBCD-Null, or zero, prior to data
being recorded.
Where applicable, dialed digit formats conform to these conventions
N = digits 2-9 _
X = digits 0-9
Y = digits 2-8
Thus, if the specification for a call record field contains a N, the valid
field values are the
digits 2-9.
Each call record, except SER, contains call specific timepoint fields. The
timepoint fields are
~ 5 recorded in epoch time format. Epoch time is the number of one second
increments from a
particular date/time in history. The embodiment of the present invention uses
a date/time of
midnight (00:00 am UTC) on January 1, 1976, but this serves as an example and
is not a
limitation. It would be readily apparent to one skilled in the relevant art to
implement an
epoch time based on another date/time. In the records, Timepoint 1 represents
the epoch time
2o that is the origination time of the call 30802. The other timepoint stored
in the records are the
number of seconds after Timepoint 1, that is, they are offsets from Timepoint
1 that a
particular timepoint occurred. All of the timepoint fields must be filled in
with "0's" prior to
any data being recorded. Therefore, if a timepoint occurs, its count is one (
1 ) or greater.
Additionally, timepoint counters. not including Timepoint 1, do not rollover
their counts, but
25 stay at the maximum count if the time exceeds the limits.
The switch clock reflects local switch time and is used for all times except
billing. Billing
information is recorded in epoch time. which in this embodiment is UTC. The
Time offset is
a number reflecting the switch time relative to the U'rC, that is) the offset
due to time zones
3o and, if appropriate, daylight savings time changes. There are three factors
to consider when
evaluating time change relative to UTC. First, there are time zones on both
sides of UTC,
and therefore there may be both negative and positive offsets. Second. the
time zone offsets
count down from zero (in Greenwich, England) in an Eastward direction until
the
479
CA 02279845 1999-OS-17
WO 98/23080 _ PGT/US97/21174
International Dateline is reached. At the Dateline, the date changes to the
next day, such that
the offset becomes positive and starts counting down until the zero offset is
reached again at
Greenwich. Third, there are many areas of the world that have time zones that
are not in
exact one-hour increments. For example, Australia has one time zone that has a
thirty (30)
minute difference from the two time zones on either side of it, and Northern
India has a time
zone that is fifteen (15) minutes after the one next to it. Therefore, the
Time Offset of the call
records must account for variations in both negative and positive offsets in
fifteen (15)
minute increments. The embodiment of the present invention satisfies this
requirement by
providing a Time Offset representing either positive or negative one minute
increments.
to
There are two formulas used to convert local switch time to epoch time and
back.
i) Epoch Time + (Sign Bit * Time Offset) = Local Switch Time
ii) Local Switch Time - (Sign Bit * Time Offset) = Epoch Time
The switch records the Time Offset in the SER using a value where one ( 1 )
equals one ( 1 )
minute, and computes the Time Offset in seconds and adds this value to each
local Timepoint
1 before the call record is recorded. For example, Central Standard Time is
six (6) hours
before UTC. In this case, the Sign Bit indicates " 1 " for negative offset and
the Time Offset
value recorded in the SER would be 360 (6 hours * 60 minutes/hour = 360
minutes). See
Figure 86 for more details on the SER record format. When recording Timepoint
I in the call
record, the switch multiplies the Time Offset by 60, because there is 60
seconds in each 1
minute increment, and determines whether the offset is positive or negative by
checking the
Sign Bit. This example results in a value of -21,600 (-1 * 360 minutes* 60
seconds/minute = -
21,600 seconds). Using equation (ii) from above, if the local switch time were
midnight, the
corresponding epoch time might be, for example, 1,200,000,000. Subtracting the
Time
Offset of -21,600 results in a corrected epoch time of 1,200,021,600 seconds,
which i s the
epoch time for 6 hours after midnight on the next day in epoch time. This
embodiment works
equally as well in switches that are positioned on the East side of Greenwich
where the Time
3o Offset has a positive value.
Two commands are used when changing time. First, Figure 90 illustrates the
control flow of
the Change Time command 30900, which changes the Local Switch Time and the
Time
480
CA 02279845 1999-OS-17
WO 98/Z30$0 PCT/(1S97/21174
Offset. In Figure 90, after a switch operator enters the Change Time command,
the switch
enters step 30902 and prompts the switch operator for the Local Switch Time
and Time
Offset from UTC. In step 30902 the switch operator enters a new Local Switch
Time and
Time Offset. Continuing to step 30904, the new time and Time Offset are
displayed back to
the switch operator. Continuing to step 30906, the switch operator must verify
the entered
time and Time Offset before the actual time and offset are changed on the
switch. If in step
30906 the switch operator verif es the changes, the switch proceeds to step
30908 and
generates a SER with an Event Qualifier equal to two which identi .fees that
the change was
made to the Local Switch Time and Time Offset of the switch. The billing
center uses the
SER for its bill processing. The switch proceeds to step 30910 and exits the
command.
Referring back to step 30906, if the switch operator does not verify the
changes, the switch
proceeds to step 30910 and exits the command without updating the Local Switch
Time and
Time Offset. For more information on SER, see Figure 86.
~ 5 Figure 91 illustrates the control flow for the Change Daylight Savings
Time command 31000
which is the second command for changing time. In Figure 91, after a switch
operator enters
the Change Daylight Savings Time command, the switch enters step 31002 and
prompts the
switch operator to select either a Forward or Backward time change. Continuing
to step
31004, the switch operator makes a selection. In step 31004, if the switch
operator selects the
zo Forward option, the switch enters step 31006. In step 31006, the switch
sets the Local Switch
Time forward one hour and adds one hour (count of GO) to the Time Offset. The
switch then
proceeds to step 31010. Referring back to step 31004, if the switch operator
selects the
Backward option, the switch sets the Local Switch Time back one hour and
subtract one hour
(count of 60) from the Time Offset. The switch then proceeds to step 31010.
In step 31010, the switch operator must verify the forward or backward option
and the new
Local Switch Time and Time Offset before the actual time change takes place.
If in step
31010, the switch operator verifies the new time and Time Offset, the switch
proceeds to step
31012 and generates a SER with an Event Qualifier equal to nine which changes
the Local
3o Switch Time and Time Offset of the switch. The switch proceeds to step
31014 and exits the
command. Referring back to step 31010, if the switch operator does not verify
the changes,
the switch proceeds to step 31014 and exits the command without updating the
Local Switch
Time and Time Offset.
-- 481
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174 -
After the successful completion of a Change Daylight Savings Time Command, the
billing
records are affected by the new Time Offset. This embodiment allows the epoch
time, used
as the billing time, to increment normally through the daylight savings time
change
procedure, and not fo be affected by the change of Local Switch Time and Time
Offset.
2. Network Call Identifier
An embodiment provides a unique NCID that is assigned to each telephone call
that traverses
through the telecommunications network. Thus, the NCID is a discrete
identifier among all
t o network calls. The NCID is transported and recorded at each switch that is
involved with the
telephone call.
The originating switch of a telephone call generates the NCID. The chosen
embodiment of
the NCID of the present invention is an eighty-two (82) bit identif er that is
comprised of the
t 5 following subfields:
i) Originating Switch ID ( 14 bits) : This field represents the NCS Switch ID
as defined
in the Office Engineering table at each switch. The SER call record, however,
contains an -
alpha numeric representation of the Switch ID. Thus, a switch uses the
alphanumeric Switch
2o ID as an index into a database for retrieving the corresponding NCS Switch
ID.
ii) Originating Trunk Group ( 14 bits) : This field represents the originating
trunk group
as defined in the 32/64-word call record format described above.
25 iii) Originating Port Number ( 19 bits) : This field represents the
originating port number
as defined in the 32/64-word call record format described above.
iv) Timepoint 1 (32 bits) : This field represents the Timepoint 1 value as
defined in the
32/64-word call record format described above.
v) Sequence Number (3 bits) : This field represents the number of calls which
have
occurred on the same port number with the same Timepoint 1 (second} value. The
first
482
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
telephone call will have a sequence number set to '0.' This value increases
incrementally for
each successive call which originates on the same port number with the same
Timepoint 1
value.
It would be readily apparent to one skilled in the relevant art to create an
NCID of a different
format. Each switch records the NCID in either the 32 or 64-word call record
format.
Regarding the 32-word call record format, intermediate and terminating
switches will record
the NCID in the AuthCode field of the 32-word call record if the AuthCode
filed is not used
to record other information: In this case, the Originating Switch ID is the
NCS Switch ID,
to not the alphanumeric Switch ID as recorded in the SE;R call record. If the
AuthCode is used
for other information, the intermediate and terminating switches record the
NCID in the 64-
word call record format. In contrast, originating switches do not use the
AuthCode field
when storing an NCID in a 32-word call record. Originating switches record the
subfields of
the NCID in the corresponding separate fields of the 32-word cal t record.
That is, the
~ 5 Originating Switch ID is stored as an alphanumeric Switch ID in the Switch
ID field of the
SER call record; the Originating Trunk Group is stored in the Originating
Trunk Group field
of the 32-word call record; the Originating Port Number is stored in the
Originating Port field
of the 32-word call record; the Timepoint I is stored in the Timepoint 1 field
of the 32-word
call record; the Sequence Number is stored in the NC1:D Sequence Number field
of the 32-
20 word call record. The 32-word call record also includes an NCID Location
(NCIDLOC) field
to identify when the NCID is recorded in the AuthCode field of the call
record. If the NCID
Location field contains a 'l,' then the AuthCode field contains the NCID. If
the NC1D
Location field contains a '0,' then the NCID is stored in its separate sub-
fields in the call
record. Only intermediate and terminating switches set the NCID Location field
to a ' 1'
25 because originating switches store the NCID in the separate fields of the
32-word call record.
Regarding the 64-word call record format, the expanded call record includes a
separate field,
call the NCID field, to store the 82 bits of the NCID. 'This call record is
handled the same
regardless of whether an originating, intermediate, or germinating switch
stores the NCID. In
3o the 64-word call record format, the Originating Switch ID is the NCS Switch
ID, not the
alphanumeric Switch ID as recorded in the SER call record.
- Figure 92 illustrates the control flow of the Network Call Identifier switch
call processing. A
483
CA 02279845 1999-OS-17
WO 98/23080 PGT/US97/21174
call 30202 comes into a switch 30106-30110 (called the current switch for
reference
purposes; the current switch is the switch that is currently processing the
call) at step 31104.
In step 31104, the current switch receives the call 30202 and proceeds to step
31106. In step
31106, the current switch accesses a local database and gets the trunk group
parameters
associated with the originating trunk group of the call 30202. After getting
the parameters,
the current switch proceeds to step 31108. In step 31108) the current switch
determines if it
received an NCID with the call 30202. If the current switch did not receive an
NCID with
the call 30202, the switch continues to step 31112.
In step 31112, the switch analyzes the originating trunk group parameters to
determine the
originating trunk group type. If the originating trunk group type is an
InterMachine Trunk
(IMT) or a release link trunk (RLT), then the switch proceeds to step 31116.
An IMT is a
trunk connecting two normal teiecommunication switches, whereas a RLT is a
trunk
connecting an intelligent services network (1SN) platform to a normal
telecommunication
t 5 switch. When the current switch reaches step 31116, the current switch
knows that it is not
an originating switch and that it has not received an NCID. In step 31116, the
current switch
analyzes the originating trunk group parameters to determine whether it is
authorized to
create an NCID for the call 30202. In step 31116, if the current switch is not
authorized to
create an NCID for the call 30202, the current switch proceeds to step 31118.
When in step
20 31118, the current switch knows that it is not an originating switch, it
did not receive an
NCID for the call 30202, but is not authorized to generate an NCID. Therefore,
in step
31118, the current switch writes the call record associated with the call
30202 to the local
switch database and proceeds to step 31120. In step 31120, the current switch
transports the
call 30202 out through the network with its associated NCID. Step 31120 is
described below
25 in more detail.
Referring again to step 31116, if the current switch is authorized to create
an NCID for the
call 30202, the current switch proceeds to step 31114. In step 31114, the
current switch
generates a new NCID for the call 30202 before continuing to step 31136. In
step 31136, the
3o current switch writes the call record, including the NCID, associated with
the call 30202 to
the local switch database and proceeds to step 31120. In step 31120, the
current switch
transports the call 30202 out through the network with its associated NCID.
Step 31120 is
described below in more detail.
484
CA 02279845 1999-OS-17
PCT/US97121174
Referring again to step 31112, if the current switch determines that the
originating trunk
group type is not an IMT or RLT, the current switch proceeds to step 31114.
When reaching
step 31114, the cun:ent switch knows that it is an originating switch and,
therefore, must
generate a NCID for the call 30202. Step 31114 is described below in more
detail. After
generating a NCID in step 31114, the current switch proceeds to step 31136 to
write the call
record, including the NCID, associated with the call 30202 to the local
database. After
writing the call record, the current switch proceeds to step 31120 to
transport the call out
through the network with its associated NCID. Step 31120 is also described
below in more
t o detail.
Refernng again to step 31108, if the current switch determines that it
received an NCID with
the call 30202, the current switch proceeds to step 31110. In step 31110, the
current switch
processes the received NCID. In step 31110, there are two possible results.
First, the current
~ 5 switch may decide not to keep the received NCID thereby proceeding from
step 31110 to step
31114 to generate a new NCID. Step 31110 is described below in more detail. In
step
31114, the current switch may generate a new NCII) for the call 30202 before
continuing to
step 31136. Step 31114 is also described below in more detail. In step 31136,
the current
switch writes the call record associated with the call 30202 to the local
database. The current
2o switch then proceeds to step 31120 and transports the call 30202 out
through the network
with its associated NCID. Step 31120 is also described below in more detail.
Referring again to step 31110, the current switch may decide to keep the
received NCID
thereby proceeding from step 31110 to step 31115. In step 31115, the current
switch adds the
25 received NCID to the call record associated with the call 30202. Steps
31110 and 31115 are
described below in more detail. After step 31115, the current switch continues
to step 31136
where it writes the call record associated with the call 30202 to the local
database. The
current switch then proceeds to step 31120 and transports the call 30202 out
through the
network with its associated NCID. Step 31120 is also described below in more
detail.
' Figure 93 illustrates the control logic for step 31110 which processes a
received NCID. The
current switch enters step 31202 of step 31110 when it determines that an NCID
was received
with the call 30202. In step 31202, the current switch analyzes the
originating trunk group
485
CA 02279845 1999-OS-17
WO 98/23080 PCTlUS97/21174
parameters to determine the originating trunk group type. If the originating
trunk group type
is an IMT or RLT, then the current switch proceeds to step 31212. When in step
31212, the
current switch knows that it is not an originating switch and that it received
an NCID for the
call 30202. Therefore, in step 31212, the current switch keeps the received
NCID and exits
step 31110, thereby continuing to step 31115 in Figure 92, after which the
current switch will
store the received NCID in the call record and transport the call.
Referring again to step 31202, if the originating trunk group type is not an
IMT or RLT, the
current switch proceeds to step 31204. In step 31204, the current switch
determines if the
1o originating trunk group type is an Integrated Services User Parts Direct
Access Line (ISUP
DAL) or an Integrated Services Digital Network Primary Rate Interface (ISDN
PRI). ISUP
is a signaling protocol which allows information to be sent from switch to
switch as
information parameters. An ISUP DAL is a trunk group that primarily is shared
by multiple
customers of the network, but can also be dedicated to a single network
customer. In
15 contrast, an ISDN PRI is a trunk group that primarily is dedicated to a
single network
customer, but can also be shared by multiple network customers. A network
customer is an
entity that leases network resources. In step 31204, if the current switch
determines that the
trunk group type is not an ISUP DAL or ISDN PRI, the current switch proceeds
to step
31206. When in step 31206, the current switch knows that it received an NCID
that was not
2o generated by a switch that is part of the telecommunication network or by a
switch that is a
customer of the network. Therefore, in step 31206, the current switch discards
the received
NCID because it is an unreliable NCID. From step 31206, the current switch
exits step
31110, thereby continuing to step 31114 in Figure 92 where the current switch
will create a
new NCID and transport that NCID with the call 30202.
Referring back to step 31204, if the current switch determines that the
originating trunk group
type is an ISUP DAL or ISDN PRI, the current switch continues to step 31208.
When in step
31208, the current switch knows that it received an NCID from a customer trunk
group.
Therefore, the current switch analyzes the originating trunk group parameters
to determine
3o whether it is authorized to create a new NCID for the call 30202. The
current switch may be
authorized to create a new NCID and overwrite the NCID provided by the
customer to ensure
that a valid NCID corresponds to the call 30202 and is sent through the
network. In step
31208, if the current switch is not authorized to create a new NCID for the
call 30202, the
486
CA 02279845 1999-OS-17
WO 98/2380 PGT/US97/21174
current switch proceeds to step 31210. In step 31210, the current switch
checks the validity
of the received NCID, for example, the NCID length. 1f the received NCID is
invalid, the
current switch proceeds to step 31206. In step 31206, the current switch
discards the invalid
NC1D. From step 31206, the current switch exits step 31110, thereby continuing
to step
31114 in Figure 92 where the current switch will create a new NCID and
transport that NCID
with the call 30202.
. Referring again to step 31210, if the current switch determines that the
received NCID is
valid, the current switch proceeds to step 31212. In step 31212 the current
switch keeps the
received NCID and exits step 31110, thereby continuing to step 31115 in Figure
92 where the
t o current switch will store the received NCID in the call record and
transport the call.
Figure 94A illustrates the control logic for step 31114 which generates an
NCID. The
current switch enters step 31302 when an NCID must be created. In step 31302,
the current
switch will calculate a sequence number. The sequence number represents the
number of
t s calls which have occurred on the same port number with the same Timepoint
1 value. The
first call has a sequence number value of '0,' after which the sequence number
will increase
incrementally for each successive call that originates on the same port number
with the same
Timepoint 1 value. After creating the sequence number in step 31302, the
current switch
proceeds to step 31304. In step 31304, the current switch creates a call
record for the call
20 30202, including in it the call's 30202 newly created NCID. After the call
record has been
created, the current switch exits step 31114 and proceeds to step 31136 in
Figure 92 where
the current switch writes the call record to the local switch database.
Figure 94B illustrates the control logic for step 3111 which adds a received
NCID to the
25 call record associated with the call 30202. Upon entering step 31115, the
current switch
enters step 31306. When in step 31306, the current switch knows that it has
received a valid
NCID from an intermediate or terminating switch, or from a customer switch. In
step 31306,
the current switch determines if the AuthCode field of the 32-word call record
is available for
storing the NCID. If the AuthCode field is available, the current switch
proceeds to step
30 31310. In step 31310, the current switch stores the NCID in the AuthCode
field of the 32-
- word call record. The current switch must also set the NCID Location field
to the value ' 1'
which indicates that the NCID is stored in the AuthCode field. After step
31310, the current
switch exits step 31115 and continues to step 31136 in Figure 92 where the
current switch
487
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97121l74
writes the call record to the local switch database.
Referring again to step 31306, if the AuthCode field is not available in the
32-word call
record, the current switch proceeds to step 31308. In step 31308, the current
switch stores the
NCID in the NCID field of the 64-word call record. After step 31308, the
current switch
exits step 31115 and continues to step 31136 in Figure 92 where the current
switch writes the
call record to the local switch database.
Figure 95 illustrates the control logic for step 31120 which transports the
call from the
current switch. There are two entry points for this control logic: steps 31402
and 31412.
Upon entering step 31402 from step 31136 on Figure 92, the current switch
knows that it has
created an NCID or has received a valid NCID. In step 31402, the current
switch accesses a
local database and gets the trunk group parameters associated with the
terminating trunk
group for transporting the call 30202. After getting the parameters, the
current switch
proceeds to step 31404. In step 31404, the current switch determines the
terminating trunk
group type. If the terminating trunk is an ISUP trunk, the current switch
proceeds to step
31408. In step 31408, the current switch analyzes the parameters associated
with the ISUP
trunk type to determine whether or not to deliver the NCID to the next switch.
If the current
switch is authorized to deliver the NCID, the current switch proceeds to step
31416. In step
31416, the current switch transports the call to the next switch along with a
SS7 initial
address message (IAM). The NCID is transported as part of the generic digits
parameter of
the IAM. The IAM contains setup information for the next switch which prepares
the next
switch to accept and complete the call 30202. The format of the generic digits
parameter is
shown below in Table 306
Generic Digits Parameter
Code: 11000001
Type: 0
Byte #, Bit # Description
488
CA 02279845 1999-OS-17
WO 98/23080 - PCT/US97/21174
byte 1, bits Type of Digits : Indicates the contents
0-4 of the parameter.
This field has a binary value of ' 11
O 11' to indicate that
the parameter contains the NCID.
byte 1, bits Encoding Scheme : Indicates the format
5-7 of the parameter
contents. This field has a binary value
of '011' to
indicate that the NCID is stared in the
binary format.
byte 2, bits Originating Switch ID
0-7
byte 3, bits
0-5
byte 3, bits Originating Trunk Group
6-7
byte 4, bits
0-7
byte 5, bits
0-3
byte 5, bits Originating Port Number
4-7
byte 6, bits
0-7
byte 7, bits
0-6
byte 7, bit Not Used
7
byte 8, bits Timepoint 1
0-7
byte 9, bits
0-7
byte 10, bits
0-7
byte I 1, bits
0-7
byte 12, bits NCID Sequence Number
0-2
byte 12, bits Not Used
3-7
Table 306
489
CA 02279845 1999-OS-17
W0.98I23080 PG"T/US97/21174
After transporting the call 30202 and the IAM, the current switch proceeds to
step 31418,
thereby exiting the switch processing.
Referring again to step 31408, if the current switch is not authorized to
deliver the NCID to
the next switch in an IAM message, the current switch proceeds to step 31412.
In step
31412, the current switch transports the call 30202 to the next switch under
normal
procedures which consists of sending an IAM message to the next switch without
the NCID
recorded as part of the generic digits parameter. After transporting the call
30202, the current
switch proceeds to step 31418, thereby exiting the switch processing.
Referring again to step 31404, if the current switch determines that the
terminating trunk is
not an ISUP, the current switch proceeds to step 31406.
In step 31406, the current switch determines if the terminating trunk group is
an ISDN trunk
(the terminating trunk group is dedicated to one network customer). If the
terminating trunk
group is an ISDN, the current switch proceeds to step 31410. In step 31410,
the current
switch analyzes the parameters associated with the ISDN trunk group type to
determine
whether or not to deliver the NCID to the next switch. If the current switch
is authorized to
deliver the NCID, the current switch proceeds to step 31414. In step 31414,
the current
switch transports the call to the next switch along with a setup message. The
setup message
2o contains setup information for the next switch which prepares the next
switch to accept and
complete the call 30202. The NCID is transported as part of the locking shift
codeset 6 _
parameter of the setup message. The format of the locking shift codeset 6
parameter is
shown below in Table 307
Locking Shift Codeset 6 Parameter
Code: 11000001
Type: 0
Byte #, Bit # Description
490
CA 02279845 1999-OS-17
WO 98/23080 _ PCT/US97121174
byte I, bits Type of Digits : Indicates the contents
0-4 of the parameter.
This field has a binary value of ' 11011'
to indicate that
the parameter contains the NCID.
byte 1, bits Encoding Scheme : Indicates the format
5-7 of the parameter
contents. This field has a binary value
of '011' to
indicate that the NCID is stored in the
binary format.
byte 2, bits Originating Switch ID
0-7
byte 3, bits
0-S
byte 3, bits Originating Trunk Group
6-7
byte 4, bits
0-7
byte 5, bits
0-3
byte S, bits Originating Port Number
4-7
byte 6, bits
0-7
byte 7, bits
0-6
byte 7, bit.7 Not Used
byte 8, bits Timepoint 1
0-7
byte 9, bits
0-7
byte 10, bits
0-7
byte 11, bits
0-7
byte 12, bits NCID Sequence Number
0-2
byte 12, bits Not Used
3-7
Table 307
491
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
After transporting the call 30202 and the setup message, the current switch
proceeds to step
- 31418, thereby exiting the switch processing.
Referring again to step 31410, if the current switch determines that it does
not have authority
to deliver the NCID to the next switch in a setup message, the current switch
proceeds to step
31412. In step 31412, the current switch transports the call 30202 to the next
switch under
normal procedures which consists of sending a setup message to the next switch
without the
NCID recorded as part of the locking shift codeset 6 parameter. After
transporting the call
t o 30202; the current switch proceeds to step 31418, thereby exiting the
switch processing.
Referring again to step 31412, this step is also entered from step 31118 on
Figure 92 when
the current switch did not receive an NCID, is an intermediate or terminating
switch, and is
not authorized to create an NCID. In this case, in step 31412, the current
switch also
15 transports the call 30202 to the next switch under normal procedures which
consists of
sending an IAM or setup message to the next switch without the NCID recorded
as part of the
parameter. After transporting the call 30202, the current switch proceeds to
step 31418,
thereby exiting the switch processing.
2o A system and method for the switches of a telecommunications network to
generate call
records for telephone calls using a flexible and expandable record format.
Upon receipt of a
telephone call, a switch in the network analyzes the telephone call to
determine whether the
default call record is sufficiently large to store call record information
pertaining to the
telephone call, or whether the expanded call record must be used to store the
call information
25 pertaining to the telephone call. After determining which call record to
use, the switch
generates the default or expanded call record. The switch sends a billing
block, comprised of
completed call records, to a billing center upon filling an entire billing
block.
While various embodiments have been described above, it should be understood
that they
30 have been presented by way of example only, and not limitation. Thus, the
breadth and scope
of a preferred embodiment should not be limited by any of the above described
exemplary
embodiments, but should be defined only in accordance with the following
claims and their
equivalents.
492
CA 02279845 1999-OS-17
WO 9880 PCT/US97I211'74
- APPENDIX
Table 301 - CDR/PNR Record Fot~mat~
Word #) Bit # Description
Word 0, bits 0-3 Call Record Id (GRID): Identifies the
record type.
0 = Default
1 = CDR
2 = SER
3 = PNR
4 = OSR
5 = POSR
6 = ECDR
7 = EPNR
8 = EOSR
9 = EPOSR
10-IS = Not Used
Word 0, bits 4-15 Call Disconnect ID (CDID): Identifies
the call record. Each call
record has a unique ID number. These
12 bits contain the 12 least
significant bits of the CDID.
Word 1, bits 0-I S Timepoint 1 (TPI ): A binary count of
the number of seconds that
Word 2, bits 0-15 occurred- between midnight (UTC) on January
1) 1976, and the
tithe that the incoming call was detected
by the switch.
Word 3, bits 0-12 Timepoint 3 (TP3): A binary count of
the number of seconds
between Titnepoint 1 and the time the
outgoing signalling protocol
was completed; that is, the number of
seconds that it took for the
switch to connect to the outgoing trunk.
Word 3, bits 13-15 Titnepoint 6 (TP6;1: A binary count of
the number of seconds
Word 4) bits 0-9 between timepoint 1 and the time Answer
Supervision was
detected or received. This is the time
that it took for the call to be
answered by the person or audio system
being called.
Word 4, bits 10-15 Timepoint 7 (TP7;1: A binary count of
the nutnt>er v. seconds
Word S) bits 0-15 between timepoint 1 and the time that
the originating or -
terminating parry disconnected vrhichever
is first.
Word 6, bits 0-15 Originating Port (OP): The absolute port
number of the originating
Word 7) bits 0 trunk. Originating trunk is the line
on which the call came to the
switch.
Word 7, bits 1-15 Terminating Port (TP): The absolute port
number of the last
Word 8) bits 0-1 terminating trunk seized for an outgoing
call attempt. The
terminating trunk is the last line on
which the call is transmitted.
Word 8, bits 2-14 Originating Trunk Gmup (OTG): A binary
number expressing the
Originating Trunk Group number of the
ot~iginating trunk. An
originating trunk group is a group of
ports coming from the same
I location.
Word 8, bits l5 Terminating Trunk Group (TTG): A binary
number expressing the
Word 9, bits 0-11 Terminating Trunk: Group number of the
Terminating trunk. A
terminating trunk group is a group of
ports going to the same
location. If a call fails because no
trunks are available) record the
last trunk group number that was attempted.
493
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
Word 1I) Bit ~ Description
Word 9, bits 12-15 Timepoint 3 qualifier (TP3Q): Contains
the outpulsed call
disposition qualifier which provides the
telephone number of the
person making the call to the person being
called. The person
being called needs to have signed up for
the "ANI Delivery"
service and have a display device for
displaying the caller's
telephone number.
0 = Default
1 = ANI/CSI was delivered
2 = DNIS was delivered--
3 = ANI/CSI and DNIS were delivered
4-S = Not Used
6 = NCT
7 = NCT, ANI/CSI was delivered
8 = NCT) DNIS was delivered
9 = NCT, ANI/CSI and DNIS was delivered
10 = NCT Tandem
11-15 = Not Used
Word 10) bits 0-1 Titnepoint 6 qualifier (TP6Q): Contains
the answer supervision
qualifier indicating the way in which
the telephone call was
answered.
0 = Hardware detected an Answer
_ 1 = Software detected Voice
2 = Not Used
3' = Operator/NARS detected an Answer
* Not Used in CDR/PNR
Word 10, bits 2-7 Action Code (AC): The switch provides
an action code which
indicates the type of destination address,
or what type of telephone
number was called) or an error code.
494
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/230 PCT/L1S97/21174
~.
Word ~Y, Bit ~ Description
0 = Default
1 = 7-digit number without overflow
2 = 7-digit number with overflow
3 = DDD number
4 = IDDD number
5 = Switch generated Action Code
6 = Incoming exclusion failure
7 = ID code failure
8 = Unexp~ted error occurs in the NCS/DAP
9 = Misdialed number and the NCS/DAP is
unable to translate
the dialed number
10 = 10-digit number without overflow
11 = 10-digit number with overflow
12 = National with overflow
13 = International with overflow
14 = ANI not fowid
15 = NPA-NXXX not found
16 = Pilot number not found
17 = Associated partition not found
18 = ADF format error
19 = Switch ID not found
20 = 800 number not found
21 = 800 number out of band
22 = 800 number no longer in service
23 = Invalid ID code
24 = Range privilege
25 = ?-digit number not in database
26 = 10-digit exclusion feature
27 = 900 number not found
28 = 900 number out of band
29 = 900 number no longer in service
30 = NCS network management blocked
31 = NCS Gate Denial
32 = FIexSTC) Overflow Not Allowed
33 = FIexSTC, Overflow Allowed
34 = SAC Number Not Found
35 = SAC Number Out of Band
36 = 700 Number Not Found
37 = 700 Number Out of Band
38 = ICR designated Out of Band
39 = NCT - Reversed CaII Direction
40-49 = Not Used
SO = Flexible Direct Termination CaII
without overflow
_- 51 = Flexible Direct Termination Call
with overflow
52 = Outbound VNet without overflow
53 = Outbound IVNet with overflow
54 = Global Switch Profile Not Found
55 = ANI Index Provided by DAP
56-62 = Not Used
63 = Intcrnacional Inbound AAP
495
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PGTIUS97/21I74
Word, Bit # Description
Word 10, bits 8-11 Originating Trunk Class (OTC): Indicates
what type of
originating trunk was accessed.
0 = ONAL (FG-A)
1 = GNAT (FG-B, FG-C, FG-D) CAMA, LAMA)
2 = DAL, VNET CAMA, FGS-DAL)
3 = IMT (Inband or SS7) -
4 = International Circuit (R1) R2, #5)
#6, #7).
5 = ISDN PRI
6 = OST
7-15 = Not Used
FG = Feature Group
Word 10, bits 12-15 Terminating Trunk Class (TTC): Indicates
what type of
terminating trunk was accessed.
0 = ONAL (FG-A)
I = GNAT (FG-B) FG-C) FG-D) CAMA) LAMA)
2 = DAL, VNET CAMA, FGS-DAL)
3 = IMT (Inband or SS7)
4 = International Circuit (R1) R2) #5)
#G, #7)
5 = ISDN PRI
6 = OST
7-15 = Not Used
FG = Feature Group
Word 11, bits 0-7 Information Digits (ID): The switch receives
these digits from the
originating trunk group indicating the
type of telephone on which
the telephone call originated) such as
a home telephone, pay
telephone, or prison telephone.
I
FG-B Direct)
LAMA FG-D MCIIMT #5 #6
bits 0-3:TBCD Null X X TBCD Null X
bits 4-7: X X X X - X
Word l l ) bits Automatic Number Identification (ANI)
8-15 Index Number: The index
number is obtained from the ANI Index
Table for all calls except
800 calls. The ANI number is looked up
to determine whether the
caller is a VNet customer or not. If the
caller is a VNet caller) the
index number is used to look up the destination
address.
496
SUBSTITUTE SHEET (RULE 2B)
CA 02279845 1999-OS-17
PCTIUS97121174
Word ~Y) Bit ~ Description
Word 12, bits 0-15 Call Location ID (CLI): Represents the
10 digits from where the
Word 13, bits 0-15 call came. If switch receives more than
l0 digits, record them in
Word 14, bits 0-7 the ECDR/EPNR. There are nine (9) types
of calling locations:
1. VNet CAMA DAL originations: If CSI
is available) prefix the
CSI with filed HNPA and HNXX information,
if available, and
record. Use NOCL.1 value of 7.
2. FG-C originations: if ANI. or' CSI
information is not available
and the number is in the OOY+NXX+XXXX
format) record the
OOY in CLIl-3) and record the OSID/OTG
in CL14-10. Use
NOCLI value of 8.
3. Inband FG-D Originations: Record the
ANI that was received
starting with CLI1. Use NOCLI value of
1.
4. SS7 FG-D Originations: Record the charge
number, if
available. If not available, record the
tailing party number. Use
NOCLI value of 2 or 3.
S. International otiginations: Record
the country code and the
national number of the calling patty.
Use NOCLI of 9.
6. SS7 IMTs Originations: Record the following
infotTnation in
this order of importance: l) charge number,
2) calling patty
number, 3) OSID/OTG from generic digits.
Use NOCLI of 2) 3,
or 8.
7. SS7 Reseller Originations: The CLI
field is filled with TBCD-
Nulls.
8. SS? Private Network Originations: The
I CL.I field is filled with-
TBCD-Nulls.
I
9. PRI Organizations: Record the calling
parry number received in
the ISDN setup message.
497
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97I21174
Word b, Bit Jf Description
The format:
1-10 digit Incoming
ANI OSID/OTG lnt'1
Word 12, bits 0-3 CLI1 TBCD Null X(CC)
Word 12) bits 4-7 CLI2 TBCD Null X(CC)
Word 12, bits 8-11 CLI3 TBCD Null X(CC)
Word 12, bits 12-15 CL14 X(OSID) X'(NN)
Word 13, bits 0-3 CLIS X(OSID) X(NN)
Word 13, bits 4-7 CLI6 X(OSID) X(NN)
Word 13, bits 8-11 CLI7 X(OTG) X(NN)
Word 13) bits 12-15 CLI8 X(OTG) X(NN)
Word 14, bits 0-3 CLI9 X(O?G) X(NN)
Word 14, bits 4-7 CLI10 X(OTG) X(NN)
CC = Customer Connect
NN = National Number
OSID = Originating Switch NSC 1D (000-999)
OTG = Originating Trunk Group (0000-8191
)
Word 14) bits 8-15 Authorization Codes: Represents 22 digits
of who gets billed for
Word 15, bits 0-15 the call which includes one or more of
the following and/or an
'~ Word 16) bits optional Supplementary Code:
0-15
Word 17) bits 0-15
Word 18, bits 0-15 1. Authorization Code - Contains the authorization
code digits.
Word 19, bits 0-15 AUTH 1-AUTHS records the dialed or filed
authorization codes,
afterwhich is recorded an optional variable
1-4 digit security code,
SECI-SEC4, comprised of TBCD digits 0-9
and A-D. After the
I last digit) record a TBCD-Null) afterwhich
record any
supplementary code digits) SUPP1-SUPP12.
Record TBCD-Null
in any unused byte. Authorization Code
format:
498
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
wo 9sn3oso rc~r~rs9~nma
Word A~, Bit ~ Description
._~
_
5 digit 6 digit 7 digit
Auth Code Auth Auth Code
Code
Word 14) bitsAl AUTHI AUTHI AUTH1
8-11
Word 14, bitsAZ AUTH2 AUTH2 AUTH2
12-15
Word 15, bitsA3 AUTH3 AUTH3 AUTH3
0-3
Word 15, bitsA4 AUTH4 AUTH4 AUTH4
4-7
Word 15, bitsAS AUTHS AUTHS AUTHS
8-1 l
Word I5) bitsA6 SEC1 AUTH6 AUTH6
12:-15
Word 16, bitsA7 SEC2 SEC1 AUTH7
0-3
Word 16, bitsA8 SEC3 SEC2 SEC1
4-7
Word 16, bitsA9 SEC4 SEC3 SEC2.
8-I1
Word 16) bitsA10 TBCD-NuilSEC4 SEC3
12-15
Word 17, bitsA11 SUPPl TBCD-NullSEC4
0-3
Word 17, bitsA12 SUPP2 SUPPI TBCD-Null
4-7
Word 17) bitsA13 SUPP3 SUPP2 SUPPI
8-11
Word 17, bitsA14 SUPP4 SUPP3 SUPP2
12-15
Word 18) bitsA15 SUPPS SUPP4 SUPP3
0-:3
Word 18) bitsA16 SUPP6 SUPPS SUPP4
4=1
Word 18, bitsA17 SUPP7 SUPP6 SUPPS
8-:l l
Word 18, bitsA18 SUPPS SUPP7 SUPP6
12-IS
Word 19) bitsA19 SUPP9 SUPP8 SUPP7
0-a
Word 19) bitsA20 SUPPIO SUPP9 SUPP8
4-;l
Word 19, bitsA21 SUPPI SUPPIO SUPP9
8-'.l l l
Word 19) bitsA22 SUPPI2 SUPPI1 SUPP10
12-IS
499
SUBSTITUTE SHEET (RULE 26~
CA 02279845 1999-OS-17
WO 98/23080 PCT/I1S97/2II74
Word ~, Bit ~Y Description
2. Calling (CSI) -
Station ID Contains
the digits
of the
calling
station identifier. recorded starting
The CSI digits at Al. A
will be
TBCD-Null
is recorded
after the
last CSI
digit, followed
by
Supplemental igits. Unusedcontain a TBCD-Null.
Code d bytes
Calling Station
ID format:
7 digit 10 digit
CSI CSI
Word 14, bitsA1 X X
8-11
Word 14, bitsA2 X X
12-15
Word 15) bitsA3 X X
0-3
Word 15, bitsA4 X X
4-7
Word 15, bitsAS X X
8-11
Word 15) bitsA6 X X
12-15
_
Word 16, bitsA7 X X
0-3
Word 16, bitsA8 TBCD-NullX
4-7
Word 16, bitsA9 SUPPI X
8-11
Word 16) bitsA10 SUPP2 X
12-15
Word 17) bitsA11 SUPP3 TBCD-Null
0-3
Word 17) bitsA12 SUPP4 SUPP1
4-7
Word 17) bitsA13 SUPPS SUPP2
8-11
Word 17, bitsA14 SUPP6 SUPP3
12-15
Word 18, bitsA15 SUPP7 SUPP4
0-3
Word 18, bitsA16 SUPP8 SUPPS
4-7
Word 18, bitsA17 SUPP9 SUPP6
8-11
Word 18, bitsA18 SUPP10 SUPP7
12-15
Word 19) bitsA19 SUPPI SUPP8
0-3 l
Word 19, bitsA20 SUPP12 SUPP9
4-7
Word 19) bitsA21 SUPPI SUPP10
4-11 l
Word 19, bitsA22 SUPP12 SUPP11
12-15
500
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
rc~rrtrs9~nma
Word !!, Bit ~ Description
...~
__
3. Supplementary emental Codes are
Codes - Suppl recorded
starting in bytes
A1. Unused contain
TBCD-Null.
Supplementary
Code format:
_ 800/900 VNet
Supp. Codes
Word 14) bits A1 SUPP1
8-11.
Word 14) bits A2 SUPP2
12-1.5
Word !5) bits A3 SUPP3
0-3
Word 15, bits A4 SUPP4
4-7
Word 15, bits AS SUPPS
8-t 1
Word 15, bits A6 SUPP6
12-15
Word 16) bits A7 SUPP7
0-3
Word 16, bits A8 SUPP8
4-7
Word 16, bits A9 SUPP9
8-11
_ Word 16, bits A10 SUPP10
12-15
Word 17, bits Al SUPPl l
0-3 l
Word 17, bits A12 SUPPI2
4-7
Word t7, bits A13 SUPP13
8-11
Word 17, bits A14 SUPP14
12-15
Word 18) bits AIS SUPP15
0-3
Word 18, bits A16 SUPP16
4-7
Word 18, bits A17 SUPP17
8-11
Word 18, bits A18 SUPP18
12-IS
Word 19, bits A19 SUPP19
0-3
Word 19) bits A20 SUPP20
4-?
Word 19) bits A21 SUPP21
8-11
Word 19) bits A22 SUPP22
12-15
501
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/Z3080 PGT/tTS97/Z1I74
Word ~Y) Bit # Description I
4. VNet Remote caller accesses VNet
Access - If services
the
through the
Remote Access
Service) the
access number
is recorded
starting at recorded after the
A 1. A TBCD-Null last digit
is
followed by
any Supplemental
Codes. Unused
bytes contain
TBCD-Null.
VNet Remote
Access format:
Word 14) bits A1 X
8-l I
Word 14, bits A2 X
12-15
Word 15) bits A3 X
0-3
Word 15, bits A4 X
4-7
Word 15, bits AS X
8-11
Word 15, bits A6 X
12-15
Word 16, bits A7 X
0-3
Word 16, bits A8 X
4-7
Word 16) bits A9 X
8-11
Word 16) bits A10 X
12-IS
Word 17) bits A11 TBCD-Null
0-3
Word 17, bits A12 SUPP1
4-7
Word 17, bits A13 SUPP2
8-11
Word 17, bits A14 SUPP3
12-15
Word 15) bits A15 SUPP4
0-3
Word 18, bits A16 SUPPS
4-7
Word 18, bits A17 SUPP6
8-I1
Word 18) bits A18 SUPP7
12-15
Word 19, bits A19 SUPP8
0-3
Word 19) bits A20 SUPP9
4-7
Word 19) bits A21 SUPP10
8-11
Word 19, bits A22 SUPP11
12-15 __
502
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98123080 - PCT/US97IZII74
Word 11, Bit ~ Description
5. Calling calling party number
Parry Number is recorded
- The
for SS7 FGD inations
call orig received
with
a
charge
number
and
a calling party. the SS7 calling party
number Recordnumber in
A1-I0. A TBCD-Nullis
recorded
after
the
last
digit,
followed
by
supplementary
codes. Unused
bytes contain
TBCD-Null.
Calling
parry number
format:
Word 14, bits AI N
8-11
Word 14, bits A2 X
12-15
Word 15) bits A3 X
0-3
Word 15) bits A4 N
4-7
Word 15) bits AS X
8-11
Word 15, bits A6 X
12-~15
Word 16, bits A7 N
0-3
Word 16, bits A8 X
4-7
Word 16) bits A9 X
8-11
Word 16, bits A10 X
12-15
Word 17) bits Al TBCD-Null
0-3 l
Word 17, bits A12 SUPP1
4-7
Word 17, bits A13 SUPP2
8-11
Word 17) bits A14 SUPP3
12-15
Word 18, bits A15 SUPP4
0-3
Word 18, bits A16 SUPPS
4-7
Word 18, bits A17 SUPP6
8-11
Word 18) bits A18 SUPP7
12-15
Word 19, bits A19 SUPP8
0-3
Word 19) bits A20 SUPP9
4-7
Word 19, bits A21 SUPP10
8-I1
Word 19) bits A22 SUPPl l
12-15
503
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/2I174
Word A~, Bit 7! Description
6. Credit Card Number - Record the commercial
credit card or
presubcribed credit card number starting
in Al. The PIN digits of
a valid presubscribed credit card number
are masked out by
writing TBCD-A over the 4 PIN digits.
A TBCD-Null is recorded
after the last digit, followed by supplementary
codes. Unused
bytes contain TBCD-Null. Credit card number
format:
Word 14, bits 8-11 A1 X
Word 14, bits 12-15 A2 X
Word 15) bits 0-3 A3 X
Word 15) bits 4-7 A4 X
Word 15, bits 8-11 AS X
Word 15) bits 12-15 A6 X
Word 16, bits 0-3 A7 X
Word 16, bits 4-7 A8 X
Word 16) bits 8-11 A9 X
Word 16) bits 12-15 A10 X
-- Word 17) bits 0-3 Al l X
Word 17, bits 4-7 A12 X
Word 17) bits 8-lI- A13 X
Word 17, bits 12-15 A14 X
Word 18) bits 0-3 A15 X
Word I8, bits 4-7 A16 X
Word 18) bits 8-11 A17 X
Word 18, bits 12-15 A18 X
Word 19, bits 0-3 A9 X
Word 19, bits 4-7 A20 TBCD-Null
Word 19) bits 8-I1 A21 SUPP1
Word 19, bits 12-15 A22 SUPP2
504
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97l21174
.....
Word) Bit A' Description
7. 14 Digit Cards
MCI/VNet -
The
14
digit
calling
card/VNet
card number
is recorded
starting in
A1 with the
last 4 PIN
digits
masktd out TBCD-Afor those digits.
by writing A TBCD-Null is
written after
the last digit)
followed by
supplemental
codes.
Unused bytes ll. Calling card/VNet
contain TBCD-Nu card format:
Word I4, bits A1 X
8-11
Word 14, bits A2 X
12-15
Word 15, bits A3 X
0-3
Word 15) bits A4 X
4-7
Word 15, bits AS X
8-11
Word I5) bits A6 X
12-IS
Word 16, bits A7 X
0-3
Word 16, bits A8 X
4-7
Word 16) bits A9 X
8-11
Word 16, bits A10 X
12-IS
Word 17, bits A11 TBCD-A
0-3
Word 17) bits A 12 TBCD-A
4-7
Word 17) bits A13 TBCD-A
g-11
Word 17, bits A14 TBCD-A
12-15
Word 18, bits A15 TBCD-Null
0-3
Word 18, bits A16 SUPP1
4-7
Word 18) bits A17 SUPP2
8-11
Word l8,bits A18 SUPP3
12-15
Word 19, bits A19 SUPP4
0-3
Word 19, bits A20 SUPPS
4-7
Word 19, bits A21 SUPP6
8-11
Word 19, bits A22 SUPP7
12-15
505
SUBSTfTUTE SHEET (RULE 28)
CA 02279845 1999-OS-17
WO 98/230 PG"f/US97/21174
Word ~) Bit TI Description
8. Telecommunications/P'TT
Cards - The
23 digits)
or less, of
the
telecommunications
card is recorded
starting in
A1. A TBCD-Null
is recorded , followed by supplemental
after the last codes.
digit
Unused bytes
contain TBCD-Null.
Telecommunications
card
format:
Word 14) bits A1 X
8-11
Word 14, bits A2 X
12-15
Word 15, bits A3 X
0-3
Word 15, bits A4- X
4-7
Word 15, bits AS X
8-11
Word 15, bits A6 X
12-15
Word 16) bits A7 X
0-3
Word 16, bits A8 X
4-7
Word I6) bits A9 X
8-11
Word 16) bits A10 X
12-15
Word 17) bits A X
0-3 11
WoM 17, bits A12 X
4-7
Word 17, bits A13 X
8-11
Word 17, bits A14 X
12-15
Word 18, bits A X
0-3 15
Word 18) bits A16 X
4-7
Word 19) bits A17 X
8-11
Word 19, bits AI8 X
12-15
Word 19) bits A19 X
0-3
Word 19, bits A20 X
4-7
Word 19, bits A21 X
8-11
Word 19, bits A22 X
12-15
506
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
wo 9snn3oso rc~rnrs9~mma
Word-JI) Bit A~ Description'
9. OSID and
OTG - For
international
inbound VNet
or SAC calls,
the OSID and
OTG are recorded
as received
from the SS7
Generic
Digits parameter.
After the
parameters
are recorded,
the remaining
bytes contain
TBCD-Null.
OSID and OTG
format:
Word 14) bits A1 X (OSID)
8-1 l
Word 14, bits A2 X (OSIDj
12-15
Word 15) bits A3 X (OSID)
0-3
Word 15, bits A4 X (OTG)
4=7
Word 15) bits AS X (OTG)
8-1 l
Word 15) bits A6 X (OTG)
12-:IS
Word 16, bits A7 X (OTG)
0-3
Word 16, bits A8 TBCD-Null
4-7
Word 16, bits A9 TBCD-Null
8-i:l
Word 16, bits A10 TBCD-Null
12-15
Word 17, bits A11 TBCD-Null
0-3
Word 17, bits A12 TBCD-Null
4-7
Word 17) bits A13 TBCD-Null
8-l:l
Word I7) bits A14 TBCD-Null
l2-15
Word I8, bits A15 TBCD-Null
0-3
Word 18) bits A16 TBCD-Nult
4-7
Word I8) bits A17 TBCD-Null
8-11
Word 18, bits A18 TBCD-Null
12-15
Word 19, bits A19 TBCD-Null
0-3
Word I9, bits A20 TBCD-Null
4-7 -
Word 19, bits A21 TBCD-Null
8-11
Word 19, bits A22 TBCD-Null
12-15
I
OSID ~ Originating
Switch ID
i OTG = Originating
Trunk Group
507
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/Z3080 PG"T/US97/Z1174
Word b, Bit ll Description
10. Business
Group ID -
For some SS7
trunk groups,
a business
group ID is
received in
a SS7 parameter
and is recorded
in Al-A6.
After the last
digit) a TBCD-Null
is recorded
followed by
any
supplemental nused
codes. U bytes
contain
TBCD-Null.
Word 14, bits A1 X
8-11
Word 14) bits A2 X
12-15
Word 15, bits A3 X
0-3
Word 15, bits A4 X
4-7
Word 15, bits AS X
8-11
Word 15, bits A6 X
12-15
Word 16, bits A7 TBCD-Null
0-3
Word 16, bits A8 SUPP1
4-7
Word 16, bits A9 SUPP2
8-11
Word 16, bits A10 SUPP3
12-15
Word 17, bits A11 SUPP4
0-3
Word 17, bits A12 SUPPS
4-7
Word 17, bits A13 SUPP6
8-11
Word 17, bits A14 SUPP7
12-15
Word 18) bits A15 SUPP8
0-3
Word 18) bits A16 SUPP9
4-7
Word 18) bits A17 SUPP10
8-11
Word 18, bits A18 SUPP11
12-15
Word 19, bits A19 SUPP12
0-3
Word 19, bits A20 SUPP13
4-7
Word 19) bits A21 SUPP14
8-11
Word 19) bits A22 SUPP15
12-15
11. Network
Information
- For some
SS7 trunk
groups) a
network
information
ID is received
in a SS7 parameter
and is recorded
in
A1-A4. After igit)
the last d a
TBCD-Null
is
recorded
followed
by
any supplemental. bytes contain TBCD-Null.
codes Unused
Word 14) bits Al N
8-11
Word 14, bits A2 X
12-15
Word 15, bits A3 X
0-3
Word 15, bits A4 N
4-7
Word 15) bits AS TBCD-Null
8-11
Word 15, bits A6 SUPPI
I2-15
Word 16) bits A7 SUPP2
0-3
Word 16) bits AS SUPP3
4-7
Word 16) bits A9 SUPP4
8-11
Word 16) bits A10 SUPPS
12-15
Word 17) bits A11 SUPP6
0-3 ~
Word 17,~its A12 SUPP7
4-7
Word 17, bits A13 SUPP8
8-11
Word 17, bits A14 SUPP9
12-15
Word 18) bits A15 SUPP10
0-3
Word 18) bits A16 SUPPl l
4-7
Word 15) bits A17 SUPP12
8-11
Word 18) bits A18 SUPP13
12-1:5
Word 19) bits A19 SUPP14
0-3
Word 19, bits A20 SUPP15
4-7
Word 19, bits A21 SUPP16
8-11
Word 19) bits A22 SUPP17
12-1:5
508
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98rZ3080 PCT/LJS97/21174
Word A~, Bit ll Description
12. Network Call Identifier (NCID) - If
the NCID is recorded in
the 'A' field, it will be recorded in
binary beginning with A1.
The Entry Code field will be indicative
of the call processing
associated with the particular call or
"0". If the NCID is recorded
in the NCID field of a 64 word call record,
the Entry Code will
also be indicative of the call processing
associated with the
particular call or "0". The NCID is comprised
of the following:
Originating Switch ID
Originating Trunk Group
Originating Port Number
Timepoint One
NCID Sequence Number
Word 20) bits 0-15 Destination Address: This is the seventeen
digits of the destination
Word 21, bits 0-15 address which is the number being called.
If more than 17 digits is
Word 22, bits 0-15 required, use ECDR/EPNR format. Unused
bytes contain~BCD-
Word 23, bits 0-15 Null.
Word 24) bits 0-3
7-digit 10-digit DDD IDDD
Word 20, bits 0-3 D1 N N N CC
Word 20, bits 4-7 D2 X X X CC
Word 20, bits 8-1 F D3 X X X CC
Word 20) bits 12-IS D4 X N N NN
Word 21, bits 0-3 DS X X X NN
Word 21) bits 4-7 D6 X X X NN
Word 21) bits 8-11 D7 X X X NN
Word 21,- bits 12-15 DS X(TSID) X NN
Word 22, bits 0-3 D9 X(TSID) X NN
Word 22, bits 4-7 D10 X(TSID) X NN
Word 22) bits 8-l l D11 XfT'TG) X(TSID)
T-Null NN
Word 22) bits 12-15 D12 X('T'TG) X(TSID)
T-Null NN
Word 23, bits 0-3 D13 X(TTG) X(TSID) T-Null
NN
Word 23) bits 4-7 D14 X(TTG) X(TSID) T-Null
NN
Word 23, bits 8-11 D15 T-Null X('ITG)
T-Null NN
Word 23) bits 12-15 D16 T-Null X(TTG)
T-Null T-Null
Word 24) bits 0-3 D17 T-Null X(TTG) T-Null
T-Null
CC = Customer (:arrier -
NN = National Number
TSID = Terminating Switch ID
TTG = Terminating Trunk Group
509
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/Z3080 PCT/US97/21174
Word ff, Bit ~ Description
Word 24) bits 4-15 Pretranslated Digits: This represents
the digits as dialed by the
Word 25, bits 0-IS caller which may or may not be the Destination
Address. The
Word 26, bits 0-11 pretranslated digits are only recorded
if a translation of the number
occurs. if the dialed number is the destination
number) and is not
translated to another number, this field
contains TBCD-Nulls. If
there are more than 10 digits, use the
ECDR/EPNR format.
10 digit
VNet, SAC OOY 7 digit IDDD
DNIS) or SAC VNet or 10 digit
Hotline Code Hotline (example)
Word 24, bits 4-7 PTD1 N 0 N N
Word 24) bits 8-1 l PTD2 X 0 X N
Word 24) bits 12-15 PTD3 X Y X N
Word 25, bits 0-3 PTD4 N N X N
Word 25, bits 4-7 PTDS X X X N
Word 25) bits 8-11 PTD6 X X X N
Word 25, bits 12-15 PTD7 X X X N
Word 26) bits 0-3 PTD8 X X TBDC-Nul! .
N
Word 26) bits 4-7 PTD9 X X TBDC-Null N
Word 26, bits 8-11 PTD10 X X TBDC-Null
N
Word 26) bits 12-15 Not Used.
Word 27, bits 0-3 Feature Code (FC): The switch determines
a feature code for the
call which indicates whether a specific
type of data line is required
for the call such as a higher quality
line for facsimile
transmissions.
0 = Default
1 = FAX
2 = NABS
3 = Data Call
4 = Switched DS 1 (HSCS)
5 = Switched DS3 (HSCS)
6-8 = Not Used
9 = NX64
10 = Offset Routing
I1 = AAP Cal! (Used in Gateway Toll Ticket
Conversion)
12 = Card Gate Denial
13 = Forum Dia! In audio/video conference
14 = Concert Freephone
15 = Not Used
Word 27) bits 4-7 Terminating Network Code (TNC): Indicates
the terminating
-- facilities to be used for the remainder
of the path of the call. For
example) an indicator for no satellite
transmission.
0 = Default
I = No Routing Restrictions
2 = Avoid Satellite
3 = Route via DSI
4 = Route via DS1 and avoid satellite
5 = Route via Protected Facilities Required
6 = Route via Protected Facilities Preferred
7-15 = Not Used
510
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PCT/USg7IZI174
Word A~, Bit k Description
Word 27, bits 8-11 Network Access Type (NAT): Indicates
which type of network
access was used as defined at the originating
switch on the
network; that is, how the caller gained
access to the network. The
types of access are:
0 = Default
1 = 800 call
2 = Credit Card Access
3 = Operator Assistance Access
4 = VNET Remote Access
5 = BPP Access
6 = FGD Cut-Through Access
7-15 = Not Used
Word 27, bits 12-15 Titnepoint 7 Qualifier (TP7Q): Contains
the call's first disconnect
qualifier, that is, how the call was
terminated. The types of
ditconnectit)n 8IC:
0 = Calling parry discotmects
1 = Called parry disconnects
2 = Calling parry reorigination
3 = Switch initiated (ez. switch error
cut off the call)
4 = All Routes Busy
5 = Disconnected due to a long ring;
ring timer exceeded
6 = Cali disconnected due to network
invoked transfer
7 = Feature/Service Interaction
8-15 = Not Used
Word 28, bits 0-6 Entry Code (EC): Indicates the type of
call processing that took
place and what type of information is
recorded in the --
Authorization Code field. If more than
one entry code is received,
record the last one.. The following codes
are valid:
51 1
suesriTUrE sHeEr ~RU~ 2s~
CA 02279845 1999-OS-17
WO 98123080 PCT/I1S97/21174
Word #) Bit # L)escription
0 = Default
1 = Person-to-Person (P-P)
2 = Station-to-Station (S-S)
3 = Third Party Billing (3rd parry number
recorded)
4 = P-P collect (bill to called parry)
5 = S-S collect (bill to called patty)
6 = MCI card or VNet card (S-S)
7 = BOC inward dialing without call completion
8 = general assistance
9 = BOCILEC card
10 = Presubsribed credit card
11 = PTT card
12 = Directory Assistance
13 = Commercial Credit Card
14 = BOC inward dialing with call completion
15 = MCI card or VNet card (P-P) -
16-19 = Not Used
20 = ANl validation (screened pass/fail)
21 = Auth Validation (filed or dialed)
22 = Not Used
23 = 700 Service Access Code (overrides
#20)
24 = 500, 800 Service Access Code (overrides
#20)
25 = 900 Service Access Code (overrides
#20)
26-28 = Not Used
29 = Operator Release Timer Expired
30 = EVS/NARS - Disconnect message referral
(DMR) without
referral
31 = EVSINARS - DMR with refetrai to MCI
number
32 = EVSINARS - DMR with referral to non-MCI
number
33 = EVS/NARS - DMR with referral and
call extension (CE) to
MCI number
34 = EVS/NARS - DMR with referral and
CE to non-MCI
number
35 = EVS/NARS - Customized Message Announcement
(CMA)
with CE
512
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/Z3080 PGT/US97/21174
Word ~) Bit Il Description
36 = EVS/NARS - CMA without CE
37 = EVS/NARS - Enhanced Calt Routing
(ECR)
38-41 = EVS/NARS - Reserved
427 = Not Used
48 = GETS card
49 = Not Used
50 = Billed to intctnational number
51 = Calling station ID information recorded
52 = Supplemental code only recorded
53 = VNet remote access number recorded
54 = SS7 calling party number recorded
55 = OSID and OTG recorded
56 = DNIS recorded
57 = Business graup ID recorded
58 = Network information recorded
59 = BG + Null + OSID/OTG
60 = Card Number + Null + OSID/OTG
61 = VNet RA + Null + OSID/OTG
62 = VNet RA + Nuil + OSIDIOTG
63 = Network CaII Transfer (NC:'I~
64-79 = Reserved
80-89 = Reserved
90-99 = Reserved
100 = 18C It's Me PIN S/S
101 = 18C It's Me Global S/S
102 = 18C It's Me ANI S/S
103 = 18C lt's Me NPA S/S
104 = 18C It's Me: Messenger S/S
105 = I8C It's Me Messenger PIN S/S
106 = 18C It's Ma Messenger Global S/S
107 = 18C BOC Card S/S
-. 108 = 18C MCI Card S/S
109 = Aos Messenger S/S
110 = lntetuational Messenger S/S
111 = International Speed Dial
112-127 = Not Used
Word 28, bits 7-9 Prefix Digits (PD): Represents the prefix
digits of the called
number. These digits tell the switch
how to process the call.
0 = No prefix digits received
1 = 0- (operator assisted)
2 = 0+ (domestic CDOS)
3 = O1 + (international CDOS)
4 = 01.1 +IDDD .
5 = 1 +DDD
6 = 0+opcrator assisted, subscriber address
7 = *XX when XX = 0-9, Star Card
513
SUBSTITUTE SHEET (RUr.E 26)
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97l21174
Word b) Bit A~ Description
Word 28, bits 10-12 NDID (NCS/DAP ID): Indicates whether the
switch processed the
call or if one of the databases) such
as NCS/DAP) was queried for
information for services) including but
not limited to, VNET)
Calling Card, 800) and 900 calls. The
NDID further indicates the
ID of the NCS/DAP that was involved in
the last transaction
attempt.
0 = Switch call processing
1 = NCS/DAP 1
2 = NCS/DAP 2
3 = NCS/DAP 3
4-S = Not Used
6 = Received fmm operator platform via
RLT
7 = TCAP to NCS/DAP
Word 28, bits 13-15 Division ID (DIV1D): Contains the division
ID for credit card
calls, including the telecommunication
system's card. The DIVID
is received from the NCS/DAP for the card
number validation. If
no infotatation is received by the switch,
record the default value
of '0.'
0 = No division ID specified
1 = Division ID I
2 = Division ID2
3 = Division ID3
4 = Division ID4
S = Division IDS
6 = Division ID6
7 = Division ID7
Word 29) bit 0 Distant Overflow (DO): When sec to 1 in
the originating switch's
call record, indicates that a direct termination
overflow (DTO)
transaction was attempted at an intermediate
or terminating switch
in order to get the final destination
address digits for this call.
Word 29) bit 1 Not Used.
Word 29, bit 2 Customer Connect (CC): Indicates whether
to use timepoint 6 or
timepoint 3 to calculate the call duration.
0 = Use Time Point 6, *F to calculate
the call duration
1 = Use Time Point 3. *C to calculate
the call duration
Word 29) bit 3 Inter-Network (IN): Indicates whether
or not a call is originating
from one customer/network and is terminating
to a different
customerlnetwork. The default setting
= 0; bit sec to 1 if a
business group or Netinfo parameter is
received from the
NCS/DAP.
Word 29, bit 4 Not Used.
Word 29, bit 5 SAC Bit (SC): This bit is used for the
Flezible SAC feature. This
bit will be set to "1" whenever the received
number which is
collected during the address digit collection
phase) is identified as
a SAC number in the FlezSac Indez associated
with the originating
trunk group. This bit will be set to "0"
in all other cases.
514
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO ~~ - PCT/LTS97/21174
Word ~) Bit it Description
Word 29) bit 6 Call Direction (CD): Indicates whether
the call originated in the
domestic or international network.
0 = Call origination occurred in the Domestic
Network
1 = Call origination occurred in the International
Network
Word 29, bit 7 Destination (DE): Indicates when a call
is expected to terminate to
an international destination
0 = Default, NANP. Domestic VNet, or any
otkter calls which are
not expected to terminate to an international
destination
1 = Calls expected to terminate to an
international destination
Word 29) bit 8 Dedicated Termination (DT): Indicates
that a 10-digit shared
network number was completed to a dedicated
destination. If the
terminating trunk class (TTC) in the call
record is equal to 3 or 7,
then it is considered to be a direct termination
trunk.
Word 29) bits 9-10 Not Used.
Word 29, bit 11 Satellite (SA): Indicates that a satellite
circuit was involved in the
call. The default sating is 0; bit set
to 1 indicates that a satellite
was involved in the call. The bit is set
when the incoming trunk
gmup is classmarked as sateilite equipped,
when ttte SAT digit on
an incoming inband IMT call shows that
a satellite circuit is
invotved in the connection, or when the
SS7 Nature of Connection
parameter indicates that a satellite trunk
was previously used. This
is used for trouble-shooting purposes,
and not for billing.
Word 29, bits 12-IS Nature Of Calling Location ID (NOCLI):
A binary value that
identifies what data is recorded in the
Call Location ID. The
Calling Location ID field will contain
the information that is
referenced in the NOCLI.
0 = Not Used
1 = ANI from Inbound trunk
2 ~ SS7 charge number
3 = SS7 calling parry number
4 = original called number
5 = Pseudo ANI created at this switch
6 = CSI from originating trunk
7 = Filed NPA-NXX trunk group information
plus CSI
8 = NNN+OSID~-OTG or OOY+OSID+OTG (N=TBCD-Null)
i 9 = Country Code + national number
10 = No CLI record
11 = Redirecting Number
I 12 = CLI received from Operator piatfotm
via RLT
13 = ANI of NCT originator
14-15 = Not Used
515
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 9812308(1 PGT/US97/21174
Word 11, Bit a Description
Word 30) bits 0-15 Carrier Number (CN): Represents the carrier
number provided on
FG-B or FG-D originations) or the carrier
number received over
an SS7 IMT. if only three digits are
used, then they are recorded
in CN2-CN4 and CN l will contain a TBCD-NuII.
This field also
contains the last four digits of the
specific 800 number assigned to
VISA cards (9595). It will also contain
the last four digits of the
MCI card access number regardless of
the access facility.
Ezamples of carrier numbers art: MCI
= 222) ATT ~ 288, and
Friends = 333.
FGB/FGD FGB/D
3 digit 4 digit visa
CIC CIC card
Word 30) bits 0-3 CN 1 TBCD-Null X 9
Word 30, bits 4-7 CN2 X X 5
Word 30) bits 8-I1 CN3 X X 9
Word 30) bits 12-15 CN4 X X 5
SS7 MCI VNet
TNS card card
Word 30) bits 0-3 CN I X 1 I
Word 30, bits 4-7 CN2 X 0 1
Word 30, bits 8-11 CN3 X 2 I
Word 30, bits 12-15 CN4 X 2 I
Word 31, bits 0-3 Authorization Code ID Field (ACIF): Contains
the Authorization
-
Code Identification Field for recording
a card number status. This
field indicates whether the card number
(calling card or credit
card) is good or bad.
0 = Seven digit auchcode file (default)
1 = 1st or only five digit authcode file
2 = 2nd five digit file
3 = 3rd five digit file
4 = 4th five digit file
5 = 5th five digit file
6 = Siz digit authcode file
7 = Range restriction failure (invalid
address digits)
8 = Positive Commercial Credit Card/89
Card/M Card Validation
9 = Not Used
10 = MCI CardNisa Card invalid or not
assigned. Disallowed.
11 = BOC billing number assigned but
blocked
12 = BOC billing number usage ezceeded
13 = Not Used
14 = Default authorization of MCI Card/VISA
Card if response
timeout from NCS/DAP
15 = MCI CardNISA Card authorized by
NCS/DAP
516
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
Word A~) Bit ~ Description
Word 31) bits 4-10 Release Code: Used with titnepoint 7
qualifier to determine from
which dit~ection the release message
came. The code indicates why
one of the parties hung up) for example)
normal release = 16, and
no circuit available = 34.
- 1 = Unallocated number
2 = No route to specified network
3 = No route to destination
4 = Send special information tone
5 = Misdialed trunk prefix -
16 = Normal clearing
17 = User Busy
18 = No user responding
19 = No user responding (user alerted)
21 = Call rejected
22 = Number changed
27 = Destination out of service
28 = Address incomplete
29 = Facility rejected
31 = Normal - unspecified
34 = No circuit available
38 = Network out of order
41 = Temporary failure
42 = Switching equipment congestion
44 = Requested channel not available
47 = Resource unavailable - unspecified
50 = Requested facility not subscribed
55 = Incoming calls barred within CUG
57 = Bearer capability not authorized
58 = Bearer capability not available
63 = Service -or option not available
65 = Bearer capability not implemented
69 = Requested facility not implemented
70 = Only restricted digital information
bearer capability is
available
79 = Service or option not implemented
87 = Called user not member of CUG
88 = Incompatible destination
91 = Invalid transit network selector
95 = Invalid message - unspecified
97 = Message type non-existent or not
implemented
99 = Parameter non-existent or not implemented
- discarded
102 = Recovery on timer expired
103 = Parameter non-existent or not implemented
- passed on
111 = Protocol error - unspecified
127 = Interworking - unspecified
Word 31, bits 11-13 NCID Sequence Number: Represents the
number of calls which
have occurred on the same port number
with the same Timepoim 1
v alue. The first call will have the sequence
number set to '0'. This
value will increase incrementally for
each successive call which
originates on the same port number which
has the same Timepoint
1 value. Range = 0-7.
517
SUBSTITUTE SHEET (RULE 2B)
CA 02279845 1999-OS-17
WO 98/23080 - PCT/US97I21174
Word ~Y) Bit ~ Description
Word 31, bit 14 NCID Location (NCIDLOC): This bit identifies
when the
s
recorded in the Authcode field of the
call record. The NCID is
recorded in the Authcode field of the
call record at intermediate
and terminating switches if the Authcode
field is not being used to
record other information. If the Authcode
field is being used to
record other information, the NCID is
recorded in the "NCID"
field of the 64 word call record.
0 = NCID is not recorded in the Authcode
field (default)
1 = NCID is recorded in the Authcode field
Word 31, bit IS Remote ANI Screened (RS): This bit is
set to' 1' if the NPA of the
ANI is not listed in the switch's Local-Service-Area
table, and the
ANI was sent to the DAP for ANI index
screening purposes. This
bit is set to '0' if the switch sent the
ANI to the DAP for ANI
index screening purposes and no response
is received from the
DAP or if normal switch ANI screening
occurs.
I 0 = ANI was not screened by the DAP (default)
I = ANI was screened by the DAP
518
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
Table 302 - ECDR/EPNR Record Format:
Word ~) Bit ~ Description - I
Words 0-11, bits Same as CDR/PNR format.
0-15
Word I2, bits 0-15 Calling Location ID: Contains I-15 digits
of dte originating station
Word 13, bits 0-15 line. This is the ANI number of the calling
party. If 1 to 15 ANI
Word 14, bits 0-15 or CSI digits are received, they are recorded
in order' starting with
Word 15, bits 0-11 CLI1. Unused bytes contain TBCD-Null.
If no ANI or CSI is
available, record the OSID/OTG in CLI4-l0,
except where noted.
if nothing is recorded in the CLI field,
use a NOCLI value of 10.
This field contains 1 of the following
nine fotittats:
1. VNet CAMA DAL originations: If CSI
is available, prefix the
CSI with filed HNPA and HNXX information)
if available, and
record. Use NOCLI value of 7.
2. FG-C Originations: If ANI or CSI information
is not available
and the number is in the OOY+NXX-XXXX
format) record the
OOY code that was received in CLI1-3)
and record the OSID/OTG
in CLI4-10. Use NOCLI value of 8.
3. Inband FG-D Originations: Record the
ANI that was received
starting with CLI. Use NOCLI value of
1.
4. SS7 FG-D Originations: Record the charge
number, if
available. If the charge number is not
available, record the calling
party number. Use NOCLI value of 2 or
3.
S. International Originations: Record
the country code and
national number of the calling party.
Use NOCLI value of 9.
6. SS7 IMTs Originations: Record the following
information in
this order of importance: 1) charge number)
2) calling party
number, 3) OSD/OTG from generic digits.
Use NOCLI value of
2) 3, or 8.
7. SS7 Reseller Originations: The CLI
field will be filled with
TBCD Nulls.
8. SS7 Private Network Originations: The
CLI field will be filled
with TBCD Nulls.
9. PRI Originations:. Record the calling
party number received in
the 1SDN setup message.
519
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PGT/US97121174
-
Word ~) Bit ~ Description
The format:
1-15 digit
ANI/CSI
( 13 digit Incoming
example) OSID/OTG Int'1
Word I2, bits 0-3 CLI1 X TBCD-Null X(CC)
Word 12, bits 4-7 CLI2 X TBCD-Null X(CC)
Word I2) bits 8-11 CLI3_ X TBCD-Null X(CC)
Word I2, bits 12-15 CLI4 X X(OSID) X(NN)
Word 13) bits 0-3 CLIS X X(OSID) X(NN)
Word 13) bits 4-7 CLI6 X X(OSID) X(NN)
Word 13, bits 8-11 CLI7 X X(OTG) X(NN)
Word I3, bits 12-15 GLIB X X(OTG) X(NN)
Word 14) bits 0-3 CLI9 X X(OTG) X(NN)
Word 14) bits 4-7 CLI10 X X(OTG) X(NN)
Word 14, bits 8-11 CLI11 X TBCD-Null X(NN)
Word 14) bits 12-15 CLII2 X TBCD-Null
X(NN)
Word 15, bits 0-3 CLI13 X TBCD-Null X(NN)
Word 15, bits 4-7 CLI14 TBCD-Null TBCD-Null
X(NN)
Word i5) bits 8-11 CLI15 TBCD-Null TBCD-Null
X(NN)
CC = Customer Connect
NN = National Number
OSID = Originating Switch ID (000-999)
OTG = Originating Trunk Group (0000-g
191 )
Word 15, bits 12-I5 Authorization Code (Auth Code): Same as
CDR/PNR fo
A
rmat
Word 16, bits 0-15 uth
Code, but represents 45 digits.
Word 17, bits 0-1S
Word 18) bits 0-15 1. Authorization Codes:
Word 19, bits 0-15
Word 20, bits 0-15
5 digit 6 digit 7 digit
Word 21, bits 0-15 Word 15
bits 12-15 A 1 AUTH 1 A
)
Word 22, bits 0-15 UTH 1 AUTH 1
Word 16
bits 0-3 A2 AUTH2
,
Word 23, bits 0-15 AUTH2 AUTH2
Word 16
bits 4-7 A3 AUTH3
)
Word 24, bits 0-15 AUTH3 AUTH3
Word 16) bits 8-11 A4 AUTH4 AUTH4
AUTH4
Word 25, bits 0-15 Word 16) bits 12-15 AS AUTHS AUTHS
AUTHS
Word 26) bits 0-15 Word 17, bits 0-3 A6 SEC1 AUTH6
AUTH6
Word 17) bits 4-7 A7 SEC2 SEC1 AUTH7
Word 17, bits 8-11 A8 SEC3 SEC2 SECI
Word 17, bits 12-!5 A9 SEC4 SEC3 SEC2
Word 18) bits 0-3 A 10 T-Null SEC4 SEC3
Word 18, bits 4-7 ~ A11 SUPPl T-Null SEC4
Word 18, bits 8-11 A12 SUPP2 SUPP1 T-Null
Word 18) bits 12-15 A13 SUPP3 SUPP2 SUPPI
520
SUBSTITUTE SHEET (RULE 28)
CA 02279845 1999-OS-17
WO 98123080 PCT/US97/21174
Word a, Bit a Description
Word 19, bits SUPP3 SUPP2
0-3 A14 SUPP4
Word 19, bits SUPPS SUPP4 SUPP3
4-7 A15
Word 19) bits SUPP6 SUPPS SUFP4
8-11 A16
Word 19, bits SUPP7 SUPP6 SUPPS
12-IS A17
Word 20, bits SUPP8 SUPP7 SUPP6
0-:3 A18
Word 20) bits SUPP9 SUPP8 SUPP7
4-'7 A19
Word 20) bits SUPP10SUPP9 SUPP8
8-l l A20
Word 20) bits SUPP11SUPP10SUPP9
12-15 A21
Word 21, bits SUPP12SUPP11SUPP10
0-3 A22
Word 21) bits SUPP13SUPP12SUPP11
4-'i A23
Word 21, bits SUPP14SUPP13SUPP12
8-11 A24
Word 21, bits SUPP15SUPP14SUPP13
12-15 A25
Word 22, bits SUPP16SUPP15SUPP14
0-:f A26
Word 22, bits SUPP17SUPP16SUPP15
4-7 A27
Word 22) bits SUPP18SUPPI7SUPP16
8-11 A28
Word 22, bits SUPP19SUPP18SUPP11
12-15 A29
Word 23) bits SUPP20SUPPI9SUPP18
0-3 A30
Word 23, bits SUPP21SUPP20SUPP19
4-'; A31
Word 23, bits SUPP22SUPP21SUPP20
8-11 A32
Word 23, bits SUPP23SUPP22SUPP21
12..15 A33
Word 24) bits SUPP24SUPP23SUPP22
0-3~ A34
Word 24, bits SUPP25SUPP24SUPP23
4-7 A35
Word 24, bits SUPP26SUPP25SUPP24
8-11 A36
Word 24, bits SUPP27SUPP26SUPP25
12-15 A37
Word 25, bits SUPP28SUPP27SUPP26
0-3 A38
Word 25) bits SUPP29SUPP28SUPP27
4-7 A39
Word 25) bits SUPP30SUPP29SUPP28
8-11 A40
Word 25, bits T-NullSUPP30SUPP29
12-IS A41
Word 26) bits T-NullT-NullSUPP30
0-3 A42
Word 26, bits T-NullT-Nul1T-Null
4-7 A43
Word 26) bits T-NullT-NullT-Null
8-11 A44
Word 26, bits T-NullT-NullT-Nutl
12-IS A45
T-Null = TBCD-Null
2. Calling Station
ID (CSI):
7 digit 1-IO digit
Word 15) bits A1- X X
12-15
Word 16) bits A2 X X
0-3
Word 16, bits A3 X X
4-7
Word 16, bits A4 X X
8-I 1
Word 16) bits AS X X
12-15
Word 17, bits A6 X X
0-3 ~
Word 17, bits A7 X X
4-7
Word 17, bits A8 TBCD-Null
8-11 X
Word 17, bits A9 SUPPl X
12-15
Word 18, bits A10 SUPP2 X
0-3
Word 18, bits A11 SUPP3 TBCD-Null
4-7
Word 18) bits A12 SUPP4 SUPP1
8-11
Word 18) bits AI3 SUPPS SUPP2
12-15
521
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
Word A~) Bit 1! Description
Word 19) bits A14 SUPP6 ~ SUPP3
0-3
Word 19) bits AIS SUPP7 SUPP4
4-7
Word 19, bits A16 SUPP8 SUPPS
8-11
Word 19, bits A17 SUPP9 SUPP6
12-IS
Word 20) bits A18 SUPP10 SUPP7
0-3
Word 20) bits A19 SUPP11 SUPP8
4-7
Word 20) bits A20 SUPP12 SUPP9
8-11
Word 20, bits A21 SUPP13 ;SUPP10
12-15 ~
Word 21, bits A22 SUPPI4 SUPPI l
0-3
Word 21, bits A23 SUPP15 SUPPI2
4-7
Word 21, bits A24 SUPP16 SUPP13
8-11
Word 21, bits A25 SUPP17 SUPP14
12-15
Word 22) bits A26 SUPP18 SUPP15
0-3
Word 22, bits A27 SUPP19 SUPP16
4-7
Word 22, bits A28 SUPP20 SUPPI7
8-11
Word 22, bits A29 SUPP2I SUPP18
12-15
Word 23) bits A30 SUPPZ2 SUPP19
0-3
Word 23, bits A31 SUPP23 SUPP20
4-7
Word 23, bits A32 SUPP24 SUPP21
8-11
Word 23, bits A33 SUPP25 SUPPZZ
12-IS
Word 24) bits A34 SUPP26 SUPP23
0-3
Word 24) bits A35 SUPP27 SUPP24
4-7
Word 24) bits A36 SUPP28 SUPP25
g-11
Word 24) bits A37 SUPP29 SUPP26
12-15
Word 25, bits A38 SUPP30 SUPP27
0-3
Word 25, bits A39 TBCD-Null SUPP28
4-7
Word 25) bits A40 TBCD-Null SUPP29
8-11
Word 25) bits A41 TBCD-Null SUPP30
12-15
Word 26) bits A42 TBCD-Null TBCD-Null
0-3
Word 26, bits A43 TBCD-Null TBCD-Null
4-7
Word 26, bits A44 TBCD-Null TBCD-Null
8-11
Word 26, bits A45 TBCD-Null TBCD-Null
l2-15
3. Suppiemental
Codes:
WoM 15, bits A1 SUPPI
12-15
Word 16, bits A2 SUPP2
0-3
Word 16, bits A3 SUPP3.
4-7
Word 16) bits A4 SUPP4
8-11
Word 16, bits AS SUPPS
12-15
Word 17, bits A6 SUPP6
0-3
Word 17) bits A7 SUPP7
4-7
Word 17, bits A8 SUPP8
8-11
Word 17, bits A9 SUPP9
12-15
_- Word 18, bits A10 SUPP10
0-3
Word 18, bits A11 SUPPI 1
4-7
Word 18, bits A12 SUPP12
8-11
Word 18) bits A13 SUPP13
I2-15
522
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
wo 9sr~oso pc~r~s97r~m74
Word A~, Bit ~ Description
Word 19, bits A14 SUPP14
0-3
Word 19, bits A15 SUPP15
4-7
Word 19, bits A16 SUPP16
8-11
Word 19, bits A17 SUPP17
12-IS
Word 20) bits AI8 SUPPl8
0-:3
Word 20, bits A19 SUPP19
4=7
Word 20, bits A20 SUPP2Q
8-11
Word 20, bits A21 SUPP21
12-15
Word 21) bits A22 SUPP22
0-3
Word 21, bits A23 SUPP23
4=.7
Word 21) bits A24 SUPP24
8-:l 1
Word 21) bits A25 SUPP25
12-15
Word 22) bits A26 SUPP26
0-:1
Word 22) bits A27 SUPP27
4-7
Word 22) bits A28 SUPP28
8-1.:1
Word 22) bits A29 SUPP29
12~-15
Word 23) bits A30 TBCD-Null
0-3
Word 23, bits A31 TBCD-Null
4-i'
Word 23, bits A32 TBCD-Null
8-11
Word 23, bits A33 TBCD-Null
12..15
Word 24, bits A34 TBCD-Null
0-3
Word 24, bits A35 TBCD-Null
4-7
Word 24, bits A36 TBCD-Null
8-11
Word 24, bits A37 TBCD-Null
12-15
Word 25, bits A38 TBCD-Null
0-3
Word 25, bits A39 TBCD-Null
4-7
Word 25, bits A40 TBCD-Null
8-11
Word 25, bits A41 TBCD-Null
12-15
Word 26, bits A42 TBCD-Null
0-3
Word 26, bits A43 TBCD-Null
4-7
Word 26, bits A44 TBCD-Null
8-11
Word 26, bits A45 TBCD-Null
12-15
4. VNet Remotcand
Access Calling
Party
Number:
Word 15, bits A1 N
12-15
Word 16) bits A2 X
0-3
Word 16, bits A3 X
4-7
Word 16, bits A4 N
8-1 l
Word 16, bits AS X
12-15
Word 17) bits A6 X
0-3
Word 17, bits A7 X
4-7
Word 17) bits A8 X
8-11
Word 17) bits A9 X
12-15
Word 18) bits A 10 X
0-3
Word 18, bits A11 TBCD-Null
4-7
Word 18) bits A12 SUPP1
8-11
Word 18) bits AI3 SUPP2
12-IS
523
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98!23080 PCT/US97/21174
Word II) Bit ~ Description
Word 19, bits A14 SUPP3'
0-3
Word 19, bits A15 SUPP4
4-7
Word 19, bits A16 SUPPS
8-11
Word 19, bits A17 SUPP6
12-IS
Word 20) bits A18 SUPP7
0-3
Word 20, bits A19 SUPP8
4-7
Word 20, bits A20 SUPP9
8-11
Word 20, bits A21 SUPPIO
12-15
Word 21, bits A22 SUPPI 1
0-3
Word 21, bits A23 SUPPI2
4-7 _
Word 21, bits A24 SUPPI3
8-11
Word 21) bits A25 SUPP14
12-15
Word 22, bits A26 SUPPIS
0-3
Word 22) bits A27 SUPP16
4-7
Word 22, bits A28 SUPPt7
8-11
Word 22, bits A29 SUPPI8
12-15
Word 23) bits A30 SUPP19
0-3
Word 23, bits A31 SUPP20
4-7
Word 23) bits A32 SUPP21
8-11
Word 23, bits A33 SUPP22
12-15
Word 24) bits A34 SUPP23
0-3
Word 24, bits A35 SUPP24
4-7
Word 24,bits A36 SUPP25
8-11
Word 24, bits A37 SUPP26
12-15
Word 25, bits A38 SUPP27
0-3
Word 25) bits A39 SUPP28
4-7
Word 25, bits A40 SUPP29
8-11
Word 25, bits A41 SUPP30
12-15
Word 26, bits A42 TBCD-Null
0-3
Word 26, bits A43 TBCD-Null
4-7
Word 26, bits A44 TBCD-Null
8-11
I Word 26, bits A45 TBCD-Null
12-IS
I
5. Credit Card:
Word I5) bits AI X
12-15
Word 16, bits A2 X
0-3
Word 16, bits A3 X
4-7
Word 16, bits A4 X
8-11
Word 16) bits AS X
12-15
Word 17, bits A6 X
0-3
Word 17) bits A7 X
4-7
Word 17) bits A8 X
8-11
Word 17, bits A9 X
12-15
_- Word 18, bits A10 X
0-3
Word 18) bits A 11 X
4-7
Word 18, bits A12 X
8-11
Word 18) bits A13 X
12-15
524
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
PCT/US97/21174
Word ~, Bit t~ Description
Word 19) bits A 14 X
0-3A
Word 19, bits A 15 X
4-7
Word 19, bits A16 X
8-I1
Word 19, bits A17 X
12-15
Word 20, bits A 18 X
0-3
Word 20, bits A 19 X
4-7
Word 20, bits A20 TBCD-Null
8-11
Word 20) bits A21 SUPPI
12-15
Word 21, bits A22 SUPP2
0-3
Wool 21, bits A23 SUPP3
4-7
Word 21) bits A24 SUPP4
8-i I
Word 21) bits A25 SUPPS
12-15
Word 22) bits A26 SUPP6
0-3
Word 22, bits A2'7 SUPP7
4-7
Word 22) bits A28 SUPPS
8-11
Word 22, bits A29 SUPP9
12-15
Word 23) bits A30 SUPPIO
0-3
Word 23, bits A31 SUPP11
4-7
Word 23) bits A32 SUPP12
8-11
Word 23, bits A33 SUPPI3
12-15
Word 24) bits A34 SUPP14
0-3
Word 24) bits A35 SUPP15
4-7
Word 24, bits A36 SUPP16
8-11
Word 24, bits A37 SUPP17
12-15
Word 25) bits A38 SUPP18
0-3
Word 25) bits A39 SUPP19
4-7
Word 25, bits A40 SUPP20
8-11
Word 25) bits A4I SUPP21
12-15
Word 26, bits A42 SUPP22
0-3
Word 26, bits A43 SUPP23
4-7
Word 26, bits A44 SUPP24
8-11
Word 26) bits A45 SUPP25
12-15
6. 14 Digit
MC VNet Calling
Card:
Word 15, bits Al X
12-I5
Word 16) bits A2 X
0-3
Word 16, bits A3 X
4-7
Word 16) bits A4 X
8-l I
Word 16, bits p5 X
12-15
Word i7, bits A6 X
0-3
Word 17, bits A7 X
4-7
Word 17, bits A8 X
8-11
Word 17, bits A9 X
12-15
Word .18, bitsA10 X
0-3
Word 18, bits A11 TBCD-A
4-7
Word 18) bits A12 TBCD-A
8-11
Word 18, bits A13 TBCD-A
12-15
525
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PCTIUS97/21174
Word l~) Bit A~ Description
Word I9, bits A14 TBCD-A
0-3
Word 19, bits A15 TBCD-Null
4-7
Word 19) bits A16 SUPPI
8-I I
Word 19) bits A17 SUPP2
12-15
Word 20, bits A18 SUPP3
0-3
Word 20, bits A 19 SUPP4
4-7
Word 20) bits A20 SUPPS
8-11
Word 20, bits A21 SUPP6
12-IS
Word 21, bits A22 SUPP7
0-3
Word 21) bits A23 SUPP8
4-7
Word 21, bits A24 SUPP9
8-11
Word 21, bits A25 SUPP10
12-15
Word 22) bits A26 SUPP11
0-3
Word 22, bits A27 SUPP12
4-7
Word 22, bits A28 SUPPt3
8-11
Word 22, bits A29 SUPP14
12-15
Word 23, bits A30 SUPP1S
0-3
Word 23, bits A31 SUPP 16
4-7
Word 23, bits A32 SUPP 17
8-11
Word 23) bits A33 SUPP18
12-15
Word 24, bits A34 SUPP19
0-3
Word 24,bits A35 SUPP20
4-7
Word 24, bits A36 SUPP21
8-11
Word 24) bits A37 SUPP22
12-1S
Word 25, bits A38 SUPP23
0-3
Word 25) bits A39 SUPP24
4-7
Word 2S) bits A40 SUPP25
8-11
Word 2S) bits A41 SUPP26
12-1S
_ _
Word 26) bits A42 SUPP27
0-3
Word 26, bits A43 SUPP28
4-7
Word 26) bits A44 SUPP29
8-11
Word 26, bits A45 SUPP30
12-15
7. OSD/OTG:
Word 15, bits A1 X (OSID)
12-15
Word 16) bits A2 X (OSID)
0-3
Word 16) bits A3 X (OSID)
4-7
Word 16) bits A4 X (OTG)
8-11
Word 16) bits AS X (OTG)
12-15
i Word 17, bits A6 X (OTG)
0-3
Word 17, bits A7 X (OTG)
4-7
Word 17, bits A8 TBCD-Nuli
8-11
Word 17) bits A9 TBCD-Nuil
12-15
Word 18) bits A10 TBCD-Null
0-3
Word 18) bits A11 TBCD-Null
4-7
Word 18, bits A12 TBCD-Null
8-11
Word 18, bits A13 TBCD-Null
12-15
526
SUBSTITUTE SHEET (RULE 28)
CA 02279845 1999-OS-17
WO 98/23080 _ p~~~~7121174
I~ Word k) Bit JJ ~ Description
Word 19) bits A14 TBCD-Null
0-3
Word 19) bits A15 TBCD-Null
4-7
Word 19, bits A16 TBCD-Nul1
g-11
Word 19) bits A17 TBCD-Null
12-15
Word 20) bits A18 TBCD-Null
0-3
Word 20, bits A 19 TBCD-Null
4-7
' Word 20, bits A20 TBCD-Null
8-11
Word 20, bits A21 TBCD-Null
12-15
Ward 21; bits A22 TBCD-Null
0-3
Word 21, bits A23 TBCD-Null
4-7
Word 21, bits A24 TBCD-Null
g-11
Word 21, bits A25 TBCD-Null
12-15
Word 22) bits A26 TBCD-Null
0-3
Word 22, bits A27 TBCD-Null
4-7
Word 22) bits A28 TBCD-Null
8-I 1
Word 22, bits A29 TBCD-Null
12-IS
Word 23, bits A30 TBCD-Null
0-3
Word 23, bits A31 TBCD-Null
4-7
Word 23) bits A32 TBCD-Null
8-11
Word 23) bits A33 TBCD-Null
12-15
Word 24) bits A34 TBCD-Null
0-3
Word 24) bits A35 THCD-Null
4-?
Word 24, bits A36 TBCD-Null
8-I 1
Word 24, bits A37 TBCD-Null
12-15
Word 25) bits A38 TBCD-Null
0-3
Word 2S, bits A39 TBCD-Null
4-7
Word 25) bits A40 TBCD-Null
8-1 I
Word 25, bits A41 TBCD-Null
12-IS
Word 26) bits A42 TBCD-Null
0-3
Word 26) bits A43 TBCD-Null
4-7
Word 26) bits A44 TBCD-Null
8-l l
Word 26) bits A45 TBCD-Null
12-15
OSID = Originating Switch ID
OTG = Originating Trunk ID
8. Telecommunication/1?TT Cards:
Word 15) bits A1 X
12-15
Word 16) bits A2 X
0-3
Word 16, bits A3 X
4-7
Word 16) bits A4 X
8-11
Word 16, bits AS X
12-15
Word 17) bits A6 X
0-3
Word I7, bits A7 X
4-7
Word 17, bits A8 X
8-11
Word 17, bits A9 X
12-15
Word 18, bits A 10 X
0-3
Word 18) bits A I 1 X
4-7
Word 18, bits A12 X
8-11
Word 18) bits A13 X
12-15
' 527
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
wo 9sn3oso rc-r~rs9~nma
Word ~, lilt k Description
Word 19, bits 0-3 A 14
Word 19, bits 4-7 A15 X
Word 19) bits 8-11 A16 X
Word 19) bits 12-15 Ai7 X
Word 20, bits 0-3 A18 X
Word 20) bits 4-7 A19 X
Word 20, bits 8-11 A20 X
Word 20, bits 12-15 A21 X
Word 21, bits 0-3 A22 X
Word 21) bits 4-7 A23 X
Word 21, bits 8-11 A24 TBCD-Null
Word 21) bits 12-15 A25 SUPP1
Word 22) bits 0-3 A26 SUPP2
Word 22) bits 4-7 A27 SUPP3
Word 22) bits 8-11 A28 SUPP4
Word 22, bits 12-15 A29 SUPPS
Word 23, bits 0-3 A30 SUPPS
- Word 23, bits 4-7 A31 SUPP7
Word 23) bits 8-11 A32 SUPP8
Word 23, bits 12-15 A33 SUPP9
Word 24) bits 0-3 A34 SUPP10
Word 24, bits 4-7 A35 SUPP11
Word 24) bits 8-11 A36 SUPP12
Word 24) bits 12-IS A37 SUPP13
Word 25, bits 0-3 A35 SUPP14
Word 25) bits 4-7 A39 SUPPIS
Word 25, bits 8-11 A40 SUPPI6
Word 25) bits 12-15 A41 SUPP17
Word 26, bits 0-3 A42 SUPP18
Word 2b) bits 4-7 A43 SUPP 19
Word 26, bits 8-11 A44 SUPP20
Word 26, bits 12-15 A45 SUPP2I
9. Business Group ID:
Word 15, bits 12-15 AI X
Word 16) bits 0-3 A2 X
Word 16) bits 4-7 A3 X
Word 16, bits 8-11 A4 X
Word 16, bits 12-IS AS X
Word 17, bits 0-3 A6 X
Word 17, bits 4-7 A7 TBCD-Null
Word 17) bits 8-11 A8 SUPPI
Word 17) bits 12-15 A9 SUPP2
Word 18, bits 0-3 A10 SUPP3
Word 18, bits 4-7 A11 SUPP4
Word 18, bits 8-11 A12 SUPPS
Word 18, bits 12-15 A13 SUPP6
528
SUBSTITUTE SHEET (RULE 26)
CA 02279845 ~199~9-05-17
WO 98/23080 PGT/US97/21174 -
Word ~, Bit ~Y Description
Word 19, bits A l4 SUPP7
0-3
Word 19) bits A15 SUPP8
4-7
Word 19) bits A16 SUPP9
8-11
Word I9, bits A17 SUPP10
12-15
Word 20, bits A18 SUPPI1
0-3
Word 20, bits A19 SUPPI2
4-7
Word 20, bits A20 SUPPI3,
8-11
Word 20) bits A21 SUPP14
12-15
Word 21) bits A22 SUPP 15
0-3
Word 21) bits A23 SUPP16
4-7
Word 21) bits A24 SUPPI7
8-11
Word 21, bits A25 SUPPI8
12-IS
Word 22) bits A26 SUPPI9
0-3
Word 22) bits A27 SUPP20
4-7
Word 22, bits A28 SUPP21
8-11
Word 22, bits A29 SUPP22
12-15
Word 23) bits A30 SUPP23
0-3
Word 23, bits A31 SUPP24
4-7
Word 23, bits A32 SUPP25
8-11
Word 23, bits A33 SUPP26
12-15
Word 24, bits A34 SUPP27
0.3
Word 24) bits A35 SUPP28
4..7
Word 24) bits A36 SUPP29
8-11
Word 24, bits A37 SUPP30
12-15
- Word 25, bits A38 TBCD-Null
0-3
Word 25) bits A39 TBCD-Null
4-.7
Word 25, bits A40 TBCD-Null
8-I1
Word 25, bits A4I TBCD-Null
12-15
Word 26) bits A42 TBCD-Null
0-3
Word 26, bits A43 TBCD-Null
4-7
Word 26) bits A44 TBCD-Null
8-I1
Word 26, bits A45 TBCD-Null
12-15
I1. Network Information:
Word 15, bits A1 X
12-15
Word 16, bits A2 X
0-3
Word 16) bits A3 X
4-7
Word 16) bits A4 X
8-11
Word 16) bits A5 TBCD-Null
12-15
Word 17) bits A6 SUPPI
0-3
Word 17) bits A7 SUPP2
4-7
Word 17) bits A8 SUPP3
8-11
Word 17, bits A9 SUPP4
12-15
Word 18; bits A10 SUPPS
0-3
Word 18, bits A11 SUPP6
4-7
Word 18) bits A12 SUPP7
8-11
Word 18) bits A13 SUPP8
12-15
529
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23p80 - PCT/US97121174
Word ~, Bit ~Y Description
Word 19, bits 0-3 A14 SUPP9
Word 19, bits 4-7 A15 SUPP10
Word l9, bits 8-11 A16 SUPP11
Word 19, bits 12-15 A17 SUPP12
Word 20) bits 0-3 A18 SUPP13
Word 20, bits 4-7 A19 SUPP14
Word 20) bits 8-l I A20 SUPP15
Word 20) bits I2-IS A21 SUPP16
Word 21, bits 0-3 A22 SUPP17
Word 2 1) bits 4-7 A23 SUPPl8
Word 21, bits 8-I1 A24 SUPP19
Word 21, bits 12-15 A25 SUPP20
Word 22, bits 0-3 A26 SUPP21
Word 22, bits 4-7 A27 SUPP22
Word 22, bits 8-11 A28 SUPP23
Word 22, bits 12-15 A29 SUPP24
Word 23, bits 0-3 A30 SUPP25
Word 23) bits 4-7 A31 SUPP26
Word 23) bits 8-11 A32 SUPP27
Word 23) bits 12-15 A33 SUPP28
Word 24) bits 0-3 A34 SUPP29
Word 24, bits 4-7 A35 SUPP30
Word 24) bits 8-11 A36 TBCD-Null
Word 24, bits 12-15 A37 TBCD-Null
Word 25, bits 0-3 A38 TBCD-Null
Word 25, bits 4-7 A39 TBCD-Null
Word 2:5, bits 8-11 A40 TBCD-Null
Word 25) bits 12-15 A41 TBCD-Null
Word 26) bits 0-3 A42 TBCD-Null
Word 26, bits 4-7 A43 TBCD-Null
Word 26, bits 8-11 A44 TBCD-Null
Word 26, bits 12-IS A45 TBCD-Null
12. Network Call Identifier (NCID) -
If the NCID is recorded in
the "A" field) it will be recorded in
binary beginning with Al.
The Entry Code field will be indicative
of the call processing
associated with the particular call or
"0". If the NCID is recorded
in the NCID field of a 64 word call record,
the Entry Code will
also be indicative of the call processing
associated with the
particular call or "0". The NCID is comprised
of the following:
Originating Switch ID
Originating Trunk Gmup
Originating Port Number
Timepoint One
NCID Sequence Number
I
~i Word 27) bits 0-3 Feature Code (FC): Same as CDR/PNR format.
I Word 27) bits 4-7 Terminating Network Code (TNC): Same
as CDR/PNR format.
Word 27, bits 8-11 Network Access Type (NAT): Same as CDR/PNR
format.
Word 27, bits 12-15 Timepoint 7 Qualifier (TP&Q): Same as
CDR/PNR format.
Word 28, bits 0-6 Entry Code (EC): Same as CDR/PNR format.
Word 28, bits 7-9 Prefix Digits (PD): Same as CDR/PNR format.
530
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/Z3080 PCT/US971~1174
Word-~, Bit ~ Description
Word 28) bits !0-12 NCS/DAP ID (NDID): Same as CDR/PNR format.
Word 28, bits 13-IS Division ID (DIVID): Same as CDRIPNR fotittat.
Word 29) bit 0 Distant Overflow (DO): Same as CDR/PNR
format.
Word MCI Network Overflow (MNO): This bit indicates
29, whether
bit
1
or not
the Cause parameter that initiated overflow
was generated due to
MCI network detected conditions versus
Reseller or Customer
Location detected circumstances. This bit
is set to 1 if the MNO
subfield of the MBCSI parameter is set
to i which indicates that
the cause parameter that initiated overflow
was generated due to
MCI network detected conditions. This bit
is set to 0 if the MNO
subfield of the MBCSI parameter is set
to 0 which indicates that
the cause parameter that initiated overflow
was generated due to a
LEC) BOC, or Reseller condition.
Word Customer Connect (ce): Same as CDR/PNR
29) format.
bit
2
Word Inter-Network (IN): Same as CDR/PNR format.
29,
bit
3
Word Reported Overflow (RO): Same as CDR/PNR
29) format.
bit
4
Word Not Used.
29,
bit
Word Call Direction (CD): Same as CDR/PNR format.
29,
bit
6
Word Destination (DE): Same as CDR/PNR format.
29,
bit
7
Word Dedicated Termination (DT): Same as CDR/PN
29,
bit
8
R format.
Word Not Used.
29)
bits
9-10
Word Satellite (SA): Same as CDR/PNR format.
29)
bit
11
Word Nature of Calling Location ID (NOCLI):
29, Same as CDR/PNR
bits
12-15
format.
Word Carrier Number (CN): Same as CDR/PNR format.
30,
bits
0-15
Word Authorization Code ID (ACIF): Same as CDR/PNR
31, format.
bits
0-3
Word Release Code (RC): Same as CDR/PNR format.
31)
bits
4-10
Word NCiD Sequence Number: Same as CDR/PNR format.
31,
bits
11-13
Word NCID Location (NCIDLOC): Same as CDR/PNR
31,
bit
14
format.
Word Remote AN1 Screened (RS): Same as CDR/PNR
31,
bit
format.
Word Not Used.
32,
bits
0-15
Word
33)
bits
0-15
Word Destination Address (DA): Records up to
34, 25 digits of the
bits
0-15
Word destination address in TBCD format in the
35, sequence that the
bits a
0-15
y
Word re
36) received or translated to) starting with
bits D1. Unused bytes contain
0-15
Word
37
bits
0-15
, TBCD-Null.
Word
38)
bits
O-15
Word
39,
bits
0-IS
Word
40,
bits
0-3
531
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97l21174 -
Word !/, Bit A~ Description
- i
7-digit DD IDDD
10-digit
D
Word 34, bits D1 N N N CC
0-3
Word 34) bits D2 X X X CC
4-7
Word 34, bits D3 X X X CC
8-11
Word 34, bits D4 X N N NN
l2-15
Word 35, bits DS X X X NN
0-3
Word 35) bits D6 X X X~ NN
4-7
Word 35, bits D7 X X X NN
8-11
Word 35, bits D8 X(TS1D)X X NN
12-IS
Word 36, bits D9 X(TSID)X X NN
0-3
Word 36) bits D10X(TSID)X X NN
4-7
Word 36, bits D11X(TTG) X(TSID)T-NuilNN
8-11
Word 36) bits D12X(TTG) X(TSID)T-NullNN
12-15
Word 37, bits D13X('TTG)X(TSID)T-NullNN
0-3
Word 37, bits D14X(TTG) X(TTG)T-NullNN
4-7
Word 37) bits D15T-Null X(TTG)T-NullNN
8-11
Word 37, bits D T-Null X(TTG)T-NuIIT-Null
12-15 16
Word 38, bits D T-Null X(TTG)T-NullT-Null
0-3 17
Word 38) bits Dl8T-Null T-NullT-NullT-Null
4-7
Word 38, bits D19T-Null T-NullT-NullT-Null
8-11
Word 38, bits D20T-Null T-NullT-NullT-Null
12-15
Word 39, bits D21T-Null T-NullT-NullT-Null
0-3
Word 39, bits D22T-Null T-NuilT-NullT-Nuli
4-7
Word 39, bits D23T-Null T-NullT-NullT-Null
8-11
Word 39) bits D24T-Null T-NullT-NullT-Null
12-15
Word 40) bits D25T-NuII T-NullT-NullT-Null
0-3
CC = Customer
Connect
NN = National
Number
TSID = Terminating
Switch ID
TTG = Terminating ID
Trunk
T-Null = TBCD-Null
532
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98n3080 PCT/US97/21174
I~ Word ~, Bit ~ ~ Description
18-digit
Word 34, bits-0-3D1 N
Word 34, bitsD2 N
4-7
Word 34, bitsD3 N
8-11
Word 34, bitsD4 N
12-IS
Word 35, bitsDS N
0-3
Word 3S, bitsD6 N
4-7
Word 35) bitsD7 N
8-11
Word 35) bitsD8 N
I2-1S
Word 36, bitsD9 N
0-3
Word 36, bitsD N
4-7 10
Word 36, bitsD N
8-I 1 11
Word 36, bitsD12 N
12-IS
Word 37, bitsD13 N
U-3
Word 37) bitsD14 N
4-7
Word 37, bitsDIS N
8-11
Word 37, bitsD16 N
I2-1S
Word 38, bitsD17 N
0-3
Word 38, bitsD18 N
4-7
Word 38, bitsD19 X(TSID)
8-11
Word 38) bitsD20 X(TSID)
12-15
Word 39, bitsD21 X(TSID)
0-3
Word 39, bitsD22 X(TTG)
4-7
Word 39, bitsD23 X(TTG)
8-11
Word 39, bitsD24 X('ITG)
I2-1S
Word 40) bitsD2S X{TTG)
0-3
TSID = Terminating Switch ID
TTG = Terminating Trunk ID
Word 40, bits 1'retranslated a
4-1S Digits (PTD):
Represents
up to 15
digits of
Word 41, bits number that ed aller
0-1S is the translation by
of a number the
dial c
.
Word 42, bits
0-15
Word 43, bits 10 di
0-15 i
g VNet/
t
VNet, OOY 7 digitIDDD
SAC
DNIS, SAC VNet
or or
1S
digit
Hotline Code SNS
(example)
Word 40, bitsPTD 1 0 N N
4-7 N
Word 40, bitsPTD2 X 0 X N
8-11
Word 40) bitsPTD3 X Y X N
12-1S
Word 41, bitsPTD4 N N X N
0-3
Word 41, bitsPTDS X X X N
4-7
Word 41, bitsP'TD6 X X N
8-11 X
Word 4L, bitsPTD7 X X X N
12-1S
- Word 42, bitsPTD8 X X T-NullN
0-3
Word 42) bitsPTD9 X X T-NullN
4-7
Word 42, bitsPTD10 X T-NullN
8-11 X
Word 42, bitsPTD11 T-NullT-NullN
12-1S T-Null
Word 43, bitsPTD12 T-NullT-NullN
0-3 T-Null
Word 43) bitsPTD13 T-NullT-NullN
4-7 T-Null
Word 43, bitsPTDI4 T-NullT-NullN
8-1 I T-Null
Word 43) bitsPTD15 T-NullT-NullN
12-1S T-Null
il ( T-Null = TBCD-Null
533
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/Z3080 PCT/US97121174
Word ~I, Bit ~' Description
~I
Word 44) bits 0-7 Enhanced International Routing (EIR)
Call Type: Contains the
EIR call type ID as received from the
DAP in the NCS billing
information parameter or from the operator
in the NCS billing
information ISUP RLT parameter. Recorded
in binary.
Word 44) bits 8-14 Overflow Cause Value (OVFVAL): This field
is the binary
equivalent of the first cause value received
or formatted in-switch.
This value is taken from the cause value
subfield in ctit: cause
parameter that initiated overflow.
Word 44, bit 15 Counts As Bid (CB): This field is used
with the EIR feature. The
bit is set to ' 1' or '0' as per the
information received from the
DAP in the CB field of the NCS billing
information parameter or
from the operator in the NCS billing
information ISUP RLT
parameter.
0 = Does not count as bid (default)
I = Counts as bid
Word 45) bits 0-3 Overflow Cause Location (OVFCL): This
field is the binary
equivalent to the value recorded from
the first cause location
received or formatted in-switch. This
information is taken from
the cause location subfield in the cause
parameter that initiated
overflow.
Word 45, bits 4-15 Desired Terminating Address (DTA): These
15 bytes contain the
Word 46) bits 0-IS originally intended or "desired" termination
before overflow was
Word 47, bits 0-IS triggered. They contain either: 1) the
desired terminating switch
Word 48) bits 0-IS id and trunk group for calls that were
sent to a DTC termination)
2) a national number, or 3) international
number based on what
the action code returned from the DAP
for the desired
termination.
DTC
DTSID +
DTTG DDD
Word 45) bits 4-7 DTA 1 0 N
Word 45) bits 8-11 DTA2 X(DTSID1) X
Word 45) bits 12-15 DTA3 X(DTSiD2) .
X
Word 46, bits 0-3 DTA4 X(DTSID3) N
Word 46, bits 4-7 DTAS 0 X
Word 46) bits 8-11 DTA6 X(DTTGI) X
Word 46) bits 12-15 DTA7 X(DTTG2) X
Word 47, bits 0-3 DTAB X(DTTG3) X
Word 47) bits 4-7 DTA9 X(DTTG4) X
Word 47, bits 8-I1 DTA10 TBCD-Null X
Word 47, bits 12-15 DTA1I TBCD-Null TBCD-Null
Word 48) bits 0-3 D'fAl2 TBCD-Null TBCD-Null
i Word 48, bits 4-7 DTA13 TBCD-Null TBCD-Null
Word 48, bits 8-11 DTA14 TBCD-Null TBCD-Null
Word 48, bits 12-IS DTA15 TBCD-Null TBCD-Null
DTSID = Desired Termination Switch ID
DTTG = Desired Termination Trunk Group
534
SUBSTITUTE SHEET (RULE 28)
CA 02279845 1999-OS-17
w° ° ~ rcrms9~mi7a
Word Il, Bit A~ Description
IDDD DTC
(example) (future)
Word 45, bits 4-7 DTA 1 CC X(DTSID 1 )
Word 45, bits 8-11 DTA2 CC X(DTSID2)
Word 45, bits 12-15 DTA3 CC X(DTSID3)
Word 46, bits 0-3 DTA4 NN X(DTSID4)
Word 46) bits 4-7 DTAS NN X(DTTGI)
~
Word 46, bits 8-11 DTA6 NN
X(DTTG2)
Word 46, bits 12-15 DTA7 NN X(DTTG3)
Word 47) bits 0-3 DTA8 NN X(DTTG4)
Word 47, bits 4-7 DTA9 NN X(DTTGS)
Word 47, bits 8-.l l DTA10 NN TBCD-Null
Word 47, bits 12-15 DTAI l NN TBCD-Null
Word 48, bits 0-3 DTA12 NN TBCD-Null
Word 48, bits 4-7 DTA13 NN TBCD-Null
Word 48, bits 8-11 DTA14 NN TBCD-Null
Word 48) bits 12-15 DTA15 TBCD-Null TBCD-Null
CC = Customer Connect
DTSID = Desired Tetatination Switch ID
DTTG = Desired Termination Trunk Group
NN = National Number
Word 49, bits 0-6 Overflow Count (OVFC): Indicates the total
number of
intermediate overflow attempts before
successful termination was
achieved. This value is incremented each
time the DAP is
accessed for overflow information.
Word 49) bits 7-12 Desired Termination Action Code (DTAC):
This field represents
the action code which was received from
the DAP in the first
response. This information is used to
identify the type of
information which is recorded in the DTA
field.
Word 49) bit 13 Not Used.
Word 49) bits 14-15 Network CaII Identifier (NCID): Contains
the binary
Words 50-54) bits 0-15 representation of the NCID. The NC1D is
recorded here at
intermediate and terminating switches
if the Authcode field is
being used to record other information.
The NCID is created at
the originating switch and is passed to
intermediate and
terminating switches. The format of the
NCID is:
Originating Switch ID (OSID)
Originating Trunk Group (OTG)
Originating Port (OP)
Timepoint 1 (TPI)
NCID Sequence Number
Words 55-58) bits 0-15 Not Used.
Word 59, bits 0-10
535
SUBSTITUTE SHEET (RULE 2Bj
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
Word II; Bit ~ Description
Word 59) bits 11-13 User to User Type (UUS Type): Contains
a binary representation
used to identify the type of User to User
services being utilized.
If this field is set to '0' and the UUIE
Count field is sec to a value
other than '0') then non-call associated
User to User information
is being transferred.
0 = No message or call associated UUS
invoked (default)
1 = MA-UUI only
2 = CA-TSC at call setup only
3 = CA-TSC after gall setup only
4 = CA-TSC at call setup and CA-TSC after
call setup
5 = MA-UUI and CA-TSC at call setup
6 = MA-UUI and CA-TSC after call setup
7 = MA-UUI and CA-TSC at call setup and
CA-TSC after call
setup
Word 59) bits 14-15 User to User Information Element Count
(UUIE Count): Contains -
Word 60, bits 0-13 the binary count of UUIE delivered in
either direction per TSC.
Both the originating and terminating switches
shall maintain a
counter to count the number of UUIE delivered
on a per call
basis. Each switch shall count all UUIE
in either direction
whether delivered or not. The billed parry
shall be responsible for
paying for the UUIE transport. If the
count reaches the maximum
value of b5535) it will hold at this value
until a new call record is
created. The beared channel will be disconnected
one the
maximum count is reached.
Word 60, bits 14-IS Overflow Case Coding Standard (OVFCS):
Contains the binary
equivalent of the first coding standard
received or formatted in-
switch. This value is taken from the coding
standard subfield in
the cause parameter that initiated overflow.
It will not be
overwritten by subsequent coding standards
received or in-switch
formatted values. This field is used for
enhanced overflow calls
only.
Word 61, bits 0-15 Originating NX64 Bitmap: Records the port
number that
Word 62, bits 0-7 corresponds with the originating control
channel of the call in the
originating port in the CDR/PNR. This
bitmap is used to identify
the subsequent channels in the same T1
timespan that are used in
the call. A particular bit is set to indicate
if this channel was used
on the call. The number of bits that are
set is used to identify the
number N in an NX64 call.
Word 62, bits 8-15 Terminating NX64 Bitmap: Record the port
number that
Word 63, bits 0-15 corresponds to the terminating control
_i channel of the call in the
terminating port in the CDR/PNR. This
bitmap will be used to
identify the subsequent channels is the
same T1 span that are used
in the call. A particular bit is set to
indicate if this channel was
used oa the call. The number of bits that
are set is used to identify
the number N in an NX64 call. In general)
each channel transmits
at 64 Kbits/second, and if a customer
needs more than one
channel) this bitmap indicates which channels
are used in the call.
536
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/Z3080 PCTlUS97/21174
Word A~) Bit ~ I Description
Table 303 OSR/POSR Record Format~
Word O, bits 0-3 Call Record Id (CRID): Identifies the
record type.
0 = Default
- 1 = CDR
2 = SER
3 = PNR
4 = OSR
5 = POSR
6 = ECDR
? = EPOSR
8 = EOSR
9 = EPOSR
10-15 = Not Used
Word 0) bits 4-15 Call Disconnect ID (CDID): Identifies
the call record. Each call
rscord has a unique ID number. These
12 bits contain the 12 least
significant bits of the CDID.
Word 1) bits 0-15 Timepoint 1 (TPl): A binary count of
the number of seconds that
Word 2) bits 0-15 occurrtd between midnight (UTC) on January
l) 1976) and the
time that the incoming call was detected
by the switch.
Word 3, bits 0-12 Timepoint 4 (TP4): A binary count of
the number of seconds
between Timepoint 1 and the time the
operator position was seized
by the switch.
Word 3, bits 13-15 Timepoint 6 (TP6): A binary count of
the number of seconds
Word 4) bits 0-0 between titnepoint 1 and the time Answer
Supervision was
detected or received. This is the time
that it took for the call to be
answered by the person or audio system
being called.
Word 4, bits 10-15 Timepoint 7 (TP7): A binary count of
the number of seconds
Word 5) bits 0-15 between timepoint 1 and the time that
the originating or -
terminating parry disconnected whichever
is first.
Word 6, bits 0-15 Originating Port (OP): The absolute port
number of the
Word 7, bit 1 originating trunk. Originating trunk
is the line on which the call
came to the switch.
Word ?) bits 2-IS Terminating Port (TP): The absolute port
number of the last
Word 8, bits 0-1 terminating trunk seized for an outgoing
call attempt. The
terminating trunk is the last line on
which the call is transmitted.
Word 8, bits 2-14 Originating Trunk Group (OTG): A binary
number expressing the
Originating Trunk Group number of the
originating trunk. An
originating trunk group is a group of
ports coming from the same
location.
Word 8) bit 15 Terminating Tnmk Group (TTG): A binary
number expressing the
Word 9, bits 0-11 Terminating Trunk Group number of the
Terminating trunk. A
terminating trunk group is a group of
ports going to the same
location. If a call falls because no
trunks are available, record the
last trunk group number that was attempted.
537
SUBSTITUTE SHEET (RULE 26~
CA 02279845 1999-OS-17
WO 98/23080 PCT/I1S97I21174
Word Il, Bit !I Description
I
Word 9) bits 12-15 Timepoint 3 qualifier (TP3Q): Contains
the outpulsed call
disposition qualifier which provides
the telephone number of the .
person making the call to the person
being called. The person
being called needs to have signed up
for the "ANI Delivery"
service and have a display device for
displaying the caller's
telephone number.
0 = Default
1 = ANIICSI was delivered
2 = DNIS was delivered
3 = AN/CSI and DNIS were delivered
4-5 = Not Used
6=NCT
7 = NCT) AN/CSI was delivered
8 = NCT, DNIS was delivered
9 = NCT, ANIICSI and DNIS was delivered
10 = NCT Tandem.
11-15 = Not Used
Word 10, bits 0-1 Timepoint 6 qualifier (TP6Q): Contains
the answer supervision
qualifier indicating the way in which
the telephone call was
answered.
0 = Hardware detected an Answer
1 = Software detected Voice
2 = Not Used
3 = Operator/NARS detected an Answer
I Word 10) bits Action Code (AC): The switch provides
2-7 an action code which
indicates the type of destination address,
or what type of telephone
number was called, or an error code.
0 = Default
1 = 7-digit number without overtlow
2 = 7-digit number with overflow .
3 = DDD number
4 = IDDD number
5 = Switch generated Action Code
6 = Incoming exclusion failure
7 = ID code failure
8 = Unexpected error occurs in the NCS/DAP
9 = Misdialed number and the NCS/DAP
is unable to translate
the dialed number
10 = 10-digit number without overflow
11 = 10-digit number with overflow
12 = National with overflow
13 = International with overflow
14 = ANI not found
15 = NPA-NXXX not found
16 = Pilot number not found
17 = Associated partition not found
18 = ADF format error
19 = Switch ID not found
20 = 800 number not found
538
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21I74
Word #) Bit~# Description
- --. "_._
_
21 = 800 number out of band
22 = Not Used
23 = Invalid ID code
24 = Range privilege
25 = 7-digit number not in database
26 = 10-digit exclusion feature
27 = 900 number not found
28 = 900 number out of band
29 = Not Used
30 = NCS network management blocked
31 = NCS Gate Denial
32 = FIezSTC) Overflow Not Allowed
33 = FIezSTC) Overflow Allowed
34 = SAC Number Not Found
35 = SAC Number Out of Band
36 = 700 Number Not Found
37 = ?00 Number Out of Band
38 = ICR designated Out of Band
39 = NCT - Reversed call direction
40-48 = Not Used
49 = Infotmatian Call
50 = Flexible Direct Termination Call
without overflow
51 = Flexible Direct Termination Call
with overflow
52 = Outbound IVNet without overflow
53 = Outbound IVNet with overflow
54 = Global Switch Profile not found
55 = ANI Index Provided by DAP
56-62 = Not Used
63 = International Inbound APP
Word 10, bits 8-11 Originating Trunk Class (OTC): Indicates
what type of originating
trunk was accessed.
0 = ONAL (FG-A)
1 = ONAT (FG-B, FG-C, FG-D) CAMA) LAMA)
_
2 = DAL, VNET CAMA, FGS-DAL)
3 = IMT (Inband or SS7)
4 = International Circuit (RI) R2) #5)
#6, #7)
5 = ISDN PRI
6 = OST
7-15 = Not Used
Word 10, bits 12-15 Terminating Trunk Class (TTC): Indicates
what type of
terminating trunk was accessed.
0 = ONAL (FG-A)
1 = GNAT (FG-B, FG-C, FG-D) CAMA, LAMA)
2 = DAL, VNET CAMA) FGS-DAL)
3 = IMT (Inband or SS7)
4 = International Circuit (R1, R2, #5,
#6, #7)
5 = ISDN PRI
6 = OST
7-15 = Not Used
FG = Feature Group
539
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/Z3080 PGTILTS97/21174
Word It, Bit Il Description
Word 1 l) bits Information Digits (1D): The switch receives
0-7 these digits from the
originating trunk group indicating the
type of telephone on which
the telephone call oryginated) such as
a home telephone, pay
telephone) or prison telephone.
FG-B Direct,
CAMA FG-D MCI IMT ' I15~ N6
bits 0-3: TBCD Null X X TBCD Null X
bits 4-7: X X X X X
Word 11, bits 8-11 Originating NACC (ONACC): This field
contains the Notth
American Coding Convention code which
is received in the
incoming digit stream to the operator
switch. This code identifies
the type of assistance required for inbound
international calls.
0 = default
', 1 = 121 (Assistance without call completion)
2 = 131 (Directory assistance)
3 = 151 (Assistance with call completion)
4 = 160 (Manual transit)
5 = 191 (Call USA)
i
6-15 = Not Used
~I Word 11) bits Terminating NACC (TNACC): This field
12-15 contains the North
I, American Coding Convention code which
is transmitted in the
I incoming digit stream to another operator
switch. This code
identifies the type of assistance required
at the next operator
switch.
0 = default
1 = 121 (Assistance without call completion)
2 = 131 (Directory assistance)
3 = 151 (Assistance with call completion)
I 4 = 160 (Manual transit)
5 = 191 (Call USA)
6-15 = Not Used
~~ Word 12) bits Call Location ID (CLI): Represents the
0-15 10 digits from where the
Word 13, bits 0-15 call came. If switch receives more than
10 digits) record them in
~ Word 14, bits the ECDR/EPOSR.
0-7
1. VNet CAMA DAL originations: If CSI
is available, prefix the
CSI with filed HNPA and HNXX information)
if available, and
record. Use NOCLI value of 7.
2. FG-C originations: If ANi or CSI information
is not available
and the number is in the OOY+NXX+XXXX
format, record the
OOY in CLI 1-3, and record the OSID/OTG
in CLI4-10. Use
NOCLI value of 8.
3. Inband FG-D Otiginations: Record the
ANI that was received
starting with CLI1. Use NOCLI value of
1.
540
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
PG"T/US9?/Zi174 -
Word A~. Bit ~ Description
4. SS? FG-D Originations: Record the charge
number) if
available. If not available) record the
calling parry number. Use
NOCLI value of 2 or 3.
S. International originations: Record
the country code and the
national number of the calling party.
Use NOCL1 of 9.
6. SS7 IMTs Originations: Record the following
information in
this order of importance: 1) charge number,
2) calling party
number) 3) OSID/OTG from genetic digits.
Use NOCLI of 2, 3,
or 8.
7. SS? Reseller Originations: The CLI
field is f lied with THCD-
Nulls.
8. SS? Private Network Originations: The
CLI field is filled with
TBCD-Nulls.
9. PRI Organizations: Record the calling
party number received in
the ISDN setup message.
The format:
1-10 digit Iacotning
ANI OSID/OTG Int'1
Word 12, bits 0-3 CLI1 TBCD Null X(CC)
Word 12) bits 4-? CLI2 TBCD Nuil X(CC)
Word 12, bits 8-11 CLI3 TBCD Null X(CC)
Word 12, bits 12-15 CLI4 X(OSID) X(N
Word 13) bits 0-3 CLIS X(OSID) X(NN) _
Word 13, bits 4-7 CLI6 X(OSID) X(N
Word 13, bits-8-II CLI? X(OTG) X(NN)
Word 13) bits 12-15 CLI8 X(OTG) X(NN)
Word 14, bits 0-3 CLI9 X(OTG) X(NN)
Word 14, bits 4-? CLIIO X(OTG) X(NN)
CC = CuStOIIICr COIIIlect
NN = National Number
OSID = Originating Switch NSC ID (000-999)
OTG = Originating Trunk Group (0000-8191
)
541
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 - PCT/US97121174
Word A', Bit !f Description
Word 14, bits 8-15 Authorization Codes: Represents billed
22 digits of who gets for
Word 15, bits 0-15 the call which includes one or
more of the following and/or
an
Word 16, bits 0-15 optional Supplementary Code:
Word 17, bits 0-15
Word 18, bits 0-15 1. Authorization Code - Contains
the authorization code digits.
Word 19, bits 0-l5 AUTHI-AUTHS records the dialed
or filed authorization codes,
afterwhich is recorded an optional
variable 1-4 digit security
code,
SECI-SEC4, comprised of TBCD After
digits 0-9 and A-D. the
last digit, record a TBCD-Null,
afterwhich record any
supplementary code digits, SUPP1-SUPP12.
Record TBCD-Nuli
in any unused byte. Authorization
Code format:
5 digit 6 digit 7 digit
Auth Code Auth Code Auth Code
Word 14, bits 8-11 Ai AUTH 1 AUTH I
AUTH 1
Word 14) bits 12-IS A2 AUTH2 AUTH2
AUTH2
Word 15) bits 0-3 A3 AUTH3 AUTH3AUTH3
Word 15, bits 4-7 A4 AUTH4 AUTH4AUTH4
Word 15) bits 8-11 AS AUTHS AUTHSAUTHS
Word 15, bits 12-15 A6 SEC1 AUTH6AUTH6
Word 16, bits 0-3 A7 SEC2 SECI AUTH7
Word 16) bits 4-7 A8 SEC3 SEC2 SECT
Word 16) bits 8-11 A9 SEC4 SEC3 SEC2
Word 16) bits 12-15 A10 TBCD-NullSEC3
SEC4
Word 17, bits 0-3 A11 SUPP1 TBCD-NullSEC4
Word 17, bits 4-7 A12 SUPP2 SUPP1TBCD-Null
Word 17) bits 8-11 A13 SUPP3 SUPP1
SUPP2
Word 17) bits 12-15 A14 SUPP4 SUPP2
SUPP3
Word 18) bits 0-3 A15 SUPPS SUPP4SUPP3
Word 18) bits 4-7 A16 SUPP6 SUPPSSUPP4
Word 18) bits 8-11 A17 SUPP7 SUPPS
SUPP6
Word 18, bits 12-15 A18 SUPP8 SUPP6
SUPP7
Word 19, bits 0-3 A 19 SUPP9 SUPP7
SUPP8
Word 19, bits 4-7 A20 SUPP10 SUPP8
SUPP9
Word 19, bits 8-11 A21 SUPP11 SUPP9
SUPP10
Word 19, bits 12-15 A22 SUPP12 SUPP10
SUPP11
542
SUBSTfTUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
wo 9sn3o8o rcrnrs9~rnit>«4
Word ~, Bit ~ Description
2. Calling Station ID (CSI) - Contains the digits of the calling
station identifier. The CSI digits will be recorded starting at Al. A
TBCD-Null is recorded after the last CSI digit, followed by
Supplemental Code digits. Unused bytes contain a TBCD-Null.
Calling Station ID format:
7 digit 10 digit
CSI ~Sl
Word 14) bits Al X X
8-1 I
Word 14, bits A2 X X
12-IS
Word 15) bits A3 X X
0-3
Word 15) bits A4 X X
4-7
Word 15, bits AS X X
8-11
Word 15, bits A6 X X
12-IS
Word 16, bits A7 X X
0-3
Word 16) bits A8 TBCD-Null X
4-7
Word 16) bits A9 SUPPI X
8-11
Word 16) bits A10 SUPP2 X
12-15
Word 17, bits A11 SUPP3 TBCD-Null
0-3
Word I7, bits A12 SUPP4 SUPP1
4-7
Word 17) bits A13 SUPPS SUPP2
8-11
Word 17, bits A14 SUPP6 SUPP3
12-15
Word 18, bits A15 SUPP7 SUPP4
0-3
Word 18) bits A16 SUPP8 SUPPS
4-7
Word 18, bits A17 SUPP9 SUPP6
8-11
Word 18, bits AI8 SUPP10 SUPP7
12-IS
Word I9, bits A19 SUPP11 SUPP8
0-3
Word 19, bits A20 SUPP12 SUPP9
4-7
Word 19, bits A21 SUPP13 SUPP10
8-11
Word 19, bits A22 SUPP14 SUPPI
12-IS l
543
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PGT/ITS97/21174 -
Word A~) Bit fl Description
3. Supplementary
Codes - Supplemental
Codes are
recorded
starting in contain TBCD-Null. Supplementary
A1. Unused
bytes
Code format:
800/900 VNet
Supp. Codes
Word 14, bitsA1 SUPP1
8-11
Word 14) bitsA2 SUPP2
12-15
Word 15) bitsA3 SUPP3
0-3
Word 15) bitsA4 SUPP4
4-7
Word 15, bitsAS SUPPS
8-11
Word 15) bitsA6 SUPP6
12-15
Word 16, bitsA7 SUPP7
0-3
Word 16, bitsA8 SUPP8
4-7
Word 16, bitsA9 SUPP9
8-I1
Word 16, bitsA10 SUPP10
12-15
Word 17, bitsA11 SUPPI 1
0-3
Word 17, bitsA12 SUPPI2
4-7
Word 17, bitsA13 SUPP13
8-11
Word 17) bitsA14 SUPP14
12-15
Word 18) bitsA15 SUPP15
0-3
Word 18) bitsA16 SUPP16
4-7
Word 18) bitsA17 SUPP17
8-11
Word 18, bitsA18 SUPP18
12-15
Word 19, bitsA19 SUPP19
0-3
Word 19, bitsA20 SUPP20
4-7
Word 19, bitsA21 SUPP21
8-11
Word l9, bitsA22 SUPP22
12-15
544
SU9STlTUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
wo 9sr~o pcr~rs9~nm~4
Word A~. Bit ~ Description
4. VNet Remote the caller accesses
Access - VNet services
If
through the
Remote Access
Service)
the access
number is
recorded starting
at A1. A
TBCD-Null
is recorded
after the
last
digit followed
by any Supplemental
Codes. Unused
bytes contain
TBCD-Null.
VNet Remote
Access format:
Word 14) bitsA N
8-11 1
Word 14, bitsA2 X
12-15
Word 15) bitsA3 X
0-3
Word 15) bitsA4 N
4-?
Word 15) bitsAS X
8-11
Word 15, bitsA6 X
12-15
Word 16) bitsA7 X
0-3
Word 16) bitsA8 X
4-7
Word 16, bitsA9 X
8-11
Word 16, bitsA10 X
12-15
Word 17) bitsA TBCD-Null
0-3 11
Word 17) bitsA12 SUPP1
4-7
Word 17, bitsA13 SUPP2
8-11
Word 17, bitsA14 SUPP3
12-15
Word 18) bitsA15 SUPP4
0-3
Word 18, bitsA SUPPS
4-7 16
Word 18, bitsAI7 SUPP6
8-11
Word 18) bitsA18 SUPP7
12-15
Word 19, bitsA19 SUPP8
0-3
Word 19) bitsA20 SUPP9
4-7
Word 19) bitsA21 SUPPIO
8-I 1
Word 19, bitsA22 SUPPI1
12-15
545
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98123080 PGT/US97/21174
Word ~I) Bit A~ Il~scription
5. Calling
Party Number
- The calling
parry number
is recorded
for SS7 FGD received with a charge
call originations number and
a calling
party number.
Record the
SS7 coiling
party number
in
A1-10. A TBCD-Null
is
recorded
after
the
last
digit)
followed
by
supplementaryUnusedbytes contain TBCD-Null.
codes. Calling
parry number
format:
Word 14, bitsAl N
8-ll
Word 14, bitsA2 X
12-15
I Word 15, bitsA3 X
0-3
Word 15, bitsA4 N.
4-7
Word 15, bitsAS X
8-11
Word 15, bitsA6 X
12-15
Word 16) bitsA7 X
0-3
Word 16) bitsA8 X
4-7
- Word 16, bitsA9 X
8-11 .
Word 16, bitsA10 X
12-15
Word 17, bitsA11 TBCD-Null
0-3
Word 17, bitsA12 SUPP1
4-7
Word 17, bitsA13 SUPP2
8-11
Word 17, bitsA14 SUPP3
12-15
Word 18) bitsA15 SUPP4
0-3
Word 18, bitsA16 SUPPS
4-7
Word 18, bitsA17 SUPP6
8-11
Word 18) bitsA18 SUPP7
12-15
Word 19, bitsA19 SUPP8
0-3
Word 19, bitsA,20 SUPP9
4-7
Word 19, bitsA21 SUPP10
8-11
Word 19, bitsA22 SUPPI l
12-15
546
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PCT/LTS97/21174
Word ry, Bit A~ Description
6. Credit Card Number - Record the cotamercial
credit card or
presubscribed credit card number starting
in A1. The PIN digits
of a valid presubscribed credit card number
are masked out by
writing TBCD-A over the 4 PIN digits.
A TBCD-Null is recorded
after the last digit, followed by supplementary
codes. Unused
bytes contain TBCD-Null. Credit card number
format:
Word 14, bits 8-11 A 1 X
Word 14, bits 12-IS A2 X
Word 15, bits 0-3 A3 X
Word 15, bits 4-7 A4 X
Word 15) bits 8-11 A5 X
Word 15) bits 12-15 A6 X
Word 16, bits 0-3 A7 X
Word 16, bits 4-7 A8 X
Word 16) bits 8-11 A9 X
Word 16) bits 12-15 A10 X
Word 17, bits 0-3 A11 X
Word 17, bits 4-7 A 12 X
Word 17) bits 8-11 AI3 X
Word 17, bits I2-15 A 14 X
Word 18) bits 0-3 A 15 X
Word 1 S, bits 4-7 A l6 X
Word 18, bits 8-I1 A17 X
Word 18, bits 12-15 A18 X
Word 19, bits 0-3 A19 X
Word 19) bits 4-7 A20 TBCD-Null
Word 19, bits 8-11 A21 SUPP1
Word 19) bits 12-15 A22 SUPP2
547
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97I21174
Word II, Blt !I Description
7. 14 Digit et - The 14 digit calling
MCI/VN Cardscard/VNet
card number
is recorded
starting
in A1 with
the last
4 PIN digits
masked out
by writing
TBCD-A for
those digits.
A TBCD-Null
is
written afterdigit,llowed by supplemental
the last fo codes.
Unused bytes
contain TBCD-Null.
Calling card/VNet
card format:
Word 14) bitsA1 X
8-I 1
Word l4) bitsA2 X
12-15
Word 15, bitsA3 X
0-3
Word 15) bitsA4 X
4-7
Word 15, bitsAS X
8-11
Word 15, bitsA6 X
12-15
Word 16) bitsA7 X
0-3
Word 16, bitsA8 X
4-7
Word 16, bitsA9 X
8-11
Word 16) bitsA10 X
12-15
Word 17, bitsA11 TBCD-A
0-3
Word 17, bitsA12 TBCD-A
4-7
Word 17) bitsA13 TBCD-A
8-11
Word 17, bitsA14 TBCD-A
12-15
Word 18) bitsA15 TBCD-Nuil
0-3
Word 18) bitsA16 SUPPl
4-7
Word 18, bitsA17 SUPP2
8-11
Word 18) bitsA18 SUPP3
12-15
Word 19, bitsA SUPP4
0-3 19
Word 19, bitsA20 SUPPS
4-7
Word 19, bitsA21 SUPP6
8-11
Word 19, bitsA22 SUPP7
12-IS
548
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
d PCT/US97/211~4
Word 1Y) Bit A~ Description
8. Telecotnmunications/1'TT
Cards - The
23 digits)
or less,
of the
telecommunications
card is recorded
starting
in A 1. A
TBCD-Null
is recorded last , followed by supplemental
after the digitcodes.
Unused bytes
contain TBCD-Null.
Telecommunications
card
format:
Word 14) bitsA1 X
8-11
Word 14, bitsA2 X
12-IS
Word 15, bitsA3 X
U-3
Word 15, bitsA4 X
4-?
Word 15, bitsAS X
8-11
Word 15, bitsA6 X
12-15
Word I6) bitsA7 X
0-3
Word 16) bitsA8 X
4-?
Word 16, bitsA9 X
8-11
Word 16, bitsA10 X
12-15
Word 17, bitsAi X
0-3 l
Word 17) bitsA12 X
4-7
Word 17) bitsA13 X
8-I i
Word I?, bitsA14 X
12-15
Word 18, bitsAIS X
0-3
Word 18, bitsA16 X
4-?
Word 18, bitsA17 X
8-I1
Word 18) bitsAIS X
12-15
Word 19, bitsA19 X
0-3
I Word 19, bitsA20 X
4-7
Word 19) bitsA21 X
8-11
Word 19) bitsA22 X
12-15
54Q
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97IZ1174
Word If, Blt tl Description
9. OSID and For
OTG - international
inbound
VNet
or
SAC
calls;
the OSID and
OTG are recorded
as received
from the
SS7
Generic Digits
parameter.
After the
parameters
are recorded,
the
remaining D-Null. OSID and OTG
bytes contain format:
TBC
Word 14, bitsA1 X (OSID)
8-11
Word 14, bitsA2 X (OSID)
12-15
Word 15, bitsA3 X (OSID)
0-3
Word 15, bitsA4 X (OTG)
4-7
Word 15, bitsAS X (OTG)
8-11
Word 15, bitsA6 X (OTG)
12-15
Word 16, bitsA7 X (OTG)
0-3
Word 16) bitsA8 TBCD-Null
4-7
Word 16, bitsA9 TBCD-Null
8-11
Word 16) bitsA10 TBCD-Null
12-15
Word 17) bitsA11 TBCD-Null -
0-3
Word 17) bitsA TBCD-Null
4-7 12
Word 17, bitsA13 TBCD-Null
8-11
Word 17, bitsA14 TBCD-Null
12-15
Word 18, bitsA TBCD-Null
0-3 15
Word 18, bitsA16 TBCD-Null
4-7
Word 18) bitsA17 TBCD-Null
8-11
Word 18, bitsA18 TBCD-Null
12-15
Word 19, bitsA19 TBCD-Null
0-3
Word 19, bitsA20 TBCD-Null
4-7
Word 19) bitsA21 TBCD-Null
8-11
i
Word 19, bitsA22 TBCD-Null
12-15
I OSID = OriginatingSwitch
Group
(000-999)
OTG = Originating
Trunk Group
(0000-8191)
550
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PCT/IIS97I21174
Word II, Bit ~ Description
10. Business
Group 1D
- For some
SS7 trunk
groups) a
business
group ID is in SS7 parameter and is recorded
roceived a in A1-
A6. After TBCD-Nuil is recorded
the last followed by any
digit, a
supplemental Unused
codes. bytes
contain
TBCD-Null.
Word 14, bitsA1 X
8-I1
Word 14, bitsA2 X
12-15
Word 15) bitsA3 X
0-3
Word 15, bitsA4 X
4-7
Word 15) bitsAS X
8-11
Word 15) bitsA6 X
12-15
Word 16, bitsA7 TBCD-Null
0-3
Word 16) bitsA8 SUPPI
4-7
Word 16) bitsA9 SUPP2
8-11
Word 16, bitsA10SUPP3
12-15
Word 17, bitsAl SUPP4
0-3 l
Word 17, bitsA SUPPS
4-7 I2
Word 17, bitsA13SUPP6
8-11
Word 17) bitsA14SUPP7
12-15
Word 18, bitsA15SUPP8
0-3
Word 18, bitsA16SUPP9
4-7
Word 18, bitsA17SUPPIO
8-11
Word 18) bitsA18SUPPI1
12-15
Word 19) bitsA19SUPP12
0-3
Word 19, bitsA20SUPPI3
4-7
Word 19, bitsA21SUPP14
8-11
Word 19, bitsA22SUPP15
12-15
11. Network For some SS7 trunk groups,
information a network
-
information in a SS7 parameter and
ID is received is recorded in
AI-A4. After digit) a TBCD-Nuli is recorded
the last followed by
any supplemental nused bytes contain TBCD-Null.
codes. U
Word 14) bitsA1 N
8-11
Word 14, bitsA2 X _
12-15
Word 15) bitsA3 X
0-3
Word 15) bitsA4 N
4-7
Word I5) bitsAS TBCD-Null
8-11
Word I5) bitsA6 SUPP1
12-15
Word 16) bitsA7 SUPP2
0-3
Word 16, bitsA8 SUPP3
4-7
Word 16) bitsA9 SUPP4
8-I1
Word 16, bitsA10SUPPS
I2-15
Word 17) bitsAl SUPP6
0-3 l
Word 17, bitsA SUPP7
4-7 12
Word 17, bitsA13SUPP8
8-11
Word I7) bitsA14SUPP9
12-15
Word 18) bitsA15SUPP10
0-3
Word 18, bitsA16SUPP11
4-7
Word 18, bitsA17SUPPI2
8-11
Wocd 18, bitsA18SUPP13
12-15
Word 19, bitsA19SUPP14
0-3
Word 19) bitsA20SUPP15
4-7
Word 19) bitsA21SUPP16
8-11
Word 19, bitsA22SUPP17
12-15
551
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PGT/US97121174
Word 11, Bit A~ Description
12. BOC Card:
The BOC/LEC
Card Number
is recorded
in A1-
A10 with the
remaining
bytes containing
TBCD-Null.
Word 14, bitsA1 N
8-11
Word 14, bitsA2 X
12-15
Word 15, bitsA3 X
0-3
Word 15, bitsA4 N
4-7
Word 15, bitsAS X
8-11
Word 15) bitsA6 X
12-15
Word 16) bitsA7 X
0-3
Word 16) bitsA8 X
4-7
Word 16) bitsA9 X
8-1 I
Word 16, bitsA10 X
12-IS
Word 17) bitsA11 TBCD-Null
0-3
Word 17) bitsA12 TBCD-Null
4-7
Word 17) bitsA13 TBCD-Null
8-11
Word 17) bitsA14 TBCD-Null
12-15
Word 18) bitsA15 TBCD-Null
0-3
Word 18, bitsA16 TBCD-Null
4-7
Word 18, bitsA17 TBCD-Null
8-11~
Word 18, bitsA18 TBCD-Null
12-15
Word 19) bitsA19 TBCD-Null
0-3
Word 19, bitsA20 TBCD-Null
4-7
Word 19, bitsA21 TBCD-Null
8-11
Word 19) bitsA22 TBCD-Null
12-15
13. Third a call is billed to
Parry Numbers: a third parry NANP
If
number, record
the number
in AI-A10
with the
remaining
bytes
containing
TBCD-Null.
Word 14, bitsA1 N
8-11
Word 14, bitsA2 X
l2-15
Word l5) bitsA3 X
0-3
Word 15, bitsA4 N
4-7
Word 15, bitsAS X
8-11
Word 15, bitsA6 X
12-15
Word 16, bitsA7 X
0-3
Word 16) bitsA8 X
4-7
Word 16) bitsA9 X
8-11
Word 16, bitsA10 X
12-15
Word 17) bitsAl TBCD-Null
0-3 l
Word 17) bitsA12 TBCD-Nuil
4-7
Word 17, bitsA13 TBCD-Null
8-11
Word 1T) bitsA14 TBCD-Null
12-15
Word 18, bitsA15 TBCD-Null
0-3
Word 18) bitsA16 TBCD-Null
4-7
Word 18) bitsA17 TBCD-Null
8-11
Word 18, bitsA TBCD-Null
12-15 18
Word 19) bitsA TBCD-Null
0-3 19
Word 19, bitsA20 TBCD-Null
4-7
Word 19, bitsA21 TBCD-Null
8-11
Word 19, bitsA22 TBCD-Null
12-15
552
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
PCT/US97n1174 -
_
Word ~J) BIt ~l Description
14. Imernational f a call is billed to
Numbers: an international
I
number, record
the starting
number in
A1. Unused
bytes contain
TBCD-Null.
Word 14, bitsA X (CC)
8-11 1
( Word 14, bitsA2 X (CC)
12-15
Word 15, bitsA3 X (CC)
0-3
Word 15, bitsA4 X (NN)
4-7
Word I5) bitsAS X (NN)
8-I1
' Word 15, bitsA6 X (NN)
12-i5
Word 16, bitsA7 X (NN)
0-3
Word 16) bitsA8 X (NN)
4-7
Word 16) bitsA9 X (NN)
8-11
WoM 16, bits A10 X (NN)
12-15
Word 17, bitsAl X (NN)
0-3 l
Word 17) bitsA12 X (NN)
4-7
Word 17, bitsA13 X (NN)
8-11
Word I7) bitsA14 X (NN)
12-15
Word 18) bitsA15 X (NN)
0-3
Word 18) bitsA16 TBCD-Null
4-7
Word 18, bitsA17 TBCD-Nult
8-I1
Word 18) bitsA18 TBCD-Nul!
12-15
Word I9, bitsA TBCD-Null
0-3 19
Word 19) bitsA20 TBCD-Null
4-7
Word 19, bitsA21 TBCD-Null
8-11
Word 19, bitsAZZ TBCD-Null
12-15
CC = Customer
Cotmect
NN = National
Number
553
SUBSTITUTE SHEET (RULE 28)
CA 02279845 1999-OS-17
WO 98/23080 - PCT/ITS97/21174
Word A~, Bit ~ Description ',
15. LAN Sequence : If a call is handled
Numbers by a LAN, and
billable information
cannot be
transported
back to the
billing
switch) then
the LAN records
all of the
billable
information
in a
Billing Detail and sends back a LAN
Record (BDR) sequence
number to
the switch.
The LAN sequence
number is
recorded
in
AI-A16 with
the remaining
bytes containing
TBCD-Null.
Word 14, bitsAI X
8-11
Word 14) bitsA2 X
12-15
Word 15, bitsA3 X
0-3
Word 15, bitsA4 X
4-7
Word 15) bitsAS X
8-11
Word 15, bitsA6 X
I2-15
Word 16) bitsA7 X
0-3
Word 16, bitsA8 X
4-7
Word 16) bitsA9 X
8-11
Word 16, bitsA10 X
12-15
Word 17) bitsA X
0-3 1
I
Word 17, bitsA12 X
4-7
Word I7) bitsA13 X
8-11
Word 1T, bitsA14 X
12-15
Word 18, bitsA15 X
0-3
Word 18, bitsA16 X
4-7
Word 18, bitsA TBCD-Null
8-11 17
Word 18) bitsA18 TBCD-Null
12-15
Word 19, bitsA TBCD-Null
0-3 19
Word 19) bitsA20 TBCD-Null
4-7
Word 19, bitsA21 TBCD-Null
8-11
Word 19) bitsA22 TBCD-Null
12-15
554
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
w0 98/23080 PCT/US97/21174
Word ll) Bit IJ Description
16. DNIS: The
DNIS may be
recorded as
received from
the SS7
generic address , such as with EVS/NARS
parameter processed
calls.
Word 14, bits N
8-11 A1
Word 14) bits X
12-15 A2
Word 15) bits X
0-3 A3
Word 15, bits N
4-7 A4
Word 15) bits X
8-I 1 AS
Word 15, bits X
12-15 A6
Word 16, bits X
0-3 A7
Word 16, bits X
4-7 A8
Word 16, bits X
8-11 A9
Word I6, bits X
12-15 A10
Word 17, bits TBCD-Null
0-3 A11
Word 17) bits TBCD-Null
4-7 A12
Word 17) bits TBCD-Nuil
8-11 AI3
Word 17, bits TBCD-Null
12-15 A14
Word 18, bits TBCD-Null
0-3 A15
Word 18, bits TBCD-Null
4-7 A16
Word 18, bits TBCD-Null
8-11 A17
Word 18) bits TBCD-Null -
12-15 A18
Word 19, bits TBCD-Null
0-3 A19
Word 19, bits TBCD-Null
4-7 A20
Word 19, bits TBCD-Null
8-11 A21
Word 19, bits TBCD-Null
12-15 A22
17. Network Call
Identifier (NCID):
If the NCID
is recorded
i
n
the "A" field,
it is recorded
in binary beginning
with A 1. The
entry code will call processing associated
indicate the with the
particular call
or '0.' If the
NCID is recorded
in the NCID
field
of a 64-wot~call
record, the
entry code will
also indicate
the call
processing associated
with the particular
call or '0.'
The NC1D
comprises the
following:
Originating Switch
ID
Originating Trunk
Group
Originating Port
Number
Timepoint I
NCID Sequence
Number
555
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 - PCT/US97/21174
Word !l, Bit J! Description
Word 20, bits 0-15 Destination This
Address: is
the
seventeen
digits
of
the
destination
Word 21, bits 0-15 address whichdomestic
is the or
international
number
being
Word 22) bits 0-IS called, or
an operator
number format.
In the POSR,
if the dialed
Word 23, bits 0-15 number was d
translate by
the
NCS/DAP
or
LAN)
the
translated
Word 24) bits 0-3 number will
be recorded.
If more than
17 digits
is required,
use
EOSR/EPOSR
format. Unused
bytes contain
TBCD-Null.
7-digit 10-digit DDD IDDD
Word 20, bitsD N N ~ N CC
0-3 1
Word 20) bitsD2 X X. X CC
4-7
Word 20, bitsD3 X X X CC
8-I1
Word 20, bitsD4 X N N NN
12-15
Word 21) bitsDS X X X NN
0-3
Word 21, bitsD6 X X X NN
4-7
Word 21, bitsD7 X X X NN
8-11
Word 21, bitsD8 X(TS1D) X X NN
12-15
Word 22, bitsD9 X(TSID) X X NN
0-3
Word 22) bitsD10X(TSID) X X NN
4-7
Word 22) bitsD11X('I"fG) X(TSID) T-Null
8-11 NN
Word 22, bitsD12X('ITG) X(TSID) T-Null
12-15 NN
Word 23, bitsD13X(TTG) X(TSID) T-Null
0-3 NN
Word 23) bitsD14X(TTG) X('T'TG) T-Null
4-7 NN
Word 23, bitsD15T-Null X('TTG) T-Null
8-11 NN
Word 23, bitsD16T-Null X(TTG) T-Null T-Null
12-15
Word 24) bitsD17T-Null X(TTG) T-Null T-Null
0-3
CC = Customer
Connect
NN = National
Number
TSID = TerminatingSwitch
ID
TTG = Terminating
Ttztnk Group
BOC Op-to-Op Op-to-Op
Inward Domestic/ Manual
Dialing Int'I Transit
Word 20, bitsD N X(CC) X(CC)
0-3 1
Word 20, bitsD2 O/I X(CC) X(CC)
4-7
Word 20, bitsD3 X X(CC) X(CC)
8-11
Word 20, bitsD4 X(ATC) TBCD-Null 1
12-15
- Word 21, bitsDS X(ATC) TBCD-Null b
0-3
Word 21, bitsDb X(ATC) TBCD-Null 0
4-7
Word 21, bitsD7 X(S11) TBCD-Null TBCD-Null
8-11
Word 21) bitsD8 X(S12) TBCD-Null TBCD-Null
12-15
Word 22, bitsD9 X(S13) TBCD-Null TBCD-Null
0-3
Word 22, bitsDIOX(S14) TBCD-Null TBCD-Null
4-7
I Word 22, bitsD11X(S15) TBCD-Null TBCD-Null
8-11
Word 22, bitsD12TBCD-Null TBCD-Null TBCD-Null
12-15
Word 23, bitsD13TBCD-Null TBCD-Null TBCD-Nuil
0-3
Word 23, bitsD14TBCD-Null THCD-Null TBCD-Null
4-7
Word 23) bitsD15TBCD-Null TBCD-Null TBCD-Null
8-11
Word 23, bitsD16TBCD-NuII TBCD-Null TBCD-Null
12-15
Word 24, bitsD17TBCD-Null TBCD-Null TBCD-Null
0-3
Word 24) bits 4-15 Operator ID (OPIN):
Nutaber Contains
the
operator
id
number
of
Word 25, bits 0-1 the operator
that handled
the call.
556
SU9ST1TUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
wo 9sn3oso pc~r~rs9~nm7a
Word A~, Bit ~Y Description
Word 25, bit 2 Not Used.
Word 25, bits 3-IS Timepoint 5 (TPS): A binary count of the
number of seconds
between the time TPi occurred and the
time that the operator
stopped handling the call and releases
the position. If the call is
transferred to other operators) the value
contained in this field
shall express the release time of the
last operator providing the
service.
Word 26) bits 0-15 Room Number (RN): Contains the last four
digits of the Callin
g
Station ID (CSI) when a call originates
from a hotel) a university,
or any other community identified by only
a main telephone
number. The CSI shall be obtained from
the originating signalling
information, or verbally by the operator
who enters the
information manually into the OSR.
Word 27, bits 0-3 Feature Code (FC): The switch determines
a feature code far the
call which indicates whether a specific
type of data line is required
for the call such as a higher quality
line for facsimile
transmissions.
0 = Default
1 = FAX
2 = NABS
3 = Data Call
4 = Switched DS1 (HSCS)
5 = Switched DS3 (HSCS)
6-8 = Not Used
9 = NXt54
10 = Offnet Routing
11 = AAP Call (Used in Gateway Toll Ticket
Conversion)
12 = Card Gate Denial
13 = Forum Dial out audio/video conference
14 = Concert Freephone
15 = Not Used
Word 27, bits 4-7 Terminating Network Code (TNC): Indicates
the terminating
facilities to be used for the remainder
of the path of the call. For
example, an indicator for no satellite
transmission.
0 = Default
1 = No Routing Restrictions
2 = Avoid Satellite
3 = Route via DS1
4 = Route via DS 1 and avoid satellite
_- 5 = Rotite via Protected Facilities Required
6 = Route via Protected Facilities Preferred
7-15 = Not Used
557
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
PGT/US97/2I174
Word, Blt ~I Description I
I
Word 27, bits 8-11 Network Access Type (NAT): Indicates
which type of network
access was used as defined at the originating
switch on the
network; that is, how the caller gained
access to the network. The
types of access are:
0 = Default
1 = 800 call
2 = Credit Card Access
3 = Operator Assistance Access
4 = VNET Remote Access
5 = Billed party preference (BPP) Access
6 = FGD Cut-Through Access
7-15 = Not Used
Word 27) bits 12-15 Timepoint 7 Qualifier (TP7Q): Contains
the call's first disconnect
qualifier; that is) how the call was
terminated. The types of
disconnection are:
0 = Calling party disconnects
1 = Called party disconnects
2 = Calling parry reorigination
3 = Switch initiated (ex. switch error
cut off the call)
4 = All Routes Busy
5 = Disconnected due to a long ring;
ring timer exceeded
6-15 = Not Used
Word 28) bits 0-6 Entry Code (EC): Indicates the type of
call processing that took
place and what type of infot~ttation
is recorded in the
Authorization Code field. If more than
one entry code is received,
record the last one. The following codes
are valid:
558
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO ~ PCT/US97/21174
Ili Word b, Bit ~ ~ Description
0 = Default
1 = Person-to-Person (P-P)
2 = Station-to-Station (S-S)
3 = Third Party Billing (3rd party number recorded)
4 = P-P collect (bill to called party)
= S-S collect (bill to caked parry)
6 = MCI card or VNet card (S-S)
7 = BOC inward dialing without call completiotl
8 = general assistance
9 = BOC/LEC card
= Presubscribed credit card
i l = PTT card
12 = Directory Assistance
13 = Commercial Credit Card
14 = BOC inward dialing with call completion
= MCI card or VNet card (P-P)
16-19 = Not Uscd -
= ANI.validation (screened pass/fail)
21 = Auth Validation (filed or dialed)
22 = Not Used
23 = 700 Service Access Code (overrides A~20)
24 = 500, 800 Service Access Code (overrides x20)
= 900 Service Access Code (overrides X20)
26-28 = Not Used
29 = Operator Release Timer Expired
= EVS/NARS - Disconnect message referral (DMR) without
referral
31 = EVS/NARS - DMR with referral to MCI number
32 = EVS/NARS - DMR with referral to non-MCI number
33 = EVS/NARS - DMR with refemat and call extension (CE) to
MCI number
34 = EVS/NARS - DMR with referral and CE to non-MCI
number
--- EVS/NARS - Custotniud Message Announcement (CMA)
with CE
559
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PCTiUS97/21174
Word ~) Bit A~ Description
36 = EVS/NARS - CMA without CE
37 = EVS/NARS - Enhanced Call Routing
(ECR)
38-41 = EVS/NARS - Reserved
42-47 = Not Used
48 = GETS card
49 = Not Used
50 = Billed to international number
51 = Calling station ID information recorded
52 = Supplemental code only recorded
53 = VNet remote access number recorded
54 = SS7 calling parry number recorded
55 = OSID and OTG recorded
56 = DNIS recorded
57 = Business group ID recorded
58 = Network information recorded
59 = BG + Nuli + OSID/OTG
60 = Card Number + Null + OSID/OTG
61 = VNet RA + Null + OSID/OTG
62 = VNet RA + Null + OSID/OTG
63 = Network Call Transfer (NCT)
64-79 = Reserved
80-89 = Reserved
90-99 = Reserved
100 = 18C lt's Me PIN S/S
101 = i8C It's Me Global S/S
102 = 18C It's Me ANI S/S
103 = 18C It's Me NPA S/S
104 = 18C Messenger SlS
105 = 18C Messenger PIN SIS
106 = 18C Messenger Global S/S
107 = 18C BOC Card SIS
108 = 18C MCI Card S/S
109 = Aos Messenger S/S
I 10 = International Messenger
I 11 = International Speed Dial
l I2-127 = Not Used
Word 28, bits 7-9 Prefix Digits (PD): Represents the prefix
digits of the called
number. These digits tell the switch how
to process the call.
0 = No prefix digits received
1 = 0- (operator assisted)
2 = 0+ (domestic CDOS)
3 = Ol + (international CDOS)
4 = OZ 1 +IDDD
5 = 1 +DDD
6 = 0+operator assisted, subscriber address
7 = *XX where XX = 0-9, Star Card
560
SUBSTITUTE SHEET {RULE 26)
CA 02279845 1999-OS-17
WO PCT/US97/21174
Word N) Bit /! .- Description
Word 28, bits 10-12 NDID (NCS/DAP ID): Indicates whether
the switch processed the
call or if one of the databases) such
as NCS/DAP, was queried for
information for services, including but
not limited to) VNET,
Calling Card, $00) and 900 calls. The
NDID further indicates the
ID of the NCS/DAP that was involved in
the last transaction
attempt.
0 = Switch call processing
1 = NCS/DAP 1
2 = NCSIDAP 2
3 = NCS/DAP 3
4-5 = Not Used
6 = Received from operator platform via
RLT
7 = TCAP to NCS/DAP
Word 28, bits 13-15 Division ID (DIVID): Contains the division
ID for credit card
calls, including the telecommunication
system's card. The DIVID
is received from the NCS/DAP for the
card number validation. If
no information is received by the switch)
record the default value
of '0.'
0 = No division ID specified
1 = Division ID1
2 = Division ID2
3 = Division 1D3
4 = Division ID4
5 = Division IDS
6 = Division ID6
7 = Division ID'7 ---
Word 29, bit 0 Distant Overtiow (DO): When set to 1
in the originating switch's
call trcord) indicates that a direct
termination overflow (DTO)
transaction was attempted at an intermediate
or terminating switch
in order to get the f nat destination
address digits for this call.
Word 29) bit 1 Not Used.
Word 29) bit 2 Customer Cortrtect (CC): Indicates whether
to use timepoint 6 or
timepoint 3 to calculate the call duration.
0 = Use Time Point 6) *F to calculate
the call duration
1 = Use Time Point 3) *C to calculate
the call duration
Word 29, bit 3 Inter-Network (IN): Indicates whether
or not a call is o
i
i
i
r
g
nat
ng
from one customer/network and is terminating
to a different
customer/network. The default setting
= 0; bit set to l if a
business group or Netinfo parameter is
received from the
NCS/DAP.
Word 29, bit 4 Not Used
' Word 29, bit 5 SAC Bit (SC): This bit is used for the
Flexible SAC feature. This
bit will be sec to " 1 " whenever the
received number which i
s
collected during the address digit collection
phase) is identified as
a SAC number in the FlezSac Index associated
with the
originating trunk group. This bit will
._ be set to "0" in all other
~.
551
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98123080 PCT/US97I21174
Word A~) Bit A~ Description
Word 29, bit 6 Call Direction (CD): Indicates whether
the call originated in the -
domestic or international network.
0 = Call origination occurred in the
Domestic Network
I = Call origination occurred in the
International Network
Word 29, bit 7 Destination (DE): Indicates when a call
is expected to terminate to
an international destination.
0 = Default, NANP) Domestic VNet) or
any ocher calls which
are not expected to tertttinate to an
international destination
1 = Calls expected to terminate to an
international destination
Word 29, bit 8 Dedicated Termination (DT): Indicates
that a 10-digit shared
network number was completed to a dedicated
destination. If the
terminating trunk class (TTC) in the
call record is equai
to 3 or 7)
_
then it is considered to be a direct
termination trunk.
Word 29) bit 9 Person-to-Person (PP): This bit is set
to 1 if the operator
authorizes a person-to-person call. This
bit is used in combination
with the entry codes to determine the
nature of the call.
Word 29, bit 10 Transferred Bit (XB): This bit is set
to 1 if the call has been
transferred from one operator position
or ARU to another.
Word 29, bit 11 Satellite (SA): Indicates that a satellite
circuit was involved in the
call. The default setting is 0; hit set
to 1 indicates that a satellite
was involved in the call. The bit is
set when the incoming trunk
group is classmarked as satellite equipped)
when the SAT digit on
an incoming inband IMT call shows that
a satellite circuit is
involved in the connection) or when the
SS7 Nature of Connection
parameter indicates that a satellite
trunk was previously used. This
is used for trouble-shooting purposes,
and not for billing.
j Word 29, bits 12-15 Nature Of Calling Location ID (NOCLI):
A binary value that
i dentifies what data is recorded in the
Call Location ID. The
Calling Location ID field will contain
the information that is
referenced in the NOCLI.
0 = Not Used
1 = ANI from Inbound trunk
2 = SS7 charge number
3 = SS7 calling parry number
4 = original called number
5 = Pseudo ANI created at this switch
6 = CSI from originating trunk
7 = Filed NPA-NXX trunk group information
plus CSI
8 = NNN+OSID+OTG or OOY+OSID+OTG (N =
TBCD-
Null)
9 = Country Code + national number
10 = No CLI record
11 = Redirecting Number
12 = CLI received from Operator platform
via RLT
13 = ANI of NCT Originator
14-15 = Not Used
562
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
PCT/US97/21I74
Word lt, Bit A~ Description
i
-
Word 30) bits 0-IS Carrier Number (CN): Represents the carrier
number provided on
FG-B or FG-D originations, or the carrier
number received over
an SS7 IMT. If only three digits are used)
then they are recorded
in CN2-CN4 and CN 1 will contain a TBCD-Null.
This field also
contains the last four digits of the specific
800 number assigned to
VISA cards (9595). It will also contain
the last four digits of the
MCI card access number regardless of the
access facility.
Examples of carrier numbers are: MCI =
222, ATT = 288, and
Friends = 333.
FGB/FGD FGB/D
3 digit 4 digit visa
CIC CIC card
Word 30, bits 0-3 CNI Null X 9
Word 30, bits 4-7 CN2 X X S
Word 30, bits 8-1 I CN3 X X 9
Word 30, bits 12-15 CN4 X X S
SS7 MCI VNet
TNS card card
Word 30, bits 0-3 CN 1 X I 1
Word 30, bits 4-7 CN2 X 0 1
Word 30, bits 8-11 CN3 X 2 1
Word 30) bits 12-15 CN4 X 2 1
Word Authorization Code ID Field (ACIF): Contains
31, the Authori
bits i
0-3
zat
on
Code Identification Field for recording
a card number status. This
field indicates whether the card number
(calling card or credit
card) is good or bad.
0 = Seven digit authcode file
1 = 1st or only five digit authcode file
2 = 2nd five digit file
3 = 3rd five digit file
4 = 4th five digit file
S = Sth five digit file
6 = Six digit authcode file
7 = Range restriction failure (invalid
address digits)
8 = Positive Commercial Credit Cardl89
Card/M Card Validation
9 = Not Used
10 = MCI CardlVisa Card invalid or not
assigned. Disallowed
.
11 = BOC billing number assigned but blocked
12 = BOC billing number usage exceeded
13 = Not Used
I4 = Default authorization of MCI Card/VISA
Card if response
timeout from NCS/DAP
1S = MCI Card/VISA Card authorized by NCSIDAP
563
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PCT/ITS97/21174
Word #, Bit # Description
Word 31, bits 4-10 Release Code: Used with timepoint 7 qualifier
to determine from
which direction the release message came.
The code indicates why
one of the parties hung up) for example,
normal release = 16,
and no circuit available = 34.
1 = Unallocated number
2 = No route to specified network
3 = No route to destination
4 = Send special information tone
5 = Misdialed trunk prefix
16 = Normal clearing
17 = User Busy
18 = No user responding
19 = No user responding (user alerted)
21 = Call rejected
22 = Number changed
27 = Destination out of service
28 = Address incomplete
29 = Facility rejected
31 = Normal - unspecified
34 = No circuit available
38 = Network out of order
41 = Temporary failure
42 = Switching equipment congestion
44 = Requested channel not available
47 = Resource unavailable - mtspecified
i 50 = Requested facility not subscribed
55 = Incoming calls barred within CUG
57 = Bearer capability not authorized
58 = Bearer capability not available
63 = Service or option not available
65 = Bearer capability not implemented
69 = Requested facility not implemented
70 = Only restricted digital information
bearer capability is
available
79 = Service or option not implemented
87 = Called user not member of CUG
88 = Incompatible destination
91 = Invalid transit network selector
' 95 = Invalid message - unspecified i
97 = Message type non-existent or not
implemented '
99 = Parameter non-existent or not implemented
- discarded
102 = Recovery on timer expired
103 = Parameter non-existent or not implemented
- passed on
I 11 = Protocol error - unspecified
127 = Interworking - unspecified
Word 31, bits 11-13 NCID Sequence Number: Represents the
number of calls which
have occurred on the same port number
with the same Timepoint
1 value. The first call will have the
sequence number set to '0'.
This value will increase incrementally
for each successive call
which originates on the same port number
which has the same
Timepoint 1 value. Range = 0-7.
564
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
PCT/US97/21174
Word ~, Bit ~Y Description
Word 31 ( bit l4 NCID Location (NCIDLOC): This bit identifies
when the NCID i
s
recorded in the Authcode field of the
call record. The NCID is
recorded in the Authcode field of the
call record at intermediate
and terminating switches if the Authcode
field is not being used to
record other information. If the Authcode
field is being used to
record other information, the NCID is
recorded in the "NCID"
field of the 64 word call record.
0 = NCID is not recorded in the Authcode
field (default)
1 = NC1D is recorded in the Authcode field
Word 31, bit 15 Remote AN1 Screened (RS): This bit is
set to '1' if the NPA of
the ANl is not listed in the switch's
Local-Service-Area table. and
the ANI was sent to the DAP for ANl index
screening purposes.
This bit is set to '0' if the switch sent
the ANI to the DAP for
ANI index screening purposes and no response
is received from
the DAP or if normal switch ANI screening
occurs.
0 = ANI was not screened by the DAP (default)
1 = ANI was screened by the DAP
Words 0-11) bits Same as OSR/POSR format.
0-15
Word 12) bits 0-15 Calling Location ID: Contains 1-IS digits
of the originatin
station
Word 13, bits 0-IS g
line. This is the ANI number of the calling
party
If 1 to 15 ANI
Word 14, bits 0-15 .
or CSI digits are received, they are recorded
in order starting with
Word 15, bits 0-11 CLII. Unused bytes contain TBCD-Null.
If no ANI or CSI is
available, record the OSID/OTG in CL14-10)
except where noted.
If nothing is recorded in the CLI field)
use a NOCLI value of Z0.
This field contains 1 of the following
nine formats:
1. VNet CAMA DAL originations: If CSI
is available, prefix the
CSI with filed HNPA and HNXX information)
if available) and
record. Use NOCLI value of 7.
2. FG-C Originations: If ANI or CSI information
is not available
and the numbtr is in the 00Y+NXX-XXXX
format) record the
OOY code that was received in CLI1-3,
and record the OSID/OTG
in CLI4-10. Use NOCLI value of 8.
3. Inband FG-D Originations: Record the
ANI that was received
- staring with CL1. Use NOCLI value of 1.
4. SS7 FG-D Originations: Record the charge
number) if
available. If the charge number is not
available, record the calling
parry number. Use NOCLI value of 2 or
3.
5. International Originations: Record
the country code and
national number of the calling patty.
Use NOCLI value of 9.
6: SS7 IMTs Originations: Record the following
information in
this order of importance: I) charge number)
2) calling parry
number, 3) OSID/OTG from generic digits.
Use NOCLI value of
2, 3, or 8.
7. SS7 Reseller Originations: The CLI
field will be filled with
TBCD Nulls.
565
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
Word U) Bit ~ Description , _,
8. SS7 Private Network Originations:
The CLI field will be filled
with TBCD Nulls.
9. PRI Originations: Record the calling
parry. number received in
the ISDN setup message.
The format:
I-LS digit
ANI/CSI
- (13 digit Incoming
example) OSmlOTG Int'1
Word 12, bits 0-3 CLI1 X TBCD-Null X(CC)
Word 12, bits 4-7 CLI2 X TBCD-Null X(CC)
Word 12, bits 8-11 CLI3 X TBCD-Null X(CC)
Word 12, bits 12-15 CLI4 X X(OSID) X(NN)
Word 13, bits 0-3 CLIS X X(OS1D) X(NN)
- Word 13, bits 4-7 CLI6 X X(OS1D) X(NN)
Word I3, bits 8-11 CLI7 X X(OTG) X(NN)
Word I3) bits 12-15 CLIB X X(OTG) X(NN)
Word 14, bits 0-3 CL19 X X(OTG) X(NN)
Word 14, bits 4-7 CLI10 X X(OTG) X(NN)
Word 14, bits 8-I1 CLII l X TBCD-Null
X(NN)
Word 14) bits 12-15 CLI12 X TBCD-Null
X(NN)
Word 15, bits 0-3 CLII3 X TBCD-Null X(NN)
Word 15, bits 4-7 CLI14 TBCD-Null TBCD-Null
X(NN)
Word 15) bits 8-11 CLI15 TBCD-NuH TBCD-Null
X(NN)
CC = Customer Connect
NN = National Number
OSID = Originating Switch ID
OTG = Originating Trunk Group
Word 15, bits 12-15 Authorization Code (Auth Code): Same
as OSR/POSR format
Word 16) bits 0-IS Auth Code) but represents 45 digits.
Word 17, bits 0-15 _
Word 18) bits 0-15 1. Authorization Codes:
Word 19, bits 0-15
Word 20, bits 0-l5 5 digit 6 digit 7 digit
Word 21) bits 0-IS
Word 22, bits 0-15 Word 15, bits 12-15 A 1 AUTH 1 AUTH 1
AUTH 1
Word 23, bits 0-IS Word 16, bits 0-3 A2 AUTH2 AUTH2 AUTH2
Word 24, bits 0-15 Word 16, bits 4-7 A3 AUTH3 AUTH3 AUTH3
Word 25, bits 0-15 Word 16, bits 8-11 A4 AUTH4 AUTH4 AUTH4
Word 26, bits 0-15 Word 16, bits I2-15 AS AUTHS AUTHS AUTHS
Word 17) bits 0-3 A6 SEC1 AUTH6 AUTH6
Word 17, bits 4-7 A7 SEC2 SEC1 AUTH7
Word 17, bits 8-11 A8 SEC3 SEC2 SECT
Word 17, bits 12-15 A9 SEC4 SEC3 SEC2
Word 18, bits 0-3 A10 T-Null SEC4 SEC3
Word 18) bits 4-7 A11 SUPP1 T-Null SEC4
Word 18, bits 8-11 A12 SUPP2 SUPP1 T-Null
Word 18, bits 12-15 A13 SUPP3 SUPP2 SUPP1
566
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/Z3080 PCT/US97/21174 -
Word fl, Bit tl Description
--
Word 19) bits SUPP4 SUPP3 SUPP2
0-3 A14
Word I9, bits SUPPS SUPP4 SUPP3
4-7 A15
Word 19, bits SUPP6 SUPPS SUPP4
8-i l AI6
Word 19, bits SUPP7 SUPP6 SUPPS
12-15 A17
Word 20, bits SUPP8 SUPP7 SUPP6
0-3 A18
Word 20, bits SUPP9 SUPP8 SUPP7
4-7 A19
Word 20) bits SUPPIOSUPP9, SUPP8
8-11 A20 ~
Word 20, bits SUPPI1SUPP10 SUPP9
12-15 A21
Word 21) bits SUPP12SUPP1! SUPP10
0-3 A22
Word 21) bits SUPP13SUPP12 SUPP11
4-7 A23
Word 21, bits SUPP14SUPP13 SUPP12
8-11 A24
Word 21) bits SUPP15SUPP14 SUPP13
12-IS A25
Word 22) bits SUPP16SUPP15 SUPP14
0-3 A26
Word 22, bits SUPP17SUPP16 SUPP15
4-7 A27
Word 22, bits SUPP18SUPP17 SUPP16
8-11 A28
Word 22; bits SUFP19SUPPI8 SUPPi7
I2-15 A29
Word 23) bits SUPP20SUPP19 SUPP18
0-3 A30
Word 23, bits SUPP21SUPP20 SUPP19
4-7 A31
Word 23, bits SUPP22SUPP21 SUPP20
8-11 A32
Word 23, bits SUPP23SUPP22 SUPP21
12-15 A33
Word 24) bits SUPP24SUPP23 SUPP22
0-3 A34
Word 24) bits SUPP25SUPP24 SUPP23
4-7 A35
Word 24) bits SUPP26SUPP25 SUPP24
8-11 A36
Word 24, bits SUPP27SUPP26 SUPP25
12-15 A37
Word 25, bits SUPP28SUPP27 SUPP26
0-3 A38
Word 25, bits SUPP29SUPP28 SUPP27
4-7 A39
Word 25) bits SUFP30SUPP29 SUPPZ8
8-I1 A40
Word 25, bits T-NullSUPP30 SUPP29
12-15 A41
Word 26, bits T-NullT-Null SUPP30
0-3 A42
Word 26, bits T-NuilT-Null T-Null
4-7 A43
Word 26, bits T-NullT-Null T-Null
8-11 A44
Word 26) bits T-NuilT-Null T-Null
12-15 A45
T-Null = TBCD-Null
2. Calling Station
ID (CSI):
7 digit!-10 digit
Word 15) bits X X
12-15 A1
Word 16) bits X X
0-3 A2
Word 16, bits X X
4-7 A3
Word 16, bits X X
8-11 A4
Word 16) bits X X
12-15 AS
Word 17, bits X X
0-3 ~ A6
Word 17, bits X X
4-7 A7
Word 17, bits TBCD-Null
8-11 A8 X
Word 17, bits SUPPI X
12-IS A9
Word 18, bits SUPP2 X
0-3 A10
Word 18, bits SUPP3 TBCD-Null
4-7 AI I
Word 18, bits SUPP4 SUPP1
8-11 A12
Word 18, bits SUPPS SUPP2
12-15 A13
567
SUBSTITUTE SHEET (RULE 25)
CA 02279845 1999-OS-17
WO 98/23080 - PCT/US97I21174
Word ~, Bit k Description
i
Word 19, bits SUPP6 SUPP3
0-3 A14
Word 19, bits SUPP7 SUPP4
4-7 A15
Word 19) bits SUPP8 SUPPS
8-11 A16
Word 19, bits SUPP9 SUPP6
12-15 A17
Word 20, bits SUPP10 SUPP7
0-3 A18
Word 20) bits SUPP11 SUPP8
4-7 A19
Word 20, bits SUPP12 SUPP9
8-11 A20
Word 20, bits SUPP13 SUPI'10
I2-15 A21
Word 21 ) bits SUPPI4 SUPPI l
0-3 A22
Word 21, bits SUPP15 SUPPI2
4-7 A23
Word 21) bits SUPP16 SUPP13
8-11 A24
Word 21) bits SUPP17 SUPP14
12-15 A25
Word 22) bits SUPP18 SUPPIS
0-3 A26
Word 22, bits SUPP19 SUPP16
4-7 A27
Word 22, bits SUPP20 SUPP17
8-11 A28
Word 22, bits SUPP21 SUPPI8
12-15 A29
Word 23, bits SUPP22 SUPP19
0-3 A30
Word 23, bits SUPP23 SUPP20
4-7 A31
Word 23) bits SUPP24 SUPP21
8-11 A32
Word 23) bits SUPP25 SUPP22
12-IS A33
Word 24, bits SUPP26 SUPP23
0-3 A34
Word 24, bits SUPP27 SUPP24
4-7 A35
Word 24) bits SUPP28 SUPP25
8-11 A36
Word 24, bits SUPP29 SUPP26
12-15 A37
Word 25) bits SUPP30 SUPP27
0-3 A38
Word 25) bits TBCD-NullSUPP28
4-7 A39
Word 25, bits TBCD-NullSUPP29
8-11 A40
Word 25, bits TBCD-NullSUPP30
12-15 A41
Word 26) bits TBCD-NullTBCD-Null
0-3 A42
Word 26) bits TBCD-NutlTBCD-Null
4-7 A43
Word 26) bits TBCD-NullTBCD-Null
8-11 A44
Word 26, bits TBCD-Null
I2-15 A45 TBCD-NuII
3. Supplemental
Codes:
Word 15) bits SUPP1
12-15 A1
Word 16, bits SUPP2
0-3 A2
Word 16) bits SUPP3
4-7 . A3
Word 16, bits SUPP4
8-1 I A4
Word 16) bits SUPPS
IZ-15 AS
- Word 17, bits SUPP6
0-3 A6
Word 17, bits SUPP7
4-7 A7
Word 17, bits SUPP8
8-11 A8
Word 17, bits SUPP9
12-15 A9
Word 18, bits SUPP10
0-3 A10
Word 18) bits SUPPl
4=7 A11 l
Word 18, bits SUPP12
8-i l A 12
Word 18, bits SUPP13
12-IS A13
568
SUBSTITUTE SHEET (RULE 2B)
CA 02279845 1999-OS-17
PCT/US97121174
Word A~, Bit ~ Description
Word 19) bits SUPP14
0-3 A14
Word 19) bits SUPP15
4-7 A15
Word 19) bits SUPP16
8-11 A16
Word 19) bits SUPP17
12-15 A17
Word 20, bits SUPP18
0-3 A18
Word 20) bits SUPP19
4-7 A19
Word 20) bits SUPP20
8-i l A20
Word 20, bits SUPP21
12-15 A21
Word 21, bits SUPP22
0-3 A22
Word 21, bits SUPP23
4-7 A23
Word 21) bits SUPP24
8-11 A24
Word 21) bits SUPP25
12-15 A25
Word 22, bits SUPP26
0-3 A26
Word 22, bits SUPP27
4-7 A27
Word 22) bits SUPP28
8-I 1 A28
Word 22, bits SUPP29
i 2-15 A29
Word 23) bits TBCD-Null
0-3 A30
Word 23, bits TBCD-Null
4-7 A31
Word 23, bits TBCD-Null
8-11 A32
Word 23, bits TBCD-Null
I2-15 A33
Word 24) bits TBCD-Null
0-3 A34
Word 24, bits TBCD-Null
4-7 A35
Ward 24) bits TBCD-Null
8-11 A36
Word 24, bits TBCD-Null
12-15 A37
Word 25) bits TBCD-Null
0-3 A38
Word 25, bits TBCD-Null
4-7 A39
Wotd 25, bits TBCD-NutI
8-11 A40
Word 25, bits TBCD-Null
12-15 A41
Word 26, bits TBCD-Null
0-3 A42
Word 26) bits TBCD-Null
4-7 A43
Word 26, bits TBCD-Nuli
8-I1 A44
Word 26, bits TBCD-Null
12-15 A45
4. VNet Remote
Access and Calling
Party Number:
Word 15, bits N
12-15 A1
Word 16, bits X
0-3 A2
Word 16) bits X
4-7 A3
Word 16) bits N
8-11 A4
Word 16, bits X
12-15 A5
Word I7) bits X
0-3 A6
Word 17) bits X
4-7 A7
Word 17, bits X
8-11 A8
Word 17, bits X
12-15 A9
__ Word I$, bits X
0-3 A10
WoM I8, bits TBCD-Null
4-7 Al l
Word 18, bits SUPP1
8-11 A12
Word 18, bits SUPP2
12-15 A13
569
SUBSTITUTE SHEET (RULE 2B)
CA 02279845 1999-OS-17
WO 98/23(180 PCT/US97/21174
~i~ord A~, Bit ~ Description
Word 19, bits SUPP3
0-3 A14
Word 19) bits SUPP4
4-7 A15
Word 19, bits SUPPS
8-11 A16
Word 19, bits SUPP6
12-15 A17
Word 20) bits SUPP7
0-3 A18
Word 20) bits SUPP8
4-7 A19
Word 20, bits SUPP9
8-11 A20
Word 20) bits SUPP10
12-15 A21
Word 21, bits SUPP11
0-3 A22
Word 21, bits SUPPI2
4-7 A23
Word 21) bits SUPP13
8-11 A24
Word 21, bits SUPP14
12-15 A25
Word 22) bits SUPP15
0-3 A26
Word 22, bits SUPP16
4-7 A27
Word 22) bits SUPP17
8-11 A28
Word 22, bits SUPP18
12-15 A29
Word 23, bits SUPP19
0-3 A30
Word 23) bits SUPP20
4-7 A31
Word 23, bits SUPP21
8-11 A32
Word 23) bits SUPP22
12-15 A33
Word 24) bits SUPP23
0-3 A34
Word 24, bits SUPP24
4-7 A35
Word 24) bits SUPP25
8-11 A36
_
Word 24, bits SUPP26
12-15 A37
Word 25, bits SUPP27
0-3 A38
Word 25, bits SUPP28
4-7 A39
Word 25) bits SUPP29
8-11 A40
Word 25, bits SUPP30
12-15 A41
WoM 26, bits 0-3 TBCD-Null
A42
Word 26) bits TBCD-Null
4-7 A43
Word 26, bits TBCD-Null
8-11 A44
Word 26, bits TBCD-Null
12-15 A45
5. Calling Party
Number:
Word 15, bits N
12-15 A1
Word 16) bits X
0-3 A2
Word 16, bits X
4-7 A3
Word 16, bits N
8-11 A4
Wotd 16, bits X
12-15 AS
Word 17, bits X
0-3 A6
Word 17, bits X
4-7 A7
Word 17) bits X
8-11 A8
Word 17, bits X
12-15 A9
Word 18, hits X
0-3 A 10
Word 18, bits TBCD-Null
4-7 A I 1
Word 18) bits SUPP1
8-11 A12
Word 18) bits SUPP2
12-15 A13
570
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23t~0 ' PCT/US97I21174
Word k) Blt At I>~scription
._.~ ~
~
r~
Word 19) bits SUPP3
0-3 A14
Word 19, bits SUPP4
4-7 A 15
Word 19) bits SUPPS
8-11 A16
Word 19, bits SUPP6
12-15 A17
Word 20) bits SUPP7
0-3 A18
Word 20, bits SUPP8
4-7 A19
Word 20, bits SUPP9
8-11 A20
Word 20, bits SUPP10
12-15 A21
Word 21) bits SUPP11
0-3 A22
Word 21, bits SUPPI2
4-7 A23
Word 21, bits SUPP13
8-11 A24
Word 21, bits SUPP14
12-IS A25
Word 22) bits SUPP15
0-3 A26
Word 22, bits SUPP16
4-7 A27
Word 22) bits SUPP17
8-11 A28
Word 22) bits SUPP18
12-15 A29
Word 23, bits SUPP19
0-3 A30
Word 23) bits SUPP20
4-7 A31
Word 23) bits SUPP21
8-11 A32
Word 23) bits SUPP22
12-15 A33
Word 24, bits SUPP23
0-3 A34
Word 24, bits SUPP24
4-7 A35
Word 24, bits SUPP'?.5
8-11 A36
Word 24, bits SUPP26
12-15 A37
Word 25) bits SUPP27
0-3 A35
Word 25, bits SUPP28
4-7 A39
WoM 25, bits SUPP29
8-11 A40
Word 25) bits SUPP30
12-IS A4l
Word 26, bits TBCD-Null
0-3 A42
Word 26) bits TBCD-Null
4-7 A43
Word 26) bits TBCD-Null
8-11 A44
Word 26, bits TBCD-Null
12-15 A45
6. Credit Catd:
Word 15, bits X
12-15 AI
Word 16) bits X
0-3 A2
Word 16, bits X
4-7 A3
Word 16, bits X
8-11 A4
Word 16) bits X
12-15 AS
Word 17, bits X
0-3 A6
Word 17, bits X
4-7 A7
Word I7) bits X
8-I 1 A8
__ Word 17; bits X
12-15 A9
Word 18) bits X
0-3 A 10
Word 18, bits X
4-? A11
Word 18, bits X
8-11 A12
Word 18, bits X
12-15 A13
571
SUBSTITUTE SHEET (RULE 26~
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21174
Word A~, Bit ~ Description
Word 19, bits X
0-3 A 14
Word 19, bits X
4-7 A 15
Word 19, bits X
8-11 A16
Word 19, bits X
12-15 A17
Word 20, bits X
0-3 A 18
Word 20, bits X
4-7 A l9
Word 20, bits TBCD-Null -
8-11 A20
Word 20, bits SUPP1
12-15 A21
Word 21) bits SUPP2
0-3 A22
Word 21) bits SUPP3
4-7 A23
Word 21) bits SUPP4
8-11 A24
Word 21) bits SUPPS
12-15 A25
Word 22) bits SUPP6
0-3 A26
Word 22) bits SUPP7
4-7 A27
Word 22) bits SUPP8
8-11 A28
Word 22) bits SUPP9
12-15 A29
Word 23, bits SUPPIO
0-3 A30
Word 23, bits SUPPI1
4-7 A31
Word 23) bits SUPPl2
8-11 A32
Word 23) bits SUPPl3
12-15 A33
Word 24, bits SUPP14
0-3 A34
Word 24, bits SUPP15
4-7 A35
Word 24) bits SUPP16
8-11 A36
Word 24) bits SUPP17
12-15 A37
Word 25, bits SUPP18
0-3 A38
Word 25) bits SUPP19
4-7 A39
Word 25, bits SUPP20
8-11 A40
Word 25, bits SUPP21
12-15 A41
Word 26, bits SUPP22
0-3 A42
Word 26) bits SUPP23
4-7 A43
Word 26, bits SUPP24
84 1 A44
Word 26, bits SUPP25
12-15 A45
7. 14 Digit MCI/VNet
Calling Card:
Word 15, bits X
12-15 A1
Word 16, bits X
0-3 A2
Word 16) bits X
4-7 A3
' Word 16, bits X
8-11 A4
Word 16) bits X
12-15 AS
Word 17) bits X
0-3 A6
Word 17, bits X
4-7 A7
Word 17, bits
8-I1 A8
Word 17, bits X I
12-15 A9
Word 18, bits X
0-3 A10
Word 18, bits TBCD-A -
4-7 A 11
Word 18, bits TBCD-A
8-11 A12
Word 18, bits TBCD-A
12-15 A13
572
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98123080 PGT/US97/21174
Word ~, Bit ~ Description
Word 19, bits TBCD-A
0-3 A14
Word 19, bits TBCD-Null
4-7 A15
Word 19, bits SUPPI
8-11 A16
Word i9) bits SUPP2
12-15 AI7
Word 20, bits SUPP3
0-3 A18
Word 20) bits SUPP4
4-7 A19
Word 20, bits SUPPS
8-11 A20
Word 20, bits SUPP6
12-15 A21
Word 21, bits SUPP7
0~-3 A22
Word 21, bits SUPP8
4-7 A23
Word 21, bits SUPP9
8-11 A24
Word 21, hits SUPP10
12-IS A25
Word 22, bits SUPPI l
0-3 A26
Word 22, bits SUPP12
4-7 A27
Word 22) bits SUPP13
8-11 A28
Word 22) bits SUPPI4
12-15 A29
Word 23) bits SUPP15
0-3 A30
Word 23) bits SUPP16
4-7 A31
Word 23) bits SUPP17
8-11 A32
Word 23, bits SUPPl8
12-15 A33
Word 24) bits SUPP19
0-3 A34
Word 24, bits SUPP20
4-7 A35
Word 24, bits SUPP21
8-I I A36
Word 24, bits SUPP22
12-15 A37
Word 25, bits SUPP23
0-3 A38
Word 25, bits SUPP24
4-7 A39
Word 25) bits SUPP25
8-11 A40
Word 25, bits SUPP26
12-15 A41
Word 26) bits SUPP27
0-3 A42
Word 26, bits SUPP28
4-7 A43
Word 26) bits SUPP29
8-1 I A44
Word 26, bits SUPP30
12-15 A45
8. OSID/OTG:
Word 15) bits X (OSID)
12-15 A1
Word 16, bits X (OSID)
0-3 A2
Word I6, bit:4-7 X (OSID)
A3
Word 16, bits X (OTG)
8-11 A4
Word 16, bits X (OTG)
12-15 AS
Word 17, bits X (OTG)
0-3 A6
Word 17) bits X (OTG)
4-7 A7
Word I?, bits TBCD-Null
8-11 A8
Word 17) bits TBCD-Null
I2-15 A9
Word 18) bits TBCD-Null
0-3 A10
Word 18, bits TBCD-Null
4-7 A11
Word 18, bits TBCD-Null
8-11 A12
WoM 18, bits I2-15TBCD-Null
A13
573
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98123080 ' PGT/US97/21174
Word A', Bit ~ Description
Word 19, bits TBCD-Null
0-3 A14
Word 19) bits TBCD-Null
4-7 A15
Word 19, bits TBCD-Null
8-11 A16
Word 19) bits TBCD-Null
12-15 A17
Word 20, bits TBCD-Null
0-3 A 18
Word 20) bits TBCD-Null
4-7 A 19
Word 20, bits TBCD-Null
8-I1 A20
Word 20, bits TBCD-Null
12-15 A21
Word 21) bits TBCD-Null
0-3 A22
Word 21) bits TBCD-Null
4-7 A23
Word 21) bits TBCD-Null
8-11 A24
Word 21, bits TBCD-Null
12-15 A25
Word 22, bits TBCD-Null
0-3 A26
Word 22, bits TBCD-Null
4-7 A27
Word 22) bits TBCD-Null
8-11 A28
Word 22, bits TBCD-Null
12-15 A29
Word 23, bits TBCD-Null -
0-3 A30
Word 23) bits TBCD-Null
4-7 A31
Word 23) bits TBCD-Null
8-11 A32
Word 23) bits TBCD-Null
12-15 A33
Word 24, bits TBCD-Null
0-3 A34
Word 24, bits TBCD-Null
4-7 A35
Word 24) bits TBCD-Null
8-11 A36
Word 24, bits TBCD-Null
12-15 A37
Word 25, bits TBCD-Null
0-3 A38
Word 25, bits TBCD-Null
4-7 A39
Word 25) bits TBCD-Null
8-11 A40
Word 25, bits TBCD-Null
12-15 A41
Word 26) bits TBCD-Nuli
0-3 A42
Word 26, bits TBCD-Null
4-7 A43
Word 26, bits TBCD-Null
8-11 A44
Word 26) bits TBCD-Null
12-15 A45
OSID = Originating
Switch ID (000-999)
OTG = Originating
Trunk ID (0000-8191)
9. Telecotnmunication/PTT
Cards:
Word 15, bits X
12-15 A1
Word 16, bits X
0-3 A2
Word 16) bits X
4-7 A3
Word 16) bits X
8-11 A4
Word 16, bits X
12-IS AS
Word 17) bits X
0-3 A6
Word 17) bits X
4-7 A7
Word 17) bits X
8-11 A8
Word 17, bits X
12-15 A9
Word 18) bits X
0-3 A10
Word 18, bits X
4-7 A11
Word 18, bits X
8-11 A 12
Word 18) bits X
12-15 A13
574
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98!23080 PGT/US97/21174
- ~~
Word ~, Bit ~ Description
Word 19, bits X
0-3 A 14
Word 19) bits X
4-7 A15
Word 19, bits X
8-11 A16
Word 19, bits X
12-15 A17
Word 20) bits X
0-3 A 18
Word 20) bits X
4-7 A19
Word 20) bits X
8-I 1 A20
Word 20, bits X
12-15 A21
Word 21, bits X
0-3 A22
Word 21) bits X
4-7 A23
Word 21) bits TBCD-Nuil
8--11 A24
Word 21) bits SUPPI
la-15 A25
Word 22, bits SUPP2
4-~3 A26
Word 22, bits SUPP3
4-.7 A27
Word 22, bits SUPP4
8-~11 A28
Word 22, bits SUPPS
12-15 A29
Word 23) bits SUPP6
0-3 A30
Word 23) bits SUPP7
4-.7 A31
Word 23, bits SUPP8
8-~11 A32
Word 23, bits SUPP9
1:>.-15 A33
Word 24) bits SUPP10
0-3 A34
Word 24, bits SUPPI 1
4-7 A35
Word 24, bits SUPP12
8-I1 A36
Word 24) bits SUPP13
12-15 A37
Word 25, bits SUPP14
0-3 A38
Word 25) bits SUPP15
4-7 A39
Word 25) bits SUPP16
8-11 A40
Word 25) bits SUPP17
12-15 A41
Word 26, bits SUPP18
4-3 A42
Word 26) bits SUPP19
4-7 A43
Word 26, bits SUPP20
8-11 A44
Word 26) bits SUPP21
12-15 A45
10. Business Group
ID:
Word 15) bits X
12-1S A1
Word 16) bits X
0-3 A2
Word 15, bits X
4-7 A3
Word 15) bits X
8-11 A4
Word 16) bits X
12-15 AS
Word 17, bits X
0-3 A6
Word I7) bits TBCD-Null
4-7 A7
Word 17) bits SUPP!
8-I I A8
Word 17, bits SUPP2
12.-15 A9
Word 18) bits SUPP3
0-3 A10
Word 18, bits SUPP4
4=7 Ai l
Word 18) bits SUPPS
8-11 A12
Word 18, bits SUPP6
12-IS A13
575
SUBSTITUTE SHEET (RULE 28)
CA 02279845 1999-OS-17
WO 98/230811 PCTIUS97/21174
Word 11, Bit ~ Description
i
Word 19) bits SUPP7
0-3 A 14
Word 19) bits SUPP8
4-7 A15
Word l9, bits SUPP9
8-11 A16
Word 19, bits SUPP10
12-15 A17
Word 20, bits SUPP11
0-3 A18
Word 20, bits SUPP12
4-7 A19
Word 20) bits SUPP13
8-11 A20
Word 20) bits SUPP14
12-15 A21
Word 21) bits SUPPIS
0-3 A22
Word 21) bits SUPP16
4-7 A23
Word 21) bits SUPP17
8-11 A24
Word 21, bits SUPP18
12-15 A25
Word 22) bits SUPP19
0-3 A26
Word 22) bits SUPP20
4-7 A27
Word 22, bits SUPP21
8-11 A28
Word 22) bits SUPP22
12-15 A29
Word 23) bits SUPP23
0-3 A30
Word 23, bits SUPP24
4-? A31
Word 23) bits SUPP25
8-11 A32
Word 23, bits SUPP26
12-15 A33
Word 24) bits SUPP27
0-3 A34
Word 24, bits SUPP28
4-7 A35
Word 24) bits SUPP29
8-11 A36
Word 24, bits SUPP30
12-15 A37
Word 25, bits TBCD-Null
0-3 A38
Word 25, bits TBCD-Null
4-7 A39
Word 25, bits TBCD-Null
8-11 A40
Word 25, bits TBCD-Null
12-15 A41
Word 26, bits TBCD-Null --
0-3 A42
Word 26, bits TBCD-Null
4-7 A43
Word 26, bits TBCD-Null
8-11 A44
Word 26, bits TBCD-Null
I2-15 A45
11. Network Information:
Word I5, bits X
12-15 Al
Word 16, bits X
0-3 A2
Word 16, bits X
4-7 A3
Word 16, hits X
8-11 A4
Word 16) bits TBCD-Null
12-15 AS
Word 17, bits SUPP1
0-3 A6
Word 17, bits SUPP2
4-7 A7
Word 17, bits SUPP3
8-11 A8
Word 17, bits SUPP4
12-15 A9
Word 18, bits SUPPS
0-3 A10
Word 18) bits SUPP6
4-7 A11
Word 18, bits SUPP7
8-11 A12
Word 18, bits SUPP8
12-IS A13
Word 19) bits SUPP9
0-3 A I4
Word 19, bits SUPP10
4-7 A15
Word 19) biu SUPP11
8-11 A16
Word 19) bits SUPP12
12-15 A17
576
SUBSTITUTE SHEET (RULE 26)
CA 022798451999-05-17
wo 9sn3a~o rc~rrtrs9~nma
Word b) Bit ~ Description
Word 20, bits SUPP13
0-3 A18
Word 20, bits SUPP14
4-.7 A19
Word 20, bits SUPP15
8-11 A20
Word 20, bits SUPPl6
12-15 A21
Word 21, bits SUPP17
0-3 A23
Word 21, bits SUPP18
4-7 A23
Word 21) bits SUPPI9
8-I1 A24
Word 21, bits SUPP20
12-IS A25
Word 22, bits SUPP21
0-3 A26
Word 22, bits SUPP22
4-7 A27
Word 22) bits SUPP23
8-11 A28
Word 22, bits SUPP24
12:-15 A29
Word 23) bits SUPP25
0-:3 A30
Word 23) bits SUPP26
4=7 A31
Word 23) bits SUPP27
8-I1 A32
Word 23, bits SUPP28
12-IS A33
Word 24, bits SUPP29
0-:3 A34
Word 24, bits SUPP30
4=I A35
Word 24) bits TBCD-Null
8-11 A36
Word 24, bits TBCD-Null
12-15 A37
Word 25, bits TBCD-Null
0-:3 A38
Word 25, bits TBCD-Null
4= 7 A39
Word 25) bits TBCD-Null
8-I1 A40
Word 25) bits TBCD-Nuil
12-15 A41
Word 26, bits TBCD-Null
0-3 A42
Word 26, bits TBCD-Null
4-7 A43
Word 26) bits TBCD-Null
8-11 A44
Word 26, bits TBCD-Null
12-IS A45
12. BOC/LBC Card:
Word 15, bits N
12-IS A1
Word 16, bits X
0-3 A2
Word 16) bits X
4-7 A3
Word 16, bits N
8-11 A4
Word 16, bits X
12-~IS AS
Word 17) bits X
0-3 A6
Word 17, bits X
4-T A7
Word 17, bits X
$-11 AR
Word I7) bits X
12-15 A9
- Word 18, bits X
0-3 A10
Word 18) bits TBCD-Null
4-7 A1 I
Word 18) bits TBCD-Null
8-11 A12
Word l8) bits TBCD-Null
12-15 A13
577
SUBSTITUTE SHEET (RULE 2fi)
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97I21174
Word b) Bit li Description
I
Word 19, bits TBCD-Null
0-3 A 14
Word 19, bits TBCD-Null
4-7 A15
Word 19, bits TBCD-Null
8-I l A16
Word 19, bits TBCD-Null
12-15 A17
Word 20) bits TBCD-Null
0-3 A18
Word 20) bits TBCD-Null
4-7 A19
Word 20, bits TBCD-Null
8-11 A20
Word 20, bits TBCD-Null
12-15 A21
Word 21, bits TBCD-Null
0-3 A22
Word Z1) bits TBCD-Null
4-7 A23
Word 21, bits TBCD-Null
8-11 A24
Word 21) bits TBCD-Null
12-15 A25
Word 22) bits TBCD-Null
0-3 A26
Word 22, bits TBCD-Null
4-7 A27
Word 22, bits TBCD-Null
8-11 A28
Word 22, bits TBCD-Null
12-15 A29
Word 23, bits TBCD-Null
0-3 A30
Word 23) bits TBCD-Null
4-7 A31
Word 23) bits TBCD-Null
8-I1 A32
Word 23, bits TBCD-Null
i2-15 A33
Word 24, bits TBCD-Null
0-3 A34
Word 24, bits TBCD-Null
4-7 A35
Word 24) bits TBCD-Null
8-I 1 A36
Word 24) bits TBCD-Null
12-15 A37
Word 25) bits TBCD-Null
0-3 A38
Word 25, bits TBCD-Null
4-7 A39
Word 25) bits TBCD-Null
8-11 A40
Word 25, bits TBCD-Null
12-15 A41
Word 26, bits TBCD-Null
0-3 A42
Word 26) bits TBCD-Nuil
4-7 A43
Word 26, bits TBCD-Null
8-11 A44
Word 26, bits TBCD-Null
I2-15 A45
13. Third Party
Numbcr:
Word 15, bits N
12-15 AI
Word 16) bits X
0-3 A2
Word 16, bits X
4-7 A3
Word 16, bits N
8-11 A4
Word 16, bits X
12-15 A5
Word 17, bits X
0-3 A6
Word 17) bits X
4-7 A7
Word 17, bits X
8-11 A8
Word 17, bits X
12-15 A9
Word 18, bits X
0-3 A10
Word 18, bits TBCD-Null
4-7 A 11
Word 18, bits TBCD-Null
8-11 A12
Word 18) bits TBCD-Null
12-15 A13
Word 19, bits TBCD-Null
0-3 A 14
Word 19, bits TBCD-Null
4-7 A15
Word 19) bits TBCD-Null
8-I I A16
Word 19, bias TBCD-Null
12-15 A17
578
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23880 PtCT/US97/21174 -
~ ~~.~
Word A~, Bit A~ Description
Word 20, bits TBCD-Null
0-3 A18
Word 20, bits TBCD-Null
4-7 A19
Word 20, bits TBCD-Null
8-11 A20
Word 20) bit:; TBCD-Null
12-15 A21
Word 21, bits TBCD-Null
0-3 A22
Word 21, bits TBCD-Null
4-7 A23
Word 21) bits TBCD-Null
8-11 A24
Word 21, bits TBCD-Null
I2-15 A25
Word 22) bits TBCD-Null
0-3 A26
_ TBCD-Null
Word 22) bits
4-? A27
Word 22, bits TBCD-Null
8-11 A28
Word 22) bits TBCD-Null
12-15 A29
Word 23) bits TBCD-Null
0-3 A30
Word 23, bits TBCD-Null
4-7 A31
Word 23) bits TBCD-Null
8-11 A32
Word 23, bits TBCD-Null
12-IS A33
Word 24) bits TBCD-Null
0-3 A34
Word Z4, bits TBCD-Null
4-7 A35
Word 24, bits TBCD-Null
8-11 A36
Word 24, bits TBCD-Null
12-IS A37
Word 25, bits TBCD-Null
0-3 A38
Word 25) bits TBCD-Null
4-7 A39
Word 25) bits TBCD-Null
8-11 A40
Word Z5) bits TBCD-Null
12-IS A41
Word 26) bits TBCD-Null
0-3 A42
Word 26) bits TBCD-Null
4-7 A43
Word 26, bits TBCD-Null
8-11 A44
Word 26, bits TBCD-Null
:l2-15 A45
14. International
Number:
Word 15, bits X(CC)
I2-15 Ai
Word 16, bits X(CC)
(I-3 A2
Word 16, bits X(CC)
4-7 A3
Word 16, bits X(NN)
8-11 A4
Word 16, bits X(NN)
12-15 AS
Word 17) bits X(NN)
0-3 A6
Word 17, bits X(NN)
4-7 A7
Word 17) bits X(NN)
8-11 A8
Word 17) bits X(NN)
12-15 A9
Word 18) bits X(NN)
0-3 A10
Word 18, bits X(NN)
4-7 A 11
Word 18) bits X(NN)
8-11 A12
Word I8, bits X(NN)
1'2-IS A13
Word 19, bits X(NN)
0-3 A 14
Word 19, bits X(NN)
4.-7 A15
Word 19) bits TBCD-Null
8-11 A16
Word 19, bits TBCD-Null
I'?-IS A17
579
SUBSTITUTE SHEET (RULE 28)
CA 02279845 1999-OS-17
WO 98/23080 - PCT/US97/21174
Word II, Bit I! Description
Word 20) bits TBCD-Null
0-3 A18
Word 20, bits TBCD-Null
4-? A19
Word 20) bits TBCD-Null
8-11 A20
Word 20, bits TBCD-Null
12-15 A2I
Word 21, bits TBCD-Null
0-3 A22
Word 21, bits TBCD-Null
4-7 A23
Word 21, bits TBCD-Null
8-11 A24
Word 21, bits TBCD-Null
12-15 A25
Word 22, bits TBCD-Null
0-3 A26
Word 22, bits TBCD-Null
4-7 A27
Word 22) bits TBCD-Null
8-11 A?.8
Word 22, bits TBCD-Null
12-15 A29
Word 23, bits TBCD-Null
0-3 A30
Word 23, bits TBCD-Null
4-7 A31
Word 23, bits TBCD-Null
8-11 A32
Word 23) bits TBCD-Null
12-15 A33
Word 24) bits TBCD-Null
0-3 A34
Word 24, bits TBCD-Null
4-7 A35
Word 24) bits TBCD-Null
8-11 A36
Word 24, bits TBCD-Null
12-15 A37
Word 25, bits TBCD-Null
0-3 A38
Word 25) bits TBCD-Null
4-7 A39
Word 25, bits TBCD-Null
8-I1 A40
Word 25, bits THCD-Null
12-15 A41
Ward 26) bits TBCD-Null
0-3 A42
Word 26) bits TBCD-Null
4-7 A43
Word 26, bits TBCD-Null
8-1 I A44
Word 25) bits TBCD-Null
!2-15 A45
CC = Customer
Connect
NN = National
Number
15. LAN Sequence
Number:
Word 15) bits X
12-15 A1
Word 16, bits X
0-3 A2
Word 16) bits X
4-7 A3
Word 16, bits X
8-11 A4
Word 16) bits X
12-15 A5
Word l7) bits X
0-3 A6
Word 17) bits X
4-7 A7
Word 17, bits X
8-11 A8
Word 17, bits X
12-15 A9
Word 18) bits X
0-3 . A10
Word 18, bits X
4-7 A11
Word 18, bits X
8-I I A 12
Word 18, bits TBCD-Null
12-15 A13
Word 19) bits TBCD-Null I
0-3 A 14
Word 19) bits TBCD-Null
4-7 A15
Word 19) bits TBCD-Null
8-11 A16
Word 19, bits TBCD-Null
12-15 A17
580
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
0 PCT/US97/21174
II~ Wont ~, Bit ~ I Dest.Mptfon
Word 20) A18 TBCD-Null
bits 0-3
Word 20) AI9 TBCD-Null
bits 4..7
Word 20, A20 TBCD-Null
bits 8..11
Word 20, TBCD-Null
bits 12-15
A21
Word 21, A2Z TBCD-Null
bits 0-3
Word 21, A23 TBCD-Null
bits 4-.7
Word 21, A24 TBCD-Null
bits 8-I
I
Word 21, TBCD-Null
bits 12
-15 A''S
Word 22) A26 TBCD-Null
bits 0-3
Word 22, A27 TBCD-Null
bits 4-7
Word 22, A28 TBCD-Nutl
bits 8-I
I
Word 22) TBCD-Null
bits 12:-15
A29
Word 23, A30 TBCD-Null
bits 0-3
Ward 23, A31 TBCD-Null
bits 4-7
Word 23) A32 TBCD-Null
bits 8-11
Word 23) TBCD-Null
bits 12-15
A33
Word 24) A34 TBCD-Null
bits 0-:3
Word 24) A35 TBCD-Null
bits 4-7
Word 24, A36 TBCD-Null
bits 8-l
l
Word 24, A37 TBCD-Null
bits 12-15
Word 25, A38 TBCD-Null
bits 0-'.3
Word 25, A39 TBCD-Null
bits 4-'1
Word 25) A40 TBCD-Null
bits 8-I
1
Word 25) A41 TBCD-Null
bits 12-I5
Word 26, A42 TBCD-Null
hits 0-3
Word 26) A43 TBCD-Null
bits 4-7
Word 26) A44 TBCD-Null
bits 8-11
Word 26) A45 TBCD-Null
bits 12.-15
16. DNIS:
Word 15) bits N
12-15 A1
Word 16) bits X
0-3 A2
Word 16) bits X
4-T A3
Word 16) bits N
8-11 A4
Word 16) bits X
12-15 A5
Word 17, bits X
0-3 A6
Word 17, bits X
4-7 A7
Word 17) bits X
8-11 A8
Word 17, bits X
i2-15 A9
Word 18) bits X
0-3 A10
Word 18, bits TBCD-Nuil
4-7 Al 1
Word 18) bits TBCD-Null
8-I1 A12
Word 18) bits TBCD-Null
12-15 A13
Word 19, bits TBCD-Null
0-3 A 14
Word 19, bits TBCD-Null
4-7 A15
Word 19, bits TBCD-Null
8-11 A16
Word 19, bits TBCD-Null
12-15 A17
581
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO PGT/ITS97I21174
Word A~, Bit A~ Description
Word 20, bits 0-3 Ai8 TBCD-Null
Word 20, bits 4-7 A19 TBCD-Null
Word 20, bits 8-~11 A20 TBCD-Nuil
Word 20, bits 1'~-15 A21 TBCD-NuII
Word 21, bits 0-~3 A22 TBCD-Null
Word 21, bits 4..7 A23 TBCD-Null
Word 21, bits 8-~11 A24 TBCD-Null
Word 21) bits 12-15 A25 TBCD-Null
Word 22, bits 0-3 A26 _ TBCD-Null
Word 22) bits 4-7 A27 TBCD-Null
Word 22) bits 8-11 A28 TBCD-Null
Word 22) bits 12-15 A29 TBCD-Null
Word 23, bits Q-3 A30 TBCD-Null
Word 23, bits 4-7 A31 TBCD-Null
Word 23) bits 8-11 A32 TBCD-Null
Word 23) bits 12-15 A33 TBCD-Null
Word 24, bits 0-3 A34 TBCD-Null
Word 24) bits 4-7 A35 TBCD-Null
Word 24) bits 8-11 A36 TBCD-Null
Word 24, bits 12-15 A37 TBCD-Null
Word 25) bits 0-3 A38 TBCD-Null
Word 25, bits 4-7 A39 TBCD-Null
Word 25) bits 8-11 A40 TBCD-Null
Word 25, bits 12-15 A41 TBCD-Null
Word 26) bits 0-3 A42 TBCD-Null
Word 26) bits 4-7 A43 TBCD-Null
Wotd 26) bits 8-11 A44 TBCD-Null
Ward 26, bits 12-15 A45 TBCD-Null
17. Network Call Identifier (NCID): If
the NCID is recorded in
the "A" field) it is recorded in binary
beginning with A1. The
entry code wih indicate the call processing
associated with the
particular call ar '0.' If the NCID is
recorded in the NCID field
of a 64-word call record, the entry code
will also indicate the call
processing associated with the particular
call or '0.' The NCID
comprises the following:
Originating Switch 1D
Originating Trunk Group
Originating Port Number
Timepoint 1
NCID Sequence Number
Word 27) bits 0-3 Feature Code (FC): Same as OSR/POSR format.
Word 27) bits 4-7 Terminating Network Code (TNC): Same as
OSR/POSR format.
Word 27, bits 8-11 Network Access Type (NAT): Same as OSR/POSR
fortnat.
Word 27, bits 12-15 Timepoint 7 Qualifier (TP&Q): Same as
OSR/POSR format.
Word 28, bits 0-6 Entry Code (EC): Same as OSR/POSR format.
Word 28, bits 7-9 Prefix Digits (PD): Same as OSR/POSR format
Word 28, bits 10-12 NCS/DAP ID (NDID): Same as OSRIPOSR format.
Word 28, bits 13-15 Division ID (DIVID): Same as OSR/POSR
format.
582
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PGT/US97/21174
Word ~Y, Bit A~ Description
Word 29) bits 0 Distant Overflow (DO): Same as OSR/POSR
format.
Word 29) bit 1 MCI Network Overflow (MNO): Same as OSR/POSR
format.
Word 29, bit 2 Customer Connect (CC): Same as OSR/POSR
format.
Word 29) bit 3 Inter-Network (IN): Same as OSR/POSR format.
Word 29) bit 4 Not Used
Word 29, bit S SAC Bit (SC): This bit is used for the
Flexible SAC feature. This
bit will be set to "I" whenever the received
number which is
collected during the address digit collection
phase, is identified as
a SAC number in the FlexSac Index associated
with the
originating trunk group. This bit will
be sec to "0" in all other
cases.
Word 29, bit 6 CaII Direction (CD): Same as OSR/POSR
format.
Word 29, bit ? Destination (DE): Same as OSRIPOSR format.
Word 29, bit 8 Dedicated Termination (DT): Same as OSR/POSR
format.
Word 29, bit 9 Person-to-Person (PO): Same as OSR/POSR
format.
Word 29, bit 10 Transferred Bit (XB): Same as OSRIPOSR
format.
Word 29, bit 11 Satellite (SA): Same as OSR/POSR format.
Word 29) bits 12-15 Nature of Calling Locarion ID (NOCLI):
Same as OSR/POSR
format.
Word 30) bits 0-15 Carrier Number (CN): Same as OSR/POSR
format.
Word 31) bits 0-3 Authorization Code ID (ACIF): Same as
OSR/POSR format.
Word 31, bits 4-ZO Release Code (RC): Same as OSR/POSR format.
Word 31, bits 11-13 NCID Sequence Number: Same as OSR/POSR
format.
Word 31, bit 14 NCID Location (NCIDLOC): Same as OSR/POSR
format.
Word 31, hit 15 Remote ANI Screened (RS): Same as OSR/POSR
format.
Word 32) bits 0-15 Time & Changes Guest Name (T&C Guest):
Word 33) bits 0-15 Records the Time
and Charges guest name that will be passed
back to the switch
from the operator service platform for
the time and charges
feature. The inforrnation is recorded
as ASCII characters starting
with the first character in word 32) bits
0-7.
583
SUBSTITUTE SHEET (RULE 28)
CA 02279845 1999-OS-17
WO 98/23080 PGT/US97/21174
Word ~Y, Bit A~ Description
Word 34, bits 0-15 Destination Address
(DA): Records up to
25 digits of the
Word 35, bits 0-I5 destination address
in TBCD format in
the sequence that
they are
Word 36, bits 0-15 received or translated
to) starting with
D 1. Unused bytes
contain
Word 37, bits 0-15 TBCD-Null.
Word 38) bits 0-15
Word 39, bits 0-15 7-digit 10-digitDDD IDDD
Word 40, bits 0-3 Word 34, bits 0-3 D N N CC
1 N
Word 34, bits 4-7 D2 X X ' CC
X
Word 34, bits 8-11 X X CC
D3 X
Word 34) bits 12-15 N N NN
.D4 X
Word 35) bits 0-3 D5 X X NN
X
Word 35) bits 4-7 D6 X X NN
X
Word 35, bits 8-I I X X NN
D7 X
Word 35, bits 12-15 X X NN
D8 X(TSID)
Word 36, bits 0-3 D9 X X NN
X(TSID)
Word 36, bits 4-7 D10 X X NN
X(TSID)
Word 36, bits 8-I1 X(TSID)T-NullNN
D1I X(TTG)
Word 36) bits 12-15 X(TSID)T-NullNN
D12 X(TTG)
Word 37, bits 0-3 D X(TSID)T-NullNN
13 X(TTG)
Word 37, bits 4-7 D14 X(TTG) T-NullNN
X(TTG)
Word 37) bits 8-l l X(TTG) T-NullNN
D15 T- Null
Word 37, bits 12-IS X(TTG) T-NullT-Null
D16 T-Nuli
Word 38, bits 0-3 D17 X(TTG) T-NullT-Null
T-Nuli
Word 38) bits 4-7 D T-NuIi T-NullT-Null
18 T-Null
Word 38, bits 8-I1 T-Null T-NullT-Null
D19 T-Nuli
Word 38, bits I2-15 T-Null T-NutlT-Null
D20 T-Null
Word 39, bits 0-3 D21 T-Null T-NullT-Null
T-Null
Word 39) bits 4-7 D22 T-Null T-NullT-Null
T-Null
Word 39, bits 8-11 T-Null T-NullT-Null
D23 T-Null
Word 39) bits 12-15 T-Null T-NullT-Null
D24 T-Null
Word 40, bits 0-3 D25 T-Null T-NullT-Null
T-Null
CC = Customer Connect
NN = National Number
TSID = Terminating
Switch ID
TTG = Terminating Trunk
ID
T-Null = TBCD-Null
564
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
PCT/US97/21174
I~ Word 1l, Bit ~ I Description
18-digit
Word 34) D N
bits (1-3 1
Word 34) D2 N
bits 4-7
Word 34, D3 N
bits 8-11
Word 34) N
bits 12-IS
D4
Word 35) DS N
bits 0-3
Word 35, D6 N
bits 4-7
Word 35, D7 N
bits 8-11
Word 35, N
bits 12-15
D8
Word 36, D9 N
bits 0-3
Word 36, D N
bits 4-7 10
Word 36) D11N
bits 8-11
Word 36) N
bits 12-15
D12
Word 37, D N
bits 0-3 13
Word 37) D N
bits 4.-7 14
Word 37, D15N
bits 8-11
Word 37) D N
bits 12-15 l6
Word 38) D17N
bits 0-3
Word 38, D18N
bits 4-.7
Word 38) D19X (TSID)
bits 8-~11
Word 38) D20X (TSID)
bits 12-IS
Word 39) D21X (TSID)
bits 0-3
Word 39) D22X (TTG)
bits 4-7
Word 39, D23X (TTG)
bits 8-11
Word 39) D24X (TTG)
bits 12-15
Word 40, D25X (T'TG)
bits 0-3
TSID = Terminating Switch
ID
TTG = Terminating Trunk
Group
Word 40, bits Pretranslated Digits
4-15 (PTD): Represents u
to 15 di
i
f
p g
Word 41) bits number that is the translation ts
0-15 of a number dia o
a
led
b
h
y e caller.
Word 42) bits t
0-15
Word 43) bits
0-15
10 digit VNed
VNet,SAC OOY 7 IDDD
digit
DNIS, or SAC VNet l5
or digit
Hotline CodeSNS (example)
Word 40
bits 4-7 PTDI N
, 0 N N
Word 40) bits 8-I 1 0 N
PTD2 X
N
Word 40, bits I2-IS Y X N
PTD3 X
Word 41, bits 0-3 PTD4 N X N
N
Word 41, bits 4-7 PTDS X X N
X
Word 41) bits 8-11 PTD6X X N
X
Word 41, bits 12-IS X X N
PTD7 X
Word 42) bits 0-3 PTD8 X T-NullN
X
Word 42) bits 4-7 PTD9 X T-NullN
X
Word 42, bits 8-11 PTDIOX T-NullN
X
Word 42) bits 12-IS T-NullT-NullN
PTD11 T-Null
Word 43) bits 0-3 PTD12T-NullT-NullN
T-Null
Word 43, bits 4-7 PTD13T-NullT-NullN
T-Null
Word 43, bits 8-11 PTD14T-NullT-NullN
T-Null
Word 43) bits 12-1S T-NullT-Nul!N
PTD15 T-NuEI
T-Null = TBCD-Null
585
SUBSTITUTE SHEET (RULE 26j
CA 02279845 1999-OS-17
WO 98/23080 PCT/US97/21I74
Word k, Bit ~ Description
Word 44) bits 0-7 Enhanced international Routing (EIR) Call
Type: Contains the EIR -
call type ID as received from the DAP in
the NCS billing
information parameter or from the operator
in the NCS billine
information ISUP RLT parameter. It is recorded
in binary) the
default = '0.'
Word 44, bits 8-14 Overflow Cause Value (OVFVAL): This field
is the bi
nary
equivalent of the first cause value received
or fotinatted in-switch
.
This value is taken from the cause value
subfieid in the
cause
parameter that initiated overflow.
Word
44) Counts As Bid (CB): Used with the EiR feature.
bit This bit is set to
15
'I' or '0' as per the information received
from the DAP in the CB
field of the NCS billing information parameter
or from the
operator in the NCS billing information
ISUP RLT parameter.
0 = Does not count as bid (default)
1 = Counts as bid
Word Overflow Cause Location (OVFCL): This field
45) is the binary
bits
0-3
equivalent of the value recorded from the
first cause location
received or formatted in-switch. This information
is taken from
the cause location subfield in the cause
parameter that initiated
overflow.
Word Desired Tet~ninating Address (DTA): These
45) 15 bytes contain the
bits
4-15
Word originally intended or "desired" termination
46, before overflow was
bits
0-IS
Word ttyggered. They contain either: 1) the
47, desired terminating switch id
bits
0-15
Word and trunk group for calls that were sent
48) to a DTC termination, 2)
bits
0-15
a national number) or 3) international
number based on what the
action code returned from the DAP for the
desired termination.
DTC
DTSID +
DTTG DDD
Word 45) bits 4-7 DTA L 0 N
Word 45) bits 8-11 DTAZ X (DTSID 1 ) X
Word 45) bits 12-15 DTA3 X (DTSID2) X
Word 46, bits 0-3 DTA4 X (DTSID3) N
Word 46, bits 4-7 DTAS 0 X
Word 46, bits 8-lI DTA6 X (DTTGI) X
Word 46) bits 12-IS DTA7 X (DTTG2) X
Word 47, bits 0-3 DTA8 X (DTTG3) X
Word 47) bits 4-7 DTA9 X (DTTG4) X
Word 47) bits 8-11 DTA10 TBCD-Null X
Word 47) bits I2-IS DTA11 TBCD-Null TBCD-Nul!
Word 48) bits 0-3 DTA12 TBCD-Null TBCD-Null
Word 48, bits 4-7 DTA13 TBCD-Null TBCD-Null
Word 48, bits 4-11 DTA14 TBCD-Nuil TBCD-Null
Word 4$, bits 12-15 DTA15 TBCD-Null TBCD-Null
DTSID = Desired Terminating Switch ID
DTTG = Desired Terminating Trunk Group
586
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
PCT/US97/Z1174
Word ~) Bit ~ Description '
IDDD DTC
(example) (future)
Word 45) bits 4-7 DTA 1 CC X (DTSID I
)
Word 45, bits 8-11 DTA2 CC X (DTSID2)
Word 45, bits 12-15 DTA3 CC X (DTSID3)
Word 46, bits 0-3 DTA4 NN X;(DTSID4)
Word 46) bits 4-7 DTAS NN X (DTTG I )
~
Word 46) bits 8-11 DTA6
NN X (DTTG2)
Word 4b) bits I2-15 DTA7 NN X (DTTG3)
Word 47, bits 0-3 DTA8 NN X (DTTG4)
Word 47, bits 4-7 DTA9 NN X (DTTGS)
Word 47, bits 8-11 DTA10 NN TBCD-Null
Word 47, bits 12-15 DTA11 NN TBCD-Null
Word 48) bits 0-3 DTA12 NN TBCD-Null
Word 48) bits 4-7 DTA13 NN TBCD-Null
Word 48) bits 8-11 DTA14 NN TBCD-Null
Word 48, bits 12-15 DTA15 TBCD-Null TBCD-Null
CC = Customer Connect
NN = National Number
DTSID = Desired Terminating Switch ID
DTTG = Desired Terminating Trunk Group
Word 49, bits 0-6 Overflow Count (OVFC): Indicates the total
number of
intermediate overflow attempts before
successful termination was
achieved. This value is incremented each
time the DAP is
accessed for overflow information.
Word 49) bits 7-12 Desired Termination Action Code (DTAC):
This field represents
the action code which was received from
the DAP in the first
response. This information is used to
identify the type of
information which is recorded in the DTA
field.
Word 49) bit 13 Not Used
Word 49, bits 14-15 Network Call Identifier (NC1D): Contains
the binary
Words 50-54, bits 0-15 representation of the NCID. The NCID is
recorded here at
iacermediste and terminating switches
if the Authcode field is
being used to rexord other information.
The NCID is created at
the originating switch and is passed to
intermediate and
terminating switches. The format of the
NCID is:
Originating Switch ID (OSID)
Originating Trunk Group (OTG)
Originating Port (OP)
Timepoint 1 (TPI)
NCID Sequence Number
Word 55, bits 0-15 Time and Charges Room Number (T&C Room):
This field
Word 56, bits 0-15 records the time; and charges room number
that will be passed
Word 57, bits 0-15 back to the switch from the operator service
platform for the time
and charges feature. The information is
recorded as ASCII
characters starting with the first character
in word 53, bits 0-7.
587
SUBSTITUTE SHEET (RUL.E 26)
CA 02279845 1999-OS-17
WO 98123080 PGT/ITS97/21174
Word i'I, Bit ~Y Description
Word 58) bits 0-15 EVS Application Counter (EAC-i): This
Word 59 field records the EVS
bits 0-15
) application counter values if an ARU
Word 60 is used in the call. The field
bits 0-156
, contains the digits that were dialed
by the customer in response to
audio menu options.
Word 61, bits 0-13 Operator ID Number (OPIN): This field
contains th
e operator ID
number of the operator that handled the
call.
Word 61, bits 14-15 Overflow Cause Coding Standard (OVFCS):
Contains the binary
equivalent of the first coding standard
received or formatted in-
switch. This value is taken from the
coding standard subfieid in
the cause parameter that initiated overflow.
It will not be
overwritten by subsequent coding standards
received or in-switch
formatted values. This field is used
for enhanced overflow calls
only.
Word 62, bits 0-12 Timepoint 5 (TPS): A binary count of
the number of seconds
between the time timepoint 1 occurred
and the time that the
operator stopped handling the call and
releases the position. If the
call is transferred to other operators,
the value contained in this
field shall express the release time
of the last operator providing
the service.
Word 62, bits 13-15 Not Used.
Word 63, bits 0-15 Room Number (RN): Contains the last four
digits of the Callin
g
Station ID (CSI) when a call originates
from a hotel
a
i
i
,
un
vers
ty,
or any other community identified by
only a main telephone
number. The CSI shall be obtained from
the originating signalling
information) or verbally by the operator
who enters the
information manually into the OSR.
Word 0) bits 0-3 ~ Call Record Id (CRID): Identifies the record type.
0 = Default
1 = CDR
2 = SER
3 = PNR
4 = OSR
= POSR
6 = ECDR
7 = EPOSR
8 = EOSR
9 = EPOSR
10-15 = Not Used
Word 0, bits 4-15 Sync word: This word contains a minus two (77768).
Word 1, bits 0-15 Call Disconnect 1D (CDID): Identifies the cal . Each call
Word 2) bits 0-15 record has a unique number. When a switch cold restart of
reload
occurs) the CDID is set to 0 and a Switch Event Record with an
event code of 3 is written. When the CDID count rolls over, an
event code of i0 SER is recorded.
588
SUBSTITUTE SHEET (RULE 2B)
CA 02279845 1999-OS-17
WO 98/23080 - PCTIUS97121174
Word #, Bit # Description
Word 3, bits 0-IS Switch ID (SWID): Contains the unique
identifier of the current
switch. the SWID consists of three (3)
packed alphanumeric
characters. The lead character may be
any hex digit (0-F). The
next two (2) characters are any number
in a base 36 system. Base
36 symbols are 0-9, A-Z. The maximum
octal number in the base
36 is 438 which represents the letter
Z. Values 44a through 77s are
unused.
Word 3, bits 0-3 SWIDI (0-9) A-F)
Word 3) bits 4-9 SWID2 (0-9) A-Z)
Word 3, bits 10-15 SWID3 (0-9, A-Z)
Word 4, bits 0-7 Switch Type (ST): Indicates the type
of switch.
0 = default
1 = 580L SCX
2 = DEX-400
3 = CTSS-1006
4 = CTSS-4000
5 = DMS-250
6 = AXE-10
7 = DEX-600
8 = DMS-300
9 = DMS-TOPS
10 = DEX-600E
11 = AS20
12 = AS27
13 = EVS ARU
14-255 = Not Used
589
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PC'T/US97/21174
Word ~) Bit A~ Description
Word 4) bits 8-15 Event Qualifier (EQ): Identifies the event
causing the record.
0 = default
1 = Input command or automatic system
update that changed date
- 2 = Input command or automatic system
update that changed
time
3 = System restart
4 = Hourly log (HH:00:00)
5 = Recovery Action
6 = End of billing data (End of File)
7 = Stan of billing data (Start of File)
8 = NEMAS SRB blocking record (end of
billing block)
9 = Daylight savings time changed (time
and offset time changed)
IO = CDID LOG (CDID roiled over to 0)
11 = Not Used
I2 = Blank SER (filler record for billing
block)
13-255 = Not Used
An event code 7 SER will always be the
first record in the call
history data set.
An event code 8 SER will always be the
last record in the call
block and will be immediately proceeded
by event code 6.
An event code 9 SER will be invoked by
a rnan-machine
command that invokes a Daylight Saving
'Time change.
An event code 10 SER will be written each
time the Call
Disconnect ID (CDID) rolls over from a
maximum count to '0'
.
This event code will not be written for
CDID rollovers due to
system restarts.
Word 5, bits 0-15 SER Event Time (SERET): Contains the epoch
Word 6 time of this SER
bits 0-IS
) and is used for event codes.
Word 7, bits 0-3 Not Used
Word 7, bits 4-15 First CDID (FCD1D): Contains the last
12 bits of the CDID that
was recorded in the first call record
or SER in this billing block
.
This field is used in SER event code 8.
Word 8) bits 0-3 Not Used
Word 8, bits 4-15 Last CDID (LCDID): Contains the CDID th
t
a
was recorded in the
last call record or SER in this billing
block. This field is used in
SER 8.
Word 9, bits 0-3 Not Used
Word 9, bits 4-15 Next CDID (NCDID): Contains the CDID in
the next call record
or SER. This field is used in SER 8.
Word 10) bits 0-IS NEMAS Blocking Sequence Number (NBSN):
Contains the
NEMAS blocking sequence number in event
code 8 SERs
The
.
first event code 8 SER within a call history
tile is set to a NBSN
value of 0. The NBSN value is sequentially
incremented in
following event code 8 SERB.
590
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
WO 98/23080 PGT/US97/21174 -
Word A~) Bit A~ Description
Word 11) bits 0-IS Previous Time (PT): Contains the epoch
tithe of the time before a ~
Word 12) bits 0-IS system time change was made. Used in SER
1) 2) and 9.
Word 13, bit 0 Sign Bit (SB): Indicates whether the time
offset is a negative or
positive number. This field is used in
all SERB.
0 = positive offset
1 = negative offset
Word 13, bits I-10 Time Offset (TOI: Used to record the time
offset from universal
time (UTC) in one minute increments. This
field is used in all
SERB.
Word 13) bits 11-15 Not Used.
Word 14, bits 0-15
Word 15) bits 0-15
Word !6, bits 0-15 Software Load ID1-6: Contains 6 bytes
of the software load
Word 17, bits 0-15 identifier of the switch recording the
billing. This field is written
Word 18) bits 0-15 in EBCDIC format and contains the same
data as the software
load identifier that is recorded in the
call history tape label
Word 19, bits 0-1 S Last Patch A~ 1, I12: These 2 bytes contain
the latest patch . _
number/point release of the switch recording
the billing. This field
is written in EBCDIC format and contains
the same data as the
latest patch numberlpoint reiesse that
is recorded in the coil
history tape label. The point release
identifies the upgrade level of
the current software load. Used in SER
7.
Word 20) bits 0-5 Quantity CDR (QCDR): Contains the quantity
of CDRs that were
recorded in this billing block. Used only
for eveat code 8 SERB.
Word 20) bits 6-i l Quantity ECDR (QECDR): Contains the quantity
of expanded
CDRs that wsre recorded in this billing
block. Used only for
event code 8 SERs.
Word 20, bits 12-15 Not Used
Word 21, bits 0-5 Quantity PNR (QPNR): Contains the quantity
of PNRs that were
recorded in this billing block. Used only
for event code 8 SERB.
Word 21, bits 6-11 Quantity EPNR (QEPNR): Contains the quantity
of expanded
PNRs that were t~ecorded in this billing
block. Used only for event
code 8 SERB.
Word 21, bits 12-15 Not Used
Word 22, bits 0-5 Quantity_OSR (QOSR): Contains the quantity
of OSRs that were
recorded in this billing block. Used only
for event code 8 SERB.
Word 22) bits 6-11 Quantity EOSR (QEOSR): Contains the quantity
of expanded
OSRs that were recorded in this billing
block. Used only for event
code 8 SERs.
Word 22) bits 12-15 Not Used
Word 23) bits 0-5 Quantity POSR (QPOSR): Contains the quantity
of POSRs that.
were recorded in this billing block. Used
only for event code 8
SERs.
591
SUBSTITUTE SHEET (RULE 2B)
CA 02279845 1999-OS-17
WO 98/23080
PCTJUS97/21174
Word k) Blt ~ Description
-------~.
Word Z3, bits 6-11 - Quantity EPOSR (QEPOSR): Contains the
quantity of expanded
POSRs that were recorded in this billing
block. Used oNy for
event code 8 SERs)
Word 23, bits i2-15 Not Used
Word 24) bits 0-S Quantity SER (QSER): Contains the quantity
of SERB that were
recorded in this billing block. Used only
for event code g SERB.
Word 24, bits 6-12 Call History File Number ( Contains the
call history file
number as assigned whey a call history
file is opened at the
switch. Used in all SERB. The first opened
file contains a CHFN
value of 0. Each new file opened in that
same day shall increment
the CHFN by one. When the Julian date
changes (at midnight),
the next file opened shall cause the CHFN
to be reset back to
zero.
Word 24, bits I3-14 Not Used.
Word 24, bit 15 SER 12 Used (SU): This bit is set in an
SER 8 if the previous call
record was a SER I2.
Word 25, bits 0-15 CDR Throttle Start Time: Records the epoch
time whe
CDR
Word 26, bits 0-15 n
throttling started. Used in SER 8.
Word 27) bits 0-15 CDR Throttle Stop Time: Records the epoch
time when CDR
Word 28, bits 0-15 throriling stopped. Used in SER 8.
Word 29, bits 0-11 Not Used.
Word 29, bits 12-IS Fotmat Version: This field is filled with
1's to identify the 32/64
word format. The billing system must then
look to Word 0
bits 0-
,
3 to determine the type of call record
used.
Word 30, bits 0-15 Throttle Count: Used to record the number
Word 31 of CDRs that were not
bits 0-15
) written during the time that CDR throttling
was invoked. Used in
SER 8.
592
SUBSTITUTE SHEET (RULE 26)
CA 02279845 1999-OS-17
DEMANDES OU BREVETS VOLUMiNEUX
LJ4 PRESENTS PARTIE DE CETTE DEMAnJDE OU CE BREVET
COMPREND PLUS D'UN TOME.
CECI EST LE TOME ~ DE z-
NOTE: Pour les tomes additionels, veuiitez cantacter ie Bureau canadien des
brevets
JUMBO APPLICATIONS/PATENTS
Tl~liS SECTION OF THE APPLlCATION/PATENT CONTAINS MORE
THAN ONE VOLUME
~ THIS IS VOLUME .~ OF
NOTE: .For additional volumes please contact'the iCanadian .Patent Office
