[Gpephone-devel] How to make phoneserver adapt to different typesof modem?

[sunxiaohui]

Hi all:

This is a good idea. I think we need not make all the AT command configuable, since some of them is MANDATORY in the specification of 3GPP 27.007/27.005. As to the OPTIONAL commands, we can query its implementation before we use it. 

----------------------------------------------------------------
Xiaohui Sun 
Email：sunxiaohui at dsp.ac.cn
Tel: +86 10 6256 5615 ext.301

DSP and Network Research Center
Institute of Acoustics, Chinese Academy of Sciences
Beisihuan West Road 21, Beijing 100080, China
----------------------------------------------------------------



发件人： yu tang
发送时间： 2007-03-15 13:08:52
收件人： gpephone-devel at linuxtogo.org
抄送： 
主题： [Gpephone-devel] How to make phoneserver adapt to different typesof modem?

Hi, 
It is very important to have a good structure of phoneserver to make it adapt to different types of modem. 
Here is some idea which may be a start of discussion. 
A config file is read when phoneserver is started. The config file includes the configuration information of modem, 
Such as: 
SERIAL_PORT: {/dev/ttyS0} 
SERIAL_BAUDRATE: {...} 
ATCOMMAND_BUFFER_SIZE:{...} 
//format of AT command sent and repsonse message 
//FUNCTION : COMMAND: RESPONSE 
DIAL:{ ATD<number>;}:{OK} 
CONFERENCE:{+CHLD=3 }: {PPURC:8192,,4} 
….. 
So each config file corresponds to one different modem. When phoneserver starts, it read the config file. 
When phoneserver need to DIAL a call out, it founds out that the command should be DIAL:{ ATD<number>;}:{OK}, and the response should be OK. 
The idea is very rough, comments are welcome. 
Thanks. 


雅虎免费邮箱-3.5G容量，20M附件 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.linuxtogo.org/pipermail/gpephone-devel/attachments/20070316/30a6c258/attachment.htm