Chapter 8. Advanced Use Cases for Access Server

This chapter will give you advanced use cases for Access Server. The cases listed here are not so trivial, the simple cases are already listed mostly in Chapter 6.

8.1. Making Access Server Secure

TBA

8.2. Digital Pen

Access Server will support most of the digital pens. The examples below are for Nokia Digital Pen SU-1B but they should apply to other pens too.

To setup Access Server for digital pens you have to give following iWRAP commands. The best way to do this is to edit /etc/bluetooth.conf file from the command prompt or with the setup application.


      # Emulate a phone
      SET BLUETOOTH CLASS 500204
      SET BLUETOOTH LISTEN 1 "*/usr/sbin/dun"
      SDP ADD DUN 1 "Digital Pen DUN"
      # Add two pens and their pin codes
      SET BLUETOOTH AUTH 00:07:cf:51:f6:8e 9079 --REPLY
      SET BLUETOOTH AUTH 00:07:cf:51:d5:2b 6603 --REPLY
      # Note: See pen's manual for correct bluetooth address and pin code
      # Optionally reject all other incoming connections
      SET BLUETOOTH AUTH * - --NEWPAIR
    

After these settings you can pair and use the digital pen with Access Server just like you would use it with a phone. Both modes, receiving pictures to Access Server, and external server via dialup, are supported.

8.3. SPP to Socket

Access Server can automatically forward an incoming connection to an external server via TCP/IP. This is mostly used to forward incoming SPP connections, but is not limited to that.

To setup Access Server to do this you have to give following iWRAP commands. The best way to do this is to edit /etc/bluetooth.conf file from the command prompt or with the setup application.


      # Forward incoming connection to IP 192.168.42.99 socket 7444
      SET BLUETOOTH LISTEN 1 192.168.42.99:7444
      # Add SDP record for SPP
      SDP ADD SPP 1 "SPP to External Server"
    

In addition to those commands you have to disable Serial Port Profile from the setup application. For more information see Section 2.4.

After these settings all incoming RFCOMM connections to channel 1 (SPP) will be forwarded to IP 192.168.42.99 socket 7444 using TCP connection.