iaxclient-devel — Development Discussion List

Re: [Iaxclient-devel] What are people thinking of/ planning to use iaxclient for?

[Steve K. <st...@st...>]

Scott Lambert wrote:

>On Thu, Jul 03, 2003 at 02:32:47PM -0400, Steve Kann wrote:
>  
>
>>There's now 36 people on the iaxclient-devel mailing list, and I figured
>>now would be a good time to get an idea from people of what they're
>>using or planning on using iaxclient for, what they'd like to see in
>>there, and what they'd like to work on.
>>
>>Obviously, nobody needs to tell us what they're doing, but I think that
>>if I know, or other people know what others are thinking, it can help
>>people work together better.
>>
>>I know there's a crew out there planning on using the library itself, in
>>some MS-Windows applications.  There's the people who have helpfully
>>contributed already (and they've been noted in the README).  I guess I'm
>>curious as to who's doing this as a hobby, who's planning on using this
>>as part of larger projects, etc.
>>    
>>
>
>Currently, I'm in the hobby end.  Mostly, I want a soft phone that
>connects to my home asterisk server from wherever without having to drag
>around another piece of hardware (ATA-186 or the like).  If it's going
>to connect to an Asterisk server, it might as well use the asterisk
>protocol.  Not having setup either, it looks to me like IAX is much
>simpler to configure than SIP or H.323.
>
>Basically, I want a dead simple way to use my home phone wherever I am.
>I am almost never without my FreeBSD laptop.
>

hmm, have you been using iaxclient on your laptop?  Are you using it 
with built-in microphone, and speakers, or with a headset (or at least 
headphones?).

If it's the former, then echo-cancellation is going to be something 
you'll need :)

I actually tried out Apple's ichat, and their acoustical echo 
cancellation seemed pretty good.  I didn't hear a lot of echo.  But they 
cheat a bit:  On powerbooks, there are two speakers, and the microphone 
is _embedded_ in the left speaker area.  So, I guess their echo 
cancellation wasn't good enough to deal with that kind of echo, so they 
end up playing output audio only through the right speaker :)

I dunno if other laptops use this somewhat questionable design or not..  
Most PC notebooks seem to have them separated a bit.

-SteveK

Re: [Iaxclient-devel] What are people thinking of/ planning to use iaxclient for?

[Scott L. <la...@la...>]

