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

[JIANG Dan RD-ILAB-PEK]

Yes.
 
This method could deal with some asynchronous calls, such as Dial out, Hold, Hangup, etc. 
 
But how does it handler the unsolited event, such as incoming call, call status indication? 
For different modem, the format of message  which is sent to phoneserver may be different.
Phoneserver has to analysis the message with certain rules to get proper information.
 
How could this be solved?
 
Is there other method available?
 
 
 
 

________________________________

From: gpephone-devel-bounces at linuxtogo.org [mailto:gpephone-devel-bounces at linuxtogo.org] On Behalf Of yu tang
Sent: 2007年3月15日 13:00
To: gpephone-devel at linuxtogo.org
Subject: [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. 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.linuxtogo.org/pipermail/gpephone-devel/attachments/20070315/06cc7e93/attachment.htm