On 31 Mar 2017, at 17:18, Andreas Bøckmann wrote:
> Hello,
>
> I am hoping somebody can explain to me how MediaProxy receives "traffic
> information" from OpenSIPS.
Mediaproxy doesn't receive traffic information from OpenSIPS. Mediaproxy
determines endpoint addresses based in received media from endpoints. If you
see Unknown in those log lines from mediaproxy, it means it has not received
any RTP/RTCP traffic from that endpoint, so it cannot determine where to
forward the streams, thus no audio.
>
> I am trying to use two different GWs to reach PSTN but I am experiencing
> no-audio using one of them and the only thing I can see that is different is
> in MediaProxy logs.
> .
> The call flow is similar (late offer).
>
> --> INVITE
> <- 183/180
> <- 200 OK SDP
> --> ACK SDP
>
> Got traffic information for stream: (audio) Unknown (RTP: 1.2.3.4:10002,
> RTCP: Unknown) <-> 2.3.4.5:16388 <-> 2.3.4.5:16390 <-> 4.5.6.7:11390 (RTP:
> 4.5.6.7:11390, RTCP: 4.5.6.7:11391)
>
> Got traffic information for stream: (audio) Unknown (RTP: 1.2.3.4:1,
> RTCP: Unknown) <-> 2.3.4.5:16384 <-> 2.3.4.5:16386 <-> 3.4.5.6:22458 (RTP:
> Unknown, RTCP: Unknown)
>
> As I see this MediaProxy has all 3 relevant IPs in both cases; but it's not
> set in "RTP:" for the call which does not have audio so I am wondering how
> this can be?
>
> What's the missing piece here so that MediaProxy knows "3.4.5.6" is "RTP:" ?
>
>
> //Andreas
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Dan
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
