Does anyone have any information on a distributed installation?

706 views
Skip to first unread message

Darren Williams

unread,
Nov 18, 2019, 6:37:22 PM11/18/19
to ivozprovider-users
The Ivozprovider team says the standalone installer is not for production and is just for testing etc but there appears to be no documentation whatsoever on installing for production use.

Does anyone have a distributed installation working?

Thanks
Daz

john gord

unread,
Jan 9, 2020, 11:20:42 AM1/9/20
to ivozprovider-users
Depends what you mean by distributed.  If you use it exactly the way it's designed it should work.  It's not designed to have more than one DB live. Either Redis or MySQL.  That is one of the things to be aware of.

Here are a few notes I made to myself.  Setting DNS properly is very important so that the servers can find each other.  These notes are at least a year old.  Recent changes may make some of these notes inaccurate.

# MAKE SURE RESOLV.CONF IS EDITABLE
chattr -i /etc/resolv.conf
mv /etc/resolv.conf /etc/resolv.conf.orig
touch /etc/resolv.conf

# SET resolv.conf TO LOOK AS FOLLOWS:
domain ivozprovider.local
search ivozprovider.local
nameserver 127.0.0.1
nameserver 8.8.8.8

apt install ivozprovider-profile-data
apt install ivozprovider-profile-proxy
apt install ivozprovider-profile-portal
apt install ivozprovider-profile-as


systemctl enable kamailio@users
systemctl enable kamailio@trunks
systemctl start kamailio@users
systemctl start kamailio@trunks


#### CHECK ALL IVOZ DAEMONS

systemctl status mysql
systemctl status redis
systemctl status bind9
systemctl status apache2
systemctl status memcached
systemctl status supervisor
systemctl status gearman-job-server
systemctl status cgrates
systemctl status kamailio@users
systemctl status kamailio@trunks
systemctl status rtpengine
systemctl status ivozprovider-cdrs.timer
systemctl status asterisk

## VIEW CGRATES API TRAFFIC on local interface
ngrep -t -W byline port 2080 -d lo

