Hi Ariel.
The problem with Your routing logic is that You don't route in-dialog messages.
Basically, Your request_route should look something like this:
request_route {
# per request initial checks
route(REQINIT);
# CANCEL processing
if (is_method("CANCEL"))
{
if (t_check_trans())
t_relay(
Hi.
It is not true a and you are just not using modules responsible for
authentication (if you are using the default configuration).
However, those modules are preconfigured as well as the routing logic.
All you have to do is set up a database (if you want persistent (not ram) data
storage for u
Hi.
I have been looking into LDAP way of authenticating users.
Reading this guide
http://www.kamailio.org/dokuwiki/doku.php/tutorials:kamailio31-auth-ldap
and reading the AUTH and LDAP module documentations, it seems to me that
currently you can bind to LDAP (using some service account for exa
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
The ACK was indeed broken. The problem was at the SBC, where I did not expect
it.
Everything works as it should.
Thank you very much for your help.
Martin
__
Od: "Klaus Darilion"
Komu:
Dátum: 28.08.2012 09:36
Predmet: Re: [SR-Users]
The Route and Record-route headers are identical.
From debug (when alias=domain.ch:5060):
authentication of INVITE:
Aug 24 14:22:44 server /usr/sbin/kamailio[8588]: NOTICE: :
-- In route(AUTH), just before
from_uri==myself --
Aug 24 14:22:44 serve
Ok, so .. I have a session border controller device that is a contact point for
my SIP domain (SRV record in DNS set to its IP). All the trafic goes through it
and it does things like topology hiding etc.. The device forwards the INVITE
messages to Kamailio, because of the routing.
The loose
Hello to everybody.
I am currently working with Kamailio 3.3.1 on RedHat.
The "loose_route" function was not working correctly and I observed some very
strange behaviour (not as one described in the documentation of the function).
I have found that there needs to be a port included in the "alias"
