[OpenSIPS-Users] Wrong TCP socket being used on TLS registrations

[Ray Jackson]

Hi all,

I'm facing a weird issue which I think is related to broken TCP socket 
reuse logic where the wrong client is receiving incoming calls due to 
the wrong socket being used for the incoming INVITE.


The scenario is when I have 2 clients registering using TLS behind NAT 
at the same Public IPv4 address and both clients are using the same 
private port number.  So client 1 registers and the Via and contact 
header looks like:


Via: SIP/2.0/TLS 
192.168.42.162:5062;branch=z9hG4bK1409895926;rport;alias Contact: 
;reg-id=2;+sip.instance=""


Client 2 registers from behind the same Public IPv4 address and the Via 
and contact header looks like:


Via: SIP/2.0/TLS 192.168.42.186:5062;branch=z9hG4bK-aff1f3b3 Contact: 
;expires=300


The location table shows Client 1 received field of 103.212.1.2:5062 and 
Client 103.212.1.2:23456


When a call comes in for Client 1 the location lookup seems to return 
the correct 'received' address and port (e.g. 103.212.1.2:5062) and all 
the logs indicate that this is where the SIP INVITE *should* be going to 
(in the $du field).  However when you check the SIP traffic it selects 
Client 2's socket and the traffic goes to port 23456 instead of 5062.


I think this is related somehow to the TCP port reuse logic inside 
Opensips.  My suspicion is that Opensips is looking at the Contact or 
Via port number (which is the same for both client 1 and 2) and then 
somehow mapping this to the wrong TCP received socket.


Does anybody have any suggestions here?  Should I be fixing the NAT in 
the Contact header (using fix_nated_contact).  I read somewhere that you 
shouldn't rewrite the Contact header to avoid problems with sending a 
different Contact URI to the client on calls.  Or is this issue more 
related to the Via header and the TCP port reuse logic looking at this 
port instead of the actual received port when choosing the outgoing socket?


FYI: I am using both force_rport() and fix_nated_register() for incoming 
registrations from these clients and matching_mode of 0 in usrloc.  
However, I am not using fix_nated_contact() for registrations.


Thanks,

Ray

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] mid_registrar and nathelper problem

[Alejandro Mejia Evertsz]

Hi!
This is my first OpenSIPS installation, and I'm trying to achieve a simple
sip proxy for extensions to register to a PBX.
Got some configurations from samples all over docs and google searches and
everything seems to work fine until there's a call from the PBX to a
registered endpoint.
The endpoint rings, but when it answers the call, it sends OK to proxy, and
proxy to PBX, but when PBX sends ACK and proxy to endpoint, the ACK gets
lost on the proxy (never reaching the endpoint).

Same problem reported by another user on Dec. 2020 here:
https://opensips.org/pipermail/users/2020-December/044146.html
He didn't got any replies to his thread, so I would appreciate anyone's
help here.

Configuration file:
https://pastebin.com/GaQEMzmb

SIP Trace:
https://pastebin.com/3cREhszJ

As you can see, the ACK doesn't even try to leave the public (WAN)
interface of the proxy.

Thanks in advance for your help.

Alejandro
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] rest_post logs

[Alberto]

Hi,

Is there a way to turn off logs for rest_post requests?

This is my log settings:
log_level=-1
xlog_level=-1
log_stdout=yes
log_stderror=yes
log_facility=LOG_LOCAL0

This is the type of output I want to suppress:
Sep 01 13:31:48 opensips opensips[59740]: > POST /api/opensips/doit HTTP/1.1
Sep 01 13:31:48 opensips opensips[59740]: Host: 127.0.0.1
Sep 01 13:31:48 opensips opensips[59740]: Accept: */*
Sep 01 13:31:48 opensips opensips[59740]: Content-Type: application/json
Sep 01 13:31:48 opensips opensips[59740]: Content-Length: 156
Sep 01 13:31:48 opensips opensips[59740]:
Sep 01 13:31:48 opensips opensips[59740]: * upload completely sent off: 156
out of 156 bytes
Sep 01 13:31:48 opensips opensips[59740]: * Mark bundle as not supporting
multiuse
Sep 01 13:31:48 opensips opensips[59740]: < HTTP/1.1 200 OK
Sep 01 13:31:48 opensips opensips[59740]: < Server: nginx
Sep 01 13:31:48 opensips opensips[59740]: < Date: Fri, 01 Sep 2023 13:31:48
GMT
Sep 01 13:31:48 opensips opensips[59740]: < Content-Type: application/json;
charset=utf-8
Sep 01 13:31:48 opensips opensips[59740]: < Content-Length: 360
Sep 01 13:31:48 opensips opensips[59740]: < Connection: keep-alive
Sep 01 13:31:48 opensips opensips[59740]: < Access-Control-Allow-Origin: *
Sep 01 13:31:48 opensips opensips[59740]: < Content-Security-Policy:
default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action
'self';frame-ancestors 'self';img-src 'self' data:;object-src
'none';script-src 'self';script-src-attr 'none';style-src 'self' https:
'unsafe-inline';upgrade-insecure-requests
Sep 01 13:31:48 opensips opensips[59740]: < Cross-Origin-Opener-Policy:
same-origin
Sep 01 13:31:48 opensips opensips[59740]: < Cross-Origin-Resource-Policy:
same-origin
Sep 01 13:31:48 opensips opensips[59740]: < Origin-Agent-Cluster: ?1
Sep 01 13:31:48 opensips opensips[59740]: < Referrer-Policy: no-referrer
Sep 01 13:31:48 opensips opensips[59740]: < Strict-Transport-Security:
max-age=15552000; includeSubDomains
Sep 01 13:31:48 opensips opensips[59740]: < X-Content-Type-Options: nosniff
Sep 01 13:31:48 opensips opensips[59740]: < X-DNS-Prefetch-Control: off
Sep 01 13:31:48 opensips opensips[59740]: < X-Download-Options: noopen
Sep 01 13:31:48 opensips opensips[59740]: < X-Frame-Options: SAMEORIGIN
Sep 01 13:31:48 opensips opensips[59740]: <
X-Permitted-Cross-Domain-Policies: none
Sep 01 13:31:48 opensips opensips[59740]: < X-XSS-Protection: 0
Sep 01 13:31:48 opensips opensips[59740]: <
Sep 01 13:31:48 opensips opensips[59740]: * Connection #0 to host 127.0.0.1
left intact

Thanks
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] ERROR:tls_mgm:load_tls_library: No TLS library module loaded

[Prathibha B]

I've loaded tls_mgm module in /lib64/opensips/modules. Still getting this
error.

NOTICE:core:main: version: opensips 3.5.0-dev (x86_64/linux)
Sep 01 10:45:49 ip-172-31-34-24 opensips[363797]: Sep 1 10:45:49 [363797]
NOTICE:core:main: using 128 MB of shared memory, allocator: Q_MALLOC_DBG
Sep 01 10:45:49 ip-172-31-34-24 opensips[363797]: Sep 1 10:45:49 [363797]
NOTICE:core:main: using 4 MB of private process memory, allocator:
Q_MALLOC_DBG
Sep 01 10:45:49 ip-172-31-34-24 opensips[363797]: Sep 1 10:45:49 [363797]
NOTICE:signaling:mod_init: initializing module ...
Sep 01 10:45:49 ip-172-31-34-24 opensips[363797]: Sep 1 10:45:49 [363797]
ERROR:tls_mgm:load_tls_library: No TLS library module loaded
Sep 01 10:45:49 ip-172-31-34-24 opensips[363797]: Sep 1 10:45:49 [363797]
ERROR:core:init_mod: failed to initialize module tls_mgm
Sep 01 10:45:49 ip-172-31-34-24 opensips[363797]: Sep 1 10:45:49 [363797]
ERROR:core:main: failed to initialize modules!
Sep 01 10:45:49 ip-172-31-34-24 opensips[363797]: Sep 1 10:45:49 [363797]
NOTICE:core:main: Exiting...

-- 
Regards,
B.Prathibha
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips not getting started

[Prathibha B]

● opensips.service - LSB: Start the OpenSIPS SIP server
 Loaded: loaded (/etc/init.d/opensips; generated)
 Active: active (exited) since Fri 2023-09-01 10:10:10 UTC; 7s ago
   Docs: man:systemd-sysv-generator(8)
Process: 361928 ExecStart=/etc/init.d/opensips start (code=exited,
status=0/SUCCESS)
CPU: 44ms

Sep 01 10:10:10 ip-172-31-34-24 opensips[361947]: Sep  1 10:10:10 [361947]
NOTICE:core:main: using 128 MB of shared memory, allocator: Q_MALLOC_DBG
Sep 01 10:10:10 ip-172-31-34-24 opensips[361947]: Sep  1 10:10:10 [361947]
NOTICE:core:main: using 4 MB of private process memory, allocator:
Q_MALLOC_DBG
Sep 01 10:10:10 ip-172-31-34-24 opensips[361947]: Sep  1 10:10:10 [361947]
NOTICE:signaling:mod_init: initializing module ...
Sep 01 10:10:10 ip-172-31-34-24 opensips[361947]: Sep  1 10:10:10 [361947]
WARNING:usrloc:ul_check_config: 'db_mode' is now deprecated, use
'working_mode_preset'!
Sep 01 10:10:10 ip-172-31-34-24 opensips[361947]: Sep  1 10:10:10 [361947]
ERROR:tls_mgm:load_tls_library: No TLS library module loaded
Sep 01 10:10:10 ip-172-31-34-24 opensips[361947]: Sep  1 10:10:10 [361947]
ERROR:core:init_mod: failed to initialize module tls_mgm
Sep 01 10:10:10 ip-172-31-34-24 opensips[361947]: Sep  1 10:10:10 [361947]
ERROR:core:main: failed to initialize modules!
Sep 01 10:10:10 ip-172-31-34-24 opensips[361947]: Sep  1 10:10:10 [361947]
NOTICE:core:main: Exiting
Sep 01 10:10:10 ip-172-31-34-24 opensips[361928]:  already running
...done.
Sep 01 10:10:10 ip-172-31-34-24 systemd[1]: Started LSB: Start the OpenSIPS
SIP server.


*I've loaded tls_mgm.so in /lib64/opensips/modules. But still it is showing
the error.*

On Fri, 1 Sept 2023 at 15:29, Prathibha B  wrote:

> while running
>
> systemctl start opensips
> systemctl status opensips
>
> opensips.service - LSB: Start the OpenSIPS SIP server
>  Loaded: loaded (/etc/init.d/opensips; generated)
>  Active: active (exited) since Fri 2023-09-01 09:10:43 UTC; 47min ago
>Docs: man:systemd-sysv-generator(8)
> Process: 361274 ExecStart=/etc/init.d/opensips start (code=exited,
> status=0/SUCCESS)
> CPU: 45ms
>
> Sep 01 09:10:43 ip-172-31-34-24 systemd[1]: Starting LSB: Start the
> OpenSIPS SIP server...
> Sep 01 09:10:43 ip-172-31-34-24 opensips[361274]:  * Starting opensips
> opensips
> Sep 01 09:10:43 ip-172-31-34-24 opensips[361292]: Listening on
> Sep 01 09:10:43 ip-172-31-34-24 opensips[361292]:  udp:
> 172.31.34.24 [172.31.34.24]:5060
> Sep 01 09:10:43 ip-172-31-34-24 opensips[361292]:  tls:
> 172.31.34.24 [172.31.34.24]:5061
> Sep 01 09:10:43 ip-172-31-34-24 opensips[361292]:  ws:
> 172.31.34.24 [172.31.34.24]:8080
> Sep 01 09:10:43 ip-172-31-34-24 opensips[361292]:  wss:
> 172.31.34.24 [172.31.34.24]:443
> Sep 01 09:10:43 ip-172-31-34-24 opensips[361292]: Aliases:
> Sep 01 09:10:43 ip-172-31-34-24 opensips[361274]:  already running
> ...done.
> Sep 01 09:10:43 ip-172-31-34-24 systemd[1]: Started LSB: Start the
> OpenSIPS SIP server.
>
> the ports don't appear in nestat -ltnp
>
> The configuration file is also attached. How to resolve this?
> --
> Regards,
> B.Prathibha
>


-- 
Regards,
B.Prathibha
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] opensips not getting started

[Prathibha B]

while running

systemctl start opensips
systemctl status opensips

opensips.service - LSB: Start the OpenSIPS SIP server
 Loaded: loaded (/etc/init.d/opensips; generated)
 Active: active (exited) since Fri 2023-09-01 09:10:43 UTC; 47min ago
   Docs: man:systemd-sysv-generator(8)
Process: 361274 ExecStart=/etc/init.d/opensips start (code=exited,
status=0/SUCCESS)
CPU: 45ms

Sep 01 09:10:43 ip-172-31-34-24 systemd[1]: Starting LSB: Start the
OpenSIPS SIP server...
Sep 01 09:10:43 ip-172-31-34-24 opensips[361274]:  * Starting opensips
opensips
Sep 01 09:10:43 ip-172-31-34-24 opensips[361292]: Listening on
Sep 01 09:10:43 ip-172-31-34-24 opensips[361292]:  udp:
172.31.34.24 [172.31.34.24]:5060
Sep 01 09:10:43 ip-172-31-34-24 opensips[361292]:  tls:
172.31.34.24 [172.31.34.24]:5061
Sep 01 09:10:43 ip-172-31-34-24 opensips[361292]:  ws:
172.31.34.24 [172.31.34.24]:8080
Sep 01 09:10:43 ip-172-31-34-24 opensips[361292]:  wss:
172.31.34.24 [172.31.34.24]:443
Sep 01 09:10:43 ip-172-31-34-24 opensips[361292]: Aliases:
Sep 01 09:10:43 ip-172-31-34-24 opensips[361274]:  already running
...done.
Sep 01 09:10:43 ip-172-31-34-24 systemd[1]: Started LSB: Start the OpenSIPS
SIP server.

the ports don't appear in nestat -ltnp

The configuration file is also attached. How to resolve this?
-- 
Regards,
B.Prathibha


opensips.cfg
Description: Binary data
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] systemctl status opensips

[Prathibha B]

I'm getting  *Active: active (exited). How to resolve this issue?*

On Thu, 31 Aug 2023 at 14:22, Prathibha B  wrote:

> opensips.service - LSB: Start the OpenSIPS SIP server
>  Loaded: loaded (/etc/init.d/opensips; generated)
>*  Active: active (exited) since Thu 2023-08-31 08:17:20 UTC; 32min
> ago*
>Docs: man:systemd-sysv-generator(8)
> Process: 347316 ExecStart=/etc/init.d/opensips start (*code=exited,
> status=0/SUCCESS*)
> CPU: 44ms
>
> Aug 31 08:17:20 ip-172-31-34-24 systemd[1]: Starting LSB: Start the
> OpenSIPS SIP server...
> Aug 31 08:17:20 ip-172-31-34-24 opensips[347316]:  * Starting opensips
> opensips
> Aug 31 08:17:20 ip-172-31-34-24 opensips[347333]: Listening on
> Aug 31 08:17:20 ip-172-31-34-24 opensips[347333]:  udp:
> 127.0.0.1 [127.0.0.1]:5060
> Aug 31 08:17:20 ip-172-31-34-24 opensips[347333]:  tls:
> 127.0.0.1 [127.0.0.1]:5061
> Aug 31 08:17:20 ip-172-31-34-24 opensips[347333]:  ws:
> 127.0.0.1 [127.0.0.1]:8080
> Aug 31 08:17:20 ip-172-31-34-24 opensips[347333]:  wss:
> 127.0.0.1 [127.0.0.1]:443
> Aug 31 08:17:20 ip-172-31-34-24 opensips[347333]: Aliases:
> Aug 31 08:17:20 ip-172-31-34-24 opensips[347316]:  already running
> ...done.
> Aug 31 08:17:20 ip-172-31-34-24 systemd[1]: Started LSB: Start the
> OpenSIPS SIP server.
>
> *netstat -ltnup doesn't show 5060, 5061, 8080 and 443*
>
> --
> Regards,
> B.Prathibha
>


-- 
Regards,
B.Prathibha
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Error in opensips.cfg file

[Prathibha B]

This issue is resolved after migration to the latest version.

On Fri, 1 Sept 2023 at 13:41, Alejandro Mejia Evertsz <
ame...@voxdatacomm.com> wrote:

> Hello Phrathib
>
> It seems you're using some commands used in version 2.
> You may need to look for the correct syntax to use them on version 3.
> There is a document on the website that explains migrating from 2 to 3.
> https://www.opensips.org/Documentation/Migration-2-4-0-to-3-0-0
>
> Hope it helps
>
> On Wed, Aug 30, 2023, 11:17 PM Prathibha B 
> wrote:
>
>> Aug 31 04:14:49 [339966] CRITICAL:Traceback (last included file at the
>> bottom):
>> Aug 31 04:14:49 [339966] CRITICAL: 0. //etc/opensips/opensips.cfg
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:183:12-14: syntax error
>> Aug 31 04:14:49 [339966] CRITICAL:
>> Aug 31 04:14:49 [339966] CRITICAL:  # check if the clients are using
>> WebSockets or WebSocketSecure
>> Aug 31 04:14:49 [339966] CRITICAL:  if (proto == "WS" || proto ==
>> "WSS")
>> Aug 31 04:14:49 [339966] CRITICAL:  ^~~
>> Aug 31 04:14:49 [339966] CRITICAL:  setflag(SRC_WS);
>> Aug 31 04:14:49 [339966] CRITICAL:
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:183:12-14: bare word  found, command
>> calls need '()'
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:183:12-14: bad command!)
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:183:16-17: bad command!)
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:183:18-20: bad command!)
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:183:27-29: bare word  found, command
>> calls need '()'
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:183:27-29: bad command: missing ';'?
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:183:31-32: bad command!)
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:183:32-33: bad command!)
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:184:17-18: bad arguments for command 
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:193:17-23: syntax error
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:193:23-24: bad arguments for command 
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:194:13-19: syntax error
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:194:19-20: bad arguments for command 
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:239:16-22: syntax error
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:239:22-23: bad arguments for command 
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:239:38-44: syntax error
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:239:44-45: bad arguments for command
>> 
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:241:21-27: syntax error
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:241:27-28: bad arguments for command 
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:241:44-50: syntax error
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:241:50-51: bad arguments for command
>> 
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:243:22-28: syntax error
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:243:28-29: bad arguments for command 
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:243:44-50: syntax error
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:243:50-51: bad arguments for command
>> 
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:245:22-28: syntax error
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:245:28-29: bad arguments for command 
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:245:45-51: syntax error
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>> //etc/opensips/opensips.cfg:245:51-52: bad arguments for command
>> 
>> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
>

Re: [OpenSIPS-Users] Error in opensips.cfg file

[Alejandro Mejia Evertsz]

Hello Phrathib

It seems you're using some commands used in version 2.
You may need to look for the correct syntax to use them on version 3.
There is a document on the website that explains migrating from 2 to 3.
https://www.opensips.org/Documentation/Migration-2-4-0-to-3-0-0

Hope it helps

On Wed, Aug 30, 2023, 11:17 PM Prathibha B  wrote:

> Aug 31 04:14:49 [339966] CRITICAL:Traceback (last included file at the
> bottom):
> Aug 31 04:14:49 [339966] CRITICAL: 0. //etc/opensips/opensips.cfg
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:183:12-14: syntax error
> Aug 31 04:14:49 [339966] CRITICAL:
> Aug 31 04:14:49 [339966] CRITICAL:  # check if the clients are using
> WebSockets or WebSocketSecure
> Aug 31 04:14:49 [339966] CRITICAL:  if (proto == "WS" || proto ==
> "WSS")
> Aug 31 04:14:49 [339966] CRITICAL:  ^~~
> Aug 31 04:14:49 [339966] CRITICAL:  setflag(SRC_WS);
> Aug 31 04:14:49 [339966] CRITICAL:
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:183:12-14: bare word  found, command
> calls need '()'
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:183:12-14: bad command!)
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:183:16-17: bad command!)
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:183:18-20: bad command!)
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:183:27-29: bare word  found, command
> calls need '()'
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:183:27-29: bad command: missing ';'?
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:183:31-32: bad command!)
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:183:32-33: bad command!)
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:184:17-18: bad arguments for command 
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:193:17-23: syntax error
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:193:23-24: bad arguments for command 
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:194:13-19: syntax error
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:194:19-20: bad arguments for command 
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:239:16-22: syntax error
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:239:22-23: bad arguments for command 
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:239:38-44: syntax error
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:239:44-45: bad arguments for command
> 
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:241:21-27: syntax error
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:241:27-28: bad arguments for command 
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:241:44-50: syntax error
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:241:50-51: bad arguments for command
> 
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:243:22-28: syntax error
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:243:28-29: bad arguments for command 
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:243:44-50: syntax error
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:243:50-51: bad arguments for command
> 
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:245:22-28: syntax error
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:245:28-29: bad arguments for command 
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:245:45-51: syntax error
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:245:51-52: bad arguments for command
> 
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:257:16-22: syntax error
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:257:22-23: bad arguments for command 
> Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error i

Re: [OpenSIPS-Users] bad arguments for command

[Karsten Wemheuer]

Hi,

Am Donnerstag, dem 31.08.2023 um 12:48 +0530 schrieb Prathibha B:
> Aug 31 06:58:48 [346547] CRITICAL:Traceback (last included file at
> the bottom):
> Aug 31 06:58:48 [346547] CRITICAL: 0. //etc/opensips/opensips.cfg
> Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:184:11-17: syntax error
> Aug 31 06:58:48 [346547] CRITICAL:  # check if the clients are
> using WebSockets or WebSocketSecure
> Aug 31 06:58:48 [346547] CRITICAL:  if ($socket_in(proto) == "WS"
> || $socket_in(proto) == "WSS")
> Aug 31 06:58:48 [346547] CRITICAL:  setflag(SRC_WS);
> Aug 31 06:58:48 [346547] CRITICAL:  ^~~
> Aug 31 06:58:48 [346547] CRITICAL:
> Aug 31 06:58:48 [346547] CRITICAL:  # consider the client is
> behind NAT - always fix the contact
> Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in
> //etc/opensips/opensips.cfg:184:17-18: bad arguments for command
> 

maybe use quotes around parameter like
setflag("SRC_WS");

HTH,
Best regards Karsten


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] ul_dump brief is not accepted, opensips 3.4

[William Jin]

Hi,

1,
looks like ul_dump brief params is not accepted


OS: Ubuntu 22
opensips -V
version: opensips 3.4.0-rc1 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, Q_MALLOC, 
F_MALLOC, HP_MALLOC, DBG_MALLOC, CC_O0, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, 
MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll, sigio_rt, select.
git revision: c64766a85
main.c compiled on  with gcc 11

apt policy opensips-cli
opensips-cli:
  Installed: 0.1~20230512~161b5ea-1
  Candidate: 0.1~20230512~161b5ea-1
  Version table:
 *** 0.1~20230512~161b5ea-1 500
500 https://apt.opensips.org jammy/cli-nightly amd64 Packages

opensips-cli --version
OpenSIPS CLI 0.2.0

opensips-cli -x mi ul_dump brief
ERROR: command 'ul_dump' returned: -32602: Invalid params (Bad type for 
parameter 'brief')

2,
When doing dr_reload through httpd, the load of the HTTPD ps will increase and 
other services rely on it like opensips prometheus  will stuck and return 
nothing until dr_reload is completed

curl -s -X POST -H 'Content-Type: application/json' {server-IP}:/mi 
-d'{"jsonrpc": "2.0","id": 1,"method": "dr_reload"}' | json_pp

curl 127.0.0.1:/metrics

Is it possible to increase the worker number of HTTPD ps?


Regards,
William Jin

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] We need you to fill out our Carrier Application!!

[BE . Logistics LLC]

#

#

[BE. Logistics 
LLC](https://5y0ou.r.a.d.sendibm1.com/mk/cl/f/sh/1t6Af4OiGsDg0ir9CZLQIyf8RbaBmN/YzTb1Uuosclo)

#

#

Fill Out Our Carrier Application
for Dispatch Services

**No Dispatching for Sprinter Vans, Car Haulers, or Dump Trucks**

We are looking to partner with:

Hotshots (32ft+ OTR 2-6 weeks on the road)

Box Trucks (24ft+ OTR 2-6 weeks on the road)

Flatbed- 48ft+ Local, Regional & OTR

DRY Van- Local, Regional & OTR

REEFER - Local, Regional, or OTR

We would love to talk with you!
Click below to fill out our Carrier Application.

#

[Carrier 
Application](https://5y0ou.r.a.d.sendibm1.com/mk/cl/f/sh/1t6Af4OiGsE8LR3ZavRLTEixpQYvUR/3yD3Q7fm6aan)

#

The Hot Shots average is $4,000-$6,000.
The Box Trucks average is $3,000 to $5,000.
The Flatbeds average $8,000-$10,000.
The Dry Van average $6,000-$8,000.
The Reefer average $7,000-$9,000.

If you’re interested, go to our website 
https://www.belogistics.net/carrier-application and fill out the carrier 
application.

BENEFITS:

No contract length
No force dispatch
No going to areas outside your desire
All paperwork included
Only loads booked over the national average rate per your equipment

**No Dispatching for Sprinter Vans, Car Haulers, or Dump Trucks**

[Facebook](https://5y0ou.r.a.d.sendibm1.com/mk/cl/f/sh/1t6Af4OiGsEag9FzzHXGdUmnDFXfCV/NuiBQ0HF7Fju)

[LinkedIn](https://5y0ou.r.a.d.sendibm1.com/mk/cl/f/sh/1t6Af4OiGsF30rSQNddBnkqcb4WOuZ/Dt6Wy_2edNdK)

[Instagram](https://5y0ou.r.a.d.sendibm1.com/mk/cl/f/sh/1t6Af4OiGsFVLZeqlzj6y0uRytV8cd/FvBhR0Gyvlkk)

[YouTube](https://5y0ou.r.a.d.sendibm1.com/mk/cl/f/sh/1t6Af4OiGsFxgHrHALp28GyHMiTsKh/p7wfEKqbQ8xi)

#

[BE. Logistics 
LLC](https://5y0ou.r.a.d.sendibm1.com/mk/cl/f/sh/1t6Af4OiGsGQ103hYhuxIX26kXSc2l/9Mbv518XSdFD)

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Unable to enable secure renegotiation option in WolfSSL from OpenSIPs 3.2.2

[rkumar--- via Users]

Hello,

 

We are getting issue with OpenSIPs using TLS library "WolfSSL" when clients
using OpenSSL 3.0.  we are getting Pre TLS handshake Errors . Please check
and let us know  what can be done to resolve this issue.

 

ERROR:tls_wolfssl:_wolfssl_tls_accept: New TLS connection [0x7f1276c51740]
from 202.65.142.206:51053 failed to accept

ERROR:tls_wolfssl:_wolfssl_tls_accept: TLS accept error: -313, received
alert fatal error , connection [0x7f1276c51740]

ERROR:proto_tls:tls_read_req: failed to do pre-tls handshake!

INFO:core:tcp_trigger_report: Connection [0x7f1276c51740] is getting release
because of [Read error]

 

 

To address above issue we are trying to enable "secure-renegotiation" from
WolfSSL end   but when we enable this , we are getting following error from
WolfSSL library 

 

error "WRITE DUP and SECURE RENEGOTIATION cannot both be on"

 

so we disabled "WRITE DUP" and enabled "SECURE RENEGOTIATION" , and
compilation is getting succeeded but  OpenSIPs unable to load  WolfSSL
module as it is using "WRITE DUP" functions in WolfSSL module .

 

ERROR:core:sr_load_module: could not open module  tls_wolfssl.so: undefined
symbol: wolfSSL_write_dup

ERROR:core:load_module: failed to load module

 

Software versions used :

 

OpenSIPs : 3.2.2

Embedded WolfSSL: 4.7.1

 

Regards,

V Ravi Kumar

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Failed to init TLS domain 'default'

[Prathibha B]

ERROR:tls_mgm:init_tls_domains: Failed to init TLS domain 'default'.
ERROR:core:init_mod: failed to initialize module tls_mgm
ERROR:core:main: failed to initialize modules!
-- 
Regards,
B.Prathibha
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] mid_registrar and nathelper problem

[Alejandro Mejia Evertsz]

Hi!
This is my first OpenSIPS installation, and I'm trying to achieve a simple
sip proxy for my office extensions to register to our PBX.
Got some configurations from samples all over docs and google searches and
everything seems to work fine until there's a call from the PBX to a
registered endpoint.
The endpoint rings, but when it answers the call, it sends OK to proxy, and
proxy to PBX, but when PBX sends ACK and proxy to endpoint, the ACK gets
lost on the proxy (never reaching the endpoint).

Same problem reported by another user on Dec. 2020 here:
https://opensips.org/pipermail/users/2020-December/044146.html
He didn't got any replies to his thread, so I would appreciate anyone's
help here.

Configuration file:
https://pastebin.com/GaQEMzmb

SIP Trace:
https://pastebin.com/3cREhszJ

As you can see, the ACK doesn't even try to leave the public (WAN)
interface of the proxy.

Thanks in advance for your help.

Alejandro
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Time's Running Out! Hurry up and Apply Now!

[BE . Logistics LLC]

#

#

[BE. Logistics 
LLC](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/sh/1t6Af4OiGsDg0ir9CZLQIyf8RbaBmN/aOtBA3I-oJqV)

#

WE'VE HIRED 2 DISPATCHERS!!

#

#

Fill Out Our Carrier Application
for Dispatch Services

**No Dispatching for Sprinter Vans, Car Haulers, or Dump Trucks**

We are looking to partner with:

Hotshots (32ft+ OTR 2-6 weeks on the road)

Box Trucks (24ft+ OTR 2-6 weeks on the road)

Flatbed- 48ft+ Local, Regional & OTR

DRY Van- Local, Regional & OTR

REEFER - Local, Regional, or OTR

We would love to talk with you!
Click below to fill out our Carrier Application.

#

[Carrier 
Application](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/sh/1t6Af4OiGsE8LR3ZavRLTEixpQYvUR/XP2iJHz49uML)

#

The Hot Shots average is $4,000-$6,000.
The Box Trucks average is $3,000 to $5,000.
The Flatbeds average $8,000-$10,000.
The Dry Van average $6,000-$8,000.
The Reefer average $7,000-$9,000.

If you’re interested, go to our website 
https://www.belogistics.net/carrier-application and fill out the carrier 
application.

BENEFITS:

No contract length
No force dispatch
No going to areas outside your desire
All paperwork included
Only loads booked over the national average rate per your equipment

**No Dispatching for Sprinter Vans, Car Haulers, or Dump Trucks**

#

https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/sh/1t6Af4OiGsEag9FzzHXGdUmnDFXfCV/7_ky4eQWQGYk

New Authority Broker List

Have you believed the lie that ALL brokers make you wait 6 months before 
they’ll give you freight? If so, our list proves thats not so…

[Purchase 
List](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/sh/1t6Af4OiGsF30rSQNddBnkqcb4WOuZ/K4LWoqSsOMNM)

[Facebook](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/sh/1t6Af4OiGsFVLZeqlzj6y0uRytV8cd/1ZofJpWnVRSO)

[LinkedIn](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/sh/1t6Af4OiGsFxgHrHALp28GyHMiTsKh/0fc8_XJCqSMP)

[Instagram](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/sh/1t6Af4OiGsGQ103hYhuxIX26kXSc2l/c_XdtVL9saCZ)

[YouTube](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/sh/1t6Af4OiGsGsLiG7x40sSn5w8MRLkp/RoTbyY1Nffvg)

#

[BE. Logistics 
LLC](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/sh/1t6Af4OiGsHKgQSYLQ6nd39lWBQ5St/rWxNwjrTNzlC)

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] We need you to fill out our Carrier Application!!

[BE . Logistics LLC]

#

#

[BE. Logistics 
LLC](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/zWXwFBqILY386zM84ctCd4cTXL67ymahPic_XTf-W8n38leem0PPmW1Kzg1iXevKcP4w0gxfQl3cAghLavS227GFTXT8eZ-LspEFwIMRvHPDbrgtDkbLRUGpsRlRSb6j_cdXXJkDZUdFcyaxXHK3ObdVoIGXYYQ2doNCYcdmbb20Bd1rP495LcLlKbxwEgv4ayKzSlwyRZ5IbTcadQ)

#

WE'VE HIRED 2 DISPATCHERS!!

#

#

Fill Out Our Carrier Application
for Dispatch Services

**No Dispatching for Sprinter Vans, Car Haulers, or Dump Trucks**

We are looking to partner with:

Hotshots (32ft+ OTR 2-6 weeks on the road)

Box Trucks (24ft+ OTR 2-6 weeks on the road)

Flatbed- 48ft+ Local, Regional & OTR

DRY Van- Local, Regional & OTR

REEFER - Local, Regional, or OTR

We would love to talk with you!
Click below to fill out our Carrier Application.

#

[Carrier 
Application](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/H09c7xOhc_ijO7GhNS4SL7kCejh4U6YG2g3gozAMy3BpCivvkzrqnyJSdJW6ER6osWrbnMXOivBndkDhdbaxgxCIR2fa7Y9OoHoDHAJEpomg-SrWTR6iIkAHI2vE9HYTKav_0CNQFZ9G3WUAESRecIVC7Oon4RgaLBV7XsrxCOIl5_PWIvV7b7-t5ANjCQxUkjUvxYADLntJP845ZaIUepQeqIYNrGkIqI3KMWHknEFh5vi-)

#

The Hot Shots average is $4,000-$6,000.
The Box Trucks average is $3,000 to $5,000.
The Flatbeds average $8,000-$10,000.
The Dry Van average $6,000-$8,000.
The Reefer average $7,000-$9,000.

If you’re interested, go to our website 
https://www.belogistics.net/carrier-application and fill out the carrier 
application.

BENEFITS:

No contract length
No force dispatch
No going to areas outside your desire
All paperwork included
Only loads booked over the national average rate per your equipment

**No Dispatching for Sprinter Vans, Car Haulers, or Dump Trucks**

#

https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/XZlCZywTUcBr_xckJh0kiVZKgJy04d2iF3P379GtqLFGpYPCF9AsoiNYbSn1S72H8J4V0u2PPy1hsQdR9isiZwalm803UDN_5c5DtZ1xlPq4Lue_I0nSvoLKVbOi5ecpZoOAAJ1tVlgE9OJgI3mWgStDHkxDtCYKj6MdNTBj1R1xAPi5giMGpqjDZ9hSxj2WmCOCDmQpBWeDmyMkerqr2GcSbNWCLUdo_xvhiAmogF3bVTA9ptwWySSxUvKFLJmX

New Authority Broker List

Have you believed the lie that ALL brokers make you wait 6 months before 
they’ll give you freight? If so, our list proves thats not so…

[Purchase 
List](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/Y5HDyynwyzL2mySiY5qi_Mkhk2hdRYy1OsF_hhu_sPfvd4G9JYoJmgBdnv-zVAy0k6y-_rpSwJIG6iBt9jjCryh5NrvyUFhdqO4U-zbicTCzGZ64MVTUcBPvYGUBpALP8vhtEnJiIULlUwKW0X7gtwRwdFAkuO93_9zwfiArIWtt_Me48-L6O8m6BqQ7bdeSV_I82BfC0dXE7-qnXp6_x-WrsI-BVFdkq14_P-r_J4AWhMsYk6gJvtXSUqrWm45j)

[Facebook](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/aa8VZmX3ZVDjEuf-pkqNSrjoBWiQU-vgGTQYQo1DsLthLLfBQ8LEiUzYHY7iVqv3NSJBa2NBwiKfG4HJOb6B1Ifq3alAYYdwjaDZZVftdgFa4UKmsN4tH-ZTd1l3c-DeHLp845JWrRBRMIcemlruY55TUP9-4c7en2n2G9cjKfY2J--GGn6t2O51-zFLIHp4lQVAjVzFNYY0L43cp6FS1TFpUvZ8Bw)

[LinkedIn](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/divQRu0yLqRl4fIoQ6Cg6-UjrPbRzwk0acuatBic8vPlMgrWjbG7XZ1IRlf4ju8gC7GCPh_dNv3JrCyoX73OUpa0qAfSI8fxD8nBzH43rfnl6HnxFlwGWHBD3DiMjLkuWF16_yVadtTH51aJZELRCaRCgFkRAnGDE1y465FzvHG9ZPyhVw-uPE8cgqI6RYdxsgzKyukRVIORqgBr2qwDCLTy5YPsB13UmOPE8YCrbuUbeecYtGt04XBsSkQq9Q)

[Instagram](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/o2lZpkLMBPkQ4HtnF5UYWm4yLnXQglWkDL9KSqbL7n1B_fWZmN_TkUnrR0PVIX14o3HnCWBvNUMqG-D5-3E46h47y133HCUGN1kurBfyCUchnq6uDqGhOQxRncxSTfeINQuQSL6XM80EdkxQuBpuUu2URtercrWytMFFVqSVVkkyRiK79l2i5CaMQAazKzvTGZX7HkhLlpK3uvsRYOhJYJAPyaDo_H0jKJFc7ZA8)

[YouTube](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/kuqjBiyBDnhcbsYvGueM3EvMeWeF0EIpkJ2xasgypyX-ZlcQdn6hNM-U_Ij9zD4CIjt8uiyyh9closjbCrmnRkmTfYiLV9DnUiDXLJWS3rPA8IUvDhUI9QmLmahelxoLNhZrHTQY0SB9fOcIm1FhM-bVFA_OGaqBuF3bGLDO1xRiZcG2wQAmAHYFnBxrbO1dOZF_6GnxYZebEScohX_hAgVkENuN-qen5z4kCepMzGEznZYKYFbM8AkViRtvABI)

#

[BE. Logistics 
LLC](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/8EqqV0tLHKH_2fIy8QYZ4TkMc0ObH5tqRttWjRAHLhQo00gOwI3DRPJBlL5HuWnKfosye6jwbM7Gd6OA85wOzEUthBYuFKnUmhwI0ZzuYJVyE14eb_yXolwsZh3DunCuPB-hiMKIxIR-qqMjIo29rbmHldHDyoVGDFE0cieQ99jMdguyI5tQnHC3Q1ctKrfVxp01kA_4e5avb9Ob5w)

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] ❌Ensure your protecting your trucking business with these resources and making personal connections❌

[BE . Logistics LLC]

[ View in 
browser](https://5y0ou.r.ag.d.sendibm3.com/mk/mr/sh/1t6AVsd2XFnIGIUn9Mot3ZmqZCTQ5T/YnVYZNYQ7IlC)

The intent of this list is to help carriers and freight dispatchers form direct 
relationships with freight brokers outside of using the load boards.

This list has 2000 Freight Broker contacts, which includes their company name, 
contact information, location, and email addresses.

 

EVERYTHING you need to begin making relationships that’ll take your business to 
new heights! 

We compiled a directory of  a/c, container, pipe, reel, steel, and wire 
shippers from within the multiple states for Flatbeds and Hot Shots.

 

**DISCLAIMER: Use of this directory does not guarantee sales. Results may vary 
and are dependent upon you ability.

Are you looking to leverage a trailer you own to another owner operator and get 
paid?

 

If so, this lease agreement is an asset to you to ensure all parties are on the 
same page and you’re not liable for any issues that may transpire.

Please PROTECT yourself!


Are you a Motor Carrier looking to add Owner Operators unto your business? 

 

If so, you’re required to have a lease agreement.

This is perfect for those that need a Lease Agreement immediately . Once 
purchased you will receive the download. Just edit your details and send to 
your potential Owner Operator.

Why is a Bill of Lading important?

 

A bill of lading is one of the most important documents in the shipping 
industry. It is a legally binding document providing the driver and the carrier 
all the details needed to process the freight shipment and invoice. Not every 
shipper/broker provides a Bill of Lading, so being prepared with a Bill of 
Lading for each carrier will help assist in proper documentation, saving the 
carrier time, and being able to receive payment for services rendered.

This item is a basic invoice template.

 

This is perfect for those that need an invoice immediately. Once purchased you 
will receive the download. Just edit your details and send to your customer.


[ **ALL THE 
RESOURCES!!**](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/h5Z6hKc8uVRUOq6zV_l4GLojwBSry4Ah29OUiQwNjitlfgxKT0MXQZqgtvuBJkcLfWMCtZBx462bWv_XgQZZ_biSilklH8gpR0CyKbNpViKK8sHs4O4g3Hc1Ts4Yqjx3olW4eMdEOI9Wu_O-Uga6FD8Xdio4xqsB5rFrDs9Z7Lzch7ATMXuYjyQ-T1t8Yip702gkg2360z4LVPGaVp0/dispatcher-carrier-document-resources)
-

**BE. Logistics LLC**

[**https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/EEmZY3len2R16ZmI--nFTdqDeGxVtew8XgtQ-cNWU3BJV8QB4px9PGFaz5inTSd6tcalQALACp29GHuOm88lc3aBOTQ5etMEDUYGPsg5QXT2_EbLt1M7I7mqRoikwQLdL3jD0OyYr_W4oOXCWVqom-UGDd-3ARtKRqMLhSOWRE3a2Svbv5CnbB0HKHWqG2rmBkdRo8oJdtE8nZrUrgo-**](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/5DrdDaoEk3leb4qYMHSnnudAoDoHCepNdvP7aL1JZClGlj3wNCQlliITh0pIkF6nzjPYKGZB5qrizODh0SHvGHveCLZxNHjn9CVBmjj_bHzummPBz8m2F-Yay-rVvmWfc-qr2-OwpXVdOiea6lFgqv8VkJU6IAZTVY4AvMTH5497Ba7OJaT3AoNowx9OHj5R3V8gJIiNiIpY09MzL-w1)

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Implementation Issues with Opensips as a Load Balancer

[Joan Leyrana]

Hello Team, I'm trying to implement Opensips with Asterisk as a load
balancer (I have been looking at the documentation, but I can't find a
guide for the newer versions of Opensips). I have already installed the
MySQL database, Opensips version 3.3, and OCP 9.3.3. I have added my
Asterisk servers to the load balancer, generated my load balancer script,
and activated the necessary modules in the config file. However, it is not
working for me, and I have the following doubts:

Will the VoIP phones register with Opensips? Why does generating the load
balancer script disable the registrar module?

The route logic generated by the load balancer is not working, or at least
it doesn't allow me to register the phones.

My understanding is that the route is as follows:

VoIP Phone -- >Registrar --> Opensips Opensips --> Media --> Asterisk

Am I skipping any important steps

Regards,

[image: Banner] 
*Joan Leyrana*
Gerente Infraestructura | Nextor Telecom
*O *55 4440 6008
*E *j...@nextor.io
Presa Falcón 128 Irrigación, CDMX 11500
*www.nextor.io* 
[image: facebook icon] 
[image: twitter icon] 
[image: youtube icon]

[image: linkedin icon] 
[image: instagram icon] 
[image: Banner] 
[image: Banner]

[image: Banner] 

Contacto con supervisor : *cali...@nextor.io *

Considere el medio ambiente antes de imprimir este mensaje.
*CONFIDENCIALIDAD.* Este mensaje puede contener información confidencial,
por lo que su divulgación está prohibida de acuerdo a las leyes aplicables.
Si usted no es el destinatario o el responsable de la entrega del presente,
se le notifica que la publicación, distribución o reproducción de este
mensaje, quedan estrictamente prohibidas. *AVISO DE PRIVACIDAD*. NZXT
TELECOMUNICACIONES DE MEXICO, S.A. DE C.V., con domicilio en Presa Falcón
128 Primer piso, Colonia Irrigación, CDMX 11500, utilizará sus datos
personales recabados para proveer y/o realizar gestiones administrativas
relacionadas con los servicios y/o productos que ofrece. Para mayor
información acerca del tratamiento de los derechos que puede hacer valer,
puede acceder al Aviso de Privacidad Integral a través de la página de
internet www.nextor.io
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] ❌ Want to connect DIRECTLY with Freight Brokers without a Dispatcher or load boards❌

[BE . Logistics LLC]

[ View in 
browser](https://5y0ou.r.ag.d.sendibm3.com/mk/mr/sh/1t6AVsd2XFnIGIUn9Mot3ZmqZCTQ5T/kPk6G5y5fqyg)

[ **BROKER CONTACT 
LIST!!**](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/1U3FrHcnsukOuYw32vW1Tq1jNQ5ftFVXQJEx1Jn-eV-VE0QPr6kNICnXuub-cpV81l-rGKqkHCr_fQAE6rRw8MBEguXQO44TWQ46zL4LeCAiELdPoElUTiV_yOtLuzv3tYiS1hv71lSRiP9L1uo2OFWE9XvzwCznIxw3FweD7jFf-THuObxq9rsaE5Rx_npktTx2FnAy11yfIOALLTE/products/p/new-authority-broker-list-tnf6n-yf9jc-87ap6-r2lsc)
--


###The intent of this list is to help carriers and freight dispatchers form 
direct relationships with freight brokers outside of using the load boards.
###

###This list has 2000 Freight Broker contacts, which includes their company 
name, contact information, location, and email addresses.
###==

### 

###EVERYTHING you need to begin making relationships that’ll take your business 
to new heights! 
###=

**BE. Logistics LLC**

[**https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/tiTQNd1EmEgC5_ajX_MNIwqGqHqUFqqRfj2pv_pJ28P7CorXrNC7e1tsSduaVhxgr-yLXppy1NLeD1yUQ4Is1Yd1op1sFTG7EDtxCFqbbFK2gF4sFL6fvRfHgm8VcZQtlw7ehO2mksGMtvEGvI_ZlPxtLYp_C9Dfmgs4iuPJwxJgU8vpmZ4uKsPT1zrcZZVObi9XWbKGRuiGjvYYRzM**](https://5y0ou.r.ag.d.sendibm3.com/mk/cl/f/HByTNAASXXC1z4Qz0rJiW_YuagDNLo7xZg7FxAVhcVBxejPemG_cXxJnK5ijFjnW5_zX3WUX7OfjjpxjUlVFbgftuuj4eetisvf9wMegHQz1sQ80d5wmgpbniixKzt8p46EEVTEZGTGe5zzqhoMyMiCVnYdlGsIAjlEpw2ebOl1cwYCe5pLK62oyueRf1vE8gIAOovAOn23nx2ywMjA)

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] B2B Opensips + RTPEngine

[chaker . barkaoui]

Hi Bogdan-Andrei,
Thank you for your help, the rtp_relay_engage function worked very well and we 
can now have the SDP changed correctly when the frames are passing the B2B 
opensips.

## Handle rtp_relay
  $rtp_relay = "co";
  $rtp_relay_peer = "co";
  $rtp_relay_engage("rtpengine");

We are meeting a new problem : we have two interfaces on our Opensips, one 
external and one internal and we have to change the SDP engage with each 
interface.
We want the opensips to change SDP with RTP internal when we're going from 
external to internal (in UAS mode), and with external in the other way (in UAC 
mode).


SIP1   SIPext  SIPint   
  SIPcl
  +   INVITE (SDP RTP1) >   B2B -- INVITE (SDP 
RTPint) --->   Client
RTP1  RTPext   RTPint   
  RTPcl


   <---   200OK  (SDP RTPext)    B2B<-- 200OK  (SDP 
RTPcl) ---   Client




Thanks for your help.

Chaker Barkaoui
Ingénieur Support et Intégration
Sofrecom Tunisie
Orange/CXMB/SOFRECOM/UA
 
IT/SOFRECOM
 
TUNISIE/C2S
 
OLT/ENABLERS
Immeuble Sterling, Rue du lac de Biwa 1053 Les berges du lac .
[cid:image001.png@01D9AD95.7E146B20]
www.sofrecom.com
Part of the Orange group
__
De : Users 
mailto:users-boun...@lists.opensips.org>> De 
la part de Bogdan-Andrei Iancu
Envoyé : lundi 12 juin 2023 08:24
À : OpenSIPS users mailling list 
mailto:users@lists.opensips.org>>; GUESMI Amel 
SOFRECOM mailto:amel.gue...@orange.com>>
Objet : Re: [OpenSIPS-Users] B2B Opensips + RTPEngine

Hi Amel,

With 3.3 you can use the this 
https://opensips.org/docs/modules/3.3.x/rtp_relay.html#func_rtp_relay_engage - 
the engage will take care of all sequential (in the b2b scenario) insertion of 
the rtp relay you use.

Regards,

Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

  https://www.siphub.com
On 6/8/23 10:28 AM, amel.gue...@sofrecom.com 
wrote:
Hello,

We are using opensips 3.3

Amel

De : Users 
 De 
la part de Bogdan-Andrei Iancu
Envoyé : jeudi 8 juin 2023 08:12
À : OpenSIPS users mailling list 
; KHARROUBI Mohamed 
SOFRECOM 
Objet : Re: [OpenSIPS-Users] B2B Opensips + RTPEngine

Hi,

Which OpenSIPS version do you use? some have auto rtp engaging support via the 
rtp_relay module.

Regards,


Bogdan-Andrei Iancu



OpenSIPS Founder and Developer

  https://www.opensips-solutions.com

  https://www.siphub.com
On 6/6/23 6:06 PM, 
mohamed.kharro...@sofrecom.com wrote:
Hello Community,

We are trying to set up an Opensips with RTPEngine in a B2B configuration to 
handle media processing. There is no scenario for the B2B we're trying to 
implement, we're just using the topology « «top hiding » !

However, regardless of our configuration, the SDP of the INVITE and 200 OK 
packets is not modified to include the RTPEngine IP address and port

How should the RTPEngine be configured in the Opensips.cfg or which function(s) 
should be called to achieve this?


Bien Cordialement,
[cid:image002.png@01D9AD95.7E146B20][cid:image003.jpg@01D9AD95.7E146B20] 

Kharroubi Mohamed
Senior DevOps/System Engineer
Orange/ IMT/ OLPS/ OPS/ International Centers/ Tunisia

mohamed.kharro...@sofrecom.com
www.sofrecom.com

Part of the Orange group




___

Users mailing list

Users@lists.opensips.org

http://lists.opensips.org/cgi-bin/mailman/listinfo/users



___

Users mailing list

Users@lists.opensips.org

http://lists.opensips.org/cgi-bin/mailman/listinfo/users

___
Users mailing list
Us

[OpenSIPS-Users] Call center issue in 3.1; call center not working after migration to 3.2

[Kosmas Palios]

Hello community,

Our team has managed to setup a SIP Trunk to forward calls to a number of
SIP clients, in opensips 3.1.16. We are using the call center module, and
it works fine for low traffic. We would like to ask two separate but
related questions.

ISSUE 1

We are using the call center module to forward calls to 100 SIP agents, and
it works well if traffic is relatively low (about 25 incoming calls per
minute). However, when traffic is higher, i.e. up to 60 incoming calls per
minute, we see calls getting rejected because of cc_handle_call() failing
with error message:

DBG:b2b_entities:server_new: It is a retransmission, drop

ERROR:b2b_logic:b2b_process_scenario_init: failed to create new b2b server
instance

Unfortunately, every time this happens, an agent's status gets stuck to
"incall" forever, even though no cc_calls row includes him. So that agent
is lost.

We are running in UDP mode, using 6 UDP workers. I’m attaching the
configuration file as opensips_3_1_16.cfg

I can share the whole setup if needed.

ISSUE 2

We decided to migrate to 3.2 after seeing the bugfix to b2b_clients leak.
When we got to migrating the call center, we read this blogpost:
https://blog.opensips.org/2021/01/06/the-script-driven-sip-b2bua/

" When comes to the modules using the b2b_logic API (providing features on
top of the B2B engine), the only affected one is the call_center module.
The change is minor – the xml file controlling the call queuing logic was
removed, as not needed any more. Otherwise, in terms of usage, it is
exactly the same."

However, when we removed the lines:

modparam("b2b_logic_xml","script_scenario",
"/etc/opensips/scenario_callcenter.xml")

modparam("call_center", "b2b_scenario", "call center")

the call center started behaving weird: it created another invite to the
sip trunk, instead of creating the invite to the agent (the call id was
good, but the to uri was wrong). I can give detailed logs on this, but I
wouldn't want to make this email any bigger than it already is. I’m also
attaching the configuration file as opensips_3_2_13.cfg

To sum up, our questions are:

1. Any ideas on what the problem is with creating a new server instance for
high numbers of calls?

2. What's the recommended way to migrate the call center to version 3.2 ?
Can we find an example script-driven call center somewhere?

Thank you in advance for your help!

Best regards,

Kosmas


P.S.: about our team: we are a small team from Athens, Greece integrating
voice assistants on various platforms. Unfortunately we missed the latest
Opensips summit held last September.


opensips_3_1_16.cfg
Description: Binary data


opensips_3_2_13.cfg
Description: Binary data
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] SRV fail-over on registration

[Chad Attermann]

Hello,

It’s clear from docs and testing that OpenSIPs will fail-ver to less-preferred 
SRV record on INVITE, but it does not appear to do the same on REGISTER. Is 
this by design or am I missing something? I can’t seem to find anything 
relevant in docs either.

Thanks,

Chad.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users