On Thu, Jul 03, 2003 at 02:32:47PM -0400, Steve Kann wrote:
> There's now 36 people on the iaxclient-devel mailing list, and I figured
> now would be a good time to get an idea from people of what they're
> using or planning on using iaxclient for, what they'd like to see in
> there, and what they'd like to work on.
> 
> Obviously, nobody needs to tell us what they're doing, but I think that
> if I know, or other people know what others are thinking, it can help
> people work together better.
> 
> I know there's a crew out there planning on using the library itself, in
> some MS-Windows applications.  There's the people who have helpfully
> contributed already (and they've been noted in the README).  I guess I'm
> curious as to who's doing this as a hobby, who's planning on using this
> as part of larger projects, etc.

Currently, I'm in the hobby end.  Mostly, I want a soft phone that
connects to my home asterisk server from wherever without having to drag
around another piece of hardware (ATA-186 or the like).  If it's going
to connect to an Asterisk server, it might as well use the asterisk
protocol.  Not having setup either, it looks to me like IAX is much
simpler to configure than SIP or H.323.

Basically, I want a dead simple way to use my home phone wherever I am.
I am almost never without my FreeBSD laptop.

-- 
Scott Lambert                    KC5MLE                       Unix SysAdmin
la...@la...      

Re: [Iaxclient-devel] What are people thinking of/ planning to use iaxclient for?

[Gary <ga...@au...>]

From John Todd :

<quote>
Goal:
I'd like to see something I can hand out to someone who has never 
used a VoIP service before.  I should be able to hand them a 
compressed file, and they uncompress it.  A very obvious 
"Preferences" area allows them to enter in their username and 
password, and a hostname of a remote server.  Then, without too much 
difficulty, they should be able to make calls as long as I've got the 
correct user account data in my Asterisk server.  I want my mother to 
be able to figure it out (even though I'd never give her anything 
other than a phone that looked like a phone.  :)
</quote>

I think that about sums it up.

The only thing I could possibly add is to have code portable enough
that it could easily be embedded into a suitable handset.

GAry

.

Re: [Iaxclient-devel] What are people thinking of/ planning to use iaxclient for?

[John T. <jt...@lo...>]

Well, since you asked, I'll give you the list of things that would be 
ultimately useful.  Some of these probably are not envisioned for 
IAXclient, and some are quite complex to implement.  However, from an 
end-user perspective, here's what see as the list:

Basic requirements:
   - MacOSX and Windows clients (though I am very excited about the 
*BSD ports; OpenBSD interface would be excellent.)
   - easy configuration of user ID and password (preferably store-able 
in the Keychain for MacOS)
   - conference ability
   - ability to select codecs on a per host and then (optionally) per call
   - live call quality statistics of some type
   - speed-dial buttons (with IAX specifications, as well, if required)
   - multiple logins to multiple servers at once
   - ring tones
   - the ability to launch other programs with customizable command 
line upon ring (/usr/local/bin/say "You are getting a call from 
${CALLERID}")
   - ability for dial requests to be handed in from other applications 
(like double-clicking on a URL from a browser)
   - playback of touch tone sequences when keys pressed (at least keyclicks)
   - different GUI hints to allow for dialed number input via "keypad" 
(not being able to dial a number from the big fat keys at the top of 
the screen is somewhat odd)


Pie-in-the-sky requirements:
   - video support (H.263 dumping into quicktime - avoids nasty SIP 
firewall nightmares)
   - selectable trivial answering machine (I know this should be done 
on the server, but sometimes it's easier to just press a button on 
the client and record an "I'm away" message, a la AIM's "away" 
preference button)
   - distributed directory feature of some sort (LDAP?  XML?)
   - TAPI interface for TAPI-compliant software
   - full debug and configuration and history output, in text, 
available with a single click (this is for customer cut-and-paste 
into email for the remote technician who has to debug configs; better 
than stepping the customer through a million windows and scrollbars 
to see what is set to what, and what the last call did, etc.)




Goal:
I'd like to see something I can hand out to someone who has never 
used a VoIP service before.  I should be able to hand them a 
compressed file, and they uncompress it.  A very obvious 
"Preferences" area allows them to enter in their username and 
password, and a hostname of a remote server.  Then, without too much 
difficulty, they should be able to make calls as long as I've got the 
correct user account data in my Asterisk server.  I want my mother to 
be able to figure it out (even though I'd never give her anything 
other than a phone that looked like a phone.  :)

This requirement list is not much different than that of a SIP UA, 
such as the Xten or Pingtel.  I'm not planning anything in particular 
with this system right now, but I see a growing number of my clients 
who keep asking me for soft clients.  One that works natively with 
Asterisk would be very powerful.


JT

>Hey list,
>
>There's now 36 people on the iaxclient-devel mailing list, and I 
>figured now would be a good time to get an idea from people of what 
>they're using or planning on using iaxclient for, what they'd like 
>to see in there, and what they'd like to work on.
>
>Obviously, nobody needs to tell us what they're doing, but I think 
>that if I know, or other people know what others are thinking, it 
>can help people work together better.
>
>I know there's a crew out there planning on using the library 
>itself, in some MS-Windows applications.  There's the people who 
>have helpfully contributed already (and they've been noted in the 
>README).  I guess I'm curious as to who's doing this as a hobby, 
>who's planning on using this as part of larger projects, etc.
>
>Feel free to reply to the list, or just to me if you don't want to 
>make things public, or not at all if you don't want to either..
>
>I think it's pretty clear what I'm planning for my own needs; I just 
>need what's more or less already described on the website, which is 
>a very small, very simple, cross-platform graphical client which 
>really just supports making a single outbound call, to a destination 
>specified on the command-line.  The important things for us are call 
>quality, reliable operation, and some audio options.  At this point, 
>I think that I'll be basing my client on "wx", and using wxwindows 
>for development because it's worked out pretty well, but I might end 
>up making separate native Win32 and MacOSX UIs to it.
>
>Some things that we still need that haven't been discussed here yet 
>are some really good echo cancellation, so we can have full-duplex 
>calls for users without headsets (i.e. using standard speakers and 
>microphones).  Right now, that's pretty unusable on laptops because 
>of echo, and not very pleasant unless you have a good directional 
>microphone, and keep the speakers low.
>
>Thanks.
>
>-SteveK
>
>--
>   Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
>                 HorizonLive.com - collaborate . interact . learn
>    "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

[Iaxclient-devel] What are people thinking of/ planning to use iaxclient for?

[Steve K. <st...@st...>]

Hey list,

There's now 36 people on the iaxclient-devel mailing list, and I figured
now would be a good time to get an idea from people of what they're
using or planning on using iaxclient for, what they'd like to see in
there, and what they'd like to work on.

Obviously, nobody needs to tell us what they're doing, but I think that
if I know, or other people know what others are thinking, it can help
people work together better.

I know there's a crew out there planning on using the library itself, in
some MS-Windows applications.  There's the people who have helpfully
contributed already (and they've been noted in the README).  I guess I'm
curious as to who's doing this as a hobby, who's planning on using this
as part of larger projects, etc.

Feel free to reply to the list, or just to me if you don't want to make
things public, or not at all if you don't want to either..

I think it's pretty clear what I'm planning for my own needs; I just
need what's more or less already described on the website, which is a
very small, very simple, cross-platform graphical client which really
just supports making a single outbound call, to a destination specified
on the command-line.  The important things for us are call quality,
reliable operation, and some audio options.  At this point, I think that
I'll be basing my client on "wx", and using wxwindows for development
because it's worked out pretty well, but I might end up making separate
native Win32 and MacOSX UIs to it.  

Some things that we still need that haven't been discussed here yet are
some really good echo cancellation, so we can have full-duplex calls for
users without headsets (i.e. using standard speakers and microphones). 
Right now, that's pretty unusable on laptops because of echo, and not
very pleasant unless you have a good directional microphone, and keep
the speakers low.

Thanks. 

-SteveK


-- 
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

Re: [Iaxclient-devel] Patchset to get testcall to build on FreeBSD

[Steve K. <st...@st...>]

OK, I applied your diff, except for 2 pieces:

1) The gsm/Makefile changes, since these aren't actually used.
2) The change to testcall.c's include of "iaxclient.h", since it also
shouldn't be needed.

The first I'm fairly sure about; you probably just tried to build
libgsm.a separately, which isn't necessary.

The second, I'm not sure why you added; surely your cc is honoring the
-I../../lib flag?

Also, you might want to try building with IAXVER=2, to build against
libiax2.  (just run make IAXVER=2, after making clean in lib, or
temporarily change lib/Makefile to build against libiax2).  At some
point, when we resolve some small issues, we'll be switching the client
to use IAX2 instead of IAX1 -- and this way, that change won't break the
FreeBSD build either.

If you make any changes to libiax2, I also want to keep that in sync
with Mark's canonical copy at Digium, so if they're significant, you
might want to talk to him about disclaiming your changes.


-SteveK

On Wed, 2003-07-02 at 21:30, Scott Lambert wrote:

> I've managed to get testcall to build and run on FreeBSD.  I don't know 
> that it is doing what it is supposed to do, but it does run. :-)
> 
> I probably don't have my asterisk setup properly.
> 
> la...@la... ~/src/vendor/iaxclient/simpleclient/testcall
> 21:25:40 Wed Jul 02 $ ./testcall 
> settings: 
>         silence threshold: -99.000000
>         level output: off
> 
>             TestCall accept some keyboard input while it's running.
>             You must hit 'enter' for your keypresses to be recognized,
>             although you can type more than one key on a line
> 
>             q: drop the call and hangup.
>             0-9 * or #: dial those DTMF digits.
> Calling guest@192.168.1.101/default
> ready for keyboard input
> IAXCLIENT: Call rejected by remote

-- 
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

Re: [Iaxclient-devel] Patchset to get testcall to build on FreeBSD

[Scott L. <la...@la...>]

BTW, I put the binaries and the diffs on the web.  

These are all done on FreeBSD 5.1. 

-- 
Scott Lambert                    KC5MLE                       Unix SysAdmin
la...@la...      

Re: [Iaxclient-devel] Patchset to get testcall to build on FreeBSD

[Scott L. <la...@la...>]

No need to cc: me.

