Port3101.org : Your BES Connection

Port3101.org : Your BES Connection (http://www.port3101.org/index.php)
-   Featured BlackBerry KB Articles (http://www.port3101.org/forumdisplay.php?f=3)
-   -   KB11552 - What is PIN SMS and phone call log file data (http://www.port3101.org/showthread.php?t=618)

hdawg 02-19-2009 08:09 AM

KB11552 - What is PIN SMS and phone call log file data
 
KB11552 - What is PIN SMS and phone call log file data

Environment


<content>
  • BlackBerry® Enterprise Server software version 4.1
  • BlackBerry smartphones
  • SDR85594
</content>
<hr class="section">
Overview

Logs containing data from saved personal identification number (PIN) messages, short message service (SMS) messages, and calls can be turned on for auditing purposes. You can use these logs to view details for PIN, SMS, and call transactions that are sent to and from a BlackBerry smartphone. Logs are saved as comma separated values (CSV) files and named <message_type>Log_<YYYYMMDD>.CSV.
Refer to the following list of requirements for the logging feature:
  • On BlackBerry smartphones, wireless synchronization must be turned on and valid [SYNC] service books must exist.
  • On the BlackBerry Enterprise Server, wireless backup and restore must be turned on and the BlackBerry Synchronization Service must be running.
  • Wireless synchronization must be turned on for PIN messages, SMS messages, and phone call logs.
Descriptions of PIN Fields
The following table lists fields in the PINLog file and their descriptions.
<table class="borders" style="border-collapse: collapse;"> <tbody> <tr> <td class="Header" style="vertical-align: top;">Column Name</td> <td class="Header" style="vertical-align: top;">Description</td> </tr> <tr> <td style="vertical-align: top;"> Name.ID
where Name corresponds to the Name column in BlackBerry Manager and Name.ID corresponds to the format used in Backup Connector (CBCK) logs to identify the BlackBerry smartphone user.
</td> <td style="vertical-align: top;">The BlackBerry smartphone user who is sending or receiving the PIN message.</td> </tr> <tr> <td style="vertical-align: top;">PIN</td> <td style="vertical-align: top;">The BlackBerry smartphone PIN.</td> </tr> <tr> <td style="vertical-align: top;">Email Address</td> <td style="vertical-align: top;">The BlackBerry smartphone user's Simple Mail Transfer Protocol (SMTP) email address.</td> </tr> <tr> <td style="vertical-align: top;">Type of Message</td> <td style="vertical-align: top;">Incoming or outgoing PIN message type.</td> </tr> <tr> <td style="vertical-align: top;"> To
Multiple recipients are listed and separated by semi-colons (;).
Note: If the recipient's PIN exists on a BlackBerry Enterprise Server instance that points to the same SQL database as the the sender's PIN, the display name appears as Display Name:PIN. Otherwise, no name appears.
</td> <td style="vertical-align: top;">The BlackBerry smartphone PINs to which the PIN message is sent.</td> </tr> <tr> <td style="vertical-align: top;"> CC
Multiple recipients are listed and separated by semi-colons (;).
Note: If the recipient's PIN exists on a BlackBerry Enterprise Server instance that points to the same SQL database as the the sender's PIN, the display name appears as Display Name:PIN. Otherwise, no name appears.
</td> <td style="vertical-align: top;">The BlackBerry smartphone PINs to which the PIN message carbon copy is sent.</td> </tr> <tr> <td style="vertical-align: top;"> BCC
Multiple recipients are listed and separated by semi-colons (;).
Note: If the recipient's PIN exists on a BlackBerry Enterprise Server instance that points to the same SQL database as the the sender's PIN, the display name appears as Display Name:PIN. Otherwise, no name appears.
</td> <td style="vertical-align: top;">The BlackBerry smartphone PINs to which the PIN message blind carbon copy is sent.</td> </tr> <tr> <td style="vertical-align: top;">From</td> <td style="vertical-align: top;">The name of the BlackBerry smartphone user and the PIN of the BlackBerry smartphone from which the PIN message is sent.</td> </tr> <tr> <td style="vertical-align: top;">Subject</td> <td style="vertical-align: top;">The PIN message subject.</td> </tr> <tr> <td style="vertical-align: top;">Body</td> <td style="vertical-align: top;">The PIN message body.</td> </tr> <tr> <td style="vertical-align: top;"> Send/Received Date
Appears in the format YYYY/MM/DD HH:MM:SS
</td> <td style="vertical-align: top;">The PIN message transmission date and time.</td> </tr> <tr> <td style="vertical-align: top;"> Server Log Date
Appears in the format YYYY/MM/DD HH:MM:SS
</td> <td style="vertical-align: top;">The log record date and time.</td> </tr> <tr> <td style="vertical-align: top;">Command</td> <td style="vertical-align: top;">An Add, Update, or Replace request for the PIN message.</td> </tr> <tr> <td style="vertical-align: top;">UID</td> <td style="vertical-align: top;">The log record's unique identifier, used to cross-reference to CBCK logs and for debugging.</td> </tr> </tbody> </table>



<hr> Descriptions of SMS Fields
The following table lists fields in the SMSLog file and their descriptions.
<table class="borders" style="border-collapse: collapse;"> <tbody> <tr> <td class="Header" style="vertical-align: top;"> Column Name</td> <td class="Header" style="vertical-align: top;">Description</td> </tr> <tr> <td style="vertical-align: top;"> Name.ID
where Name corresponds to the Name column in BlackBerry Manager and Name.ID corresponds to the format used in CBCK logs to identify the BlackBerry smartphone user.
</td> <td style="vertical-align: top;">The BlackBerry smartphone user who is sending or receiving the SMS message.</td> </tr> <tr> <td style="vertical-align: top;">Email Address</td> <td style="vertical-align: top;">The BlackBerry smartphone user's email address.</td> </tr> <tr> <td style="vertical-align: top;">Type of Message</td> <td style="vertical-align: top;">Incoming or outgoing SMS message type.</td> </tr> <tr> <td style="vertical-align: top;"> To
Multiple recipients are listed and separated by semi-colons (;).
</td> <td style="vertical-align: top;"> The phone numbers to which outgoing SMS messages are sent or the email addresses to which they are sent (for BlackBerry smartphones on the Code Division Multiple Access (CDMA) network).
Note: This field is empty for incoming SMS messages.
</td> </tr> <tr> <td style="vertical-align: top;">From</td> <td style="vertical-align: top;"> The phone number of the BlackBerry smartphone from which the SMS message is sent.
Note: This field is empty for outgoing SMS messages.
</td> </tr> <tr> <td style="vertical-align: top;">Callback Phone Number</td> <td style="vertical-align: top;"> The phone number of the BlackBerry smartphone from which the SMS message is sent (only for BlackBerry smartphones on the CDMA network).
Note: This field is empty for outgoing SMS messages.
</td> </tr> <tr> <td style="vertical-align: top;">Body</td> <td style="vertical-align: top;">The SMS message body.</td> </tr> <tr> <td style="vertical-align: top;"> Send/Received Date
Appears in the format YYYY/MM/DD HH:MM:SS
</td> <td style="vertical-align: top;">The SMS message transmission date and time.</td> </tr> <tr> <td style="vertical-align: top;"> Server Log Date
Appears in the format YYYY/MM/DD HH:MM:SS
</td> <td style="vertical-align: top;">The log record date and time.</td> </tr> <tr> <td style="vertical-align: top;">Command</td> <td style="vertical-align: top;">An Add, Update, or Replace request for the SMS message.</td> </tr> <tr> <td style="vertical-align: top;">UID</td> <td style="vertical-align: top;">The log record's unique identifier, used to cross-reference to CBCK logs and for debugging.</td> </tr> <tr> <td style="vertical-align: top;">Overall Message Status</td> <td style="vertical-align: top;">This status displays the status of the SMS message. It indicates whether the SMS message was sent (Tx_Sent), received (Rx_Received), or if a transmission (Tx_Error) error occurred.</td> </tr> </tbody> </table>



<hr> Descriptions of Phone Call Fields
The following table lists fields in the PhoneCallLog file and their descriptions.
<table class="borders" style="width: 100%; border-collapse: collapse;"> <tbody> <tr> <td class="Header" style="vertical-align: top;">Column Name</td> <td class="Header" style="vertical-align: top;">Description</td> </tr> <tr> <td style="vertical-align: top;"> Name.ID
where Name corresponds to the Name column in BlackBerry Manager and Name.ID corresponds to the format used in CBCK logs to identify the BlackBerry smartphone user.
</td> <td style="vertical-align: top;">The BlackBerry smartphone user who is placing or receiving the call.</td> </tr> <tr> <td style="vertical-align: top;">Type of Call</td> <td style="vertical-align: top;"> Incoming or outgoing call.
The following are types of incoming calls:
  • Completed
  • Missed Call, Unopened
  • Missed Call, Opened
  • Received but Unhandled (for BlackBerry smartphones with Nextel® Direct Connect® only)
  • Handled (for BlackBerry smartphones with Nextel Direct Connect only)
</td> </tr> <tr> <td style="vertical-align: top;"> Name
where Name corresponds to the phone number in the Address Book of the BlackBerry smartphone.
</td> <td style="vertical-align: top;">The name of the BlackBerry smartphone user placing an incoming call or the name of the BlackBerry smartphone user receiving an outgoing call. Note: This field is empty for outgoing calls if the phone number is manually entered.
</td> </tr> <tr> <td style="vertical-align: top;">Phone Number</td> <td style="vertical-align: top;">The phone number of the BlackBerry smartphone user placing an incoming call or the phone number of the BlackBerry smartphone user receiving an outgoing call.</td> </tr> <tr> <td style="vertical-align: top;"> Start Date
Appears in the format YYYY/MM/DD HH:MM:SS
</td> <td style="vertical-align: top;">The date and time, in Greenwich Mean Time (GMT), at which a call is placed or received on the BlackBerry smartphone.</td> </tr> <tr> <td style="vertical-align: top;"> Server Log Date
Appears in the format YYYY/MM/DD HH:MM:SS
</td> <td style="vertical-align: top;">The log record date and time.</td> </tr> <tr> <td style="vertical-align: top;"> Elapsed Time
Appears in the format HH:MM:SS
</td> <td style="vertical-align: top;">The elapsed time of the call.</td> </tr> <tr> <td style="vertical-align: top;"> Memo
</td> <td style="vertical-align: top;">Any notes associated with the Call Log.</td> </tr> <tr> <td style="vertical-align: top;">Command</td> <td style="vertical-align: top;">An Add, Update, or Replace request for the call.</td> </tr> <tr> <td style="vertical-align: top;">UID</td> <td style="vertical-align: top;">The log record's unique identifier, used to cross-reference to CBCK logs and for debugging.</td> </tr> </tbody> </table>

vkdabies 02-24-2009 09:44 PM

Hi Mr. E,

How do I enable the logs to audit Phone calls/SMS/PIN messages from my internal BES users?

I'm looking at the Blackberry Server Config Panel but I'm not seeing it there...maybe something I'm not seeing...I have BES 4.1.4.16 integrated with Novell GroupWise 7.0.3 and there are two BES servers with a total of 540 users...

Cheese Sammich 02-25-2009 07:04 AM

Quote:

Originally Posted by vkdabies (Post 4825)
Hi Mr. E,

How do I enable the logs to audit Phone calls/SMS/PIN messages from my internal BES users?

I'm looking at the Blackberry Server Config Panel but I'm not seeing it there...maybe something I'm not seeing...I have BES 4.1.4.16 integrated with Novell GroupWise 7.0.3 and there are two BES servers with a total of 540 users...

These are options that you'd set in the IT Policy level.
The IT Policy settings are:

PIM Sync Policy Group > Disable PIN Messages Wireless Sync = False (Setting to False will ENABLE logging.)

Repeat above for SMS messages and Call Logs.

hdawg 02-25-2009 08:13 AM

FYI: By default phone call logging is enabled

tincho 01-21-2011 05:34 PM

Hi

Can anyone explain me whats the meaning of the "Command" header (Add, Update or Replace) in the phonecalllog?

THX


All times are GMT -4. The time now is 03:17 AM.

Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2019, vBulletin Solutions, Inc.


SEO by vBSEO 3.3.2 PL2