Edwin:
Thanks for the table info.  I guess that's what I was saying but not clearly.  
I compiled and installed MediaProxy.  Then it started automatically.  I did a 
"ps ax | grep media-" and it was running.  There was a *.pid and *.sock file in 
/var/run/mediaproxy/ directory.
LOL - but I hadn't configured the config.ini file yet, so the database 
accounting section of the file was still commented out.  
I thought that's why I suspect I don't have the media_sessions table in my 
database - the config.ini file that MediaProxy read on start-up didn't tell it 
to use database accounting, so it didn't connect to my db to create the table.  
I'm still learning!
Again, thanks for the info.
Regards
Gary 

> Date: Fri, 25 Jul 2014 07:23:36 -0700
> From: [email protected]
> To: [email protected]
> Subject: Re: [OpenSIPS-Users] MediaProxy 2.6.1 - manually creating    
> media_sessions table
> 
> Hi Gary,
> 
> If you give your database user CREATE rights the database is greated at
> first start.
> 
> But to answer your question:
> CREATE TABLE IF NOT EXISTS `media_sessions` (
>   `id` int(11) NOT NULL AUTO_INCREMENT,
>   `call_id` varchar(255) COLLATE utf8_unicode_ci NOT NULL,
>   `from_tag` varchar(64) COLLATE utf8_unicode_ci NOT NULL,
>   `to_tag` varchar(64) COLLATE utf8_unicode_ci DEFAULT NULL,
>   `info` mediumblob,
>   PRIMARY KEY (`id`)
> ) ENGINE=MyISAM  DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci
> AUTO_INCREMENT=52 ;
> 
> Cheers,
> 
> Edwin
> 
> 
> 
> --
> View this message in context: 
> http://opensips-open-sip-server.1449251.n2.nabble.com/MediaProxy-2-6-1-manually-creating-media-sessions-table-tp7592620p7592621.html
> Sent from the OpenSIPS - Users mailing list archive at Nabble.com.
> 
> _______________________________________________
> Users mailing list
> [email protected]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
                                          
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to