On Wed, Jul 02, 2003 at 11:20:22PM -0400, Steve Kann wrote:
> Thanks, Scott.
> 
> I'll try these out tomorrow.
> 
> The gsm Makefile patch shouldn't be necessary, though, because we 
> aren't actually using the gsm Makefiles; the lib/Makefile makes all the 
> objects necessary for the gsm codec.
> 
> I guess I can't decide if the "OSTYPEREAL" thing you did makes things 
> clearer or more complicated -- probably simpler and less likely to 
> break when us "Linux bigots" change things but forget to maintain the 
> FreeBSD targets :)

It was merely an expedient for setting MAKE=gmake rather than MAKE=make.

It would probably be better to generalize out the "Linux" case to "unix"
and just override anything that is needed for a particular subset of
"unix".  That would probably end up making OS X a subset of "unix"
along with linux, *BSD, and everything else.  That's probably more
far reaching than I realize right now, and I'm really supposed to be
sleeping.

Choosing the name of "make" and setting the CFLAGS to use the right     
threads lib have been the only thing that has needed a knob in the      
Makefiles so far.                                                       

It's a real pain in the gluteous maximus trying to use sourceforge.net's
cvs server, at least with an anonymous login.

I made basically the same changes to the wx/Makefile and it builds/runs
now.
 
> You should try to have it call a public IAX server or make a sucessful 
> test call though; gu...@mi... should work..
 
Using hostnames in testcall seems to be bad.

Calling gu...@mi.../s@default
ready for keyboard input
Segmentation fault (core dumped)

but an IP works just fine. :-)

Calling guest@216.207.245.8/s@default
ready for keyboard input
Scheduling retransmission 9
Scheduling retransmission 9
IAXCLIENT: Call 0 ringing
IAXCLIENT: Call 0 answered
Scheduling retransmission 9
Scheduling retransmission 9
Scheduling retransmission 9
9
sending 9
Scheduling retransmission 9
Scheduling retransmission 9
456
sending 4
sending 5
sending 6
...
q
Hanging up and exiting
IAXCLIENT: Hanging up call 0

Audio was good and it heard my "keypresses".  Now where is my headset?

wx, IAXTest, works too.  Holy cow!  That was easier than I had expected.

Too bad iaxtel.com seems to be flakey right now.

-- 
Scott Lambert                    KC5MLE                       Unix SysAdmin
la...@la...      

Re: [Iaxclient-devel] Patchset to get testcall to build on FreeBSD

[Steve K. <st...@st...>]

Thanks, Scott.

I'll try these out tomorrow.

The gsm Makefile patch shouldn't be necessary, though, because we 
aren't actually using the gsm Makefiles; the lib/Makefile makes all the 
objects necessary for the gsm codec.

I guess I can't decide if the "OSTYPEREAL" thing you did makes things 
clearer or more complicated -- probably simpler and less likely to 
break when us "Linux bigots" change things but forget to maintain the 
FreeBSD targets :)

You should try to have it call a public IAX server or make a sucessful 
test call though; gu...@mi... should work..

-SteveK

On Wednesday, July 2, 2003, at 09:30  PM, Scott Lambert wrote:

> I've managed to get testcall to build and run on FreeBSD.  I don't know
> that it is doing what it is supposed to do, but it does run. :-)
>
> I probably don't have my asterisk setup properly.
>
> la...@la... 
> ~/src/vendor/iaxclient/simpleclient/testcall
> 21:25:40 Wed Jul 02 $ ./testcall
> settings:
>         silence threshold: -99.000000
>         level output: off
>
>             TestCall accept some keyboard input while it's running.
>             You must hit 'enter' for your keypresses to be recognized,
>             although you can type more than one key on a line
>
>             q: drop the call and hangup.
>             0-9 * or #: dial those DTMF digits.
> Calling guest@192.168.1.101/default
> ready for keyboard input
> IAXCLIENT: Call rejected by remote
>
> -- 
> Scott Lambert                    KC5MLE                       Unix 
> SysAdmin
> la...@la...
> <iaxclient.diff>

[Iaxclient-devel] Patchset to get testcall to build on FreeBSD

[Scott L. <la...@la...>]

I've managed to get testcall to build and run on FreeBSD.  I don't know 
that it is doing what it is supposed to do, but it does run. :-)

I probably don't have my asterisk setup properly.

la...@la... ~/src/vendor/iaxclient/simpleclient/testcall
21:25:40 Wed Jul 02 $ ./testcall 
settings: 
        silence threshold: -99.000000
        level output: off

            TestCall accept some keyboard input while it's running.
            You must hit 'enter' for your keypresses to be recognized,
            although you can type more than one key on a line

            q: drop the call and hangup.
            0-9 * or #: dial those DTMF digits.
Calling guest@192.168.1.101/default
ready for keyboard input
IAXCLIENT: Call rejected by remote

-- 
Scott Lambert                    KC5MLE                       Unix SysAdmin
la...@la...      

Re: [Iaxclient-devel] Newbie's Guide to Installing wxWindows on Win32

[Steve K. <st...@st...>]

Thanks, Michael!

That's pretty much what I did when I did the first build, with wx-msw
2.4.0.

I've added these to the README in iaxclient/simpleclient/wx

-SteveK


On Wed, 2003-07-02 at 12:14, Michael Van Donselaar wrote:

> After tearing out what little hair I have left, I've finally gotten this
> figured out.
> 
> The two things that bit me were a borken make in minGW and using
> ./configure to configure wxWindows.
> 
> The docs in  wxWindows say there's two ways to compile: directly with
> the makefiles, or using configure.  ./configure is your friend right?
> Wrong.  Use the makefiles directly.
> 
> I have verified the following for WinXP and for Win2000.  Steve, feel
> free to include these in your README.
> 
> 1)  Download and run setup.exe from www.cygwin.com.
>     Install the base plus Devel/make.
>     *** You need to use the make from cygwin ***
>     The make in MinGW extras is borken.
> 
> 2)  Download MinGW-2.0.0-3.exe from www.mingw.org.
>     Install, accepting defaults
> 
> 3)  Download wxMSW-2.4.1-setup.zip from wxwindows.org
>     Install to the default directory, c:\wxWindows-2.4.1
> 
> 4)  Configure the WXWIN environment variable and add cygwin/minGW paths:
>     Right click "My Computer".  Click Properties.  Click "Advanced" tab
>     Click "Environment Variables"
>     Prepend "C:\mingw\bin;c:\cygwin\bin;" to the path
>     Create a WXWIN env variable with value "c:/wxwin-2.4.1" (Note the
>     forward slash, rather than back slash.)
> 
> 5)  Compile the wxWindows library.  The docs outline two methods.
>     *** DO NOT ./confgure -- USE THE MAKEFILES DIRECTLY ***
>     Start a cygwin session. 
>     cd c:/wxwindows-2.4.1/src/msw
>     make -f makefile.g95
> 
> 6)  Test the wxWindows library:
>     cd c:/wxwindows-2.4.1/samples/minimal
>     make -f makefile.g95 minimal
>     ./minimal.exe
> 
> 7)  Install the iaxclient sources in /usr/src/iaxclient
>     cd /usr/src/iaxclient/simpleclient/wx
>     make
>     strip wx
>     ./wx.exe
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> Iaxclient-devel mailing list
> Iax...@li...
> https://lists.sourceforge.net/lists/listinfo/iaxclient-devel

