ith
reusing the same IP facing Microsoft as the facing my internal devices
and/or the mix between UDP and TLS.
On you case, to you use the same IP address for facing Microsoft and
you devices? Do you use TLS on both sides of the call?
Thank you
Le 21 févr. 2023 à 17:07, John Burke a
Hey Daren,
Aliases should work I believe, however, you can also use the domain module[1]
to dynamically maintain “local” FQDNs.
[1] https://opensips.org/docs/modules/devel/domain.html
Sent from my iPhone
> On Feb 21, 2023, at 8:33 AM, Daren FERREIRA wrote:
>
> Hello,
>
> According to my
The kernel module still requires a fallback user space rule for the first few
packets. Once the user space daemon determines the forwarding rule set, it
pushes to the kernel module. The kernel module can then pickup the packets.
Their GitHub page has a detailed step by step for this process.
efore the 200, then
this doesn't work... but I think this is baked into RFC and in any rate
my unit tests for this scenario have never failed when migrating versions :)
Thanks,
John Burke
On 10/30/22 9:44 AM, M S wrote:
Hi list,
When a dialog is created with initial INVITE,
Hey Alexey,One solution might be to use a parallel set of AVPs (1 for CIDs, 1
for weight) and use "set_select_weight" [1] to select a random index. There is
also a PR in to shuffle an AVP list in place [2].If your list of CIDs is large,
then it may not be performant to load the list on every
Hey Marcin,
I also came across this when implementing S/S. In RFC8224 4.1, it
suggests the parameter is optional and the default is assumed to be ES256:
/Second, the JSON key "alg" MUST mirror the value of the optional//
//"alg" parameter in the SIP Identity header field. Note that if//
ne_retr
[3]
https://github.com/OpenSIPS/opensips/blob/cc20f738b83f5a9c7f24630309ddb5bab889bf56/modules/rtpengine/rtpengine.c#L2133-L2150
John Burke
On 10/21/21 1:45 AM, Sasmita Panda wrote:
Hi ,
I have configured 2 rtpengine in opensips-2.2 as beow .
modparam("rtpengine", &q
Hey Mark,
The load balancing weights are set on a per node basis via their socket
URL. If no weight is explicitly set, then the default is 1.
schema:
::(=)
ex:
udp:192.168.1.200:2=25
There currently is no way to dynamically change the weight of a node,
although there's an open PR [1]
doesn't know about your proxy, as the 200 won't contain any Record-Route
headers to build the route set for sequential reqs nor will the 200
contain a URI referencing your proxy in the Contact header.
Thanks,
John Burke
On 9/1/21 6:48 AM, Alexey Kazantsev via Users wrote:
Hi list,
feeling
oose_route();
t_relay();
exit;
} else { # don't process and strip routes
remove_hf("Route");
}
}
...
}
Thanks,
John Burke
**
*
*
On 8/27/21 9:01 AM, Louis Rochon wrote:
Răzvan,
Thank you for the quick r
] which would allow for weights to be
changed via the "rtpengine_enable" MI command.
[1] https://github.com/OpenSIPS/opensips/pull/2600
Thanks,
John Burke
On 8/20/21 5:00 AM, Mark Allen wrote:
I've not been able to find the answer to this. Can anyone help?
On Thu, 22 Jul 2021 at 1
Hey Johan,
Failure routes are in the context of request [1] - from the docs: "Note that
inside the 'failure_route', the request that initiated the transaction is being
processed, and not its reply."
You can access reply context from failure route by specifying the context of
$rs:
I will be out of the office until 11/25. For immediate concerns please contact
supp...@voxtelesys.com or 402-403-4435.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Hello:
I am using opensips 2.4.2, working with the rtpengine module trying to get
stats per call leg. I have tried using the $rtpstat(STAT)[index] function with
to-tag/from-tag but it seems to only return the first called stat... with
subsequent calls returning an empty string.
14 matches
Mail list logo
