Re: [SR-Users] Doing a quick test with http_async_client module from master branch

Hi Daniel, I tested the latest master branch with different scenarios: successful replies with/without suspending the transaction, error cases (connection refused) and timeouts. Look fine for now, I will try to setup some longer tests to check on the long run. Thank you :) Cheers, Federico On

Re: [SR-Users] Forwarding Registration to Asterisk

On 12/6/17 6:48 PM, Wilkins, Steve wrote: Hello Matt, I have attempted an outbound_proxy, but when I do this I get the following response from Asterisk - [Dec 6 23:42:51] VERBOSE[14500][C-0001] pbx.c: Executing [20001@from-internal:5] Dial("PJSIP/kamailio-", "PJSIP/20001,30,t")

Re: [SR-Users] Forwarding Registration to Asterisk

Hello Matt, I have attempted an outbound_proxy, but when I do this I get the following response from Asterisk - [Dec 6 23:42:51] VERBOSE[14500][C-0001] pbx.c: Executing [20001@from-internal:5] Dial("PJSIP/kamailio-", "PJSIP/20001,30,t") in new stack [Dec 6 23:42:51]

Re: [SR-Users] Forwarding Registration to Asterisk

Matt, On Wed, Dec 06, 2017 at 04:10:21PM -0600, Matthew Jordan wrote: > 1. Proxy REGISTER requests through to Asterisk, allowing Asterisk to > (believe) it is the Registrar > > In this particular case, you'll need a PJSIP endpoint for each SIP endpoint > that is registering. Identification will

Re: [SR-Users] Forwarding Registration to Asterisk

Hello, I saw next emails but prefer answer directly here. Comments inline. Regards, Ivo On 12/06/2017 08:33 PM, Wilkins, Steve wrote: Hello All, *Problem*: My main issue is that when I “REGISTER” a client via Kamailio, and I attempt to “Dial” a different endpoint within an Asterisk Dial

Re: [SR-Users] Forwarding Registration to Asterisk

On Wed, Dec 6, 2017 at 2:16 PM, Wilkins, Steve wrote: > Hello and thank you for the reply. > > I did try something like this before with no luck => Dial(PJSIP/ > 20001@129.4.1.32) where 129.4.1.32 is the IP Address of Kamailio. > When I attempt this, I get the error =>

Re: [SR-Users] IMS with online Charging system

I am pretty sure that CGRates team was made some development related to diameter charging interface. On 12/06/2017 07:37 PM, Amar Tinawi wrote: Hello all Is there any open souce ocs can be integrated with kamailio IMS ? Is it possible to integrate with CGrates ?

Re: [SR-Users] Forwarding Registration to Asterisk

You could also just use the Kamailio address in your Dial command... Dial(SIP/user@kamailio) This will be beneficial if you will be running multiple asterisk servers using a base registered on Kamailio. Of course, there's many ways to go about this... --fred

[SR-Users] Forwarding Registration to Asterisk

Hello All, Problem: My main issue is that when I "REGISTER" a client via Kamailio, and I attempt to "Dial" a different endpoint within an Asterisk Dial Plan, Asterisk throws an error stating that the endpoint (the number I am dialing via "Dial") is not registered or reachable. However,

[SR-Users] IMS with online Charging system

Hello all Is there any open souce ocs can be integrated with kamailio IMS ? Is it possible to integrate with CGrates ? ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Need useful graphics ideas

Hi Joel, Hi List, Thanks for the nice ideas. We already use go-lang telegraf for collecting data. I saw an push to influx version of this "another sipserver" config. But if there is no influx the start of the server breaks. The pull or statsd method are both nice. I use webrtc on my frontend

Re: [SR-Users] Need useful graphics ideas

I use a mix of the above... With kamailio I export that stats I want via http: event_route[xhttp:request] { # Verify request come from localhost if(src_ip!=127.0.0.1) { xhttp_reply("403", "Forbidden", "text/html", "Forbidden"); xlog("L_WARN", "[HTTP] Unauthorized access

Re: [SR-Users] t_set_fr behaviour

thanks daniel might be good to add to documentation Kelvin Chua On Mon, Nov 13, 2017 at 4:32 PM, Daniel-Constantin Mierla wrote: > Hello, > > > On 11.11.17 07:04, Kelvin Chua wrote: > > hi guys, > > > > has anyone of you tried playing around with a scenario similar to

[SR-Users] load testing ims_charging

i am trying to load test the ims_charging module and notice some issues whenever i send test calls one by one, it's perfect. but when i use sipp and generate a bunch of calls, i would get this intermittently CRITICAL: ims_charging [ro_timer.c:122]: insert_ro_timer(): Trying to insert a bogus ro

Re: [SR-Users] Doing a quick test with http_async_client module from master branch

I'll do some test tonight and report. Cheers, Federico On 6 Dec 2017 10:25 am, "Daniel-Constantin Mierla" wrote: > Hello, > > anyone around here that can do a quick test with http_async_module? I > don't have a testbed for it right now and I would spend the time on > other

Re: [SR-Users] Need useful graphics ideas

Hi, You can trigger kamctl and collect necessary data and then push this data to grafana. Check this script which collects data for zabbix, but logic should be same: https://gist.github.com/crashdump/7751564 With kind regards, Jurijs On Wed, Dec 6, 2017 at 10:29 AM, Loic Chabert

Re: [SR-Users] Need useful graphics ideas

Hi, If you are aware about golang, you should probably wrote a telegraf input plugin for kamailio. Installed on kamalio's Host, telegraf will export metric to influxdb. Then you can graph it with grafana :) Regards. Le 6 déc. 2017 08:54, "Karsten Horsmann" a écrit : >

Re: [SR-Users] redis via haproxy

There is no problems without haproxy. And haproxy no problems without kamailio :) I used tcpdump (can't attach here) to dump port 6380, so kamailio should connect to haproxy, because it send ping and receive pong. 2017-12-06 11:06 GMT+03:00 Юрий Горличенко : > Hi try

Re: [SR-Users] redis via haproxy

Hi try first to use single redis for make sure that it is not a ha proxy trouble. If error still exists - try to collect debug information. >Среда, 6 декабря 2017, 10:53 +03:00 от Aidar Kamalov >: > >Hello, > >Kamailio after restart(or start) sometimes can't connect