-- 
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

[Iaxclient-devel] Newbie's Guide to Installing wxWindows on Win32

[Michael V. D. <mv...@va...>]

After tearing out what little hair I have left, I've finally gotten this
figured out.

The two things that bit me were a borken make in minGW and using
./configure to configure wxWindows.

The docs in  wxWindows say there's two ways to compile: directly with
the makefiles, or using configure.  ./configure is your friend right?
Wrong.  Use the makefiles directly.

I have verified the following for WinXP and for Win2000.  Steve, feel
free to include these in your README.

1)  Download and run setup.exe from www.cygwin.com.
    Install the base plus Devel/make.
    *** You need to use the make from cygwin ***
    The make in MinGW extras is borken.

2)  Download MinGW-2.0.0-3.exe from www.mingw.org.
    Install, accepting defaults

3)  Download wxMSW-2.4.1-setup.zip from wxwindows.org
    Install to the default directory, c:\wxWindows-2.4.1

4)  Configure the WXWIN environment variable and add cygwin/minGW paths:
    Right click "My Computer".  Click Properties.  Click "Advanced" tab
    Click "Environment Variables"
    Prepend "C:\mingw\bin;c:\cygwin\bin;" to the path
    Create a WXWIN env variable with value "c:/wxwin-2.4.1" (Note the
    forward slash, rather than back slash.)

5)  Compile the wxWindows library.  The docs outline two methods.
    *** DO NOT ./confgure -- USE THE MAKEFILES DIRECTLY ***
    Start a cygwin session.=20
    cd c:/wxwindows-2.4.1/src/msw
    make -f makefile.g95

6)  Test the wxWindows library:
    cd c:/wxwindows-2.4.1/samples/minimal
    make -f makefile.g95 minimal
    ./minimal.exe

7)  Install the iaxclient sources in /usr/src/iaxclient
    cd /usr/src/iaxclient/simpleclient/wx
    make
    strip wx
    ./wx.exe

Re: [Iaxclient-devel] MinGW/cygwin/wxWindows help

[Steve K. <st...@st...>]

Michael Van Donselaar wrote:

>On Mon, 30 Jun 2003 15:58:50 -0400, you wrote:
>
>  
>
>>I installed the make from cygwin; the MinGW make isn't very good.
>>
>>(I think I added this to the READMEs already, but maybe I haven't --
>>It's been a while, and, in addition to the new baby, some dolt with a
>>truck pulled down the phone cables to my house, so I've been totally
>>disconnected).
>>
>>-SteveK
>>    
>>
>
>That did the trick.  I have just tried to follow my notes to duplicate
>this process on a Win2K machine and have gotten a couple of wx samples
>to compile and run.
>
>If it's of any use, I have written a README.wx.install-win32.
>
>
>  
>

Very cool.   Did you also need to change anything in my CVS codebase to 
make this work?  I think with this process there's still the 
libwxmswd241.a vs libwxmswd.a issue, right?

Did you also need to include windows.h?

Thanks..

Re: [Iaxclient-devel] cygwin compilation error

[Dan F. <dan...@ho...>]

Steve,

When I added the export .... to .bashrc I got further with ld. Now the =
latter is giving me the following error:

../../lib/libiaxclient.a(iaxclient_lib.o)(.text+0xbca):In function =
'iaxc_start_processing_thread':
/cygdrive/c/iaxclient/lib/iaxclient_lib.c:330 undefined reference to =
'_beginthreadex'
collect2: ld returned 1 exit status
  ----- Original Message -----=20
  From: Steve Kann=20
  To: Dan Fernandez=20
  Cc: iaxclient devel=20
  Sent: Monday, June 30, 2003 8:48 PM
  Subject: Re: [Iaxclient-devel] cygwin compilation error


  On Mon, 2003-06-30 at 19:27, Dan Fernandez wrote:=20
    Steve,
    =20
    Thanks for the tip. I added windows.h to wx.cc and I was able to =
move ahead. Now I am getting an error while linking. It=B4s telling me =
it can=B4t find wxmswd.a
    =20
    I have tried with all possible directories (/usr/local/lib, =
/usr/lib, $WXWIN/lib, $WXWIN/lib/mswd) and different names =
(libwxmsw241d.a, libwxmswd.a and wxmswd.a) and I am still getting the =
same error.
    And I am still getting the same error.
    =20
    Any ideas?=20

  Hmm, OK, so there's two issues here, which is why some of my previous =
instructions might not have worked:

  1) I originally developed this with the 2.4.0 wxwindows stuff, and =
some things might have changed in 2.4.1.  (like the "windows.h" thing).

  2) I didn't use ./configure for wxwindows build, I used makefile.g95.

  Anyway, before the whole baby thing, I got 2.4.1, and tried to do the =
"makefile.g95" build, which didn't work.  I looked into it a bit, and =
apparently that's not the "preferred" way to do the wxwindows build (I =
guess they're not maintaining those makefiles anymore), so I build with =
./configure, and then ran into some of the same problems that y'all did. =
 So, I have steps 1 - 4 of the README directions for this already =
written, but didn't get to finish them, because I realized that I ought =
to make the Makefiles smarter, so some of the steps wouldn't be =
necessary.

  I.e. ./configure installs the library as libwxmswd241.a, while the =
makefile.g95 build make libwxmswd.a, which seems like it should be a =
symlink or something to the versioned library.  The MSWin wx stuff =
doesn't have "wx-config" as far as I can see, so it's harder to make the =
link command find the library, etc.

  Okay, all that's definately not helping anyone :)

  For your question, the link line is looking for -lwxmswd and it's =
looking for it in $WXWIN/lib as libwxmswd.a  .  The versioned file you =
have (libwxmswd241.a) should work fine if you rename it, and put it in =
$WXWIN/lib.

  On the other hand, I won't be in the office tomorrow (and don't have =
Win32 boxes at home), so if people want to figure out what code changes =
are needed to make the build more "version independent", and better =
instructions, here's what I wrote so far:

  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
  Building WXWindows on Win32, with MinGW/Cygwin:

  Here's what I did to buld wxWindows 2.4.1, on Win2K, using MinGW and =
cygwin.
  This may not be the best way to do this, but it worked for me.

  1) First, I have both cygwin and MinGW installed (including cygwin's =
"make"), and MinGW
  ahead of cygwin in the PATH.

  2) I got the wxWindows 2.4.1 ZIP archive (not the -setup version), and =
unzipped
  it into the
  root of my "c" drive.  The path to this is (from cygwin or MinGW) =
c:/wxWindows-2.4.1

  3) set WXWIN environment variable to point to this location, by =
editing my .bashrc, and then
          reloading my bashrc.  here's the line:

          export WXWIN=3D"c:/wxWindows-2.4.1"

  4) as in the directions, just did this:
          cd $WXWIN
          ./configure --disable-shared
          make

  5)

  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D





     =20
      ----- Original Message -----=20
      From: Steve Kann
      To: Dan Fernandez
      Cc: iaxclient devel
      Sent: Monday, June 30, 2003 11:27 AM
      Subject: Re: [Iaxclient-devel] cygwin compilation error

      On Sat, 2003-06-28 at 18:03, Dan Fernandez wrote:=20
        Greetings!
        =20
        I am trying to build WxWin32.exe as per the instructions on the =
../simpleclient/wx/README.
        =20
        I installed and downloaded cygwin and installed wxWindows with =
the ./configure, make, and make installed (I used --enable debug and =
--disable-shared). This created a libwxmsw241d.a (I=B4ve tried renaming =
this also) on the WXWIN/lib directory.=20
        =20
        Now when I do a make I get the following errors:
        =20
        wx.cc In member function 'bool IAXFrame::GetPTTState()':
        wx.cc:441: 'VK_CONTROL' undecalred (first use this function)
        wx.cc:441: (Each undeclared identifier is reported only once for =
each function it appears in.)
        wx.cc441: 'GetAsyncKeyState' undeclared (first use this =
function)
        =20
        What have I don wrong?=20

      I don't know -- that particular constant (VK_CONTROL) is actually =
a MSWIN API constant, and not a wxWindows constant.  In my setup, the =
wxwindows headers automatically include windows.h, etc, so that was =
defined for me..

      Is that the first and only error you're getting, or is it =
complaining about not finding headers before that?

      Try adding a #include <windows.h> to the beginning of wx.cc, and =
let us know if that helps.

      -SteveK


        Thanks in advance!
        Dan=20


--=20
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed =
Linux."
          =20

--=20
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed =
Linux."
      =20

Re: [Iaxclient-devel] cygwin compilation error

[Steve K. <st...@st...>]

On Mon, 2003-06-30 at 19:27, Dan Fernandez wrote:

> Steve,
>  
> Thanks for the tip. I added windows.h to wx.cc and I was able to move
> ahead. Now I am getting an error while linking. It´s telling me it
> can´t find wxmswd.a
>  
> I have tried with all possible directories (/usr/local/lib, /usr/lib,
> $WXWIN/lib, $WXWIN/lib/mswd) and different names (libwxmsw241d.a,
> libwxmswd.a and wxmswd.a) and I am still getting the same error.
> And I am still getting the same error.
>  
> Any ideas?


Hmm, OK, so there's two issues here, which is why some of my previous
instructions might not have worked:

1) I originally developed this with the 2.4.0 wxwindows stuff, and some
things might have changed in 2.4.1.  (like the "windows.h" thing).

2) I didn't use ./configure for wxwindows build, I used makefile.g95.

Anyway, before the whole baby thing, I got 2.4.1, and tried to do the
"makefile.g95" build, which didn't work.  I looked into it a bit, and
apparently that's not the "preferred" way to do the wxwindows build (I
guess they're not maintaining those makefiles anymore), so I build with
./configure, and then ran into some of the same problems that y'all
did.  So, I have steps 1 - 4 of the README directions for this already
written, but didn't get to finish them, because I realized that I ought
to make the Makefiles smarter, so some of the steps wouldn't be
necessary.

I.e. ./configure installs the library as libwxmswd241.a, while the
makefile.g95 build make libwxmswd.a, which seems like it should be a
symlink or something to the versioned library.  The MSWin wx stuff
doesn't have "wx-config" as far as I can see, so it's harder to make the
link command find the library, etc.

Okay, all that's definately not helping anyone :)

For your question, the link line is looking for -lwxmswd and it's
looking for it in $WXWIN/lib as libwxmswd.a  .  The versioned file you
have (libwxmswd241.a) should work fine if you rename it, and put it in
$WXWIN/lib.

On the other hand, I won't be in the office tomorrow (and don't have
Win32 boxes at home), so if people want to figure out what code changes
are needed to make the build more "version independent", and better
instructions, here's what I wrote so far:

=======================
Building WXWindows on Win32, with MinGW/Cygwin:

Here's what I did to buld wxWindows 2.4.1, on Win2K, using MinGW and
cygwin.
This may not be the best way to do this, but it worked for me.

1) First, I have both cygwin and MinGW installed (including cygwin's
"make"), and MinGW
ahead of cygwin in the PATH.

2) I got the wxWindows 2.4.1 ZIP archive (not the -setup version), and
unzipped
it into the
root of my "c" drive.  The path to this is (from cygwin or MinGW)
c:/wxWindows-2.4.1

3) set WXWIN environment variable to point to this location, by editing
my .bashrc, and then
        reloading my bashrc.  here's the line:

        export WXWIN="c:/wxWindows-2.4.1"

4) as in the directions, just did this:
        cd $WXWIN
        ./configure --disable-shared
        make

5)

=======================




