Re: [Iaxclient-devel] Some proposed feature additions to the library

[Dan <dt...@fx...>]

Hi,

>>Steve & Company,
>>
>>First, thank you for the codec code.  I will be releasing a new version
>>of the free version of IAX Phone with the codec-enabled library included.
>
> Same here.  I'm loving iLBC.
Same here for DIAX.
A pre 0.9.9b is already available for download (without the help file yet)

>
>>I'm working on a few improvements (or at least additions) to the
>>library, and I want some response.  Some of these are already coded,
>>while others are still on the drawing board.  These include:
>>
>>- New registration routine
>>- Client-Side Call Recording
>>- Multi-Path Audio Output (and possibly input)
>>- Onboard Mixing for 3-way Calling
>>- URL Send/URL Event
>>- DTMF Received Event
>>
>>-= New Registration Routines =-
>>
>>I've created an iaxc_register2 function that creates a managed list of
>>registrations and their states.  It required a single change to the
>>existing registration structure -- the addition of a regid integer to
>>hold the registration identifier.  This value (simply an incrmenting
>>integer) is generated when the registration is created and is used to
>>identify the registration during callbacks (events).  The function call
>>returns the newly generated registration ID, or negative values to
>>indicate errors.
>
> Great idea. I'm all for it.
>>The general purpose of this change was to allow the client to display
>>registration status on an account-by-account basis, and to track message
>>counts for each account.  This is a very minor tweak (and I suppose we
>>could have returned the registration information in the user message,
>>but this seems to be a more elegant approach).
>
I have modified iaxclient library for DIAX usage in order ti achieve 
extended registration functionality.
It can register with up to 8 servers and get live registration status (good 
to test the link too)
for each server individualy and with the message info (new/old).
I'll publish the changes in the source together with the final 0.9.9x.
Maybe we cand find a common change to keep the library as standard as 
possible.

>>Please give me thoughts on these features.  Let me know if they would be
>>useful to you, and also if you see any reason NOT to include them.
>>Obviously Steve K will be the final decision maker, but I would like to
>>see what others think of these additions.
>
One otther small change made by me is to send user messages as codes, not as 
message strings.
In this way I can better handle the multilanguage support,.

> I see no reason to not include any of these changes.

All of them can be usefull for some of us and for some of them a compiler 
directive can be
used to minimize the library dimension if not used.
>
> I would love to see the new registration scheme implemented.
Will be great to have just one, included in the library.

The main feature requested by DIAX users is to put a call on hold to place a 
second call
and to have attended transfer capabilities.

Best regards,
Dan