Hi list,
Let me expose you a session update scenario to see how should the RTP
packets be forwarded after the update command:
- A session is setup in the RTPproxy.
U 2009/06/03 17:20:34.502864 127.0.0.1:55660 -> 127.0.0.1:7899
8621_88 U 229094d2-8d43...@172.18.2.110 1.1.1.1 16454
2f974f3a19a27caco1;1
U 2009/06/03 17:20:34.503319 127.0.0.1:7899 -> 127.0.0.1:55660
8621_88 40980 9.9.9.9.
U 2009/06/03 17:20:36.144789 127.0.0.1:55332 -> 127.0.0.1:7899
8620_92 L 229094d2-8d43...@172.18.2.110 2.2.2.2 14046
2f974f3a19a27caco1;1 9B3D5CCB0A55EFE3FD500996F5BB5514;1
U 2009/06/03 17:20:36.146491 127.0.0.1:7899 -> 127.0.0.1:55332
8620_92 62166 9.9.9.9.
1.1.1.1:16454 <--------> 9.9.9.9:40980 (RTPproxy) 9.9.9.9:62166
<---------> 2.2.2.2:14046
- RTPproxy receives and UPDATE command and it keeps receiving RTP
packets from the first source
U 2009/06/03 17:20:39.465107 127.0.0.1:55660 -> 127.0.0.1:7899
8621_89 U 229094d2-8d43...@172.18.2.110 3.3.3.3 35108
9B3D5CCB0A55EFE3FD500996F5BB5514;1 2f974f3a19a27caco1;1
U 2009/06/03 17:20:39.500070 127.0.0.1:7899 -> 127.0.0.1:55660
8621_89 62166 9.9.9.9.
1.1.1.1:16454 <--------> 9.9.9.9:40980 (RTPproxy) 9.9.9.9:62166
<---------> 2.2.2.2:14046
9.9.9.9
:62166 <--------- 3.3.3.3:35108
In some cases the RTP mapping changes and the RTP received from
1.1.1.1 is forwarded to 3.3.3.3, but in some other cases, it is still
sent to 2.2.2.2.
How should the RTPproxy manage the following UPDATE situation? Should
it change the IP addresses mapping to a different one than the first
call established or should it change it to the first RTP packet it
receives after the UPDATE (no matter if it was the same one as before
or not) ?
I hope you can give me a hint on that.
Regards,
Oriol.
_______________________________________________
Users mailing list
Users@rtpproxy.org
http://lists.rtpproxy.org/mailman/listinfo/users
