Re: Globalcall DTMF capture

David Sugar <[email protected]>
Newsgroups gmane.comp.gnu.bayonne.devel
Organization GNU Telephony
Message-ID <[email protected]>
If you come up with patches that improve stability or usability of the 
existing server, those are always welcome, as it will be continued to be 
activily maintained.  I am just looking to avoid adding anything 
experimentally that risks making the current server any less stable.

Julien Chavanton wrote:
> Sure but since we reached stability with Bayonne 1 GlobalCall, I think
> we will continue to run the stable version for quite some time.
> I will look after this.
> 
> Julien
> 
> 
> -----Original Message-----
> From: David Sugar [mailto:[email protected]] 
> Sent: May 1, 2005 3:35 PM
> To: Julien Chavanton
> Cc: [email protected]
> Subject: Re: [Bayonne-devel] Globalcall DTMF capture
> 
> A good place to experiment with this might be on the new server as soon 
> as I get the globalcall driver a bit more complete.
> 
> Julien Chavanton wrote:
> 
>>I have found some problem with DTMF events sometime.
>>
>> 
>>
>>I heard that  "dx_getdig()" is the preferred way to detect DTMF rather
> 
> 
>>then "dx_setevtmsk(devmap[portidx].chdev, DM_DIGITS)"
>>
>> 
>>
>>I think we may want to modify the global call drivers to use this 
>>alternative.
>>
>> 
>>
>>Julien
>>
>>
>>
> 
> ------------------------------------------------------------------------
> 
>>_______________________________________________
>>Bayonne-devel mailing list
>>[email protected]
>>http://lists.gnu.org/mailman/listinfo/bayonne-devel

_______________________________________________
Bayonne-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bayonne-devel
dyfet.vcf (text/x-vcard, 187 B)
begin:vcard
fn:David Sugar
n:Sugar;David
org:GNU Telephony
adr:;;;;;;USA
email;internet:[email protected]
x-mozilla-html:FALSE
url:http://www.gnutelephony.org
version:2.1
end:vcard
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.