On Monday 10 August 2015 07:37:43 Richard Fuchs wrote:
> You may have to call msg_apply_changes() before rewriting the SDP.
I tried:
rptengine_manage
msg_apply_changes
sdp_remove_line_by_prefix/replace_body_all
> But are you actually certain that the a=rtcp line causes the problems?
> Because t
On 08/10/2015 05:45 AM, Daniel Tryba wrote:
> On Wednesday 05 August 2015 16:05:52 Daniel-Constantin Mierla wrote:
>> maybe you can just removed with textops or sdpops functions plus
>> msg_apply_changes().
>
> Somehow that doesn't work for me... The a=rtcp line remains
> whatever/whereever
> I
On Wednesday 05 August 2015 16:05:52 Daniel-Constantin Mierla wrote:
> maybe you can just removed with textops or sdpops functions plus
> msg_apply_changes().
Somehow that doesn't work for me... The a=rtcp line remains whatever/whereever
I try to use sdp_remove_line_by_prefix("a=rtcp") or
replac
Hello,
maybe you can just removed with textops or sdpops functions plus
msg_apply_changes().
Cheers,
Daniel
On 04/08/15 18:02, Daniel Tryba wrote:
> Maybe a bit offtopic, but I can't find a rtpengine mailinglist and know the
> Sipwise guys are reading this list.
>
> Since upgrading to 4.2.x and
Maybe a bit offtopic, but I can't find a rtpengine mailinglist and know the
Sipwise guys are reading this list.
Since upgrading to 4.2.x and rtpengine instead of rtpproxy I'm seeing problems
with calls being terminated by upstream provider after a bit more than 5m. The
INVITE process looks okay
