Fixed.
In relay route added in
rtpengine_offer rtcp-mux-demux option.
Regards, Igor
On 2 июня 2017 г., 14:57 +0300, Richard Fuchs , wrote:
> On 02/06/17 07:40 AM, Igor Olhovskiy wrote:
> > Hi!
> >
> > I’m trying to make RTPEngine to work with calls Browser <-> SIP.
> > Call From SIP to Browser
Getting same result..
v=0
o=- 1334974643 4 IN IP4 X.X.X.X
c=IN IP4 X.X.X.X
t=0 0
m=audio 41572 UDP/TLS/RTP/SAVPF 0 9 126
a=rtpmap:0 PCMU/8000
a=rtpmap:9 G722/8000
a=rtpmap:126 telephone-event/8000
a=fmtp:126 0-16
a=ptime:20
a=maxptime:150
a=sendrecv
a=rtcp:41573
a=setup:active
a=fingerprint:sha-1
On 02/06/17 07:40 AM, Igor Olhovskiy wrote:
Hi!
I’m trying to make RTPEngine to work with calls Browser <-> SIP.
Call From SIP to Browser working perfectly, but when calling to SIP
from Browser, on 200 OK (sdp) I don’t receive
...
a=rtcp-mux
...
lines, but it was told to RTPEngine on reply_rou
Hi!
I’m trying to make RTPEngine to work with calls Browser <-> SIP.
Call From SIP to Browser working perfectly, but when calling to SIP from
Browser, on 200 OK (sdp) I don’t receive
...
a=rtcp-mux
...
lines, but it was told to RTPEngine on reply_route to add this. And this line
is mandatory for
