> Is the SIP signaling still going fine via websocket? Do you get callee
> ringing?
>
> Cheers,
> Daniel
Hello Daniel
Actually SIP signalling goes perfect, and i can see in RTP asterisk log that RTP packets are being sent, so I suppose there is something stuck somewhere in RTP maybe related with RTP Engine
>Hi,
>
>If you are using rtpengine for the rtp you might have to upgrade to a
>newer version.
>
>On my system crypto negotiation in rtpengine started failing after a
>openssl update in January. Recompiling a newer version from git fixed that.
>
>regards
>
>M
I updated to latest version through git but still stuck there. Now I can see that the config file (ngcp-rtpengine in etc default) has changed so I'm not sure how should this impact (not ADDRESS neither ADV ADDRESS now I see an Interfaces parameter)
I also find for some reason very possible that somehow rtp traffic is not getting through. ICE candidates are being negotiated, so I feel that the route is clear, so maybe there might be some crypto issues as you point out, but update has not been enough :(
Any other ideas?
