You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m stuck with an RTP related problem. Perhaps you could help me with this?
UserA => SBC-A => AS => SBC-B => UserB
UserA and UserB are MTS scenarios. The case is about to respond by UserB with 180+SDP & sending early media. In standard configuration original RTP stream iis delivered do UserB (incl. original SSRC headers). MTS scenario for UserA receives such traffic (receiveMessageRTPFLOW OK - same SSRC as originating one).
Oracle SBC offers the possibility to send locally generated stream (local media playback from WAV file). So after 180 being sent to UserA SBC-A starts sending its own stream (ignoring any media coming from UserB). Such stream has of course completely different RTP headers (ssrc/seqnum/time). In such situation MTS is ignoring the stream (which still reaches correct IP/port) and receiveMessageRTPFLOW timed out.
Later on after 200/ACK both users send/receive media without any problems in all cases (forwarded or local stream on SBC-A).
Do you have any suggestion or hint where to check? Or something in protocol configuration should be modified (for udp/rtp/rtpflow)? It seems I cannot set route.MESSAGE_ID for RTPFLOW config since it is not what UserB emits – so what else?
BTW it there any other distribution list for MTS or this is the right/only place?
Regards,
Mariusz
The text was updated successfully, but these errors were encountered:
Hi all,
I’m stuck with an RTP related problem. Perhaps you could help me with this?
UserA and UserB are MTS scenarios. The case is about to respond by UserB with 180+SDP & sending early media. In standard configuration original RTP stream iis delivered do UserB (incl. original SSRC headers). MTS scenario for UserA receives such traffic (receiveMessageRTPFLOW OK - same SSRC as originating one).
Oracle SBC offers the possibility to send locally generated stream (local media playback from WAV file). So after 180 being sent to UserA SBC-A starts sending its own stream (ignoring any media coming from UserB). Such stream has of course completely different RTP headers (ssrc/seqnum/time). In such situation MTS is ignoring the stream (which still reaches correct IP/port) and receiveMessageRTPFLOW timed out.
Later on after 200/ACK both users send/receive media without any problems in all cases (forwarded or local stream on SBC-A).
Do you have any suggestion or hint where to check? Or something in protocol configuration should be modified (for udp/rtp/rtpflow)? It seems I cannot set route.MESSAGE_ID for RTPFLOW config since it is not what UserB emits – so what else?
BTW it there any other distribution list for MTS or this is the right/only place?
Regards,
Mariusz
The text was updated successfully, but these errors were encountered: