you can search red5sip in config :) the key is "red5sip.enable"
On 1 August 2014 23:48, Horace Miles <horace.mi...@myit-solutions.com> wrote: > Maxim thanks for the response. > > I have confirmed everything but I am not sure where to find this setting. > I am assuming Admin config is Openmeeting Admin->Configuration. If so I > don’t a setting for Red5sip key. > > 3) red5sip* key should be enabled in Admin->Config – NOT SURE OF THIS STEP > > > > *From:* Maxim Solodovnik [mailto:solomax...@gmail.com] > *Sent:* Wednesday, July 30, 2014 6:07 AM > *To:* Openmeetings user-list > *Subject:* Re: Pointer on WB > > > > OM is accessible on all network interfaces by default > > config.xml need to be modified only in case you need to restrict OM client. > > > > According to red5sip enter-exit-enter-exit-.... it should be due to > misconfiguration. Unfortunately this integration is not simple by design :( > I'm using logs and debug to set it up properly. > > > > Main steps are > > 1) asterisk should be configured to have access to OM DB > > 2) asterisk bean should be uncommented and configured properly in > openmeetings-application.xml > > 3) red5sip* key should be enabled in Admin->Config > > 4) in case asterisk is integrated with OM user should be re-saved (to have > password-hash being saved in asterisk DB table) > > 5) sip should be enabled in the room > > > > this should be all (hope I haven't miss anything) > > > > On 29 July 2014 08:29, Horace Miles <horace.mi...@myit-solutions.com> > wrote: > > Hi Maxim, > > My box is connected directly to a public IP, no NAT. My understanding > was that Openmeetings to be access from the internet needed to be on a > public address. That address would be the one in the config.xml. If I a > mistaken let me know. > > Can I have your thoughts on the following: > > > > I am unable to get the sip agent to bind to 127.0.0.1. It refuses to bind > unless I have bind it to the same address that is in red5home > /webapps/openmeetings/public/config.xml > > > > The problem appears to be either that the SIP protocol wants to use > 127.0.0.1 for the subscribe or invites and SIP agent is bound to the Public > IP address. Therefore it is generating the error for seqno 2 which would > be the SIP Invite (I am assuming). I have not been able to get the SIP > tansport to bind to 127.0.0.1 which would probably solve this problem. > > > > Your thoughts/ > > > > *From:* Maxim Solodovnik [mailto:solomax...@gmail.com] > *Sent:* Friday, July 25, 2014 7:22 AM > *To:* Horace Miles > *Subject:* Re: VOIP and Sip Integration > > > > hope you will be able to fix it, please let ne know if additional help is > required > > > > On 25 July 2014 20:53, Horace Miles <horace.mi...@myit-solutions.com> > wrote: > > Hey thanks for the files. > > > > I compared and I have found the following: > > > > It appears the integration is setup for for a box that is NAT’ed. I > thought openmeetings had to be on a static public IP address? > > > > So I changed every place that is referencing 127.0.0.1 to my IP address. > > > > The Sip Agent/Openmeetings Manager does not come into the room until I > restart Asterisk. I can see it successfully logging on and then > immediately logging off. The room is successfully spawned. > > > > There seem to be a problem with the manager once it signs on with the sip > handshake (again I am guessing) > > > > chan_sip.c:4164 retrans_pkt: Retransmission timeout reached on > transmission #########@127.0.0.1 for seqno 2 (Critical Response) see…… > Packet timed out afer 32000ms with no response. > > > > I will load wireshark later today on the PBX to see what else I might find. > > > > Thanks for all your help. > > > > > > *From:* Maxim Solodovnik [mailto:solomax...@gmail.com] > *Sent:* Thursday, July 24, 2014 2:42 AM > *To:* Openmeetings user-list > *Subject:* Re: Pointer on WB > > > > Only with code modification > > On Jul 24, 2014 4:40 PM, "Raju M K" <mkraju...@gmail.com> wrote: > > Dear all, > > can i disable arrow pointer for all participants in restricted room on > Whiteboard?? > > > -- > Regards, > M K Raju. > > > > > > -- > WBR > Maxim aka solomax > -- WBR Maxim aka solomax
