That's exactly what I suggest! If you remove 100rel from INVITE, the
SIP provider should send a regular 183, not a 183 with 100rel. Then
you can safely drop the 183 without SDP.
-ovidiu
On Mon, Jan 18, 2021 at 5:08 PM solarmon wrote:
>
> The call flow is that we (our system) are the caller - we
The call flow is that we (our system) are the caller - we send the first
INVITE. The SIP provider is responding back with 183s because they want to
initiate early media.
Are you suggesting that we remove 100rel from our INVITE that we send out
to the SIP provider?
On Mon, 18 Jan 2021 at 21:54, Ov
100rel in the initial INVITE means that the caller has support for it, if
requested by the caller. If not present in INVITE, the caller should not
send provisional replies with 100rel.
-ovidiu
On Mon, Jan 18, 2021 at 15:13 solarmon wrote:
> H Ovidiu
>
> We do not want our system to change to a
H Ovidiu
We do not want our system to change to a 'ringing' state, which would
happen if it receives 180. We would like to drop the first 183 (without
SDP) but reply back with an PRACK (since 100rel was sent) and let the
subsequent 183 (with SDP) through. This is just a quirk in our system that
we
Hi,
I've been attempting to get a two node active/active setup to work with the
v3.1 clusterer module sharing usrloc and dialog. The setup is fronted by a
proxy that handles all of the NAT/media so either OpenSIPS instance can
communicate directly with the user.
What I have working so far:
You can change the 183 into an 180 and let the prack take its course.
Alternatively, you can remove 100rel from the initial INVITE and drop the
183 without SDP.
-ovidiu
On Mon, Jan 18, 2021 at 11:05 solarmon wrote:
> Hi,,
>
> I have a requirement to stop 183 without SDP packets from being pass
Hi all,
I'm trying to post a few variables in JSON in OpenSIPS 3.1, but $rm is
returning a number instead of the method in the JSON.
If I do something like this:
$json(body) := "{}";
$json(body/call_id) = $ci;
$json(body/ts) = $time(%Y-%m-%d %H:%M:%SZ);
$json(body/src_ip) = $si;
$json(body/dst_i
Hi Toni,
Thanks, I did come across that.
I was hoping not to have to install a module and have to do even more
changes to accommodate it. I was hoping that there was already a core
feature/mechanism to handle responding back with a PRACK.
Thank you.
On Mon, 18 Jan 2021, 17:35 Tomi Hakkarainen,
Hi,
I guess does not answer the guestion but take a look at this:
https://github.com/OpenSIPS/opensips/issues/2076
that said could you setup b2b logic to fix interworking issues?
Tomi
On 18. Jan 2021, at 18.31, solarmon wrote:
Hi Johan,
The first 183 packet that is received has no SDP in
Hi Johan,
The first 183 packet that is received has no SDP in it and has:
Require: 100rel
I wish to prevent this from being passed on, but still respond what with a
PRACK (since 100rel has been requested). The reason for this is that our
system will not work if it first receives a 183 without SD
you mean that the remote party sends you required:100rel ? The only way
that I know is by using b2b logic.
Maybe Bogdan can shed some light here.
Op ma 18 jan. 2021 om 17:07 schreef solarmon :
> Hi,,
>
> I have a requirement to stop 183 without SDP packets from being passed, as
> well as having t
Hello Giovanni,
All looks good!
IIRC you can alter the changelog to create custom names for packages (for
easier management).
Also, to simplify the install/update process, I create a custom mega
opensips package that has all the modules built in. That’s just my personal
preference :)
-ovidiu
On
Hi,,
I have a requirement to stop 183 without SDP packets from being passed, as
well as having to reply back with a PRACK.
I can stop the 183 without SDP from being passed on with the following in
onreply_route[]
if ($rs == "183" && !has_body_part("application/sdp")) {
drop();
Our setup...
External UAC 192.168.x.x
|
Router5.x.x.x
|
(internet)
|
Firewall 46.x.x.x maps ports
| directly to
OpenSIPS 192.168.x.x Mid-registrar and Mediaproxy
|
Asterisk 192.168.x.x
Current situation:
- UAC can call destination registered on As
My friends, Ovidiu,
so, see the following two scripts, one for first time building deb
packages, second script for updating such packages.
Can you all please give hints, corrections, etc?
FIRST TIME BUILD DEB PACKAGES:
#=
apt-get install bison debhelper default-libmysqlclient-dev
Hi All ,
First time I am going to use auth_jwt module in opensips 3.1 .
I have gone through the ppt and video of 2020 opensips Summit .
https://www.opensips.org/events/Summit-2020Distributed/assets/presentations/Vlad_Paiu-Opensips%20Jwt%202.pdf
https://www.youtube.com/watch?v=T-_uN7mdffE
I have
Hi guys,
I'm currently considering to use cgrates, but the functionality of
rate_cacher would be enough for me. therefore I was wondering, when the
beta/production version could be expected. Any milestones you could share?
--
Sent from:
http://opensips-open-sip-server.1449251.n2.nabble.com/Ope
17 matches
Mail list logo
