Re: [OpenSER-Devel] Too long keys for UTF-8

2008-03-17 Thread henning Westerholt
>> when trying to create openser mysql databases using UTF-8 as mysql >> default encoding, create scripts fails with: >> >> ERROR 1071 (42000) at line 2: Specified key was too long; max key >> length is 1000 bytes >> ERROR: Creating core tables failed! >> >> Can somebody lower some string len

[OpenSER-Devel] Error using imported sl_send_reply

2008-03-17 Thread Francisco Seratti
Im having this error when calling sl_send_reply(), imported this way: sl_send_reply = find_export("sl_send_reply", 2, REQUEST_ROUTE); And, when i call it in this way: sl_send_reply(msg, "200", "OK"); im getting this errors: Mar 17 17:25:41 [20135] ERROR:core:pv_printf: no more space for text [136

[OpenSER-Devel] compatibility between openser, openxcap and postgresql

2008-03-17 Thread Marcelo Rodrigues Leite
Hi all, I am trying to install openxcap with openser 1.2 and postgresql but I haven´t been very much successful. Throughout my researches in the web, it seems that openxcap does not work with any openser version less than 1.3 nor does it work with postgresql (only with mysql). Since I haven´t

[OpenSER-Devel] [ openser-Bugs-1912485 ] permissions: Ignoring default_allow parameter

2008-03-17 Thread SourceForge.net
Bugs item #1912485, was opened at 2008-03-12 08:59 Message generated for change (Comment added) made by hekuper You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1912485&group_id=139143 Please note that this message will contain a full copy of the comment t

Re: [OpenSER-Devel] mediaproxy server NEW FEATURE!!!

2008-03-17 Thread Dan Pascu
On Monday 17 March 2008, Patrick Miccio wrote: > may I ask if you already have a release date :) ? it will be in the next release of openser, but will be available before that in trunk. -- Dan ___ Devel mailing list Devel@lists.openser.org http://lis

Re: [OpenSER-Devel] mediaproxy server NEW FEATURE!!!

2008-03-17 Thread Patrick Miccio
hi, may I ask if you already have a release date :) ? cheers > > Hi, > > > That is the plan. Unfortunately I do not have user agents that do this, so > > I will need to rely on some other people to test it. > > > > That sounds great, for now I modified the mediaproxy.c from > openser-1.1.1-

Re: [OpenSER-Devel] Too long keys for UTF-8

2008-03-17 Thread Peter Lemenkov
2008/3/17, Jan ONDREJ (SAL) <[EMAIL PROTECTED]>: > Hello, > > when trying to create openser mysql databases using UTF-8 as mysql default > encoding, create scripts fails with: > > [EMAIL PROTECTED] openserctl]$ openserdbctl create > MySQL password for root: > INFO: test server charset > INFO

[OpenSER-Devel] Too long keys for UTF-8

2008-03-17 Thread Jan ONDREJ (SAL)
Hello, when trying to create openser mysql databases using UTF-8 as mysql default encoding, create scripts fails with: [EMAIL PROTECTED] openserctl]$ openserdbctl create MySQL password for root: INFO: test server charset INFO: creating database openser ... ERROR 1071 (42000) at line 2: Specifie

Re: [OpenSER-Devel] [Serdev] Possible bug in the tm module in the presence of packet loss/branches

2008-03-17 Thread Jiri Kuthan
At 15:37 12/03/2008, Maxim Sobolev wrote: >Dan Pascu wrote: >> Anyway, examples are many and I'm sure people can even find more practical >> ones. The main reason for all of them being possible, is the fact that a >> CANCEL is no longer really canceling the call under these circumstances, >> and

Re: [OpenSER-Devel] [Serdev] Possible bug in the tm module in the presence of packet loss/branches

2008-03-17 Thread Jan Janak
Dan Pascu wrote: > It makes sense, however I still have reservations that accounting is > handled as one would expect in this case. While all the approach you > details here makes sense from a technical point of view as per RFC > requirements, then end user experience is different. > > Consider