User Manual
Table Of Contents
- Access Server
- Table of Contents
- List of Tables
- Chapter 1. Introduction to Access Server
- Chapter 2. Getting Started with Access Server
- Chapter 3. Using the System
- 3.1. Network Interfaces
- 3.2. Bluetooth
- 3.3. Compact Flash Cards
- 3.4. USB Memory Dongles and Compact Flash Memory Cards
- 3.5. Servers
- 3.5.1. Finder
- 3.5.2. ObexSender
- 3.5.3. SMS Gateway Server
- 3.5.4. User Level Watchdog
- 3.5.5. Remote Management
- 3.5.5.1. Overview
- 3.5.5.2. Management Packet Format
- 3.5.5.3. Management Packet Information File Format
- 3.5.5.4. Management Operation Example: Hello World
- 3.5.5.5. Management Operation Example: Software Update
- 3.5.5.6. Management Operation Example: IPQUERY
- 3.5.5.7. Management with USB Memory Dongle or Compact Flash Memory Card
- 3.5.6. FTP
- 3.5.7. Web Server
- 3.5.8. SNMP
- 3.5.9. OpenVPN
- 3.5.10. SSH
- 3.5.11. Telnet
- 3.5.12. NTP
- 3.6. Utilities
- 3.7. Real Time Clock
- 3.8. Time Zone
- 3.9. System ReInstall and Upgrade
- Chapter 4. SPPoverIP
- Chapter 5. Obexsender
- Chapter 6. Software Development Kit
- 6.1. Introduction to SDK
- 6.2. Installing SDK
- 6.3. Creating Applications
- Chapter 7. iWRAP Bluetooth Interface
- 7.1. Terms
- 7.2. Starting the iWRAP Servers
- 7.3. Writing iWRAP Applications
- 7.4. Commands Controlling iWRAP
- INFO
- QUIT
- SET
- SAVE
- LOAD
- PING
- PONG
- ECHO
- LOCK
- UNLOCK
- SHUTDOWN
- SLEEP
- 7.5. Finding Bluetooth Devices
- INQUIRY
- NAME
- 7.6. Making a Bluetooth Connection
- CALL
- CONNECT
- NO CARRIER
- RING
- RINGING
- CLOSE
- LIST
- STATUS
- 7.7. Service Discovery
- SDPSEARCH
- SDPATTR
- SDPQUERY
- SDP bdaddr
- SDP ADD
- SDP DEL
- SDP LIST
- 7.8. Example Sessions
- 7.9. Error Codes
- Chapter 8. I/O API
- Chapter 9. Advanced Use Cases for Access Server
- Chapter 10. Certification Information and WEEE Compliance
- Appendix A. Directory Structure
- Appendix B. Setup Options
- Appendix C. Open Source Software Licenses
- Appendix D. Supported Hardware
Chapter 5. Obexsender
5.3.7. How to Store Files Sent to Access Server
By default, all files sent over Object Push to Access Server are stored to the /tmp/obex folder
and deleted after they have been processed. It is however possible to save the files to another
directory. The following procedure shows how to automatically copy these files to an example
folder /usr/local/remote_request. (NOTE: you must first create this folder!):
1. Create a copier script /usr/local/bin/copier. You can do it for example in the
WWW setup -> Advanced settings -> Edit other configuration files and typing here
/usr/local/bin/copier. Put the following script into the file:
#!/bin/sh
# to be called from obexsender: --fork /usr/local/bin/copier
# This directory must exist:
SAVEDIR="/usr/local/remote_request"
/bin/cp "$1" "${SAVEDIR}/$3‘/bin/date "+%s"‘-‘echo $1 | /usr/bin/cut -f 2 -d-‘"
2. Make the script executable by giving command chmod a+rx /usr/local/bin/copier at the
command line interface.
3. Edit /etc/bluetooth.conf and append to the end of the file the following line (below the
line is in two parts, combine these in the configuration file):
SET BLUETOOTH LISTEN 3 "/usr/sbin/obexserver --bdaddr $b --prefix $b-$P-
--fork /usr/local/bin/copier" 110
4. Save changes and restart Access Server.
Now all incoming files are copied to the /usr/local/remote_request directory. The format of
the files is bdaddr-btserverport-timestamp-filename.ext.
5.4. Monitoring Obexsender
Obexsender creates log about its operation to a specified log file. By default, no log file is speci-
fied, so you should do this first with instructions provided in Section 5.3.4.
When you choose View log in the Obexsender menu, you can only see the summary of
Obexsender action, i.e how many successes, failures and retries have occurred. When you
select the date or Total in the summary view, you will see more details. You will see to which
Bluetooth address the content was sent and if the transmission was a failure or success, or if
transmission will be retried later. See some example logging in the figure below:
57