>  
>  
> 
>         ----- Original Message ----- 
>         From: Steve Kann
>         To: Dan Fernandez
>         Cc: iaxclient devel
>         Sent: Monday, June 30, 2003 11:27 AM
>         Subject: Re: [Iaxclient-devel] cygwin compilation error
>         
>         On Sat, 2003-06-28 at 18:03, Dan Fernandez wrote: 
>         
>         > Greetings!
>         >  
>         > I am trying to build WxWin32.exe as per the instructions on
>         > the ../simpleclient/wx/README.
>         >  
>         > I installed and downloaded cygwin and installed wxWindows
>         > with the ./configure, make, and make installed (I used
>         > --enable debug and --disable-shared). This created a
>         > libwxmsw241d.a (I´ve tried renaming this also) on the
>         > WXWIN/lib directory. 
>         >  
>         > Now when I do a make I get the following errors:
>         >  
>         > wx.cc In member function 'bool IAXFrame::GetPTTState()':
>         > wx.cc:441: 'VK_CONTROL' undecalred (first use this function)
>         > wx.cc:441: (Each undeclared identifier is reported only once
>         > for each function it appears in.)
>         > wx.cc441: 'GetAsyncKeyState' undeclared (first use this
>         > function)
>         >  
>         > What have I don wrong?
>         
>         
>         I don't know -- that particular constant (VK_CONTROL) is
>         actually a MSWIN API constant, and not a wxWindows constant. 
>         In my setup, the wxwindows headers automatically include
>         windows.h, etc, so that was defined for me..
>         
>         Is that the first and only error you're getting, or is it
>         complaining about not finding headers before that?
>         
>         Try adding a #include <windows.h> to the beginning of wx.cc,
>         and let us know if that helps.
>         
>         -SteveK
>         
>         
>         > Thanks in advance!
>         > Dan
>         
>         -- 
>           Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
>                         HorizonLive.com - collaborate . interact . learn
>            "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

-- 
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

Re: [Iaxclient-devel] MinGW/cygwin/wxWindows help

[Dan F. <dan...@ho...>]

Michael,

MinGW gave me problems also.
I did the same as you up to 6). I was able to build wxwindows from the =
start. After the make, I did make install.

To build wx I had to copy setup.h from $WXWIN/lib/wx/include/mswd-2.4/wx =
to /usr/local/include/wx.

Hope this helps.
Dan

  ----- Original Message -----=20
  From: Steve Kann=20
  To: Michael Van Donselaar=20
  Cc: iaxclient devel=20
  Sent: Monday, June 30, 2003 4:58 PM
  Subject: Re: [Iaxclient-devel] MinGW/cygwin/wxWindows help



  I installed the make from cygwin; the MinGW make isn't very good.

  (I think I added this to the READMEs already, but maybe I haven't -- =
It's been a while, and, in addition to the new baby, some dolt with a =
truck pulled down the phone cables to my house, so I've been totally =
disconnected).

  -SteveK


  On Mon, 2003-06-30 at 15:47, Michael Van Donselaar wrote:=20
Although I've been RTFM, I am at an impasse.  I want to compile on
WinXP.  Here's what I did so far:

1) Ran setup.exe from www.cygwin.com and did the basic install.

2) Installed MinGW-2.0.0-3.exe

3) Added c:\mingw to the beginning of my path as described in
http://www.mingw.org/mingwfaq.shtml#faq-usingwithcygwin

4) opened a cygwin window and editted /etc/profile to have the windows
path at the beginning, as described in
http://www.mingw.org/mingwfaq.shtml#faq-usingwithcygwin

5) Installed wxMSW-2.4.1.setup.zip

6) Added WXWIN=3Dc:/wx to the environment

I opened a cygwin window and did=20
  cd /cygdrive/c/wx
  mkdir build-debug
 ../configure --with-msw --enable-debug --enable-debug_gdb
--disable-shared

and got a complaint about no make (Well, duh)

7) blew up the ming extras zip, and copied to c:\mingw

Tried to ./configure again and got a lot of progress in the process, but
ultimately terminated with:

  checking whether make sets ${MAKE}... eval: 1: Syntax error:
Unterminated quoted string.


What am I doing wrong?


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Iaxclient-devel mailing list
Iax...@li...
https://lists.sourceforge.net/lists/listinfo/iaxclient-devel
--=20
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed =
Linux."=20

Re: [Iaxclient-devel] cygwin compilation error

[Dan F. <dan...@ho...>]

Steve,

Thanks for the tip. I added windows.h to wx.cc and I was able to move =
ahead. Now I am getting an error while linking. It=B4s telling me it =
can=B4t find wxmswd.a

I have tried with all possible directories (/usr/local/lib, /usr/lib, =
$WXWIN/lib, $WXWIN/lib/mswd) and different names (libwxmsw241d.a, =
libwxmswd.a and wxmswd.a) and I am still getting the same error.
And I am still getting the same error.

Any ideas?


  ----- Original Message -----=20
  From: Steve Kann=20
  To: Dan Fernandez=20
  Cc: iaxclient devel=20
  Sent: Monday, June 30, 2003 11:27 AM
  Subject: Re: [Iaxclient-devel] cygwin compilation error


  On Sat, 2003-06-28 at 18:03, Dan Fernandez wrote:=20
    Greetings!
    =20
    I am trying to build WxWin32.exe as per the instructions on the =
../simpleclient/wx/README.
    =20
    I installed and downloaded cygwin and installed wxWindows with the =
./configure, make, and make installed (I used --enable debug and =
--disable-shared). This created a libwxmsw241d.a (I=B4ve tried renaming =
this also) on the WXWIN/lib directory.=20
    =20
    Now when I do a make I get the following errors:
    =20
    wx.cc In member function 'bool IAXFrame::GetPTTState()':
    wx.cc:441: 'VK_CONTROL' undecalred (first use this function)
    wx.cc:441: (Each undeclared identifier is reported only once for =
each function it appears in.)
    wx.cc441: 'GetAsyncKeyState' undeclared (first use this function)
    =20
    What have I don wrong?=20

  I don't know -- that particular constant (VK_CONTROL) is actually a =
MSWIN API constant, and not a wxWindows constant.  In my setup, the =
wxwindows headers automatically include windows.h, etc, so that was =
defined for me..

  Is that the first and only error you're getting, or is it complaining =
about not finding headers before that?

  Try adding a #include <windows.h> to the beginning of wx.cc, and let =
us know if that helps.

  -SteveK



    Thanks in advance!
    Dan=20
--=20
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) =
533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed =
Linux."
      =20

Re: [Iaxclient-devel] MinGW/cygwin/wxWindows help

[Steve K. <st...@st...>]

I installed the make from cygwin; the MinGW make isn't very good.

(I think I added this to the READMEs already, but maybe I haven't --
It's been a while, and, in addition to the new baby, some dolt with a
truck pulled down the phone cables to my house, so I've been totally
disconnected).

-SteveK


