5 Aug
2014
5 Aug
'14
7:06 p.m.
On Tue, Aug 5, 2014 at 11:06 AM, Richard Fuchs <rfuchs(a)sipwise.com> wrote:
On 05/08/14 11:01 AM, Paul Belanger wrote:
Thanks, I had a typo. I believed I fixed it.
A new piece to the puzzle, if I place the webrtc client on hold then
off, audio is setup properly with rtpengine. However, I cannot find
the reason for this yet. Clearly the "RTP output wanted, but no
crypto suite was negotiated" message is the cause of the issue but not
sure why the hold fixes it.
--
Paul Belanger | PolyBeacon, Inc.
Jabber: paul.belanger(a)polybeacon.com | IRC: pabelanger (Freenode)
Github: https://github.com/pabelanger | Twitter: https://twitter.com/pabelanger
I was hoping somebody could confirm the following is a _normal_ log
file for rtpengine. Specifically I am curious of the 'Successful STUN
binding request from' messages are continuously logged.
Chrome seems to be doing this during normal operation. I have no idea why
though, perhaps some sort of keep-alive. You should be able to confirm
successful STUN communication with Wireshark.
I did notice that you're responding to an RTP/SAVPF offer with an RTP/SAVP
answer. That might be the source of your issue.