It sounds like the dialog module might be your best bet.
On June 6, 2018 10:40:38 PM EDT, Tim Bowyer wrote:
>Hi All,
>
>Currently trying to work out the best way to keep track of how many
>calls are being sent to any given dispatcher destination.
>I remember being able to do this years ago with
this seems to work for me:
*# info level*
kamcmd cfg.seti core debug 2
# logging off
kamcmd cfg.seti core debug 0
On Mon, Jun 4, 2018 at 4:49 PM, Sergey Safarov wrote:
> Thank you Henning
> That's i looking for!
>
> Sergey
>
> пн, 4 июн. 2018 г. в 22:04, Henning Westerholt :
>
>> Am
Hello,
something like that, maybe the parameter value will be only the name of
the xavp, similar to xavp_cfg for registrar.
For attrs and extra columns, I was thinking of concatenating all of them
in 'attrs' field and have also separate those with a specific meaning
(like socket, weight, ...)
Firebase is way too out there in Google + OAuth + HTTP land. That sort
of interface really should be done through a general-purpose programming
runtime with an HTTP connector.
On Wed, Jun 06, 2018 at 12:17:21PM +0200, Daniel-Constantin Mierla wrote:
> Hello,
>
> no plans in my side for such
Updating the event route to:
event_route[xhttp:request] {
$var(xhttp_uri) = $(hu{s.tolower});
xlog("L_INFO", "event_route[xhttp:request] : hu = '$hu'
var(xhttp_uri) = '$var(xhttp_uri)'");
if ( $var(xhttp_uri) =~ "^/rpc") {
jsonrpc_dispatch();
} else if (
Hi,
I performed the following:
# kamcmd dbg.trace on
# curl --header 'Content-Type: application/json' \
--data-binary '{\
"jsonrpc": "2.0", \
"method": "ul.lookup", \
"params": [ "location","u...@example.com"], \
"id": 3 }' http://registrar.example.com/rpc
# kamcmd dbg.trace off
And the
First compile Kamailio 5.1 binaries and start the services with Kamailio
4.x IMS configuration files. You need to remove few of the deprecated
modules. Then compare the working configuration with 5.X IMS cfg files.
You can use OpenIMS HSS application. Configuration is straight forward.
Calls can
Greetings all.
We are currently developing web and mobile apps using firebase:
https://firebase.google.com/products/realtime-database/ . We have been
discussing the possibility of Kamailio querying this database.
I assume that it will be possible to query it using HTTP and JSON modules,
Hi Daniel
Finally i could implement 3GPP TS 101-671 (HI2Operations) in C
programming with asn1c.
I could use it with Kamailio like Homer.
Daniel is it could be a new module in Kamailio? How can i implement it
as a new module in Kamailio? I want to do it.
Thanks.
Mojtaba
On Mon, Apr 30, 2018 at
Hi Daniel,
love the idea!
just to be sure i understand...,
current params declaration
modparam("dispatcher", "dst_avp", "$avp(ds_dst)")
modparam("dispatcher", "attrs_avp", "$avp(ds_attrs)")
new params declaration
modparam("dispatcher", "dst_xavp", "$xavp(ds_dst)")
##modparam("dispatcher",
Ok Daniel,
thank you very much!
--
Aleksandar Sosic
linkedin.com/in/alexsosic/
mail: alex.sosic@evosip.cloud
On Wed, Jun 6, 2018 at 8:23 AM Daniel-Constantin Mierla
wrote:
>
> Hello,
>
> it was a mistake in matching KDMQ, I just pushed a fix for it in master
> branch.
>
> Cheers,
> Daniel
>
>
>
Hello,
I am starting a discussion here about my plans to do a bit of
refactoring to dispatcher module and gather some feedback if people
think of other improvements.
1) First is about moving from using avps to xavps. It should simplify at
least the config in terms of modparams, but also makes it
Hello,
it was a mistake in matching KDMQ, I just pushed a fix for it in master
branch.
Cheers,
Daniel
On 05.06.18 19:29, Aleksandar Sosic wrote:
> Hi Daniel,
>
> here you go:
>
> 0(578) DEBUG: [core/parser/msg_parser.c:152]: get_hdr_field():
> cseq : <10>
> 0(578) DEBUG:
13 matches
Mail list logo