## Config files
/etc/hostname
/etc/hosts
/etc/resolv.conf
/etc/supervisor/conf.d/*.conf
/etc/default/rtpengine
/etc/default/rtpengine-recording
/etc/cgrates/cgrates.json
/etc/bind/db.ivozprovider.local
/etc/asterisk/pjsip.conf
/etc/asterisk/manager.conf

## GOTCHA's
### IF KAMAILIO TRUNKS AND USERS ARE THE SAME SERVER
### MAKE SURE KAMAILO TRUNKS setting is port 7060
/etc/asterisk/pjsip.conf

contact=sip:trunks.ivozprovider.local
# Needs to be changed to
contact=sip:trunks.ivozprovider.local:7060


# VIEW SUPERVISOR STATUS
systemctl status supervisor
supervisorctl status

# VIEW GEARMAN STATUS
gearadmin --status
gearadmin --workers

###### VIEW GEARMAN WORKER LIST
----------

/opt/irontec/ivozprovider/microservices/workers/bin/console gearman:worker:list

## VIEW WORKER DETAILS OF ONE OF THE WORKERS FROM ABOVE LIST
/opt/irontec/ivozprovider/microservices/workers/bin/console gearman:worker:describe WorkerCgrates

john gord

unread,
Jan 9, 2020, 11:27:55 AM1/9/20
to ivozprovider-users
I should point out that I install everything on all servers to keep things simple and consistent.  That way I can make a template and use the same template for all servers.  I then enable/disable services depending on what that server is going to be used for.

Amor klich

unread,
Oct 22, 2021, 11:18:20 AM10/22/21
to ivozprovider-users
hello 

Thank you for your sharing .
I have an issue with distributed install , i didn't install like you but with profiles on 4 vms .
DB Portal and AS are OK but proxy isn't working kamailio user and trunks not coming up and cgrates also with a problem with redis protected mode .
Actually I am trying to make kamailio work here is my config 

KAMAILIO_TRUNKS 

#!KAMAILIO

#########################################################################################################
#
#        IRONTEC - ARTEMIS // Kamailio Proxy for Trunks
#
#########################################################################################################

####### Defines #########

#!define SIP_PORT 5060
#!define SIPS_PORT 5061
#!define RPC_PORT 8001
#!define XMLRPC_PORT 8002

And KAMAILIO USERS 

#!KAMAILIO

#########################################################################################################
#
#        IRONTEC - ARTEMIS // Kamailio Proxy for Users
#
#########################################################################################################

####### Defines #########

#!define TRUNKS_SIP_PORT 7060
#!define SIP_PORT 5060
#!define SIPS_PORT 5061
#!define RPC_PORT 8000
#!define WS_PORT 10080
#!define WSS_PORT 10081



Looks like a conflict with port 5060 
I have tried with port 5060 and 7060 and still the same 



root@IVOZ2:~# kamtail-proxytrunks
-- Logs begin at Fri 2021-10-22 10:12:17 CDT. --
Oct 22 10:13:47 kamailio[1000]:              tcp: trunks [10.0.0.220]:8001
Oct 22 10:13:47 kamailio[1000]:              tcp: trunks [10.0.0.220]:8002
Oct 22 10:13:47 kamailio[1000]:              tls: trunks [10.0.0.220]:5061
Oct 22 10:13:47 kamailio[1000]: Aliases:
[Oct 22 10:13:47] dmq [dmq.c:228]: mod_init(): server_uri is not a socket the proxy is listening on
[Oct 22 10:13:47] <core> [core/sr_module.c:986]: init_mod(): Error while initializing module dmq (/usr/lib/x86_64-linux-gnu/kamailio/modules/dmq.so)
Oct 22 10:13:47 systemd[1]: kama...@trunks.service: Control process exited, code=exited status=255
Oct 22 10:13:47 systemd[1]: Failed to start Kamailio - the Open Source SIP Server.


Any help will be appreciated  ; )

OCR

unread,
Mar 25, 2022, 3:38:21 AM3/25/22
to ivozprovider-users
Hi, 
Would you have a step by step of the distributed installation? When I install each profile in the 4VM, it is asking for a configuration that is not indicated in any documentation.
Regards.

Ciprian Arsenie

unread,
Jul 28, 2023, 8:31:06 AM7/28/23
to ivozprovider-users
I need help installing distributed install , can somebody make a small tutorial how to install .

Angelo de Barros Delphini

unread,
Aug 10, 2023, 3:43:23 PM8/10/23
to ivozprovider-users
Hello Jhon Gord, fraternal greetings, Following your step by step, I found some problems about the Ivoz Provider Standalone 3.2 version, I'm having a lot of difficulties to actually run and use the Ivoz Provider, something that seemed very simple, is becoming a headache, of course the fact is my little knowledge about the solutions. If anyone can shed some light, I would appreciate it, Here are the main conflicts:

2023-08-10_16-34.png

2023-08-10_16-35.png

2023-08-10_16-37.png

2023-08-10_16-38.png

2023-08-10_16-39.png

2023-08-10_16-40.png

2023-08-10_16-42.png

Thank you all for some guidance as I badly need to get the platform into production for a POC and usage approval by my board.

AirsayLongCon

unread,
Aug 10, 2023, 4:46:42 PM8/10/23
to ivozprovider-users
Have you completed your install using the stand alone iso provided by irontec? or Have you tried to install it on a fresh Debian install? It looks like you have used the  iso. What steps did you follow to install it? Is this install on a Bare metal or Virtual Machine?

Angelo de Barros Delphini

unread,
Aug 11, 2023, 8:37:00 AM8/11/23
to ivozprovider-users
Good morning, thanks for getting back. I used the ISO provided by Irontec. The installation is over a virtualized environment with Xen Server. Follow the steps provided in the documentation: URL: (https://irontec.github.io/ivozprovider/en/bleeding/basic_concepts/installation/cd_install.html). As it is a POC, the procedure is all services in a single appliance. After the POC we will use the distributed methodology.

AirsayLongCon

unread,
Aug 11, 2023, 10:26:40 AM8/11/23
to ivozprovider-users
Whats the ip address of your VM?

On the command line run "ip a" (without the quotes) to display your VMs IP. Also when you did the install, there was a screen that requested you to enter (and confirm) the mysql root password. Did you enter the same password when you had to configure ivozprovider?

AirsayLongCon

unread,
Aug 11, 2023, 10:31:38 AM8/11/23
to ivozprovider-users
Just to reiterate, there are two screens where you have to enter mysql root password. The first one (shown in the attachment below) you are CREATING the root password for mysql. In the second one, make sure you enter the same root password as the one you initially created
Screenshot from 2023-08-11 07-28-57.png

Angelo de Barros Delphini

unread,
Aug 11, 2023, 10:57:28 AM8/11/23
to ivozprovider-users
Yes, I performed this procedure on MySQL ROOT passwords. But I can reinter with dpkg-reconfigure ivozprovider if that's the case. I have a set of IP, from LAN is 10.11.12.239, from VPN is 172.28.12.239 (for remote admin only). And I have the public domain that I will use in the project. But can I be validating the settings files if the password is there or is it in the DB?

Airsay Longcon

unread,
Aug 11, 2023, 12:10:26 PM8/11/23
to Angelo de Barros Delphini, ivozprovider-users
When you assign IP addresses for the Kamailio Proxy Users and Proxy Trunks, are using the LAN address as the IP address? Or do you provide your public IP address? As far as I know, the standalone requires you to have the server's nic to have a Publicly reachable ip address. If your server is behind a NAT, you'd struggle to get ivoz to work unless you good knowledge of Kamailio. I've gotten it to partially work behind a NAT. But calls get dropped after 32 seconds as the remote end is unable to send an ACK to the final 200 OK when the call is established

On 11 Aug 2023, at 15:57, Angelo de Barros Delphini <angelo....@gmail.com> wrote:

Yes, I performed this procedure on MySQL ROOT passwords. But I can reinter with dpkg-reconfigure ivozprovider if that's the case. I have a set of IP, from LAN is 10.11.12.239, from VPN is 172.28.12.239 (for remote admin only). And I have the public domain that I will use in the project. But can I be validating the settings files if the password is there or is it in the DB?
--
You received this message because you are subscribed to a topic in the Google Groups "ivozprovider-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ivozprovider-users/YMXO3EWmdK4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ivozprovider-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ivozprovider-users/6cc35788-d0a9-4e70-adf3-3901c6937942n%40googlegroups.com.

Angelo de Barros Delphini

unread,
Aug 17, 2023, 10:39:46 AM8/17/23
to ivozprovider-users
Good morning everybody... Airsay understood your concern. When installing, the Lan IP => 10.11.12.239 and the domain IP => 189.XXX.XXX.28 were provided. 

I'm not worried about that. What actually happened is that the ISO should have installed all services on a single device. 

And it didn't... So I'm looking at how to install one by one so that the Ivoz Provider platform runs. 

See my inconvenience is that I couldn't even install the platform! 

That is, either I'm very retarded, or there's something wrong that isn't right...

Airsay Longcon

unread,
Aug 17, 2023, 12:38:23 PM8/17/23
to Angelo de Barros Delphini, ivozprovider-users
So I've spent many hours installing and reinstalling artemis and halliday versions of ivozprovider. And I've been learning a lot. One key learning for me is that unless you have very good knowledge of Kamailio and RTPENGINE, it is very very difficult running ivozprovider behind a NAT router. I had tried installing ivozprovider using the all-in-one iso on a Proxmox VM. I've also repeated the same installation using vanilla version of Debian 9 and Debian 11. While I was able to get both to "work" and I could register to extensions from outside the LAN, I couldn't fix audio issues as calls were ended after 32 seconds because one of both parties (often the calling party) could send an ACK to the 200 OK when a session was established. 

I ended up going with a cloud server with a single publicly accessible IPv4 address. I still had issues using a single IP address. Went with two IP addresses and eventually made progress. However I'm still having issues with extension-to-extension calls. I could call Bon from Charles's extension but couldn't do the reverse (getting a Decline). I'm still twiddling with it to get a good hang of it and hopefully get see competence understanding how it needs to be configured 

On 17 Aug 2023, at 15:39, Angelo de Barros Delphini <angelo....@gmail.com> wrote:



Angelo de Barros Delphini

unread,
Aug 17, 2023, 12:56:45 PM8/17/23
to ivozprovider-users
This is really complicated, I bought Kamailio's book (official) I'm studying hard. 

As for your idea, it's very good. 

I'll talk to my infra team. 

Thanks for the tips and info... I'm still in the fight!!!

Ciprian Arsenie

unread,
Aug 17, 2023, 1:41:08 PM8/17/23
to Angelo de Barros Delphini, ivozprovider-users
Normaly this platform works well with public ip addresses. I have succes installing on multiple servers and it works, i still have allot to learn.


Trimis de pe iPhone‑ul meu

Pe 17 aug. 2023, la 19:56, Angelo de Barros Delphini <angelo....@gmail.com> a scris:



MichaelSTK

unread,
Aug 18, 2023, 4:16:19 AM8/18/23
to ivozprovider-users
Do you think its possable to get it work with a local server with 2 privated ip addresses?

Op donderdag 17 augustus 2023 om 19:41:08 UTC+2 schreef arsenie...@gmail.com:

AirsayLongCon

unread,
Aug 22, 2023, 9:09:59 AM8/22/23
to ivozprovider-users
Unless you are very knowlegeable in Kamailio, I don't think it is easily doable

AirsayLongCon

unread,
Aug 22, 2023, 9:12:13 AM8/22/23
to ivozprovider-users
If you need some advice from hands-on experience, feel free to reach out.
Reply all
Reply to author
Forward
0 new messages