Hi again everyone,
Changing the DBURL in the kamailio.cfg to what the url is seems to
stop the error from before.
However, now kamailio is failing to start.
The following is the output when kamailio is restarted;
root@opensep:~# service kamailio restart
Restarting Kamailio:
loading modules
Hi Kamailio Community,
I've been configuring the presence module on Kamailio and trying to
get it working, using the following as a guideline;
http://nil.uniza.sk/instant-messaging/simple/configuring-im-and-presence-kamailio-31-howto
From that I assumed that enabling Presence would mean that IM
Hello,
can you paste the module parameters for auth and auth_db module? Or
check the combination of password column and calculate_ha1 are ok.
I guess you are using your custom configuration file, maybe you can give
a quick test with default configuration just to see if the passwords match.
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
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
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
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.
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
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]
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'
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.
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
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
13 matches
Mail list logo
