22 Jun
2005
22 Jun
'05
4:27 p.m.
Hi,
as you will have one conferencing mixer only and probably not do
cascaded mixing, the simplest method is to use a dedicated SER instance
that is only frontend to the conference mixer and forwards every request
directly to one single sems instance.
If someone calls into a conference number you simply relay the call to
this SER.
Dynamic load balancing for conference mixers are of course a different case.
Stefan
Andreas Granig wrote:
Hi all,
I gave the SEMS-conference module a try and it looks quite promising.
But one thing comes in my mind:
We've multiple SERs balanced via DNS-SRV, so a call to a conference room
can end up in any of the SEMS instances where SER is running, which
results in different conference rooms for one single number.
To solve this issue, the communication between SER and SEMS has to be
made networking enabled (assuming a simple case where one SEMS-server
serves many SERs; for multiple SEMS-Instances maybe a common DB or a
dispatcher has to be used to find the correct SEMS-Server).
Some possibilites come in my mind:
1. Adding a t_write_udp/tcp() function to SER's tm-module and add a
UDP/TCP-Listener to SEMS.
2. Enhance the new xmlrpc-module of SER to allow sending XMLRPC-requests
from inside the SER-config and add an XMLRPC-server to SEMS.
Is there already anybody working on this? Or any comments on the
approaches?
Andy
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers