[OpenSIPS-Users] What are the possible values ​​for the modparam parameter?

2022-08-11 Thread 이재천 
What are the possible values ​​for the modparam parameter? 
 
Such as sipping_bflag in nathelper module,
 
a tutorial in Tutorials-Distributed-User-Location-Full-Sharing show
 
modparam("nathelper", "sipping_bflag", "SIPPING_ENABLE") 
 
and other sample in 
https://www.ictinnovations.com/opensips-as-load-balancer-and-register-with-asterisk-servers-integeration
 shows
 
modparam("nathelper", "sipping_bflag", "SIP_PING_FLAG"). 
 
So I searched for what is the possible value,
 
but the manual page in 3.2.x 
docs(https://opensips.org/docs/modules/3.2.x/nathelper.html) shows only that
 
modparam("nathelper", "sipping_bflag", "SIPPING_ENABLE")
 
and does not shows that what is the possible values and how it acts.
 
Where can I find the information?
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Bug on TLS Management Interface

2022-08-11 Thread Bogdan-Andrei Iancu 

Hi Francisco,

So, if you use wildcard for match_sip_domain in the client TLS domain, 
doesn't work for you ?


Regards.

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
  https://www.opensips.org/events/Summit-2022Athens/

On 8/10/22 5:03 PM, Francisco Neto wrote:

Hi Bogdan-Andrei!

I’ve made the changes and now I can edit the TLS certificates normally 
by control panel but I continue having a problem.


If I configure the certificate directly on the configuration file the 
connection with Microsoft Teams is correctly established, if I 
configure through control panel, I receive on log the following messages:


ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found
Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: 
ERROR:core:tcp_conn_create: failed to do proto 3 specific init for 
conn 0x7f22a5f993d0
Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: 
ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the socket
Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: 
ERROR:proto_tls:proto_tls_send: connect failed
Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: ERROR:tm:msg_send: 
send() to 52.114.132.46:5061 for proto tls/3 failed
Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: ERROR:tm:t_uac: 
attempt to send to 'sip:sip.pstnhub.microsoft.com' failed
Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: 
ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found
Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: 
ERROR:core:tcp_conn_create: failed to do proto 3 specific init for 
conn 0x7f22a5f91420
Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: 
ERROR:core:tcp_sync_connect: tcp_conn_create failed, closing the socket
Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: 
ERROR:proto_tls:proto_tls_send: connect failed
Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: ERROR:tm:msg_send: 
send() to 52.114.76.76:5061 for proto tls/3 failed
Aug 10 11:00:04 bowser /usr/sbin/opensips[55047]: ERROR:tm:t_uac: 
attempt to send to 'sip:sip2.pstnhub.microsoft.com' failed
Aug 10 11:00:05 bowser /usr/sbin/opensips[55047]: 
ERROR:core:tcp_connect_blocking_timeout: connect timed out, 599667 us 
elapsed out of 60 us
Aug 10 11:00:05 bowser /usr/sbin/opensips[55047]: 
ERROR:core:tcp_sync_connect_fd: tcp_blocking_connect failed
Aug 10 11:00:05 bowser /usr/sbin/opensips[55047]: 
ERROR:proto_tls:proto_tls_send: connect failed
Aug 10 11:00:05 bowser /usr/sbin/opensips[55047]: ERROR:tm:msg_send: 
send() to 52.114.32.169:5061 for proto tls/3 failed
Aug 10 11:00:05 bowser /usr/sbin/opensips[55047]: ERROR:tm:t_uac: 
attempt to send to 'sip:sip3.pstnhub.microsoft.com' failed
Aug 10 11:00:09 bowser /usr/sbin/opensips[55047]: 
ERROR:proto_tls:proto_tls_conn_init: no TLS client domain found


I will send attached the screenshot of the control panel and below the 
configuration that works.


If it isn’t related to the same problem tell me and I send the message 
to the open list ok!


Thanks!

# TLS CLIENT
#modparam("tls_mgm", "client_domain", "sbcsothis")
#modparam("tls_mgm", "match_sip_domain", "[sbcsothis]*")
#modparam("tls_mgm", "match_ip_address", "[sbcsothis]*")
#modparam("tls_mgm", "verify_cert", "[sbcsothis]1")
#modparam("tls_mgm", "require_cert", "[sbcsothis]1")
#modparam("tls_mgm", "tls_method", "[sbcsothis]TLSv1-")
#modparam("tls_mgm", "certificate", 
"[sbcsothis]/etc/opensips/tls/user/sothistelecom.com.crt")
#modparam("tls_mgm", "private_key", 
"[sbcsothis]/etc/opensips/tls/user/sothistelecom.com.key")
#modparam("tls_mgm", "ca_list", 
"[sbcsothis]/etc/ssl/certs/ca-certificates.crt")

