This makes the main problem as in documents I've found on asterisk is
that it doesn't support PUBLISH, i.e. there is no way to force sending
them on MWI event. It works only on SUBSCRIBE-NOTIFY scheme.
Did you succeeded with PUBLISH on Asterisk in order to inform Kamailio
about MWI? If yes, how? Cause right now, for me, it looks like a theory,
cause no mechanics to force asterisk send PUBLISHes.
Thank you.
Regards,
Evgeniy Spinov
> If you are using asterisk for voicemail, you should let asterisk
> notify the subscribers about mwi.
> If you want to use kamailio for notifications, then you need to
> configure asterisk to send PUBLISH requests to kamailio and kamailio
> will notify the subscribers.
> Regards,
> Ovidiu Sas
I'm having an issue trying to use the construct show in the module documentation.
The docs show:
while(mq_fetch("myq"))
{
xlog("$mqk(myq) - $mqv(myq)\n");
}
And I'm doing essentially the same thing (differently named mqueue, but otherwise identical), but invariably I get this in the logs:
ERROR: <core> [action.c:1388]: ERROR: runaway while (559, 28): more then 100 loops
Am I doing something wrong, or is mq_fetch not returning appropriate values for successful versus failed fetches?
This is on Kamailio 3.1.4, FWIW.
Regards,
- Brad
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
Can someone send me bitmasks for the Subj.
Or just the reference to include file with comments in a source code.
I can't find it in all set of availible document's since the SER router. :(
I just have to know which UA except Grandstreams an CSipsample use RFC3311 :)
Thanks in advance.
Andrew O. Zhukov
will kamailio as proxy behind nat and UACs behind another nat work?
port forward sip and rtp done in the router.
UACs register successfully but no audio.
advertised_address = public_ip
advertised_port = sip
both define after the line of listen=public_ip
please advice.
thanks.
--
Regards,
MingHon
Hello,
Could anyone help with suggestions on how to setup a Proxy ( R-Proxy) that only
does a route lookup and pass the parameter back to origination Proxy/Gateway A
to forward the call based on the new parameter.
On receipt of an invite from GW/Proxy A, R- Proxy will do a route lookup for
the called number 447988870290,
If it finds a route then it should append the network prefix to the new INVITE
or rewrite the INVITE 23430442088870290 in the 302 Moved Temporarily message
sent back to GW/Proxy A in the Contact field and there are two CC-Diversion
header fields included; at GW/Proxy (IP address) who originated the call and
already has a route or dial plan for the new prefix and also another one for
same at GW/Proxy (IP address).
Is there any way to do this without creating a loop in the network ?
Previously this setup can be achieved with the originating network having 2
GW/Proxies i.e. GW/Proxy A and GW/Proxy B. In the 302 Temporarily moved
message the Contact will show GW/Proxy B, while the 2 CC-Diversion header
fields will add GW/Proxy B and GW Proxy A.
Regards,
Abdul Hakeem
Hello.
Trying to understand how to work with the presence_mwi module. It seems
to me, that it's just for my purpose - inform subscribed peers about
waiting messages. But it do not export any functions, noting.
The scheme is simple: Peer->Kamailio->Asterisk.
Asterisk can accept voicemail and when the message is saved I want to
receive NOTIFY for subscribed peer. As I understand, peer should
register on Kamailio, kamailio should accept this subscription and send
subscription to asterisk. After this, need to proxy all NOTIFY to the
peer.
Anyway, cannot find any way to do that. How it's usually done, please,
advice.
Thanks in advance.
Thanks Juha
I populated the lcr tables by hand. This is how they look now, I have 2 lcr_ids [1 and 2], each instance has its own gw. And each instance has its own prefix to match for [4444 and 5555].
The idea is that a call comes in with R-URI 444413051234567, it should match the lcr_id= 200, then it should go out using gw 192.168.169.200 etc
mysql> select * from lcr_gw;
+----+--------+------------+-----------------+-------------------+------+--------+------------+-----------+-------+------+-------+---------+
| id | lcr_id | gw_name | ip_addr | hostname | port | params | uri_scheme | transport | strip | tag | flags | defunct |
+----+--------+------------+-----------------+-------------------+------+--------+------------+-----------+-------+------+-------+---------+
| 1 | 200 | switchvox | 192.168.169.200 | pbx1.mydomain.com | 5060 | none | 1 | 1 | 0 | | 0 | 0 |
| 2 | 201 | switchvox2 | 192.168.169.201 | pbx1.mydomain.net | 5060 | none | 1 | 1 | 0 | | 0 | 0 |
+----+--------+------------+-----------------+-------------------+------+--------+------------+-----------+-------+------+-------+---------+
mysql> select * from lcr_rule;
+----+--------+--------+----------+---------+---------+
| id | lcr_id | prefix | from_uri | stopper | enabled |
+----+--------+--------+----------+---------+---------+
| 1 | 200 | 4444 | | 0 | 1 |
| 2 | 201 | 5555 | | 0 | 1 |
+----+--------+--------+----------+---------+---------+
mysql> select * from lcr_rule_target;
+----+--------+---------+-------+----------+--------+
| id | lcr_id | rule_id | gw_id | priority | weight |
+----+--------+---------+-------+----------+--------+
| 1 | 200 | 1 | 1 | 5 | 1 |
| 2 | 201 | 2 | 2 | 5 | 1 |
+----+--------+---------+-------+----------+--------+
Then I tried the sercmd commands to reload and dump and I do not see the contents o the screen. Is this how is supposed to work now?.
with debug level set to 3 I do this "/usr/local/kamailio-3.1/sbin/sercmd lcr.dump_rules"
and see these lines on the syslog:
Jun 28 11:53:57 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: ctl [../../io_wait.h:390]: DBG: io_watch_add(0x2b772e494660, 12, 3, 0x9679e8), fd_no=1
Jun 28 11:53:57 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: ctl [io_listener.c:452]: handle_stream read: new connection (1) on /tmp/ser_ctl
Jun 28 11:53:57 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: ctl [io_listener.c:505]: handle_stream read: eof on /tmp/ser_ctl
Jun 28 11:53:57 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: ctl [../../io_wait.h:617]: DBG: io_watch_del (0x2b772e494660, 12, -1, 0x10) fd_no=2 called
if I do this: "/usr/local/kamailio-3.1/sbin/sercmd lcr.reload"
I see these:
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: ctl [../../io_wait.h:390]: DBG: io_watch_add(0x2b772e494660, 12, 3, 0x9679e8), fd_no=1
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: ctl [io_listener.c:452]: handle_stream read: new connection (1) on /tmp/ser_ctl
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db.c:294]: connection 0x951b78 found in pool
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:118]: allocate 48 bytes for result set at 0x952728
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:68]: 5 columns returned from the query
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:155]: allocate 40 bytes for result names at 0x9527b8
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:165]: allocate 20 bytes for result types at 0x952610
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[0] at 0x9528b8
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x9528b8)[0]=[id]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[1] at 0x952928
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952928)[1]=[prefix]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:136]: use DB1_STRING result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[2] at 0x951a98
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x951a98)[2]=[from_uri]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:136]: use DB1_STRING result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[3] at 0x951b08
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x951b08)[3]=[stopper]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[4] at 0x952998
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952998)[4]=[enabled]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_dbase.c:326]: no rows returned from the query
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: lcr [lcr_mod.c:985]: loading, cycle 0 with <0> rows
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:81]: freeing 5 columns
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[0] at 0x9528b8
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[1] at 0x952928
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[2] at 0x951a98
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[3] at 0x951b08
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[4] at 0x952998
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:94]: freeing result names at 0x9527b8
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:99]: freeing result types at 0x952610
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:136]: freeing result set at 0x952728
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:118]: allocate 48 bytes for result set at 0x952728
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:68]: 12 columns returned from the query
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:155]: allocate 96 bytes for result names at 0x951ef8
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:165]: allocate 48 bytes for result types at 0x951c38
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[0] at 0x951b08
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x951b08)[0]=[gw_name]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:136]: use DB1_STRING result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[1] at 0x951a98
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x951a98)[1]=[ip_addr]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:136]: use DB1_STRING result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[2] at 0x952928
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952928)[2]=[port]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[3] at 0x9528b8
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x9528b8)[3]=[uri_scheme]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[4] at 0x952610
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952610)[4]=[transport]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[5] at 0x952998
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952998)[5]=[params]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:136]: use DB1_STRING result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[6] at 0x9527b8
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x9527b8)[6]=[hostname]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:136]: use DB1_STRING result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[7] at 0x951fb8
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x951fb8)[7]=[strip]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[8] at 0x952028
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952028)[8]=[tag]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:136]: use DB1_STRING result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[9] at 0x952098
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952098)[9]=[flags]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[10] at 0x952108
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952108)[10]=[defunct]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[11] at 0x951288
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x951288)[11]=[id]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:169]: no rows returned from the query
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:81]: freeing 12 columns
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[0] at 0x951b08
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[1] at 0x951a98
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[2] at 0x952928
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[3] at 0x9528b8
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[4] at 0x952610
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[5] at 0x952998
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[6] at 0x9527b8
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[7] at 0x951fb8
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[8] at 0x952028
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[9] at 0x952098
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[10] at 0x952108
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[11] at 0x951288
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:94]: freeing result names at 0x951ef8
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:99]: freeing result types at 0x951c38
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:136]: freeing result set at 0x952728
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:118]: allocate 48 bytes for result set at 0x952728
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:68]: 4 columns returned from the query
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:155]: allocate 32 bytes for result names at 0x952998
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:165]: allocate 16 bytes for result types at 0x951288
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[0] at 0x952098
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952098)[0]=[rule_id]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[1] at 0x952028
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x952028)[1]=[gw_id]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[2] at 0x951fb8
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x951fb8)[2]=[priority]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:85]: allocate 16 bytes for RES_NAMES[3] at 0x9528b8
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:92]: RES_NAMES(0x9528b8)[3]=[weight]
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_res.c:100]: use DB1_INT result type
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: db_mysql [km_dbase.c:326]: no rows returned from the query
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: lcr [lcr_mod.c:1344]: loading, cycle 0 with <0> rows
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:81]: freeing 4 columns
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[0] at 0x952098
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[1] at 0x952028
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[2] at 0x951fb8
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:85]: freeing RES_NAMES[3] at 0x9528b8
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:94]: freeing result names at 0x952998
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:99]: freeing result types at 0x951288
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_res.c:136]: freeing result set at 0x952728
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: <core> [db_pool.c:97]: connection still kept in the pool
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: ctl [io_listener.c:505]: handle_stream read: eof on /tmp/ser_ctl
Jun 28 11:55:04 registrar /usr/local/kamailio-3.1/sbin/kamailio[4309]: DEBUG: ctl [../../io_wait.h:617]: DBG: io_watch_del (0x2b772e494660, 12, -1, 0x10) fd_no=2 called
I am trying to port our setup from kamailio 1.4.3 to 3.1.4 and I see
> huge differences on the LCR module.
there is a script somewhere (read wiki) that upgrades the tables.
> I have these main questions:
>
> 1- does lcr_id replaces the grp_id?
not really. lcr_ids denote independent lcr instances.
> 2- what happened to the fifo commands to add gws etc:
fifo commands to manipulate lcr tables are not supported by me.
-- juha
From: fborot(a)hotmail.com
To: sr-users(a)lists.sip-router.org
Subject: Questions about LCR module
Date: Mon, 27 Jun 2011 17:23:05 -0400
I am trying to port our setup from kamailio 1.4.3 to 3.1.4 and I see huge differences on the LCR module.
I have these main questions:
1- does lcr_id replaces the grp_id?
2- what happened to the fifo commands to add gws etc:
lcr addgw <gw_name> <ip> <port> <scheme> <transport> <grp_id> <flags> <tag> <strip>
............... add a gateway with flags, tag and strip ............
................(flags, tag, and strip are optional arguments) .....
lcr rmgw <gw_name> ..........................................................
............... delete a gateway
lcr addroute <prefix> <from> <grp_id> <prio> .................................
.............. add a route ( use '' to match anything in <from> )
lcr rmroute <prefix> <from> <grp_id> <prio> .................................
.............. delete a route
3- it looks like the kamctl fifo lcr reload can not be used anymore, instead I found that there is a sercmd command that can be used to "show" and "reload" only the lcr tables
What would be the best way to use this module on this version?
Any help/hint would be greatly appreciated.
thank you
fborot
Hello,
I've just setup Kamailio+ Asterisk following Daniel Constantin Mierla
howto
http://kb.asipto.com/asterisk:realtime:kamailio-3.1.x-asterisk-1.6.2-astdb
Everything seemts to works and I'm able to place a call to local
extensions.
I'm able to establish a call but strangely I get and 491 error code on
my SIP Phones
In my Asterisk console I get this error :
[Jun 28 18:14:42] WARNING[24432]: chan_sip.c:18087 handle_response_invite:
just did sched_add waitid(23) for sip_reinvite_retry for dialog
LIFuQLu1l3ZtKrNy0XDX7lEk.Y5JdFko in handle_response_invite
== Spawn extension (from-local, 102, 1) exited non-zero on
'SIP/103-00000000'
Anybody can give me an hand to solve this issue ?
Best regards
Hello
I have little experience with the dialog module -so sorry if the quesiton is
silly-, and I was wondering if I could use it for doing accounting (acc
works just fine, but I was looking for a unique stop record that includes
all the call information). The basic idea would be to assign the initial
INVITE to a profile; and then, when BYE is received, build a cdr based of
the dialog attributes...but afaik , upon reception of the BYE the dialog is
destroyed. is there a way to access the dlg attributes inside the script
when the BYE transaction is processed?
Thanks in advance
Javi
I am trying to port our setup from kamailio 1.4.3 to 3.1.4 and I see huge differences on the LCR module.
I have these main questions:
1- does lcr_id replaces the grp_id?
2- what happened to the fifo commands to add gws etc:
lcr addgw <gw_name> <ip> <port> <scheme> <transport> <grp_id> <flags> <tag> <strip>
............... add a gateway with flags, tag and strip ............
................(flags, tag, and strip are optional arguments) .....
lcr rmgw <gw_name> ..........................................................
............... delete a gateway
lcr addroute <prefix> <from> <grp_id> <prio> .................................
.............. add a route ( use '' to match anything in <from> )
lcr rmroute <prefix> <from> <grp_id> <prio> .................................
.............. delete a route
3- it looks like the kamctl fifo lcr reload can not be used anymore, instead I found that there is a sercmd command that can be used to "show" and "reload" only the lcr tables
What would be the best way to use this module on this version?
Any help/hint would be greatly appreciated.
thank you
fborot
