Re: [RFR] templates://isdnutils/{ipppd.templates,isdnlog.templates,isdnutils-b ase.templates,isdnvboxserver.templates}
Christian Perrier wrote:
> Preamble: I *did not* review debian/control for this package. [...]
Okay, I'll keep my hands off the package descriptions too. They
aren't great, but they're intelligible.
> Template: ipppd/ispphone
[...]
> At least one phone number has to be dialed in order to connect
> - to your Internet service provider (ISP).
> + to the Internet service provider (ISP).
That makes it sound as if there's only one ISP in the world. It's
hard to avoid "your" here... but I suppose in this particular case
we could make it "to _an_ ISP".
> Template: ipppd/isplogin
[...]
> +_Description: ISP user name:
> + Most ISPs require a user name and password to be provided when
> + connecting.
The terminology I'm used to here is "account name" (it's definitely
not the name of the user).
> Template: ipppd/isppasswd
[...]
> +_Description: ISP password:
> + Please enter the password to use when connecting to the ISP. This password
> + will be kept in /etc/ppp/pap-secrets and
> + /etc/ppp/chap-secrets together along with the username.
together with the account name.
"Together with" or "along with", not "together along with".
> --- isdnutils.old/debian/isdnlog.templates 2009-09-18 18:26:24.672339165 +0200
> +++ isdnutils/debian/isdnlog.templates 2009-09-18 19:02:09.349343195 +0200
> @@ -1,52 +1,54 @@
> Template: isdnlog/country
[...]
> + Please choose the local country. This will be used to set the rate table to
> + use for calculating the calls costs
This makes me think "but didn't I tell my computer this about ten
seconds after I inserted the debian-installer CD?", but never mind.
> Template: isdnlog/isdnrate-daemon
[...]
> + This setting is only useful for people with special requirements, such as those using the
> + isdn2h323 package.
There is no isdn2h323 package - debian-legal decided it was
undistributable (GPL with extra restrictions). We could say:
This setting is only useful for special setups, such as for an
ISDN-to-H.323 gateway.
> _Description: Firmware to load:
> + Some ISDN cards can't function properly until some firmware has been
> + loaded. A notable example is the Sedlbauer SpeedFax+ PCI or Siemens
> I-Surf, which need ISAR.BIN to be loaded. Choose "ISAR.BIN" if this is
> + necessary.
That's two: "Notable examples are the Sedlbauer SpeedFax+ PCI and
Siemens I-Surf, which need [...]"
> Template: isdnutils/firmwarecards
[...]
> + If you use more than one card, enter the number of the card(s) that need
> + the firmware to be loaded.
There are verb agreement issues lurking in this sentence ("the card
or cards that needs or need the firmware"); I'd like to avoid the
issue by saying "the card(s) in need of firmware".
> Template: isdnvboxserver/user
[...]
> +_Description: Login for the answering machine:
> + When clients (using the vbox program provided by the isdnvboxclient
> + package) connect to the answering machine, they will be prompted with a
> + user name and password.
> + .
> + The user name you define here does not have to be a user on the
> + system itself.
Make that:
Connections to the answering machine (using the vbox program provided
by the isdnvboxclient package) will be prompted for a username and
password.
.
The username you define here does not have to correspond to a login
account on this system.
> Template: isdnvboxserver/vboxnodir
> Type: error
> _Description: No home directory
> - The home directory `${DIR}' for user `${USER}' doesn't exist. This means
> + The home directory `${DIR}' for user `${USER}' does not exist. This means
> that the file `${DIR}/.vbox.conf' cannot be created.
Does it really mean ${USER} here and below and not ${User}? Is it
always going to be "root" or does it redefine it?
I'll stick to standardising quotes: "", not `'.
> Template: isdnvboxserver/doinit
> Type: error
> _Description: Device in inittab doesn't agree with devfs mode
> The entry for vboxgetty in /etc/inittab uses a device name that does not
> correspond to the current devfs usage; either a devfs (/dev/isdn/ttyIxx)
> name is used in inittab while devfs is not mounted, or the non-devfs name
> is used while devfs is mounted.
"Current devfs usage"?
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
diff -ru isdnutils-3.9.20060704.pristine/debian/ipppd.templates isdnutils-3.9.20060704/debian/ipppd.templates
--- isdnutils-3.9.20060704.pristine/debian/ipppd.templates 2009-09-19 12:52:20.000000000 +0100
+++ isdnutils-3.9.20060704/debian/ipppd.templates 2009-09-22 09:52:28.000000000 +0100
@@ -1,47 +1,44 @@
Template: ipppd/ispwontdoit
Type: error
-_Description: ISP dialup config already exists
- The files device.${IPPP0} and ipppd.${IPPP0} already exist. Therefore the
+_Description: ISP dialup configuration already exists
+ The device.${IPPP0} and ipppd.${IPPP0} files already exist. Therefore, the
ipppd configuration phase won't touch anything there, as it looks like
- it's already been configured.
+ it has already been configured.
.
If it doesn't work yet, and you want to try the automatic configuration,
stop all ISDN processes (use "/etc/init.d/isdnutils stop"), remove the
files mentioned above, and rerun the configuration with "dpkg-reconfigure
- ipppd". After that, restart the ISDN processes: "/etc/init.d/isdnutils
+ ipppd". After that, restart the ISDN processes with "/etc/init.d/isdnutils
start".
Template: ipppd/whichif
Type: string
Default: ippp0
_Description: Interface to configure:
- Most people should say "ippp0" here, as that is the default for a connection
- to an ISP. The default gateway will be ippp0.
+ The default setting should be safe for most configurations.
.
- However, some people have special requirements, and they may choose
- another interface that will be configured (e.g. because they don't
- want this connection to be the default gateway).
+ However, if you have special requirements or want to choose
+ to configure another interface, please enter it here.
.
- Note that currently at most one interface can be configured in this manner.
- Leave the field blank if you do not want to configure anything now for ipppd.
+ Leave the field blank if you do not want to configure anything now.
Template: ipppd/wrongif
Type: error
-_Description: Wrong interface name
- You can only give names starting with "ippp" followed by a number between
+_Description: Invalid interface name
+ Valid interface names begin with "ippp" followed by a number between
0 and 63.
Template: ipppd/ispphone
Type: string
Default: manual
-_Description: What is your ISP's telephone number?
+_Description: ISP's telephone number:
At least one phone number has to be dialed in order to connect
- to your Internet service provider (ISP).
+ to an Internet service provider (ISP).
.
- Enter the telephone number here, including dialing prefixes,
+ Please enter that telephone number here, including dialing prefixes,
area codes, and so on, but without any spaces.
.
- You can enter multiple telephone numbers, separated by spaces.
+ Multiple telephone numbers may be entered and should be separated by spaces.
.
Leave the field blank if you want to configure the connection manually.
@@ -62,22 +59,22 @@
Template: ipppd/isplogin
Type: string
-_Description: User name for logging into your ISP:
- Most ISPs need a user name and password for authenticating you as a
- valid user before allowing access. Enter the user name here. The password
- will be asked for next.
+_Description: ISP account name:
+ Most ISPs require an account name and password to be provided when
+ connecting.
Template: ipppd/isppasswd
Type: password
-_Description: Password for logging into your ISP:
- The password you give here will be entered into /etc/ppp/pap-secrets and
- /etc/ppp/chap-secrets together with the username.
+_Description: ISP password:
+ Please enter the password to use when connecting to the ISP. This password
+ will be kept in /etc/ppp/pap-secrets and
+ /etc/ppp/chap-secrets together with the account name.
Template: ipppd/isploginpapalreadythere
Type: error
_Description: ISP user name already in pap-secrets
The user name you entered for logging into your ISP is already listed in
- the /etc/ppp/pap-secrets file. That's not a problem; the existing entry
+ the /etc/ppp/pap-secrets file. The existing entry
will be commented out, and a new entry with the data you just entered will
be inserted.
@@ -85,7 +82,7 @@
Type: error
_Description: ISP user name already in chap-secrets
The user name you entered for logging into your ISP is already listed in
- the /etc/ppp/chap-secrets file. That's not a problem; the existing entry
+ the /etc/ppp/chap-secrets file. The existing entry
will be commented out, and a new entry with the data you just entered will
be inserted.
@@ -93,8 +90,8 @@
Type: error
_Description: ISP user name already in chap-secrets and pap-secrets
The user name you entered for logging into your ISP is already listed in
- the chap-secrets and pap-secrets files in /etc/ppp/. That's not a problem;
- the existing entries will be commented out, and new entries with the data
+ the chap-secrets and pap-secrets files in /etc/ppp/.
+ The existing entries will be commented out, and new entries with the data
you just entered will be inserted.
Template: ipppd/oldipup
@@ -131,7 +128,7 @@
Template: ipppd/noisdnutilsinit
Type: error
_Description: (Re)start ipppd manually
- There is no /etc/init.d/isdnutils on your system; hence you will have to
+ There is no /etc/init.d/isdnutils on this system; hence you will have to
stop and start any ipppd daemons manually.
Template: ipppd/isdnutilsinitbad
diff -ru isdnutils-3.9.20060704.pristine/debian/isdnlog.templates isdnutils-3.9.20060704/debian/isdnlog.templates
--- isdnutils-3.9.20060704.pristine/debian/isdnlog.templates 2009-09-19 12:52:20.000000000 +0100
+++ isdnutils-3.9.20060704/debian/isdnlog.templates 2009-09-22 09:53:27.000000000 +0100
@@ -1,52 +1,54 @@
Template: isdnlog/country
Type: select
#flag:translate:9
-__Choices: AT, CH, DE, ES, FR, LU, NL, NO, other
-# Translators: If your 2-letter code country is in the following list:
-# "AT, CH, DE, ES, FR, LU, NL, NO"
-# translate this string by this code. Otherwise, just write "other" (but
-# do not translate it).
-_Default: other[ default country]
+Choices-C: AT, FR, DE, LU, NL, NO, ES, CH, other
+__Choices: Austria, France, Germany, Luxemburg, Netherlands, Norway, Spain, Switzerland, other
+# Translators:
+# Please choose among
+# "Austria, France, Germany, Luxemburg, Netherlands, Norway, Spain, Switzerland, other"
+_DefaultChoice: other
_Description: Country:
- This is used for setting a number of defaults, e.g. what rate tables to
- use for calculating the cost of a call.
+ Please choose the local country. This will be used to set the rate table to
+ use for calculating the calls costs
Template: isdnlog/country_manual
Type: string
-_Description: ISO two-letter code for your country:
- This can't really be used for setting any defaults, but maybe some day...
- .
- Note that you will probably have to edit /etc/isdn/isdn.conf before
- isdnlog will be able to work.
+Description: Country's ISO two-letter code:
+ Please enter the ISO code of the local country. As no rate
+ tables are available, this setting will be unused.
Template: isdnlog/countryprefix
Type: string
Default: +
-_Description: Prefix for international number:
+_Description: Prefix to dial before international number:
Template: isdnlog/countrycode
Type: string
Default: 49
-_Description: Code of your country:
- e.g. ${default_countrycode} for ${default_country}
+#flag:comment:3
+# Translators: do not translate ${default_countrycode} and ${default_country}
+_Description: Country ITU code:
+ Please enter the international code for the local country.
+ .
+ Example: ${default_countrycode} for ${default_country}
Template: isdnlog/areaprefix
Type: string
Default: 0
-_Description: Prefix for areacode, if applicable:
+_Description: Prefix for area code, if applicable:
Template: isdnlog/areacode
Type: string
-_Description: Local areacode, if applicable:
+_Description: Local area code, if applicable:
Template: isdnlog/isdnrate-daemon
Type: boolean
Default: false
_Description: Run isdnrate as a daemon?
- isdnrate is a utility to calculate the costs of a connection to a given
+ The isdnrate utility calculates the costs of a connection to a given
phone number, used e.g. for LCR systems to find the cheapest carrier on a
call-by-call basis. Having it run as a daemon speeds things up as then it
only has to load all the data once.
.
- This is only for people with special requirements, such as those using the
- isdn2h323 package. Hence most people should not choose this option.
+ This setting is only useful for special setups, such as for an
+ ISDN-to-H.323 gateway.
diff -ru isdnutils-3.9.20060704.pristine/debian/isdnutils-base.templates isdnutils-3.9.20060704/debian/isdnutils-base.templates
--- isdnutils-3.9.20060704.pristine/debian/isdnutils-base.templates 2009-09-19 12:52:20.000000000 +0100
+++ isdnutils-3.9.20060704/debian/isdnutils-base.templates 2009-09-22 09:53:55.000000000 +0100
@@ -4,16 +4,16 @@
__Choices: none, ISAR.BIN
Default: none
_Description: Firmware to load:
- Some ISDN cards can't function properly until firmware has been
- downloaded. Notable example is the Sedlbauer SpeedFax+ PCI or Siemens
+ Some ISDN cards can't function properly until some firmware has been
+ loaded. A notable example is the Sedlbauer SpeedFax+ PCI or Siemens
I-Surf, which need ISAR.BIN to be loaded. Choose "ISAR.BIN" if this is
- necessary. If you don't know what to answer here, choose "none".
+ necessary.
Template: isdnutils/firmwarecards
Type: string
_Description: ISDN card numbers to load with the firmware:
- If you have more than one card, enter the number of the card(s) that have
- to be loaded with the firmware, starting with 1, separated by commas. If
- you have only one card, the obvious answer here is "1". If you have two
- cards which both have to be loaded with firmware, enter "1,2".
-
+ If you use more than one card, enter the number of the card(s) in need
+ of firmware.
+ .
+ Multiple entries should be separated by commas. Card numbers are integers
+ where "1" is the first card, "2" the second, etc.
diff -ru isdnutils-3.9.20060704.pristine/debian/isdnvboxserver.templates isdnutils-3.9.20060704/debian/isdnvboxserver.templates
--- isdnutils-3.9.20060704.pristine/debian/isdnvboxserver.templates 2009-09-19 12:52:20.000000000 +0100
+++ isdnutils-3.9.20060704/debian/isdnvboxserver.templates 2009-09-22 09:58:58.000000000 +0100
@@ -2,12 +2,12 @@
Type: string
Default: quit
_Description: Number that vbox should answer:
- Vbox must know what number to listen to. Depending on your country's ISDN
- system, this may or may not include the areacode. It is usually without
- the leading 0.
+ Vbox must know what number to listen to. Depending on the country's ISDN
+ system, this may or may not include the area code. Leading "0" should most
+ often be dropped.
.
Leave the field blank if you want to configure by hand, or if you already
- have an existing (working) vbox
+ use an existing (working) vbox
configuration from the time when this was still part of isdnutils (unless
you want to create a new configuration).
@@ -15,64 +15,69 @@
Type: string
Default: 4
_Description: Number of rings for vbox to pick up the line:
- One ring is about 5 seconds. You can fine-tune the number of rings for
- certain phonenumbers manually, e.g. any salesmen you know the number of
- (or calls without caller-ID) can be dumped into the answering machine
- after one ring. See `man vbox.conf' for more information.
+ One ring is about 5 seconds. This setting can later be fine-tuned
+ for each incoming telephone number, for instance to aggressively
+ filter some incoming numbers.
+ .
+ You should read vbox.conf(5) for more information.
Template: isdnvboxserver/attachmsg
Type: boolean
Default: true
-_Description: Should the message be attached to the email?
+_Description: Should incoming messages be attached to notification mails?
When a message is recorded, an email notification is sent. If that
email should contain the message as an attachment, choose the option.
- .
- Note: the attachment can be large.
Template: isdnvboxserver/daemonuser
Type: string
Default: vboxdaemonuser
-_Description: User who runs the answering machine:
- vboxd runs with the privileges of a normal (non-root) user. This is
- typically your non-root login name. This user must be a member of the
- `dialout' group.
+_Description: Run the answering machine as:
+ The vboxd daemon should run as an unprivileged (non-root) user. It must be
+ a member of the "dialout" group.
Template: isdnvboxserver/nosuchuser
Type: text
-_Description: User ${Daemonuser} doesn't exist on the system
- The user who runs the answering machine should be a valid user name
- on this system.
+#flag:comment:1
+# Translators, do not translate "Daemonuser"
+_Description: ${Daemonuser} unknown
+ The user you chose does not exist on this machine. You must choose
+ a valid username.
Template: isdnvboxserver/user
Type: string
-_Description: Username which may connect to the vbox server:
- To listen to messages using vbox (from the isdnvboxclient package), you
- need a username and password. Enter the username here. This does not have
- to be a user on the system itself.
+_Description: Login for the answering machine:
+ Connections to the answering machine (using the vbox program provided
+ by the isdnvboxclient package) will be prompted for a username and
+ password.
+ .
+ The username you define here does not have to correspond to a login
+ account on this system.
Template: isdnvboxserver/password
Type: password
+#flag:comment:1,1
+# Translators, do not translate "${User}"
_Description: Password for ${User}:
- Please don't use ':' in it! The way it is stored cannot handle this.
+ Please choose the password for the ${User} connection user.
Template: isdnvboxserver/vboxnodir
Type: error
_Description: No home directory
- The home directory `${DIR}' for user `${USER}' doesn't exist. This means
- that the file `${DIR}/.vbox.conf' cannot be created.
+ The home directory "${DIR}" for user "${USER}" does not exist. This means
+ that the file "${DIR}/.vbox.conf" cannot be created.
Template: isdnvboxserver/vboxnouser
Type: error
-_Description: User doesn't exist
- The user `${USER}' doesn't exist on the system. Please rerun the
- configuration with `dpkg-reconfigure isdnvboxserver' to enter another
+_Description: Non-existing user
+ The user "${USER}" doesn't exist on the system. Please rerun the
+ configuration with "dpkg-reconfigure isdnvboxserver" to enter another
username, or after creating the user.
Template: isdnvboxserver/doinit
Type: boolean
Default: true
_Description: Should vboxgetty be enabled?
- vboxgetty is in /etc/inittab, but not yet enabled. Choosing this option
+ A call for vboxgetty is defined in /etc/inittab, but not yet enabled. Choosing this option
will enable it once this package is fully configured. Refuse this option
if you want to tweak it manually.
@@ -84,7 +89,7 @@
name is used in inittab while devfs is not mounted, or the non-devfs name
is used while devfs is mounted.
.
- You will have to fix this by hand.
+ This problem has to be fixed manually.
Template: isdnvboxserver/devfs_vboxgettyconf
Type: error
@@ -94,7 +99,7 @@
(/dev/isdn/ttyIxx) name is used in vboxgetty.conf while devfs is not
mounted, or the non-devfs name is used while devfs is mounted.
.
- You will have to fix this by hand.
+ This problem has to be fixed manually.
Template: isdnvboxserver/dummy
Type: note
Template: ipppd/ispwontdoit
Type: error
_Description: ISP dialup configuration already exists
The device.${IPPP0} and ipppd.${IPPP0} files already exist. Therefore, the
ipppd configuration phase won't touch anything there, as it looks like
it has already been configured.
.
If it doesn't work yet, and you want to try the automatic configuration,
stop all ISDN processes (use "/etc/init.d/isdnutils stop"), remove the
files mentioned above, and rerun the configuration with "dpkg-reconfigure
ipppd". After that, restart the ISDN processes with "/etc/init.d/isdnutils
start".
Template: ipppd/whichif
Type: string
Default: ippp0
_Description: Interface to configure:
The default setting should be safe for most configurations.
.
However, if you have special requirements or want to choose
to configure another interface, please enter it here.
.
Leave the field blank if you do not want to configure anything now.
Template: ipppd/wrongif
Type: error
_Description: Invalid interface name
Valid interface names begin with "ippp" followed by a number between
0 and 63.
Template: ipppd/ispphone
Type: string
Default: manual
_Description: ISP's telephone number:
At least one phone number has to be dialed in order to connect
to an Internet service provider (ISP).
.
Please enter that telephone number here, including dialing prefixes,
area codes, and so on, but without any spaces.
.
Multiple telephone numbers may be entered and should be separated by spaces.
.
Leave the field blank if you want to configure the connection manually.
Template: ipppd/eaz
Type: string
Default: 0
_Description: Local MSN:
When making a call with ISDN, the MSN (phone number) that is originating
the call must be given in the call-setup message. While a wrong MSN will
usually be replaced by the main MSN for the ISDN line, especially on
PABXes, a wrong MSN (often the extension number in this case) will cause
the call-setup to fail. So, it is best to enter the correct local MSN
here.
.
This may also be necessary if you want the costs to be registered to one
particular MSN, in case you have more than one MSN and this is supported
by your telco.
Template: ipppd/isplogin
Type: string
_Description: ISP account name:
Most ISPs require an account name and password to be provided when
connecting.
Template: ipppd/isppasswd
Type: password
_Description: ISP password:
Please enter the password to use when connecting to the ISP. This password
will be kept in /etc/ppp/pap-secrets and
/etc/ppp/chap-secrets together with the account name.
Template: ipppd/isploginpapalreadythere
Type: error
_Description: ISP user name already in pap-secrets
The user name you entered for logging into your ISP is already listed in
the /etc/ppp/pap-secrets file. The existing entry
will be commented out, and a new entry with the data you just entered will
be inserted.
Template: ipppd/isploginchapalreadythere
Type: error
_Description: ISP user name already in chap-secrets
The user name you entered for logging into your ISP is already listed in
the /etc/ppp/chap-secrets file. The existing entry
will be commented out, and a new entry with the data you just entered will
be inserted.
Template: ipppd/isploginpapchapalreadythere
Type: error
_Description: ISP user name already in chap-secrets and pap-secrets
The user name you entered for logging into your ISP is already listed in
the chap-secrets and pap-secrets files in /etc/ppp/.
The existing entries will be commented out, and new entries with the data
you just entered will be inserted.
Template: ipppd/oldipup
Type: error
_Description: /etc/ppp/ip-up.d/00-isdnutils still exists
The /etc/ppp/ip-up.d/00-isdnutils file from the old isdnutils package
still exists. If you changed that file at some point, you may need to redo
those changes in the 00-ipppd file (which is the new name). After that,
please delete the old 00-isdnutils file.
.
Until it is deleted, it will still be used. This may cause conflicts.
Template: ipppd/oldipdown
Type: error
_Description: /etc/ppp/ip-down.d/99-isdnutils still exists
The /etc/ppp/ip-down.d/99-isdnutils file from the old isdnutils package
still exists. If you changed that file at some point, you may need to redo
those changes in the 99-ipppd file (which is the new name). After that,
please delete the old 99-isdnutils file.
.
Until it is deleted, it will still be used. This may cause conflicts.
Template: ipppd/oldipupdown
Type: error
_Description: old /etc/ppp/ip-up.d and ip-down.d scripts still exist
The /etc/ppp/ip-up.d/00-isdnutils and /etc/ppp/ip-down.d/99-isdnutils
files from the old isdnutils package still exist. If you changed those
files at some point, you may need to redo those changes in the 00-ipppd
and 99-ipppd files (which are the new names). After that, please delete
the old 00-isdnutils and 99-isdnutils files.
.
Until they are deleted, they will still be used. This may cause conflicts.
Template: ipppd/noisdnutilsinit
Type: error
_Description: (Re)start ipppd manually
There is no /etc/init.d/isdnutils on this system; hence you will have to
stop and start any ipppd daemons manually.
Template: ipppd/isdnutilsinitbad
Type: error
_Description: Error running isdnutils init script
The /etc/init.d/isdnutils script ran with errors. Please check the
installation of the isdnutils-base package; reinstall it if necessary.
Perhaps moving /etc/init.d/isdnutils.dpkg-dist (if it exists) to
/etc/init.d/isdnutils will also help.
Template: isdnlog/country
Type: select
#flag:translate:9
Choices-C: AT, FR, DE, LU, NL, NO, ES, CH, other
__Choices: Austria, France, Germany, Luxemburg, Netherlands, Norway, Spain, Switzerland, other
# Translators:
# Please choose among
# "Austria, France, Germany, Luxemburg, Netherlands, Norway, Spain, Switzerland, other"
_DefaultChoice: other
_Description: Country:
Please choose the local country. This will be used to set the rate table to
use for calculating the calls costs
Template: isdnlog/country_manual
Type: string
Description: Country's ISO two-letter code:
Please enter the ISO code of the local country. As no rate
tables are available, this setting will be unused.
Template: isdnlog/countryprefix
Type: string
Default: +
_Description: Prefix to dial before international number:
Template: isdnlog/countrycode
Type: string
Default: 49
#flag:comment:3
# Translators: do not translate ${default_countrycode} and ${default_country}
_Description: Country ITU code:
Please enter the international code for the local country.
.
Example: ${default_countrycode} for ${default_country}
Template: isdnlog/areaprefix
Type: string
Default: 0
_Description: Prefix for area code, if applicable:
Template: isdnlog/areacode
Type: string
_Description: Local area code, if applicable:
Template: isdnlog/isdnrate-daemon
Type: boolean
Default: false
_Description: Run isdnrate as a daemon?
The isdnrate utility calculates the costs of a connection to a given
phone number, used e.g. for LCR systems to find the cheapest carrier on a
call-by-call basis. Having it run as a daemon speeds things up as then it
only has to load all the data once.
.
This setting is only useful for special setups, such as for an
ISDN-to-H.323 gateway.
Template: isdnutils/firmware
Type: select
#flag:translate:1
__Choices: none, ISAR.BIN
Default: none
_Description: Firmware to load:
Some ISDN cards can't function properly until some firmware has been
loaded. A notable example is the Sedlbauer SpeedFax+ PCI or Siemens
I-Surf, which need ISAR.BIN to be loaded. Choose "ISAR.BIN" if this is
necessary.
Template: isdnutils/firmwarecards
Type: string
_Description: ISDN card numbers to load with the firmware:
If you use more than one card, enter the number of the card(s) in need
of firmware.
.
Multiple entries should be separated by commas. Card numbers are integers
where "1" is the first card, "2" the second, etc.
Template: isdnvboxserver/msn
Type: string
Default: quit
_Description: Number that vbox should answer:
Vbox must know what number to listen to. Depending on the country's ISDN
system, this may or may not include the area code. Leading "0" should most
often be dropped.
.
Leave the field blank if you want to configure by hand, or if you already
use an existing (working) vbox
configuration from the time when this was still part of isdnutils (unless
you want to create a new configuration).
Template: isdnvboxserver/rings
Type: string
Default: 4
_Description: Number of rings for vbox to pick up the line:
One ring is about 5 seconds. This setting can later be fine-tuned
for each incoming telephone number, for instance to aggressively
filter some incoming numbers.
.
You should read vbox.conf(5) for more information.
Template: isdnvboxserver/attachmsg
Type: boolean
Default: true
_Description: Should incoming messages be attached to notification mails?
When a message is recorded, an email notification is sent. If that
email should contain the message as an attachment, choose the option.
Template: isdnvboxserver/daemonuser
Type: string
Default: vboxdaemonuser
_Description: Run the answering machine as:
The vboxd daemon should run as an unprivileged (non-root) user. It must be
a member of the "dialout" group.
Template: isdnvboxserver/nosuchuser
Type: text
#flag:comment:1
# Translators, do not translate "Daemonuser"
_Description: ${Daemonuser} unknown
The user you chose does not exist on this machine. You must choose
a valid username.
Template: isdnvboxserver/user
Type: string
_Description: Login for the answering machine:
Connections to the answering machine (using the vbox program provided
by the isdnvboxclient package) will be prompted for a username and
password.
.
The username you define here does not have to correspond to a login
account on this system.
Template: isdnvboxserver/password
Type: password
#flag:comment:1,1
# Translators, do not translate "${User}"
_Description: Password for ${User}:
Please choose the password for the ${User} connection user.
Template: isdnvboxserver/vboxnodir
Type: error
_Description: No home directory
The home directory "${DIR}" for user "${USER}" does not exist. This means
that the file "${DIR}/.vbox.conf" cannot be created.
Template: isdnvboxserver/vboxnouser
Type: error
_Description: Non-existing user
The user "${USER}" doesn't exist on the system. Please rerun the
configuration with "dpkg-reconfigure isdnvboxserver" to enter another
username, or after creating the user.
Template: isdnvboxserver/doinit
Type: boolean
Default: true
_Description: Should vboxgetty be enabled?
A call for vboxgetty is defined in /etc/inittab, but not yet enabled. Choosing this option
will enable it once this package is fully configured. Refuse this option
if you want to tweak it manually.
Template: isdnvboxserver/devfs_inittab
Type: error
_Description: Device in inittab doesn't agree with devfs mode
The entry for vboxgetty in /etc/inittab uses a device name that does not
correspond to the current devfs usage; either a devfs (/dev/isdn/ttyIxx)
name is used in inittab while devfs is not mounted, or the non-devfs name
is used while devfs is mounted.
.
This problem has to be fixed manually.
Template: isdnvboxserver/devfs_vboxgettyconf
Type: error
_Description: Device in vboxgetty.conf doesn't agree with devfs mode
The device entry in /etc/isdn/vboxgetty.conf uses a device name that does
not correspond to the current devfs usage; either a devfs
(/dev/isdn/ttyIxx) name is used in vboxgetty.conf while devfs is not
mounted, or the non-devfs name is used while devfs is mounted.
.
This problem has to be fixed manually.
Template: isdnvboxserver/dummy
Type: note
Description: for internal use
Note to translators: no need to translate this, not shown to users.
Reply to: