Hi David,
thank you for the helpful suggestions.
> Having the user register on fs when you have OpenSIPS/kamailio only
> complicates things, not to mention OpenSIPS can take A LOT more
> registers than fs ( on another setup I had around 8k users and
> eventually moved to Kamailio/OpenSIPS as a r
Hello,
I totally misunderstood your question, then.
Still dialplan should be useful. Instead of matching the domain, match the
$ru and send it where it is supposed to be registered based on the
dispatcher id.
If the user can only register on one fs, then you’re good for registers and
conferences
Thanks for your reply and the example, David.
If I did understand your example correct, it basically solves the issue
only for internal calls because of the match for ".*domain*"
My main issue is the scenario where I do get a call from the PSTN. Those
calls do not contain the corresponding Fr
Hello
Dialplan is perfect for this.
I did this on kamailio, but it's probably doable porting it.
It would be something like:
modparam("dialplan", "db_url", DBURL)
...
route[DISPATCH] {
...
# Get the attrs field for the matching domain, will store the result in
$var(dispatcher_id)
dp_transl
Hi list,
I'm currently building a HA setup with 2 openSIPS 2.4 instances which do
share a floating IP through keepalived. They are working as 1:1
mid_registrar, gateway to the PSTN and dispatcher for multiple
FreeSWITCH instances. Those FreeSWITCH instances hold all accounts,
domains and medi
