Hi everyone
At my workplace there's plenty of hardphone directly connected to an hosted sbc
in the cloud.
As an added value i proposed to add locally Kamailio as a proxy server to
'federate' all the sip traffic.
ipphone behind nat (A) <---> sip proxy local 192.168.x.x (B)<> sbc
registrar (m
Hello everyone,
I'm trying to use BLF with the config here (except with SQlite):
http://kb.asipto.com/kamailio:presence:k43-blf
BLF seems to work perfectly except after the call is ended I get
"sqlite commit failed: database is locked" error messages as seen
here:
http://pastebin.com/xVijj9
Hi everyone
At my workplace there's plenty of hardphone directly connected to an hosted sbc
in the cloud.
As an added value i proposed to add locally Kamailio as a proxy server to
'federate' all the sip traffic.
ipphone behind nat (A) <---> sip proxy local 192.168.x.x (B)<> sbc
registrar (
Hello,
Is it possible to use kamailio to be a stateful outbound proxy ?
The use case is kamailio is an outbound proxy for multiple instances of
Asterisk.
Thus all responses need to go back to the same instance of Asterisk that
generated them.
After the call is established.
How can I ensure tha
Jignesh,
Everything you're asking for is part of Kamailio's core functionality:
1. Most useful applications of Kamailio involve stateful relay, and the
stock included configurations are stateful.
2. The loose-routing section of the configuration, and, more broadly,
RFC 3261 in general, take
Hi,
The destination node is down. By adding the following code Kamailo re-routing
INVITE to a new destination after getting 408 timeout (as below).
failure_route[MANAGE_FAILURE]{ if (t_branch_timeout()) { # change to
new destination IP $rd = "10.10.10.10"; t_relay(); exi
On 28/03/16 22:56, Daniel-Constantin Mierla wrote:
> Hello,
>
> no much spare time (which I guess everyone lacks of, anyhow), but
> ultimately I could assist a bit someone that is going to work with C
> (eventually C++) and/or WebRTC -- not doing much of the Java these days,
> I will let that fo
Hi.
It probably also should be noted, that the current implementation works
with a lot of different client implementations (we use Python for Nagios
and PHP for Management (both built-in XML-RPC as well as ZendFramework's
XML-RPC client)), so it cannot be that wrong.
Just my $0,02,
Carsten
2016-
Hello;
You are right. I found rpc_add function. we can add whatever
we want to response xml.
Cheers
29.03.2016 11:10 tarihinde
Daniel-Constantin Mierla-6 [via SIP Router] yazdı:
H
Hello,
I haven't originally implemented the rpc interface in Kamailio (which we
inherited via SER merge in 2008), but I expect to be some reason for
this behaviour, give the code is like 10 years old by now. A fault code
is a fault code, and if there was successful execution, then there was
no fau
Hello Daniel;
there is only rpc_send method in rpc module that dont have
any code and other parameters. it sends empty xml text. if it has
parameters like fault function , i think it will be useful.
Cheers.
Hello,
is this correct if there was no error? The fault node should be in case
of errors, not success. You should check the xmlrpc specs to be sure any
chance is conform with the requirements there.
Cheers,
Daniel
On 29/03/16 09:26, ycaner wrote:
> hello;
> i checked the rpc command and yes , yo
hello;
i checked the rpc command and yes , you are right there isnt . i will add a
rpc return code. it will look like if my pr is accepted.
faultCode
200
Hi guys!
We have an issue with XML-RPC module.
>From this doc: http://kamailio.org/docs/modules/4.3.x/modules/xmlrpc.html
"Success replies always contain at least one return value. In our case the
simplest success replies contain single boolean with value 1"
We are trying to reload domain module
Hello,
refreshing about the major release 4.4.0 planned for tomorrow -- if any
dev has patches to backport to branch 4.4 should do it as soon as possible.
Cheers,
Daniel
On 18/03/16 12:16, Daniel-Constantin Mierla wrote:
> Hello,
>
> with no major issues reported lately, I think we are on a good
15 matches
Mail list logo
