🚀 go-pugleaf

In comp.sys.next.programmer, samurai@cs.mcgill.ca (Darcy BROCKBANK) writes:
>Well, it doesn't work for me that is.
>
>1) The example "MessageCenter" that shipped wouldn't compile
>because it had the wrong libraries. I changed the library
>from libphonekit to libphone, and it compiled.

It compiled fine for me without any problems and without any
changes.  Are you using project builder?  The Makefile
uses these libs:

   LIBS = -lphone_s -lMedia_s -lNeXT_s

What is this libphonekit you are talking about?  Are you running
3.0 or one of the pre releases?

>2) MessageCenter now crashes whenever incoming calls arrive.

Message Center doesn't handle errors very well - hey it's a demo.

It was doing that for me at one point.  Check the console log for
an error messages - then if there is one, find it in the code and
figure out what's going on.

When I had the same problem, it was because I had recorded a new
greating, and later removed the .snd file.  If message center can't
open the greating file, it just prints an error and exits (it doesn't
bomb).  It would try to open the file whenever a new phone call
came in.

>3) Giving up on this nice example, I've been struggling along
>with the flakiness of the phonekit.
>
>The flakiness could be due to the fact that I don't know what
>the hell I'm doing however...

>However, it never recieves notification of:
>
>- remotePickup
>- remoteRing
>- dialingComplete
>- remoteBusy

>I'm in Canada, and I'm using an ISDN Extender on
>a POTS line.

How can a POTS interface know that the remote end has picked up
the phone?  It can't (at least not very easilly).  And remote Ring
and remoteBusy could only work if it had very intelligent tone
detection - which I assume it doesn't.  I assume that these only
work for ISDN calls.  The NeXT ISDN Extender is an ISDN interface
that does POTS on the side.  I don't think it was ever intended to
be a great POTS interface.  These type of signals come over the ISDN
D channel as digital messages, so it's easy to relay this information
to the program.  To try to get these functions on a POTS line, you
have to write very fancy tone detection DSP code.  Maybe NeXT will
add that one day, but I wouldn't hold my breath.  You can always
just process the data stream yourself and look for ring tones.

However, dialingComplete should work for POTS.  The manual even
says that you have to use it to insert delays which are sometimes
needed.  I've never tried it yet so I don't have an idea why
that wasn't working for you.

Curt Welch