David Thomson writes:
> Is it possible to include a public key and digital signature in the
> register events and have kamailio perform the transformation to
> validate the client's identity? If so which module provides such
> functionality? Has something like this been implemented in the past?
Hi,
I am working on a project where a custom sip client will be integrated into a
suite of applications to provide voip. The sip client will be working with
Kamailio. The goal is to ensure that the client is authorized for
communication with kamailio before allowing any calls to be made.
Hi Everyone,
> You don't need to do anything to support MESSAGE requests on Kamailio.
>> Following the guide from the web site, you will enable Presence.
>> However, your problem seems to be with the client software.
>> If I am correct, Blink uses Session mode (MSRP) for I
Hi Andreas,
===
>Check what's in line 392, it should give you a hint what's wrong.
===
That's where it mentions the DBURL. I think I fixed this issue by,
instead of using DBURL, I just use the location (mysql://...).
That allows Kamailio to restart with no issu
On 19.09.2012 16:13, Yufei Tao wrote:
I should have made it clearer: $du is null both before and after lookup
location in LOCATION_BRANCH when no fix_nated_register was done (thus
'received' column in location table was null). When fix_nated_register
was done, $du for each branch was null befor
In LOCATION_BRANCH, after lookup location, I've added: if ($du==$null)
$du=$ru; And now everything works! In summary, either of the following
would fix the problem: 1. call fix_nated_contact for all clients, so
that 'received' column in location table is populated (so that $du will
be set), or 2.
Hi All,
Finally i found the issue,
Here is one of the bad trace for SUBSCRIBE(722bytes) and NOTIFY(1282bytes)
which corrupted the memory. The messages came in the order NOTIFY and
SUBSCRIBE. The core is generated in a different place but I believe this
could be the reason for memory corruption.
I should have made it clearer: $du is null both before and after lookup
location in LOCATION_BRANCH when no fix_nated_register was done (thus
'received' column in location table was null). When fix_nated_register
was done, $du for each branch was null before lookup location, but set
to 'received' a
Hi Daniel,
Thank you very much..
The below script works fine.
I've been a long time struggling with script while the problem was in the
x-lite. After using another phone things went smooth.
Thanks a lot.
Cheers,
F Chahrour
From: Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Hi Gary!
You don't need to do anything to support MESSAGE requests on Kamailio.
Following the guide from the web site, you will enable Presence.
However, your problem seems to be with the client software.
If I am correct, Blink uses Session mode (MSRP) for IM service.
Bria uses Page mode (sip ME
On 19.09.2012 12:24, Yufei Tao wrote:
Hi Klaus
Thanks for the reply!
I check the $du, it is always null before and after the lookup. Is it
only set when relaying to a proxy (from record-route), and not to a client?
That's strange. For NATed clients, $du must contain the 'received' URI.
Oth
On 09/18/2012 04:58 PM, Nathaniel L Keeling III wrote:
> 11(28548) DEBUG: db_postgres [km_dbase.c:393]: PQclear(1008b8560) result
> set
> 11(28548) DEBUG: auth_db [authorize.c:124]: HA1 string calculated:
> e13d569284e76a33ca63e4d6203f844a
> 11(28548) DEBUG: auth [api.c:211]: check_response: Our re
Hi Klaus
Thanks for the reply!
I check the $du, it is always null before and after the lookup. Is it
only set when relaying to a proxy (from record-route), and not to a client?
When no fix_nated_register is called, the lookup location for both
clients y2 and y3 is successful from the log, when p
You can configure msilo module parameters as here (for offline user's
message storing)
http://telephonynetworks.blogspot.com/2012/08/configuracion-de-kamailio-33-con-nat.html
*/*Este modulo es opcional, se utiliza para guardar mensajes en la
base de datos si el usuario esta offline, y se lo envia
On 09/18/2012 12:15 PM, Gary Shergill wrote:
> Note that I am testing this with one computer connected by Bria and
> another computer connected via Blink. I am able to log on to a user on
> each (test1 and test2) and they are able to call each other. The issue
> is, with presence enabled, they are
15 matches
Mail list logo
