This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP-L138 device based media gateway design querries

Other Parts Discussed in Thread: OMAP-L138

Hi;

In my design I am using OMAP-L138 device and the application is some thing like multi stack media gateway. Where main media gateway application running on ARM core and telephony-codec's will be running on DSP core.

There are multiple peripheral cards of variety types like FXS/FXO/ENM/PRI etc and all are connected for the purpose of inter-voice communication over 4-MB TDM highway.

In our application we will be using variety of telephony-codecs like G711A/U laws, G722. G726 etc.

Regarrding the design, following are my querries.

1. The codec implementation (software) supported by TI is only the payload conversion and RTP streaming and time stamping needs to be handled by application. This is my understanding, is it true?

2. If above true and since my input is to McBSP is already G711-A law compressed; in this scenario to use G711 codec I just need to buffer the packets and pass them to RTP stack is this OK?

3. In McBSP there is some thing called companding hardware, which provides 16 bit linear data. Is there any provision to enable/disable the companding hardware per time slot basic(channel) and is it dynamic.

4.In my design I need to use 3 ethernet interfaces (MAC), is there any sample design which uses multiple MAC's with OMAP-L138. If available please give details.

regards

Prafulla