- sr-users - kamailio.org

BLF on different IPs/domains
by Phil Lavin 12 Feb '16

12 Feb '16

Hi all, A different BLF query to my other one so creating another thread. We've tried to have a BLF client SUBSCRIBE using a secondary IP on Kamailio. It is not sent a NOTIFY, but a client which has done a SUBSCRIBE using the primary IP is. If we route the problematic client such that it connects to the primary IP, it too is sent a NOTIFY. Looking at the query that is done on the database when a call is made to 441164969988 it is as follows: select `callid`,`to_tag`,`from_tag` from `active_watchers` where `presentity_uri`='sip:441164969988@185.28.212.118' AND `event`='dialog' Where 185.28.212.118 is the primary IP. In reality, it should be doing an additional query for anything considered `myself`. i.e. select `callid`,`to_tag`,`from_tag` from `active_watchers` where `presentity_uri`='sip:441164969988@10.20.11.118' AND `event`='dialog' I've been scouring the docs for a way to add additional IPs and/or domains for the purpose of querying active_watchers but I can't see anything relevant. What's the process here? Thanks Phil

2 3

kamailio xmpp gateway configuration issue
by kevin hifx 12 Feb '16

12 Feb '16

Dear friends, I am facing an issue, when trying to configure xmpp gateway between kamailio and ejabbred xmpp server. I have followed the steps mention in this web site: http://www.kamailio.org/docs/modules/4.1.x/modules/xmpp.html The kamailio service is running but in the log file it show that xmpp connection failed. "*Feb 5 11:32:33 sip-xmpp-server /usr/sbin/kamailio[646]: ERROR: xmpp [network.c:122]: net_connect(): connect() failed: Connection refused* " (Both kamailio and ejabbred installed on the same server in local network and have local DNS server) I have added following entries in the kamailio configuration file. I am only mentioning the xmpp section. " ####### Global Parameters ######### alias=sip-xmpp.kevin.org ####### Modules Section ######## #!ifdef WITH_MYSQL loadmodule "db_mysql.so" #!endif loadmodule "mi_fifo.so" loadmodule "kex.so" loadmodule "corex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "ctl.so" loadmodule "cfg_rpc.so" loadmodule "mi_rpc.so" loadmodule "acc.so" # XMPP loadmodule "xmpp.so" # ----------------- setting module-specific parameters --------------- modparam("mi_fifo", "fifo_name", "/var/run/kamailio/kamailio_fifo") modparam("rr", "enable_full_lr", 1) # XMPP modparam("xmpp", "domain_separator", "*") modparam("xmpp", "gateway_domain", "sip-xmpp.kevin.org") modparam("xmpp", "xmpp_domain", "xmpp-sip.kevin.org") modparam("xmpp", "xmpp_host", "xmpp.kevin.org") ###############XMPP # initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); exit; }; ### absorb retransmissions ### if (!t_newtran()) { sl_reply_error(); return; } if (method == "MESSAGE") { log("*** xmpp-handled MESSAGE message.\n"); if (xmpp_send_message()) { t_reply("200", "Accepted"); } else { t_reply("404", "Not found"); } return; } log("*** xmpp: unhandled message type\n"); t_reply("503", "Service unavailable"); return; ############### " could you please help me solve this issue. Thank you kevin

2 5

Only Cassandra, Possible?
by Barış Şekerciler 12 Feb '16

12 Feb '16

Hello, I want to use only Cassandra DB for Kamailio. Is this possible? If it yes, how can I do that? For example, if I replace the DBENGINE as DB_CASSANDRA can I use it like this? Thank you. Regards.

2 3

Kamailio TLS
by Kethzer Docteur 12 Feb '16

12 Feb '16

Im trying to enable Kamailio TLS but the configuration is not running at all when I cahnge it liike this as follow. Kamailio 3.3 ubuntu 12.04 LTS #!define WITH_TLS #!ifdef WITH_TLS enable_tls=yes #!endif #!ifdef WITH_TLS loadmodule "tls.so" #!endif #!ifdef WITH_TLS # ----- tls params ----- modparam("tls", "config", "/etc/kamailio/tls.cfg") #!endif Please help -- Kethzer Docteur

4 3

Negative return codes from functions
by Phil Lavin 11 Feb '16

11 Feb '16

