Hello,
short note to remind about the release of v3.3.1 later today. Apply your
commits to branch 3.3 before 12:00 GMT.
Cheers,
Daniel
On 7/31/12 8:40 AM, Daniel-Constantin Mierla wrote:
Hello,
I am planning to package v3.3.1 out of the latest branch 3.3 this
Thursday, August 2. If you are
TLSV1_method is not used inside db_postgres, so it is a dependency of pg
library. Do you have the tool pg_config installed in your system?
Cheers,
Daniel
On 8/2/12 2:33 AM, Akan wrote:
I had to upgrade to the lastest version of Postgres to get past this
error but then ran into the problem of
Alex,
uac_redirect doesn't work for me. Please see the below link
http://blog.gmane.org/gmane.comp.voip.ser/month=20050201/page=10
In the above link, check the email from "Jan Janak" on Feb 3rd, with the
"call flow". I exactly require the same. Do we have some handling for this?
Regards,
Ananth
You'll have to be more specific about why it "doesn't work".
Also, keep in mind that 'uac_redirect' is just a convenience. If it's
not doing what you want, just build a failure_route[], capture the 302
yourself, extract the Contact header yourself, parse the data yourself,
and manually fork t
[root@new db_postgres]# make Q=0
config.mak included
config.mak included
gcc -fPIC -DPIC -g -O9 -funroll-loops -Wcast-align -m64
-minline-all-stringops -falign-loops -ftree-vectorize -mtune=opteron
-Wall-DNAME='"kamailio"' -DVERSION='"3.3.0"' -DARCH='"x86_64"'
-DOS='linux_' -DOS_QUOTED='"li
Daniel,
I remove RPM-s
postgresql
postgresql-devel
postgresql-libs
kamailio-postgres
install
postgresql84
postgresql84-devel
postgresql84-libs
and assemble
db_postgres using
make Q=0
in db_postgres directory.
then put
db_postgres.so to /usr/lib64/kamailio/modules directory.
Currently I's
Thanks Alex. Failure_route should suffice.
On Thu, Aug 2, 2012 at 2:39 PM, Alex Balashov wrote:
> You'll have to be more specific about why it "doesn't work".
>
> Also, keep in mind that 'uac_redirect' is just a convenience. If it's not
> doing what you want, just build a failure_route[], captur
Hello,
What I am trying to work out is whether Kamailio now supports enough of
Outbound and GRUU that the contact aliasing I am using with WebSockets
is no longer necessary?
Also, is the current support complete enough that there are no issues
around WebSocket connections being broken and the cli
2012/7/30 Daniel-Constantin Mierla :
> There is one situation that will not work even with gruu/ob -- in sip a
> phone can call without registering. A gruu contact is obtained via
> registration and then used for next requests by UA itself. By calling
> without registering, there is no gruu contact
2012/7/31 José Luis Millán :
> Outbound provides the UAC a way to update a binding even if it reboots. For
> that, a unique and permanent value of instance-id is used, which in
> conjunction with the AoR and reg-id determines the binding to the UAC.
>
> Having said this, I guess that the CSeq compa
2012/8/2 Peter Dunkley
> I believe for WebSockets the situation is exactly the same as you would
> have for a client connecting over TCP from behind a NAT.
It should be exactly the same situation.
--
Iñaki Baz Castillo
___
SIP Express Router (SER)
Hello,
Kamailio SIP Server v3.3.1 stable release is out.
This is a maintenance release of the latest stable branch, 3.3, that
includes fixes since release of v3.3.0. There is no change to database
schema or configuration language structure that you have to do on
installations of v3.3.0. Deplo
Hello! I'm new to this list and Kamailio.
First, thanks to all the programmers that developed this software.
I'd like to ask several questions on how to get started with Kamailio
and the basic understanding of it. I'm trying to figure out Kamailio
only since yesterday. Right now I have a singl
Hi Markus!
On 08/02/2012 12:40 PM, Markus wrote:
Hello! I'm new to this list and Kamailio.
Welcome!
- Give only a single IP address to all customers and termination
providers (the same IP address), 195.5.5.5.
That would be difficult, unless you really have your anycast ducks in a
row. A
** **
*
*
** **
Hi,
** **
I have a question regarding the below ACK response Kamilaio receives from a
carrier. Can someone please help me understand why the “*Route:
sip:callmanager@192.168.160.43:5060> *sent from Kamailio is missing a “<”
as shown in the captures below? Our Internal proxy is
> ** **
>
> *
> *
>
> ** **
>
> Hi,
>
> ** **
>
> I have a question regarding the below ACK response Kamilaio receives from
> a carrier. Can someone please help me understand why the “*Route:
> sip:callmanager@192.168.160.43:5060> *sent from Kamailio is missing a “<”
> as shown in the captures bel
Yes but it was for an older version that was uninstalled. I changed the
path to pull in the current version and still received the same error. I
checked the version for openssl and the same thing was happening. I
changed the path again and recompiled kamailio and still no change. I
noticed when
Somwhere losted since openser 1.0 :)
Please fix in:
start() {
echo -n $"Starting $prog: "
.
[ $RETVAL = 0 ] && touch something
to
[ $RETVAL = 0 ] && touch someting && success
I mean call function
success
in the end of the expression.
Thanks in advance
___
Somwhere losted since openser 1.0
file kamailio.init
Please fix in function start:
start() {
echo -n $"Starting $prog: "
.
[ $RETVAL = 0 ] && touch something
to
[ $RETVAL = 0 ] && touch someting && success
I mean call function
success
in the end of the expression.
Thanks in a
19 matches
Mail list logo
