One other question. Do I need to run record_route() after I run
record_route_preset(string1, string2)? I tried this and the Record-Route
doesn't show presets I defined.
On Fri, Feb 10, 2017 at 9:25 AM, Andy Chen wrote:
> So the ingress is actually TLS -> our VIP address and I see that as the
>
Daniel-Constantin Mierla writes:
> They were reported in the past, iirc, but apparently only by a specific
> version of compiler, or maybe some specific flags to gcc.
...
> Are you running special gcc or with other flags than the default?
The warnings appear on amd64 architecture (I don't have i3
So the ingress is actually TLS -> our VIP address and I see that as the
second record.
The first record shows the physical interface of the system with no
transport value so it's always defaulting to UDP. I need to set this
particular header to use transport=tcp so subsequent UPDATE messages from
What is the actual goal? If one of the RRs is generated by an ingress
out of a TCP listener, it should already have ;transport=TCP in it.
On Fri, Feb 10, 2017 at 08:53:56AM -0800, Andy Chen wrote:
> Hi all,
>
> I need some advise on how to use the record_route() function. So I make
> that call
Hi all,
I need some advise on how to use the record_route() function. So I make
that call when the first method comes in and there are two Record-Route
headers created. However, one of of the headers I want to add
transport=tcp. What is the best way to do this?
I've tried adding that string pe
Hello,
short note for the people that might be interested on the topic -
Allison Smith (aka, the voice of Asterisk) will be on VoIP Users
Conference later today, in about 2 hours, among the topics of discussion
being the Kamailio World 2017. I will also join, trying to squeeze some
updates about u
OK.
From the code, I noticed that the old API (before kemi), it exports a
getHeader(...) method to Python API.
Just for sake of completion - starting with 5.0, there are more methods
available, including a method to retrieve the value of any kamailio cfg
variable, like in:
-
https://github.com
I tested passing the parameter as suggested by Konstantin and it works fine:
In kamailio.cfg :
/python_exec("SendPushNotification", $_s($tU@$td!!$fU@$fd!!$ci));
/
In our python script:
/ def SendPushNotification(self, msg, parameters):
requestUri = ""
fromUri = ""
cal
Hello,
we are using 4.4.2.
Giovanni
--
View this message in context:
http://sip-router.1086192.n5.nabble.com/python-exec-and-parameters-tp155803p155913.html
Sent from the Users mailing list archive at Nabble.com.
___
SIP Express Router (SER) and
Hello,
what version of kamailio are you using?
Cheers,
Daniel
On 10/02/2017 07:55, gmele wrote:
> Hello,
>
> thx for the info. We will check if we wait for an enhanced version of
> python_exec or pass the parameters in a string.
>
> Regards
>
>
> Giovanni
>
>
>
> --
> View this message in conte
Hello,
here you can find both video and slides of my presentation at FOSDEM 2017,
Bruxelles:
https://fosdem.org/2017/schedule/event/freeswitch/
Enjoy!
--
Sincerely,
Giovanni Maruzzelli
OpenTelecom.IT
Cell : +39-347-2665618
___
SIP Express Router
On 09/02/2017 16:47, Konstantin M. wrote:
> That's correct, it accepts only one parameter for now.
> After many years our company has switched to kamailio, I'm actively
> working on new version of app_python, more flexible and usable than
> current one, many new features...
> I'm not ready to pus
They were reported in the past, iirc, but apparently only by a specific
version of compiler, or maybe some specific flags to gcc.
On kamailio.org, which is a 32b jessie, the results of 'make' are clean:
...
CC (gcc) [kamailio]core/rand/isaac/rand.o
CC (gcc) [kamailio]core/cfg/cfg
I don't see in your config that you send back the 401 response. In the
msrp readme example, that part is like:
# frame for local server - send Use-Path
# -- passwd can be loaded from DB based on $au
$var(passwd) = "xyz123";
if(!pv_www_authenticate("myrealm", "$var(p
14 matches
Mail list logo
