Actually I had read the readme and I was wondering if opensips perhaps didn't
support all the
flags since some were missing from the documentation. Also on the subject of
DTLS I am
guessing that no flags means DTLS pass through but not certain. Also on the
subject of DTLS
when it plays MITM i
Hello Robert,
Take a look at the README file.
Based on the flags, rtpengine can bridge encrypted RTP traffic to
unencrypted RTP traffic. It can also do transcoding.
So yes, it plays man-in-the-middle :)
Regards,
Ovidiu Sas
On Tue, May 19, 2020 at 18:32 Robert Dyck wrote:
> Perhaps someone wit
Perhaps someone with knowledge of the inner workings of rtpengine could
enlighten us about
the interaction between ICE and DTLS. My experience suggests that it plays
man-in-the-middle
and fakes the DTLS negotiation in some circumstances.
Rob
On Tuesday, May 19, 2020 3:15:54 P.M. PDT Giovanni M
On Tue, May 19, 2020, 20:10 Ovidiu Sas wrote:
opensips rtpengine module provides a
> mechanism to pass those flags as strings to the rtpengine instance.
> Maybe we should add this to the documentation.
>
+1 +1 +1 (me, myself and I)
-giovanni
Regards,
> Ovidiu Sas
>
> On Sat, May 16, 2020 at
Hi Dhaval
Usually for using rtpengine_play_media we need A and B party,B party
generates Reply and SDP.
If you want to omit B party you should generate Reply and SDP inside
script. please see the workaround mentioned here[1]
and also this feature request[2].
[1] https://github.com/sipwise/rtpengi
For complete rtpengine documentation, take a look at the rtpengine README.md:
https://github.com/sipwise/rtpengine
There are new feature added with each new rpengine release.
The opensips rtpemgine module documentation (with respect to flags)
should be seen as a starting point.and the rtpengine REA
Hi everyone
I've been reading the blog on this subject:
https://blog.opensips.org/2019/04/04/no-downtime-for-opensips-3-0-restarts/
But when I enable the enable_restart_persistency parameter OpenSIPS fails
to start. With log level 4 I get:
DBG:core:init_mod: initializing module drouting
INFO:dr
Hello.
I'm trying to configure Call_center module in OpenSIPS 2.4.7 with
FreeSwith as media server.
I have configured flow and agent. Agent "testoper" (with URI
101@example.local) successfully logged in to the flow "techsupport"
with fifo command:
root@os1:~# opensipsctl fifo cc_agent_login testope
Interesting. We did not require any such special handling for it to work on our
side. We no longer run with shared IPs, though, so maybe something has changed.
Sorry I couldn't be more help.
Ben Newlin
On 5/19/20, 10:25 AM, "John Quick" wrote:
Hi Ben,
Thanks for answering this one.
Hi All,
I was trying to play with the 3.1 feature specifically media handling
capabilities.
I want opensips act as a playing server by answering WebRTC based calls.
Here is a scenario I was trying to do.
-- Opensips will receive WSS call
-- Process the call
-- Play file with 200 OK
-- Sending to
Hi Ben,
Thanks for answering this one. I agree totally with your analysis, but I can
also assure you that the "different" port number is present in the R-URI of the
ACK.
This is what OpenSIPS receives, over TLS, from the remote UAC:
ACK sip:+35312345...@195.xx.yy.zz:5050;transport=tcp SIP/2.0
I
John,
This is occurring because the local OpenSIPS is seeing its own local URI in the
R-URI and is (correctly) assuming the message is meant for it. At that point
there is some ambiguity in the situation as even though the Route headers
indicate loose routing, OpenSIPS cannot leave the R-URI as
Latest nightly build
version: opensips 3.0.2 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, Q_MALLOC,
F_MALLOC, HP_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
Hi James,
I reported this problem to the forum on 14th April. Since then, I sent a
stripped down copy of my opensips.cfg file to Bogdan to help with any
investigation.
I was seeing this problem on v2.4.7, but it did not happen in v2.4.6 using
exactly the same cfg script file. Which version are you
Hi James and others,
James, I have provided some explanation and guidance specific to you at the end
of this post. First, I need to retract some of the explanation I gave in my
original post because it was wrong. The basic problem is as described -
handling of loose routed sequential requests g
Hi, this happens one single opensips instance server it receives the inbound
packet fine, then when its send out on the same interface it’s fragmented, so I
don’t think it’s network or router switch related. Have seen such problems in
the past in virtual environments but this is not the case now
Can be a problem of the virtual env, and/or the router/switch...
Try substitute real hardware to virtual, and different models of
router/switch
In a LAN, UDP fragmentation is not supposed to be a problem at all...
answered from mobile, please pardon terseness and typos,
-giovanni
On Tue, May 19
17 matches
Mail list logo
