RTP Payload Multi-decoder

RTP Payload Multi-decoder Summary The purpose of this project is to create a C++ library to decode RTP packets payload using USCI - Unified Speech Codec Interface from Intel® Integrated Performance Primitives (preferred method) and a C# wrapper in order to use that library in C# managed code projects. For all other libraries not included in Intel® Integrated Performance Primitives, acceptance is required and the full source code has to be delivered. Details A. Providing .pcap file format examples containing different RTP payload types, the prototype has to be able to decode all RTP streams included in each file to different u-Law buffered files on the disk and then, convert all u-Law buffer files to Wave GMS format when the complete stream is decoded. B. Buffering all streams to a temporary u-Law file format is preferred but other methods could be also welcome requesting acceptance in advance. C. At least, but not limited to, the prototype has to be able to convert the following payload types: G711, G729, G728, G722, G726, G723, GMS and their variants. D. RTP streams could contain different payload types in the same stream, the algorithm has to detect and convert each packet from the received payload type to the common u-Law buffers on the fly. E. RTP packet timestamp synchronization is required. F. The main function for decoding should work by passing parameters such as payload, payload type, payload length and returning the packet payload converted to u-Law buffer(s). All received u-Law buffers will be time synchronized and written to a temporary file timely or sized based. G. Because the Unified Speech Codec Interface from Intel® Integrated Performance Primitives, C++ code has to be used to interface with the Intel library, it is mandatory to use C# managed code in the rest of the modules. For all C++ modules, a C# wrapper is mandatory. Please try to minimize the use of C++ to the best of your abilities. H. Full source code has to be provided with no exception, and be fully documented. I. Any proposed change to this approach has to be proposed and accepted by Trisys. Changes could be accepted if they improve the solution or performance and full source code and explanations are required. J. Confidentiality document has to be signed. K. Trisys, Inc. will own the property and rights of the developed solution. L. Prior experience with technologies above has to be clearly indicated by submitting your resume and details of the projects M. The acceptance criteria will be running voice files with different RTP payload(s) and their successful conversion. The quality of the converted files has to be of the telephone conversation quality. Time frame • 2/3 weeks. Please do NOT submit your proposal unless you have significant hands-on expertise in this area.