According to the debug output, it seems that your Gridborg device is not sending any media packets to the relay. The last 2 entries from the media relay log, indicate that the callee (200.200.200.200) has sent both a RTP and a RTCP packet resulting in its addresses being discovered by mediaproxy, however no packet was received from the caller side, so mediaproxy doesn't know the caller media addresses, thus it can't forward the media because it doesn't know where to.
debug: Got initial answer from callee for stream: (audio) 10.10.101.101:20752 (RTP: Unknown, RTCP: Unknown) <-> 100.100.100.100:50020 <-> 100.100.100.100:50022 <-> 200.200.200.200:13320 (RTP: Unknown, RTCP: Unknown) debug: Got traffic information for stream: (audio) 10.10.101.101:20752 (RTP: Unknown, RTCP: Unknown) <-> 100.100.100.100:50020 <-> 100.100.100.100:50022 <-> 200.200.200.200:13320 (RTP: 200.200.200.200:13320, RTCP: Unknown) debug: Got traffic information for stream: (audio) 10.10.101.101:20752 (RTP: Unknown, RTCP: Unknown) <-> 100.100.100.100:50020 <-> 100.100.100.100:50022 <-> 200.200.200.200:13320 (RTP: 200.200.200.200:13320, RTCP: 200.200.200.200:13321) Initially mediaproxy doesn't know the address of neither endpoint (all show Unknown). Then the callee sends a RTP packet followed by a RTCP packet and you can see in the log as the addresses become known. Yet the caller addresses remain Unknown because it has never sent a packet to the relay. I'd look for the problem in the device itself or the router that does the NAT traversal for the device. Your server side configurations are fine. On 20 Jan 2012, at 0:02, Jock McKechnie wrote: > Greetings; > > I've been deploying OpenSIPS (v1.7.0) and MediaProxy (from git) a lot > lately (huzzah for reliable and flexible software) and have been > having a great time... until today, and naturally, this system is the > one that I have my colleagues breathing down my neck on. > > Gridborg -> OpenSIPS + MediaProxy -> Client > > Signalling works perfectly. Call comes up normally, call tears down > normally. However when audio comes _back_ from the client it gets to > MediaProxy and is not passed on to gridborg. > > From the MediaProxy debugging I believe that MP isn't able to > determine the RTP port on the gridborg system and so cannot pass the > audio back, but I've been staring at the signalling all day long and I > just can't work out why not. I have several other systems doing this > (gridborg -> OpenSIPS+MediaProxy) without issue, AND if I use > something more conventional (Asterisk) it seems to work just fine, > although this may be a false symptom. > > I could really, really use some help. I've included everything I could > think of trapping, if you think I should find something else, let me > know and I'll reproduce. > > 10.10.101.101 is the gridborg system, > 100.100.100.100 is the public IP of the OpenSIPS+MediaProxy server, > 200.200.200.200 is the public IP of the client system. > We're sending the call to (123) 456-7890. > (Obviously I've audited the trace/configs to put these addresses in, > but that's the only editing) > > OpenSIPS config: > http://pastebin.com/YvRyuJjZ > > MediaProxy config: > http://pastebin.com/QjYUzJpp > > SIP trace: > http://pastebin.com/d1f9MxPA > > MediaProxy debug: > http://pastebin.com/PLGNhnR9 > > My deepest thanks to anyone who can shed light on this; > > - Jock > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- Dan _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