On Mon, 2003-06-30 at 15:47, Michael Van Donselaar wrote:

> Although I've been RTFM, I am at an impasse.  I want to compile on
> WinXP.  Here's what I did so far:
> 
> 1) Ran setup.exe from www.cygwin.com and did the basic install.
> 
> 2) Installed MinGW-2.0.0-3.exe
> 
> 3) Added c:\mingw to the beginning of my path as described in
> http://www.mingw.org/mingwfaq.shtml#faq-usingwithcygwin
> 
> 4) opened a cygwin window and editted /etc/profile to have the windows
> path at the beginning, as described in
> http://www.mingw.org/mingwfaq.shtml#faq-usingwithcygwin
> 
> 5) Installed wxMSW-2.4.1.setup.zip
> 
> 6) Added WXWIN=c:/wx to the environment
> 
> I opened a cygwin window and did 
>   cd /cygdrive/c/wx
>   mkdir build-debug
>  ../configure --with-msw --enable-debug --enable-debug_gdb
> --disable-shared
> 
> and got a complaint about no make (Well, duh)
> 
> 7) blew up the ming extras zip, and copied to c:\mingw
> 
> Tried to ./configure again and got a lot of progress in the process, but
> ultimately terminated with:
> 
>   checking whether make sets ${MAKE}... eval: 1: Syntax error:
> Unterminated quoted string.
> 
> 
> What am I doing wrong?
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> Iaxclient-devel mailing list
> Iax...@li...
> https://lists.sourceforge.net/lists/listinfo/iaxclient-devel

-- 
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

[Iaxclient-devel] MinGW/cygwin/wxWindows help

[Michael V. D. <mv...@va...>]

Although I've been RTFM, I am at an impasse.  I want to compile on
WinXP.  Here's what I did so far:

1) Ran setup.exe from www.cygwin.com and did the basic install.

2) Installed MinGW-2.0.0-3.exe

3) Added c:\mingw to the beginning of my path as described in
http://www.mingw.org/mingwfaq.shtml#faq-usingwithcygwin

4) opened a cygwin window and editted /etc/profile to have the windows
path at the beginning, as described in
http://www.mingw.org/mingwfaq.shtml#faq-usingwithcygwin

5) Installed wxMSW-2.4.1.setup.zip

6) Added WXWIN=3Dc:/wx to the environment

I opened a cygwin window and did=20
  cd /cygdrive/c/wx
  mkdir build-debug
 ../configure --with-msw --enable-debug --enable-debug_gdb
--disable-shared

and got a complaint about no make (Well, duh)

7) blew up the ming extras zip, and copied to c:\mingw

Tried to ./configure again and got a lot of progress in the process, but
ultimately terminated with:

  checking whether make sets ${MAKE}... eval: 1: Syntax error:
Unterminated quoted string.


What am I doing wrong?

Re: [Iaxclient-devel] cygwin compilation error

[Steve K. <st...@st...>]

On Sat, 2003-06-28 at 18:03, Dan Fernandez wrote:

> Greetings!
>  
> I am trying to build WxWin32.exe as per the instructions on the
> ../simpleclient/wx/README.
>  
> I installed and downloaded cygwin and installed wxWindows with the
> ./configure, make, and make installed (I used --enable debug and
> --disable-shared). This created a libwxmsw241d.a (I´ve tried renaming
> this also) on the WXWIN/lib directory. 
>  
> Now when I do a make I get the following errors:
>  
> wx.cc In member function 'bool IAXFrame::GetPTTState()':
> wx.cc:441: 'VK_CONTROL' undecalred (first use this function)
> wx.cc:441: (Each undeclared identifier is reported only once for each
> function it appears in.)
> wx.cc441: 'GetAsyncKeyState' undeclared (first use this function)
>  
> What have I don wrong?


I don't know -- that particular constant (VK_CONTROL) is actually a
MSWIN API constant, and not a wxWindows constant.  In my setup, the
wxwindows headers automatically include windows.h, etc, so that was
defined for me..

Is that the first and only error you're getting, or is it complaining
about not finding headers before that?

Try adding a #include <windows.h> to the beginning of wx.cc, and let us
know if that helps.

-SteveK


>  
> Thanks in advance!
> Dan

-- 
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

Re: [Iaxclient-devel] init audio and subsequent streaming(win98 <<)

[Steve K. <st...@st...>]

On Sun, 2003-06-29 at 15:00, fa...@ti... wrote:

> Hi.
> 
> In iaxclient_lib the Audio is initialized and is opened as soon the application 
> starts. this is OK to initialize other stuff like os_init but there is a kind 
> of drawback in opening the audio channel even when we dont have a call session.
> 
> The drawback exactly is that we cant play anyother sound. Like if you open the 
> windows client and you want to play a ringing tone , you simply cant do it as 
> windows 98 and earlier allow only one waveoutput handle open. 
> 
> This is not an issue on windows 2k and later. not sure b/w 98 and 2k.
> 
> So wont tht be OK to openstream only when we answer a call or our call has been 
> answered. Or should we use opened audio channel to play ring tone. I think 
> playing a ring tone would be very usefull. 


Yes, the plan is to re-write a bunch of the audio code, so that it:

1) Initializes the audio system at startup, to get lists of available
devices and properties,
2) Open and close the audio device as necessary, i.e. when you select an
active call, or we want to make a ring notification, etc.
3) Allow the user to choose a particular input and output device,
perhaps also a different output device for ringing.

This would probably mean that if the user chooses a different audio
device while a call is in progress, we'd close the current device, and
open a new one, etc.




> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> Iaxclient-devel mailing list
> Iax...@li...
> https://lists.sourceforge.net/lists/listinfo/iaxclient-devel

-- 
  Steve Kann - Chief Engineer - 520 8th Ave #2300 NY 10018 -  (212) 533-1775
                HorizonLive.com - collaborate . interact . learn
   "The box said 'Requires Windows 95, NT, or better,' so I installed Linux."

[Iaxclient-devel] init audio and subsequent streaming(win98 <<)

[<fa...@ti...>]

Hi.

In iaxclient_lib the Audio is initialized and is opened as soon the application 
starts. this is OK to initialize other stuff like os_init but there is a kind 
of drawback in opening the audio channel even when we dont have a call session.

The drawback exactly is that we cant play anyother sound. Like if you open the 
windows client and you want to play a ringing tone , you simply cant do it as 
windows 98 and earlier allow only one waveoutput handle open. 

