Here is the log of a session connecting Psion 5mx to Nokia 8810. If you look
through the junk to the IrCOMM frames, you can see the AT commands going
out, and the results pinging back from the phone. This session results in a
connect (if you're interested, to Demon UK using 0845 number through
Vodafone). There seems to be an excess of "AT"'s in the conversion, but
other than that, it may help you get a connection up.

Experience with Orange suggests that if you're using an ISDN/Data number,
you might have to enable data with the provider, but if you're calling an
analog modem number, you can probably just dial (the network cannot
differentiate these calls from voice calls).

Cheers,
Joth
P.S. Apologies for attachment to list -- it's only 3.5kb of zipped text.

-----Original Message-----
From: Bj�rn Mork <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: 15 November 1999 15:42
Subject: Re: [Linux-IrDA]Problems with Ericsson SH888 & IrDA


Thomas Heide Clausen <[EMAIL PROTECTED]> writes:

> Now the funny thing starts when I have this little chat with the modem:
>
> atz
> OK
> atdt<phonenumber>
> [The mobile lites up and types "dialling <phonenumber>, then a second
later the
> light goes off]
> NO CARRIER

Ahh, good news ;-) I have excactly the same problem with my 8810. So
then maybe it isn't the phone anyway? These are my experiences with
the 8810 and the most recent Linux-IrCOMM:

ATD<phonenumber>;

Sets up a voice call without problems.

ATD1,2,3,4,5,6,7

Each "," should give 2 seconds delay, but they don't. The "NO CARRIER"
is just as immediate as without the commas.

This is very annoying, since the IrCOMM-connection to the phone is very
stable with this version of Linux-IrCOMM. Every AT-command that I've
tried (which is close to every command in the standard :-) except "D",
works.

If you want to play with the phonebook(s), you can try these:

AT+CPBS="ME"

selects phonebook (use AT+CPBS=? to see the options, and AT+CPBS? to
see the current selection).

AT+CPBR=1,5

reads entry 1-5 from the current phonebook.

AT+CPBW=....

writes an entry to the phonebook. The format is similar to the output
from a read command. Use AT+CPBW=? to get string limits, options etc.

> I can dial the phonenumber from the keypad of the phone with no problems.

Damn. I've never thought of that possibility... Is it possible to dial
a "data number" from the keypad without initiating a voice call to
the modem instead? I'll have to try this as soon as I get home.

> So I
> am lead to believe that i either still have IrDA problems or that I need
some
> spooky init-string. Most docs I've come across said "AT&F", which I have
tried
> with no much luck. Likewise, I have had no luck with "ATZE0" - which I
have
> also seen mentioned (but which afaik does nothing but disable echo'ing of
what
> I send to the modem).

I think it must be some weird Linux-IrDA related problem. I know Dag
has looked at it several times. But without being able to reproduce
the problem, it's of course not easy to find the bug.

> Anyone with a clue who can help me out? Thanks in advance.

As for the other suggestions you've got: I do know that my carrier
and SIM is data enabled. I use the phone with a Psion Series 5, and
have no problems making modem calls using just ATZ as init string.
ISDN calls are a bit more tricky as Dave pointed out. I have to use
AT+CBST=71,0,1 or ATS35=0 (the last one is probably Nokia specific).

But the point is that I am using the exact same phone, init string
and modem number combinations with both the Psion and Linux. The
Psion works, Linux does not. Why do we two experience this problem,
and not everybody? I have tried changing most of the variables I
could think of, except the PC. Which makes me suspect the PC, or
more presisely something hardware related. I am actually seriuosly
considering installing Windows95 to see if I can reproduce the
problem there...


Bj�rn



_______________________________________________
Linux-IrDA mailing list  -  [EMAIL PROTECTED]
http://www4.pasta.cs.UiT.No/mailman/listinfo/linux-irda

8810s.zip

Reply via email to