[OpenSIPS-Users] push notifications - and now packages failing

2024-03-15 Thread rvg
Hi all,

Maybe I thought wrong and I tried another system with AMD-INTEL architecture.

Desperate I started to install packages.





The following packages have unmet dependencies:



mediaproxy-common : Depends: python3 (< 3.9) but 3.10.6-1~22.04 is to be 
installed



E: Unable to correct problems, you have held broken packages.



Any advice is appreciated

Regards,

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


[OpenSIPS-Users] Freeswitch integration

2024-03-15 Thread Dragan, Calin via Users
Hi,

I'm trying to use Freeswitch as a media server with Opensips as a load 
balancer, I need something very basic for a POC. (I configured the load 
balancer and dispatcher based on old information found here: 
https://developer.signalwire.com/freeswitch/FreeSWITCH-Explained/Enterprise-Deployment/Enterprise-deployment-OpenSIPS_13173169/#freeswitch-configuration,
 here: 
https://developer.signalwire.com/freeswitch/FreeSWITCH-Explained/Auxiliary-Knowledge-and-Utilities/OpenSIPS-configuration-for-2-or-more-FreeSWITCH-installs_13173462/
 and here: 
https://www.opensips.org/Documentation/Tutorials-OpenSIPSFreeSwitchIntegration)

I'm adding the X-Auth-IP header to the requests like this (this is based on the 
config that ships with the 3.4.x release in the docker image, so I guessed that 
this is where I should add the header):

route[relay] {
   # for INVITEs enable some additional helper routes
   if (is_method("INVITE")) {
remove_hf("X-Auth-IP");
   append_hf("X-Auth-IP: $si\r\n");
   append_to_reply("X-Auth-IP: $si\r\n");
   xlog("L_INFO", "$ci|log|X-Auth-IP: $si\n");
   xlog("L_INFO", "SIP Message: $mb");

  t_on_failure("missed_call");
  t_on_branch("per_branch_ops");
  t_on_reply("handle_nat");
   }

   if (!t_relay()) {
  send_reply(500,"Internal Error");
   }
   exit;
}

On the freeswitch side I added the IP set by opensips in the list of allowed 
addresses.

Now, with or without authentication enabled on the Freeswitch side (i.e. 
regardless of what I set in the "auth-calls" param, or if I enable the 
accept-blind-auth), or even whether the Freeswitch is running or not, when I 
try to place a call from/to some registerd addresses, I get the "407 Proxy 
authentication required" response.

Could you please give me some hints on what I might be doing wrong, or direct 
me to a contemporary tutorial?
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] TLS - Private Key fails

2024-03-15 Thread Rodrigo R Passos
Hi everyone,


I'm trying to start opensips with a certificate generated by opensips-cli,
like a tutorial. I have the following results keys after completing the
command.

INFO: user certificate created in /etc/opensips/tls/user/wss-cert.pem

INFO: user private key created in /etc/opensips/tls/user/wss-privkey.pem

INFO: user CA list (chain of trust) created in
/etc/opensips/tls/user/wss-calist.pem


This is my configuration, in opensips.cfg:

modparam("tls_mgm", "server_domain", "wss")
modparam("tls_mgm", "match_ip_address","[wss]10.0.0.114:5443")
modparam("tls_mgm", "ca_dir", "[wss]/etc/opensips/tls/rootCA/certs")
modparam("tls_mgm", "ca_list", "[wss]/etc/opensips/tls/user/wss-calist.pem")
modparam("tls_mgm",
"certificate","[wss]/etc/opensips/tls/user/wss-cert.pem")
modparam("tls_mgm",
"private_key","[wss]/etc/opensips/tls/user/wss-privkey.pem")
modparam("tls_mgm", "verify_cert", "[wss]0")
modparam("tls_mgm", "require_cert", "[wss]0")
modparam("tls_mgm", "ciphers_list", "[wss]NULL")
modparam("tls_mgm", "tls_method", "[wss]TLSv1")


So, when I start opensips, the log shows information saying the private key
doesn't match with the public key. Follow the log:


Mar 15 14:27:14 esbc01 opensips[80845]: Mar 15 14:27:14 [80845]
ERROR:tls_openssl:load_private_key: unable to load private key file
'/etc/opensips/tls/user/wss-privkey.pem'.

Mar 15 14:27:14 esbc01 opensips[80845]: Retry (2 left) (check password case)

Mar 15 14:27:14 esbc01 opensips[80845]: Mar 15 14:27:14 [80845]
ERROR:tls_openssl:load_private_key: key
'/etc/opensips/tls/user/wss-privkey.pem' does not match the public key of
the certificate