This is not an issue on windows 2k and later. not sure b/w 98 and 2k.

So wont tht be OK to openstream only when we answer a call or our call has been 
answered. Or should we use opened audio channel to play ring tone. I think 
playing a ring tone would be very usefull. 

Re: [Iaxclient-devel] Dialing after registration.

[<fa...@ti...>]

Quoting Darren Smith <da...@ba...>:

> Hi
> 
> I've been tinkering with the WinIAX (MSVC) client too, learning Windows API
> basically
> (*spit*).
> 
> I've now added menus to the main form, as well as created 'Registration',
> 'About' &
> 'Options' dialogs....
> 
> It also now registers to asterisk and supports incoming calls etc.
>
So did you do anything to dial or send DTMF when you have registered and 
without actually placing a call. I guess that is one reason to have registratio 
option.  
> In terms of the external calls, all i did was see if the number had an @ sign
> in.
> 
> If it had an @ sign I just dial the iax call as they typed, otherwise i just
> use:
> <user>:<pass>@<server>/<what-they-typed> stealing the info straight off the
> registration
> form.
> 
Well I am using separate box for username pass and host. I guess that is easy 
to understand for users.

> Once i've tidied my code up a bit i'll stick it up somewhere for people to
> have a look at,
> being a VC++ n00b it's a tad messy atm ;-)
> 
> Oh i've also started hacking 'ringtone','playback' and 'microphone' voice
> device controls
> too, having fun with combo boxes atm.
> 
> HWND RecordBox = GetDlgItem(m_hwndOptionsDlg,IDC_RECORD);
> SendMessage(RecordBox,   LB_RESETCONTENT , 0, 0);
> SendMessage(RecordBox, LB_ADDSTRING, 0, (LPARAM) (LPCTSTR) pwic.szPname);
> 
> Can't believe windows C coding was so prehistoric tbh, unless i'm doing
> things the hard
> way, which I usually do ;-)
> 
Well we do have MFC that makes things a lot easier. But reuires a dll which is 
sometimes not available on systems like windows95 or fresh windows98. but i 
guess is available on about 95-98% windows machines now.
> Regards
> 
> Darren
> 
> ----- Original Message ----- 
> From: <fa...@ti...>
> To: <iax...@li...>
> Sent: Sunday, June 29, 2003 4:24 PM
> Subject: [Iaxclient-devel] Dialing after registration.
> 
> 
> > Hi.
> >
> > I was working on WinIAX client (MSVC one). I checked the wxWindows client
> also.
> > In SIP client when we register we usually can dial a number by pressing
> the
> > digits and pressing the dial button.
> > But in wxWindows when we register we cant just press digits to dial. we
> still
> > need to make a call to asterisk gateway by putting the IAX URI in the
> dial
> > string and then have to press dial button. There you can then press digits
> to
> > go to specific extension.
> >
> > This is a bit different than what I have seen in SIP phones. Is this the
> way
> > IAX is supposed to work. To register but not to send DTMF/Dial to server
> untill
> > you also specify iax uri and dial to it.
> >
> > Am I missing something or we should get it to work like the normal SIP
> phones
> > would work.
> >
> >
> > -------------------------------------------------------
> > This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> > Data Reports, E-commerce, Portals, and Forums are available now.
> > Download today and enter to win an XBOX or Visual Studio .NET.
> > http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> > _______________________________________________
> > Iaxclient-devel mailing list
> > Iax...@li...
> > https://lists.sourceforge.net/lists/listinfo/iaxclient-devel
> >
> 

Re: [Iaxclient-devel] Dialing after registration.

[Darren S. <da...@ba...>]

Hi

I've been tinkering with the WinIAX (MSVC) client too, learning Windows API basically
(*spit*).

I've now added menus to the main form, as well as created 'Registration', 'About' &
'Options' dialogs....

It also now registers to asterisk and supports incoming calls etc.

In terms of the external calls, all i did was see if the number had an @ sign in.

If it had an @ sign I just dial the iax call as they typed, otherwise i just use:
<user>:<pass>@<server>/<what-they-typed> stealing the info straight off the registration
form.

Once i've tidied my code up a bit i'll stick it up somewhere for people to have a look at,
being a VC++ n00b it's a tad messy atm ;-)

Oh i've also started hacking 'ringtone','playback' and 'microphone' voice device controls
too, having fun with combo boxes atm.

HWND RecordBox = GetDlgItem(m_hwndOptionsDlg,IDC_RECORD);
SendMessage(RecordBox,   LB_RESETCONTENT , 0, 0);
SendMessage(RecordBox, LB_ADDSTRING, 0, (LPARAM) (LPCTSTR) pwic.szPname);

Can't believe windows C coding was so prehistoric tbh, unless i'm doing things the hard
way, which I usually do ;-)

Regards

Darren

----- Original Message ----- 
From: <fa...@ti...>
To: <iax...@li...>
Sent: Sunday, June 29, 2003 4:24 PM
Subject: [Iaxclient-devel] Dialing after registration.


> Hi.
>
> I was working on WinIAX client (MSVC one). I checked the wxWindows client also.
> In SIP client when we register we usually can dial a number by pressing the
> digits and pressing the dial button.
> But in wxWindows when we register we cant just press digits to dial. we still
> need to make a call to asterisk gateway by putting the IAX URI in the dial
> string and then have to press dial button. There you can then press digits to
> go to specific extension.
>
> This is a bit different than what I have seen in SIP phones. Is this the way
> IAX is supposed to work. To register but not to send DTMF/Dial to server untill
> you also specify iax uri and dial to it.
>
> Am I missing something or we should get it to work like the normal SIP phones
> would work.
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> Iaxclient-devel mailing list
> Iax...@li...
> https://lists.sourceforge.net/lists/listinfo/iaxclient-devel
>

[Iaxclient-devel] Dialing after registration.

[<fa...@ti...>]

Hi.

I was working on WinIAX client (MSVC one). I checked the wxWindows client also.
In SIP client when we register we usually can dial a number by pressing the 
digits and pressing the dial button.
But in wxWindows when we register we cant just press digits to dial. we still 
need to make a call to asterisk gateway by putting the IAX URI in the dial 
string and then have to press dial button. There you can then press digits to 
go to specific extension.

This is a bit different than what I have seen in SIP phones. Is this the way 
IAX is supposed to work. To register but not to send DTMF/Dial to server untill 
you also specify iax uri and dial to it.

Am I missing something or we should get it to work like the normal SIP phones 
would work.