Alexei, what exectly doesn't work? I got this message many times, but there
were no problems with it. Insecure option was not changed by me.
2013/7/11 Alexei Fedotov
> I've noticed someone (Artyom?) changed
>
> /etc/asterisk/sip.conf.bak:;insecure=invite
> to
> /etc/asterisk/sip.conf:insecure=v
I've noticed someone (Artyom?) changed
/etc/asterisk/sip.conf.bak:;insecure=invite
to
/etc/asterisk/sip.conf:insecure=very
on our production server. We get the following problem in the log:
[Jul 7 22:34:29] WARNING[29149] chan_sip.c: Unknown insecure mode
'very' on line 1173
--
With best reg
I get the following error in the log. Does anyone know what happens?
[Jul 11 19:39:50] WARNING[15754][C-0060] res_odbc.c: SQL Execute
returned an error -1: 42S22: [MySQL][ODBC 3.51
Driver][mysqld-5.1.41-3ubuntu12.10]Unknown column 'insecure' in 'where
clause' (96)
[Jul 11 19:39:50] WARNING[157
I have updated fields in java class
Unfortunately OpenJPA creates these 2 columns as
| port | int(11) | NO | | NULL||
| type | varchar(6) | NO | | NULL||
it seems there is nothing I can do with this
On Mon, M
I'm not sure enum is supported by multiple databases
I can check port (should investigate how to support smallint)
On Mon, Mar 4, 2013 at 7:24 PM, Vieri wrote:
> Hi,
>
> my conf:
> `port` mediumint(8) unsigned NOT NULL DEFAULT '0',
>
> OM default:
> port is varchar(5)
>
> Since port is alw
Hi,
my conf:
`port` mediumint(8) unsigned NOT NULL DEFAULT '0',
OM default:
port is varchar(5)
Since port is always a number, wouldn't it be better if it were defined as an
int instead of a varchar? Does OM need it declared as text sonehow?
My conf:
`type` enum('user','peer','friend') NOT NU
you can add columns you need to this table (I did it with no issues)
We have all required columns in our table
I'm not sure having 2 tables is possible (you better try it)
On Mon, Mar 4, 2013 at 5:50 PM, Vieri wrote:
> Hi,
>
> OM uses a limited set of fields for the "sipusers". I'm wondering if
Hi,
OM uses a limited set of fields for the "sipusers". I'm wondering if it's any
problem adding as many fields as possible even if OM doesn't use them?
I'd like to co-populate the sipusers table with my own values, not just OM's.
Ideally, I wish Asterisk RT could allow specifying more than 1 si
Understood. Thanks!
--- On Thu, 2/28/13, Maxim Solodovnik wrote:
> Additionally DB table is created
> after first OM start, and can be
> created/dropped on install/uninstall
> this way red5sip_user is immutable to such changes
>
>
> On Fri, Mar 1, 2013 at 1:12 AM, Maxim Solodovnik wrote:
>
>
Additionally DB table is created after first OM start, and can be
created/dropped on install/uninstall
this way red5sip_user is immutable to such changes
On Fri, Mar 1, 2013 at 1:12 AM, Maxim Solodovnik wrote:
> It is easier to make changes to this user while debugging :)
> I saw no issues havin
It is easier to make changes to this user while debugging :)
I saw no issues having OM users in DB and red5sip_user in config.
On Fri, Mar 1, 2013 at 1:05 AM, Vieri wrote:
> Hi,
>
> According to the OM documentation:
> - Add user for the "SIP Transport":
> [red5sip_user]
> - edit /etc/asterisk/
Hi,
According to the OM documentation:
- Add user for the "SIP Transport":
[red5sip_user]
- edit /etc/asterisk/extconfig.conf:
sippeers => odbc,asterisk,sipusers
Maybe I'm mistaken but if you use Asterisk Realtime for sip peers and users
then maybe the more natural way of adding "red5sip_user" i
fixed,
thanks Timur!
On Thu, Feb 28, 2013 at 10:32 PM, Тимур Тлеукенов wrote:
> This step in Asterisk configuration instruction is not needed:
> "Ensure dahdi was installed successfully:
> modprobe dahdi"
>
> DAHDI is unused in new setup.
>
> 2013/2/28 Maxim Solodovnik
>
> > Hello All,
> >
> >
This step in Asterisk configuration instruction is not needed:
"Ensure dahdi was installed successfully:
modprobe dahdi"
DAHDI is unused in new setup.
2013/2/28 Maxim Solodovnik
> Hello All,
>
> I would like to announce major changes in SIP in upcoming 2.1 release
>
>1. Confbridge is used i
-
From: Maxim Solodovnik [mailto:solomax...@gmail.com]
Sent: Thursday, February 28, 2013 9:02 AM
To: Openmeetings user-list; dev
Subject: [ANNOUNCE] SIP in Openmeetings is changed
Hello All,
I would like to announce major changes in SIP in upcoming 2.1 release
1. Confbridge is used
Hello All,
I would like to announce major changes in SIP in upcoming 2.1 release
1. Confbridge is used instead of MeetMe.
2. OM video codec is changed to be H264
3. Calls to OM rooms will not start until there is no OM users in the
room, and will automatically ends as soon as last use
16 matches
Mail list logo
