Hey Jony,
while during "make deb" it complains of lua files
output
..
In file included from app_lua_api.c:37:
app_lua_api.h:27:17: warning: lua.h: No such file or directory
app_lua_api.h:28:21: warning: lauxlib.h: No such file or directory
app_lua_api.h:29:20: war
El Wed, 6 Oct 2010 04:55:55 -0400
X- x -X escribió:
> Hey Jony,
>
> while during "make deb" it complains of lua files
>
Make sure you have an updated 3.1 branch. There was a fix for this yesterday by
Daniel.
___
SIP Express Router (SER) and Kamail
Hello,
in order to build the packages for 3.1.0 without conflicts, please make
your commits before 14:00CEST (Madrid, Paris, Berlin - UTC+2). If you
still have some to do afterwards, please ask on
sr-...@lists.sip-router.org before committing.
Thanks,
Daniel
--
Daniel-Constantin Mierla
htt
Shouldn't me doing " git pull " today /even now have fixed it ? (it still
not doing it for me though). I still get that error. of not finding those
lua.h etc..
I do see it being upgrade to 3.1 during the compile
...
dpkg-buildpackage: source package kamailio
dpkg-buildpack
Hello Henning.
Yes, I made both things. The only thing is that I have the next configuration:
debug=5
log_stderror=no
memdbg=3
memlog=3
But it worked in the previous version, so it should work now also (or that I
suppose). Really I think that's not the problem, because the debug for the
shared
Guys,
This mail has nothing to do with Kamailio or SR, so feel free to discard it.
I'm trying to find a command-line tool to grab updates from an RSS feed.
I tried to install rsstail but it has a lot of dependencies and cannot
make it work.
Does anyone have some software I can download and use
Kamailio (OpenSER) v3.1.0 is out – major release with impressing
number of new features and improvements.
This release is a result of more than 8 months of development and
testing from the teams of Kamailio (OpenSER) and SIP Express Router
(SER) projects. Backed up by a solid development grou
An important note I should add here:
- starting with this version, there is a single stable branch for both
Kamailio and SER, so when you compile the sources, you must run first:
make FLAVOUR=kamailio cfg
Then:
make all
make install
A step by step tutorial is available at:
http://www.kamai
On Wednesday 06 October 2010, Daniel-Constantin Mierla wrote:
> Kamailio (OpenSER) v3.1.0 is out – major release with impressing
> number of new features and improvements.
Hello Daniel,
thanks a lot. :-) I've uploaded the tarball and the changelog also to
sourceforge.
Cheers,
Henning
__
>> Hi Alex. I use a general context in asterisk to route calls already
>> and wanted to get away from pattern matches. I'm using asterisk
>> realtime and want to decrease the load. I'll play around with the
>> 'uac_replace_from()' and 'append_hf' to see what works best for me.
>
> Well, you don'
On 10/06/2010 12:55 PM, JR Richardson wrote:
So the first thing I notice with using 'uac_replace_from()' is the
caller ID number is replaced with the replaced value, so I guess this
is not what I need for my particular application. I'll fool around
with the 'append_hf' and some pattern matches
hi,
i have been looking for a way to authenticate users based on the IP from
they come from . Also i would like to limit the number of channels (
simultaneous calls) that each user can make . is their any way to do this
using kamailio 3.0 and siremis 1.0 ?
my configuration is like this:
sipphones
Hi!
Shrouk Khan wrote:
> Also i would like to limit the number of channels (simultaneous calls)
> that each user can make .
I think this blog post will help you forward:
http://by-miconda.blogspot.com/2010/01/best-of-new-in-kamailio-300-19-htable.html
There are also other approaches. You ca
On 10/06/2010 11:47 AM, Shrouk Khan wrote:
> hi,
> i have been looking for a way to authenticate users based on the IP from
> they come from .
There are a number of ways you could do this. They way I did it by using
a group named ipauth. If the user is a member of the group, compare the
request IP
I'm working on a setup where we have rtpproxy on a machine with eth0
IP 10.10.5.141/19 and eth1 IP 10.10.10.78/24. When using
force_rtp_proxy("","10.10.5.141"); the connection information (c) field
in the SDP is not being set to the ip 10.10.5.141 It is instead being
set to 10.10.10.78
We
On 10/06/2010 06:41 PM, Stagg Shelton wrote:
I'm working on a setup where we have rtpproxy on a machine with eth0
IP 10.10.5.141/19 and eth1 IP 10.10.10.78/24. When using
force_rtp_proxy("","10.10.5.141"); the connection information (c)
field in the SDP is not being set to the ip 10.10.5.141 I
Thanks Alex.
Early tests after your change seem to indicate that fixed the problem.
I'm looking at the docs with this new perspective, and when we read the
description of the i flag and the e flag it seems to suggest that they
are used independently. Nothing jumped out at us to use them tog
On 10/06/2010 07:06 PM, Stagg Shelton wrote:
Early tests after your change seem to indicate that fixed the problem.
I'm looking at the docs with this new perspective, and when we read
the description of the i flag and the e flag it seems to suggest that
they are used independently. Nothing jumpe
You post reminded me that I should update the examples on the repo
(which I just did).
It is better to use the new rtpproxy_offer/rtpproxy_answer functions.
For a quick example, please check:
http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=blob_plain;f=modules_k/rtpproxy/examples/alg.cf
I assume that means rtpproxy_answer|offer actually work now. :-)
Last time there was a conversation about using them, in fall 2009, we
concluded that they don't work and went back to using force_rtp_proxy().
On 10/06/2010 07:18 PM, Ovidiu Sas wrote:
You post reminded me that I should update
They work ok in my setup. The plan is to remove force_rtp_proxy in 3.2.
Regards,
Ovidiu Sas
On Wed, Oct 6, 2010 at 7:19 PM, Alex Balashov wrote:
> I assume that means rtpproxy_answer|offer actually work now. :-)
>
> Last time there was a conversation about using them, in fall 2009, we
> conclu
On 10/06/2010 07:22 PM, Ovidiu Sas wrote:
They work ok in my setup. The plan is to remove force_rtp_proxy in
3.2.
A wholeheartedly palatable goal -- if they work. :-)
IIRC, the issue we had was with trying to use them with the same
richness and diversity of flags that force_rtp_proxy() has
They are all wrappers around the same embedded function.
Don't know what was the issue that you encounter then, but please try
now and report any issues.
The new rtpproxy module is using now the core sdp parser and it is way
easier to track down any potential issues.
Also, multipart content should
thnkx all , looking in to it. So far it seems like everything is done on the
kamailo.cfg and done manually by hand. Doesnt the siremis/seradmin or any
other kamailio/openser portal has anything to do with these kinds of
configuration ?
On Thu, Oct 7, 2010 at 4:15 AM, Mikko Lehto wrote:
> Hi!
>
On 10/06/2010 10:00 PM, Shrouk Khan wrote:
Doesnt the siremis/seradmin or any other kamailio/openser portal
has anything to do with these kinds of configuration ?
Not really. It's the user's responsibility to tell Kamailio/OpenSER
what they want it to do; you can think of it as an applicati
NEVER use any GUI to configure a server... Never...
On Wednesday 06 October 2010, Shrouk Khan wrote:
> thnkx all , looking in to it. So far it seems like everything is done on
> the kamailo.cfg and done manually by hand. Doesnt the siremis/seradmin or
> any other kamailio/openser portal has any
26 matches
Mail list logo
