I got a problem with mediaproxy (mediarelay). The media relay is in front of our Teles C4 platform.
After an INVITE from client to opensips to Teles (C4) the first teles audiocodes starts sending RTP (0.3 seconds) from 31.168.32.35, after this our mediarelay starts sending audio to 31.168.32.35. Nothing strange here. This Teles gateway can not forward the call and the call is hunted to the second gateway, 31.168.32.36. After this the first 183 SDP is sent from teles (C4) to opensips with 31.168.32.36 in the connection information. Teles states it is correct to sent audio from the first audiocodes, then hunt to the second and only put the second ip in the SDP packet. Problem is mediaproxy/mediarelay starts sending audio to the first audiocodes and does not alter the stream because ip and port are the same in all sip packets. Question is, can I change the behavior of de mediaproxy (latching only to client side) or, if not, how can I prove to Teles the behavior of C4 in incorrect? Debug information: sip client: 183.33.152.6 opensips proxy: 82.145.12.237 media-relay: 82.145.12.229 teles audiocodes 1: 31.168.32.35 teles audiocodes 2: 31.168.32.36 media-relay: debug: Received new SDP offer media-relay: StreamListenerProtocol starting on 50400 media-relay: StreamListenerProtocol starting on 50401 media-relay: StreamListenerProtocol starting on 50402 media-relay: StreamListenerProtocol starting on 50403 media-relay: debug: Added new stream: (audio) 183.33.152.6:7082 (RTP: Unknown, RTCP: Unknown) <-> 82.145.12.229:50400 <-> 82.145.12.229:50402 <-> Unknown (RTP: Unknown, RTCP: Unknown) media-relay: debug: created new session [email protected]: [email protected] (677067DA12947590) --> [email protected] media-relay: debug: Got traffic information for stream: (audio) 183.33.152.6:7082 (RTP: Unknown, RTCP: Unknown) <-> 82.145.12.229:50400 <-> 82.145.12.229:50402 <-> Unknown (RTP: 31.168.32.35:22440, RTCP: Unknown) media-relay: debug: Got traffic information for stream: (audio) 183.33.152.6:7082 (RTP: Unknown, RTCP: Unknown) <-> 82.145.12.229:50400 <-> 82.145.12.229:50402 <-> Unknown (RTP: 31.168.32.35:22440, RTCP: 31.168.32.35:22441) media-relay: debug: updating existing session [email protected]: [email protected] (677067DA12947590) --> [email protected] media-relay: debug: Received updated SDP answer media-relay: debug: Got initial answer from callee for stream: (audio) 183.33.152.6:7082 (RTP: Unknown, RTCP: Unknown) <-> 82.145.12.229:50400 <-> 82.145.12.229:50402 <-> 31.168.32.36:28620 (RTP: 31.168.32.35:22440, RTCP: 31.168.32.35:22441) media-relay: debug: Got traffic information for stream: (audio) 183.33.152.6:7082 (RTP: 183.33.152.6:7082, RTCP: Unknown) <-> 82.145.12.229:50400 <-> 82.145.12.229:50402 <-> 31.168.32.36:28620 (RTP: 31.168.32.35:22440, RTCP: 31.168.32.35:22441) media-relay: debug: updating existing session [email protected]: [email protected] (677067DA12947590) --> [email protected] media-relay: debug: Received updated SDP answer media-relay: debug: Unchanged stream: (audio) 183.33.152.6:7082 (RTP: 183.33.152.6:7082, RTCP: Unknown) <-> 82.145.12.229:50400 <-> 82.145.12.229:50402 <-> 31.168.32.36:28620 (RTP: 31.168.32.35:22440, RTCP: 31.168.32.35:22441) media-relay: debug: Got traffic information for stream: (audio) 183.33.152.6:7082 (RTP: 183.33.152.6:7082, RTCP: 183.33.152.6:7083) <-> 82.145.12.229:50400 <-> 82.145.12.229:50402 <-> 31.168.32.36:28620 (RTP: 31.168.32.35:22440, RTCP: 31.168.32.35:22441) media-relay: debug: removing session [email protected]: [email protected] (677067DA12947590) --> [email protected] media-relay: (UDP Port 50400 Closed) media-relay: (UDP Port 50401 Closed) media-relay: (UDP Port 50402 Closed) media-relay: (UDP Port 50403 Closed) -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/mediaproxy-latching-tp7596774.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
