btsrv.conf.in

Affix - Bluetooth Protocol Stack for Linux has been developed at Nokia Research Center in Helsinki

#
# $Id: btsrv.conf.in,v 1.12 2003/12/11 16:50:56 kds Exp $
#
# btsrv configuration file.
#
# Some options:
#
# flags		- Can be one of the following:
#		    socket - execute the command with the RFCOMM socket
#	            tty -    execute the command with the /dev/bty device
#		    std    - connects socket/bty to stdin and stdout
#
# exec		- Command to execute with the new RFCOMM socket or the bty virtual
#		    serial device on its standard input and output.
#		    Possible parameters to the command:
#			%i = connection identifier
#	  		%l = tty line number if virtual serial device is used,
#				-1 if RFCOMM socket is used
#			%a = bluetooth address of the connecting device
#			%c = RFCOMM server channel
#

# General server options

# Initialize device (/etc/affix/affix does it as well)
initdev		no
# start services
startsvc	yes
# manage PIN
managepin	yes
# store and use link keys for authentication
managekey	yes

# Services
<service SerialPort>
	# activate a service
	active		yes
	
	# SDP service name/provider/description attributes
	name		"Serial Port";
	#provider 	"Nokia Research Center";
	#descript 	"Serial Port Profile";
	
	# security levels (service level)
	# security	open, auth, author, encrypt;
	# open	- no security
	# auth	- require authenticaion to access service
	security	open
	
	# service class: service1, ...
	#class		information networking;

	flags		tty;
	exec		"/etc/affix/serial %l %i %a %c";
</service>

<service DialupNetworking>
	active		yes
	name		"Dialup Networking";
	security	auth;
	flags		tty,std;
	exec		"@prefix@/bin/btmodem -l -q -b /dev/bty%l -m /dev/ttyS0";
</service>

<service DialupNetworking>
	active		yes
	name		"Dialup Networking Emulation";
	security	auth;
	flags		tty,std;
	exec		"@prefix@/bin/btmodem -e;/etc/affix/ppp_server connid %i masquerade";
</service>

<service Fax>
	active		yes
	name		"Fax Service";
	security	auth;
	class		telephony;
	flags		tty;
	exec		"@prefix@/bin/btmodem -l -q -b /dev/bty%l -m /dev/ttyS0";
</service>

<service LANAccess>
	active		yes
	name		"LAN Access";
	security	auth;
	flags		tty,std;
	exec		"/etc/affix/ppp_server connid %i masquerade";
</service>

<service OBEXFileTransfer>
	active		yes
	name		"OBEX File Transfer";
	security	auth;
	flags		socket,std;
	exec		"@prefix@/bin/btobex";
</service>

<service OBEXObjectPush>
	active		yes
	name		"OBEX Object Push";
	security	auth;
	flags		socket,std;
	exec		"@prefix@/bin/btobex";
</service>

<service PANNap>
	active		yes
	name		"PAN NAP";
	security	auth;
	exec		"";
</service>

<service Headset>
	active		yes
	name		"Headset";
	security	open;
	flags		tty;
	exec		"/etc/affix/serial %l %i %a %c";
</service>

<service HeadsetAG>
	active		yes
	name		"HeadsetAG";
	security	open;
	flags		tty;
	exec		"/etc/affix/serial %l %i %a %c";
</service>

<service HandsFree>
	active		yes
	name		"HandsFree";
	security	open;
	flags		tty;
	exec		"/etc/affix/serial %l %i %a %c";
</service>

<service HandsFreeAG>
	active		yes
	name		"HandsFreeAG";
	security	open;
	flags		tty;
	exec		"/etc/affix/serial %l %i %a %c";
</service>

# default device params. should come before named sections
#<device *>
#</device>

<device bt0>
	# device public bluetooth name
	#name	"Selma"
	
	# device class  major, minor, service1, ...
	class		computer hand, information, audio, networking, transfer;

	# scan: disc - discoverable, conn - connactible
	scan		disc, conn
	
	# securyty mode
	# open	- no security
	# link	- link level security
	# 	auth - authentication enabled
	# 	encrypt - encryption enabled
	# service - service level security
	security 	service pair #auth , encrypt
	
	# connection role - switching options
	# allow | deny 		- allow or deny role switching
	# slave | master 	- accept role: remain slave or become a master
	role		allow, slave

	pkt_type	DM1, DH1, DM3, DH3, DM5, DH5, HV1

</device>