On 03.02.2021 00:14, Alex Kinch wrote:
but there now appears to be another issue whereby $json is outputting
$socket_in(port) as a string instead of numeric? It's numeric as
expected if I go back to 3.1.1
Well, you have just uncovered another slight inaccuracy in the $socket()
variable code,
On Tue, 2 Feb 2021 at 20:11, Liviu Chircu wrote:
> This problem is identical to the previous one and the patch for the
> $json variable should cover both of them. Make sure you're using the
> nightly 3.1 packages or wait for the 3.1.2 release, after which you can
> test out the fix.
Sorry,
On Tue, 2 Feb 2021 at 20:11, Liviu Chircu wrote:
This problem is identical to the previous one and the patch for the
> $json variable should cover both of them. Make sure you're using the
> nightly 3.1 packages or wait for the 3.1.2 release, after which you can
> test out the fix.
>
Thanks
Hi,
Trying to follow up on this as seeking advice.
>
> Hi,
>
> I've recently installed and configured OpenSIPs 3.1 + CDRTool 9.9 on CentOS
> 7 platform. As per functionality based not facing any issues as able to get
> SIP traces and accounting.
>
> As per CDRTool 9.9 release, they've added
On 02.02.2021 18:32, Alex Kinch wrote:
Just found another similar related issue so thought I'd pop it on the
same thread.
$socket_in(af) returns INET or INET6 as expected but after passing
through $json it's numeric and 0 in both cases.
Redacted examples below. I'm on 3.1.1 from
Hello Johan,
Huge thank you that resolve the issue.
volga629
On 2/2/21 12:58 PM, Johan De Clercq
wrote:
if your _expression_ means : any number of digits, then try
something like below:
I believe I have made some headway on this today. It appears that in my
opensips.cfg, the line towards the top that is
socket=tcp:0.0.0.0:5060 AS 52.24.166.239:5060
is creating a listener for me (from your earlier question).
In the script where I call media_fork_to_uri, I've added the
if your expression means : any number of digits, then try something like
below:
try ([0-9]*)([A-Z]*)([0-9]*)
replace with \1\3.
Op di 2 feb. 2021 om 17:45 schreef volga629 via Users <
users@lists.opensips.org>:
> Hello Everyone,
> Here are some test result
>
> Feb 3 00:38:46 voice-proxy
Johan,
Thanks for your comment, but in this instance the problem is something very
subtle.
OpenSIPS is acting as a Proxy, not as an endpoint. So the Contact header in the
ACK contains the address of the UAC.
OpenSIPS identified itself earlier in the dialog using the correct FQDN in the
topmost
Hello Everyone,
Here are some test result
Feb 3 00:38:46 voice-proxy /usr/sbin/opensips[1337808]: [REQ_ROUTE]
[INVITE] got incorrect 1506855JMGTJ4566 adjusting...
Feb 3 00:38:46 voice-proxy /usr/sbin/opensips[1337808]: [REQ_ROUTE]
[INVITE] new username ->
Hi Liviu,
Just found another similar related issue so thought I'd pop it on the same
thread.
$socket_in(af) returns INET or INET6 as expected but after passing through
$json it's numeric and 0 in both cases.
Redacted examples below. I'm on 3.1.1 from Debian/Ubuntu packages.
Thanks,
Alex
Feb
Hello Everyone,
I am trying clean up with dialplan any characters from $rU
except digits.
I tried regex rule
Matching Regular _expression_
([0-9]*)
Substitution Regular
_expression_
([0-9]*)
Hi Răzvan.
Thank you for looking at this with me.
Attached is my opensips.cfg file.
In addition to starting OpenSIPS, the only other thing I am doing is starting
RTPProxy using the following command. If there is more that I should be doing
to configure listeners, I am unaware.
Hello Everyone,
Dispatcher in cluster causing destinations goes down
unexpectedly.
Scenario:
Two nodes with last ip octet 61 and 41.
Freeswitch stats to calculate weight.
Issue:
61 is set to ping all destinations and report to
is contact an fqdn ?
If not, look no further.
Op di 2 feb. 2021 om 15:06 schreef John Quick :
> I am seeing a problem in calls made to MS Teams via OpenSIPS configured as
> an SBC.
> The usual INVITE, 180, 183, 200 OK sequence looks okay, but the ACK request
> is not accepted by MS Teams.
> When
Hi, Eugene!
Could you give us a bit more information about the listeners (sockets)
you are using?
Best regards,
Răzvan Crainea
OpenSIPS Core Developer
http://www.opensips-solutions.com
On 2/1/21 11:22 PM, Eugene Christensen wrote:
Hello,
I’m trying to use the Media Exchange module and
I am seeing a problem in calls made to MS Teams via OpenSIPS configured as
an SBC.
The usual INVITE, 180, 183, 200 OK sequence looks okay, but the ACK request
is not accepted by MS Teams.
When I say "not accepted", I mean an ACK is sent to the Teams Proxy, but
Teams responds after 30 seconds with
17 matches
Mail list logo
