Hello. I started configure Kamailio 3.3 server with mysql database, that running on the remote server. I customise settings at kamailio.cfg (for BDURL) and kamctlc file (for my db - changed user, password, dbhost and other settings, such as dbengine and etc.)
Now, when I tried add new subscriber from kamctl util (kamctl add newuser@kamailioIP passwd). I see "access denied for <myuser>@<interface of kamailio server>", But as I aleady says I configured filew with other settings for db server.
Where I must configure ip of dbhost to connect kamctl to my dbserver?
Hi to all,
I’m using “kamailio” command to see alerts,notices and warnings but it also starts a new kamailio process.Is there a way to see command line without starting a new kamailio process?
I need something just like asterisk –rvvvvvvvvvvv in asterisk.
Thanks in Advance.
I tried to call record_route_preset() in branch route in order to add
contact specific RR headers when request is forked to more than one
contact. What happened was that I got error message:
Sep 26 17:03:47 wheezy2 /usr/sbin/sip-proxy[2436]: ERROR: rr [rr_mod.c:256]: Duble attempt to record-route
Is it really so that record routing is not a branch specific thing? Is
there a way to solve this problem?
-- Juha
Hi folks,
I am using Kamailio with IMS, I added the configuration of the WebSocket to the kamailio.cfg in the PCSCF to enable WebRTC clients like (JsSIP) to communicate with each other.. The registration works so far, however when I try to make peer-2-peer call between alice and bob, the caller gets a "403 error" "403 Forbidden Mohammed- Dialog not found on S-CSCF or Terminating user not suitable for unregistered services" from the S-CSCF..
I did trace on the PCSCF and I found a strange signaling behaviour.
the invite is negotiated between the IMS components as follows:
INVITE from PCSCF to SCSCF
INVITE from PCSCF to PCSCF
PCSCF responses itself with "403 Forbidden - You must register first with a S-CSCF"
SCSCF sends the response "403 Forbidden Mohammed- Dialog not found on S-CSCF or Terminating user not suitable for unregistered services" to the PCSCF
The private IP address of the PCSCF is 172.19.6.35 and of the SCSCF is 172.19.6.36. The PCSCF has a public IP "193.175.132.235"
The IMS components don't run on the same machine, PCSCF and SCSCF are listening to the port 5060. the WebSocket port of the PCSCF is 8000
Can anyone help me get a solution for this problem
Thanks in advance
Best regards,
Medo
Mohammed Al-khameri
Technical University Berlin TUB
Hello
I’am using default config with options from an example. It looks like event route isn’t execuded after hangup.
Apr 26 16:26:14 kamailio /usr/local/sbin/kamailio[4611]: INFO: <script>: 1000 has 1 call(s)
Apr 26 16:26:15 kamailio /usr/local/sbin/kamailio[4611]: INFO: <script>: 1000 has 1 call(s)
Apr 26 16:26:16 kamailio /usr/local/sbin/kamailio[4611]: INFO: <script>: 1000 has 1 call(s)
Apr 26 16:26:17 kamailio /usr/local/sbin/kamailio[4611]: INFO: <script>: 1000 has 1 call(s)
Apr 26 16:26:18 kamailio /usr/local/sbin/kamailio[4611]: INFO: <script>: 1000 has 1 call(s)
Apr 26 16:26:19 kamailio /usr/local/sbin/kamailio[4611]: INFO: <script>: 1000 has 1 call(s)
Apr 26 16:26:20 kamailio /usr/local/sbin/kamailio[4611]: INFO: <script>: 1000 has 1 call(s)
Apr 26 16:26:20 kamailio /usr/local/sbin/kamailio[4604]: INFO: <script>: Setting up money based credit control
Apr 26 16:26:20 kamailio /usr/local/sbin/kamailio[4604]: INFO: <script>: Setting up channel based credit control
Apr 26 16:26:20 kamailio /usr/local/sbin/kamailio[4604]: INFO: <script>: CNXCC ROUTE: 1000 has 2 call(s)
kamailio.cfg
…
…
# ----- prepaid call controll -----
#!define DLG_FLAG 28
#!define CC_FLAG 29
loadmodule "dialog.so"
modparam("dialog", "hash_size", 2048)
modparam("dialog", "default_timeout", 3600)
modparam("dialog", "db_mode", 0)
modparam("dialog", "dlg_flag", DLG_FLAG)
modparam("rtimer", "timer", "name=ta;interval=1;mode=1;")
modparam("rtimer", "exec", "timer=ta;route=SHOW_CHANNEL_COUNT")
loadmodule "cnxcc.so"
modparam("cnxcc", "dlg_flag", CC_FLAG)
modparam("cnxcc", "credit_check_period", 1) #check every 1 second
…
…
…
route {
…
…
if (!allow_source_address("2") and !allow_source_address("1")){
route(CNXCC);
route(PSTN);
}
…
}
route[CNXCC]
{
$var(client) = "1000";
xlog("L_INFO", "Setting up money based credit control");
$var(credit) = "10"; # 10$ of credit
$var(cost_per_sec) = "1"; # 1$ per sec
$var(i_pulse) = "1"; # 1$ to establish the call
$var(f_pulse) = "1"; # 1$ per second
# if only one call is established, that call should last 9 seconds.
if (!cnxcc_set_max_credit("$var(client)",
"$var(credit)",
"$var(cost_per_sec)",
"$var(i_pulse)",
"$var(f_pulse)")) {
xlog("Error setting up credit control");
return;
}
$var(count) = -1;
if (!cnxcc_get_channel_count("$var(client)", "$var(count)")) {
xlog("Error getting customer's channel count");
}
xlog("L_INFO", "CNXCC ROUTE: $var(client) has $var(count) call(s)");
if ($var(retcode) < -1) {
xlog("Too many channels for customer");
sl_send_reply(403, "Forbidden");
if (!cnxcc_terminate_all("$var(client)")) {
xlog("Error terminating customer's calls");
} else {
xlog("Terminating customer's call");
}
exit;
}
}
route[SHOW_CHANNEL_COUNT]
{
$var(count) = @cnxcc.channels["1000"].count;
xlog("L_INFO", "1000 has $var(count) call(s)");
}
event_route[dialog:failed]
{
xlog("dialog failed");
}
event_route[cnxcc:call-shutdown]
{
xlog("L_INFO", "Shutting down channel by callcontroll");
xlog("L_INFO", "[$ci]: call killed");
$var(count) = $var(count)-1;
if (!cnxcc_get_channel_count("$var(client)", "$var(count)")) {
xlog("Error getting customer's channel count");
}
xlog("L_INFO", "CNXCC ROUTE: $var(client) has $var(count) call(s)");
# perform some kind of notification, database update, email sending, etc
}
Greetings
Andrzej Ciupek
Od: Carlos Ruiz Díaz
Wysłano: sobota, 26 kwietnia 2014 15:19
Do: Kamailio (SER) - Users Mailing List, Andrzej Ciupek
Hi,
sorry guys, I forgot about this. I will make my own tests and post the results.
Andrzej, can you post the configuration file you are using?
Regards,
Carlos
On Sat, Apr 26, 2014 at 4:15 AM, Kelvin Chua <kelchy(a)gmail.com> wrote:
No, I have not yet found the solution for this issue on my setup.
Maybe Carlos can help us out
On Apr 26, 2014 5:10 PM, "Andrzej Ciupek" <andrzej.ciupek(a)hotmail.com> wrote:
Hello
Have You solved this issue ?
I’am using Kamailio 4.1.3 and I’am getting the same results.
Greetings
Andrzej Ciupek
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Carlos
http://caruizdiaz.comhttp://ngvoice.com
+52 55 3048 3303
No, I have not yet found the solution for this issue on my setup.
Maybe Carlos can help us out
On Apr 26, 2014 5:10 PM, "Andrzej Ciupek" <andrzej.ciupek(a)hotmail.com>
wrote:
> Hello
>
> Have You solved this issue ?
> I’am using Kamailio 4.1.3 and I’am getting the same results.
>
> Greetings
> Andrzej Ciupek
>
Hi folks,
I am using Kamailio with IMS, I added the configuration of the WebSocket to the kamailio.cfg in the PCSCF to enable WebRTC clients like (JsSIP) to communicate with each other.. The registration works so far, however when I try to make peer-2-peer call between alice and bob, the caller gets a "403 error" "403 Forbidden Mohammed- Dialog not found on S-CSCF or Terminating user not suitable for unregistered services" from the S-CSCF..
I did trace on the PCSCF and I found a strange signaling behaviour.
the invite is negotiated between the IMS components as follows:
INVITE from PCSCF to SCSCF
INVITE from PCSCF to PCSCF
PCSCF responses itself with "403 Forbidden - You must register first with a S-CSCF"
SCSCF sends the response "403 Forbidden Mohammed- Dialog not found on S-CSCF or Terminating user not suitable for unregistered services" to the PCSCF
The private IP address of the PCSCF is 172.19.6.35 and of the SCSCF is 172.19.6.36. The PCSCF has a public IP "193.175.132.235"
The IMS components don't run on the same machine, PCSCF and SCSCF are listening to the port 5060. the WebSocket port of the PCSCF is 8000
Can anyone help me get a solution for this problem
Thanks in advance
Best regards,
Medo
Mohammed Al-khameri
Technical University Berlin TUB
Greetings,
I need a little help with the LCR module. I am running Kamailio 4.1.2.
The LCR module is behaving in a way that is inconsistent with our old 1.5
versions. We have a customer that passes a certain caller-id. That
from_uri should be routing over a specific trunk. Here are the relevant
bits of the LCR data from kamcmd.
I would expect gw_index: 7 to match before gw_index: 6 here, but that is
not the case. Any help would be greatly appreciated. Please note, i Have
stripped out a bunch of other routes that are not in play here... hence the
reason gw_index starts at "6".
kamcmd> lcr.dump_gws
{
lcr_id: 1
gw_id: 11
gw_index: 6
gw_name: Route A
scheme: sip
ip_addr: 1.2.3.4
hostname:
port: 5060
params:
transport: UDP
strip: 0
prefix:
tag:
flags: 2
defunct_until: 0
}
{
lcr_id: 1
gw_id: 1
gw_index: 7
gw_name: Route P
scheme: sip
ip_addr: 4.3.2.1
hostname:
port: 5060
params:
transport: UDP
strip: 0
prefix: DLR#
tag:
flags: 0
defunct_until: 0
}
kamcmd> lcr.dump_rules
{
lcr_id: 1
rule_id: 31
prefix: +1
from_uri: 2089328663
request_uri:
stopper: 0
}
{
gw_index: 6
priority: 1
weight: 1
}
{
lcr_id: 1
rule_id: 5
prefix: +1
from_uri:
request_uri:
stopper: 0
}
{
gw_index: 7
priority: 1
weight: 1
}
