May this mailing list have a search function? This function will make us convient to find what we concern about.
OpenIMSCore mailing list have this function, and I felt it Improved productivity.
And the mailing list archive system seems to be operated manually. Can the mails be archived automatically? So it can be more instant to developers from asia.
BR WangXinXin
Hi, I am a rookie in SIP related area.
I run into OpenIMSCore in recent days, and then I was introduced to Kamailio.
Now I am wondering what SIP stack does Kamailio or OpenIMSCore implements? Or neither of them use a SIP stack?
Can anybody help me on this? Thanks !
sr-users-request(a)lists.sip-router.org пишет:
> Hello On 04/09/15 07:57, ?????? ???? wrote:
>> >Hello (sorry for my bad english) - i try to create voice record
>> >service by request. User A call to user B. In call by pressing
>> >combination like *55 Kamailio must redirect both sides to asterisk,
>> >whitch create dynamic conference room with recording. As i understand
>> >i need to use dlg_refer() from dialog module, but in log file i get:
>> >Konsole output
>> >Sep 4 10:45:14 voipc-node2 /usr/local/sbin/kamailio[18941]: ERROR:
>> >dialog [dlg_req_within.c:85]: build_dlg_t(): no contact available
>> >Sep 4 10:45:14 voipc-node2 /usr/local/sbin/kamailio[18941]: ERROR:
>> >dialog [dlg_transfer.c:188]: dlg_refer_callee(): failed to create dlg_t
>> >
>> >
>> >In script i try to refer with:
>> >dlg_refer("callee","sip:100@10.10.9.209");
>> >dlg_refer("caller","sip:100@10.10.9.209");
>> >
> in what context do you use the above actions? In other words, do you
> execute them when you process a specific request? If yes, which one?
>
> Another question, how do you capture when *55 is pressed? Is dtmf sent
> via sip info request?
>
> Cheers,
> Daniel
>
> -- Daniel-Constantin Mierla http://twitter.com/#!/miconda -
> http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio -
> http://www.asipto.com Kamailio Advanced Training, Sep 28-30, 2015, in
> Berlin - http://asipto.com/u/kat
For now i try to use event_route[dialog:start] - i testing - can
kamailio redirect both sides to external service, and will it work with
event_route[dispatcher:dst-down]. If it will work, i will add SIP INFO
processing for service codes
--
Ярин Андрей
Инженер ООО "И.С.-Телеком"
8(351)7786878 доб 113
8(351)2555724 доб 113
8(351)2555787 доб 113
Hello there,
I'm using carrierroute module to route calls based on prefix, everything
was working until i tried use prefixes that start with +, kamailio core
doesn't allow me use the + on carrierroute prefix, i get the following
message from kamailio logs:
INFO: carrierroute [cr_carrier.c:100]: add_domain_data(): adding domain 1
'main' to carrier 1 'carriers'35(17196) DEBUG: carrierroute
[cr_carrier.c:101]: add_domain_data(): domain position 0 (domain_num=1,
first_empty_domain=0)35(17196) INFO: carrierroute [cr_data.c:414]:
get_domain_data_or_add(): added domain 1 'main' to carrier 1
'carriers'35(17196) INFO: carrierroute [cr_data.c:470]: add_route(): found
carrier and domain, now adding route
35(17196) ERROR: <core> [dtrie.c:130]: dtrie_insert(): cannot insert
non-numerical character
35(17196) ERROR: carrierroute [cr_domain.c:168]: add_route_to_tree():
cannot insert route flags into d-trie
anyone can help in order allow use + in carrierroute prefix.
Best regards
José Seabra
Hello,
dispatcher gives me destination sets with entries in reverse order:
I have installed from Kamailio deb repository packages version 4.3.2+jessie.
# kamailio -V
version: kamailio 4.3.2 (x86_64/linux)
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS,
DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
F_MALLOC, DBG_F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE,
USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: unknown
compiled with gcc 4.9.2
I configured dispatcher:
modparam("dispatcher", "use_default", 1)
modparam("dispatcher", "list_file", "/etc/kamailio/dispatcher.list")
modparam("dispatcher", "flags", 3)
modparam("dispatcher", "dst_avp", "$avp(AVP_DST)")
modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)")
modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)")
modparam("dispatcher", "sock_avp", "$avp(AVP_SOCK)")
modparam("dispatcher", "ds_ping_interval", 5)
modparam("dispatcher", "ds_probing_mode", 1)
I have this dispatcher.list:
1 sip:192.168.1.144:5060 2
1 sip:192.168.1.145:5060 2
1 sip:192.168.1.146:5060 2
2 sip:192.168.1.146:5060 2
2 sip:192.168.1.145:5060 2
So, I expect dispatcher to have:
set 1 first two destinations in distribution via hash on callid, and third
destination as failover (192.168.1.146 <http://192.168.1.146:5060>) .
set 2 all traffic on first destination, and if first fails, all traffic
will failover to second destination (192.168.1.145
<http://192.168.1.146:5060>).
Instead reindex_dests shuffle the sets upside down:
DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/1] <sip:
192.168.1.144:5060>
DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/2] <sip:
192.168.1.145:5060>
DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/3] <sip:
192.168.1.146:5060>
DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [2/1] <sip:
192.168.1.146:5060>
DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [2/2] <sip:
192.168.1.145:5060>
DEBUG: dispatcher [dispatch.c:494]: reindex_dests(): found [2] dest sets
DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 2 sip:
192.168.1.145:5060 2 0 (,0,0)
DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 2 sip:
192.168.1.146:5060 2 0 (,0,0)
DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1 sip:
192.168.1.146:5060 2 0 (,0,0)
DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1 sip:
192.168.1.145:5060 2 0 (,0,0)
DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1 sip:
192.168.1.144:5060 2 0 (,0,0)
DEBUG: dispatcher [dispatcher.c:347]: mod_init(): loaded dispatching list
So, Kamailio give me set 1 and set 2 as per post-reindex_dests, and
failover is 192.168.1.144 for set 1, and 192.168.1.146 for set 2.
Is this the expected behavior?
Am I doing something wrong in configuration?
Thank you all in advance,
-giovanni
Sincerely,
Giovanni Maruzzelli
Cell : +39-347-2665618
Hi list!
We use Kamailio 4.2 for presence BLF with DB_TEXT.
And i want to make cluster with a few Kamailio's presences, to load
balance.
Can you please tell me - is that possible to use same shared DB_TEXT
database with 2 or more Kamailio servers ?
modparam("presence", "subs_db_mode", 3)
modparam ("presence","dburl","/tmp/share/dbtext")
1-st server will handle SUBSCRIBE's and this Subscribe's should be
accessible also from 2-nd server.
Then PUBLISH'es will be sent to both servers in round robin algorithm.
Will Kamailio's work with one shared DB or - i'll got some errors ?
Maybe i'm wrong somewhere ?
Thanks in advance.
Kind regards
Ewgeny
