On 10/05/2024 04.49, palany wrote:
Thank you Richard. I have changed my rtpengine.conf as per your
instruction and now sdp m is now showing the correct ip but the o is
still showing the private ip as below.
The o= line is not relevant for the media flow, but you can add
`replace-origin` to
Hi Henning,
thank you for your reply. I did a lot testings during the past days and I think
I found a solution that is working, although it's very dirty...
I found out it is possible to send a manual KDMQ-Message to all Proxy-Nodes
including the one that it sending die KDMQ-Message. So I
Hi all!
Solved the issue by using s.decode.base64t instead of s.decode.base64 ...
Thanks anyway!
*Sérgio Charrua*
On Fri, May 10, 2024 at 9:40 AM Sergio Charrua
wrote:
> Hi all!
>
> I have been dealing with STIR/SHAKEN for a few weeks now, and while doing
> some tests I have found an issue
Thank you Richard. I have changed my rtpengine.conf as per your instruction and
now sdp m is now showing the correct ip but the o is still showing the private
ip as below.
v=0.
o=- 1 2 IN IP4 192.168.1.33.
s=CounterPath X-Lite 3.0.
c=IN IP4 13.246.88.123.
t=0 0.
m=audio 30016 RTP/AVP 8
Hi all!
I have been dealing with STIR/SHAKEN for a few weeks now, and while doing
some tests I have found an issue which I can't find the reason for.
The script has the following route logic:
route[HANDLE_STIRSHAKEN]
{
xlog("L_INFO", "HANDLE_STIRSHAKEN - STIR/SHAKEN Logic");
if
