If you get the sources you need to create script
-configure. You do it by typing:
-
tfuj:~/gnokii-0.3.3pre5$ autoconf
-
-
If you get the sources from the tarball you don't need to do
-this - configure is already made for you. For quick install do simply:
-
tfuj:~/gnokii-0.3.3pre5$ ./configure
-tfuj:~/gnokii-0.3.3pre5$ make
-tfuj:~/gnokii-0.3.3pre5$ make install
-
-
-
But configure has some options. Except obvious
-parameters as --prefix which specifies a path to install GNOKII, you
-can specify one of the following:
-
-
-
--help
-
Shows you list of available options
-
-
--enable-debug
-
Turns on debugging. It's usefull especially for developers. But if you
- find a bug in GNOKII, please compile the sources with debugging enabled and
- send this output to the GNOKII mailing list. This is used by gnokii
- program.
-
-
--enable-xdebug
-
The same as above but used by xgnokii.
-
-
--enable-rlpdebug
-
This option turns on debugging specific to the RLP stuff. Note, that it's
- very important at the moment as this part of GNOKII is under the hardest
- development.
-
-
--without-x
-
Don't include X Window system support - xgnokii.
-
-
--enable-security
-
Turns on some security functions:.... Use them with caution.
-
-
--enable-win32
-
Include MS Windows support. Yes, it really exists. ;-)
-
-
--with-model=MODEL, --with-port=PORT
-
Specify the model of the phone (eg. 6150) and the port it is connected to
- (eg. /dev/ttyS1). These values can be overwritten with ones from the config
- files.
-
When the configure succeed, it shows options GNOKII
-will be compiled with:
-
Host system: linux-gnulibc1
- Gnokii version: 0.3.3_pre5
- Xgnokii version: 20000613
- Phone model: 6130
- Serial port: /dev/ttyS1
- X (GTK) support: no
- Debug: yes
- XDebug: no
- RLPDebug: no
- NLS: yes
- Security: yes
- Win32:
- Prefix: /usr2
-
-
-
Now, the only thing left to do is just ro run:
-
tfuj:~/gnokii-0.3.3pre5$ make
-tfuj:~/gnokii-0.3.3pre5$ make install
-
-
-
Finally, you have GNOKII installed in your system. And now REAL
-FUN begins. :-)
-
-
How to install it from binaries ?
-
-
-
If you downloaded gnokii as a pre-built binary you should install
-it in the conventional manner for the package type in question.
-For example if you downloaded a .rpm file you can install it by
-running the following as root.
-
-
rpm -i gnokii-0.3.2-i386.rpm
-
-
If you are using a Debian based system, you can use dpackage
-to do the installation (FIXME - is this correct ?)
-
-
How to make connection with phone ?
-
-
-
There are three ways to make it:
-
-
-
connecting phone with computer using cable. All phones allow to make it
-(even 3210 - connector is inside). If you want to know more
-about creating your own cable, read cables faq.
-
using IrDa port in phone and computer. Notice, that your computer
-and phone must have it (only some series of Nokia phones has it - for example,
-6110, 6150)
-
connecting to phone special device called "dongle" (it has IrDa port)
-and making IrDa connection between it and phone. Current gnokii cas use
-Tekram IRmate 210 - see patches
-
-
-
How to configure gnokii ?
-
-
-
First it to use --with-model and --with-port options for
-configure script. But I do not recommend this. In my opinion these should be
-removed from configure. Second disadvantage is that you can't use it when
-you are installing a binary package.
-
-
So, will use better method :-).
-You should copy the gnokiirc
-file from the Docs/examples directory to your
-home directory and name it gnokiirc or copy it into /etc directory
-and name gnokiirc.
-
-
Using your favorite
-editor ensure that the settings are correct for your system,
-the sample file has details of the various options available. The most
-difficult problem could be discovering model of your phone - go into
-our firmware page
-and try to use codes written in column
-Firmware version code. If your phone will display something,
-see model number on the third line, look on the
-firmware page
-again (for it) and read phone model then.
-
-
Note that you will need read/write permissions on whatever
-serial port you specify in gnokiirc. You can now use gnokii
-and xgnokii.
-
-
Of course, you don't have to make any config, if you will use
-these config options. There are default:
-
-
Go into configuration of your IrDa port (the most often it's made in
-BIOS, sometimes using program provided by computer's producer):
-
-
-
-
Enable it
-
Setup the COM-Port on which it should work.
-Here are addresses:
- ttyS0 (COM1): 3F8, IRQ: 4
- ttyS1 (COM2): 2F8, IRQ: 3
- ttyS2 (COM3): 3E8, IRQ: 4
- ttyS3 (COM4): 2E8, IRQ: 3
-
-
-
-
-
-
Configure gnokii (see previous question)
-setting type of connection to
-infrared.
-
-
If you are using linux, put linux-irda off (you can't use gnokii over infrared and
-linux-irda at the same time - it means too, if you want use
-linux-irda you must close all gnokii-applications what
-use the infrared-port in moment).
-
-
-
-
How to configure gnokii driver for data connection ?
-
-
-
After installing and configuring gnokii you should make another group
-and allow mgnokiidev (it our virtual modem driver)
-to use it. For example (if you have installed gnokii
-into /usr/local):
-
-
Then connect your phone to your PC and then run gnokiid:
-
-
[ first console ]
-tfuj:/home/pawel/gnokii# ./gnokiid/gnokiid
-
-
-
If successful, you should see a message saying that mgnokiidev has been
-run to create /dev/gnokii. If you're using a 5110/6110 series phone
-you should hear a beep and see an "accessory connected" message on
-the phone. If you're using a 3810 series phone you won't see anything
-on the phones LCD.
-
-
Number 501808080 is an Internet access number for all Idea
-Centertel (Polish GSM operator) abonents. With these files the only thing to do
-is to run gnokiid and /usr/sbin/ppp-gnokii. Note that both:
-/usr/sbin/ppp-gnokii and /etc/ppp/ppp-gnokii must be
-executable files. At the moment you have to run ppp-gnokii as the
-superuser unless the simple user has a permission to write to a pty
-device. gnokiid must be run as the user belinging to gnokii
-group.
-
-
Then "pppd call demon-gnokii" should connect
- ('tail -f /var/log/messages' to see what is happening)
-
-
If a call terminates you should get 'NO CARRIER' and gnokiid should
-continue to work, but this is early code and you may find you have to
-Ctrl-C and restart gnokiid (especially if the phone says the terminal
-connection has been lost)
-
-
AND ANOTHER EXAMPLE PPP SCRIPT FROM Jon Wikne:
-
-
-
-#!/bin/sh
-#
-# Script to launch PPP over a Nokia 5110 / 6110 mobile phone
-# 20-06-2000 -- Jon Wikne
-#
-### NOTE: "01234567" and "username" below must be replaced
-### with your actual ISP's phone number and your user name.
-#
-### NOTE 2: If you are calling an ISDN number or a digital
-### line you may also need ATS35=0 in the chat sequence.
-
-# Launch gnokiid....
-echo "Launching gnokiid... "
-/usr/local/sbin/gnokiid &
-
-# Wait for gnokiid to find the phone.
-sleep 7
-
-# Now, down to business!
-echo "Calling and starting pppd... "
-pppd /dev/gnokii 115200 debug connect \
-'chat -v ECHO ON ABORT BUSY ABORT ERROR ABORT "NO CARRIER" \
-"" AT OK ATDT01234567 CONNECT ""' \
-noipdefault ipcp-accept-local ipcp-accept-remote \
-user username
-
-# Some cleaning up to do....
-
-echo -n "Stopping gnokiid... "
-ps ax | awk 'BEGIN { prog="/usr/local/sbin/gnokiid"; ARGC=1 }
-{ if (prog == $5) { print $1 ; exit 0 } }' $1
-kill "$1"
-echo $1
-
-
-
Permission problem...
-
-
-
-> Now xgnokii want to connecting..... and some minutes later it's say:
-> Gnokii serial_open: open: Permission denied
-> Couldn't open FB61 device: Permission denied
-
-you should set your /dev/ttySx to:
-
-crw-rw---- 1 root dialout 4, 65 Jul 5 2000 /dev/ttyS1
-
-and add yourself to the group dialout. or make a new group gnokii
-and do the same thing for this group. see the gnokii doc about
-this, especialy if you want to use gnokiid.
-
-
-
Xgnokii files missed...
-
-
-
-> > I start to configure:
-> >
-> > elwinx:/usr/src/gnokii# ./configure --prefix=/usr/local/
-> >
-> > checking for X... (cached) libraries /usr/X11R6/lib, headers
-> > /usr/X11R6/include
-> > checking for X11/xpm.h... (cached) no
-> > configure: warning: Cannot find include X11/xpm.h
-> > configure: warning: Disabling xgnokii.
-
-
-
For Debian GNU/Linux 2.2 potato:
-
-
-
-> Do:
-> dpkg -S \*xpm.h
-> and show the result. You can't use xgnokii without libxpm.
-
-After I installed the xpm4g-dev_3.4k-5.deb xgnokii found my X
-
-My next Problem was the Program didn't find the gtk.h
-
-I installed this lib's
-libglib1.2-dev
-libgtk1.2-dev_1.2.7-1.deb
-
-and xgnokii are start up
-
-
-
For Redhat:
-
-
-
-On Red Hat 6.2 (or derived?)
-
-sloth:danielm[12]% locate xpm.h
-/usr/X11R6/include/X11/xpm.h
-sloth:danielm[13]% rpm -qf /usr/X11R6/include/X11/xpm.h
-xpm-devel-3.4k-2
-
-On Red Hat 7 (or derived?)
-
-mouth:danielm[4]% locate xpm.h
-/usr/X11R6/include/X11/xpm.h
-mouth:danielm[5]% rpm -qf /usr/X11R6/include/X11/xpm.h
-XFree86-devel-4.0.1-1
-
-
-
Infrared problem
-
-
-
-> I'm having trouble getting Gnokii to work with my Nokia 6110 using the
-> infrared connection. It works perfectly with the cable. When I run gnokii
-> as non-root I get the following output:
->
-> Added new section global
-> Adding key/value port//dev/ttyS3
-> Adding key/value model/6110
-> Adding key/value initlength/default
-> Adding key/value connection/infrared
-> Adding key/value bindir//usr/local/sbin/
-> Entering monitor mode...
-> Initialising GSM interface...
-> Starting IR mode...!
-> Couldn't open FB61 infrared device: Device or resource busy
-> Hmmm... GSM_LinkOK never went true. Quitting.
->
-> And if I run it as root it looks like this:
->
-> Added new section global
-> Adding key/value port//dev/ttyS3
-> Adding key/value model/6110
-> Adding key/value initlength/default
-> Adding key/value connection/infrared
-> Adding key/value bindir//usr/local/sbin/
-> Entering monitor mode...
-> Initialising GSM interface...
-> Starting IR mode...!
-> PC: 1c:00:0c:02:00:09:00:01:00:0d:00:00:02:01:40:00:52:06:
-> Timeout in IR-mode
-> PC: 1c:00:0c:02:00:09:00:01:00:0d:00:00:02:01:41:00:53:06:
-> Timeout in IR-mode
-> PC: 1c:00:0c:02:00:09:00:01:00:0d:00:00:02:01:42:00:50:06:
-> Timeout in IR-mode
-> PC: 1c:00:0c:02:00:09:00:01:00:0d:00:00:02:01:43:00:51:06:
-> Timeout in IR-mode
-> PC: 1c:00:0c:02:00:09:00:01:00:0d:00:00:02:01:44:00:56:06:
-> Timeout in IR-mode
-> Hmmm... GSM_LinkOK never went true. Quitting.
->
-> It makes no difference if IR-reception is activated or not (well maybe the
-> numbers are different, I haven't checked)
->
-> I have followed the Alessandro's beta-HOWTO which was posted June 22 2000
-> with the subject "Re: IR setup".
->
-> In /var/log/messages I have found the following:
->
-> Feb 18 23:34:16 bmw kernel: ircomm_tty: virtual tty driver for IrCOMM (
-> revision:Wed May 26 00:49:11 1999 )
-> Feb 18 23:34:16 bmw kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A
-> Feb 18 23:34:16 bmw kernel: ttyS03 at 0x02e8 (irq = 3) is a 16550A
->
-> I have tried both with and without the irda-module loaded (insmod
-> irda) but without luck.
->
-> I'm using a Fujitsu C325 Lifebook (labtop) and my Nokia 6110 is version
-> 4.33. Has anyone experienced problems like these and hopefully has found a
-> solution, or maybe just have some ideas for what I should try next.
-
-"I also had removed the Ethernet PCcard.
-That thing got assigned the _interrupt_ (irq 3) that the serial interface
-for the IR port needs. Without it gnokii works."
-
-Now I've got contact to my Nokia 6110 using the infrared port.
-
-
-
Answering data calls problem...
-
-
-
-> It seems like it's some sort of PacBell or Verizon thing, because I
-> get a ring when I try to dial a voice call, but when I dial from
-> minicom/gnokiid I get "NO CARRIER" ("Check Operator Services" on the
-> phone), and dialing in from the Palm still gets no ring.
-
-First we should know how operators manage data call services,
-is there any international standard (it would be, to make international data
-calls possible). I described, how it works with my operator (Plusgsm/PL)
-and I'm interesting if it's a worldwide standard for these services?
-Did somebody tried to make a cellular-to-cellular international data transfer ?
-
-In Plusgsm there are three kinds of data calls :
-1. OUTGOING CALLS. Service activation is free with no additional monthly charge.
+
+
+
+
+ Configuration
+
+
+
+
+
+
If you get the sources you need to create script
+configure. You do it by typing:
+
tfuj:~/gnokii-0.3.3pre5$ autoconf
+
+
If you get the sources from the tarball you don't need to do
+this - configure is already made for you. For quick install do simply:
+
tfuj:~/gnokii-0.3.3pre5$ ./configure
+tfuj:~/gnokii-0.3.3pre5$ make
+tfuj:~/gnokii-0.3.3pre5$ make install
+
+
+
But configure has some options. Except obvious
+parameters as --prefix which specifies a path to install GNOKII, you
+can specify one of the following:
+
+
+
--help
+
Shows you list of available options
+
+
--enable-debug
+
Turns on debugging. It's usefull especially for developers. But if you
+ find a bug in GNOKII, please compile the sources with debugging enabled and
+ send this output to the GNOKII mailing list. This is used by gnokii
+ program.
+
+
--enable-xdebug
+
The same as above but used by xgnokii.
+
+
--enable-rlpdebug
+
This option turns on debugging specific to the RLP stuff. Note, that it's
+ very important at the moment as this part of GNOKII is under the hardest
+ development.
+
+
--without-x
+
Don't include X Window system support - xgnokii.
+
+
--enable-security
+
Turns on some security functions:.... Use them with caution.
+
+
--enable-win32
+
Include MS Windows support. Yes, it really exists. ;-)
+
+
--with-model=MODEL, --with-port=PORT
+
Specify the model of the phone (eg. 6150) and the port it is connected to
+ (eg. /dev/ttyS1). These values can be overwritten with ones from the config
+ files.
+
When the configure succeed, it shows options GNOKII
+will be compiled with:
+
Host system: linux-gnulibc1
+ Gnokii version: 0.3.3_pre5
+ Xgnokii version: 20000613
+ Phone model: 6130
+ Serial port: /dev/ttyS1
+ X (GTK) support: no
+ Debug: yes
+ XDebug: no
+ RLPDebug: no
+ NLS: yes
+ Security: yes
+ Win32:
+ Prefix: /usr2
+
+
+
Now, the only thing left to do is just ro run:
+
tfuj:~/gnokii-0.3.3pre5$ make
+tfuj:~/gnokii-0.3.3pre5$ make install
+
+
+
Finally, you have GNOKII installed in your system. And now REAL
+FUN begins. :-)
+
+
How to install it from binaries ?
+
+
+
If you downloaded gnokii as a pre-built binary you should install
+it in the conventional manner for the package type in question.
+For example if you downloaded a .rpm file you can install it by
+running the following as root.
+
+
rpm -i gnokii-0.3.2-i386.rpm
+
+
If you are using a Debian based system, you can use dpackage
+to do the installation (FIXME - is this correct ?)
+
+
How to make connection with phone ?
+
+
+
There are three ways to make it:
+
+
+
connecting phone with computer using cable. All phones allow to make it
+(even 3210 - connector is inside). If you want to know more
+about creating your own cable, read cables faq.
+
using IrDa port in phone and computer. Notice, that your computer
+and phone must have it (only some series of Nokia phones has it - for example,
+6110, 6150)
+
connecting to phone special device called "dongle" (it has IrDa port)
+and making IrDa connection between it and phone. Current gnokii cas use
+Tekram IRmate 210 - see patches
+
+
+
How to configure gnokii ?
+
+
+
First it to use --with-model and --with-port options for
+configure script. But I do not recommend this. In my opinion these should be
+removed from configure. Second disadvantage is that you can't use it when
+you are installing a binary package.
+
+
So, will use better method :-).
+You should copy the gnokiirc
+file from the Docs/examples directory to your
+home directory and name it gnokiirc or copy it into /etc directory
+and name gnokiirc.
+
+
Using your favorite
+editor ensure that the settings are correct for your system,
+the sample file has details of the various options available. The most
+difficult problem could be discovering model of your phone - go into
+our firmware page
+and try to use codes written in column
+Firmware version code. If your phone will display something,
+see model number on the third line, look on the
+firmware page
+again (for it) and read phone model then.
+
+
Note that you will need read/write permissions on whatever
+serial port you specify in gnokiirc. You can now use gnokii
+and xgnokii.
+
+
Of course, you don't have to make any config, if you will use
+these config options. There are default:
+
+
Go into configuration of your IrDa port (the most often it's made in
+BIOS, sometimes using program provided by computer's producer):
+
+
+
+
Enable it
+
Setup the COM-Port on which it should work.
+Here are addresses:
+ ttyS0 (COM1): 3F8, IRQ: 4
+ ttyS1 (COM2): 2F8, IRQ: 3
+ ttyS2 (COM3): 3E8, IRQ: 4
+ ttyS3 (COM4): 2E8, IRQ: 3
+
+
+
+
+
+
Configure gnokii (see previous question)
+setting type of connection to
+infrared.
+
+
If you are using linux, put linux-irda off (you can't use gnokii over infrared and
+linux-irda at the same time - it means too, if you want use
+linux-irda you must close all gnokii-applications what
+use the infrared-port in moment).
+
+
+
+
How to configure gnokii driver for data connection ?
+
+
+
After installing and configuring gnokii you should make another group
+and allow mgnokiidev (it our virtual modem driver)
+to use it. For example (if you have installed gnokii
+into /usr/local):
+
+
Then connect your phone to your PC and then run gnokiid:
+
+
[ first console ]
+tfuj:/home/pawel/gnokii# ./gnokiid/gnokiid
+
+
+
If successful, you should see a message saying that mgnokiidev has been
+run to create /dev/gnokii. If you're using a 5110/6110 series phone
+you should hear a beep and see an "accessory connected" message on
+the phone. If you're using a 3810 series phone you won't see anything
+on the phones LCD.
+
+
Number 501808080 is an Internet access number for all Idea
+Centertel (Polish GSM operator) abonents. With these files the only thing to do
+is to run gnokiid and /usr/sbin/ppp-gnokii. Note that both:
+/usr/sbin/ppp-gnokii and /etc/ppp/ppp-gnokii must be
+executable files. At the moment you have to run ppp-gnokii as the
+superuser unless the simple user has a permission to write to a pty
+device. gnokiid must be run as the user belinging to gnokii
+group.
+
+
Then "pppd call demon-gnokii" should connect
+ ('tail -f /var/log/messages' to see what is happening)
+
+
If a call terminates you should get 'NO CARRIER' and gnokiid should
+continue to work, but this is early code and you may find you have to
+Ctrl-C and restart gnokiid (especially if the phone says the terminal
+connection has been lost)
+
+
AND ANOTHER EXAMPLE PPP SCRIPT FROM Jon Wikne:
+
+
+
+#!/bin/sh
+#
+# Script to launch PPP over a Nokia 5110 / 6110 mobile phone
+# 20-06-2000 -- Jon Wikne
+#
+### NOTE: "01234567" and "username" below must be replaced
+### with your actual ISP's phone number and your user name.
+#
+### NOTE 2: If you are calling an ISDN number or a digital
+### line you may also need ATS35=0 in the chat sequence.
+
+# Launch gnokiid....
+echo "Launching gnokiid... "
+/usr/local/sbin/gnokiid &
+
+# Wait for gnokiid to find the phone.
+sleep 7
+
+# Now, down to business!
+echo "Calling and starting pppd... "
+pppd /dev/gnokii 115200 debug connect \
+'chat -v ECHO ON ABORT BUSY ABORT ERROR ABORT "NO CARRIER" \
+"" AT OK ATDT01234567 CONNECT ""' \
+noipdefault ipcp-accept-local ipcp-accept-remote \
+user username
+
+# Some cleaning up to do....
+
+echo -n "Stopping gnokiid... "
+ps ax | awk 'BEGIN { prog="/usr/local/sbin/gnokiid"; ARGC=1 }
+{ if (prog == $5) { print $1 ; exit 0 } }' $1
+kill "$1"
+echo $1
+
+
+
Permission problem...
+
+
+
+> Now xgnokii want to connecting..... and some minutes later it's say:
+> Gnokii serial_open: open: Permission denied
+> Couldn't open FB61 device: Permission denied
+
+you should set your /dev/ttySx to:
+
+crw-rw---- 1 root dialout 4, 65 Jul 5 2000 /dev/ttyS1
+
+and add yourself to the group dialout. or make a new group gnokii
+and do the same thing for this group. see the gnokii doc about
+this, especialy if you want to use gnokiid.
+
+
+
Xgnokii files missed...
+
+
+
+> > I start to configure:
+> >
+> > elwinx:/usr/src/gnokii# ./configure --prefix=/usr/local/
+> >
+> > checking for X... (cached) libraries /usr/X11R6/lib, headers
+> > /usr/X11R6/include
+> > checking for X11/xpm.h... (cached) no
+> > configure: warning: Cannot find include X11/xpm.h
+> > configure: warning: Disabling xgnokii.
+
+
+
For Debian GNU/Linux 2.2 potato:
+
+
+
+> Do:
+> dpkg -S \*xpm.h
+> and show the result. You can't use xgnokii without libxpm.
+
+After I installed the xpm4g-dev_3.4k-5.deb xgnokii found my X
+
+My next Problem was the Program didn't find the gtk.h
+
+I installed this lib's
+libglib1.2-dev
+libgtk1.2-dev_1.2.7-1.deb
+
+and xgnokii are start up
+
+
+
For Redhat:
+
+
+
+On Red Hat 6.2 (or derived?)
+
+sloth:danielm[12]% locate xpm.h
+/usr/X11R6/include/X11/xpm.h
+sloth:danielm[13]% rpm -qf /usr/X11R6/include/X11/xpm.h
+xpm-devel-3.4k-2
+
+On Red Hat 7 (or derived?)
+
+mouth:danielm[4]% locate xpm.h
+/usr/X11R6/include/X11/xpm.h
+mouth:danielm[5]% rpm -qf /usr/X11R6/include/X11/xpm.h
+XFree86-devel-4.0.1-1
+
+
+
Infrared problem
+
+
+
+> I'm having trouble getting Gnokii to work with my Nokia 6110 using the
+> infrared connection. It works perfectly with the cable. When I run gnokii
+> as non-root I get the following output:
+>
+> Added new section global
+> Adding key/value port//dev/ttyS3
+> Adding key/value model/6110
+> Adding key/value initlength/default
+> Adding key/value connection/infrared
+> Adding key/value bindir//usr/local/sbin/
+> Entering monitor mode...
+> Initialising GSM interface...
+> Starting IR mode...!
+> Couldn't open FB61 infrared device: Device or resource busy
+> Hmmm... GSM_LinkOK never went true. Quitting.
+>
+> And if I run it as root it looks like this:
+>
+> Added new section global
+> Adding key/value port//dev/ttyS3
+> Adding key/value model/6110
+> Adding key/value initlength/default
+> Adding key/value connection/infrared
+> Adding key/value bindir//usr/local/sbin/
+> Entering monitor mode...
+> Initialising GSM interface...
+> Starting IR mode...!
+> PC: 1c:00:0c:02:00:09:00:01:00:0d:00:00:02:01:40:00:52:06:
+> Timeout in IR-mode
+> PC: 1c:00:0c:02:00:09:00:01:00:0d:00:00:02:01:41:00:53:06:
+> Timeout in IR-mode
+> PC: 1c:00:0c:02:00:09:00:01:00:0d:00:00:02:01:42:00:50:06:
+> Timeout in IR-mode
+> PC: 1c:00:0c:02:00:09:00:01:00:0d:00:00:02:01:43:00:51:06:
+> Timeout in IR-mode
+> PC: 1c:00:0c:02:00:09:00:01:00:0d:00:00:02:01:44:00:56:06:
+> Timeout in IR-mode
+> Hmmm... GSM_LinkOK never went true. Quitting.
+>
+> It makes no difference if IR-reception is activated or not (well maybe the
+> numbers are different, I haven't checked)
+>
+> I have followed the Alessandro's beta-HOWTO which was posted June 22 2000
+> with the subject "Re: IR setup".
+>
+> In /var/log/messages I have found the following:
+>
+> Feb 18 23:34:16 bmw kernel: ircomm_tty: virtual tty driver for IrCOMM (
+> revision:Wed May 26 00:49:11 1999 )
+> Feb 18 23:34:16 bmw kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A
+> Feb 18 23:34:16 bmw kernel: ttyS03 at 0x02e8 (irq = 3) is a 16550A
+>
+> I have tried both with and without the irda-module loaded (insmod
+> irda) but without luck.
+>
+> I'm using a Fujitsu C325 Lifebook (labtop) and my Nokia 6110 is version
+> 4.33. Has anyone experienced problems like these and hopefully has found a
+> solution, or maybe just have some ideas for what I should try next.
+
+"I also had removed the Ethernet PCcard.
+That thing got assigned the _interrupt_ (irq 3) that the serial interface
+for the IR port needs. Without it gnokii works."
+
+Now I've got contact to my Nokia 6110 using the infrared port.
+
+
+
Answering data calls problem...
+
+
+
+> It seems like it's some sort of PacBell or Verizon thing, because I
+> get a ring when I try to dial a voice call, but when I dial from
+> minicom/gnokiid I get "NO CARRIER" ("Check Operator Services" on the
+> phone), and dialing in from the Palm still gets no ring.
+
+First we should know how operators manage data call services,
+is there any international standard (it would be, to make international data
+calls possible). I described, how it works with my operator (Plusgsm/PL)
+and I'm interesting if it's a worldwide standard for these services?
+Did somebody tried to make a cellular-to-cellular international data transfer ?
+
+In Plusgsm there are three kinds of data calls :
+1. OUTGOING CALLS. Service activation is free with no additional monthly charge.
For default this service is disabled, you have to call operator's helpdesk
- to enable. With this service is possible to call:
- a) any internet gate
- b) WAP gate
- c) any "private" computer with own transfer protocol
- d) ?? send a fax ?? (with special fax software for cellular modem
- included in NCDS)
- 1 minute charge is similar to voice calls. It's not allowed by the operator
- to answer incoming data call.
-2. INCOMING CALLS. You have to pay for service activation (5$) and additional
- monthly charge (10$). Then you will get a new SIM card with 2 phone numbers:
- one for voice/sms and second one - for incoming data calls only.
- 1 min charge depends on the network from the call was initiated,
- generally 1...2 times x voice call.
-3. FAX CALLS. Another payable service, not covered by above mentioned.
- There is a special trick for incoming fax: it's stored in "FAX mailbox",
- you can call this mailbox with standard fax machine
- (or cellular modem connected to PC) to receive it.
-
-I guess your operator have similar restrictions for incoming data calls and
-here is your problem. Incoming call is recognized as a data type and rejected.
-It would be nice to know if it's rejected on the operator's software level or
-by the phone software (acc. to informations stored in the SIM).
-In the second case it's easier to omit these restrictions. But be careful !
-You will be treated by the law in the same way as if you try to hack
-Bill Gates credit card number ;-) .
-
-
-
Xgnokii works, gnokii not...
-
-
-
-> 1. Why is it that xgnokii communicates perfectly with my 3210, while the
-> only thing that the command line gnokii does is:
-> GSM/FBUS init failed! (Unknown model ?). Quitting.
-> [cvd@sirius gnokii]$ ./gnokii --monitor
-> Opened configuration file /home/cvd/.gnokiirc
-> Added new section global
-> Adding key/value port//dev/ttyS1
-> Adding key/value model/3210
-> Adding key/value initlength/default
-> Adding key/value connection/serial
-
-Look into latest gnokiirc from /docs/default. "serial" setting for connection
-is not used from long time. Change to other actual parameter ("fbus" ?)...
-
-
-
-
-
+ to
enable. With this service is possible to call:
+ a) any internet gate
+ b) WAP gate
+ c) any "private" computer with own transfer protocol
+ d) ?? send a fax ?? (with special fax software for cellular modem
+ included in NCDS)
+ 1 minute charge is similar to voice calls. It's not allowed by the operator
+ to answer incoming data call.
+2. INCOMING CALLS. You have to pay for service activation (5$) and additional
+ monthly charge (10$). Then you will get a new SIM card with 2 phone numbers:
+ one for voice/sms and second one - for incoming data calls only.
+ 1 min charge depends on the network from the call was initiated,
+ generally 1...2 times x voice call.
+3. FAX CALLS. Another payable service, not covered by above mentioned.
+ There is a special trick for incoming fax: it's stored in "FAX mailbox",
+ you can call this mailbox with standard fax machine
+ (or cellular modem connected to PC) to receive it.
+
+I guess your operator have similar restrictions for incoming data calls and
+here is your problem. Incoming call is recognized as a data type and rejected.
+It would be nice to know if it's rejected on the operator's software level or
+by the phone software (acc. to informations stored in the SIM).
+In the second case it's easier to omit these restrictions. But be careful !
+You will be treated by the law in the same way as if you try to hack
+Bill Gates credit card number ;-) .
+
+
+
Xgnokii works, gnokii not...
+
+
+
+> 1. Why is it that xgnokii communicates perfectly with my 3210, while the
+> only thing that the command line gnokii does is:
+> GSM/FBUS init failed! (Unknown model ?). Quitting.
+> [cvd@sirius gnokii]$ ./gnokii --monitor
+> Opened configuration file /home/cvd/.gnokiirc
+> Added new section global
+> Adding key/value port//dev/ttyS1
+> Adding key/value model/3210
+> Adding key/value initlength/default
+> Adding key/value connection/serial
+
+Look into latest gnokiirc from /docs/default. "serial" setting for connection
+is not used from long time. Change to other actual parameter ("fbus" ?)...
+