Mar 15 14:27:14 esbc01 opensips[80845]: Mar 15 14:27:14 [80845]
ERROR:tls_mgm:init_tls_domains: Failed to init TLS domain 'wss'

Mar 15 14:27:14 esbc01 opensips[80845]: Mar 15 14:27:14 [80845]
ERROR:core:init_mod: failed to initialize module tls_mgm

Mar 15 14:27:14 esbc01 opensips[80845]: Mar 15 14:27:14 [80845]
ERROR:core:main: error while initializing modules



All procedures to create my own certificate follow the tutorial.


Anyone know what is happening or have any problems like me?


BR


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


[OpenSIPS-Users] Problems with new installation of 3.4

2024-03-15 Thread Stefan Carlsson
Hi !

After followed the installation of 3.4 LTS to a fresh ubuntu ver 22 a found 
some serious problems ...

installing is done via apt.

1) Not all the modules were included in the rep. as it should ref. to spec. 
vers.  manual

2) After downloading the source , trying to compile the modules missing...  
dependencies needed and info is missing in the main doc. or moduledoc.

For example:

make: *** No rule to make target '../../lib/digest_auth/libdigest_auth.a', 
needed by 'uac_auth.so'.  Stop.

trying to make all from opensips src. root folder ...

Compiling main.c
In file included from main.c:152:
ssl_tweaks.h:2:10: fatal error: openssl/opensslv.h: No such file or directory


Any ideas ...


Mvh // Regards ...
_
Stefan Carlsson

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


Re: [OpenSIPS-Users] OpenSIPs generate PRACK

2024-03-15 Thread Social Boh
I'm trying using directly opensips-cli via exec module to see if all OK 
and then pass the data tu mi_script module


I think I have a sintaxis problem with the line:

exec("opensips-cli -x mi t_uac_dlg method=INVITE 
ruri="sip:alice@127.0.0.1:7050" headers="From: 
sip:bobster@127.0.0.1:1337\r\nTo: sip:alice@127.0.0.1:7050\r\nContact: 
sip:bobster@127.0.0.1:1337\r\n"")


I don't know how use " in the line because Headers and ruri need them. 
The result is a error:


ERROR:core:handle_mi_request: Invalid parameters

Any hint, please?

Regards

---
I'm SoCIaL, MayBe

El 26/02/2024 a las 7:43 a. m., Bogdan-Andrei Iancu escribió:
yes, you can use the b2b_logic (together with b2b_entities) for that, 
but it may be a too heavy tool for the purpose. Maybe you can try to 
generate the PRACK from OpenSIPS level by using the t_uac_dlg MI 
function [1] via the mi_script module [2] - basically to trigger that 
MI cmd from the onreply_route, when receiving the 180 reply.


[1] https://opensips.org/html/docs/modules/3.4.x/tm.html#mi_t_uac_dlg
[2] https://opensips.org/html/docs/modules/3.4.x/mi_script.html#afunc_mi

Regards,
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com
On 25.02.2024 14:54, Social Boh wrote:


I know the best way is the original caller handle and reply the 183, 
but I HAVE to do this at OpenSIPs level.


Can I use B2B_Entities and B2B_logic to do this? Is there a scenario 
to use tu parse and reply the 183?


Thank you

---
I'm SoCIaL, MayBe
El 16/02/2024 a las 11:31 a. m., Bogdan-Andrei Iancu escribió:
I agree here, the 183 must be relayed back to the original caller 
(which generate the received INVITE) and let it do the PRACK - this 
confirmation must be end-2-end in the dialog.


Regards,
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com
On 12.02.2024 11:36, Ihor Olkhovskyi wrote:
You should relay 183 to original source (ione that is sending 
INVITE) and got PRACK from there.

That would be the most correct way of handling this

Le lun. 12 févr. 2024 à 02:29, Social Boh  a 
écrit :


Maybe someone can help me.

This is the scenario.

OpenSIPs receive a INVITE and send it to a server that reply
with a 302
message (always)

Then OpenSIPs, in the failure route, take the user part present
in the
302 contact header, change the destination IP and send with t_relay

The destination reply with a 183 with Require: 100rel header so
OpenSIPs
have to reply with a PRACK. This is my problem.

I don't know which is the best way to handle this (the PRACK)

Thank you

Regards

---
I'm SoCIaL, MayBe

El 9/02/2024 a las 6:46 a. m., Social Boh escribió:
> Hello list,
>
> can OpenSIPs generate a PRACK message to reply a 180/183 message?
>
> Thank you
>
> Regards
>
> ---
> I'm SoCIaL, MayBe
>
>
> ___
> 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



--
Best regards,
Ihor (Igor)

___
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
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users