Like any other email client, Email Notification uses the From field to identify the person that left the
message being delivered. In the email message, the data in the From field is formatted as
Name
[Reply To]
, where:
•
Name
identifies the person that left the message.
•
Reply To
3
is the email address used when the email recipient replies to the message.
This information is not provided in the recipient’s inbox – just the actual email message.
For messages left by
Intercom
callers:
•
Name
is:
- The extension name (if programmed).
-
OR
-
- The extension number (if there is no name programmed).
•
Reply To
4
is:
- The email address of the person that left the message (if programmed).
-
OR
-
- The
Reply To Email Address
data from Program 47-18-09.
-
OR
-
- The
Send From Email Address
data from Program 47-18-09.
For messages left by
Outside
callers:
•
Name
is always the text “Outside Caller”.
•
Reply To
4
is:
- The
Reply To Email Address
data from Program 47-18-09.
-
OR
-
- The
Send From Email Address
data from Program 47-18-09.
SMS Text Message Delivery to a Cell Phone
The table below shows the basic format of a InMail email notification delivered to a cell phone as an
SMS Text Message. The information is much the same as that delivered to an email account. There
may be more than one text message for each notification, depending on the number of characters the
provider allows in each text message (typically 120-160 characters). SMS will not send the wav file
attachment, even if enabled in programming.
An extension set up for notification via SMS Text Messaging should have the
Email Message as Attachment option disabled in system programming. Attempt-
ing to deliver a wav file attachment to an SMS messaging service may have
undesirable results.
•
SMS Text Message Notification
The following shows a typical SMS Text Message when the InMail is set up to provide email notifica-
tion only (no wav file of the actual message). In this case, the provider divided the message into two
parts: one for the message header and one for the message body. This is only an example – your
provider may handle similar content differently.
Table 1-21 Typical SMS Notification (No Wav File)
Description
Text
Text Message for Message Header
Text Message Inbox:
InMail [2 OF 2]
Text Message Body:
*1
MESSAGE FROM: InMail [2 OF 2]
SENT: 3:51PM 9/17
*1. Your cell phone display will automatically break the text lines to best fit the screen.
ISSUE 1.0
SL1000
I
Features and Specifications Manual
1-277
Summary of Contents for SL1000
Page 1: ...Features and Specifications Manual A50 031169 001 ISSUE 1 0 January 2011 ...
Page 41: ...Operation None ISSUE 1 0 SL1000 A Features and Specifications Manual 1 33 ...
Page 57: ...Operation None ISSUE 1 0 SL1000 B Features and Specifications Manual 1 49 ...
Page 95: ...Operation None ISSUE 1 0 SL1000 C Features and Specifications Manual 1 87 ...
Page 154: ...Operation None ISSUE 1 0 SL1000 D Data Line Security 1 146 ...
Page 324: ...Operation LCR Operation Flow Diagram ISSUE 1 0 SL1000 L LCR Least Cost Routing 1 316 ...
Page 325: ...LCR Dial LCR Dial Editing ISSUE 1 0 SL1000 L Features and Specifications Manual 1 317 ...
Page 326: ...LCR Cost Centre Code ISSUE 1 0 SL1000 L LCR Least Cost Routing 1 318 ...
Page 586: ...Memo ISSUE 1 0 SL1000 Features Availability by Software Revision 3 6 ...
Page 587: ...Memo ISSUE 1 0 SL1000 Features and Specifications Manual 3 7 ...
Page 588: ...Features and Specifications Manual NEC Corporation ISSUE 1 0 ...