Hi all, Just a sanity check, really. Does Kamailio consider negative response codes to be false? For example, should the following log execute? if (!foo()) { # Returns -2 x_log("Foo is false"); } The reason for asking here is that I'm implementing flood protection using pike, based off the kamailio.cfg that ships with v4.3. The logic is thus: if (!pike_check_req()) { # Do blocking } However pike_check_req only returns -1 or -2 in the case of failure, never 0. The blocking code is, thus, never executed. Changing to explicitly check for != 1 works correctly. Am I missing something here or is the example kamailio.cfg incorrect? Cheers

2 3

Kamailio 4.2.6 crash
by Igor Potjevlesch 11 Feb '16

11 Feb '16

Hello, I have seen couple of crashes since yesterday. I copy/paste the last "bt full": Program terminated with signal 11, Segmentation fault. #0 0x0000000000619694 in fm_extract_free (qm=0x7fcdf8780000, frag=0x7fcdf8a62c78) at mem/f_malloc.c:206 206 *pf= (gdb) bt full #0 0x0000000000619694 in fm_extract_free (qm=0x7fcdf8780000, frag=0x7fcdf8a62c78) at mem/f_malloc.c:206 pf = 0x6576203b50555349 hash = 2097 #1 0x000000000061ad68 in fm_malloc (qm=0x7fcdf8780000, size=1104, file=0x7fce0f081a7b "tm: t_msgbuilder.c", func=0x7fce0f0860a0 "build_local_reparse", line=369) at mem/f_malloc.c:490 f = 0x7fcdf8780b08 frag = 0x7fcdf8a62c78 hash = 156 __FUNCTION__ = "fm_malloc" #2 0x00007fce0f011fa9 in _shm_malloc (size=1099, file=0x7fce0f081a7b "tm: t_msgbuilder.c", function=0x7fce0f0860a0 "build_local_reparse", line=369) at ../../mem/shm_mem.h:208 p = 0x6 #3 0x00007fce0f01920e in build_local_reparse (Trans=0x7fcdf8a5e2f0, branch=0, len=0x7fff00c32fbc, method=0x7fce0f087a25 "ACK", method_len=3, to=0x7fff00c32d90, reason=0x0) at t_msgbuilder.c:369 invite_buf = 0x7fcdf8a62868 "INVITE sip:<CALLED>@goren SIP/2.0\r\nRecord-Route: <sip:A.B.C5.60;lr;did=5b1.3112>\r\nCSeq: 1 INVITE\r\nCall-ID: 3da8-469-1111201513435-JANGO-1-A.B.C_leg2\r\nFrom: <sip:<CALLING>@<HOST_FROM>>;"... invite_buf_end = 0x7fcdf8a62c70 "" cancel_buf = 0x415440 "1\355I\211\321^H\211\342H\203\344\360PTI\307\300\300\363m" s = 0x7fcdf8a62868 "INVITE sip:<CALLED>@goren SIP/2.0\r\nRecord-Route: <sip:A.B.C5.60;lr;did=5b1.3112>\r\nCSeq: 1 INVITE\r\nCall-ID: 3da8-469-1111201513435-JANGO-1-A.B.C_leg2\r\nFrom: <sip:<CALLING>@<HOST_FROM>>;"... s1 = 0x0 d = 0x10703ab0 <Address 0x10703ab0 out of bounds> invite_len = 1032 hf_type = 2540 first_via = 0 to_len = 67 cancel_buf_len = 1099 reason_len = 0 code_len = 0 reas1 = 0x0 reas_last = 0x0 hdr = 0xa7294e __FUNCTION__ = "build_local_reparse" #4 0x00007fce0f02e58b in build_ack (rpl=0x7fce107038b8, trans=0x7fcdf8a5e2f0, branch=0, ret_len=0x7fff00c32fbc) at t_reply.c:439 to = {s = 0xa728f6 "To: <sip:+<CALLED>@A.B.C5.60:5060>;tag=3658827875-928685\r\nContent-Length: 0\r\n\r\n", len = 67} __FUNCTION__ = "build_ack" #5 0x00007fce0f03b3ca in reply_received (p_msg=0x7fce107038b8) at t_reply.c:2253 msg_status = 488 last_uac_status = 100 ack = 0x7fce10588010 "\001" ack_len = 0 branch = 0 reply_status = 274235864 onreply_route = 1 cancel_data = {cancel_bitmap = 0, reason = {cause = 0, u = {text = {s = 0x0, len = 10955086}, e2e_cancel = 0x0, packed_hdrs = {s = 0x0, len = 10955086}}}} uac = 0x7fcdf8a5e458 t = 0x7fcdf8a5e2f0 lack_dst = {send_sock = 0x13a948, to = {s = {sa_family = 10306, sa_data = "\247\000\000\000\000\000(\r\030\000\000\000\000"}, sin = {sin_family = 10306, sin_port = 167, sin_addr = {s_addr = 0}, sin_zero = "(\r\030\000\000\000\000"}, sin6 = {sin6_family = 10306, sin6_port = 167, sin6_flowinfo = 0, sin6_addr = { __in6_u = {__u6_addr8 = "(\r\030\000\000\000\000\000\270|^\020\316\177\000", __u6_addr16 = {3368, 24, 0, 0, 31928, 4190, 32718, 0}, __u6_addr32 = {1576232, 0, 274627768, 32718}}}, sin6_scope_id = 93}}, id = 0, proto = -72 '\270', send_flags = {f = 106 'j', blst_imask = 94 '^'}} backup_user_from = 0x758a50 backup_user_to = 0x415440 backup_domain_from = 0x300c337e0 backup_domain_to = 0x0 backup_uri_from = 0x7fce10703ab0 backup_uri_to = 0x7fff00c330d0 backup_xavps = 0x628478 replies_locked = 0 branch_ret = 0 prev_branch = 275790040 blst_503_timeout = 32718 hf = 0x18e00c33060 onsend_params = {req = 0x7fff00c32f50, rpl = 0x47deb8, param = 0x0, code = 274623280, flags = 32718, branch = 0, t_rbuf = 0xa7294e, dst = 0xa727e1, send_buf = { s = 0x7fff00c33010 "\320\060", <incomplete sequence \303>, len = 6402299}} ctx = {rec_lev = 7715456, run_flags = 0, last_retcode = 7704068, jmp_env = {{__jmpbuf = {232, 140523014225936, 140523014226728, 140523014618240, 29, 0, 140523015781040, 4281408}, __mask_was_saved = 12793824, __saved_mask = {__val = {0, 140733206179856, 6439748, 140733206179616, 140523001001690, 140733206179584, 0, 67108864, 65537912, 1288288, 1570952, 1576232, 8, 94, 0, 1473240891392}}}}} __FUNCTION__ = "reply_received" #6 0x000000000048cc3a in do_forward_reply (msg=0x7fce107038b8, mode=0) at forward.c:783 new_buf = 0x0 dst = {send_sock = 0x0, to = {s = {sa_family = 0, sa_data = '\000' <repeats 13 times>}, sin = {sin_family = 0, sin_port = 0, sin_addr = {s_addr = 0}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 0, sin6_port = 0, sin6_flowinfo = 0, sin6_addr = {__in6_u = { __u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}}, id = 0, proto = 0 '\000', send_flags = {f = 0 '\000', blst_imask = 0 '\000'}} new_len = 1 r = 0 ip = {af = 12792240, len = 32767, u = {addrl = {6466393, 280}, addr32 = {6466393, 0, 280, 0}, addr16 = {43865, 98, 0, 0, 280, 0, 0, 0}, addr = "Y\253b\000\000\000\000\000\030\001\000\000\000\000\000"}} s = 0x410004 "" len = 0 __FUNCTION__ = "do_forward_reply" #7 0x000000000048e27d in forward_reply (msg=0x7fce107038b8) at forward.c:885 ---Type <return> to continue, or q <return> to quit--- No locals. #8 0x0000000000509c9c in receive_msg ( buf=0xa727c0 "SIP/2.0 488 Not Acceptable Here\r\nVia: SIP/2.0/UDP A.B.C5.60;rport=5060;branch=z9hG4bKce12.98a05ce27e0243c4d775920d81e7ce82.0\r \nVia: SIP/2.0/UDP <HOST_FROM>;branch=z9hG4bK.5667f6e0\r\nFrom: <sip:332"..., len=398, rcv_info=0x7fff00c333b0) at receive.c:275 msg = 0x7fce107038b8 ctx = {rec_lev = 10237056, run_flags = 0, last_retcode = 0, jmp_env = {{__jmpbuf = {0, 0, 0, 272136986608, 1812476198913, 0, 272145363728, 272145384176}, __mask_was_saved = 0, __saved_mask = {__val = {140523014366192, 140733206180688, 1, 140522613671152, 272137013029, 50195, 1024, 4307759872, 140522613671152, 140733206180608, 6299381, 140733206180896, 140522613671152, 81, 6299509, 140733206180976}}}}} ret = 12792656 inb = { s = 0xa727c0 "SIP/2.0 488 Not Acceptable Here\r\nVia: SIP/2.0/UDP A.B.C5.60;rport=5060;branch=z9hG4bKce12.98a05ce27e0243c4d775920d81e7ce82.0\r \nVia: SIP/2.0/UDP <HOST_FROM>;branch=z9hG4bK.5667f6e0\r\nFrom: <sip:332"..., len = 398} __FUNCTION__ = "receive_msg" #9 0x0000000000608f02 in udp_rcv_loop () at udp_server.c:521 len = 398 buf = "SIP/2.0 488 Not Acceptable Here\r\nVia: SIP/2.0/UDP A.B.C5.60;rport=5060;branch=z9hG4bKce12.98a05ce27e0243c4d775920d81e7ce82.0\r \nVia: SIP/2.0/UDP <HOST_FROM>;branch=z9hG4bK.5667f6e0\r\nFrom: <sip:332"... tmp = 0x3f60c4067a <Address 0x3f60c4067a out of bounds> from = 0x7fce105e7920 fromlen = 16 ri = {src_ip = {af = 2, len = 4, u = {addrl = {151524537, 0}, addr32 = {151524537, 0, 0, 0}, addr16 = {5305, 2312, 0, 0, 0, 0, 0, 0}, addr = "\271\024\b\t", '\000' <repeats 11 times>}}, dst_ip = {af = 2, len = 4, u = {addrl = {1016190299, 0}, addr32 = {1016190299, 0, 0, 0}, addr16 = {54619, 15505, 0, 0, 0, 0, 0, 0}, addr = "[Õ<", '\000' <repeats 11 times>}}, src_port = 5060, dst_port = 5060, proto_reserved1 = 0, proto_reserved2 = 0, src_su = { s = {sa_family = 2, sa_data = "\023Ä¹\024\b\t\000\000\000\000\000\000\000"}, sin = {sin_family = 2, sin_port = 50195, sin_addr = {s_addr = 151524537}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 151524537, sin6_addr = {__in6_u = { __u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}}, bind_address = 0x7fce105aa2b0, proto = 1 '\001'} __FUNCTION__ = "udp_rcv_loop" #10 0x00000000004a6d9b in main_loop () at main.c:1629 i = 0 pid = 0 si = 0x7fce105aa2b0 si_desc = "udp receiver child=0 sock=A.B.C5.60:5060\000\177\000\000 5\303\000\377\177\000\000\003zN\000\000\000\000\000\016\b\000\000\377\177\00 0\000\260\204x\370\315\177\000\000\000\000\000\020\004\000\000\000\260\204x\ 370\315\177\000\000@TA\000\000\000\000\000\340\067\303\000\001\000\000\000p5 \303\000\377\177\000\000\246zN\000\000\000\000" nrprocs = 8 __FUNCTION__ = "main_loop" #11 0x00000000004acedf in main (argc=7, argv=0x7fff00c337e8) at main.c:2581 cfg_stream = 0xac7010 c = -1 r = 0 tmp = 0x7fff00c34f70 "" tmp_len = 32767 port = 12793534 proto = 0 options = 0x6ff8f8 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ret = -1 seed = 3913881212 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x40d11c p = 0xc2 <Address 0xc2 out of bounds> __FUNCTION__ = "main" Regards, Igor.

2 15

Reg: REGISTER request don't have username in request line
by sainath.ellendula＠wipro.com 11 Feb '16

11 Feb '16

Hi Team, Working on Kamailio setup with IMS components(P-CSCF, I-CSCF, S-CSCF). Assigned IP's: hss/server-10.0.0.9 P-CSCF-10.0.0.10 I-CSCF-10.0.0.11 S-CSCF-10.0.0.12 Here tried to send an REGISTER request from Boghe IMS client, the register request should go from P-CSCF to I-CSCF, here P-CSCF - I-CSCF communication is not happening but I could able ping. One more thing observed from logs here is REGISTER request don't have username (username is not there in request line), Execution log: 0(1338) DEBUG: ims_usrloc_pcscf [usrloc.c:106]: get_alias_host_from_contact(): no alias param Please find attachment of Zone file, SCSCF.xml, Diameter.xml, ICSCF.xml and tcpdump. Any changes/suggestions would be very helpful. Regards, Sainath The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

2 1

Terminate dialogs on [websocket:closed]
by mayamatakeshi 11 Feb '16

11 Feb '16

Hello, I am using module websocket and it works very well. However I would like to send BYE to the other end if event [websocket:closed] happens. >From the docs I can see websocket module itself doesn't provide for this. I was considering doing something like this: - use module htable to match $si:$sp to dialogs - use event_route[dialog:start] to insert dialog info to my htable under $si:$sp of Websocket side of the call - use event_route[dialog:end] to remove dialog info from htable - use event_route[websocket:closed] to iterate over entries in the htable under key $si:$sp and call dlg_get() and dlg_bye(). Obs: in the above, there is a risk of losing some dialogs as insertion in htable cannot be done atomically, but I am fine with it as it it not expected to happen as WebSocket users would only infrequently generate simultaneous calls. However before going with this, I would like to ask for other possible approaches. Regards, Takeshi

2 6

Route for BYE requests
by alexandre.anconetti＠orange.com 11 Feb '16

11 Feb '16

Hello, I would like some advice about a situation i have encountered recently. I'm using Kamailio 4.3.4 as a "proxy" : I have a media server, and to reach this server all the requests have to pass through my Kamailio server. The Kamailio server does not have to handle authentification or registration, all of that stuff is done on the media server. To do that I'm using the following route : route[REDIRECT] { if($rU == "" ) { $ru = ("sip:1.2.3.4:xxxx"); } else { $ru = ("sip:" + $rU + "@1.2.3.4:xxxx"); } } 1.2.3.4 is my media server's address. I have 2 users : an "internal" one registered on the media server, and an "external" one which is a random caller. It works fine for EXT -> Kamailio -> Media server requests but when I try to hang up with my internal user, the "BYE" request uses the following path : Internal user -> Media server -> Kamailio -> Media server instead of : Internal user -> Media server -> Kamailio -> External user. Obviously it is because of the REDIRECT route which send back the "BYE" request to the media server, when it should sends that request to the external user. So, how should I modify that route to do what I want ? Maybe should I create a second route ? Any answer will be appreciated :) Best regards, Alexandre _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

2 1

kamctl ul add...<path>
by kssyrr 10 Feb '16

10 Feb '16

1 0

RTCWeb Breaker question
by SamyGo 10 Feb '16

10 Feb '16

Hi All, reference to this link: https://www.kamailio.org/wiki/devel/rtcweb_breaker#scenarios I want to know if the module to communicate with RTCWeb Breaker is available or it was just a proposal and no more under consideration. I have webrtc clients registered to Kamailio but due to lack of (scalable/efficient) transcoding capabilities they can not make video calls to Video IP-Phones. I tried using webrtc2sip from doubango telecom and it actually enabled me to achieve the goal, the problem with that case is webrtc2sip is working with sipml5 client and there is not a big list of WebRTC clients that work with it. If I can achieve the referred rtc_web_breaker architecture then I believe a lot of webRTC clients will be able to integrate with my setup. Thanks, Regards, Sammy

2 4

Kamailio SST and Dialog module workings
by Jason Penton 10 Feb '16

10 Feb '16

Hi Kamailio users and Devs. I am interested to know if any of you are using SST module with DIALOG module and sharing the timeout avp between the two - expecting the call to be torn down if no in-dialog requests are processed. If you are using it, is it working as you expect? To me it seems that the timers in the dialog module will never be updated by any in-dialog requests. I just wanted to check before I start looking at fixing... perhaps I am missing something. Cheers Jason

2 2

Permission module about from_pattern
by Yasin CANER 10 Feb '16

10 Feb '16

2 3

regular expression for fromuser
by Yasin CANER 10 Feb '16

10 Feb '16

1 0

regular expression for from_pattern
by Yasin CANER 10 Feb '16

10 Feb '16

1 0

info: dialog_ng renamed to ims_dialog
by Daniel-Constantin Mierla 09 Feb '16

09 Feb '16

Hello, based on a previous discussion on mailing lists, I just renamed the dialog_ng to ims_dialog in order to reflect better its purpose nowadays (use together with the other ims modules) and avoid confusion that it is something that includes the features of dialog module and some new stuff. Functions and params are not renamed, being anyhow overlapping a lot with dialog module, but they are not intended to be used at the same time. Perhaps some examples still need to be updated (contributions are welcome here if you identify such places). If any other issue is discovered to the ims modules, write here to get it fixed. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

1 0

Re: [SR-Users] Kamailio IMS deployment
by Franz Edler 09 Feb '16

09 Feb '16

The REGISTER request is OK. There is no username included in REGISTER request.Regarding the mismatch: do you use NATURAL on your platform? Next step should be a tracefile (tcpdump) and later a debug-log from the node which shows the problem. Von Samsung-Tablet gesendet-------- Ursprüngliche Nachricht --------Von: sainath.ellendula(a)wipro.com Datum: 2016.02.09 08:05 (GMT+01:00) An: franz.edler(a)technikum-wien.at Cc: basitstar(a)hotmail.com, sr-users(a)lists.sip-router.org Betreff: RE: Re:[SR-Users] Kamailio IMS deployment Hi Franz, Please find ping status and seems good. root@server:~# ping -c 1 hss.net1.test PING hss.net1.test (10.0.0.9) 56(84) bytes of data. 64 bytes from server.net1.test (10.0.0.9): icmp_seq=1 ttl=64 time=0.017 ms --- hss.net1.test ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.017/0.017/0.017/0.000 ms root@server:~# ping -c 1 pcscf.net1.test PING pcscf.net1.test (10.0.0.10) 56(84) bytes of data. 64 bytes from server.net1.test (10.0.0.10): icmp_seq=1 ttl=64 time=0.020 ms --- pcscf.net1.test ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.020/0.020/0.020/0.000 ms root@server:~# ping -c 1 icscf.net1.test PING icscf.net1.test (10.0.0.11) 56(84) bytes of data. 64 bytes from server.net1.test (10.0.0.11): icmp_seq=1 ttl=64 time=0.018 ms --- icscf.net1.test ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.018/0.018/0.018/0.000 ms root@server:~# ping -c 1 scscf.net1.test PING scscf.net1.test (10.0.0.12) 56(84) bytes of data. 64 bytes from server.net1.test (10.0.0.12): icmp_seq=1 ttl=64 time=0.017 ms --- scscf.net1.test ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.017/0.017/0.017/0.000 ms root@server:~# Seems Some progress happened: Tried register using Boghe IMS client and observed few errors: 0(1445) INFO: <script>: [REGISTER] from [sip:alice@net1.test] to [sip:alice@net1.test] 0(1445) ERROR: <script>: REGISTER (sip:alice@net1.test (10.0.0.8:55280) to sip:alice@net1.test, 2006cdca-0076-bacb-5010-bffa714b3cdb) 0(1445) DEBUG: <core> [parser/msg_parser.c:153]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <7994> <REGISTER> 0(1445) DEBUG: <core> [parser/msg_parser.c:187]: get_hdr_field(): DEBUG: get_hdr_body : content_length=0 0(1445) DEBUG: maxfwd [mf_funcs.c:85]: is_maxfwd_present(): value = 70 0(1445) DEBUG: <core> [parser/msg_parser.c:89]: get_hdr_field(): found end of header 0(1445) DEBUG: sanity [mod_sanity.c:248]: w_sanity_check(): sanity checks result: 1 0(1445) DEBUG: siputils [checks.c:97]: has_totag(): no totag 0(1445) DEBUG: <core> [select.c:412]: run_select(): Calling SELECT 0x7fb548dd2400 0(1445) DEBUG: tm [t_lookup.c:1011]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=1 T start=0xffffffffffffffff 0(1445) DEBUG: tm [t_lookup.c:466]: t_lookup_request(): t_lookup_request: start searching: hash=65064, isACK=0 0(1445) DEBUG: tm [t_lookup.c:424]: matching_3261(): DEBUG: RFC3261 transaction matching failed 0(1445) DEBUG: tm [t_lookup.c:648]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found 0(1445) DEBUG: tm [t_lookup.c:1080]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=2 T end=(nil) 0(1445) DEBUG: sl [sl.c:280]: send_reply(): reply in stateless mode (sl) 0(1445) DEBUG: siputils [checks.c:97]: has_totag(): no totag 0(1445) DEBUG: tm [t_lookup.c:1011]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=2 T start=(nil) 0(1445) DEBUG: tm [t_lookup.c:1086]: t_check_msg(): DEBUG: t_check_msg: T previously sought and not found 0(1445) DEBUG: ims_registrar_pcscf [save.c:273]: save_pending(): contact requesting to expire in 600000 seconds 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:106]: get_alias_host_from_contact(): no alias param 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:155]: get_hash_slot(): using host for hash [10.0.0.8] 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:159]: get_hash_slot(): Returning hash slot: [167] 0(1445) DEBUG: ims_usrloc_pcscf [udomain.c:465]: get_pcontact(): Searching for contact in P-CSCF usrloc [sip:alice@10.0.0.8:55280;transport=udp] 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:106]: get_alias_host_from_contact(): no alias param 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:183]: get_aor_hash(): using host for hash [10.0.0.8] 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:187]: get_aor_hash(): Returning hash slot: [1662767783] 0(1445) DEBUG: ims_usrloc_pcscf [udomain.c:483]: get_pcontact(): Comparing needle user@host:port [alice@10.0.0.8:55280] and contact_user@contact_host:port [alice@10.0.0.8:51219] 0(1445) DEBUG: ims_usrloc_pcscf [udomain.c:494]: get_pcontact(): Searching for [sip:alice@10.0.0.8:55280;transport=udp] and comparing to [sip:alice@10.0.0.8:51219;transport=udp] 0(1445) DEBUG: ims_usrloc_pcscf [udomain.c:553]: get_pcontact(): Port don't match: 51219 (contact) 51219 (received) != 55280! 0(1445) DEBUG: ims_registrar_pcscf [save.c:310]: save_pending(): Adding pending pcontact: <sip:alice@10.0.0.8:55280;transport=udp> 0(1445) DEBUG: ims_usrloc_pcscf [pcontact.c:132]: new_pcontact(): New contact [<sip:alice@10.0.0.8:55280;transport=udp>] with 0 associated IMPUs in state: [registration pending] 0(1445) DEBUG: ims_registrar_pcscf [save.c:314]: save_pending(): registering for UL callback 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:106]: get_alias_host_from_contact(): no alias param Please guide me for any more changes has to be done, As observed in Wireshark(Register request from 10.0.0.8(host)-PCSCF as REGISTER sip:net1.test SIP/2.0). I think the register request should sent as REGISTER sip:alice@net1.test SIP/2.0 Thanks in advance!! Regards, Sainath From: Franz Edler [mailto:franz.edler@technikum-wien.at] Sent: Tuesday, February 9, 2016 3:00 AM To: Sainath Ellendula (NEP) <sainath.ellendula(a)wipro.com> Cc: basitstar(a)hotmail.com; sr-users(a)lists.sip-router.org Subject: RE: Re:[SR-Users] Kamailio IMS deployment Sainath, what was the result for ping on - icsct.net1.test - scscf.net1.test - hss.net1.test to increase debug level you have to modify the corresponding cfg-file, e.g. kamailio-icscf.cfg in line 35: debug=2 Just increase to debug=3 and then start the process again. BR Franz The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

1 0

GCC version in use
by Daniel-Constantin Mierla 09 Feb '16

09 Feb '16

Hello, looking a bit over our makefiles, I am thinking of simplifying some parts related to compiler optimizations, as I noticed some of them are for gcc 2.x. So I would like to see if people are still using old OSes and/or old GCC versions. In other words, if you use old or some dedicated systems and plan to deploy most recent Kamailio versions, reply here with the gcc version in use, particularly interested to see the use of gcc 2.x or 3.x. The idea is not to remove the support for it completely, but to simply and don't try to find all tunings for old versions, but go more with the default gcc options. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

3 7

Re: [SR-Users] Kamailio IMS deployment
by sainath.ellendula＠wipro.com 09 Feb '16

09 Feb '16

Hi Franz, Thank you so much for your response. As suggested modified changes and don't observe connection refused error. After modification few more errors observed. Detailed errors as below. 10.0.0.9 /catalina-optional.jar:lib/catalina.jar:lib/c3p0-0.9.1.jar:lib/base64.jar:lib/asm.jar:lib/asm-attrs.jar:lib/antlr-2.7.6.jar::log4j.properties:.. 2016-02-01 12:09:28,371 INFO de.fhg.fokus.hss.main.TomcatServer - startTomcat Tomcat-Server is started. 2016-02-01 12:09:29,301 WARN org.apache.catalina.connector.MapperListener - registerEngine Unknown default host: 10.0.0.9 2016-02-01 12:09:30,294 INFO de.fhg.fokus.hss.web.servlet.ResponseFilter - init Response Filter Initialisation! 2016-02-01 12:09:31,251 INFO de.fhg.fokus.hss.main.TomcatServer - startTomcat WebConsole of FHoSS was started ! 2016-02-01 12:09:34,813 WARN org.hibernate.impl.SessionFactoryObjectFactory - addInstance InitialContext did not implement EventContext 2016-02-01 12:09:34,847 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - <init> Bean style constructor called, don't forget to configure! 2016-02-01 12:09:34,851 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure FQDN: hss.net1.test 2016-02-01 12:09:34,852 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure Realm: net1.test 2016-02-01 12:09:34,853 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure Vendor_ID : 10415 2016-02-01 12:09:34,854 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure Product Name: JavaDiameterPeer 2016-02-01 12:09:34,854 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure AcceptUnknwonPeers: true 2016-02-01 12:09:34,855 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure DropUnknownOnDisconnect: true 2016-02-01 12:09:34,864 INFO de.fhg.fokus.hss.main.HSSContainer - waitForExit Type "exit" to stop FHoSS! 2016-02-01 12:09:34,873 ERROR de.fhg.fokus.diameter.DiameterPeer.peer.StateMachine - I_Snd_Conn_Req StateMachine: Peer icscf.net1.test:3869 not responding to connection attempt 2016-02-01 12:09:34,876 ERROR de.fhg.fokus.diameter.DiameterPeer.peer.StateMachine - I_Snd_Conn_Req StateMachine: Peer scscf.net1.test:3870 not responding to connection attempt 10.0.0.10 root@server:~# kamailio -f /usr/local/etc/kamailio/kamailio-pcscf.cfg loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(1856) INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: pcscf.net1.test [10.0.0.10]:4060 Aliases: *: pcscf.net1.test:* WARNING: no fork mode 0(1856) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(1856) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available 0(1856) INFO: ims_usrloc_pcscf [hslot.c:62]: ul_init_locks(): locks array size 512 0(1856) INFO: <core> [udp_server.c:150]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1856) INFO: <core> [udp_server.c:200]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(1856) WARNING: ims_usrloc_pcscf [usrloc_db.c:59]: connect_db(): DB connection already open... continuing 0(1856) INFO: <script>: [REGISTER] from [sip:alice@net1.test] to [sip:alice@net1.test] 0(1856) ERROR: <script>: REGISTER (sip:alice@net1.test (10.0.0.8:55859) to sip:alice@net1.test, aaeacddd-376e-4a63-5745-2757d1b9a29d) 10.0.0.11 9(1870) WARNING: cdp [tcp_accept.c:123]: create_socket(): create_socket(): Trying to open/bind/listen on 10.0.0.11 port 3869 9(1870) WARNING: cdp [tcp_accept.c:148]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.0.0.11 port 3869 9(1870) INFO: cdp [acceptor.c:96]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 10(1871) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(1871) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(1871) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(1871) INFO: cdp [receiver.c:932]: peer_connect(): peer_connect(): Peer hss.net1.test:3868 connected 8(1869) ERROR: cdp [peerstatemachine.c:635]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket 10(1871) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 10(1871) WARNING: cdp [peermanager.c:315]: peer_timer(): Inactivity on peer [hss.net1.test], sending DWR... - if we don't get a reply, the peer will be closed 10.0.0.12 9(1883) WARNING: cdp [tcp_accept.c:123]: create_socket(): create_socket(): Trying to open/bind/listen on 10.0.0.12 port 3870 9(1883) WARNING: cdp [tcp_accept.c:148]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.0.0.12 port 3870 9(1883) INFO: cdp [acceptor.c:96]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 7(1881) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... 7(1881) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [] Receiver process starting up... 10(1884) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(1884) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(1884) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(1884) INFO: cdp [receiver.c:932]: peer_connect(): peer_connect(): Peer hss.net1.test:3868 connected 8(1882) ERROR: cdp [peerstatemachine.c:635]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket 10(1884) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 10(1884) WARNING: cdp [peermanager.c:315]: peer_timer(): Inactivity on peer [hss.net1.test], sending DWR... - if we don't get a reply, the peer will be closed 10(1884) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 Could you please guide me here. Any suggestions would be very helpful. Thanks in advance!! Regards, Sainath -----Original Message----- From: Franz Edler [mailto:franz.edler@technikum-wien.at] Sent: Saturday, January 30, 2016 1:27 PM To: Sainath Ellendula (WT01 - NEP) <sainath.ellendula(a)wipro.com>; basitstar(a)hotmail.com; sr-users(a)lists.sip-router.org Subject: RE: [SR-Users] Kamailio IMS deployment Hi, > As suggested, modified the changes in icscf.xml and scscf.xml files, PFA > modified files. > > Still getting few errors .... Now it seems to be clear to me where the problem might come from: I have restricted access to mysql server to address 10.0.0.9 only. You have to change the bind-address statement in /etc/mysql.cnf accordingly. See: http://dev.mysql.com/doc/refman/5.7/en/server-options.html#option_mysqld_bi… Change the address to "*" or to 0.0.0.0. BR Franz _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

2 6

No contact info(0 bindings) in 200-register
by sgy 08 Feb '16

08 Feb '16

Hi Members, I notice an issue: the client register to kamailio server and could receive 200-register message, but no contact infomation(shows 0 bindings) returns in the message(200-register). I checked contact exist in register message and client shows register successfully. When I run command "kamctl online", the client is not online. Could you met with this issue? Expected to your help, thank you very much. Register: REGISTER sip:12.2.1.197 SIP/2.0 Via: SIP/2.0/UDP 12.2.1.180:5060;rport;branch=z9hG4bKPjWScZ6O7MbSbtauTPHcKpjzsHb5U6wxGP Route: <sip:12.2.1.197;lr> Max-Forwards: 70 From: "2016" <sip:2016@12.2.1.197>;tag=jqx1XzTgoS-XKh-S3LyrYmjrCBSqJZ48 To: "2016" <sip:2016@12.2.1.197> Call-ID: AiD6dDi6YOK4.ArBsMpse2MQEoh4dBmP CSeq: 12358 REGISTER User-Agent: A-client Contact: "2016" <sip:2016@12.2.1.180:5060;ob>;+sip.instance="<urn:uuid:00000000-0000-1000-8000-000000020805>";reg-id=0 Supported: geolocation, gruu, path, outbound, answermode, tdialog, replaces, timer, precondition, norefersub Expires: 3600 Allow: INVITE, ACK, BYE, CANCEL, UPDATE, INFO, NOTIFY, REFER, MESSAGE, OPTIONS Authorization: Digest username="2016", realm="12.2.1.197", nonce="Vq8AMFau/wTtkI9/v58I86rqhbvPhSTW", uri="sip:12.2.1.197", response="aebb4a141197b2200bdfc5dce008d9ac" Content-Length: 0 200-Register: //No contact infomation rE/(a)SIP/2.0 200 OK Via: SIP/2.0/UDP 12.2.1.180:5060;rport=5060;branch=z9hG4bKPjpBm-dzHb.9vJY19Ccy9Yz8sx7jigkAM1;received=12.2.1.180 From: "2015" <sip:2015@12.2.1.197>;tag=tVTyij9jGH8wprKa2olsevAockWFs8k0 To: "2015" <sip:2015@12.2.1.197>;tag=090f6aa955fd574e08bca845127013d9.2885 Call-ID: fIQWmPXYtdkT94lzPscrMjzj3R5san9g CSeq: 58932 REGISTER Server: kamailio (4.2.0 (x86_64/linux)) Content-Length: 0 Best Regards, Shengy

2 9

Re: [SR-Users] Replace User Agent
by Daniel-Constantin Mierla 08 Feb '16

08 Feb '16

Hello, for changing the user-agent header you can use: remove_hf("User-Agent"); append_hf("User-Agent: abc\r\n"); Cheers, Daniel On 02/02/16 11:20, Steven Maddox wrote: > Hi, > > I've brought up this topic up before (here and on IRC) and I feel like > I'm getting closer but still a bit stuck. Since it takes a while to > explain the idea (and get past any confusion!) I've summarized it in a > diagram for easier understanding. > > At work my employers have decided to use this god awful hosted PBX > which is picky about which phones can register and checks their user > agent, the hosted PBX is marked on the diagram as the purple blob. > > > > The progress I've made since last time is getting Kamailio 4.2.4 on > that little white device, the *only* purpose of that device is to > change the user agent - nothing more... since it has lots of ports it > could have lots of "Unapproved" phones directly connected to it. > > Someone gave me a link to this as a starting point... > https://blog.voipxswitch.com/2015/03/27/kamailio-basic-sip-proxy-all-reques… > > However I'm not sure what portions of the default kamailio.cfg should > be kept to use this, additionally it doesn't include anything about > changing user agents. > > The normal configuration of an "Approved" phone is *like*... > > username="441234111999" > password="rAnD0Mp4s5" > auth_user="jsmith" > domain="company.co.uk" > registrar/proxy="uk.ic.56hnt.hlpcom.co.uk" > > In terms of the configuration of an "Unapproved" phone I can either... > > 1) Put in exactly the same as above (as though it isn't intending to > contact Kamailio)... but since the phone is directly connected to the > Kamailio device - perhaps Kamailio could watch SIP traffic coming in > on eth1 (even if it isn't addressed to it), alter the user agent and > pass it out through eth0 ? I'm not sure even Kamailio is capable of > this - but it'd be cool if possible. > > 2) Put in exactly the same as above however just change the > registrar/proxy to be the IP of the Kamailio device... Kamailio can > then keep all other configuration the same as it passes it through - > just change the user agent. > > Any thoughts? > > n.b. > 1) Yes changing the user agent definitely does allow you connect, it's > not just a guess - tested it with Asterisk. > 2) No I don't think the hosted PBX supports path extensions - I'd > rather not rely on it supporting undocumented stuff anyway. > > -- > Steven Maddox > > > _______________________________________________ > 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 -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

1 0

Users in different domains and multiple domains
by Barış Şekerciler 08 Feb '16

08 Feb '16

Hello everyone! I'm wondering something about Kamailio. Here is the idea: Such and example, I want to give base system which depends on Kamailio to 3 companies in 1 server. So I have 1 Kamailio Server and 4 or 5 Freeswitch server. Thus, I have to set a domain for each company, so total is I need 3 domains. For example a, b, c are users. But they should in the different domains for know which is which. In a word, it should seems like this: a(a)subdomain.domain.com b(a)subdomain.domain.com c(a)subdomain.domain.com a(a)subdomain2.domain.com b(a)subdomain2.domain.com c(a)subdomain2.domain.com or a(a)subdomain.domain2.com b(a)subdomain.domain2.com c(a)subdomain.domain2.com etc... So where can I do this? Remember, Kamailio should in the 1 server and all of domains and users should in this server (I will use Postgres) For more details, you can write. Thank you. Regards.

2 5

Error or Bug: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found
by Sid Mason 07 Feb '16

07 Feb '16

Hi, Below is the SIP record captured using NGREP: http://pastebin.com/hUqP56fw Regards

2 1

Error or Bug: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found
by Sid Mason 07 Feb '16

07 Feb '16

Hi, Below is the SIP record captured using NGREP Regards U 2016/02/07 20:20:06.054910 90.X.X.68:25189 -> 10.1.4.23:5060 INVITE sip:0031651022945@voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-17160a2503261a6b-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:9005@90.X.X.68:25189>. To: "003165656565"<sip:003165656565@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 1 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Content-Type: application/sdp. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 230. . v=0. o=- 1 2 IN IP4 10.1.10.11. s=CounterPath eyeBeam 1.5. c=IN IP4 10.1.10.11. t=0 0. m=audio 52282 RTP/AVP 0 8 101. a=alt:1 1 : h0yu+bYK 4sdGkNzr 10.1.10.11 52282. a=fmtp:101 0-15. a=rtpmap:101 telephone-event/8000. a=sendrecv. U 2016/02/07 20:20:06.056642 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 407 Proxy Authentication Required. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-17160a2503261a6b-1---d8754z-;rport=25189;received=90.X.X.68. To: "003165656565"<sip:003165656565@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.8324. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 1 INVITE. Proxy-Authenticate: Digest realm="voip.system.com", nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme". Content-Length: 0. . U 2016/02/07 20:20:06.059536 90.X.X.68:25189 -> 10.1.4.23:5060 ACK sip:003165656565@voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-17160a2503261a6b-1---d8754z-;rport. To: "003165656565"<sip:003165656565@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.8324. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 1 ACK. Content-Length: 0. . U 2016/02/07 20:20:06.061317 90.X.X.68:25189 -> 10.1.4.23:5060 INVITE sip:003165656565@voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:9005@90.X.X.68:25189>. To: "003165656565"<sip:003165656565@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Content-Type: application/sdp. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme",uri=" sip:003165656565@voip.system.com ",response="3473bd0cf6c9af95690edc953fd7346d",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 230. . v=0. o=- 1 2 IN IP4 10.1.10.11. s=CounterPath eyeBeam 1.5. c=IN IP4 10.1.10.11. t=0 0. m=audio 52282 RTP/AVP 0 8 101. a=alt:1 1 : h0yu+bYK 4sdGkNzr 10.1.10.11 52282. a=fmtp:101 0-15. a=rtpmap:101 telephone-event/8000. a=sendrecv. U 2016/02/07 20:20:06.065526 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189;received=90.X.X.68. To: "003165656565"<sip:003165656565@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Content-Length: 0. . U 2016/02/07 20:20:06.065940 10.1.4.23:5060 -> 103.XXX.XXX.22:5060 INVITE sip:003165656565@voip.system.com SIP/2.0. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKddff.66b1d70306f62152bc5c1a7a1b68eb82.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Max-Forwards: 69. Contact: <sip:9005@90.X.X.68:25189;alias=90.X.X.68~25189~1>. To: "003165656565"<sip:003165656565@voip.system.com>. From: <sip:voip.system.com:5060>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Content-Type: application/sdp. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 230. Remote-Party-ID: "9005" <sip:9005@103.XXX.XXX.23 >;party=calling;privacy=off;screen=no. v=0. o=- 1 2 IN IP4 10.1.10.11. s=CounterPath eyeBeam 1.5. c=IN IP4 10.1.10.11. t=0 0. m=audio 52282 RTP/AVP 0 8 101. a=alt:1 1 : h0yu+bYK 4sdGkNzr 10.1.10.11 52282. a=fmtp:101 0-15. a=rtpmap:101 telephone-event/8000. a=sendrecv. U 2016/02/07 20:20:06.090448 103.XXX.XXX.22:5060 -> 10.1.4.23:5060 SIP/2.0 100 Trying. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKddff.66b1d70306f62152bc5c1a7a1b68eb82.0;received=103.XXX.XXX.23. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: <sip:voip.system.com:5060>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Length: 0. . U 2016/02/07 20:20:10.883489 103.XXX.XXX.22:5060 -> 10.1.4.23:5060 SIP/2.0 180 Ringing. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKddff.66b1d70306f62152bc5c1a7a1b68eb82.0;received=103.XXX.XXX.23. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: <sip:voip.system.com:5060>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Length: 0. . U 2016/02/07 20:20:10.883574 103.XXX.XXX.22:5060 -> 10.1.4.23:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKddff.66b1d70306f62152bc5c1a7a1b68eb82.0;received=103.XXX.XXX.23. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: <sip:voip.system.com:5060>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Type: application/sdp. Content-Length: 327. . v=0. o=root 1558510539 1558510539 IN IP4 103.XXX.XXX.22. s=Useragent. c=IN IP4 103.XXX.XXX.22. t=0 0. m=audio 59130 RTP/AVP 9 18 0 8 101. a=rtpmap:9 G722/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. a=sendrecv. U 2016/02/07 20:20:10.884941 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 180 Ringing. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Length: 0. . U 2016/02/07 20:20:10.885646 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Type: application/sdp. Content-Length: 327. . v=0. o=root 1558510539 1558510539 IN IP4 103.XXX.XXX.22. s=Useragent. c=IN IP4 103.XXX.XXX.22. t=0 0. m=audio 59130 RTP/AVP 9 18 0 8 101. a=rtpmap:9 G722/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. a=sendrecv. U 2016/02/07 20:20:20.596774 90.X.X.68:25189 -> 10.1.4.23:5060 CANCEL sip:003165656565@voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport. To: "003165656565"<sip:003165656565@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 CANCEL. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme",uri=" sip:003165656565@voip.system.com ",response="b739a517585b9bdcd997b3e3322c3bad",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 0. . U 2016/02/07 20:20:20.599102 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 500 cancel error. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189;received=90.X.X.68. To: "003165656565"<sip:003165656565@voip.system.com >;tag=79597765d0ff0775a3cc048295d6500c-3fc1. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 CANCEL. Content-Length: 0. . U 2016/02/07 20:20:23.407575 90.X.X.68:25189 -> 10.1.4.23:5060 REGISTER sip:voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-7176c672f55aba4c-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:9005@90.X.X.68:25189;rinstance=5a52b9593b8bd582>. To: "+3165656565"<sip:9005@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=4f0c6043. Call-ID: MzliN2E4ZTRkYjViZWFiN2Y4YjRjZDExMjc4ODg0NWQ.. CSeq: 7 REGISTER. Expires: 3600. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: eyeBeam release 1102q stamp 51814. Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc1l1a3NGs8NrsUIZb+Kyau9v9Q9jUn",uri="sip:voip.system.com ",response="602901348ea359e385f99c5d4261ea5c",algorithm=MD5. Content-Length: 0. . U 2016/02/07 20:20:23.409286 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-7176c672f55aba4c-1---d8754z-;rport=25189;received=90.X.X.68. To: "+3165656565"<sip:9005@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.fab9. From: "+3165656565"<sip:9005@voip.system.com>;tag=4f0c6043. Call-ID: MzliN2E4ZTRkYjViZWFiN2Y4YjRjZDExMjc4ODg0NWQ.. CSeq: 7 REGISTER. WWW-Authenticate: Digest realm="voip.system.com", nonce="Vrc3s1a3Noe7UjBYG6PYJGPaghIpTBqa". Content-Length: 0. . U 2016/02/07 20:20:23.515175 90.X.X.68:25189 -> 10.1.4.23:5060 REGISTER sip:voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-9a36b0060c000e77-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:9005@90.X.X.68:25189;rinstance=5a52b9593b8bd582>. To: "+3165656565"<sip:9005@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=4f0c6043. Call-ID: MzliN2E4ZTRkYjViZWFiN2Y4YjRjZDExMjc4ODg0NWQ.. CSeq: 8 REGISTER. Expires: 3600. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: eyeBeam release 1102q stamp 51814. Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3s1a3Noe7UjBYG6PYJGPaghIpTBqa",uri="sip:voip.system.com ",response="e7d27803d159526ee124e64e59bcc7d0",algorithm=MD5. Content-Length: 0. . U 2016/02/07 20:20:23.520290 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 200 OK. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-9a36b0060c000e77-1---d8754z-;rport=25189;received=90.X.X.68. To: "+3165656565"<sip:9005@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.351d. From: "+3165656565"<sip:9005@voip.system.com>;tag=4f0c6043. Call-ID: MzliN2E4ZTRkYjViZWFiN2Y4YjRjZDExMjc4ODg0NWQ.. CSeq: 8 REGISTER. Contact: <sip:9005@90.X.X.68 :25189;rinstance=5a52b9593b8bd582>;expires=600;received="sip:90.X.X.68:25189". Content-Length: 0. . U 2016/02/07 20:20:23.520546 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-9a36b0060c000e77-1---d8754z-;rport=25189;received=90.X.X.68. To: "+3165656565"<sip:9005@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.351d. From: "+3165656565"<sip:9005@voip.system.com>;tag=4f0c6043. Call-ID: MzliN2E4ZTRkYjViZWFiN2Y4YjRjZDExMjc4ODg0NWQ.. CSeq: 8 REGISTER. Contact: <sip:9005@90.X.X.68 :25189;rinstance=5a52b9593b8bd582>;expires=600;received="sip:90.X.X.68:25189". WWW-Authenticate: Digest realm="voip.gpnsystem.com", nonce="Vrc3s1a3Noe7UjBYG6PYJGPaghIpTBqa", qop="auth". Content-Length: 0. . U 2016/02/07 20:20:24.426155 90.X.X.68:25189 -> 10.1.4.23:5060 SUBSCRIBE sip:9005@voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-3f31377b941acf34-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:9005@90.X.X.68:25189>. To: "+3165656565"<sip:9005@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=f1000570. Call-ID: NzJiNTM5YjlhOTIyYjFhNWRkNTkzOWQ3MzViNGJiYTg.. CSeq: 1 SUBSCRIBE. Expires: 300. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: eyeBeam release 1102q stamp 51814. Event: message-summary. Content-Length: 0. . U 2016/02/07 20:20:24.428409 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 407 Proxy Authentication Required. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-3f31377b941acf34-1---d8754z-;rport=25189;received=90.X.X.68. To: "+3165656565"<sip:9005@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.351d. From: "+3165656565"<sip:9005@voip.system.com>;tag=f1000570. Call-ID: NzJiNTM5YjlhOTIyYjFhNWRkNTkzOWQ3MzViNGJiYTg.. CSeq: 1 SUBSCRIBE. Proxy-Authenticate: Digest realm="voip.system.com", nonce="Vrc3tFa3NoiYOjmQMojfuh3ttECnmpZW". Content-Length: 0. . U 2016/02/07 20:20:24.534158 90.X.X.68:25189 -> 10.1.4.23:5060 SUBSCRIBE sip:9005@voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-4b7b5d2b2726d57d-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:9005@90.X.X.68:25189>. To: "+3165656565"<sip:9005@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=f1000570. Call-ID: NzJiNTM5YjlhOTIyYjFhNWRkNTkzOWQ3MzViNGJiYTg.. CSeq: 2 SUBSCRIBE. Expires: 300. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3tFa3NoiYOjmQMojfuh3ttECnmpZW",uri="sip:9005@voip.system.com ",response="2d1f53e6973bf2eb878f679add8bebc8",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Event: message-summary. Content-Length: 0. . U 2016/02/07 20:20:24.537592 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 404 No voicemail service. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-4b7b5d2b2726d57d-1---d8754z-;rport=25189;received=90.X.X.68. To: "+3165656565"<sip:9005@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.2dea. From: "+3165656565"<sip:9005@voip.system.com>;tag=f1000570. Call-ID: NzJiNTM5YjlhOTIyYjFhNWRkNTkzOWQ3MzViNGJiYTg.. CSeq: 2 SUBSCRIBE. Content-Length: 0. . U 2016/02/07 20:20:25.358979 10.1.4.23:5060 -> 103.XXX.XXX.22:5060 OPTIONS sip:103.XXX.XXX.22:5060 SIP/2.0. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bK828d.ce4b9911000000000000000000000000.0. To: <sip:103.XXX.XXX.22:5060>. From: <sip:dispatcher@localhost>;tag=56254dc816783af7c55a1ac0231200e3-6d5c. CSeq: 10 OPTIONS. Call-ID: 4063eaf942a6e19e-12704(a)10.1.4.23. Max-Forwards: 70. Content-Length: 0. . U 2016/02/07 20:20:25.365672 103.XXX.XXX.22:5060 -> 10.1.4.23:5060 SIP/2.0 404 Not Found. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bK828d.ce4b9911000000000000000000000000.0;received=103.XXX.XXX.23. From: <sip:dispatcher@localhost>;tag=56254dc816783af7c55a1ac0231200e3-6d5c. To: <sip:103.XXX.XXX.22:5060>;tag=as00a791b0. Call-ID: 4063eaf942a6e19e-12704(a)10.1.4.23. CSeq: 10 OPTIONS. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Accept: application/sdp. Content-Length: 0. . U 2016/02/07 20:20:26.250911 103.XXX.XXX.22:5060 -> 10.1.4.23:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKddff.66b1d70306f62152bc5c1a7a1b68eb82.0;received=103.XXX.XXX.23. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: <sip:voip.system.com:5060>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Type: application/sdp. Content-Length: 327. . v=0. o=root 1558510539 1558510539 IN IP4 103.XXX.XXX.22. s=Useragent. c=IN IP4 103.XXX.XXX.22. t=0 0. m=audio 59130 RTP/AVP 9 18 0 8 101. a=rtpmap:9 G722/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. a=sendrecv. U 2016/02/07 20:20:26.252410 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 200 OK. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Type: application/sdp. Content-Length: 327. . v=0. o=root 1558510539 1558510539 IN IP4 103.XXX.XXX.22. s=Useragent. c=IN IP4 103.XXX.XXX.22. t=0 0. m=audio 59130 RTP/AVP 9 18 0 8 101. a=rtpmap:9 G722/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. a=sendrecv. U 2016/02/07 20:20:26.362474 90.X.X.68:25189 -> 10.1.4.23:5060 ACK sip:003165656565@103.XXX.XXX.22:5060 SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-8c04097075073c09-1---d8754z-;rport. Max-Forwards: 70. Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. Contact: <sip:9005@90.X.X.68:25189>. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 ACK. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme",uri=" sip:003165656565@voip.system.com ",response="3473bd0cf6c9af95690edc953fd7346d",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 0. . U 2016/02/07 20:20:26.362493 90.X.X.68:25189 -> 10.1.4.23:5060 BYE sip:003165656565@103.XXX.XXX.22:5060 SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-fd38c235b8219d09-1---d8754z-;rport. Max-Forwards: 70. Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. Contact: <sip:9005@90.X.X.68:25189>. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 3 BYE. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme",uri="sip:003165656565@103.XXX.XXX.22 :5060",response="e3f1d030387f1b10ab21c126b8e8d656",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 0. . U 2016/02/07 20:20:26.365975 10.1.4.23:5060 -> 103.XXX.XXX.22:5060 ACK sip:003165656565@103.XXX.XXX.22:5060 SIP/2.0. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKddff.9327d42091ecb853a5c80ed2dd347040.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-8c04097075073c09-1---d8754z-;rport=25189. Max-Forwards: 69. Contact: <sip:9005@90.X.X.68:25189;alias=90.X.X.68~25189~1>. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. From: "+3165656565"<sip:voip.system.com:5060>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 ACK. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme",uri=" sip:003165656565@voip.system.com ",response="3473bd0cf6c9af95690edc953fd7346d",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 0. . U 2016/02/07 20:20:26.367367 10.1.4.23:5060 -> 103.XXX.XXX.22:5060 BYE sip:003165656565@103.XXX.XXX.22:5060 SIP/2.0. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKedff.e74ad188da31f15ff2ec2bcb57878ae2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-fd38c235b8219d09-1---d8754z-;rport=25189. Max-Forwards: 69. Contact: <sip:9005@90.X.X.68:25189;alias=90.X.X.68~25189~1>. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. From: "+3165656565"<sip:voip.system.com:5060>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 3 BYE. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme",uri="sip:003165656565@103.XXX.XXX.22 :5060",response="e3f1d030387f1b10ab21c126b8e8d656",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 0. . U 2016/02/07 20:20:26.368319 103.XXX.XXX.22:5060 -> 10.1.4.23:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKedff.e74ad188da31f15ff2ec2bcb57878ae2.0;received=103.XXX.XXX.23. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-fd38c235b8219d09-1---d8754z-;rport=25189. From: "+3165656565"<sip:voip.system.com:5060>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 3 BYE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Content-Length: 0. . U 2016/02/07 20:20:26.369422 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 200 OK. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-fd38c235b8219d09-1---d8754z-;rport=25189. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 3 BYE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Content-Length: 0. . <CAEmfXJ4KeqaPD_7k9pgFJNK3Ny4OsQ5X36M+r=Y6LQ1eYwy0pg(a)mail.gmail.com>

1 0

Re: [SR-Users] Error or Bug: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found
by Sid Mason 07 Feb '16

07 Feb '16

Hi, Thanks a lot for the reply, It means a lot to as I am stuck on this issue. I'm not sure if attachment works here or not. I will paste the log in paste bin: http://pastebin.com/0w6a8iTB Regards <CAEmfXJ4KeqaPD_7k9pgFJNK3Ny4OsQ5X36M+r=Y6LQ1eYwy0pg(a)mail.gmail.com>

2 1

Extending the default 1800 seconds of session expiration
by kssyrr 06 Feb '16

06 Feb '16

2 2

why msg_apply_changes() from REQUEST_ROUTE only
by smititelu 05 Feb '16

05 Feb '16

Hello, I don't understand why msg_apply changes() can be called from REQUEST_ROUTE *only*. Can someone explain? Can this be extended to *FAILURE_ROUTES *also? Basically I need to call this from FAILURE_ROUTES in order to avoid double SDP for rtpengine offers. Searching in the mailing list I could see that there could be other means of handling this like keeping and reading the SDP from an avp(write/read_sdp_pv), but I find the above method pretty straightforward. Thanks, Stefan

3 4

Error or Bug: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found
by Sid Mason 05 Feb '16

05 Feb '16

Hi We are receiving error on CANCEL request from client that is supposed to be relayed to an Asterisk Server: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found Any help on this is much appreciated. below is the log: Regards Sid 0(6351) DEBUG: <core> [parser/msg_parser.c:606]: parse_msg(): SIP Request: 0(6351) DEBUG: <core> [parser/msg_parser.c:608]: parse_msg(): method: <CANCEL> 0(6351) DEBUG: <core> [parser/msg_parser.c:610]: parse_msg(): uri: < sip:0031XXXXXXXXX@voip03nl.voipsystem.com> 0(6351) DEBUG: <core> [parser/msg_parser.c:612]: parse_msg(): version: <SIP/2.0> 0(6351) DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK-d8754z-ff05107e83283f5e-1---d8754z->; state=6 0(6351) DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 235, <rport> = <n/a>; state=17 0(6351) DEBUG: <core> [parser/parse_via.c:2642]: parse_via(): end of header reached, state=5 0(6351) DEBUG: <core> [parser/msg_parser.c:496]: parse_headers(): parse_headers: Via found, flags=2 0(6351) DEBUG: <core> [parser/msg_parser.c:498]: parse_headers(): parse_headers: this is the first via 0(6351) DEBUG: <core> [receive.c:134]: receive_msg(): After parse_msg... 0(6351) DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=10 0(6351) DEBUG: <core> [parser/msg_parser.c:173]: get_hdr_field(): DEBUG: get_hdr_field: <To> [59]; uri=[sip:0031XXXXXXXXX@voip03nl.voipsystem.com] 0(6351) DEBUG: <core> [parser/msg_parser.c:175]: get_hdr_field(): DEBUG: to body ["0031XXXXXXXXX"<sip:0031XXXXXXXXX@voip03nl.voipsystem.com> 0(6351) DEBUG: <core> [parser/msg_parser.c:153]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <2> <CANCEL> 0(6351) DEBUG: <core> [parser/msg_parser.c:187]: get_hdr_field(): DEBUG: get_hdr_body : content_length=0 0(6351) DEBUG: <core> [parser/msg_parser.c:89]: get_hdr_field(): found end of header {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [receive.c:177]: receive_msg(): preparing to run routing scripts... {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=614 a=5 n=route {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=734 a=25 n=xlog {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: <script>: The IP is : 90.152.66.68 and uri {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=745 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=742 a=25 n=xlog {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: <script>: Match the 0/24 IP -- the message was sent from REGUS OFFICE! {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=767 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [socket_info.c:563]: grep_sock_info(): checking if host==us: 12==9 && [90.152.66.68] == [10.1.4.23] {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [socket_info.c:582]: grep_sock_info(): checking advertise if host==us: 12==22 && [90.152.66.68] == [voip03nl.voipsystem.com] {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [socket_info.c:563]: grep_sock_info(): checking if host==us: 12==9 && [90.152.66.68] == [10.1.4.23] {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [socket_info.c:582]: grep_sock_info(): checking advertise if host==us: 12==22 && [90.152.66.68] == [voip03nl.voipsystem.com] {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [forward.c:412]: check_self(): host != me {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=761 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=766 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=761 a=24 n=pike_check_req {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: pike [ip_tree.c:286]: mark_node(): search on branch 90 (top=0x7f24a45a4688) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: pike [ip_tree.c:299]: mark_node(): only first 4 were matched! {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: pike [pike_funcs.c:93]: pike_check_req(): src IP [90.152.66.68],node=0x7f24a45a4d78; hits=[0,0],[0,1] node_flags=6 func_flags=0 {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: pike [timer.c:46]: remove_from_timer(): 0x7f24a45a4d88 from 0x7f24a4579500(0x7f24a45a4d88,0x7f24a45a4d88) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: pike [timer.c:33]: append_to_timer(): 0x7f24a45a4d88 in 0x7f24a4579500(0x7f24a4579500,0x7f24a4579500) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=782 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=807 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=782 a=25 n=mf_process_maxfwd_header {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: maxfwd [mf_funcs.c:66]: is_maxfwd_present(): max_forwards header not found! {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=807 a=26 n=xlog {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <script>: [REQINIT] (Method is CANCEL) r-uri ( sip:0031XXXXXXXXX@voip03nl.voipsystem.com) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=825 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=811 a=25 n=is_method {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=829 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[REQINIT] c=[/etc/kamailio/kamailio.cfg] l=825 a=26 n=sanity_check {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [parser/parse_addr_spec.c:172]: parse_to_param(): DEBUG: add_param: tag=0d61d760 {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=29 {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: sanity [mod_sanity.c:248]: w_sanity_check(): sanity checks result: 1 {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=617 a=5 n=route {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1104 a=55 n=force_rport {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1149 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1118 a=25 n=nat_uac_test {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1143 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1119 a=25 n=is_method {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1125 a=25 n=xlog {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: <script>: [NATDETECT]: method is CANCEL{1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_r oute=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1142 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1132 a=24 n=is_first_hop {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: siputils [sipops.c:159]: w_is_first_hop(): no 2nd via found - first hop {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1138 a=26 n=xlog {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <script>: [NATDETECT]: (is_first_hop() is true) set_contact_alias() Adds an “;alias=ip~port~transport” parameter to the contact URI{1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1139 a=24 n=set_contact_alias {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1146 a=39 n=setflag {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1151 a=26 n=xlog {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <script>: [NATDETECT]: NATDETECT is done{1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[NATDETECT] c=[/etc/kamailio/kamailio.cfg] l=1152 a=2 n=return {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=620 a=5 n=route {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[WITHINDLG] c=[/etc/kamailio/kamailio.cfg] l=842 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[WITHINDLG] c=[/etc/kamailio/kamailio.cfg] l=837 a=24 n=has_totag {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: siputils [checks.c:97]: has_totag(): no totag {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[WITHINDLG] c=[/etc/kamailio/kamailio.cfg] l=838 a=26 n=xlog {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <script>: [WITHINDLG]: Has_totag() is false; Return 1;{1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[WITHINDLG] c=[/etc/kamailio/kamailio.cfg] l=839 a=2 n=return {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=632 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=625 a=25 n=is_method {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=629 a=16 n=if {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=627 a=24 n=t_check_trans {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:701]: t_lookupOriginalT(): DEBUG: t_lookupOriginalT: searching on hash entry 38426 {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:409]: matching_3261(): DEBUG: RFC3261 transaction matched, tid=-d8754z-ff05107e83283f5e-1---d8754z- {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:798]: t_lookupOriginalT(): DEBUG: t_lookupOriginalT: canceled transaction found (0x7f24a45a4fa8)! {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:801]: t_lookupOriginalT(): DEBUG: t_lookupOriginalT completed {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [tm.c:1043]: w_t_lookup_cancel(): lookup_original: t_lookupOriginalT returned: 0x7f24a45a4fa8 {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=628 a=24 n=t_relay {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:1312]: t_newtran(): DEBUG: t_newtran: msg id=12 , global msg id=11 , T on entrance=0xffffffffffffffff {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:466]: t_lookup_request(): t_lookup_request: start searching: hash=38426, isACK=0 {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:424]: matching_3261(): DEBUG: RFC3261 transaction matching failed {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:648]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_hooks.c:358]: run_reqin_callbacks_internal(): DBG: trans=0x7f24a45a9098, callback type 1, id 0 entered {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [md5utils.c:67]: MD5StringArray(): MD5 calculated: a4351b7a4b00df7d36f1c82b3d87c603 {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:701]: t_lookupOriginalT(): DEBUG: t_lookupOriginalT: searching on hash entry 38426 {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:409]: matching_3261(): DEBUG: RFC3261 transaction matched, tid=-d8754z-ff05107e83283f5e-1---d8754z- {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:798]: t_lookupOriginalT(): DEBUG: t_lookupOriginalT: canceled transaction found (0x7f24a45a4fa8)! {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_lookup.c:801]: t_lookupOriginalT(): DEBUG: t_lookupOriginalT completed {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: tm [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: tm [t_msgbuilder.c:494]: build_local_reparse(): ERROR: build_local_reparse: cannot build CANCEL request {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: tm [t_cancel.c:310]: cancel_branch(): ERROR: attempt to build a CANCEL failed {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: tm [t_fwd.c:1388]: e2e_cancel(): ERROR: cancel error {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [mem/shm_mem.c:101]: _shm_resize(): WARNING:vqm_resize: resize(0) called {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_reply.c:1591]: cleanup_uac_timers(): DEBUG: cleanup_uac_timers: RETR/FR timers reset {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_reply.c:647]: _reply_light(): DEBUG: reply sent out. buf=0x7f24aee459c8: SIP/2.0 500 cancel e..., shmem=0x7f24a45ab880: SIP/2.0 500 cancel e {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_reply.c:657]: _reply_light(): DEBUG: _reply_light: finished {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: tm [t_funcs.c:362]: t_relay_to(): SER: new transaction fwd'ed {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) ERROR: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=629 a=2 n=exit {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [usr_avp.c:631]: destroy_avp_list(): destroying list (nil) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [xavp.c:446]: xavp_destroy_list(): destroying xavp list (nil) {1 2 CANCEL MmU5NDBhMTcxYzc1YWNmZGJiNGQ3NmU4NjU2M2I2NTc.} 0(6351) DEBUG: <core> [receive.c:278]: receive_msg(): cleaning up

2 1

Kamailio strange behaviour
by Gholamreza Sabery 05 Feb '16

05 Feb '16

I am using Kamailio 4.1.x with NAT enabled. When I want to REGISTER using my desktop client which is Linphone everything is find with any username. But on Android some users can REGISTER and someusers can not. I captured SIP packets and the only difference between packets on Android devices and packets on Desktop client is that on my desktop "received" and "rport" are not added by Kamailio in response messages. Any idea on what is happening here?

2 3

Extending the default 1800 seconds expiration of presence
by kssyrr 04 Feb '16

04 Feb '16

1 0

Sip routing
by David Bakker 04 Feb '16

04 Feb '16

I want to be able to route sip invites from my on prem skype to either an on prem jabber server or out to office 365. It depends on who the recipient is. I am sure Kamailio can do this but I am absolutely at a loss on where to start. I have tried a few different configs but I basically have to break our office communication to test. I am looking for some guidance on what to do. Thanks in advance!

2 1

Kamailio v4.4 - development frozen
by Daniel-Constantin Mierla 04 Feb '16

04 Feb '16

Hello, development (master) branch of Kamailio enters now in pre-release phase for version 4.4.0. Therefore, no new feature should be pushed to master until we create a dedicated branch for 4.4 (expected to be in about 4 weeks or so). If in doubt to push or not a commit to master, push it first on a personal branch (or attach to an email) and discuss it on sr-dev. The new modules can be a bit more dynamic if there is need to get them to the right shape (e.g., like decision to rename functions, parameters or adjust database structure). We hope to get many people involved in testing, to reach a stable state before releasing 4.4.0. If you want to get involved and need assistance, don't hesitate to write to mailing lists. Based on my quick review, there were no major changes to old core components, meaning we should have preserved quite a good level of stability overall. Help with updating the wiki page for migration from 4.3 to 4.4 as well as what is new in 4.4 is very appreciated. I will post updates about them very soon. Many thanks to everyone involved in development of 4.4 and the early testers that played with master branch so far. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 18-20, 2016 Berlin, Germany - http://www.kamailioworld.com

1 0

Kamailio Cluster
by Gholamreza Sabery 03 Feb '16

03 Feb '16

I am trying to create a cluster of Kamailio servers. I want users that are registered on one server to be able to contact and call users on other servers. How can I implement this in Kamailio? PS: My servers are in a private network and I do not have DNS.

10 21

rtpengine port allocation & recycling
by Alex Balashov 03 Feb '16

03 Feb '16

Hello, I have a high-volume installation with 100% RTP relay using rtpengine. We run rtpengine with a high and low port range of 8000 - 65000. Generally the peak concurrent channel count is around 2000-4000 ports, so in theory, so we should have enough ports for all calls currently in process. In practice, however, we get a nearly constant stream of these errors from Kamailio: Feb 2 15:52:58 sip /usr/local/sbin/kamailio[16438]: ERROR: rtpengine [rtpengine.c:1541]: rtpp_function_call(): proxy replied with error: Error rewriting SDP When I trace this back to rtpengine logs on the server, I see: --- Feb 2 15:55:47 rtphost rtpengine[14710]: [FSRIGZPJGXZWPNO.52364.907376806] Received command 'offer' from 215.111.222.101:54100 Feb 2 15:55:47 rtphost rtpengine[14710]: [FSRIGZPJGXZWPNO.52364.907376806] Creating new call Feb 2 15:55:47 rtphost rtpengine[14710]: [FSRIGZPJGXZWPNO.52364.907376806] Failed to get 2 consecutive UDP ports for relay Feb 2 15:55:47 rtphost rtpengine[14710]: [FSRIGZPJGXZWPNO.52364.907376806] Error allocating media ports Feb 2 15:55:47 rtphost rtpengine[14710]: [FSRIGZPJGXZWPNO.52364.907376806] Protocol error in packet from 215.111.222.101:54100: Error rewriting SDP [d3:sdp285:v=0#015#012o=- 1631132006999214513 4263823554000404972 IN IP4 45.201.202.203#015#012s=VOS2009#015#012c=IN IP4 45.201.202.203#015#012t=0 0#015#012m=audio 29034 RTP/AVP 18 8 0 101#015#012a=rtpmap:18 G729/8000#015#012a=fmtp:18 annexb=no#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101 0-15#015#0123:ICE6:remove7:replacel6:origin18:session-connectione7:call-id31:FSRIGZPJGXZWPNO.52364.90737680613:received-froml3:IP415:215.111.222 ... Feb 2 15:55:47 rtphost rtpengine[14710]: [FSRIGZPJGXZWPNO.52364.907376806] ... 5.125e8:from-tag32:709abb985b675e1497597a5bd44ca2d67:command5:offere] --- This is despite nearly no rtpengine engagement: [root@csrprtpus1 log]# cat /proc/rtpengine/0/status Refcount: 1 Control PID: 14709 Targets: 0 Buckets: 0 As far as I can see, the cause is that rtpengine is not deallocating ports: --- [root@rtphost log]# lsof -n | grep -i rtp rtpengine 14710 root *542u IPv6 1082109949 0t0 UDP *:39910 rtpengine 14710 root *543u IPv6 1082109950 0t0 UDP *:39911 rtpengine 14710 root *544u IPv6 1082218768 0t0 UDP *:41469 rtpengine 14710 root *545u IPv6 1082058934 0t0 UDP *:46424 rtpengine 14710 root *546u IPv6 1082366799 0t0 UDP *:22915 rtpengine 14710 root *547u IPv6 1082288397 0t0 UDP *:57245 rtpengine 14710 root *548u IPv6 1082428020 0t0 UDP *:24311 rtpengine 14710 root *549u IPv6 1082366800 0t0 UDP *:23266 rtpengine 14710 root *550u IPv6 1082798144 0t0 UDP *:22743 rtpengine 14710 root *551u IPv6 1082605782 0t0 UDP *:47845 rtpengine 14710 root *552u IPv6 1082062515 0t0 UDP *:52766 rtpengine 14710 root *553u IPv6 1082648709 0t0 UDP *:58266 rtpengine 14710 root *554u IPv6 1082122218 0t0 UDP *:54359 ... --- There are _lots_ of these: [root@rtphost log]# lsof -n | grep -i rtpengine | grep 'UDP \*:' | wc -l 56964 So, I suppose most of these just aren't being freed up. These are short-duration calls, and the vast majority of them are CANCEL'd at various stages of completion. My approach to invocation of rtpengine in the config is: 1) rtpengine_offer() in branch_route[] on outbound call: set_rtpengine_set("1"); rtpengine_offer("replace-origin replace-session-connection ICE=remove"); add_rr_param(";proxy_media=yes"); setflag(PROXY_MEDIA); This can happen multiple times, as many branches may be attempted before a gateway is found to take the call. 2) Symmetrical rtpengine_answer() in onreply_route: if(isflagset(PROXY_MEDIA) && has_body("application/sdp") && $var(origin_b2bua) == 0) { set_rtpengine_set("1"); rtpengine_answer("replace-origin replace-session-connection ICE=remove"); } 3) rtpengine_delete() in event of CANCEL: if(is_method("CANCEL")) { # Kill RTP stream if this call was using rtpengine. set_rtpengine_set("1"); rtpengine_delete(); # Implicitly forward the CANCEL and drop out of script # if the corresponding INVITE transaction exists. if(!t_relay_cancel()) { # If we are still here, the INVITE transaction # was found but an error occurred. sl_send_reply("500", "Internal Server Error"); exit; } # If we are still here, this is also bad because it means # the corresponding INVITE transaction no longer exists. xlog("L_INFO", 'action=R-MAIN-REQUEST | ret=CANCEL_NO_TRANS_MATCH'); exit; 4) rtpengine_delete() in case of BYE: if(has_totag()) { if(loose_route()) { if(is_method("BYE")) { if(check_route_param("proxy_media=yes")) { set_rtpengine_set("1"); rtpengine_delete(); } } else if(is_method("INVITE")) { # update rtpengine_offer() etc. } ... } else { ... } } Any obvious problem here? Thanks! -- Alex -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 5

Freezing the development for next major version 4.4
by Daniel-Constantin Mierla 03 Feb '16

03 Feb '16

Hello, as a follow up to previous discussions on the mailing list, I would like to propose Wednesday, Feb 3, 2016 as the day to freeze the development for next major release. It will allow the people going at Fosdem to chat and do last minute tunings before freezing. Other suggestions or comments are welcome! Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

3 6

Compile error with CNXCC on Debian 7 Wheezy
by Dirk Teurlings - SIGNET B.V. 03 Feb '16

03 Feb '16

Hi, While compiling Kamailio 4.3.4 from package sources for Debian 7 Wheezy (kamailio repository) I'm running into a problem. I've forked the CNXCC module which I was trying to keep up to date with upstream changes. But before I could do that, there is a dependency of redis added. Unfortunately, installing redis devel libs and libevent doesn't provide the correct version of redis. Also, I noticed on Debian 8 Jessie, it does compile correctly. How could Kamailio be compiled for Wheezy with these sources? I'm missing something obvious I feel. Attached is the compile log, this is with a completely unaltered sources. root@devhost:/usr/src/kamailio-4.3.4+wheezy# make -C modules/cnxcc make: Entering directory `/usr/src/kamailio-4.3.4+wheezy/modules/cnxcc' CC (gcc) [L libkmi.so.1.0] attr.o CC (gcc) [L libkmi.so.1.0] fmt.o CC (gcc) [L libkmi.so.1.0] mi.o CC (gcc) [L libkmi.so.1.0] tree.o LD (gcc) [L libkmi.so.1.0] libkmi.so.1.0 CC (gcc) [L libsrdb1.so.1.0] db.o CC (gcc) [L libsrdb1.so.1.0] db_id.o CC (gcc) [L libsrdb1.so.1.0] db_pool.o CC (gcc) [L libsrdb1.so.1.0] db_query.o CC (gcc) [L libsrdb1.so.1.0] db_res.o CC (gcc) [L libsrdb1.so.1.0] db_row.o CC (gcc) [L libsrdb1.so.1.0] db_ut.o CC (gcc) [L libsrdb1.so.1.0] db_val.o LD (gcc) [L libsrdb1.so.1.0] libsrdb1.so.1.0 CC (gcc) [L libkcore.so.1.0] cmpapi.o CC (gcc) [L libkcore.so.1.0] faked_msg.o CC (gcc) [L libkcore.so.1.0] kstats_wrapper.o CC (gcc) [L libkcore.so.1.0] parse_privacy.o CC (gcc) [L libkcore.so.1.0] parse_sst.o CC (gcc) [L libkcore.so.1.0] regexp.o CC (gcc) [L libkcore.so.1.0] statistics.o CC (gcc) [L libkcore.so.1.0] strcommon.o LD (gcc) [L libkcore.so.1.0] libkcore.so.1.0 LD (gcc) [M cnxcc.so] cnxcc.so cnxcc_mod.o: In function `redisLibeventReadEvent': /usr/include/hiredis/adapters/libevent.h:10: multiple definition of `redisLibeventReadEvent' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:10: first defined here cnxcc_mod.o: In function `redisLibeventWriteEvent': /usr/include/hiredis/adapters/libevent.h:16: multiple definition of `redisLibeventWriteEvent' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:16: first defined here cnxcc_mod.o: In function `redisLibeventAddRead': /usr/include/hiredis/adapters/libevent.h:22: multiple definition of `redisLibeventAddRead' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:22: first defined here cnxcc_mod.o: In function `redisLibeventDelRead': /usr/include/hiredis/adapters/libevent.h:27: multiple definition of `redisLibeventDelRead' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:27: first defined here cnxcc_mod.o: In function `redisLibeventAddWrite': /usr/include/hiredis/adapters/libevent.h:32: multiple definition of `redisLibeventAddWrite' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:32: first defined here cnxcc_mod.o: In function `redisLibeventDelWrite': /usr/include/hiredis/adapters/libevent.h:37: multiple definition of `redisLibeventDelWrite' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:37: first defined here cnxcc_mod.o: In function `redisLibeventCleanup': /usr/include/hiredis/adapters/libevent.h:42: multiple definition of `redisLibeventCleanup' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:42: first defined here cnxcc_mod.o: In function `redisLibeventAttach': /usr/include/hiredis/adapters/libevent.h:49: multiple definition of `redisLibeventAttach' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:49: first defined here cnxcc_redis.o: In function `redisLibeventReadEvent': /usr/include/hiredis/adapters/libevent.h:10: multiple definition of `redisLibeventReadEvent' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:10: first defined here cnxcc_redis.o: In function `redisLibeventWriteEvent': /usr/include/hiredis/adapters/libevent.h:16: multiple definition of `redisLibeventWriteEvent' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:16: first defined here cnxcc_redis.o: In function `redisLibeventAddRead': /usr/include/hiredis/adapters/libevent.h:22: multiple definition of `redisLibeventAddRead' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:22: first defined here cnxcc_redis.o: In function `redisLibeventDelRead': /usr/include/hiredis/adapters/libevent.h:27: multiple definition of `redisLibeventDelRead' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:27: first defined here cnxcc_redis.o: In function `redisLibeventAddWrite': /usr/include/hiredis/adapters/libevent.h:32: multiple definition of `redisLibeventAddWrite' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:32: first defined here cnxcc_redis.o: In function `redisLibeventDelWrite': /usr/include/hiredis/adapters/libevent.h:37: multiple definition of `redisLibeventDelWrite' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:37: first defined here cnxcc_redis.o: In function `redisLibeventCleanup': /usr/include/hiredis/adapters/libevent.h:42: multiple definition of `redisLibeventCleanup' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:42: first defined here cnxcc_redis.o: In function `redisLibeventAttach': /usr/include/hiredis/adapters/libevent.h:49: multiple definition of `redisLibeventAttach' cnxcc_check.o:/usr/include/hiredis/adapters/libevent.h:49: first defined here collect2: error: ld returned 1 exit status make: *** [cnxcc.so] Error 1 make: Leaving directory `/usr/src/kamailio-4.3.4+wheezy/modules/cnxcc' Cheers, Dirk

3 3

Possible accidental merge to master.
by Cody Herzog 03 Feb '16

03 Feb '16

Hello. I feel like a total idiot. I was inspecting the various GitHub branches for Kamailio using a GitHub visual client, and I think I managed to accidentally merge a branch back into master. The branch I was inspecting was 'lazedo/presence_improvements'. I was inspecting diffs and branches, and was amazed that I was able to screw up so badly with one single click, but I guess that's the danger of a visual git client. Anyway, before trying to do anything more, I figured I'd asked for advice, because I don't want to screw up further. Hopefully there's a simple way to revert the accidental merge, but I first wanted to confirm that I actually did make that mistake, and that it's visible to others. Thanks.

2 2

issue with INVITE frame size
by Rene Montilva 03 Feb '16

03 Feb '16

Hi list I have problem with invite packet in some wifi networks because the invite packet is less than 1000bytes(frame size) and the access point not redirect to softphone, this scenario happen with incoming calls to my DID, the packets come from the provider to kamailio with a size more than 1000 and when kamailio redirect to softphone sometimes is less than 1000. how i could solve this issue?. thanks for any help.

3 7

Kamailio/How to send all requests ?
by alexandre.anconetti＠orange.com 02 Feb '16

02 Feb '16

Hello ! I'm using Kamailio for 2 months, and I have a problem with the routing logic. My aim is to use 2 Kamailio servers (in a cluster, so I have a primary and a backup server with a Virtual IP that can switch between the 2 servers) working with 2 medias servers (same as above, a primary and a backup). The Kamailio servers are here to handle failover, so all the requests go through them, and then are sent to the active media server. My question is : Which module(s) should I load to transmit all the requests (including registers) to my media server, through the Kamailio server ? Any particular parameters ? Then, what will be in the "request_route" ? I'm using Kamailio 4.3.4. Best regards, Alexandre _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

2 2

SIP register - memory size
by José Seabra 02 Feb '16

02 Feb '16

Hello there, Can anyone tell me what is the exactly memory size that kamailio use for one sip register saved on memory? How much memory i need allocate to kamailio in order to support 50.000 subscribers. Best Regards

2 4

Kamailio Social Event at Fosdem 2016
by Daniel-Constantin Mierla 02 Feb '16

02 Feb '16

Hello, only few days left, so we need to nail the location down for Kamailio dinner at Fosdem. One suggestion in walking distance is: - http://restaurant-italien-picotin-bruxelles.be/en I understood that it was used in the past also for Fosdem Speaker's Dinner, so it might be busy and we can't get the seats. So new suggestions are more than welcome in order to have some backups to try! If there is no strong preference for something else by end of today, tomorrow we should attempt to do the reservation at this place. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

5 9

Asterisk+Kamailio
by Вячеслав Завалко 02 Feb '16

02 Feb '16

The adjustment was carried out by a manual that http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb But the sharing screen is not working softphone on a given configuration. What can be done?

2 1

kamailio + asterisk
by Вячеслав Завалко 02 Feb '16

02 Feb '16

Is it possible to do a demonstration screen caller using Kamailio + Asterisk?

2 1

Kamailio 4.3 and Freeswitch 1.0 Stable Latest
by Barış Şekerciler 02 Feb '16

02 Feb '16

Hello everyone. I'm a student and I'm working on project which about SIP communication and PBXs with IP phones. So, my first test results were OK with JITSI. But I think I need Freeswitch for working with IP phones. In a word, I need configure an integration Kamailio and Freeswitch. First, I setup Debian 8.3 Jessie and installed Kamailio on this my local server, after that I installed another Debian 8.3 Jessie (from same image) as my second server and it was going to run Freeswitch on itself. Then I tried to send my communication requests to my Freeswitch server. I made some tests, my Jitsi accounts which are set in Kamailio server were done. I've read Kamailio 3.2 and Freeswitch integration from the Kamailio wiki and I applied exactly the same thing but I did not work. When I tried to reach another IP phone from my IP phone (I registered them) phone always say "NOT FOUND". I'm sure I did my configuration properly. So, how can I figure it out these things? How can I understand, does Kamailio routes to Freeswitch to my phones? Best regards. Thanks.

2 1

Critical issue: Kamailio throwing db errors
by Sharon Nathaniel 02 Feb '16

02 Feb '16

Hi, I am not sure, if its a kamailio issue or something else, but our Kamailio 4.2 server crashes everyday. Throwing out these logs: http://pastebin.com/z1MWdk7q. We have to restart the server to get this fixed. Please help us understand what is causing the issue. Thanks and Regards, Sharon Nathaniel The information in this email is confidential and may be legally privileged. It is intended solely for the addressee and access to it by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken based on it, is strictly prohibited and may be unlawful.

2 1

Kamailio v4.3 and Freeswitch Stable Latest
by Barış Şekerciler 02 Feb '16

02 Feb '16

Hello everyone. I'm a student and I'm working on project which about SIP communication and PBXs with IP phones. So, my first test results were OK with JITSI. But I think I need Freeswitch for working with IP phones. In a word, I need configure an integration Kamailio and Freeswitch. First, I setup Debian 8.3 Jessie and installed Kamailio on this my local server, after that I installed another Debian 8.3 Jessie (from same image) as my second server and it was going to run Freeswitch on itself. Then I tried to send my communication requests to my Freeswitch server. I made some tests, my Jitsi accounts which are set in Kamailio server were done. I've read Kamailio 3.2 and Freeswitch integration from the Kamailio wiki and I applied exactly the same thing but I did not work. When I tried to reach another IP phone from my IP phone (I registered them) phone always say "NOT FOUND". I'm sure I did my configuration properly. So, how can I figure it out these things? How can I understand, does Kamailio routes to Freeswitch to my phones? Best regards. Thanks.

4 27

Force transport from TLS to UDP when using dispatcher
by mayamatakeshi 01 Feb '16

01 Feb '16

Hello, I have this scenario: - subscriber registers using TLS - call arrives from PSTN gateway (in UDP) to subscriber - I relay the INVITE to subscriber but it doesn't answer the call - the subscriber has callforward enabled - we send the call to PSTN callforward destination using carrierroute In the above, after calling cr_route I use this: $du = "sip:" + $rd + ":" + $rp + ";transport=udp"; to force the call to PSTN gateway to go out as UDP because after trying to call the subscriber, the transport changes and stays as TLS. However, if instead of callforward the user has voicemail enabled, we use dispatcher to send the call to a cluster of media servers. So, after calling ds_select_dst() I call $du = "sip:" + $dd + ":" + $dp + ";transport=udp"; but this is unable to force the call to go as UDP but it still goes as in TLS In both cases I see this in the log files: /usr/local/src/git/kamailio-4.3/kamailio[19277]: WARNING: <core> [forward.c:231]: get_send_socket2(): protocol/port mismatch (forced tls:XXX.XXX.XXX.XXX:5061, to udp:YYY.YYY.YYY.YYY:5060) But it only works for carrierroute, not for dispatcher. I am not sure if this is a bug in dispatcher. But anyway, is there any other way I could try to force transport=UDP? Regards, Takeshi

1 1

checking source domain
by Yuriy Gorlichenko 01 Feb '16

01 Feb '16

I need to understand where from packets received. Now I use something like If $si == "1.2.3.4" { xlog("L_INFO","bla bla bla"); } But I need to check source server not only by IP and PORT, but at Domain too For example if (some_pseudovariable=="pbx.server.com"){ xlog("L_INFO","bla bla bla"); } I can use $fu for example because for some packets it includes domain name of kamailio (i think details not important but this situations can be) Does kamailio have some mechanisms to do that? I searched it at cookbook but not found anything. Thank you

2 1

RTPPROXY issue and sip to sip calling
by Ahmed Rehan 31 Jan '16

31 Jan '16

Dear All I m trying to setup kamailio and asterisk in load balancing with a2billing . Currently all of my VMs, one Kamailio and two asterisks are on same subnet . I have started the RTPproxy like below ./rtpproxy -s udp:127.0.0.1:7722 -l X.X.X.153 -m 10000 -M 50000 -u root root -F -d INFO LOG_LOCAL0 My question is if all the VMs are on same subnet with same gateway what should be written in the private IP X.X.X.153/<private - ip> Secondly i m authenticating and registering the SIP on kamailio using the A2B DB . all the dialplan for a2b is being run on asterisk . Now if i want to call SIP peer to Peer like in case of followme case , How should i route the calls in Kamailio ? will it be using usr loc module? if so any help will be appreciated -- Regards Ahmed Rehan

2 1

Core Dump during shutdown on SPARC64
by Spencer Thomason 31 Jan '16

31 Jan '16

Hello, I’m trying to get Kamailio running on Solaris 11 SPARC64 and I’m receiving a bus error on shutdown. If needed, we can make SPARC hardware available for testing. Thanks, Spencer Core was generated by `/opt/kamailio/sbin/kamailio -f /opt/kamailio/etc/kamailio/kamailio.cfg -P /syst'. Program terminated with signal 10, Bus error. #0 0x00000001003e73f0 in cfg_destory_groups (block=0xffffffff76e5ded4 "") at cfg/cfg_struct.c:299 299 old_string = *(char **)(block + group->var_offset + mapping[i].offset); (gdb) bt full #0 0x00000001003e73f0 in cfg_destory_groups (block=0xffffffff76e5ded4 "") at cfg/cfg_struct.c:299 group = 0x100745e20 def = <optimized out> i = 14 group2 = <optimized out> mapping = 0x100745a78 old_string = <optimized out> #1 cfg_destroy () at cfg/cfg_struct.c:391 __FUNCTION__ = "cfg_destroy" #2 0x0000000100163fc4 in cleanup (show_status=show_status@entry=1) at main.c:540 memlog = <optimized out> __FUNCTION__ = "cleanup" #3 0x00000001001650d4 in shutdown_children (show_status=show_status@entry=1, sig=15) at main.c:665 No locals. #4 0x0000000100165c0c in handle_sigs () at main.c:695 chld = <optimized out> chld_status = 0 memlog = <optimized out> __FUNCTION__ = "handle_sigs" #5 0x000000010016e678 in main_loop () at main.c:1722 i = <optimized out> pid = <optimized out> si = <optimized out> si_desc = "udp receiver child=15 sock=104.222.31.55:9000\000\005\066\377\377\377\377v\345\322\370\000\000\000\000\000\020\000\063\377\377\377\377\177\377\360q\000\000\000\001\000B\277 \000\000\000\001\000^:P\000\000\000\001\000\002\356(\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375\377\377\377\377\377\377\377\375" nrprocs = <optimized out> woneinit = <optimized out> __FUNCTION__ = "main_loop" #6 0x000000010042cafc in main (argc=<optimized out>, argv=<optimized out>) at main.c:2597 cfg_stream = <optimized out> c = <optimized out> r = <optimized out> tmp = 0xffffffff7ffffd57 "" tmp_len = 0 port = 0 proto = 0 options = 0x100036918 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:" ret = -1 seed = 4139658536 rfd = <optimized out> debug_save = <optimized out> debug_flag = <optimized out> dont_fork_cnt = <optimized out> p = <optimized out> st = {st_dev = 2478196129807, st_ino = 405001306, st_mode = 16832, st_nlink = 2, st_uid = 0, st_gid = 0, st_rdev = 18446744073709551615, st_size = 117, st_atim = {tv_sec = 1452739293, tv_nsec = 444332080}, st_mtim = { tv_sec = 1452739411, tv_nsec = 727071262}, st_ctim = {tv_sec = 1452739411, tv_nsec = 727071262}, st_blksize = 8192, st_blocks = 16, st_fstype = "tmpfs\000\000\000\000\000\000\000\000\000\000"} __FUNCTION__ = “main" # this file is autogenerated by make cfg MAIN_NAME= kamailio CFG_NAME= kamailio SCR_NAME= sip-router FLAVOUR= kamailio INSTALL_FLAVOUR= kamailio SRC_NAME= sip-router RELEASE= 4.4.0-dev8 OS= solaris ARCH= sparc64 C_DEFS= -DNAME='"kamailio"' -DVERSION='"4.4.0-dev8"' -DARCH='"sparc64"' -DOS='solaris_' -DOS_QUOTED='"solaris"' -DCOMPILER='"gcc 4.8.2"' -D__CPU_sparc64 -D__OS_solaris -DSER_VER=4004000 -DCFG_DIR='"/opt/kamailio/etc/kamailio/"' -DRUN_DIR='"/var/run/kamailio/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DUSE_NAPTR -DWITH_XAVP -DF_MALLOC -DQ_MALLOC -DTLSF_MALLOC -DDBG_SR_MEMORY -DUSE_TLS -DTLS_HOOKS -DUSE_CORE_STATS -DSTATISTICS -DMALLOC_STATS -DWITH_AS_SUPPORT -DUSE_SCTP -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DSPARC64_MODE -DHAVE_GETIPNODEBYNAME -DHAVE_SYS_SOCKIO_H -DHAVE_SCHED_YIELD -DHAVE_ALLOCA_H -DUSE_SIGACTION -DHAVE_DEVPOLL -DHAVE_SELECT -DHAVE_FILIO_H DEFS_RM= PROFILE= CC= gcc LD= gcc MKDEP= gcc -MM -MG MKTAGS= ctags LDFLAGS= -m64 -O2 C_INCLUDES= CC_MKDEP_OPTS= -MMD -MP MOD_LDFLAGS= -G -m64 -O2 LIB_LDFLAGS= -G -m64 -O2 UTILS_LDFLAGS= -m64 -O2 LIB_SONAME= -Wl,-h, LD_RPATH= -Wl,-R, LIB_SUFFIX= .so LIB_PREFIX= lib LIBS= -ldl -lresolv -L/usr/local/lib -lxnet -lsocket -lnsl -lrt LEX= flex YACC= bison YACC_FLAGS= -d -b cfg PREFIX= /opt/kamailio LOCALBASE= /usr/local TAR= gtar INSTALL= ginstall INSTALL_CFG= ginstall -m 644 INSTALL_BIN= ginstall -m 755 INSTALL_MODULES= ginstall -m 755 INSTALL_DOC= ginstall -m 644 INSTALL_MAN= ginstall -m 644 INSTALL_LIB= ginstall -m 755 INSTALL_TOUCH= touch INSTALL_SHARE= ginstall -m 644 Q= 1 CC_EXTRA_OPTS= -O2 -m64 CPU= ultrasparc CFLAGS_RM= CFLAGS= -g -funroll-loops -mtune=native -mcpu=native -fno-strict-overflow -ftree-vectorize -Wall -mno-faster-structs MOD_CFLAGS= -fPIC -DPIC $(CFLAGS) LIB_CFLAGS= -fPIC -DPIC $(CFLAGS) UTILS_CFLAGS= $(CFLAGS) BASEDIR= $(DESTDIR) basedir= $(BASEDIR) DESTDIR= LIBDIR= lib64 RUNBASEDIR= $(DESTDIR) runbasedir= $(RUNBASEDIR) PREFIX= /opt/kamailio prefix= $(PREFIX) cfg_prefix= $(basedir)$(prefix) cfg_dir= etc/$(MAIN_NAME)/ bin_prefix= $(basedir)$(prefix) bin_dir= sbin/ modules_prefix= $(basedir)$(prefix) modules_dir= $(LIBDIR)/$(MAIN_NAME)/ doc_prefix= $(basedir)$(prefix) doc_dir= doc/$(MAIN_NAME)/ man_prefix= $(basedir)$(prefix) man_dir= man/ ut_prefix= $(basedir)$(prefix) ut_dir= share_prefix= $(basedir)$(prefix) share_dir= share/$(MAIN_NAME)/ lib_prefix= $(basedir)$(prefix) lib_dir= $(LIBDIR)/$(MAIN_NAME)/ data_prefix= $(basedir)$(prefix) data_dir= $(MAIN_NAME)/ cfg_target= $(prefix)/$(cfg_dir) lib_target= $(prefix)/$(lib_dir) data_target= $(prefix)/$(data_dir) run_prefix= $(runbasedir) run_dir= var/run/$(MAIN_NAME)/ run_target= $(run_prefix)/$(run_dir) override makefile_defs:=1 C_DEFS:=$(filter-out $(DEFS_RM) $(extra_defs),$(C_DEFS)) $(extra_defs) CFLAGS:=$(filter-out $(CFLAGS_RM) $(CC_EXTRA_OPTS), $(CFLAGS)) $(CC_EXTRA_OPTS)

2 5

P-CSCF
by Fred Schulz 30 Jan '16

30 Jan '16

Hi all, we’re just playing around with an IMS setup bases on kamailio. Therefore the kamailio is used as P-,I- and S-CSCF. We where able to register two clients through all components. As we wan to start a call session, the P-CSCF answers with „403 - Forbidden. You must register with an S-CSCF“… I found this snippet in kamailio.cfg: if (!pcscf_is_registered("location")) { send_reply("403","Forbidden - You must register first with a S-CSCF“); break; } Can one tell me what exactly the kamailio is checking there? As I figured out it is looking in database location table. The table contains the registered users registered towards the IMS. Another „problem“ we faced with is the rtpproxy. As the ngcp-mediaproxy-ng is no longer available and replaced with rtpproxy we’re trying to use it. But kamailio said that the proxy isn’t answering the way expected. ERROR: rtpengine [rtpengine.c:1622]: rtpp_test(): proxy responded with invalid response Any advise would be nice. Thank you Fred

2 2

Re: [SR-Users] P-CSCF
by Aaron Hamstra 30 Jan '16

30 Jan '16

Fred, I think you would need to use rtpengine instead of rtpproxy. https://github.com/sipwise/rtpengine -Aaron From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Fred Schulz Sent: Thursday, January 28, 2016 1:24 PM To: sr-users(a)lists.sip-router.org Subject: [SR-Users] P-CSCF Hi all, we’re just playing around with an IMS setup bases on kamailio. Therefore the kamailio is used as P-,I- and S-CSCF. We where able to register two clients through all components. As we wan to start a call session, the P-CSCF answers with „403 - Forbidden. You must register with an S-CSCF“… I found this snippet in kamailio.cfg: if (!pcscf_is_registered("location")) { send_reply("403","Forbidden - You must register first with a S-CSCF“); break; } Can one tell me what exactly the kamailio is checking there? As I figured out it is looking in database location table. The table contains the registered users registered towards the IMS. Another „problem“ we faced with is the rtpproxy. As the ngcp-mediaproxy-ng is no longer available and replaced with rtpproxy we’re trying to use it. But kamailio said that the proxy isn’t answering the way expected. ERROR: rtpengine [rtpengine.c:1622]: rtpp_test(): proxy responded with invalid response Any advise would be nice. Thank you Fred

2 1

Re: [SR-Users] Kamailio IMS deployment
by sainath.ellendula＠wipro.com 30 Jan '16

30 Jan '16

Hi Basit, Thanks for response. I have tried the below commands to grant all privileges. The commands results OK. Still I was facing the same issue which is mentioned in trailing mail. Could anyone guide me here to proceed further. Any suggestions/solutions would be very helpful. Regards, Sainath ---------- Forwarded message ---------- From: "Abdul Basit" <basitstar(a)hotmail.com<mailto:basitstar@hotmail.com>> Date: Jan 27, 2016 7:37 PM Subject: Re: [SR-Users] Kamailio IMS deployment To: "Kamailio SER - Users Mailing List" <sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org>>, "franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>" <franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>> Cc: use the following command and try again.. GRANT ALL PRIVILEGES ON *.* TO '<user>'@'<hostname>' IDENTIFIED BY '<password>'; GRANT ALL PRIVILEGES ON *.* TO '<user>'@'%' IDENTIFIED BY '<password>'; FLUSH PRIVILEGES; regards, AB ________________________________ From: sainath.ellendula(a)wipro.com<mailto:sainath.ellendula@wipro.com> To: franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at> Date: Wed, 27 Jan 2016 06:21:52 +0000 CC: sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> Subject: Re: [SR-Users] Kamailio IMS deployment Hi Franz, Thanks for the response. As suggested followed below commands to check the GRANTs on database hss_db. mysql -u root -p show grants for 'hss'@'server.net1.test'; The output result is same as mentioned below. Could you please guide me here to proceed further. Regards, Sainath ---------- Forwarded message ---------- From: "Franz Edler" <franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>> Date: Jan 27, 2016 1:07 AM Subject: RE: [SR-Users] Kamailio IMS deployment To: "Kranti Kumar" <krantikumara(a)gmail.com<mailto:krantikumara@gmail.com>>, "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org>> Cc: "Ramya Y" <y.ramya146(a)gmail.com<mailto:y.ramya146@gmail.com>> Obviously the access of HSS to the database did not succeed. You should check if access permissions to the database is enabled for HSS. Check the GRANTs on the database hss_db. mysql -u root -p show grants for 'hss'@'server.net1.test'; quit; The result should be: +-------------------------------------------------------------------------------------------------------------------+ | Grants for hss(a)server.net1.test<mailto:hss@server.net1.test> | +-------------------------------------------------------------------------------------------------------------------+ | GRANT USAGE ON *.* TO 'hss'@'server.net1.test' IDENTIFIED BY PASSWORD '*AC83FCF24B79020EF2C51D780CDFA559F25CC9BE' | | GRANT SELECT, INSERT, UPDATE, DELETE ON `hss_db`.* TO 'hss'@'server.net1.test' | +-------------------------------------------------------------------------------------------------------------------+ BR Franz From: Kranti Kumar [mailto:krantikumara@gmail.com<mailto:krantikumara@gmail.com>] Sent: Sunday, January 24, 2016 10:55 AM To: franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>; Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org>> Cc: Ramya Y <y.ramya146(a)gmail.com<mailto:y.ramya146@gmail.com>> Subject: Re: [SR-Users] Kamailio IMS deployment Thanks a lot Franz. Observed few issues even after changes done in /etc/bind. Please find the below Errors in each interfaces and also find the attachment of /var/log/syslog(not shared full logs) Could you please help me here to proceed further. HSS – Configured IP : 10.0.0.9 root@server:~# ./hss.sh – Configured IP : 10.0.0.9 Building Classpath Classpath is lib/xml-apis.jar:lib/xercesImpl.jar:lib/xerces-2.4.0.jar:lib/xalan-2.4.0.jar:lib/tomcat-util.jar:lib/tomcat-http.jar:lib/tomcat-coyote.jar:lib/struts.jar:lib/servlets-default.jar:lib/servlet-api.jar:lib/naming-resources.jar:lib/naming-factory.jar:lib/mysql-connector-java-3.1.12-bin.jar:lib/mx4j-3.0.1.jar:lib/log4j.jar:lib/junit.jar:lib/junitee.jar:lib/jta.jar:lib/jsp-api.jar:lib/jmx.jar:lib/jdp.jar:lib/jasper-runtime.jar:lib/jasper-compiler-jdt.jar:lib/jasper-compiler.jar:lib/hibernate3.jar:lib/FHoSS.jar:lib/ehcache-1.1.jar:lib/dom4j-1.6.1.jar:lib/commons-validator.jar:lib/commons-modeler.jar:lib/commons-logging.jar:lib/commons-logging-1.0.4.jar:lib/commons-lang.jar:lib/commons-fileupload.jar:lib/commons-el.jar:lib/commons-digester.jar:lib/commons-collections-3.1.jar:lib/commons-beanutils.jar:lib/cglib-2.1.3.jar:lib/catalina-optional.jar:lib/catalina.jar:lib/c3p0-0.9.1.jar:lib/base64.jar:lib/asm.jar:lib/asm-attrs.jar:lib/antlr-2.7.6.jar::log4j.properties:.. 2016-01-21 14:07:07,876 INFO de.fhg.fokus.hss.main.TomcatServer - startTomcat Tomcat-Server is started. 2016-01-21 14:07:12,462 WARN org.apache.catalina.connector.MapperListener - registerEngine Unknown default host: 10.0.0.9 2016-01-21 14:07:16,578 INFO de.fhg.fokus.hss.web.servlet.ResponseFilter - init Response Filter Initialisation! 2016-01-21 14:07:17,966 INFO de.fhg.fokus.hss.main.TomcatServer - startTomcat WebConsole of FHoSS was started ! 2016-01-21 14:08:21,200 WARN com.mchange.v2.resourcepool.BasicResourcePool - run com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1670988b<mailto:com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1670988b> -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (60). Last acquisition attempt exception: com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception: ** BEGIN NESTED EXCEPTION ** java.net.SocketException MESSAGE: java.net.ConnectException: Connection refused STACKTRACE: java.net.SocketException: java.net.ConnectException: Connection refused PCSCF – Configured IP : 10.0.0.10 root@server:~# kamailio -f /usr/local/etc/kamailio/kamailio-pcscf.cfg loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(2352) INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: pcscf.net1.test [10.0.0.10]:4060 Aliases: *: pcscf.net1.test:* WARNING: no fork mode 0(2352) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(2352) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available 0(2352) INFO: ims_usrloc_pcscf [hslot.c:62]: ul_init_locks(): locks array size 512 0(2352) INFO: <core> [udp_server.c:150]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(2352) INFO: <core> [udp_server.c:200]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(2352) WARNING: ims_usrloc_pcscf [usrloc_db.c:59]: connect_db(): DB connection already open... continuing ^C^C 0(2352) NOTICE: <core> [main.c:683]: handle_sigs(): Thank you for flying kamailio!!! 1(2373) INFO: <core> [main.c:798]: sig_usr(): signal 15 received 2(2374) INFO: <core> [main.c:798]: sig_usr(): signal 15 received 0(2352) INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ICSCF – Configured IP : 10.0.0.11 root@server:~# kamailio -f /usr/local/etc/kamailio/kamailio-icscf.cfg loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(2353) INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: icscf.net1.test [10.0.0.11]:5060 Aliases: *: icscf.net1.test:* WARNING: no fork mode 0(2353) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(2353) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available 0(2353) INFO: <core> [udp_server.c:150]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(2353) INFO: <core> [udp_server.c:200]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(2353) INFO: cdp [mod.c:227]: cdp_child_init(): CDiameterPeer child starting ... 0(2353) INFO: cdp [mod.c:229]: cdp_child_init(): ... CDiameterPeer child started 10(2370) INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... 6(2366) INFO: cdp [worker.c:331]: worker_process(): [3] Worker process started... 7(2367) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... 7(2367) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [] Receiver process starting up... 8(2368) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [hss.net1.test] Receiver process doing init on new process... 8(2368) INFO: cdp [receiver.c:183]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [hss.net1.test] 9(2369) INFO: cdp [acceptor.c:82]: acceptor_process(): Acceptor process starting up... 9(2369) WARNING: cdp [tcp_accept.c:123]: create_socket(): create_socket(): Trying to open/bind/listen on 10.0.0.9 port 3869 9(2369) WARNING: cdp [tcp_accept.c:148]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.0.0.9 port 3869 9(2369) INFO: cdp [acceptor.c:96]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 8(2368) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [hss.net1.test] Receiver process starting up... 10(2370) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2370) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2370) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2370) WARNING: cdp [receiver.c:911]: peer_connect(): peer_connect(): Error opening connection to to 10.0.0.9 port 3868 >Connection refused 10(2370) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2370) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2370) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2370) INFO: cdp [receiver.c:932]: peer_connect(): peer_connect(): Peer hss.net1.test:3868 connected 10(2370) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 10(2370) WARNING: cdp [peermanager.c:315]: peer_timer(): Inactivity on peer [hss.net1.test], sending DWR... - if we don't get a reply, the peer will be closed 8(2368) INFO: cdp [receiver.c:802]: receive_loop(): select_recv(): [hss.net1.test] read on socket [14] returned 0 > ... dropping 8(2368) INFO: cdp [receiver.c:219]: disconnect_serviced_peer(): drop_serviced_peer(): [hss.net1.test] Disconnecting from peer ^C10(2370) INFO: <core> [main.c:798]: sig_usr(): signal 2 received 0(2353) ALERT: <core> [main.c:725]: handle_sigs(): child process 2361 exited normally, status=0 0(2353) INFO: <core> [main.c:740]: handle_sigs(): dont_fork turned on, living on 0(2353) NOTICE: <core> [main.c:683]: handle_sigs(): Thank you for flying kamailio!!! 2(2362) INFO: <core> [main.c:798]: sig_usr(): signal 15 received 0(2353) INFO: cdp [mod.c:242]: cdp_exit(): CDiameterPeer child stopping ... 0(2353) INFO: cdp [diameter_peer.c:428]: diameter_peer_destroy(): destroy_diameter_peer(): Terminating all children... 0(2353) INFO: cdp [diameter_peer.c:435]: diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child [2370] to terminate... 0(2353) INFO: cdp [diameter_peer.c:447]: diameter_peer_destroy(): destroy_diameter_peer(): All processes terminated. Cleaning up. 0(2353) INFO: cdp [worker.c:140]: worker_destroy(): Unlocking workers waiting on empty queue... 0(2353) INFO: cdp [worker.c:143]: worker_destroy(): Unlocking workers waiting on full queue... 0(2353) CRITICAL: cdp [diameter_peer.c:487]: diameter_peer_destroy(): destroy_diameter_peer(): Bye Bye from C Diameter Peer test 0(2353) INFO: cdp [mod.c:244]: cdp_exit(): ... CDiameterPeer child stoped 0(2353) INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized SCSCF – Configured IP : 10.0.0.12 root@server:/etc# kamailio -f /usr/local/etc/kamailio/kamailio-scscf.cfg loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(2371) INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: scscf.net1.test [10.0.0.12]:6060 Aliases: *: scscf.net1.test:* WARNING: no fork mode 0(2371) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(2371) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available 0(2371) INFO: ims_usrloc_scscf [hslot.c:69]: ul_init_locks(): locks array size 512 0(2371) INFO: ims_usrloc_scscf [hslot_sp.c:67]: subs_init_locks(): locks array size 512 0(2371) INFO: ims_usrloc_scscf [contact_hslot.c:67]: init_contacts_locks(): locks array size 512 0(2371) INFO: <core> [udp_server.c:150]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(2371) INFO: <core> [udp_server.c:200]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(2371) INFO: cdp [mod.c:227]: cdp_child_init(): CDiameterPeer child starting ... 0(2371) INFO: cdp [mod.c:229]: cdp_child_init(): ... CDiameterPeer child started 3(2381) INFO: cdp [worker.c:331]: worker_process(): [0] Worker process started... 4(2382) INFO: cdp [worker.c:331]: worker_process(): [1] Worker process started... 5(2383) INFO: cdp [worker.c:331]: worker_process(): [2] Worker process started... 7(2390) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... 7(2390) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [] Receiver process starting up... 8(2392) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [hss.net1.test] Receiver process doing init on new process... 8(2392) INFO: cdp [receiver.c:183]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [hss.net1.test] 8(2392) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [hss.net1.test] Receiver process starting up... 9(2393) INFO: cdp [acceptor.c:82]: acceptor_process(): Acceptor process starting up... 9(2393) WARNING: cdp [tcp_accept.c:123]: create_socket(): create_socket(): Trying to open/bind/listen on 10.0.0.9 port 3870 9(2393) WARNING: cdp [tcp_accept.c:148]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.0.0.9 port 3870 9(2393) INFO: cdp [acceptor.c:96]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 10(2394) INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2394) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2394) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2394) WARNING: cdp [receiver.c:911]: peer_connect(): peer_connect(): Error opening connection to to 10.0.0.9 port 3868 >Connection refused 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2394) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2394) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2394) INFO: cdp [receiver.c:932]: peer_connect(): peer_connect(): Peer hss.net1.test:3868 connected 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 10(2394) WARNING: cdp [peermanager.c:315]: peer_timer(): Inactivity on peer [hss.net1.test], sending DWR... - if we don't get a reply, the peer will be closed 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 8(2392) INFO: cdp [receiver.c:802]: receive_loop(): select_recv(): [hss.net1.test] read on socket [15] returned 0 > ... dropping 8(2392) INFO: cdp [receiver.c:219]: disconnect_serviced_peer(): drop_serviced_peer(): [hss.net1.test] Disconnecting from peer 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2394) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2394) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2394) WARNING: cdp [receiver.c:911]: peer_connect(): peer_connect(): Error opening connection to to 10.0.0.9 port 3868 >Connection refused ^C11(2398) INFO: <core> [main.c:798]: sig_usr(): signal 2 received 9(2393) INFO: <core> [main.c:798]: sig_usr(): signal 2 received 0(2371) ALERT: <core> [main.c:725]: handle_sigs(): child process 2381 exited normally, status=0 0(2371) INFO: <core> [main.c:740]: handle_sigs(): dont_fork turned on, living on 0(2371) NOTICE: <core> [main.c:683]: handle_sigs(): Thank you for flying kamailio!!! 10(2394) INFO: <core> [main.c:798]: sig_usr(): signal 15 received 0(2371) INFO: cdp [mod.c:242]: cdp_exit(): CDiameterPeer child stopping ... On Fri, Jan 22, 2016 at 2:16 AM, Franz Edler <franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>> wrote: Hi, you can see the first error is a database error: ERROR: db_mysql [km_my_con.c:124]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on 'server.net1.test' (111) This error I expected because you have to adapt the access permissions to the database. Just check the GRANT statements in my log-file and try to understand what they do. Then adapt it accordingly. BR Franz From: Ramya Y [mailto:y.ramya146@gmail.com<mailto:y.ramya146@gmail.com>] Sent: Wednesday, January 20, 2016 2:19 PM To: franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>; Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org>> Subject: Re: [SR-Users] Kamailio IMS deployment Hi Franz we have tried with different interfaces(eth0(10.0.0.9),eth1(10.0.0.10),eth2(10.0.0.11),eth3(10.0.0.12) for P/I/S ,but facing below error. root@server:/etc# kamailio -f /usr/local/etc/kamailio/kamailio-pcscf.cfg loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(1630) INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: pcscf.net1.test [10.0.0.10]:4060 Aliases: *: pcscf.net1.test:* WARNING: no fork mode 0(1630) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(1630) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available 0(1630) INFO: ims_usrloc_pcscf [hslot.c:62]: ul_init_locks(): locks array size 512 0(1630) ERROR: db_mysql [km_my_con.c:124]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on 'server.net1.test' (111) 0(1630) ERROR: <core> [db.c:318]: db_do_init2(): could not add connection to the pool 0(1630) ERROR: ims_usrloc_pcscf [usrloc_db.c:79]: init_db(): unable to connect to the database 0(1630) ERROR: ims_usrloc_pcscf [ul_mod.c:203]: mod_init(): Error initializing db connection 0(1630) ERROR: <core> [sr_module.c:962]: init_mod(): Error while initializing module ims_usrloc_pcscf (/usr/local/lib64/kamailio/modules/ims_usrloc_pcscf.so) ERROR: error while initializing modules 0(1630) INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialize could you please help me how to proceed further, steps followed: =========== 1)Modified at - /etc/network/interfaces: created eth1,eth2,eth3 for P/I/S-CSCF. Interfaces are up. 2)Added Bind address at /etc/mysql/my.cnf bind-address 10.0.0.9 bind-address 10.0.0.10 bind-address 10.0.0.11 bind-address 10.0.0.12 3)Modified at /etc/bind/net1.test.zone $ORIGIN net1.test. $TTL 1W @ 1D IN SOA serverkde. root.net1.test ( 2010081401 ; Serial YYYYMMDDXX 3H ; refresh 15M ; retry 1W ; expiry 1D ) ; minimum 1D IN NS server server 1D IN A 10.0.0.9 hss 1D IN CNAME server as1 1D IN CNAME server as2 1D IN CNAME server xcap 1D IN CNAME server server1 1D IN A 10.0.0.10 pcscf 1D IN CNAME server1 server2 1D IN A 10.0.0.11 icscf 1D IN CNAME server2 server3 1D IN A 10.0.0.12 scscf 1D IN CNAME server3 4)Modified at /etc/bind/0.0.10.zone $TTL 86400 @ IN SOA server. root.net2.test ( 2010081401 ; Serial YYYYMMDDXX 28800 ; Refresh 14400 ; Retry 3600000 ; Expire 86400 ) ; Minimum IN NS server.net1.test. IN NS server1.net1.test. IN NS server2.net1.test. IN NS server3.net1.test. 10 IN PTR notebook.net1.test. 9 IN PTR server.net1.test. 7 IN PTR server.net2.test. 5)Modified at /etc/resolve.conf domain net1.test search net1.test nameserver server.net1.test nameserver server1.net1.test nameserver server2.net1.test nameserver server3.net1.test 6)Modified at /etc/hosts 127.0.0.1 localhost 10.0.0.9 server.net1.test server 10.0.0.10 server1.net1.test server1 10.0.0.11 server2.net1.test server2 10.0.0.12 server3.net1.test server3 10.0.0.9 net1.test 10.0.0.10 pcscf.net1.test 10.0.0.11 icscf.net1.test 10.0.0.12 scscf.net1.test Thanks, Ramyasri. On Sun, Jan 17, 2016 at 5:33 PM, Franz Edler <franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>> wrote: Fine. This exactly was my intention. BR Franz > -----Original Message----- > From: sr-users [mailto:sr-users-bounces@lists.sip-router.org<mailto:sr-users-bounces@lists.sip-router.org>] On Behalf Of > Vasiliy Ganchev > Sent: Monday, January 11, 2016 9:08 AM > To: sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> > Subject: Re: [SR-Users] Kamailio IMS deployment > > Hi Franz! > > Thanks for sharing! Great job, end excellent materials to get started with > students (beside my main work I also teach students in Odessa National > Academy of Telecommunication). > I was looking for some "light" way how to start with real deployment of IMS, > not pure theory, and this is just the kind I wanted! > > Will try your deploy in education process this year. (will share the results in > the end) > > Cheers! > > > > -- > View this message in context: http://sip- > router.1086192.n5.nabble.com/Kamailio-IMS-deployment-<http://router.1086192.n5.nabble.com/Kamailio-IMS-deployment-> > tp143593p144517.html > Sent from the Users mailing list archive at Nabble.com. > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr- > users(a)lists.sip-router.org<mailto:users@lists.sip-router.org> http://lists.sip-router.org/cgi- > bin/mailman/listinfo/sr-users _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com> _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

2 3

Re: [SR-Users] [sr-dev] Fosdem 2016
by Daniel-Constantin Mierla 29 Jan '16

29 Jan '16

Hello, ok, let's see how many we are going to be and then decide how to do it (if we are not a large group, we can just go in the city center and walk around for a place). Cheers, Daniel On 06/01/16 02:30, Alexandr Dubovikov wrote: > Hello Daniel, > > I will be there, plus Lorenzo and Torsen. Make a small event on > Saturday will be very cool, but not at Beer Mania :-) > > Wbr, > Alexandr > > On 05.01.2016 20:06, Daniel-Constantin Mierla wrote: >> Hello, >> >> anyone going to Fosdem? >> >> If no unexpected weather conditions messing the transport system, I am >> going to be there. It would be good to know who else we can meet there. >> >> If there are enough people interested, we can try organizing a social >> event (dinner/drinks) on Saturday evening. Last year we did it together >> with Jitsi team, but they are not coming this year. Perhaps there are >> other folks around the RTC dev room we can ask. >> >> On the other hand, it is harder to find a place if it is a large group, >> even harder to put all together if there are different >> groups/coordinators. Also, it is not easy to discuss withing a large >> group, as typically for a dinner we were seated to tables. Therefore >> organizing for a smaller group just for Kamailio friends could be a good >> alternative. Let's see first the number of participant and the level of >> interest for various options. >> >> This being an announcement, was crossposted to few mailing lists, but as >> most of the people are on sr-users, I think it would be good to reply >> and follow up on this discussion only there. >> >> Cheers, >> Daniel >> > > > _______________________________________________ > sr-dev mailing list > sr-dev(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

5 6

Memory issue?
by Igor Potjevlesch 29 Jan '16

29 Jan '16

Hello, I got several errors this morning on a Kamailio instance. The first occurred without a complete crash of Kamailio but 4 coredumps have been created: BFD: Warning: /core.3818 is truncated: expected core file size >= 342618112, found: 61579264. [New Thread 3818] Cannot access memory at address 0x7f66e0557658 BFD: Warning: /core.3821 is truncated: expected core file size >= 343044096, found: 21229568. [New Thread 3821] Cannot access memory at address 0x7f66e0557658 BFD: Warning: /core.3822 is truncated: expected core file size >= 342675456, found: 120066048. [New Thread 3822] Cannot access memory at address 0x7f66e0557658 BFD: Warning: /core.3839 is truncated: expected core file size >= 342401024, found: 2691072. [New Thread 3839] Cannot access memory at address 0x3d6f021168 Cannot access memory at address 0x3d6f021168 Cannot access memory at address 0x3d6f021168 It seems that Kamailio auto recovered without fully crashed during this issue. But the Kamailio FIFO was deleted and kamctl didn't worked anymore. I had to properly restart. I have seen in the logs: Jan 21 10:21:11 /usr/local/sbin/kamailio[3843]: ERROR: <core> [dtrie.c:153]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:11 /usr/local/sbin/kamailio[3839]: ERROR: <core> [dtrie.c:144]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:11 /usr/local/sbin/kamailio[3839]: ERROR: userblacklist [db.c:91]: db_build_userbl_tree(): could not insert values into trie. Jan 21 10:21:11 /usr/local/sbin/kamailio[3843]: ERROR: userblacklist [db.c:91]: db_build_userbl_tree(): could not insert values into trie. Jan 21 10:21:11 /usr/local/sbin/kamailio[3831]: ERROR: <core> [dtrie.c:144]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:11 /usr/local/sbin/kamailio[3831]: ERROR: userblacklist [db.c:91]: db_build_userbl_tree(): could not insert values into trie. Jan 21 10:21:11 /usr/local/sbin/kamailio[3841]: ERROR: <core> [dtrie.c:153]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:12 /usr/local/sbin/kamailio[3821]: ERROR: <core> [dtrie.c:153]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:12 /usr/local/sbin/kamailio[3821]: ERROR: userblacklist [db.c:91]: db_build_userbl_tree(): could not insert values into trie. Jan 21 10:21:12 /usr/local/sbin/kamailio[3828]: ERROR: <core> [dtrie.c:153]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:12 /usr/local/sbin/kamailio[3843]: ERROR: <core> [dtrie.c:153]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:12 /usr/local/sbin/kamailio[3818]: ERROR: <core> [dtrie.c:144]: dtrie_insert(): could not allocate shared memory from available pool Jan 21 10:21:12 /usr/local/sbin/kamailio[3818]: ERROR: userblacklist [db.c:91]: db_build_userbl_tree(): could not insert values into trie. [.] Jan 21 10:21:13 kernel: kamailio[3818]: segfault at 40 ip 00007f66d8812af2 sp 00007fff09c83380 error 4 in libtrie.so.1.0[7f66d8810000+5000] Jan 21 10:21:13 kernel: kamailio[3822]: segfault at 20 ip 00007f66d8812af2 sp 00007fff09c83380 error 4 in libtrie.so.1.0[7f66d8810000+5000] Jan 21 10:21:14 kernel: kamailio[3821]: segfault at 0 ip 00007f66d8812af2 sp 00007fff09c83380 error 4 in libtrie.so.1.0[7f66d8810000+5000] [.] Jan 21 10:21:14 /usr/local/sbin/kamailio[3807]: ALERT: <core> [main.c:784]: handle_sigs(): child process 3828 exited by a signal 11 Jan 21 10:21:14 /usr/local/sbin/kamailio[3807]: ALERT: <core> [main.c:787]: handle_sigs(): core was not generated Jan 21 10:21:14 /usr/local/sbin/kamailio[3807]: ALERT: <core> [main.c:784]: handle_sigs(): child process 3825 exited by a signal 11 Jan 21 10:21:14 /usr/local/sbin/kamailio[3807]: ALERT: <core> [main.c:787]: handle_sigs(): core was not generated Jan 21 10:21:14 /usr/local/sbin/kamailio[3807]: INFO: <core> [main.c:799]: handle_sigs(): terminating due to SIGCHLD Jan 21 10:21:14 /usr/local/sbin/kamailio[3832]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Jan 21 10:21:14 /usr/local/sbin/kamailio[3841]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received Jan 21 10:21:14 /usr/local/sbin/kamailio[3876]: INFO: <core> [main.c:850]: sig_usr(): signal 15 received 1 hour later a new crash but here Kamailio has completely restarted with two coredump showing the same error than previous one. And 2 coredumps readable: Core was generated by `/usr/local/sbin/kamailio -P /var/run/kamailio.pid -m 256 -M 64'. Program terminated with signal 11, Segmentation fault. #0 0x00007f13a1550af2 in dtrie_insert (root=0x7f138d7ffb38, number=0x22ba6c0 "003716716", numberlen=9, data=0x2, branches=10) at dtrie.c:141 141 if (node->child[digit] == NULL) { Core was generated by `/usr/local/sbin/kamailio -P /var/run/kamailio.pid -m 256 -M 64'. Program terminated with signal 11, Segmentation fault. #0 0x00007f13a1550af2 in dtrie_insert (root=0x7f138d7ff998, number=0x22b57a8 "0035587482", numberlen=10, data=0x2, branches=10) at dtrie.c:141 141 if (node->child[digit] == NULL) { Kamailio is 4.2.6 on this instance. Regards, Igor.

3 4

RTP Statistics
by Gholamreza Sabery 29 Jan '16

29 Jan '16

Hello everyone. I want to store RTCP Statistics for a RTP session. Currently I am using $rtpstat pseudo-variable which is exported by RTPProxy module. The value of this variable does not show actual number of packets sent and received; and only contains ttl, npkts_ina, npkts_ino, nrelayed and ndropped. I want actual number of packets sent from and actual number of packets received by a client. How can I obtain this information?

2 3

Presence: Notify on publication status refresh
by Aleš Šturm 28 Jan '16

28 Jan '16

Hi all, I am using Kamailio 4.3 as Presence server and I have a question regarding NOTIFY messages sent after publication status refresh. When PUA sends refreshing PUBLISH request (before expiration) Kamailio sends NOTIFY request. Large number of watchers per one presentity causes large traffic. RFC3265 states: NOTIFY messages are sent to inform subscribers of changes in state to which the subscriber has a subscription. But when publication is only refreshed (publication expiration is extended) the publish state is not changed (PUBLISH without XML body). >From RFC5839: The SIP PUBLISH [RFC3903] method uses a similar mechanism, where a refresh of a publication is done by reference to its assigned entity-tag, instead of retransmitting the event state each time the publication expiration is extended. Is it possible to configure Kamailio that wouldn't send NOTIFY request to watchers when publication status refresh (PUBLISH without XML Body) occur? Can anyone help? Thanks in advance, Ales

3 5

Is "new_conn_alias_flags" supported/recommended? It seems to solve my NAT problem, but I'm worried it's not safe.
by Cody Herzog 28 Jan '16

28 Jan '16

Hello. In a test environment, I've been able to use the "new_conn_alias_flags" option to solve a NAT problem, but I'm concerned that the option is not supported/safe. It seems the option is not documented, and cannot be used in the config file, because 'cfg.y' doesn't support parsing it. However, it can be set at runtime using a command such as the following: kamctl kamcmd cfg.set_now_int tcp new_conn_alias_flags 1 **Question #1** Is this option experimental and/or risky? As background, I will now try to describe my NAT problem. Perhaps there is an alternate way to solve my problem which doesn't require using "new_conn_alias_flags". My server architecture uses multiple Kamailio edge proxies, and a single central Kamailio registrar. The edge proxies listen on multiple TLS ports. All servers are on version 4.3.3. My client app includes a port tester, which periodically tests whether certain SIP proxy targets are reachable. These test connections are very brief, and don’t persist. The problem seems to relate to a behavior of iptables as follows: Client A and client B are both behind the same iptables NAT. Client A has a persistent TLS connection to one of the proxies. Client B is doing periodic port testing, and sometimes, the itpables NAT will assign exactly the same external IP and port for a test connection as is already being used by client A for its persistent connection, to the same SIP proxy IP. Only the SIP proxy target port is different. To better explain, I will list out examples for all the relevant IPs and ports along the paths. The IPs and ports I've selected are arbitrary. Client A persistent TLS connection ---------------------------------- Internal IP:Port = 10.10.10.100:30000 External IP:Port = 88.88.88.88:10000 SIP proxy IP:Port = 66.66.66.66:5061 Client B port test connection ------------------------------ Internal IP:Port = 10.10.10.101:35000 External IP:Port = 88.88.88.88:10000 *** Same as above! SIP proxy IP:Port = 66.66.66.66:443 *** SIP proxy port being different is the only thing that makes this a distinct TCP connection from above. When this happens, it seems that some of the TCP connection/alias hash tables inside Kamailio are modified such that future attempts to call client A may fail. Client B's port test connection seems to overwrite some of the state which was important for connections into Client A. After client B's test connection has stomped on client A's state, this is what happens: When an INVITE sent to client A arrives at the proxy, the proxy fails to find the matching persistent TLS connection which already exists, so it tries to open a new outbound TLS connection to client A, but that always fails because client A's NAT doesn't allow it. Such calls end up failing with a 408 timeout error. I added some extra logging to the TCP connection/alias hash code paths, and I can see some of the client A entries being overwritten when client B makes its test connection. Did I explain that well enough? I know it's a bit confusing. Anyway, after doing some code inspection, I noticed that the "new_conn_alias_flags" option seemed like it might improve this problem, or at least change the behavior. It turns out that setting "new_conn_alias_flags" equal to 1 seems to solve my problem. With that setting, client B's test connections do not overwrite any of the TCP connection hashes/aliases for client A's persistent TLS connection, and calls into client A never seem to fail. **Question #2** Does setting "new_conn_alias_flags" to 1 seem like a good way to address my type of problem? If not, is there an alternate way to solve my problem? Perhaps there are some things I should be doing with the NAT helper module that could fix the issue without relying on "new_conn_alias_flags"? I realize that I may need to provide more information to answer these questions fully, but I’m initially hoping to just get some high-level impressions, without going into a ton of details. Thanks.

2 6

kamailio 4.4 writes wrong expires parameter at the database
by Yuriy Gorlichenko 27 Jan '16

27 Jan '16

2 3

Fwd: Invalid Configuration File
by Andrew J. Smith 27 Jan '16

27 Jan '16

Hello! I followed this tutorial (http://kb.asipto.com/kamailio:skype-like-service-in-less-than-one-hour) to the T using virtual box and a debian wheezy image. Actually, I did change one thing: This repository "deb http://deb.kamailio.org/kamailio31-nightly squeeze main" always resulted in a file not found error. So I used these two lines instead: deb http://deb.kamailio.org/kamailio squeeze main deb-src http://deb.kamailio.org/kamailio squeeze main Everything else is fine except for the fact that the MySQL users have different names/passwords. I was able to generate users and configured everything as posted. When I start the service (/etc/init.d/kamailio start) I get an error message: "Not starting Kamailio SIP Server: invalid configuration file! ... failed! failed!" followed by a looooooong list of errors (copied below). I retried with Kamailio33 (31 is not available as far as I can tell). This version has the MySQL users indicated in the tutorial (openser, openserro) - newer versions have a MySQL user named kamailio... Anyway, same long list of errors as before. I also tried the same procedure on a Raspberry Pi... Everything goes exactly as described until I try to start the Kamailio server. If I don't replace the original kamailio.cfg file with the one linked to in the tutorial, the server starts, but I can't seem to connect to it using Jitsi. What am I doing wrong? Any help would be greatly appreciated. Best regards, Andrew -------------------------------------------------------- 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <db_mysql> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 191, column 12-24: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <mi_fifo> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 194, column 12-23: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <kex> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 195, column 12-19: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <tm> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 196, column 12-18: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <tmx> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 197, column 12-19: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <sl> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 198, column 12-18: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <rr> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 199, column 12-18: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <pv> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 200, column 12-18: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <maxfwd> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 201, column 12-22: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <usrloc> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 202, column 12-22: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <registrar> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 203, column 12-25: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <textops> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 204, column 12-23: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <siputils> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 205, column 12-24: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <xlog> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 206, column 12-20: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <sanity> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 207, column 12-22: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <ctl> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 208, column 12-19: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <mi_rpc> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 209, column 12-22: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <acc> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 210, column 12-19: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <auth> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 213, column 12-20: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <auth_db> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 214, column 12-23: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <nathelper> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 234, column 12-25: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <rtpproxy> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 235, column 12-24: failed to load module 0(20143) ERROR: <core> [sr_module.c:565]: load_module(): could not find module <tls> in </usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/> 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 239, column 12-19: failed to load module 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <mi_fifo> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 255, column 54: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <tm> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 260, column 39: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <tm> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 262, column 33: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <tm> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 264, column 38: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <rr> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 269, column 35: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <rr> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 271, column 35: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <registrar> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 275, column 44: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <acc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 284, column 33: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <acc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 285, column 32: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <acc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 286, column 36: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <acc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 290, column 38: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <acc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 292, column 30: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <acc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 293, column 37: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <acc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 295, column 73: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <acc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 296, column 45: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <usrloc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 310, column 75: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <usrloc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 311, column 32: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <usrloc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 312, column 35: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <auth_db> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 318, column 76: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <auth_db> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 319, column 41: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <auth_db> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 320, column 50: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <auth_db> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 321, column 43: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <auth_db> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 322, column 36: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <rtpproxy> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 363, column 77: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <nathelper> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 366, column 45: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <nathelper> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 367, column 43: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <nathelper> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 368, column 41: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <nathelper> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 369, column 64: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <nathelper|registrar> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 372, column 65: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <usrloc> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 373, column 34: Can't set module parameter 0(20143) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <tls> found 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 379, column 50: Can't set module parameter 0(20143) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command is_method (params 1) 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 418, column 24: unknown command, missing loadmodule? 0(20143) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command t_check_trans (params 0) 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 420, column 21: unknown command, missing loadmodule? 0(20143) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command t_relay (params 0) 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 421, column 12: unknown command, missing loadmodule? 0(20143) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command t_check_trans (params 0) 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 425, column 16: unknown command, missing loadmodule? 0(20143) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command remove_hf (params 1) 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 432, column 19: unknown command, missing loadmodule? 0(20143) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command is_method (params 1) 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 433, column 34: unknown command, missing loadmodule? 0(20143) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command record_route (params 0) 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 434, column 16: unknown command, missing loadmodule? 0(20143) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command is_method (params 1) 0(20143) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 437, column 24: unknown command, missing loadmodule? 0(20143) ERROR: <core> [pvapi.c:825]: pv_parse_spec2(): error searching pvar "rU" 0(20143) ERROR: <core> [pvapi.c:1029]: pv_parse_spec2(): wrong char [U/85] in [$rU] at [2 (0)] 0(20143) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 453, column 6-8: Can't get from cache: $rU ERROR: bad config file (63 errors) 0(20143) INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ... failed! failed! --------------------------------------------------------

2 1

doubt using sip tcp creating new transaction
by david escartin 27 Jan '16

27 Jan '16

hello all i'm facing some weird log from kamailio (i think they are weird) when using sip tcp in the caller side and udp in the callee side. seems like the tcp socket is active in the caller side and the call is connected, since the invite transaction completes. After that, if we receive an in-dialog request from the callee side, the kamailio doesnt find the tcp connection created and it has to create again the socket by SYN procedure for the other conn way. up to this point i think it's everything correct. A----the thing i dont understand, is that checking version 4.2.6, the logs i have when the request in-dialog comes from UAS, are like these 5(2979) DEBUG: <core> [tcp_main.c:1820]: tcp_send(): tcp_send: no open tcp connection found, opening new one 5(2979) DEBUG: <core> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 79.170.68.171 5(2979) DEBUG: <core> [tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 5063, type 2 5(2979) DEBUG: <core> [tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 1522:2178:0, 4 5(2979) DEBUG: <core> [tcp_main.c:2699]: tcpconn_1st_send(): pending write on new connection 0x7fac1168f028 (-1/968 bytes written) 5(2979) DEBUG: tm [t_funcs.c:395]: t_relay_to(): SER: new transaction fwd'ed B----while when using 4.2.2 or 4.4 1(791) DEBUG: <core> [tcp_main.c:1818]: tcp_send(): tcp_send: no open tcp connection found, opening new one 1(791) DEBUG: <core> [ip_addr.c:243]: print_ip(): tcpconn_new: new tcp connection: 79.170.68.171 1(791) DEBUG: <core> [tcp_main.c:1073]: tcpconn_new(): tcpconn_new: on port 5063, type 2 1(791) DEBUG: <core> [tcp_main.c:1382]: tcpconn_add(): tcpconn_add: hashes: 1522:3421:0, 4 1(791) INFO: <core> [tcp_main.c:2753]: tcpconn_1st_send(): quick connect for 0x7f880540f758 1(791) DEBUG: tm [t_funcs.c:394]: t_relay_to(): SER: new transaction fwd'ed the difference between A and B is that in B i use dialog flags to do the t_relay_to_tcp for the indialog requests (and not in A), and in A i use the advertised IP in the listen addresses since kamailio is behind a NAT, while B machine scenario has public IPs. could those 2 things explain the ebhaviour difference? is there anything abnormal in the case B? thanks a lot and regards david escartin

3 5

Re: [SR-Users] Kamailio IMS deployment
by sainath.ellendula＠wipro.com 27 Jan '16

27 Jan '16

Hi Franz, Thanks for the response. As suggested followed below commands to check the GRANTs on database hss_db. mysql -u root -p show grants for 'hss'@'server.net1.test'; The output result is same as mentioned below. Could you please guide me here to proceed further. Regards, Sainath ---------- Forwarded message ---------- From: "Franz Edler" <franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>> Date: Jan 27, 2016 1:07 AM Subject: RE: [SR-Users] Kamailio IMS deployment To: "Kranti Kumar" <krantikumara(a)gmail.com<mailto:krantikumara@gmail.com>>, "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org>> Cc: "Ramya Y" <y.ramya146(a)gmail.com<mailto:y.ramya146@gmail.com>> Obviously the access of HSS to the database did not succeed. You should check if access permissions to the database is enabled for HSS. Check the GRANTs on the database hss_db. mysql -u root -p show grants for 'hss'@'server.net1.test'; quit; The result should be: +-------------------------------------------------------------------------------------------------------------------+ | Grants for hss(a)server.net1.test<mailto:hss@server.net1.test> | +-------------------------------------------------------------------------------------------------------------------+ | GRANT USAGE ON *.* TO 'hss'@'server.net1.test' IDENTIFIED BY PASSWORD '*AC83FCF24B79020EF2C51D780CDFA559F25CC9BE' | | GRANT SELECT, INSERT, UPDATE, DELETE ON `hss_db`.* TO 'hss'@'server.net1.test' | +-------------------------------------------------------------------------------------------------------------------+ BR Franz From: Kranti Kumar [mailto:krantikumara@gmail.com<mailto:krantikumara@gmail.com>] Sent: Sunday, January 24, 2016 10:55 AM To: franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>; Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org>> Cc: Ramya Y <y.ramya146(a)gmail.com<mailto:y.ramya146@gmail.com>> Subject: Re: [SR-Users] Kamailio IMS deployment Thanks a lot Franz. Observed few issues even after changes done in /etc/bind. Please find the below Errors in each interfaces and also find the attachment of /var/log/syslog(not shared full logs) Could you please help me here to proceed further. HSS - Configured IP : 10.0.0.9 root@server:~# ./hss.sh - Configured IP : 10.0.0.9 Building Classpath Classpath is lib/xml-apis.jar:lib/xercesImpl.jar:lib/xerces-2.4.0.jar:lib/xalan-2.4.0.jar:lib/tomcat-util.jar:lib/tomcat-http.jar:lib/tomcat-coyote.jar:lib/struts.jar:lib/servlets-default.jar:lib/servlet-api.jar:lib/naming-resources.jar:lib/naming-factory.jar:lib/mysql-connector-java-3.1.12-bin.jar:lib/mx4j-3.0.1.jar:lib/log4j.jar:lib/junit.jar:lib/junitee.jar:lib/jta.jar:lib/jsp-api.jar:lib/jmx.jar:lib/jdp.jar:lib/jasper-runtime.jar:lib/jasper-compiler-jdt.jar:lib/jasper-compiler.jar:lib/hibernate3.jar:lib/FHoSS.jar:lib/ehcache-1.1.jar:lib/dom4j-1.6.1.jar:lib/commons-validator.jar:lib/commons-modeler.jar:lib/commons-logging.jar:lib/commons-logging-1.0.4.jar:lib/commons-lang.jar:lib/commons-fileupload.jar:lib/commons-el.jar:lib/commons-digester.jar:lib/commons-collections-3.1.jar:lib/commons-beanutils.jar:lib/cglib-2.1.3.jar:lib/catalina-optional.jar:lib/catalina.jar:lib/c3p0-0.9.1.jar:lib/base64.jar:lib/asm.jar:lib/asm-attrs.jar:lib/antlr-2.7.6.jar::log4j.properties:.. 2016-01-21 14:07:07,876 INFO de.fhg.fokus.hss.main.TomcatServer - startTomcat Tomcat-Server is started. 2016-01-21 14:07:12,462 WARN org.apache.catalina.connector.MapperListener - registerEngine Unknown default host: 10.0.0.9 2016-01-21 14:07:16,578 INFO de.fhg.fokus.hss.web.servlet.ResponseFilter - init Response Filter Initialisation! 2016-01-21 14:07:17,966 INFO de.fhg.fokus.hss.main.TomcatServer - startTomcat WebConsole of FHoSS was started ! 2016-01-21 14:08:21,200 WARN com.mchange.v2.resourcepool.BasicResourcePool - run com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@1670988b<about:blank> -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (60). Last acquisition attempt exception: com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception: ** BEGIN NESTED EXCEPTION ** java.net.SocketException MESSAGE: java.net.ConnectException: Connection refused STACKTRACE: java.net.SocketException: java.net.ConnectException: Connection refused PCSCF - Configured IP : 10.0.0.10 root@server:~# kamailio -f /usr/local/etc/kamailio/kamailio-pcscf.cfg loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(2352) INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: pcscf.net1.test [10.0.0.10]:4060 Aliases: *: pcscf.net1.test:* WARNING: no fork mode 0(2352) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(2352) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available 0(2352) INFO: ims_usrloc_pcscf [hslot.c:62]: ul_init_locks(): locks array size 512 0(2352) INFO: <core> [udp_server.c:150]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(2352) INFO: <core> [udp_server.c:200]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(2352) WARNING: ims_usrloc_pcscf [usrloc_db.c:59]: connect_db(): DB connection already open... continuing ^C^C 0(2352) NOTICE: <core> [main.c:683]: handle_sigs(): Thank you for flying kamailio!!! 1(2373) INFO: <core> [main.c:798]: sig_usr(): signal 15 received 2(2374) INFO: <core> [main.c:798]: sig_usr(): signal 15 received 0(2352) INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ICSCF - Configured IP : 10.0.0.11 root@server:~# kamailio -f /usr/local/etc/kamailio/kamailio-icscf.cfg loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(2353) INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: icscf.net1.test [10.0.0.11]:5060 Aliases: *: icscf.net1.test:* WARNING: no fork mode 0(2353) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(2353) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available 0(2353) INFO: <core> [udp_server.c:150]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(2353) INFO: <core> [udp_server.c:200]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(2353) INFO: cdp [mod.c:227]: cdp_child_init(): CDiameterPeer child starting ... 0(2353) INFO: cdp [mod.c:229]: cdp_child_init(): ... CDiameterPeer child started 10(2370) INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... 6(2366) INFO: cdp [worker.c:331]: worker_process(): [3] Worker process started... 7(2367) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... 7(2367) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [] Receiver process starting up... 8(2368) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [hss.net1.test] Receiver process doing init on new process... 8(2368) INFO: cdp [receiver.c:183]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [hss.net1.test] 9(2369) INFO: cdp [acceptor.c:82]: acceptor_process(): Acceptor process starting up... 9(2369) WARNING: cdp [tcp_accept.c:123]: create_socket(): create_socket(): Trying to open/bind/listen on 10.0.0.9 port 3869 9(2369) WARNING: cdp [tcp_accept.c:148]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.0.0.9 port 3869 9(2369) INFO: cdp [acceptor.c:96]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 8(2368) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [hss.net1.test] Receiver process starting up... 10(2370) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2370) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2370) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2370) WARNING: cdp [receiver.c:911]: peer_connect(): peer_connect(): Error opening connection to to 10.0.0.9 port 3868 >Connection refused 10(2370) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2370) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2370) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2370) INFO: cdp [receiver.c:932]: peer_connect(): peer_connect(): Peer hss.net1.test:3868 connected 10(2370) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 10(2370) WARNING: cdp [peermanager.c:315]: peer_timer(): Inactivity on peer [hss.net1.test], sending DWR... - if we don't get a reply, the peer will be closed 8(2368) INFO: cdp [receiver.c:802]: receive_loop(): select_recv(): [hss.net1.test] read on socket [14] returned 0 > ... dropping 8(2368) INFO: cdp [receiver.c:219]: disconnect_serviced_peer(): drop_serviced_peer(): [hss.net1.test] Disconnecting from peer ^C10(2370) INFO: <core> [main.c:798]: sig_usr(): signal 2 received 0(2353) ALERT: <core> [main.c:725]: handle_sigs(): child process 2361 exited normally, status=0 0(2353) INFO: <core> [main.c:740]: handle_sigs(): dont_fork turned on, living on 0(2353) NOTICE: <core> [main.c:683]: handle_sigs(): Thank you for flying kamailio!!! 2(2362) INFO: <core> [main.c:798]: sig_usr(): signal 15 received 0(2353) INFO: cdp [mod.c:242]: cdp_exit(): CDiameterPeer child stopping ... 0(2353) INFO: cdp [diameter_peer.c:428]: diameter_peer_destroy(): destroy_diameter_peer(): Terminating all children... 0(2353) INFO: cdp [diameter_peer.c:435]: diameter_peer_destroy(): destroy_diameter_peer(): Waiting for child [2370] to terminate... 0(2353) INFO: cdp [diameter_peer.c:447]: diameter_peer_destroy(): destroy_diameter_peer(): All processes terminated. Cleaning up. 0(2353) INFO: cdp [worker.c:140]: worker_destroy(): Unlocking workers waiting on empty queue... 0(2353) INFO: cdp [worker.c:143]: worker_destroy(): Unlocking workers waiting on full queue... 0(2353) CRITICAL: cdp [diameter_peer.c:487]: diameter_peer_destroy(): destroy_diameter_peer(): Bye Bye from C Diameter Peer test 0(2353) INFO: cdp [mod.c:244]: cdp_exit(): ... CDiameterPeer child stoped 0(2353) INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized SCSCF - Configured IP : 10.0.0.12 root@server:/etc# kamailio -f /usr/local/etc/kamailio/kamailio-scscf.cfg loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(2371) INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: scscf.net1.test [10.0.0.12]:6060 Aliases: *: scscf.net1.test:* WARNING: no fork mode 0(2371) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(2371) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available 0(2371) INFO: ims_usrloc_scscf [hslot.c:69]: ul_init_locks(): locks array size 512 0(2371) INFO: ims_usrloc_scscf [hslot_sp.c:67]: subs_init_locks(): locks array size 512 0(2371) INFO: ims_usrloc_scscf [contact_hslot.c:67]: init_contacts_locks(): locks array size 512 0(2371) INFO: <core> [udp_server.c:150]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(2371) INFO: <core> [udp_server.c:200]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(2371) INFO: cdp [mod.c:227]: cdp_child_init(): CDiameterPeer child starting ... 0(2371) INFO: cdp [mod.c:229]: cdp_child_init(): ... CDiameterPeer child started 3(2381) INFO: cdp [worker.c:331]: worker_process(): [0] Worker process started... 4(2382) INFO: cdp [worker.c:331]: worker_process(): [1] Worker process started... 5(2383) INFO: cdp [worker.c:331]: worker_process(): [2] Worker process started... 7(2390) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... 7(2390) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [] Receiver process starting up... 8(2392) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [hss.net1.test] Receiver process doing init on new process... 8(2392) INFO: cdp [receiver.c:183]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [hss.net1.test] 8(2392) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [hss.net1.test] Receiver process starting up... 9(2393) INFO: cdp [acceptor.c:82]: acceptor_process(): Acceptor process starting up... 9(2393) WARNING: cdp [tcp_accept.c:123]: create_socket(): create_socket(): Trying to open/bind/listen on 10.0.0.9 port 3870 9(2393) WARNING: cdp [tcp_accept.c:148]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.0.0.9 port 3870 9(2393) INFO: cdp [acceptor.c:96]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 10(2394) INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2394) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2394) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2394) WARNING: cdp [receiver.c:911]: peer_connect(): peer_connect(): Error opening connection to to 10.0.0.9 port 3868 >Connection refused 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2394) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2394) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2394) INFO: cdp [receiver.c:932]: peer_connect(): peer_connect(): Peer hss.net1.test:3868 connected 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 10(2394) WARNING: cdp [peermanager.c:315]: peer_timer(): Inactivity on peer [hss.net1.test], sending DWR... - if we don't get a reply, the peer will be closed 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 8(2392) INFO: cdp [receiver.c:802]: receive_loop(): select_recv(): [hss.net1.test] read on socket [15] returned 0 > ... dropping 8(2392) INFO: cdp [receiver.c:219]: disconnect_serviced_peer(): drop_serviced_peer(): [hss.net1.test] Disconnecting from peer 10(2394) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(2394) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(2394) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(2394) WARNING: cdp [receiver.c:911]: peer_connect(): peer_connect(): Error opening connection to to 10.0.0.9 port 3868 >Connection refused ^C11(2398) INFO: <core> [main.c:798]: sig_usr(): signal 2 received 9(2393) INFO: <core> [main.c:798]: sig_usr(): signal 2 received 0(2371) ALERT: <core> [main.c:725]: handle_sigs(): child process 2381 exited normally, status=0 0(2371) INFO: <core> [main.c:740]: handle_sigs(): dont_fork turned on, living on 0(2371) NOTICE: <core> [main.c:683]: handle_sigs(): Thank you for flying kamailio!!! 10(2394) INFO: <core> [main.c:798]: sig_usr(): signal 15 received 0(2371) INFO: cdp [mod.c:242]: cdp_exit(): CDiameterPeer child stopping ... On Fri, Jan 22, 2016 at 2:16 AM, Franz Edler <franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>> wrote: Hi, you can see the first error is a database error: ERROR: db_mysql [km_my_con.c:124]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on 'server.net1.test' (111) This error I expected because you have to adapt the access permissions to the database. Just check the GRANT statements in my log-file and try to understand what they do. Then adapt it accordingly. BR Franz From: Ramya Y [mailto:y.ramya146@gmail.com<mailto:y.ramya146@gmail.com>] Sent: Wednesday, January 20, 2016 2:19 PM To: franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>; Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org>> Subject: Re: [SR-Users] Kamailio IMS deployment Hi Franz we have tried with different interfaces(eth0(10.0.0.9),eth1(10.0.0.10),eth2(10.0.0.11),eth3(10.0.0.12) for P/I/S ,but facing below error. root@server:/etc# kamailio -f /usr/local/etc/kamailio/kamailio-pcscf.cfg loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(1630) INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: pcscf.net1.test [10.0.0.10]:4060 Aliases: *: pcscf.net1.test:* WARNING: no fork mode 0(1630) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(1630) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available 0(1630) INFO: ims_usrloc_pcscf [hslot.c:62]: ul_init_locks(): locks array size 512 0(1630) ERROR: db_mysql [km_my_con.c:124]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on 'server.net1.test' (111) 0(1630) ERROR: <core> [db.c:318]: db_do_init2(): could not add connection to the pool 0(1630) ERROR: ims_usrloc_pcscf [usrloc_db.c:79]: init_db(): unable to connect to the database 0(1630) ERROR: ims_usrloc_pcscf [ul_mod.c:203]: mod_init(): Error initializing db connection 0(1630) ERROR: <core> [sr_module.c:962]: init_mod(): Error while initializing module ims_usrloc_pcscf (/usr/local/lib64/kamailio/modules/ims_usrloc_pcscf.so) ERROR: error while initializing modules 0(1630) INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialize could you please help me how to proceed further, steps followed: =========== 1)Modified at - /etc/network/interfaces: created eth1,eth2,eth3 for P/I/S-CSCF. Interfaces are up. 2)Added Bind address at /etc/mysql/my.cnf bind-address 10.0.0.9 bind-address 10.0.0.10 bind-address 10.0.0.11 bind-address 10.0.0.12 3)Modified at /etc/bind/net1.test.zone $ORIGIN net1.test. $TTL 1W @ 1D IN SOA serverkde. root.net1.test ( 2010081401 ; Serial YYYYMMDDXX 3H ; refresh 15M ; retry 1W ; expiry 1D ) ; minimum 1D IN NS server server 1D IN A 10.0.0.9 hss 1D IN CNAME server as1 1D IN CNAME server as2 1D IN CNAME server xcap 1D IN CNAME server server1 1D IN A 10.0.0.10 pcscf 1D IN CNAME server1 server2 1D IN A 10.0.0.11 icscf 1D IN CNAME server2 server3 1D IN A 10.0.0.12 scscf 1D IN CNAME server3 4)Modified at /etc/bind/0.0.10.zone $TTL 86400 @ IN SOA server. root.net2.test ( 2010081401 ; Serial YYYYMMDDXX 28800 ; Refresh 14400 ; Retry 3600000 ; Expire 86400 ) ; Minimum IN NS server.net1.test. IN NS server1.net1.test. IN NS server2.net1.test. IN NS server3.net1.test. 10 IN PTR notebook.net1.test. 9 IN PTR server.net1.test. 7 IN PTR server.net2.test. 5)Modified at /etc/resolve.conf domain net1.test search net1.test nameserver server.net1.test nameserver server1.net1.test nameserver server2.net1.test nameserver server3.net1.test 6)Modified at /etc/hosts 127.0.0.1 localhost 10.0.0.9 server.net1.test server 10.0.0.10 server1.net1.test server1 10.0.0.11 server2.net1.test server2 10.0.0.12 server3.net1.test server3 10.0.0.9 net1.test 10.0.0.10 pcscf.net1.test 10.0.0.11 icscf.net1.test 10.0.0.12 scscf.net1.test Thanks, Ramyasri. On Sun, Jan 17, 2016 at 5:33 PM, Franz Edler <franz.edler(a)technikum-wien.at<mailto:franz.edler@technikum-wien.at>> wrote: Fine. This exactly was my intention. BR Franz > -----Original Message----- > From: sr-users [mailto:sr-users-bounces@lists.sip-router.org<mailto:sr-users-bounces@lists.sip-router.org>] On Behalf Of > Vasiliy Ganchev > Sent: Monday, January 11, 2016 9:08 AM > To: sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> > Subject: Re: [SR-Users] Kamailio IMS deployment > > Hi Franz! > > Thanks for sharing! Great job, end excellent materials to get started with > students (beside my main work I also teach students in Odessa National > Academy of Telecommunication). > I was looking for some "light" way how to start with real deployment of IMS, > not pure theory, and this is just the kind I wanted! > > Will try your deploy in education process this year. (will share the results in > the end) > > Cheers! > > > > -- > View this message in context: http://sip- > router.1086192.n5.nabble.com/Kamailio-IMS-deployment-<http://router.1086192.n5.nabble.com/Kamailio-IMS-deployment-> > tp143593p144517.html > Sent from the Users mailing list archive at Nabble.com. > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr- > users(a)lists.sip-router.org<mailto:users@lists.sip-router.org> http://lists.sip-router.org/cgi- > bin/mailman/listinfo/sr-users _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

2 1

A new edition of Kamailio Development Workshop
by Daniel-Constantin Mierla 27 Jan '16

27 Jan '16

Hello, last edition of Kamailio Development Workshop happened about three years ago. As I got requests about it from time to time, I thought of trying to organize a new edition. Rather short term by now due to various constraints, so the plan is to do it again in Alicante, Spain, during February 15-16, 2016. I put together more details at: * http://www.kamailio.org/w/development-workshop/ Besides spending 2 days digging into Kamailio C code, such event is also good for discovering and sharing development resources among participants, as well as meeting people from community -- at the previous editions I met for first time with Victor Seva, Vicente Hernando and Seudin Kasumovic, which in turn contributed a lot of code afterwards. It will be also testing phase for upcoming major release, maybe we can plan some stress testing session on site. Right now I am looking to see if there is any interest in such event in order to nail down organizing it or not. Should anyone consider to participate, write me. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

2 4

Acc message to syslog
by Yasin CANER 27 Jan '16

27 Jan '16

4 3

Strange PUA Behaviour
by Phil Lavin 26 Jan '16

26 Jan '16

Hi all, We are investigating an issue with BLF whereby the BLF key on the subscribed phone does not always "turn off" after the call has ended. We have enabled force_single_dialog to keep things simple for debugging. The attached pcap is the result. The relevant stuff as I see it is: * Packet #60 - UA sends a BYE * Packet #62 - PUA sends a PUBLISH over loopback with a state of "terminated" * Packet #65 - The PUBLISH is sent out to the subscribed UA as a NOTIFY with a state of "early" This causes the BLF light on the phone to continue flashing. We are running a version of Kamailio compiled from the HEAD of the current 4.3 branch. Any ideas? Phil Lavin Telecoms Systems Manager CloudCall by SYNETY www.cloudcall.com<http://www.cloudcall.com/> T: +44 (0) 330 335 0000 / +1 617 982 1600 D: +44 (0) 116 424 4790 / +1 617 982 4790 SM: LinkedIn<https://uk.linkedin.com/pub/phil-lavin/25/422/750> READ OUR BLOG FOR SMARTER COMMUNICATIONS<http://t.sidekickopen03.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XX43…> Confidentiality: This e-mail transmission, including any attachments, is intended only for the named recipient(s) and may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you have received this transmission in error, or are not the named recipient(s), please notify the sender immediately by return e-mail and permanently delete this transmission, including any attachments. Security: This e-mail and any attachments are believed to be free from any virus but it is the responsibility of the recipient to ensure this is so. E-mail is not a 100% secure communication.

2 19

IPTel URI forwarding to PBXes not working
by McConnachie, Alex 26 Jan '16

26 Jan '16

I am stumped as my DID provider can't route via SIP URI to PBXes but they can to IPTel. I can call my own PBX, and from my own PBX to the PBXes URI without issue. When I route the DID via URI to IPTel and set voicebox it works and routes to the voicebox. When I add a forward for the PBXes URI it then breaks and gets a denial of 404 not in service. Ideas anyone? I am scratching my head here. Appreciate any help! Regards, Alex McConnachie

2 1

Rewriting header of BYE message to carrier
by Ryan Mottley 26 Jan '16

26 Jan '16

Hi, We're running a system with Kamailio running in front of Asterisk just handling registrations and forwarding everything else to Asterisk. But we're having an issue during hangup on incoming calls. If the initiator hangs up, the call completes successfully. But if one of our phones hangs up, the BYE message comes back with a 404 "Not Found" and the call doesn't hang up on the carrier side. According to the carrier, it's because the IP in the contact on our ACK message goes to their audio IP while the header of our BYE points to their signaling IP. ACK sip:[Kamailio Pub IP]:5060;line=sr--rkpsDAp6YAp6DIpZDZmZeI2ZYI26YIRVDcpsDIpsem* SIP/2.0 Via: SIP/2.0/UDP *[Carrier Signaling IP]*;branch=z9hG4bK2236.1402e7b4.2 Via: SIP/2.0/UDP *[Carrier Audio IP]*;received=*[Carrier Audio IP]* ;branch=z9hG4bK07a8bccb;rport=5060 Route: <sip:[Kamailio Pub IP];r2=on;lr=on;ftag=as67cef00d;nat=yes>,<sip:10.120.0.1;line=sr--rkpsDthVDIhVDNh6Ogo6eKh6eAQs4LRflC2srQRflC2srGqAl-CAP6rZrZkGDmpGed2APtCvlx1> From: "+16014477389" <sip:6014477389@*[Carrier Audio IP]*>;tag=as67cef00d To: <sip:6016025063@*[Carrier Signaling IP]*>;tag=as643b40ca Contact: <sip:6014477389@*[Carrier Audio IP]*> Call-ID: 4aaefec90826a2a221f0af9500ad211b@*[Carrier Audio IP]* CSeq: 102 ACK User-Agent: packetrino Max-Forwards: 69 Content-Length: 0 BYE sip:6014477389@*[Carrier Signaling IP] *SIP/2.0 Via: SIP/2.0/UDP [Kamailio Pub IP];branch=z9hG4bK2236.fca983a45913fb510f97e781a85c7392.0 Via: SIP/2.0/UDP 10.120.0.1;branch=z9hG4bKsr-IqktV1L26BCx0jmwZeI2ZYI26YIRVDcpsDIpsem.-EF8-EtCZYmg6edIMehhA4A.AEzyuiZKfPKo7N-qAcWq6D-rsYc4Zp** Route: <sip:*[Carrier Signaling IP]*;lr=on> Max-Forwards: 69 From: <sip:6016025063@[Kamailio Pub IP]>;tag=as643b40ca To: "+16014477389" <sip:6014477389@*[Carrier Audio IP]*>;tag=as67cef00d Call-ID: 4aaefec90826a2a221f0af9500ad211b@*[Carrier Audio IP]* CSeq: 102 BYE User-Agent: Asterisk PBX 13.6.0 X-Asterisk-HangupCause: Normal Clearing X-Asterisk-HangupCauseCode: 16 Content-Length: 0 I'm thinking it's happening because their side isn't configured correctly to handle traffic coming back from a proxy, but in the meantime is there a way to rewrite the top of the BYE header to match the "audio IP" they're requesting it be sent to? Thanks! -- Ryan Mottley, Developer VOXO, LLC voxo.co - (601)602-5063

2 1

Missing dependencies for kamailio-mysql-4.2.7-3.1.x86_64
by Zuxy Meng 26 Jan '16

26 Jan '16

Hi there, I'm trying to install this rpm for my RHEL 5 box, but it asks for mysql-libs; but RHEL 5 isn't shipped with mysql-lib, only mysql55-mysql-libs, which kamailio-mysql doesn't recognize as a valid dependency. Any workaround here? Thanks! -- Zuxy Beauty is truth, While truth is beauty. PGP KeyID: E8555ED6

2 5

Fwd: [Free-RTC] FOSDEM Real Time devoom: call for help
by Daniel Pocock 26 Jan '16

26 Jan '16

-------- Forwarded Message -------- Subject: [Free-RTC] FOSDEM Real Time devoom: call for help Date: Sun, 24 Jan 2016 19:17:02 +0100 From: Saúl Ibarra Corretgé <saul(a)ag-projects.com> Reply-To: Free real-time-communications discussion list <free-rtc(a)lists.fsfe.org> To: Free real-time-communications discussion list <free-rtc(a)lists.fsfe.org>, summit(a)xmpp.org Hi all, FOSDEM is less than a week away, I hope you are all as excited about it as I am :-) We need some volunteers to help with the video recording gear on Saturday. You danât have to do it for the entire day, but the more volunteers we have the better the recording will be.. hopefully! NB: volunteers get a reserved seat, so in case the room is full youâd still be able to enjoy a seat. Please feel free to forward this message to anyone who might be interested. Thanks! -- SaÃºl Ibarra CorretgÃ© AG Projects

1 0

question about kamailio handling of forwarded invite
by DING MA 26 Jan '16

26 Jan '16

Hi, all We're trying to build a system that consists of pbx, kamailio and asterisk in the following configuration. pbx (sip trunk) --- kamailio --- asterisk The kamailio and asterisk are integrated with same database. The outgoing calls to pbx works. But there is a problem with incoming calls from pbx. If we make a consecutive calls from the same pbx user to the same user registered with kamailio. The first would go through, but the second call would be rejected by asterisk. We have insecure=invite set on the trunk/peer, so asterisk is not supposed to auth the invite from kamailio. But the pbx user (from in this case) is not in the database. The asterisk log says: [Jan 21 23:13:19] VERBOSE[20785] chan_sip.c: --- (16 headers 13 lines) --- [Jan 21 23:13:19] VERBOSE[20785] chan_sip.c: Sending to 10.0.1.30:5061 (no NAT) [Jan 21 23:13:19] VERBOSE[20785][C-00000001] chan_sip.c: Sending to 10.0.1.30:5061 (no NAT) [Jan 21 23:13:19] VERBOSE[20785][C-00000001] chan_sip.c: Using INVITE request as basis request - 4aaa2dce75c60e8546994c3501dae9e7@10.0.1.35:5061 [Jan 21 23:13:20] NOTICE[20785][C-00000001] acl.c: SIP Peer ACL: Rejecting '10.0.1.30' due to a failure to pass ACL '(BASELINE)' [Jan 21 23:13:20] NOTICE[20785][C-00000001] chan_sip.c: Failed to authenticate device <sip:95678@10.0.1.35>;tag=as4028dabf [Jan 21 23:13:20] VERBOSE[20785][C-00000001] chan_sip.c: <--- Reliably Transmitting (no NAT) to 10.0.1.30:5061 ---> SIP/2.0 403 Forbidden^M Via: SIP/2.0/TLS 10.0.1.30:5061 ;branch=z9hG4bK9c8e.5cd2c05f6a572312c7793abf5fe1183c.0;i=2;received=10.0.1.30^M Via: SIP/2.0/TLS 10.0.1.35:5061 ;received=10.0.1.35;branch=z9hG4bK249855c1;rport=59929^M From: <sip:95678@10.0.1.35>;tag=as4028dabf^M To: <sip:16317@10.0.1.30>;tag=as35f47241^M Call-ID: 4aaa2dce75c60e8546994c3501dae9e7@10.0.1.35:5061^M CSeq: 102 INVITE^M Server: Asterisk PBX 13.6.0^M Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE^M Supported: replaces, timer^M Content-Length: 0^M Comparing the two invites from kamailio to asterisk, it seems the only difference is that the second invite has an "i=2" in the Via header while the first one has "i=1". Not sure what the "i=1" is for. Would appreciate some insights on how kamailio is adding/handling the "i=#" in Via header. Thanks. Ding Ma SPG, Motorola Solutions

3 2

Acc leaking
by Yasin CANER 25 Jan '16

25 Jan '16

3 3

kamailio_call_disconnecting issue
by yasir ay 25 Jan '16

25 Jan '16

Hello, Hi team I have a kamailio SIP server for call Routing,my call flow is like VoipDialer--->Kamailio-Routing Server-->Softswitch-->Telco/PSTN Mobile caller----------------------------------------------------------------------->calle Now Am facing an issue for a call from voip to telco after answering the call i tried to disconnect.but call is not disconneting..what will i do in kamailio.cfg pls help me to re-write the script am using tls also Regards AmanIdo

2 1

using myself in equation with from_uri
by Dirk Teurlings - SIGNET B.V. 25 Jan '16

25 Jan '16

Hi, The documentation states the following. https://www.kamailio.org/wiki/cookbooks/4.2.x/core#myself if(uri==myself) { log("the request is for local processing\n"); }; Now this could also be used to do something like this: (also used in some examples) if(from_uri==myself) { log("the request is for local processing\n"); }; Using this the from_uri could be: sip:sip.voipexample.net:5061 myself in this case only has sip.voipexample.net:5060 as an Aias Now the equation wouldn't match, because the port 5061 is non-default. Would it be possible to match the from_uri to myself ignoring the port in from_uri? The only thing I can think of is using a regular expression. somthing like this: from_uri=~"sip:.+@sip\.voipexample\.net(:([0-9]{1,4}|[1-5][0-9]{4}|6[0-4][0-9]{3}|65[0-4][0-9]{2}|655[0-2][0-9]|6553[0-5])|)" But this skips the use of myself entirely. Any insight on this would be greatly appreciated! Cheers, Dirk

3 7

poros@@lists.sip-router.org
by Poros Mitra 25 Jan '16

25 Jan '16

1 0

Fosdem 2016
by Daniel-Constantin Mierla 22 Jan '16

22 Jan '16

Hello, anyone going to Fosdem? If no unexpected weather conditions messing the transport system, I am going to be there. It would be good to know who else we can meet there. If there are enough people interested, we can try organizing a social event (dinner/drinks) on Saturday evening. Last year we did it together with Jitsi team, but they are not coming this year. Perhaps there are other folks around the RTC dev room we can ask. On the other hand, it is harder to find a place if it is a large group, even harder to put all together if there are different groups/coordinators. Also, it is not easy to discuss withing a large group, as typically for a dinner we were seated to tables. Therefore organizing for a smaller group just for Kamailio friends could be a good alternative. Let's see first the number of participant and the level of interest for various options. This being an announcement, was crossposted to few mailing lists, but as most of the people are on sr-users, I think it would be good to reply and follow up on this discussion only there. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

5 5

Kamailio and openLDAP integration.
by Safdar Khan 22 Jan '16

22 Jan '16

Hi guys, I have tried to integrate kamailio and ldap.It seems like both are taking to each other. Here the purpose of ldap is for back-end support for sip user authentication rather than kamailio database.However i am able to log in but could not make call between sip users.I could not figure out what i am missing. Here is the routing block for ldap in my kamailio.cfg > request_route { > route(LDAPAUTH); > > } --- route[LDAPAUTH] > { > if(is_method("REGISTER")) > { > if(is_present_hf("Authorization")) > { > if > (!ldap_search("ldap://sipaccounts/ou=MyUsers,dc=example,dc=com?cn,userPassword?one?(cn=$fU)")) > { > switch ($retcode) > { > case -1: > sl_send_reply("404", "User Not Found"); > exit; > case -2: > sl_send_reply("500", "Internal server error"); > exit; > default: > exit; > } > } > ldap_result("cn/$avp(username)"); > ldap_result("userPassword/$avp(password)"); > route(REGISTRAR); > if (!pv_www_authenticate("$td", "$avp(password)", "4")) > { > www_challenge("$td", "1"); > exit; > } > sl_send_reply("200", "ok"); > exit; > } > else > { > www_challenge("$td", "1"); > exit; > } > } > }

3 3

SIP Trunking using Kamailio IMS
by indranil chowdhury 21 Jan '16

21 Jan '16

Hello, Is SIP trunking possible with the free version of Kamailio or we need to upgrade to business license? Kindly get back to us with the details of using SIP trunking using Kamailio. We have a requirement in our organisation regarding the same which uses IMS and SIP trunking. In this setup we would initially like to test with 2 LTE EPCs connected to two Kamailio IMS with a SIP trunk between them. Thanks and Regards, Indranil

3 2

topoh quirk with 200 OK for CANCEL
by Alex Balashov 21 Jan '16

21 Jan '16

Hi, I'm using topoh and am running into lots of these errors: Jan 19 20:34:52 csrpus1 /usr/local/sbin/kamailio[3641]: ERROR: [R-DEFAULT-STATELESS-REPLY:nmhfrms2ib9Cnm9kS00Qtbtot5PMiQ0Ni1QKS5iKibuotel14Ygc] !> Received stateless reply 200 (CANCEL) from xxx.xxx.xxx.xxx:5060 Jan 19 20:34:53 csrpus1 /usr/local/sbin/kamailio[3639]: ERROR: tm [t_lookup.c:932]: t_reply_matching(): matching transaction found but callids don't match (received: nmhfrms2ib9Cnm9kS00Qtbtot5PMiQ0Ni1QKS5iKibuotel14Ygc stored: 51899BC6-569EE4330005CE1B-7D47C700_bleg) The call topology is: UAC --> Kamailio (+ topoh) --> PSTN GW Topoh is behaving precisely as expected, but it looks like we might have hit a TM case that topoh does not accommodate somehow: 1. A CANCEL comes in from the UAC and Kamailio sends a CANCEL for its branch to the PSTN GW. 2. Kamailio sends a '200 cancelling' for the UAC's branch backward. 3. The PSTN GW replies with a 200 OK for the CANCEL (PSTN GW branch) that contains the topoh-spoofed Call-ID, but for some reason Kamailio does not match this reply, as indicated by the above error. 4. Because the 200 OK reply was stateless and not matched to a CANCEL transaction, this causes Kamailio to retransmit the CANCEL to the PSTN GW, at which point it receives: 481 Call Leg/Transaction Does Not Exist 5. #4 repeats once more. I don't see any real harm from this situation, but it seems like something that needs fixing. The 487 Request Terminated final reply is processed and relayed correctly to the UAC, and the dialog ends appropriately everywhere. FWIW, I thought this might have to do with async processing of the initial INVITE (through mqueue + rtimer), so I turned it off, but it didn't make any difference. My CANCEL handling in the main request route looks like this: if(is_method("CANCEL")) { set_rtpengine_set("1"); rtpengine_delete(); if(!t_relay_cancel()) { sl_send_reply("500", "Internal Server Error"); exit; } xlog("L_ERR", "[R-MAIN:$ci] !> " "Corresponding INVITE transaction for CANCEL " "does not (or, no longer) exists\n"); exit; } So, it just looks like TM is not matching, and therefore not absorbing the 200 OK reply to its CANCEL to the upstream gateway -- when topoh is enabled. Any insights would be appreciated! -- Alex -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300 Atlanta, GA 30346 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 11

RFC: removing (disabling) fork=no
by Daniel-Constantin Mierla 21 Jan '16

21 Jan '16

Hello, wondering if anyone is using fork=no -- some old docs suggest it is suitable for debugging, but actually kamailio doesn't work properly in this mode, leading to more troubles than benefits (e.g., having reports of invalid issues, like tcp not working in this mode). In first phase I would disable setting this value, with a warning if set to no, because most of the configs out there have fork=yes. Removing it could be considered in the future. Note that this fork=no is different than don't daemonize controlled with -D, which will stay being useful for some init.d systems. Comments or other suggestions? Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

2 2

Re: [SR-Users] Fwd: Kamailio and NAT
by Nelson Migliaro 20 Jan '16

20 Jan '16

I am thinking that I cat get the port during the first call and then use that port for the rest of calls. Maybe that first call will fail but after that, all calls will go fine. Example of a Trying showing received port: 52548 ¿Do you know what pseudovariable represent that value? I tested with all variables I could find but I could not find anyone. Thank you --------------------------------------------------------------------------------------------------------------------------------------------------------- 2016/01/19 17:38:38.981987 VENDOR-IP:5060 -> KAMAILIO-IP:5060 SIP/2.0 100 trying -- your call is important to us Via: SIP/2.0/UDP PUBLIC-IP:52548;branch=z9hG4bK8b5c.b122371ac0ac2f3ef3204b0f192cb16c.1;rport=52548 Via: SIP/2.0/UDP ASTERISK-IP:5060;received=ASTERISK-IP;branch=z9hG4bK4082d124;rport=5060 From: 888888888 <sip:888888888@ASTERISK-IP>;tag=as34f971fe To: <sip:999999999@VENDOR-DOMAIN> Call-ID: 0b5307fa290674a97b47970643fce42a@ASTERISK-IP:5060 CSeq: 102 INVITE Server: kamailio Content-Length: 0 2016-01-15 9:50 GMT+01:00 Nelson Migliaro <eng.migliaro(a)gmail.com>: > Hello Daniel, > > Yes, I am registered to the vendor. > > Regards, > > Nelson.- > > 2016-01-15 7:58 GMT+01:00 Daniel-Constantin Mierla <miconda(a)gmail.com>: > >> Ahh, I thought Asterisk is in the public internet, but actually you >> connect to a provider (vendor), which seems to run Kamailio as well. >> >> Using information from 100 trying is too late, as the INVITE was already >> sent... so one more question before trying to propose a solution. Do you >> have to register to the provider? >> >> Cheers, >> Daniel >> >> >> On 14/01/16 18:51, Nelson Migliaro wrote: >> >> Yes it is possible, but is there an easy way to workaround the issue >> using Kamailio. >> >> Because I have the port because vendor is sending that info in Trying: >> >> 2016/01/13 20:10:15.842055 VENDOR-IP:5060 -> PRIVATE-IP-KAMAILIO:5060 >> SIP/2.0 100 trying -- your call is important to us >> Via: SIP/2.0/UDP PUBLIC-IP:52548;branch= >> z9hG4bKdd74.992e238037882e809653f713a5a580a9.1;rport=*52548* >> >> I need to find the way to discover the port used by firewall (maybe >> getting that info from Trying) and then advertise that port. >> >> >> >> 2016-01-14 18:32 GMT+01:00 Daniel-Constantin Mierla < <miconda(a)gmail.com> >> miconda(a)gmail.com>: >> >>> Not really up to date with all Asterisk features -- do you know if you >>> can append a custom header to a SIP response that is going to be generated >>> by Asterisk? Eventually the reply for an OPTIONS request. >>> >>> Cheers, >>> Daniel >>> >>> >>> On 14/01/16 17:19, Nelson Migliaro wrote: >>> >>> Yes, I manage all devices, even the internet router but it does not >>> allow static pat. >>> >>> 2016-01-14 16:07 GMT+01:00 Daniel-Constantin Mierla <miconda(a)gmail.com>: >>> >>>> Do you control the Asterisk? If yes, depending on Asterisk capabilities >>>> of building replies, you may be able to do some automation to detect the >>>> external port. >>>> >>>> Cheers, >>>> Daniel >>>> >>>> On Thu, Jan 14, 2016 at 3:47 PM, Nelson Migliaro < >>>> <eng.migliaro(a)gmail.com>eng.migliaro(a)gmail.com> wrote: >>>> >>>>> There is not a public Kamailio, only one Kamailio behind NAT, >>>>> >>>>> Right now the configuration is: >>>>> >>>>> Asterisk <-> Kamailio (Private IP + advertise public IP + RTP Proxy ) >>>>> <-> Internet router (public IP + symmetric na) <-> Internet >>>>> >>>>> Regards, >>>>> >>>>> 2016-01-14 15:43 GMT+01:00 Daniel-Constantin Mierla < >>>>> <miconda(a)gmail.com>miconda(a)gmail.com>: >>>>> >>>>>> Is the kamailio behind nat communicating with another kamailio on a >>>>>> public IP? >>>>>> >>>>>> Cheers, >>>>>> DAniel >>>>>> >>>>>> On Thu, Jan 14, 2016 at 1:33 PM, Nelson Migliaro < >>>>>> <eng.migliaro(a)gmail.com>eng.migliaro(a)gmail.com> wrote: >>>>>> >>>>>>> Thank you Daniel for your answer, >>>>>>> >>>>>>> As you mention, there is a symmetric nat and router does not allow a >>>>>>> static NAT. >>>>>>> >>>>>>> By sniffing traffic I can see the port is using new but in case it >>>>>>> change, how can automate the process of advertising the correct port? >>>>>>> >>>>>>> Cheers! >>>>>>> >>>>>>> >>>>>>> ---------- Forwarded message ---------- >>>>>>> From: Daniel-Constantin Mierla < <miconda(a)gmail.com> >>>>>>> miconda(a)gmail.com> >>>>>>> Date: 2016-01-13 23:28 GMT+01:00 >>>>>>> Subject: Re: [SR-Users] Kamailio and NAT >>>>>>> To: "Kamailio (SER) - Users Mailing List" < >>>>>>> <sr-users(a)lists.sip-router.org>sr-users(a)lists.sip-router.org> >>>>>>> >>>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> it looks like you have a symmetric nat router, so the allocated port >>>>>>> is randomly selected. >>>>>>> >>>>>>> If you don't control the nat router to set a static forwarding rule >>>>>>> or it doesn't provide the option to set static forwarding, then you are >>>>>>> pretty much left with sniffing the traffic to discover the external port >>>>>>> and advertise it. >>>>>>> >>>>>>> Cheers, >>>>>>> Daniel >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 13/01/16 20:31, Nelson Migliaro wrote: >>>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> I finally were able to run my Kamailio behind NAT but in order to >>>>>>> accomplish that I included: >>>>>>> >>>>>>> listen=udp:SOURCE-IP:5060 advertise PUBLIC-IP:52548 >>>>>>> >>>>>>> 52548 is the port my internet router change when doing NAT >>>>>>> (5060->52548). I found this port sniffing traffic >>>>>>> >>>>>>> Conclusions at this point are: >>>>>>> >>>>>>> >>>>>>> ---------------------------------------------1-------------------------------------------------------------------------------------------------- >>>>>>> If I use this line: >>>>>>> >>>>>>> listen=udp:SOURCE-IP:5060 advertise PUBLIC-IP:5060 it does not work >>>>>>> :( >>>>>>> >>>>>>> When I dial a call, INVITE / ACK / Trying / OK goes fine because >>>>>>> they are part of the same transaction >>>>>>> When remote party disconnects the call, BYE goes to PUBLIC-IP port >>>>>>> 5060 and router blocks de request. I assume vendor sends BYE to 5060 >>>>>>> because it is a new transaction >>>>>>> >>>>>>> -----------------------------------------------2-------------------------------------------------------------------------------------------------- >>>>>>> >>>>>>> If I use this line: >>>>>>> >>>>>>> listen=udp:SOURCE-IP:5060 advertise PUBLIC-IP:52548 it work !!!!!! >>>>>>> >>>>>>> When I dial a call, INVITE / ACK / Trying / OK goes fine because >>>>>>> they are part of the same transaction >>>>>>> When remote party disconnects the call, BYE goes to PUBLIC-IP port >>>>>>> 52548 and router forward the request to Kamailio. Since there is an open >>>>>>> connection. >>>>>>> >>>>>>> I need to find the way to find the way to advertise the public port >>>>>>> internet router is doing NAT (PAT). >>>>>>> >>>>>>> >>>>>>> --------------------------------------------------------------------------------------------------------------------------------------------------- >>>>>>> This trace is a call that worked fine because I included line: >>>>>>> >>>>>>> listen=udp:SOURCE-IP:5060 advertise PUBLIC-IP:52548 >>>>>>> >>>>>>> >>>>>>> This trace is an INVITE with this line: listen=udp:SOURCE-IP:5060 >>>>>>> advertise PUBLIC-IP:52548 >>>>>>> 2016/01/13 20:10:15.793568 PRIVATE-IP-KAMAILIO:5060 -> VENDOR-IP:5060 >>>>>>> INVITE sip:NUM-DESTINATION@VENDOR-IP SIP/2.0 >>>>>>> Record-Route: < >>>>>>> sip:PUBLIC-IP:52548;lr=on;ftag=as3b72a453;vsf=AAAAAAEECQkCAgsNAXBeL0NPXVQfU0suMTY5LjIzMQ--;vst=AAAAAAAAAAAAAAAAAABCUEIAX1lKWF5MF0tB >>>>>>> A-;nat=yes> >>>>>>> Via: SIP/2.0/UDP >>>>>>> PUBLIC-IP:52548;branch=z9hG4bKdd74.992e238037882e809653f713a5a580a9.0 >>>>>>> Via: SIP/2.0/UDP >>>>>>> PRIVATE-IP-SOFTPHONE:5060;received=PRIVATE-IP-SOFTPHONE;branch=z9hG4bK2f4e76ba;rport=5060 >>>>>>> Max-Forwards: 69 >>>>>>> From: NUM-SOURCE <sip:NUM-SOURCE@PRIVATE-IP-KAMAILIO>;tag=as3b72a453 >>>>>>> To: <sip:NUM-DESTINATION@sip.VENDOR-IP> >>>>>>> Contact: >>>>>>> <sip:NUM-SOURCE@PRIVATE-IP-SOFTPHONE:5060;alias=PUBLIC-IP~5060~1> >>>>>>> Call-ID: 329950447629810f7bdeaeed0cc034e1@PRIVATE-IP-SOFTPHONE:5060 >>>>>>> CSeq: 102 INVITE >>>>>>> User-Agent: Kamailio >>>>>>> Date: Wed, 13 Jan 2016 19:10:15 GMT >>>>>>> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, >>>>>>> INFO, PUBLISH, MESSAGE >>>>>>> Supported: replaces, timer >>>>>>> Content-Type: application/sdp >>>>>>> Content-Length: 255 >>>>>>> >>>>>>> >>>>>>> Trying..... >>>>>>> >>>>>>> 2016/01/13 20:10:15.842055 VENDOR-IP:5060 -> PRIVATE-IP-KAMAILIO:5060 >>>>>>> SIP/2.0 100 trying -- your call is important to us >>>>>>> Via: SIP/2.0/UDP >>>>>>> PUBLIC-IP:52548;branch=z9hG4bKdd74.992e238037882e809653f713a5a580a9.1;rport=52548 >>>>>>> Via: SIP/2.0/UDP >>>>>>> PRIVATE-IP-SOFTPHONE:5060;received=PRIVATE-IP-SOFTPHONE;branch=z9hG4bK2f4e76ba;rport=5060 >>>>>>> From: NUM-SOURCE <sip:NUM-SOURCE@PRIVATE-IP-KAMAILIO>;tag=as3b72a453 >>>>>>> To: <sip:NUM-DESTINATION@VENDOR-IP> >>>>>>> Call-ID: 329950447629810f7bdeaeed0cc034e1@PRIVATE-IP-SOFTPHONE:5060 >>>>>>> CSeq: 102 INVITE >>>>>>> Server: kamailio >>>>>>> Content-Length: 0 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> And finally a BYE >>>>>>> >>>>>>> 2016/01/13 20:10:28.545526 VENDOR-IP:5060 -> PRIVATE-IP-KAMAILIO:5060 >>>>>>> BYE sip:34982298000@PRIVATE-IP-SOFTPHONE:5060;alias=PUBLIC-IP~5060~1 >>>>>>> SIP/2.0 >>>>>>> Via: SIP/2.0/UDP >>>>>>> VENDOR-IP;branch=z9hG4bK26d8.847e6e14eef37e2cfc8b5e81d33de73d.0 >>>>>>> From: <sip:675896262@PRIVATE-IP-KAMAILIO>;tag=gK0293ed93 >>>>>>> To: "NUM-SOURCE" <sip:NUM-SOURCE@VENDOR-IP>;tag=as3b72a453 >>>>>>> Call-ID: 329950447629810f7bdeaeed0cc034e1@PRIVATE-IP-SOFTPHONE:5060 >>>>>>> CSeq: 28731 BYE >>>>>>> Max-Forwards: 69 >>>>>>> Route: < >>>>>>> sip:PUBLIC-IP:52548;lr=on;ftag=as3b72a453;vsf=AAAAAAEECQkCAgsNAXBeL0NPXVQfU0suMTY5LjIzMQ--;vst=AAAAAAAAAAAAAAAAAABCUEIAX1lKWF5MF0tBMzA-;na >>>>>>> yes> >>>>>>> Reason: Q.850;cause=16 >>>>>>> Content-Length: 0 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- >>>>>>> >>>>>>> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- >>>>>>> >>>>>>> Finally, It is finally working because I hardcoded NAT´d port. >>>>>>> I would like to find a way to avoid setting the port in "hard". >>>>>>> >>>>>>> Thank you >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda >>>>>>> Book: SIP Routing With Kamailio - http://www.asipto.comhttp://miconda.eu >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing >>>>>>> list >>>>>>> <sr-users(a)lists.sip-router.org>sr-users(a)lists.sip-router.org >>>>>>> <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users> >>>>>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing >>>>>>> list >>>>>>> <sr-users(a)lists.sip-router.org>sr-users(a)lists.sip-router.org >>>>>>> <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users> >>>>>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Daniel-Constantin Mierla - <http://www.asipto.com> >>>>>> http://www.asipto.com >>>>>> <http://twitter.com/#%21/miconda>http://twitter.com/#!/miconda - >>>>>> <http://www.linkedin.com/in/miconda>http://www.linkedin.com/in/micond >>>>>> >>>>>> _______________________________________________ >>>>>> 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 >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>>> >>>>> >>>> >>>> >>>> -- >>>> Daniel-Constantin Mierla - <http://www.asipto.com>http://www.asipto.com >>>> http://twitter.com/#!/miconda - http://www.linkedin.com/in/micond >>>> <http://www.linkedin.com/in/miconda> >>>> >>>> _______________________________________________ >>>> 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 >>>> >>>> >>> >>> >>> _______________________________________________ >>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users >>> >>> >>> -- >>> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda >>> Book: SIP Routing With Kamailio - http://www.asipto.comhttp://miconda.eu >>> >>> >>> _______________________________________________ >>> 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 >>> >>> >> >> -- >> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda >> Book: SIP Routing With Kamailio - http://www.asipto.comhttp://miconda.eu >> >> >

2 2

Registration to sip provider
by Evren Akbulut 19 Jan '16

19 Jan '16

Hi, I am a newbie. As I read I understand I need to use UAC module for registration but cannot figure how to trigger the registration request. I enable the UAC module and it seem to be working. How can I trigger the REGISTER to a SIP provider account? And is it possible to use multiple accounts for different provider registrations? Can someone help about UAC usage please. Regards Evren Akbulut

2 1

rtpengine to do DTLS-SRTP handshake, but media should not pass through it. the media should go through media server, which is running on the same machine
by riko nir 19 Jan '16

19 Jan '16

Hi, We have a media server and (opensips + rtpengine). How can I configure opensips+rtpengine to just do DTLS handshake with the client, but the media should not go through RTPEngine. The media should go to the Media server. Thanks. Riko

1 0

Kamailio Load Balancing Cluster
by sandeep goje 19 Jan '16

19 Jan '16

Hi, I am using Kamailio as a load balancer with call load distribution to Freeswitch Gateways. I need a HA cluster of Kamailio. I have seen instructions to setup Kamailio HA cluster using KeepAlive but I also want them to share the load balancing information. I have seen OpenSIPS supports this. Is there a way in Kamailio to make both load balancers also share the load balancing information. Thank you. Regards, Sandeep The most profound statements are often said in silence. -Lynn Johnston

2 1

Get value of RPID privacy param
by Grant Bagdasarian 18 Jan '16

18 Jan '16

Hello, How do I select the value of the privacy parameter in the Remote-Party-ID header? Remote-Party-ID: "John Doe" <sip:jdoe@foo.com>;party=calling;id;privacy=full;screen=yes The following doesn't work, and I believe because it's not a valid select class: $sel((a)hf_value.remote_party_id.privacy) I'm using kamailio 4.1. Regards, Grant

5 9

IMS terminating dialog does not re-run through all iFCs after calling t_newtran()
by Russell McConnachie 17 Jan '16

17 Jan '16

Hi, My CSCF environment has an application server acting as a B2BUA. It's originating a new session, and creating a new terminating session back to the S-CSCF (two separate sessions per-call). When I perform a re-INVITE with a diversion to transfer the call to another URI it is all good until the S-CSCF attempts to call the call control logic: # Start new transaction: t_newtran(); if (isc_match_filter("orig", "location")) { t_on_failure("ISC_ORIG_FAILURE"); exit; The t_newtran() method from what I understand will create a new transaction. Inside of this new transaction, I would think that the isc_match_filter should re-run through all of the iFCs defined on the HSS service profile, but it does not seem to be doing so. It seems to be continuing at where the original transaction ISC mark skip point was set. Thanks

2 1

Different rtpproxy for different media type
by Koray Vatansever 15 Jan '16

15 Jan '16

Hi everybody, Is there a way to use different rtpproxies for different media types? I want to use one rtpproxy set for audio, and use another one for video. Is this possible in kamailio? Regards, Koray

2 5

Kamailio replies with SIP/2.0 500 Service Unavailable Under load
by sandeep goje 15 Jan '16

15 Jan '16

Hi, I am doing load testing with of Kamailio. I have sipp (version 3.3) as the load generator,Kamailio(4.2.7) as Load Balancer and Freeswitch (1.6.5) as Gateways. I am using the following command to generate load ./sipp -sf uac.xml -d 2000 -m 4000 -l 1000 -r 200 -trace_stat -i SIPP_IP -p 15060 --trace_err -trace_error_codes -trace_calldebug -trace_screen KAM_IP When the rate of generation is below 80 (-r 80), Kamailio behaves fine.But if we go beyond 80, Kamailio starts sending "500 Service Unavailable" 2016-01-12 11:18:15.375103 1452577695.375103: Aborting call on unexpected message for Call-Id '96-32493@SIPP_IP': while expecting '180' (index 2), received 'SIP/2.0 500 Service Unavailable^M Via: SIP/2.0/UDP SIPP_IP:15060;branch=z9hG4bK-32493-96-0^M From: sipp <sip:sipp@SIPP_IP:15060>;tag=96^M To: sut <sip:service@KAM_IP :5060>;tag=55f576f507e822fa6633cf4bc22740e6-6660^M Call-ID: 96-32493@SIPP_IP^M CSeq: 1 INVITE^M Server: kamailio (4.2.7 (x86_64/linux))^M Content-Length: 0^M With the above command, sipp output is ----------------------------- Statistics Screen ------- [1-9]: Change Screen -- Start Time | 2016-01-12 11:26:07.723764 1452578167.723764 Last Reset Time | 2016-01-12 11:27:16.280901 1452578236.280901 Current Time | 2016-01-12 11:27:16.282737 1452578236.282737 -------------------------+---------------------------+-------------------------- Counter Name | Periodic value | Cumulative value -------------------------+---------------------------+-------------------------- Elapsed Time | 00:00:00:001000 | 00:01:08:558000 Call Rate | 0.000 cps | 58.345 cps -------------------------+---------------------------+-------------------------- Incoming call created | 0 | 0 OutGoing call created | 0 | 4000 Total Call created | | 4000 Current Call | 0 | -------------------------+---------------------------+-------------------------- Successful call | 0 | 1192 Failed call | 0 | 2808 -------------------------+---------------------------+-------------------------- Response Time 1 | 00:00:00:000000 | 00:00:15:102000 Call Length | 00:00:00:000000 | 00:00:10:614000 ------------------------------ Test Terminated -------------------------------- Kamailio is run with command /usr/local/sbin/kamailio -f /usr/local/etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid -m 512 -M 8 -u kamailio -g kamailio version: kamailio 4.2.7 (x86_64/linux) 727746 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, DBG_QM_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: 727746 compiled on 15:59:03 Jan 11 2016 with gcc 4.6.3 System : Ubuntu 12.04.4 LTS Linux devops10-60-20-169 3.11.0-15-generic #25~precise1-Ubuntu SMP Thu Jan 30 17:39:31 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux I am not seeing any errors in Kamailio Logs. Any pointers on how to get it to serve more calls/sec Regards, Sandeep The most profound statements are often said in silence. -Lynn Johnston

4 3

Re: [SR-Users] Parser error when enabling siptrace with HEP functionality
by Sergey Basov 15 Jan '16

15 Jan '16

And one more thing. In captured packet from Homer, I see original SIP packets, without topoh modifications. But in dump from network interface by wireshark i see that packets was modified... -- Best regards, Sergey Basov e-mail: sergey.v.basov(a)gmail.com SATB-RIPE SATB-UANIC tel: (+38067) 403-62-54

2 17

rtpengine graphite statistics server
by Juha Heinanen 15 Jan '16

15 Jan '16

rtpengine README.md mentions "graphite statistics server". is that server openly available somewhere? -- juha

3 3

Kamailio and NAT
by Nelson Migliaro 15 Jan '16

15 Jan '16

Hello, I am running Kamailio behind NAT. Kanailio has a private IP and I am relaying NAT to internet router. I am using: - #!define WITH_NAT - listen=udp:PRIVATE-IP:5060 advertise PUBLIC-IP:5060 - Patched RTP proxy including the advertise option And everything goes fine. I can make calls and have two way audio. The problem begins when the callee ends the call. BYE is not received in Kamailio (caller) I included the public IP using "add_contact_alias" because "set_contact_alias" was not adding the public IP. I included this in in NATDETECT (pre loaded router) if(is_first_hop()) { xlog("L_NOTICE","Metodo: $rm \n"); xlog("L_NOTICE","is first hop\n"); #set_contact_alias(); if (!add_contact_alias("PUBLIC-IP", "$Rp", "udp")) { xlog("L_ERR", "Error in aliasing contact $ct\n"); send_reply("400", "Bad request"); exit; } } I think the problem is related to destination that BYE is sent by the vendor. From what I see IP and port is taken from advertised in contact (PUBLIC-IP and 5060). The problem is that internet router changes the source port. Contact: <sip:999999999@PRIVATE-IP:5060;alias=PUBLIC-IP~5060~1> --- Is it correcto to add_contact_alias("PUBLIC-IP", "$Rp", "udp") in order to received new transactions or should I follow a different procedure??? Thank you

4 14

dispatcher state x and the return of the probing mode
by Sven Neuhaus 14 Jan '16

14 Jan '16

Hello, when trying to set a destination to inactive using dispatcher.set_state after setting the state to "i", when I do a "dispatcher.list" I see the state as "ix". The "x" state appears not to be documented. After a short time (seconds) the flags return to state "ip" (probing). According to the module documentation I should be able to set the "probing" mode. 1. Why doesn't probing mode remain disabled? 2. What is state "x"? Cheers, -Sven

3 4

using re.subst with an $avp or $var
by Vik Killa 13 Jan '16

13 Jan '16

Hello, Is it possible to use $avp() or $var() inside re.subst? Example: $var(PrefixMatch) = "00"; $var(destnumber1) = $(ru{re.subst,/^sip:$var(PrefixMatch)(.*)@(.*)/\1/}); $var(destnumber2) = $(ru{re.subst,/^sip:00(.*)@(.*)/\1/}); xlog("L_INFO", "destnumber1 $var(destnumber1)\n"); xlog("L_INFO", "destnumber2 $var(destnumber2)\n"); In the above, destnumber2 works, yet destnumber1 does not. Thanks! /V

3 13

RTP Engine multiplexing and De-multiplexing
by riko nir 13 Jan '16

13 Jan '16

Hello, A call from a remote webrtc client is coming to (opensips+rtpengine). The media streams from the webrtc client is multiplexed. Can I use rtpengine to demultiplex the multiplexed streams and send it to other end as de-multiplexed SRTP traffic . This is because, the other end handle the srtp traffic only in demultiplxed manner. Also, the streams from the remote end is a separate SRTP and SRTCP traffic and the rtpengine has to add required ICE information to make the streams to go in a single port and it has to multiplex the streams and send it to webrtc client. It is mentioned that rtpengine can support multiplex/demultiplex. So, how can I configure rtpengine for this purpose from opensips? Your suggestions would be very helpful for us. Thanks. Riko

2 1

Regarding rtpengine dtls handling and fetching crypto keys
by riko nir 13 Jan '16

13 Jan '16

Hi all, I have a media server and it is able to handle SRTP, provided the crypto key. We are planning to give webrtc support to the media server. We are using opensips+rtpengine for that. For dtls, we are using rtpengine. The rtpengine just needs to do the dtls handshake and it needs to fetch the crypto key and it should provide the key to media server, so that the media server will be able to handle the SRTP traffic. We are bit struggling, how to get the crypto keys from rtpengine and send it to opensips and opensips will send it to media server. how this can be done? your suggestions will help us a lot. Thanks, Riko

2 4

siptrace retransmission's
by Grant Bagdasarian 12 Jan '16

12 Jan '16

Hello All, I'm load testing Kamailio with siptrace (duplicate) enabled, but for some reason not all SIP messages are arriving at the sip capture server (kamailio instance with sipcapture). The load is an average of 50 CPS. I enabled debug 9 and I get the following messages. <core> [mem/q_malloc.c:369]: qm_malloc(): qm_malloc(0x7fefde4da010, 1274) called from siptrace: siptrace.c: trace_send_hep_duplicate(1615) <core> [mem/q_malloc.c:439]: qm_free(): qm_free(0x7fefde4da010, 0x7fefde618a88), called from siptrace: siptrace.c: trace_send_hep_duplicate(1659) <core> [mem/q_malloc.c:439]: qm_free(): qm_free(0x7fefde4da010, 0x7fefde61ee18), called from siptrace: siptrace.c: trace_send_hep_duplicate(1660) <core> [mem/q_malloc.c:474]: qm_free(): qm_free: freeing frag. 0x7fefde61ede8 alloc'ed from siptrace: siptrace.c: trace_send_hep_duplicate(1615) <core> [mem/q_malloc.c:369]: qm_malloc(): qm_malloc(0x7fefde4da010, 1271) called from siptrace: siptrace.c: trace_send_hep_duplicate(1615) <core> [mem/q_malloc.c:439]: qm_free(): qm_free(0x7fefde4da010, 0x7fefde61b488), called from siptrace: siptrace.c: trace_send_hep_duplicate(1659) <core> [mem/q_malloc.c:439]: qm_free(): qm_free(0x7fefde4da010, 0x7fefde61e880), called from siptrace: siptrace.c: trace_send_hep_duplicate(1660) <core> [mem/q_malloc.c:474]: qm_free(): qm_free: freeing frag. 0x7fefde61e850 alloc'ed from siptrace: siptrace.c: trace_send_hep_duplicate(1615) DEBUG: siptrace [siptrace.c:1040]: trace_onreq_out(): retransmission DEBUG: siptrace [siptrace.c:1040]: trace_onreq_out(): retransmission DEBUG: siptrace [siptrace.c:1040]: trace_onreq_out(): retransmission DEBUG: siptrace [siptrace.c:1040]: trace_onreq_out(): retransmission DEBUG: siptrace [siptrace.c:1040]: trace_onreq_out(): retransmission DEBUG: siptrace [siptrace.c:1040]: trace_onreq_out(): retransmission DEBUG: siptrace [siptrace.c:1040]: trace_onreq_out(): retransmission In siptrace.c I see the following line of code: if(ps->flags&TMCB_RETR_F) { LM_DBG("retransmission\n"); return; } Does this in fact retransmit the message to the capture server? Has anyone else load tested kamailio with siptrace on? I'm using Kamailio 4.1. I'm also using the setflag(..) function in siptrace module to duplicate all forwarded messages to the capture server. Regards, Grant

2 3

Panning next major release - v4.4
by Daniel-Constantin Mierla 11 Jan '16

11 Jan '16

Hello, sketching the road to the next major release, so people can plan their goals for it and discuss, if needed, before the start of winter holidays: - development freezing by end of January 2016 - test for one to one and a half month - release in the first part of March 2016 If there are important topics to decide on, we can organize an IRC meeting sometime in January 2016. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

4 10

behaviour of exit();
by Grant Bagdasarian 11 Jan '16

11 Jan '16

Hello, I have the following statements in my config script. When either of the IF statements is true, what does the exit function do? Will it still pass the message to the next hop or will it just abort and drop the sip message? failure_route[DISPATCH_FAILURE] { xlog("L_INFO", "[R-FAILURE-ROUTE-DISPATCH-FAILURE:$ci] !>" "Route:DISPATCH_FAILURE;UnixTime:$TV(un);RequestURI:$rU;RequestMethod:$rm;Status:$rs;FromTag:$ft;ToTag:$tt;CallID:$ci;From:$fU;To:$rU\r\n"); t_on_branch("MSG_MOD"); if(t_is_expired()) { xlog("L_INFO", "[R-FAILURE-ROUTE-DISPATCH-FAILURE:$ci] !>" "Transaction expired - aborting\r\n"); exit; } if (t_is_canceled()) { xlog("L_INFO", "[R-FAILURE-ROUTE-DISPATCH-FAILURE:$ci] !>" "Transaction cancelled - aborting\r\n"); exit; } Thanks. Regards, Grant

2 2

Ways to reload Kamailio configuration file without restart
by Amit Patkar 11 Jan '16

11 Jan '16

Hi What are different ways to reload Kamailio configuration file without restart? I need to make configuration file changes on production server without bringing down kamailio service. *Thanks & Regards,* Amit Patkar

2 3

Re: [SR-Users] RTPPorxy -> RTPEngine migration issue
by Arsen Hovhanissian 10 Jan '16

10 Jan '16

Richard that was a champion’s answer thank you so much! Maybe it should be noted kamailio's rtpengine module documentation.

1 0

Re: [SR-Users] RTPPorxy -> RTPEngine migration issue
by Arsen Hovhanissian 10 Jan '16

10 Jan '16

Hi Richard! Here’s the output at log level 7 [1452404737.610730] WARNING: Failed to properly parse UDP command line '11683_0 d7:command4:pinge' from 10.0.0.10:54602, using fallback RE [1452404737.619006] WARNING: Failed to properly parse UDP command line '11683_1 d7:command4:pinge' from 10.0.0.10:59567, using fallback RE [1452404737.621995] WARNING: Failed to properly parse UDP command line '11694_2 d7:command4:pinge' from 10.0.0.10:57256, using fallback RE [1452404737.623204] WARNING: Failed to properly parse UDP command line '11689_1 d7:command4:pinge' from 10.0.0.10:52176, using fallback RE [1452404737.629991] WARNING: Failed to properly parse UDP command line '11687_1 d7:command4:pinge' from 10.0.0.10:55951, using fallback RE [1452404737.630268] WARNING: Failed to properly parse UDP command line '11686_1 d7:command4:pinge' from 10.0.0.10:51267, using fallback RE [1452404737.630392] WARNING: Failed to properly parse UDP command line '11690_1 d7:command4:pinge' from 10.0.0.10:55452, using fallback RE [1452404737.634052] WARNING: Failed to properly parse UDP command line '11688_1 d7:command4:pinge' from 10.0.0.10:49329, using fallback RE [1452404737.635731] WARNING: Failed to properly parse UDP command line '11693_1 d7:command4:pinge' from 10.0.0.10:43723, using fallback RE [1452404737.636118] WARNING: Failed to properly parse UDP command line '11685_1 d7:command4:pinge' from 10.0.0.10:55434, using fallback RE [1452404737.636293] WARNING: Failed to properly parse UDP command line '11692_1 d7:command4:pinge' from 10.0.0.10:34893, using fallback RE Could it be that I am starting it up wrong? Thanks a million!

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users