Hello,
I have some feature required changes in acc module.
In acc module we getting cdrs in database only which have
METHOD=INVITE
METHOD=BYE
but in my setup I also get
METHOD=OPTIONS
so I need this entry also in acc table in kamailio database.
so which changes i need to do in kamailio acc module.... or other......
my cdrs log I paste below which have mehod=options
"Sep 7 07:16:53 sip /usr/local/sbin/kamailio[29264]: NOTICE: acc
[acc.c:317]: acc_log_request(): ACC: request accounted:
timestamp=1504783013;method=OPTIONS;from_tag=eUC9UgGrD;to_tag=j90H6yy5pU6Xc;call_id=2xJd0KCt-P;code=200;reason=OK;calling=46566464645;called=you;egressIP=
kamailio.org;src_ip=1.0.0.127;to=sip:+918866213320@sip.call.org
;tag=j90H6yy5pU6Xc;from=sip:918888888888@localhost;contact=;pai=;uri=sip:
you(a)kamailio.org;onnet=0;rate=0.000333333"
Thanks.. # #
Hello kamailio list,
Recently found a problem in my configuration that uses async_route()
functionality.
It crashes after several calls when wait_timer fires.
#0 0xb74a8556 in raise () from /lib/libc.so.6
#1 0xb74a9d78 in abort () from /lib/libc.so.6
#2 0x08293ae2 in qm_free (qmp=0xad65d000, p=0x3d64692d, file=0xb6216a16
"tm: h_table.c", func=0xb621663c <__FUNCTION__.18751> "free_cell_helper",
line=187, mname=0xb621664d "tm") at core/mem/q_malloc.c:471
#3 0xb613f103 in free_cell_helper (dead_cell=0xae2cd210, silent=0,
fname=0xb6239ea5 "timer.c", fline=655) at h_table.c:187
#4 0xb61e7758 in wait_handler (ti=557858937, wait_tl=0xae2cd258,
data=0xae2cd210) at timer.c:655
#5 0x0826a2cc in timer_list_expire (t=557858937, h=0xad6b9668,
slow_l=0xad6ba144, slow_mark=312) at core/timer.c:874
#6 0x08267cb1 in timer_handler () at core/timer.c:939
#7 0x0826a4d3 in timer_main () at core/timer.c:978
#8 0x08069575 in main_loop () at main.c:1721
#9 0x080707ca in main (argc=11, argv=0xbf85f044) at main.c:2723
When crash happens, kamailio prints the following message:
Sep 4 16:15:38 [18938]: : <core> [core/mem/q_malloc.c:469]: qm_free():
BUG: qm_free: bad pointer 0x70707553 (out of memory block!) called from tm:
h_table.c: free_cell_helper(187) - aborting
Also had a few crashes in retransmission_handler():
#0 0xb750b556 in raise () from /lib/libc.so.6
#1 0xb750cd78 in abort () from /lib/libc.so.6
#2 0xb6249b5a in retransmission_handler (r_buf=0xae036674) at timer.c:367
#3 0xb6247558 in retr_buf_handler (ticks=1234464444, tl=0xae036688,
p=0x1f40) at timer.c:594
#4 0x0826a2cc in timer_list_expire (t=1234464444, h=0xad71c668,
slow_l=0xad71cd44, slow_mark=2232) at core/timer.c:874
#5 0x08267cb1 in timer_handler () at core/timer.c:939
#6 0x0826a4d3 in timer_main () at core/timer.c:978
#7 0x08069575 in main_loop () at main.c:1721
#8 0x080707ca in main (argc=11, argv=0xbff64134) at main.c:2723
ERROR: tm [timer.c:366]: retransmission_handler(): transaction 0xae0365e0
scheduled for deletion and called from RETR timer (flags 6d)
Both timers fired for an INVITE transaction that was previously suspended
by async_route(), then resumed, sent out and received a 4xx reply (407).
This configuration worked fine with kamailio 4.2.x and problem appeared
after upgrading to 5.0.2.
Trying to figure out how to narrow down the problem. Any input is
appreciated.
Hello,
I have
modparam("alias_db", "append_branches", 1)
and table dbaliases
+----+----------------+-----------------+----------+-----------------+
| id | alias_username | alias_domain | username | domain |
+----+----------------+-----------------+----------+-----------------+
| 1 | 1111 | sipchel | 34200 | sipchel |
| 2 | 1111 | sipchel | 34201 | sipchel |
+----+----------------+-----------------+----------+-----------------+
If I call to 1111 ringing only 34200, because first invite is right
(resolving to username contact), but branch inivite is wrong. Is it bug or
it is my my fault?
First:
INVITE sip:34200@172.16.3.7:5060 SIP/2.0
Via: SIP/2.0/UDP
192.168.10.54;branch=z9hG4bKa277.42eb85466191923b73c9234c5c342b67.0
Via: SIP/2.0/UDP 172.16.3.4:5060;branch=z9hG4bK-c5fef8cc
From: "" <sip:53003@192.168.10.54>;tag=1898fba2a5729040o0
To: <sip:1111@192.168.10.54>
Second:
INVITE sip:34201@sipchel SIP/2.0
Record-Route: <sip:192.168.10.54;lr=on;ftag=1898fba2a5729040o0;did=958.fd11>
Via: SIP/2.0/UDP
192.168.10.54;branch=z9hG4bKa277.42eb85466191923b73c9234c5c342b67.1
Via: SIP/2.0/UDP 172.16.3.4:5060;branch=z9hG4bK-c5fef8cc
From: "" <sip:53003@192.168.10.54>;tag=1898fba2a5729040o0
To: <sip:1111@192.168.10.54>
--
Aydar A. Kamalov
Hi.
Recently I've come across with TCP connection problem.
The topology is as following:
DNS srv load balancer - two kamailio proxy servers - one routing server.
Client appeals to NAPTR record like: sip.domain.com
So dns returns one of the proxy servers to client (depending on
weight/priority). Now both kamailio have the same priority and weight (the
goal is load balancing).
Routing server (now it is asterisk) working with chan_pjsip.so, that
supports NAPTR/SRV records.
He is able to resolve Record-Route / Route headers with value -
sip.domain.com (that proxy servers add to record-route headers while
relaying requests to him).
This topology is done to support present dialogs, even if proxy that
recently processed it, is dead.
But the problem comes, when routing server (asterisk) sends in-dialog
requests to the proxy, that wasn't used to establish the dialog.
Example, routing server obtains 200 OK from endpoint (relayed by kamailio1
to him) and he sends back ACK, but not to the kamailio1, he sends it to
kamailio2 (because he resolves NAPTR sip.domain.com and gets ip of second
kamailio). Kamailio2 processes the request as usual, because both kamailio
have the same db for dialog module, but when he tries to relay the request
to endpoint, he gots the error:
ERROR: <core> [tcp_main.c:4070]: handle_tcpconn_ev(): connect
XXX.XXX.XXX.XXX:52185 failed
The port that kamailio2 tries to use to relay the ACK, is port that
endpoint used to establish the dialog with kamailio1 and actually his TCP
connection is now established with kamailio1.
So kamailio2 tries to use the same port and gets the error.
And this is proper behavior I think.
There is no problem with UDP transport.
Has anyone seen the similar problem? That indeed is not a problem, but
proper behavior.
--
--
BR, Donat Zenichev
Wnet VoIP team
Tel: +380(44) 5-900-808
http://wnet.ua
Hello,
I am using carrierroute in Kamailio (great module btw).
All calls go the same gateway (rewrite_host). I am routing over differents
vendor using a prefix.
Prefix: 21
dnis: 999999999
$rU after rewrite_host is 21999999999
My problem is when trying to use a failure route, next domain use a
different prefix but the host.
So I get the:
Candidate destination <gateway> was previously used
Is there a flag or something to prevent this verification ?
Thank you
Nelson.-
Hi,
I am handling Two Different Account holders and Two Different Gateways with
the different lcr_ids:
id :1
lcr_id:1
gw_name:car1
ip_addr : 1.2.3.4
id :2
lcr_id:2
gw_name:car2
ip_addr : 1.2.5.3
In kamailio config file I am using load_gws(1), Here Comes my doubt, I need
to Pass the lcr_id value inside the load_gws(lcr_id) Dynamically, Is it
Possible , Please Guide me.
Thanks & Kind Regards,
*Logeshwaran G*
*"Be Hunger, Stay Foolish"*
Hi,
May I know the Difference between the "prefix" column in Lcr_gw table and
lcr_rule table.
I am using the prefix value in lcr_rule table, like 00091.
But What is the use of Prefix Column in lcr_gw table. Input Please
Thanks & Kind Regards,
*Logeshwaran G*
*"Be Hunger, Stay Foolish"*
Hello all, I'm becoming a regular here now, aren't I?
So I have this table in mysql:
+----------+----------+--------+-----------+---------+
| key_name | key_type | value1 | value2 | value3 |
+----------+----------+--------+--------+--------+
| key1 | 1 | valueA | valueF | valueK |
| key1 | 1 | valueB | valueG | valueL |
| key1 | 1 | valueC | valueH | valueM |
| key2 | 1 | valueD | valueI | valueN |
| key2 | 1 | valueE | valueJ | valueO |
I was hoping I could have all this information available in an sht, where
for example:
$sht(a=>$key1[0]), $sht(a=>$key1[1]), etc
would return:
"valueA,valueF,valueK", "valueB,valueG,valueL" etc
but I can't figure out how to setup htable to import this data on
restart. I have tried various combinations of module parameters such
as:
modparam("htable", "htable",
'my_htable=>size=8;autoexpire=86400;dbtable=my_table;cols="key_name,value1,value2,value3";'
I'm either getting errors, or dumping htable will only show one of the
value sets (key_type is not set to array).
Does anyone have a working config to share? Thanks!
George