+++
3) The attribute pass in the Server Entity must be FetchType.Lazy and the
insert/update method in the UI/ServerDao must be so modified that the
Server's Entity password is only changed when explicitly set.
Otherwise we would need to create a ServerDTO and use that everywhere where
a Server
What about the chat, I have seen you made some changes to the chat lately
Maxim? Is the Chat in the dashboard now in the database?
I add chat to the DB for Wicket only (only global chat for now with small
amount of testing)
I had no plans to change it for Flash app
On Mon, Feb 4, 2013 at
ok thx,
I guess we can also let the dashboard chat untouched.
Theoretically there is no need to put it into the database as long as the
clients initially always connect to the same node (as we did plan).
But the chat history in the conference room needs to be put into the db as
it could
I believe it will not work for the cluster (nobody ever think about this)
Unfortunately SIP integration still is not very stable :(
On Mon, Feb 4, 2013 at 10:50 AM, seba.wag...@gmail.com
seba.wag...@gmail.com wrote:
Is the red5sip integration intend to work on cluster? I guess
theoretically
Hi Sebastian,
Regarding the SIP integration: currently outcome calls work as expected for
us and there are still problems with the income calls to the room. It seems
like this does not work because of some Asterisk configuration problem. I
hope it will be resolved in a couple of days.
Best