#modparam("tls_mgm", "ca_dir", "[sbcsothis]/etc/ssl/certs/")Config file



Em 10 de ago. de 2022 04:50 -0300, Bogdan-Andrei Iancu 
, escreveu:

Hi Francisco,

Thanks for the info, it seems it was an issue with the validation 
regexp, see 
https://github.com/OpenSIPS/opensips-cp/commit/7558bc7e36c03293858c7086edfc724d56a2b9b4


So please update from GIT or TAR and give it a try (or simply do a 
manual change as per the diff link).


Let me know if it works now.

Regards,
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/
On 8/9/22 11:46 PM, Francisco Neto wrote:

Hi Bogdan-Andrei! How are you!

Below is all the information that you have request ok, fell free to 
ask me if you need something more!


*version: opensips 3.2.5 (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

poll method support: poll, epoll, sigio_rt, select.
main.c compiled on with gcc 10

*Opensips Control Panel 9.3.2*

*Debian Version 11.2*


Thank you very much for the help!



Em 9 de ago. de 2022 05:39 -0300, Bogdan-Andrei Iancu 
, escreveu:

[OpenSIPS-Users] SRTP connect error

2022-08-11 Thread Vadim Dumalekov via Users 
Hello!

I have a problem with WebRTC-clients. In the log file i see the following line:

/usr/sbin/opensips[10580]: ERROR:rtpengine:parse_flags: error processing flag 
`trust-address': no more memory



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

Re: [OpenSIPS-Users] DBAliases with Late SDP Negotiation

2022-08-11 Thread Bogdan-Andrei Iancu 

Hi,

By "in all other cases" you mean "timeout upon ringing" ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
  https://www.opensips.org/events/Summit-2022Athens/

On 8/10/22 4:20 PM, HS wrote:

Hi again.

Thanks. Exact opposite :) When using an alias, after the call to users 
device is rejected, it is redirecting successfully to VM. However, in 
all other cases it doesn't redirect to VM (when using an alias) and 
times out. On the other hand, everything works as per snippet if using 
subscriber table details.


Does that make sense please?

Thanks.

On Wed, Aug 10, 2022 at 5:25 PM Bogdan-Andrei Iancu 
mailto:bog...@opensips.org>> wrote:


Hi,

So, your issue is that, after the call to user's device is
rejected, and redirecting to VM (via failure route) you have some
wrong RURI, right ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com  
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/  


On 8/10/22 1:51 PM, HS wrote:

Hi again.

Thanks a lot for the quick response. My cfg is a bit of a
trial-and-error based, hence will email it (if that's ok).
However, dbaliases support is inserted as per default residential
script:

if ($rU==NULL) {
# request with no Username in RURI
send_reply(484,"Address Incomplete");
exit;
}

# apply DB based aliases
alias_db_lookup("dbaliases");

Thanks again.

HS.

On Wed, Aug 10, 2022 at 3:31 PM Bogdan-Andrei Iancu
mailto:bog...@opensips.org>> wrote:

Hi,

Could you share the cfg WITH the dbaliases support, to check
where the alias lookup was inserted in the cfg logic ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com  

OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/  


On 8/10/22 1:28 PM, HS wrote:

Hi again Bogdan,

Thanks for responding. I *tried* to add support for aliases.
What is interesting is that the following snippet works fine
on decline (but not otherwise):

if (t_check_status("487|408|486|480|603")){
rewritehostport("INT.IP.XX.XXX:5091");
                t_relay();
                exit;

Any thoughts on how to fix please?

Thanks.

On Tue, Aug 9, 2022 at 2:45 PM Bogdan-Andrei Iancu
mailto:bog...@opensips.org>> wrote:

Hi HS,

The aliases and late SDP negotiation has noting in common.

And the mentioned script has no support for aliase - I
guess you added such support ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com  

OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/  


On 6/20/22 5:21 PM, HS wrote:

Hi all.

Just wondering if anyone has "dbaliases" working with
the Late SDP negotiation script below:

https://opensips.org/pub/docs/tutorials/websockets/opensips-late.cfg



If we call an alias, it works fine if the user is
online. However, in case of offline users I want the
call to be forwarded to another instance/server. If we
use the ID (from subscriber table) calls are being
forwarded. But not if we dial an alias.

Appreciate the help.

___
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

Re: [OpenSIPS-Users] 401 Unauthorized on BYE request

2022-08-11 Thread Bogdan-Andrei Iancu 

Hi Alexey,

The RFC3261 says that any requests with reply (so no ACK) can/may be 
subject to authentication. So SIP-wise, it is fine. In the real-life it 
is quite unusual, still not SF :).


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
  https://www.opensips.org/events/Summit-2022Athens/

On 8/10/22 8:39 PM, Alexey Kazantsev via Users wrote:

Hi list,
is it normal at all — to authenticate BYE requests?
I’ve checked RFC 3261 now, but haven’t found anything corresponding to 
this.

Neither if it’s normal, nor if it’s not normal.
---
BR, Alexey
https://alexeyka.zantsev.com/

___
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

Re: [OpenSIPS-Users] Problem with HEP-monitoring of tls_wolfssl

2022-08-11 Thread Bogdan-Andrei Iancu 
Right, and that's good :). Still I'm trying to understand what were the 
settings that were not properly working - trace_on only in TLS, but not 
in TCP? or?


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 27-30 Sept 2022, Athens
  https://www.opensips.org/events/Summit-2022Athens/

On 8/11/22 9:05 AM, Artiom Druz wrote:

Hi Bogdan.
For now I see that Homer is catching info correctly, and I can see 
what was happened inside TLS calls in Homer's web-interface.


ср, 10 авг. 2022 г., 12:53 Bogdan-Andrei Iancu >:


Hi Artiom,

So you initially had only the trace_on set in the proto_tls
module, generating some HEP packages which were not understood by
HOMER, right ?

And after setting the trace_on in the proto_tcp module, the issue
went away? but do you get HEP packages about about the TCP and TLS
events in OpenSIPS - I'm asking as I have to say this part was not
tested by some time :-/

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com  
OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/  


On 8/10/22 5:44 AM, Artiom Druz wrote:

Hi Bogdan.
I use trace_on parameter of proto_tls module and subroute for
sending messages to Homer.

I enabled trace_on parameter for proto_tcp module and now it
works correct. I'm not sure if this is the only fix I made
because it may have been a misconfiguration in the script logic.

вт, 9 авг. 2022 г., 13:42 Bogdan-Andrei Iancu
mailto:bog...@opensips.org>>:

Hi Artiom,

Do you use any proto TCP or TLS specific tracing (like [1]),
or only pure SIP TLS tracing ?

[1]

https://opensips.org/html/docs/modules/3.2.x/proto_tls.html#param_trace_on



Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com  

OpenSIPS Summit 27-30 Sept 2022, Athens
   https://www.opensips.org/events/Summit-2022Athens/  


On 7/25/22 11:20 AM, Artiom Druz wrote:

Hello Everyone.
I have a problem with monitoring SIPS/TLS based on
tls_wolfssl module via proto_hep (target monitoring service
is Homer 7).
My opensips config works ok with SIP/UDP, but when I make a
call via TLS (OpenSIPS convert TLS from VoIP provider to
internal SIP/UDP software PBX) in dump file on Homer 7 side
I see that all packets in HEP3 payload has this info:

HEP3 Protocol
    HEP Version: HEP3
    HEP Packet Size (Bytes): 152
    IP family: IPv4
    Ingested Transport Protocol: IPv4
    Source port: 0
    Destination port: 0
    Unix Timestamp: 1658731857
    Timestamp µs: 106136
    Application Protocol: Unknown Application Protocol
    Capture Node ID: 1301
    Source IPv4 address: 127.0.0.2
    Destination IPv4 address: 127.0.0.2
    Encapsulated Payload: TLS:CLOSED:SUCCESS:Read error
    Correlation ID: 350784072629638188

Only unix timestamp and capture node id is correct.
As you can see in encapsulated payload I have an error with
read. What can be wrong?

OpenSIPS 3.2.5 (git revision 7e284ab03) compiled from source.

___
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

[OpenSIPS-Users] OpenSIPS Summit 2022 - Speaker's lineup

2022-08-11 Thread Bogdan-Andrei Iancu 




 OpenSIPS Summit


   Sept 27th - 30th, 2022, Athens, Greece


*Speaker's lineup & Schedule
*

We bring here the list of speakers and papers 
 - great 
speakers presenting great topics to share experience and knowledge to a 
great audience. Explore here all the details...




*Attend to learn* - the registration process is already open, for both 
online and in-person participants. Note that the training and Design 
Clinics options are available only for the in-person participants. 
The/*Corporate Package*/ is available with an attractive discount.


Register now 

**









--
Bogdan-Andrei Iancu
  OpenSIPS Founder and Developer
  http://www.opensips-solutions.com

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