Hello all,
Just wondering if anyone know any tutorial on setting up HA+DRBD solution for kamailio.
Especially creating partitions, DRBD devices and mount points.
Thanks in advance,
-Sid
"May the light be with you." ______________________________________________
Siddhardha Garige
www.luminepixels.com
Hi,
I'm using 'allow_trusted()' from Permissions module without a problem in a
Kamailio 4.0 routing logic. It does just work, but the MI command
'trusted_dump' tells me that the module is not in use:
'''
server:/home/jmillan# kamctl fifo trusted_dump
500 Trusted-module not in use
'''
Doing a 'trusted_reload' does neither make any query to database to
retrieve the data.
Other MI commands of same module do work correctly. ie: 'address_reload' or
'address_dump'
Note: I have tested in a Kamailio 1.5 and the result is the same.
Regards.
--
José Luis Millán
Using Kamailio 4.2-dev and MSILO, is it possible to "toggle" the auto-
notification reply MESSAGE using something similar to the following where
"$var(msilo_reply)" is emtpy at startup (or are there suggestions for a better
method):
modparam("msilo", "from_address", "$var(msilo_reply)")
...
if(CONDITION WHERE I WANT THE AUTO-REPLY RETURNS POSITIVE) {
$var(msilo_reply)="$rU(a)example.net";
}
m_store($rU)
...
My use case is that I would like the auto-notification reply to occur in some
instances, but not others. I also do not want to create a loop where the
auto-notification replies are also stored. I was originally using a simple
test: if(src_ip!=myself), but I have begun to use the IMC module as well as
the EXEC module and these MESSAGEs appear to originate from "myself."
Looking at the MSILO documentation I see there is "extra_hdrs(string)," but
this appears to be designed to add headers to dumped MESSAGEs. I was hoping
there would be a way to add a custom header to the auto-notification, on which
I could filter/drop generated replies earlier in the route, but it doesn't
appear that this exists.
My preference for the best-case scenario would be to control the generation of
the auto-notification reply in the first place rather than having to add a
control to detect the reply and drop it.
Thanks in advance for any recommendations.
--
Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E
Dear Kamailio'ns,
I am working on kamailio Server (V 4.0) installed on Ubuntu 12.04 system.
Currently i am trying file transfer feature using IMSDroid SIP clients.
file transferring is fine between two IMSDroid clients but at the
receiving end (file recipient) i cont see the sender identity/ sender name.
it is just displaying as 'null' (Screen shot is attached). But the full
file is transferring to destination address without any problem.
I have configured MSRP module related script in my kamailio configuration
file (find the attachment). but i guess it is not invoking anyway when file
transferring and the file transferring is negotiating client-to-client
basis.
And also find Sip capture of file transfer (ngrep based) for better
understanding.
What could be the problem? Why at the file recipient side it is not
displaying sender's identity (instead it is 'null')? how can i resolve
this issue?
Anyone please help me in resolving this issue.
Any help will greatly appreciate.
Regards,
Ravi.
Hi all,
I'm having some issues treating requests within dialogs with gruu enabled
with kamailio 4.1.2.
I've got the "standard" configuration of WITHIN route with the adition of
the next lines:
if(is_gruu()){
route(LOCATION);
};
before the the RELAY route call in the loose_route section.
The "problem" is that the ACK with a pub-gruu on the Req-URI is not
properly lookup. In the logs I can see the following statements:
2(4232) DEBUG: registrar [lookup.c:123]: lookup(): looking up pub gruu
[urn:uuid:d63b1c4f-d7dc-4f4e-87f1-948123266dc0]
2(4232) DEBUG: registrar [lookup.c:158]: lookup(): 'sam(a)A.B.C.D' Not found
in usrloc
Where A.B.C.D is the local IP of the UA.
Looking at the code, this last line looks like is looking for the
"standard" URI (username@domain) instead of using the pub gruu. Am I right
with this assumption or am I missing something from the code?
As far as I could look, it looks like there's an exit -1 statement in the
line 158 of lookup.c which disables the following gruu treatment.
Since the username with IP is not registered, this ACK is lost and the
sesion is not stablished (lost ACK).
Can anyone provide some hints why is this failing?
Thanks a lot in advance!
Samuel.
Hi
I am using a siremis and *kamailio * hosted server with lylix.net and they
give a link for getting a support about Siremis.
I need a support to how to make OUT call on PSTN with registered subscriber
on Softphone. Currently we have registered user on subscriber table with
their location and can make a PEER to PEER audio call and text messaging
also.
To make OUT call on PSTN we had create a LCR gateway and LCR rule with
Prefix but still can not make a OUT call getting a error 404 can u please
help me out to make a PSTN call
Waiting for your reply
Thanks
Gaurav Rai
+919716238804
Hi All
In 4.2.0 Kamailio (S-CSCF), when I try to register an IMS endpoint, I get
403 from P-CSCSF.
When I checked the error logs, SCSCF logs look as below
1(5455) INFO: ims_auth [authorize.c:824]: authenticate(): uri=sip:
group4-imslab11.in nonce=b9eec0ad9d6d186408541d8a23a7c7a5
response=df89adebbf28f25d38d2f993f7cde033 qop= nc= cnonce= hbody=
1(5455) INFO: ims_auth [authorize.c:872]: authenticate(): UE said:
df89adebbf28f25d38d2f993f7cde033 and we expect
df89adebbf28f25d38d2f993f7cde033 ha1 599fb074cf189867eed06f3b6ebc0b97
(REGISTER)
1(5455) INFO: ims_registrar_scscf [cxdx_sar.c:79]: create_return_code():
created AVP successfully : [saa_return_code] - [-2]
12(5466) INFO: ims_registrar_scscf [cxdx_avp.c:138]: cxdx_get_avp():
cxdx_get_experimental_result_code: Failed finding avp
12(5466) INFO: ims_registrar_scscf [cxdx_avp.c:138]: cxdx_get_avp():
cxdx_get_charging_info: Failed finding avp
I have added an user necs_0 in hss_db, so why I get below error.
Please let me know what is missed here.
Is S-CSCF not able to contact HSS ??
Best Regards
kamal
Hi list
I don't understand prepaid logic calculation, because when my credit is 0
or lees than cost per second, the call is established equal
$var(i_pulse) and $var(f_pulse) how this works????
Hi,
Im trying to connect my WebRTC clietn
to kamailio via WSS. I successfully connected it via WS but having
trouble connecting it via WSS. My first issue is I get error messages
while i try to compile TLS module(console log in the end of the
document). But, still it creates tls.so file. So i copied the tls.so
to my kamailio modules directory and then updated my kamailio
configuration as below:
#!define WITH_TLS
.
.listen=tcp:127.0.0.1:5061
listen=tcp:192.168.146.133:5061
.
.
#!ifdef WITH_TLS
enable_tls=yes
#!endif
.
.
#!ifdef WITH_TLS
# ----- tls params -----
modparam("tls", "config",
"/usr/local/kamailio-devel/etc/kamailio/tls.cfg")
#!endif
Now, according to this mailing
list,http://lists.sip-router.org/pipermail/sr-users/2013-March/077182.html
: “when
tls module is installed, a self signed pair of certificate-private
key is generated in /usr/local/etc/kamailio”
In
my case, I dont even have the /usr/local/etc/kamailio directory. So,
I followed
http://www.kamailio.org/dokuwiki/doku.php/tls:create-certificates
to create my certificate and key. And updated my tsl.cfg, this is how
my tsl.cfg looks like:
[server:192.168.146.133:5061]
method
= TLSv1
verify_certificate
= no
require_certificate
= no
private_key
= /etc/certs/sip.192.168.146.133/key.pem
certificate
= /etc/certs/sip.192.168.146.133/cert.pem
ca_list
= /etc/certs/demoCA/cert.pem
[client:192.168.146.133:5061]
verify_certificate
= yes
require_certificate
= yes
Then I restarted my kamailio server.
And i get the following errors in my kamailio log:
Im not sure what wrong im doing. Please
help me:
Oct 17 15:44:50 ubuntu kamailio: INFO:
tls [tls_init.c:385]: init_tls_compression(): tls: init_tls:
disabling compression...
Oct 17 15:44:50 ubuntu kamailio:
WARNING: <core> [socket_info.c:1397]: fix_hostname(): WARNING:
fix_hostname: could not rev. resolve 192.168.146.133
Oct 17 15:44:50 ubuntu kamailio:
message repeated 2 times: [ WARNING: <core>
[socket_info.c:1397]: fix_hostname(): WARNING: fix_hostname: could
not rev. resolve 192.168.146.133]
Oct 17 15:44:50 ubuntu kamailio: INFO:
<core> [tcp_main.c:4836]: init_tcp(): init_tcp: using epoll_lt
as the io watch method (auto detected)
Oct 17 15:44:50 ubuntu kamailio:
WARNING: <core> [daemonize.c:352]: daemonize(): pid file
contains old pid, replacing pid
Oct 17 15:44:50 ubuntu
/usr/local/kamailio-devel//sbin/kamailio[11013]: INFO: rr
[../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob
Oct 17 15:44:50 ubuntu
/usr/local/kamailio-devel//sbin/kamailio[11013]: INFO: rr
[rr_mod.c:159]: mod_init(): outbound module not available
Oct 17 15:44:50 ubuntu
/usr/local/kamailio-devel//sbin/kamailio[11013]: INFO: usrloc
[hslot.c:53]: ul_init_locks(): locks array size 512
Oct 17 15:44:50 ubuntu
/usr/local/kamailio-devel//sbin/kamailio[11013]: INFO: utils
[utils.c:288]: mod_init(): forward functionality disabled
Oct 17 15:44:50 ubuntu
/usr/local/kamailio-devel//sbin/kamailio[11013]: INFO: utils
[utils.c:197]: pres_db_init(): xcap_auth_status function is disabled
Oct 17 15:44:50 ubuntu
/usr/local/kamailio-devel//sbin/kamailio[11013]: ERROR: tls
[tls_init.c:668]: tls_check_sockets(): TLSs<192.168.146.133:5061>:
No listening socket found
Oct 17 15:44:50 ubuntu
/usr/local/kamailio-devel//sbin/kamailio[11013]: ERROR: <core>
[sr_module.c:970]: init_mod(): init_mod(): Error while initializing
module tls (/usr/local/kamailio-devel/lib64/kamailio/modules/tls.so)
Oct 17 15:44:50 ubuntu
/usr/local/kamailio-devel//sbin/kamailio[11013]: : tls
[tls_locking.c:103]: locking_f(): BUG: tls: locking_f (callback):
invalid lock number: 30 (range 0 - 0), called from eng_table.c:227
Oct 17 15:44:51 ubuntu kamailio: ERROR:
<core> [daemonize.c:307]: daemonize(): Main process exited
before writing to pipe
tls module compile log
xxx@ubuntu:/usr/local/src/kamailio-4.1/kamailio$
sudo make -C modules/tls
make:
Entering directory
`/usr/local/src/kamailio-4.1/kamailio/modules/tls'
make:
Leaving directory
`/usr/local/src/kamailio-4.1/kamailio/modules/tls'
make:
Entering directory
`/usr/local/src/kamailio-4.1/kamailio/modules/tls'
CC
(gcc) [M tls.so]
tls_bio.o
CC
(gcc) [M tls.so]
tls_cfg.o
CC
(gcc) [M tls.so]
tls_config.o
CC
(gcc) [M tls.so]
tls_ct_wrq.o
CC
(gcc) [M tls.so]
tls_domain.o
In
file included from tls_domain.c:39:0:
tls_domain.c:
In function âload_certâ:
tls_util.h:52:6:
warning: variable âretâ set but not used
[-Wunused-but-set-variable]
int
ret;
\
^
tls_domain.c:506:4:
note: in expansion of macro âTLS_ERRâ
TLS_ERR("load_cert:");
^
tls_domain.c:
In function âload_ca_listâ:
tls_util.h:52:6:
warning: variable âretâ set but not used
[-Wunused-but-set-variable]
int
ret;
\
^
tls_domain.c:536:4:
note: in expansion of macro âTLS_ERRâ
TLS_ERR("load_ca_list:");
^
tls_util.h:52:6:
warning: variable âretâ set but not used
[-Wunused-but-set-variable]
int
ret;
\
^
tls_domain.c:543:4:
note: in expansion of macro âTLS_ERRâ
TLS_ERR("load_ca_list:");
^
tls_domain.c:
In function âload_crlâ:
tls_util.h:52:6:
warning: variable âretâ set but not used
[-Wunused-but-set-variable]
int
ret;
\
^
tls_domain.c:575:4:
note: in expansion of macro âTLS_ERRâ
TLS_ERR("load_crl:");
^
tls_domain.c:
In function âload_private_keyâ:
tls_util.h:52:6:
warning: variable âretâ set but not used
[-Wunused-but-set-variable]
int
ret;
\
^
tls_domain.c:990:5:
note: in expansion of macro âTLS_ERRâ
TLS_ERR("load_private_key:");
^
tls_util.h:52:6:
warning: variable âretâ set but not used
[-Wunused-but-set-variable]
int
ret;
\
^
tls_domain.c:998:4:
note: in expansion of macro âTLS_ERRâ
TLS_ERR("load_private_key:");
^
tls_util.h:52:6:
warning: variable âretâ set but not used
[-Wunused-but-set-variable]
int
ret;
\
^
tls_domain.c:1005:4:
note: in expansion of macro âTLS_ERRâ
TLS_ERR("load_private_key:");
^
CC
(gcc) [M tls.so]
tls_dump_vf.o
CC
(gcc) [M tls.so]
tls_init.o
CC
(gcc) [M tls.so]
tls_locking.o
CC
(gcc) [M tls.so]
tls_mod.o
CC
(gcc) [M tls.so]
tls_rpc.o
CC
(gcc) [M tls.so]
tls_select.o
CC
(gcc) [M tls.so]
tls_server.o
In
file included from tls_server.c:52:0:
tls_server.c:
In function âtls_complete_initâ:
tls_util.h:52:6:
warning: variable âretâ set but not used
[-Wunused-but-set-variable]
int
ret;
\
^
tls_server.c:192:3:
note: in expansion of macro âTLS_ERRâ
TLS_ERR("Failed
to create SSL or BIO structure:");
^
tls_server.c:
In function âtls_shutdownâ:
tls_util.h:52:6:
warning: variable âretâ set but not used
[-Wunused-but-set-variable]
int
ret;
\
^
tls_server.c:521:4:
note: in expansion of macro âTLS_ERRâ
TLS_ERR("SSL
error:");
^
tls_server.c:
In function âtls_encode_fâ:
tls_util.h:52:6:
warning: variable âretâ set but not used
[-Wunused-but-set-variable]
int
ret;
\
^
tls_server.c:798:5:
note: in expansion of macro âTLS_ERRâ
TLS_ERR(err_src);
^
tls_util.h:52:6:
warning: variable âretâ set but not used
[-Wunused-but-set-variable]
int
ret;
\
^
tls_server.c:832:5:
note: in expansion of macro âTLS_ERRâ
TLS_ERR(err_src);
^
tls_server.c:
In function âtls_read_fâ:
tls_util.h:52:6:
warning: variable âretâ set but not used
[-Wunused-but-set-variable]
int
ret;
\
^
tls_server.c:1186:4:
note: in expansion of macro âTLS_ERRâ
TLS_ERR(err_src);
^
tls_util.h:52:6:
warning: variable âretâ set but not used
[-Wunused-but-set-variable]
int
ret;
\
^
tls_server.c:1220:4:
note: in expansion of macro âTLS_ERRâ
TLS_ERR(err_src);
^
CC
(gcc) [M tls.so]
tls_util.o
CC
(gcc) [M tls.so]
tls_verify.o
LD
(gcc) [M tls.so]
tls.so
make:
Leaving directory `/usr/local/src/kamailio-4.1/kamailio/modules/tls'