[asterisk-dev] GSM trunks & Dahdi - New funcionality Request for discussion

[Tzafrir Cohen]

On Thu, Nov 19, 2009 at 03:06:00PM +0000, Odicha wrote:

> In a abstraction layer environment with an own library and AT
> translation at dahdi driver it would be somethig like this:
> 
> case SEBI_STATE_PRE_ANSWER
> 	if (h == CALL_ANSWER_ACK)
> 		sebi->ev.e = SEBI_EVENT_ANSWER_ACK
> 		....
> 
> and the "translation" between "AT^DDSETEX=2\r" and CALL_ANSWER_ACK would
> be done at dahdi driver level. So in hdlc frames between library & dahdi
> won't have AT commands but our own signalling abstraction layer events
> and frames.

Is there a good reason to do this translation in kernel space?

One potential good reason: if the driver needs to allocate resources
that may be used by different userspace processes and needs to
understand the AT commands in order to do so.

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir