irontec
Support for MRCPv2 RFC 6787
Hi @gauravbhagwat
The easies approach to implement this is mask this streams as RTP as both protocol seem to share a lot (setup in SDP, ports, and formats).
- Update the SDP parser so handle this media types here
- Add a new packet parser here to create rtp_streams from received MRCP packets like we do for RTP packets
If the parser creates rtp streams correctly, and they match the configured SDP of a SIP message, it will be displayed in call flows. Then we can enhance the logic to display RTP or MRCP in the arrow based on the stream type.
Regards!
Thanks for the pointers. I will start this project.
Regards, Gaurav Bhagwat
On Fri, 7 Sep 2018 at 14:45, Kaian [email protected] wrote:
Hi @gauravbhagwat https://github.com/gauravbhagwat
The easies approach to implement this is mask this streams as RTP as both protocol seem to share a lot (setup in SDP, ports, and formats).
- Update the SDP parser so handle this media types here https://github.com/irontec/sngrep/blob/master/src/sip.c#L671
- Add a new packet parser here https://github.com/irontec/sngrep/blob/master/src/capture.c#L786 to create rtp_streams from received MRCP packets like we do for RTP packets https://github.com/irontec/sngrep/blob/master/src/rtp.c#L160
If the parser creates rtp streams correctly, and they match the configured SDP of a SIP message, it will be displayed in call flows. Then we can enhance the logic to display RTP or MRCP in the arrow based on the stream type.
Regards!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/irontec/sngrep/issues/254#issuecomment-419377003, or mute the thread https://github.com/notifications/unsubscribe-auth/AH-gN0KrPKIzvbFOy3Ud_3avt-ovkRr7ks5uYjkjgaJpZM4WchyQ .