Hi,
What Bobby state is really true - already had some chat with Ovidiu in
evaluating the differences (on the reply format) and the effort to align
the new xmlrpc-ng module with the old one.
If this will be doable by tomorrow, we will drop mi_xmlrpc module in
1.11. If not, it will be kept
Hello,
The new mi_xmlrpc_ng module have one big probelm - not support integer
value.
To send digit value OpenSips want to use srting.
Example:
When try to change debug level I must ot send debug 1.
workable XML this is :
methodCall
methodNamedebug/methodName
params
param
Hi,
I am doing proxy_authorize for !(method==REGISTER) is_from_local().
I request INVITE is not send from user, which does not contain
local_domain (defined in domains table) in INVITE, so this will not be
authenticated as this request will not go to this !(method==REGISTER)
I'm all for the deprecation as long as the documentation on the mi_xmlrpc_ng
module is updated to a usable level. I find myself referencing the
documentation for xmlrpc and hoping that it holds true for xmlrpc_ng.
___
Users mailing list
2014-03-18 16:29 GMT+01:00 Adrian Pinder jpin...@outlook.com:
Hi,
I installed opensips version 1.8, I can register and make calls ok between
endpoints. I have opensips installed behind a NAT and my user agent are
also behind NAT. i can register and I got rtpproxy working.
I enabled NAT
Hi,
Just upgraded to 1.10.1 and when starting openSIPS getting error as
below in a log file:
ERROR:db_mysql:mysql_raise_event: event not registered -1
Any suggestions what my be the reason for it and how to fix very much
appreciated.
Best regards,
Chris
The whole idea is not to :)
But more tests need to be done.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 19.03.2014 17:39, Ali Pey wrote:
Will this affect OpenSIPS-CP?
Regards,
Ali Pey
On Wed, Mar 19, 2014 at 10:18 AM, Kneeoh
I'd like to see the new module to be a drop in replacement for the old one..
That being said...
I was pretty surprised when I started down the path of the XMLRPC module
that the reply isn't structured. It was just one big object.
I'd like a selectable option on the module so that it either
Please pull from git, give it a try and let us know if everything is
working as expected with your old scripts.
Regards,
Ovidiu Sas
On Tue, Mar 11, 2014 at 9:48 PM, Bobby Smith bobby.sm...@gmail.com wrote:
The one thing we find annoying about deprecating this is that it's not a
drop in
Please let us know what's missing from the mi_xmlrpc_ng doc and it is
present in mi_xmlrpc doc.
Regards,
Ovidiu Sas
On Wed, Mar 19, 2014 at 10:18 AM, Kneeoh kne...@yahoo.com wrote:
I'm all for the deprecation as long as the documentation on the mi_xmlrpc_ng
module is updated to a usable
Hello Brett,
It is true that the structured output mode was not implemented in the
new module.
It seems that having the output in one big chunk is the preferred
method in the community.
If there is a real demand for structured output, we can take a look into it.
Regards,
Ovidiu Sas
On Wed,
I think the only reason for that is backwards compatibility with stuff
written for the other mi interfaces.
Honestly, my parsers for the MI output are ridiculous. It's really
complicated and prone to failure. I'd like to know if others share my
feeling here.
For little things like dr_reload I
Hello Dragomir,
As I pointed to you in a previous e-mail, the integer is not really
supported by opensips.
Even if you send a value as integer, it will still be treated as
string and each module will decide if a conversion is required.
All you need to do is adjust your script to send out string
Based on your reply, my understanding is that you are not currently
using the structured format, but you would like to have it in the
future in JSON format. Am I right?
-ovidiu
On Wed, Mar 19, 2014 at 3:07 PM, Brett Nemeroff br...@nemeroff.com wrote:
I think the only reason for that is
I presently use either the raw fifo, the UDP fifo or the old XMLRPC method.
They all return the same format which has double colon separated nodes.
It's not easy to parse into an object by any language I know.
I've written parsers for it, but I don't like them. It seems like the
structure isn't
I totally share Brett's feelings! For me dlg_list_ctx over the new module
causes lots of headaches when dialogs go over 100 or so. Structured output
would resolve such problems. I am totally in for structured SJON format too!
2014-03-19 21:07 GMT+02:00 Brett Nemeroff br...@nemeroff.com:
I
I think there are some other issues with the size of the return data. I
know for one that the mi_udp method has a buffer size limit. If you hit
this limit I think it very quietly truncates the data. I can't 100% verify
that since it's been a long time since I've used it.
I believe you can
So, you are using the raw format.
The mi_xmlrpc_ng module is using only the raw format.
The structured format in the old mi_xmlrpc module was not implemented
in the new module because it seems that it doesn't have enough
traction in the community (AFAIK).
As for returning JSON, that should be a
The new module is built on top of the httpd module which has a
parameter to define the size of the buffer. If you need large
replies, then you need to adjust the buffer size accordingly.
http://www.opensips.org/html/docs/modules/devel/httpd
That buffer is used by all modules that are sitting on
JSON+http sounds fantastic. It's like.. Starting to sound a like a RESTful
server.
I'm pretty sure others will jump on this. I know I would.
-Brett
On Wed, Mar 19, 2014 at 2:52 PM, Ovidiu Sas o...@voipembedded.com wrote:
The new module is built on top of the httpd module which has a
Hi,
If I have OpenSipS listening say on port 5066 and 50060 and I get a call and
then send it to my carrier the source port will be 5066 and the destination
port will be what ever I set it to. Other than sending the call back to 5060
and then sending it to my carrier is there any way of changing
Check out the listen core parameter:
http://www.opensips.org/Documentation/Script-CoreParameters-1-11#toc59
When opensips starts, it will bind to those sockets.
When you forward a request, you can choose the socket to send through:
http://www.opensips.org/Documentation/Script-CoreVar-1-11#toc44
22 matches
Mail list logo
