21 Mar
2024
21 Mar
'24
11:01 p.m.
Brad,
Sounds like a quite big project. And if you never used a Kamailio before
this "switch" can be quite painful in a sense that you are adding 1
extra component to already working system. Also you may get into a pit
with media relaying upon switching (different signalling and media IP)
without using rtpengine or so, but again, need testing.
What I can suggest is trying to use dSIPRouter
(https://dopensource.github.io/dsiprouter/) to have a "single point of
entry" to all of your PBX'es and than - do a switching from there.
(basically it's Kamailio + GUI) It can help you to test things faster
(and fall faster as well, which is important as well)
Your approach is correct, but I'm really not sure about idea of
"installing Kamailio on each box". Sounds complex and overkill.
Cheers,
Ihor
Le 21/03/2024 à 17:24, Brad via sr-users a écrit :
I need to move a few dozen FreePBXen with some commercial modules
running in individual VMs to a new data center.
I’m trying to work out a plan to move the PBXes to the new data center
in a way that will be transparent to the endpoints, or at the very
least with the absolute minimum of downtime.
Some of the installations are rather old, and there’s a handful of
peculiarities on each, so the typical FreePBX backup/restore process
hasn’t gone smoothly, at least in our tests.
My current train of thought is to put a clone the VMs in the new data
center and use Kamailio to route the SIP traffic to the new
servers/IPs. I’ve never used it before, so I may be barking up the
wrong tree, but it /appears/ to do what I’m suggesting.
If so, I’m thinking I can install Kamailio on each VM, point it to the
local asterisk/FreePBX initially, and clone the VM. Then, after the
new instance is up and running, point Kamailio on the original VM to
the cloned VM's asterisk, after which I can make appropriate DNS changes.
Another option would be to stand up a single Kamailio server and
redirect SIP traffic destined for individual asterisk servers to it at
the router.
Endpoints are mostly Yealink, and I’m not sure if they’ll feel the
need to restart when the registration/SIP server’s IP changes, but a
quick bounce when not in use isn’t the end of the world. I’d very much
like to avoid having to send an update to each phone manually, but I
can script a SIP NOTIFY if required.
Anything stupid, wrong, ignorant, or just smelly about this tactic?
Or, for that matter, any other suggestions?
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email tosr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe: