- sr-users - kamailio.org

DBText does not exists!
by Andrew White 27 Mar '19

27 Mar '19

Hi all, I’m currently playing with the UAC module to hand off remote registrations with trunks to Kamailio. I want to keep Kamailio’s external connections low, so I’m planning to use db_text to load the UAC info, and populate the flat file via other methods. When attempting to load my UAC DB via db_text however, I get the following: Mar 26 04:59:30 ip-10-0-0-2 /usr/local/sbin/kamailio[31904]: ERROR: db_text [dbt_lib.c:143]: dbt_cache_get_db(): database [/etc/kamailio/uac.db] does not exists! Mar 26 04:59:30 ip-10-0-0-2 /usr/local/sbin/kamailio[31902]: INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/31902 Mar 26 04:59:30 ip-10-0-0-2 /usr/local/sbin/kamailio[31904]: ERROR: db_text [dbt_base.c:102]: dbt_init(): cannot get the link to database Mar 26 04:59:30 ip-10-0-0-2 /usr/local/sbin/kamailio[31904]: ERROR: uac [uac_reg.c:1318]: uac_reg_load_db(): failed to connect to the database When running using WITH_DEBUG flag, it does not appear to attempt on normal start. A kamcmd uac.reg_reload yields: Mar 26 05:07:52 ip-10-0-0-2 kamailio: 22(32177) DEBUG: ctl [io_listener.c:442]: handle_new_connect(): handle_stream read: new connection (1) on /var/run/kamailio//kamailio_ctl Mar 26 05:07:52 ip-10-0-0-2 kamailio: 22(32177) DEBUG: <core> [core/sr_module.c:632]: find_mod_export_record(): found export of <db_bind_api> in module db_text [/usr/local/lib64/kamailio/modules/db_text.so] Mar 26 05:07:52 ip-10-0-0-2 kamailio: 22(32177) DEBUG: <core> [db.c:210]: db_bind_mod(): using db bind api for db_text Mar 26 05:07:52 ip-10-0-0-2 kamailio: 22(32177) DEBUG: db_text [dbt_base.c:55]: dbt_init(): initializing for db url: [text:///etc/kamailio/uac.db] Mar 26 05:07:52 ip-10-0-0-2 kamailio: 22(32177) DEBUG: db_text [dbt_lib.c:125]: dbt_cache_get_db(): looking for db /etc/kamailio/uac.db! Mar 26 05:07:52 ip-10-0-0-2 kamailio: 22(32177) ERROR: db_text [dbt_lib.c:143]: dbt_cache_get_db(): database [/etc/kamailio/uac.db] does not exists! Mar 26 05:07:52 ip-10-0-0-2 kamailio: 22(32177) ERROR: db_text [dbt_base.c:102]: dbt_init(): cannot get the link to database Mar 26 05:07:52 ip-10-0-0-2 kamailio: 22(32177) ERROR: uac [uac_reg.c:1318]: uac_reg_load_db(): failed to connect to the database Mar 26 05:07:52 ip-10-0-0-2 kamailio: 22(32177) DEBUG: ctl [io_listener.c:495]: handle_stream_read(): handle_stream read: eof on /var/run/kamailio//kamailio_ctl The file of course does exist, and has fine permissions (Kamailio runs as root in this case): -rw-r--r-- 1 root root 169 Mar 26 04:49 /etc/kamailio/uac.db Contents of file: l_uuid(str) l_username(str) l_domain(str) r_username(str) r_domain(str) realm(str) auth_username(str) auth_password(str) auth_proxy(str) expires(int) flags(int) reg_delay(int) 123:test:test.com:test:test.com:test.com:user:pass:10.0.0.100:600:: (At this stage I just want to see the reg packet in Wireshark). 1) Is this the correct method to do UAC? Load credentials, then Kamailio will handle the registration and renewal? I’ve struggled a bit to understand the documentation, hence the testing 2) Why is my db_text failing to load the file? Thanks! ________________________________ Andrew White - Director uConnected Email: andrew(a)uconnected.com.au Web: www.uConnected.com.au

3 6

Extract URI from Headers
by Duarte Rocha 27 Mar '19

27 Mar '19

Greetings, In my SBC i usually have to do operations on P-Asserted-Identity and Contact header. For those operations i usually have to get the user part, domain, etc. For that i'm using the URI Transformations provided by Kamailio. However, in order to do this i have to trim the header value by hand in order to remove brackets, display infos, etc. Does Kamailio have a method for extracting the URI from those kinds of headers? Best Regards, Duarte Rocha

3 3

Disable Dispatcher GW from DB
by Patrick Wakano 26 Mar '19

26 Mar '19

Hello list, Hope you are all doing well! I am looking for a way to disable a Dispatcher GW from the DB. I know I can disable it using the "kamcmd dispatcher.set_state d ..."command, but in case I do a reload or restart after that, the disabled GW will be back as active. Of course I could also delete the GW from DB, but for CDR purposes I want to keep the entry but mark as permanently disabled, so Kamailio won't try to use it nor ping it anymore. Does anyone how can I do that in the DB? I am looking for the exact same behavior the "kamcmd dispatcher.set_state d" does but from some change in the DB. Thanks, Kind regards, Patrick Wakano

3 5

Presence module. How to update contact DB record after re-SUBSCRIBE ?
by Denys Pozniak 26 Mar '19

26 Mar '19

Hello! We are using Presence module with MySQL with parameters below. And looks like module does not update contact DB record in case of re-SUBSCRIBE. So we have a case when NAT router periodically changes the outgoing port, but NOTIFY from Kamailio goes to port from initial SUBSCRIBE. Is this normal module behavior or we missed something? modparam("presence", "db_url", DBURL) modparam("presence", "subs_db_mode", 3) modparam("presence", "timeout_rm_subs", 0) modparam("presence", "expires_offset", 0) modparam("presence", "max_expires", 1800) modparam("presence", "db_update_period", 30) modparam("presence", "clean_period", 180) modparam("presence", "send_fast_notify", 1) modparam("presence", "pres_htable_size", 32) modparam("presence", "subs_htable_size", 32) modparam("presence", "publ_cache", 0) modparam("presence", "notifier_processes", 0) # kamailio -v version: kamailio 4.4.2 (x86_64/linux) 892ad6 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, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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: 892ad6 compiled on 14:45:42 Sep 26 2017 with gcc 4.8.5 -- BR, Denys Pozniak

1 0

Adding presentity_uri prefix for multi-tenanted presence/dialoginfo configuration
by Rhys Hanrahan 26 Mar '19

26 Mar '19

Hi Everyone, I’ve recently just started working with Kamailio – thanks everyone for this amazing software. Like many people, I’m in the process of trying to put Kamailio in-front of Asterisk to allow it to scale out, and my plan is for Kamailio to take over registrations, usrloc and presence/dialoginfo, as we’ve had issues where handsets are failing to get BLF updates/notifys, so I am hoping a couple of Kamailio boxes can scale better in this regard. DMQ is particularly exciting in how it will allow me to build a truly distributed platform. But I’m struggling to get presence to work the way I need it to. Our environment is multi-tenanted, but we do not (and can’t really) use multi-domains. Instead, we prefix the SIP usernames with the “tenant name” such as tenanta101 and tenantb101. My problem is that all the BLFs are configured for 101@PBX with no tenant name in the User part of the URI so that internal dialing and call pickup will work. Because in Asterisk we use “subscribecontext” this hasn’t been a problem in the past – Asterisk knows for subscriptions coming from that handset that it belongs to that tenant’s context in the dialplan and they are “isolated”, so having handsets subscribe as 101@ in their request URI was never a problem. Of course, with Kamailio I don’t have subscribecontext, and my main issue is that the “presentity_uri” being stored is 101@ while each of the SIP accounts of the handsets are registered as tenenata101@, and as such, no NOTIFYs are sent by Kamailio because it thinks that there are no watchers for the presentity_uri. If I change the SIP account username to 101 to match the BLF key, NOTIFYs are sent as expected. But then this breaks call pickup and internal dialing using the BLF keys. I would rather handle this in Kamailio than in Asterisk and having to re-configure the BLF keys for hundreds of handsets. I need to do something like: * When a SUBSCRIBE comes in, I need to prefix presentity_uri with the tenant name so the subscription changes from 101@ to tenanta101@ in the active_watchers table. * When Kamailio generates a NOTIFY, the notify would be built based on presentity_uri and would come out as tenanta101@, but the phone’s BLFs are configured for 101@ so I would need to *remove* the tenant prefix before sending out the notify. Is there a good, or recommended way to handle this scenario? Maybe something entirely different to changing the presentity_uri? I’ve written the following config to re-write the request URI and To field in any incoming subscribe requests, and successfully got the active_watchers table to store a presentity_uri containing my tenant prefix. But the problem I am having is that I can’t figure out how to modify the NOTIFY packets before they are sent – and looking at cfgtrace, it seems I might not be able to? My “standard” presence + dialoginfo configuration was taken from here as a starting point: https://kb.asipto.com/kamailio:presence:k43-blf Here is what I have so far in terms of trying to make my modifications – any guidance would be greatly appreciated. It feels like there’s probably a better way to do this than re-writing critical headers like To and Request URI? @@ -466,6 +467,8 @@ request_route { # authentication route(AUTH); + route(REWRITE_PRESENCE); + # record routing for dialog forming requests (in case they are routed) # - remove preloaded route headers remove_hf("Route"); # Presence server processing route[PRESENCE] { if(!is_method("PUBLISH|SUBSCRIBE")) return; if(is_method("SUBSCRIBE") && $hdr(Event)=="message-summary") { # Asterisk is our voicemail route(TOASTERISK); # returns here if no voicemail server is configured sl_send_reply("404", "No voicemail service"); exit; } #!ifdef WITH_PRESENCE if (!t_newtran()) { sl_reply_error(); exit; } if(is_method("PUBLISH")) { handle_publish(); t_release(); } else if(is_method("SUBSCRIBE")) { # See REWRITE_PRESENCE - this should have been executed before we get here. handle_subscribe(); t_release(); } exit; #!endif +route[REWRITE_PRESENCE] { + if (is_method("SUBSCRIBE")) { + xlog("Re-writing subscribe to include tenant prefix\n"); + # The default presentity_uri needs to be prefixed with + # the tenant name + # So re-write the To header + route(TENANTINFO); + # Now grab the tenant name. + $var(subscribe_ru) = "sip:" + $var(tenant_name) + $rU + "@" + $rd; + xlog("Re-writing SUBSCRIBE To header as: $var(subscribe_ru)\n"); + insert_hf("To: $var(subscribe_ru)\r\n", "From"); + $ru = $var(subscribe_ru); + # Force change immediately: + # http://www.kamailio.org/wiki/tutorials/faq/main#why_changes_made_to_headers… + msg_apply_changes(); + } else if (is_method("NOTIFY")) { + xlog("Re-writing NOTIFY to remove tenant prefix\n"); # This code block does not get executed right now. + # We are storing the presentity_uri with a tenant prefix + # handsets do not expect this, only 101@, 102@ etc... In their BLF configs + # So this tenant prefix must be removed when building the reply. + route(TENANTINFO); + $var(notify_ru) = "sip:" + $(rU{s.substr,$(var(tenant_name){s.len}),0}) + "@" + $rd; + xlog("Re-writng NOTIFY to use: $var(notify_ru)\n"); + insert_hf("To: $var(notify_ru)\r\n", "From"); + $ru = $var(notify_ru); + # Force change immediately: + # http://www.kamailio.org/wiki/tutorials/faq/main#why_changes_made_to_headers… + msg_apply_changes(); + } +} Thanks for your time. Rhys Hanrahan Chief Information Officer Nexus One Pty Ltd E: support(a)nexusone.com.au<mailto:support@nexusone.com.au> P: +61 2 9191 0606 W: http://www.nexusone.com.au/ M: PO Box 127, Royal Exchange NSW 1225 A: Level 12 227 Elizabeth St, Sydney NSW 2000 [ttp://quintus.nexusone.com.au/~rhys/nexus1-email-sig.jpg]

1 0

kamcmd error
by Zhong, Alec (NSB - CN/Qingdao) 26 Mar '19

26 Mar '19

Hello Could you please help check below error? I encountered below error when to use kamcmd to get the value of one script_counter. [cid:image001.png@01D4E3EB.98F9BB70] BR, Alec

1 0

FW: add script counter.
by Zhong, Alec (NSB - CN/Qingdao) 26 Mar '19

26 Mar '19

Hello, Could you please help check below error for counters module? BR, Alec From: Zhong, Alec (NSB - CN/Qingdao) Sent: 2019年3月26日 10:56 To: 'sr-dev(a)lists.kamailio.org' <sr-dev(a)lists.kamailio.org> Subject: add script counter. Hello, Could you please help check below error? I would like to add a script counter to count the number of received message by kamailio. Anything wrong to use counters module? Should counters.so be loaded? Thank you in advance. Kamailio.cfg change [cid:image001.png@01D4E3C2.32E8DFB0] Kamailo log [cid:image002.png@01D4E3C2.8237E9D0]

1 0

User part on contact header
by Duarte Rocha 25 Mar '19

25 Mar '19

Greetings, On an INVITE the user part in the Contact header mandatory? Can't seem to find info on this. Best regards, Duarte Rocha

3 2

Default port interference in TLS conneciton
by Dalibor Zeman 24 Mar '19

24 Mar '19

Hello, I am running Kamailio v. 5.1.2 with typical configuration for wss connections (default config + tls, websocket, nathelper modules), quite everything is running as should, but I am quite concerned about what I got on Homer server. My Kamailio is listening on port 4443 for TLS. Opening dialog runs as should, then UPDATE and BYE messages are received on 4443, but sent out on 5060. When I don't set up default port, 403 reply comes on a call. I'd like to know whether it is something defined by standard or it has a meaning and I should leave it as it is, or I should correct it somehow and then how. Also, if it has a meaning, then what it is. Thanks for your answer, Dalibor Zeman.

1 0

Modifying NOTIFY of presence_dialoginfo
by Kevin Olbrich 24 Mar '19

24 Mar '19

Hi! I need to customize the content of the NOTIFY sent by presence_dialoginfo. How can I change the message before it is sent? Kind regards Kevin

2 2

KEMI Ruby - exit from within function
by Andrew White 23 Mar '19

23 Mar '19

Hi all, I know ruby is pretty new to KEMI, so I understand this might not be supported. I’ve been able to build a functional basic configuration using KEMI based app_ruby. However the function KSR::x.exit is not exposed to the interpreter. Reading up on the function (https://kamailio.org/docs/tutorials/devel/kamailio-kemi-framework/kemimods/… <https://kamailio.org/docs/tutorials/devel/kamailio-kemi-framework/kemimods/…>) I can see either a native `exit` or a return from the request_route is recommended. The latter of these works fine, however the former throws the following error when called either within the request_route function or any others: Mar 22 03:40:46 guest /usr/sbin/kamailio[17474]: ERROR: {1 19731 BYE 8u6We4ReU01GuU-zoa7VuqC.qWwwg29S} app_ruby [app_ruby_api.c:105]: app_ruby_print_last_exception(): exception: exit Mar 22 03:40:46 guest /usr/sbin/kamailio[17474]: ERROR: {1 19731 BYE 8u6We4ReU01GuU-zoa7VuqC.qWwwg29S} app_ruby [app_ruby_api.c:1078]: app_ruby_run_ex(): ruby exception (6) on callback for: ksr_request_route (res type: 17) It appears the app_ruby wrapper is seeing an exit as an exception and throwing an error. I’m unsure if this is affecting my actual flow (still building the config), but the error in the logs is certainly annoying. Returning from the request_route function works fine, however this is obviously harder to do from within a sub function. Any direction on how to correctly exit in similar ways to native or other KEMI implementations would be appreciated. By the way, thanks Daniel for writing this module! This makes Kamailio significantly more accessible for myself and others like me! ________________________________ Andrew White - Director uConnected Email: andrew(a)uconnected.com.au Web: www.uConnected.com.au

2 3

Kamailio initial log - Mysql error
by Jorge Cornejo 22 Mar '19

22 Mar '19

Hi, I am new at Kamailio, I have installed a vicidial goautodial box and having some headaches. I can see at starup logs the following message: Mar 18 02:12:34 edialer1 /usr/sbin/kamailio[4028]: ERROR: db_mysql [km_my_con.c:129]: db_mysql_new_connection(): driver error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2 "No such file or directory") Mar 18 02:12:34 edialer1 /usr/sbin/kamailio[4028]: ERROR: <core> [db.c:318]: db_do_init2(): could not add connection to the pool Mar 18 02:12:34 edialer1 /usr/sbin/kamailio[4028]: ERROR: usrloc [dlist.c:654]: register_udomain(): failed to open database connection However if I execute the following command: [root@edialer1 kamailio]# kamctl db show subscriber database engine 'MYSQL' loaded Control engine 'RPCFIFO' loaded +----+------------+----------------------------+----------+---------------+- ---------------------------------+----------------------------------+------+ | id | username | domain | password | email_address | ha1 | ha1b | rpid | +----+------------+----------------------------+----------+---------------+- ---------------------------------+----------------------------------+------+ | 18 | 5474470533 | vaglxc01.goautodial.com | | NULL | 10685ad93a251bb460e7dd544a174288 | 1680d2aebe5f750c4eedb45ad6b5ba4f | NULL | | 20 | 5505791853 | edialer1.gevolution.com.br | | NULL | 04e377e3923716fb5038b0caa79b8ed3 | d65362c7ccd934f00efa21c45e479ec5 | NULL | | 21 | 2347600834 | edialer1.gevolution.com.br | | NULL | 065fc461faa06cec682213cf17352630 | 4d79bc7db16f74d13d1785dafb30391c | NULL | +----+------------+----------------------------+----------+---------------+- ---------------------------------+----------------------------------+------+ I get a DB response.so is Kamailio actually connected to the db or not? Also at logs I get Mar 18 02:13:35 edialer1 /usr/sbin/kamailio[4513]: DEBUG: db_mysql [km_res.c:66]: db_mysql_get_columns(): 1 columns returned from the query So I assume it read from the DB something.This is quite confusing as can't say properly if it is working or not. Why I am not sure? Because can't see any information on it sending information to asterisk listening on port 5070, logs won't show such action. As I can't find the asterisk information at the kamailio.cfg file, I assume it is stored at the DB, and if DB connection is broken, would explain why it doesn't work. Can you please help me to figure this out? Thanks in advance

2 1

How fair is the rtpengine loadbalancing?
by Daniel Tryba 22 Mar '19

22 Mar '19

I have 3 rtp backends defined with equal weights (33 each). But when I look at the number of calls being handled the spreaded load is always 5:4:3 for the machines in the orderd listed: modparam("rtpengine", "rtpengine_sock", "udp:10.235.32.60:7723=33 udp:10.235.32.59:7723=33 udp:10.235.32.58:7723=33") Looking at select_rtpp_node_new I see nothing unfair happening (with my total lack of knowledge of how the node set is populated). Anybody else noticing this?

2 1

Auth for SUBSCRIBE and others
by Kevin Olbrich 22 Mar '19

22 Mar '19

Hi! I am implementing forwarding of SUBSCRIBE (BLF) to an Asterisk behind Kamailio. This works but Kamailio is not requesting for Auth. I then added SUBSCRIBE to: https://github.com/kamailio/kamailio/blob/master/etc/kamailio.cfg#L746 And it now challenges the client correctly. Why does this line only show REGISTER? Shouldn't it request a challenge for all messages? And why does it work with INVITES ootb? Thank you! Kind regards Kevin

3 10

Job Offering: Software Engineer & Dev-Ops for VoIP & IMS
by Carsten Bock 22 Mar '19

22 Mar '19

Hi everyone, due to our ongoing growth in the area of mobile network infrastructure, we are currently looking into expanding our team. We are especially looking for: - Software Engineer VoIP & IMS ( https://www.ng-voice.com/software-engineer-voip-ims) - Dev-Ops (VoIP & IMS) (https://www.ng-voice.com/dev-ops-voip-ims) About us ng-voice was founded by a team of leading open-source and VoIP pioneers and passionate coders to develop software for mobile network operators. Our virtualized, cloud native solutions allow entrepreneurial-thinking mobile network operators to become software-centric and offer voice services on any 4G, 5G, WiFi or any other data network – from regular mobile network operators to private networks in remote areas. We are growing the team both in Hamburg and Berlin and are looking for new colleagues to join us. Your responsibilities • Help us deploying and integrating our software solutions • Have fun testing, validating and optimizing our solutions • Enjoy building things and solving complex problems • Proactively identify ways to unlock operational efficiency • Take care of your teammates and have fun growing a company Our requirements We are more interested in your experience and knowledge than in formal degrees: • Strong interest in telephony • Experience with signalling standards (e.g. SIP, DIAMETER) • Fluent in English • Efficient at driving deadlines and keeping yourself and others on topic Our technology stack • Docker; experience with Docker Swarm and Kubernetes is beneficial • Kamailio, RTPEngine, FreeSwitch • Redis, MySQL and RabbitMQ • SIP, RTP, DIAMETER What we offer • Flexible working hours and great office locations (Berlin and Hamburg) • Entrepreneurial culture and flat hierarchies • High degree of autonomy and no dress code • Competitive salary Please send your application to jobs(a)ng-voice.com. Let us know how your profile fits our requirements. And please let us know the earliest date you could join us plus your salary expectations. We look forward to getting to know you! Thanks, Carsten -- Carsten Bock I Managing Director ng-voice GmbH Millerntorplatz 1 I 20359 Hamburg I Germany www.ng-voice.com Mobile +49 (0)179-20 21 244 I Direct +49 (0)40-52 47 593-40 I Fax +49 (0)40-52 47 593-99 Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock, Dr. David Bachmann Ust-ID: DE279344284 Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/

1 0

How can one change acc table name in Kamailio.cfg
by Z 22 Mar '19

22 Mar '19

For some reason these two modparams are always ignored. The table name used is always acc which is default name. How can I change the table name? loadmodule "acc.so" modparam("acc", "db_table_acc", "*acc_$time(year)_$time(mon)*") modparam("acc", "db_table_missed_calls", "*acc_$time(year)_$time(mon)*") Accounting works as expected otherwise. Appreciate any help. Thanks.

3 6

Re: [SR-Users] Problem at Rx Interface - kamailio P-CSCF 5.1.6
by Valentin Christoph 20 Mar '19

20 Mar '19

Hi all, Remember this question from 23.1. It's solved now, thanks for help:-) All the best Christoph Von meinem Samsung Galaxy Smartphone gesendet. -------- Ursprüngliche Nachricht -------- Von: Valentin Christoph <Christoph.Valentin(a)kapsch.net> Datum: 23.01.19 15:06 (GMT+01:00) An: sr-users(a)lists.sip-router.org Cc: Scherney Theodor <Theodor.Scherney(a)kapsch.net>, Onic Roman <Roman.Onic(a)kapsch.net> Betreff: [SR-Users] Problem at Rx Interface - kamailio P-CSCF 5.1.6 Hi all, We are using kamailio 5.1.6, configured as P-CSCF, facing following problem. Please indicate, if you need further information – e.g. I could provide a tshark trace. If during call setup (by simulated UAs) at the terminating P-CSCF the simulated PCRF rejects the Diameter AAR message, then the kamailio P-CSCF runs into a questionable behaviour. By calling the Rx_AAR() function in configuration, the processing of the 200 OK is suspended (by the ims_qos module) and then resumed with the receipt of the AAA message. Now the ims_dialog module is called with the dlg_terminate(“all”, “reason”) function, but the 200 OK has not yet been sent. The ims_dialog sends CANCEL downstream and 488 upstream. However, the 200 OK is sent additionally. We would rather have expected the ims_dialog module should send BYE in both directions. When we respond the CANCEL with 481 Call/Transaction does not exist (which we MUST according to RFC 3261), then we would expect the ims_dialog module at least now to react with BYE in both directions. Could you help? What’s our misunderstanding? How could we proceed to get this issue fixed? Kind regards Christoph P.S.: This is a retransmission, because the original message did not pass moderator approval due to the attached tshark trace The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.

1 0

IMS: ims_isc, ims_registrar_scscf: some additions for 3rd party registration
by Valentin Christoph 20 Mar '19

20 Mar '19

Dear all, Dear Daniel, We had implemented a few additions for third party registration, based on kamailio 5.1.0 IMS modules. * either service info OR original REGISTER request or original 200 OK can be added as body to the 3rd party Registration Request, if indicated by the HSS in the user data * change: S-CSCF does not check for TEL URI, before it sends P-Associated URI to AS (SIP URIs are also sent) We would like to provide a pull request within the next days or week to have the changes as basis for a change in release 5.3.x. Drawback: probably our solution would need to be slightly modified, because we removed the check for TEL URI, if the S-CSCF sends the P-Associated-URI header to the AS in the 3rd party register request (maybe introduce a module parameter?). Any comments? Would it be reviewed and maybe taken for 5.3? All the best Christoph ____ Christoph VALENTIN Software Developer | R&D Core / SIP Core P +43 50 811 3785 | M +43 664 628 3785 christoph.valentin(a)kapsch.net<mailto:christoph.valentin@kapsch.net> Kapsch CarrierCom AG | Lehrbachgasse 11 | 1120 Vienna | Austria Company Register at: Commercial Court Vienna FN 223804 z | Registered Office Vienna | www.kapsch.net<http://www.kapsch.net/> [Kapsch Logo]<https://www.kapsch.net/> The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.

2 1

event_route tm:branch-failure and onreply_route shared variables
by Володимир Іванець 20 Mar '19

20 Mar '19

Hello! I have Kamailio setup with registrar configured to allow multiple registrations. *branch_route[MANAGE_BRANCH]* contains *t_on_reply("REPLY")* and *t_on_branch_failure("FAILURE")*. *event_route[tm:branch-failure:FAILURE]* is used to do some logic, store information in htable and in the end it calls *t_relay* function. This creates new branch. Replies for this branch go to* onreply_route[REPLY]*. The problem is that I can not find appropriate variable that would be available in both *event_route tm:branch-failure* and *onreply_route*. I need it to get saved data from htable. $T_reply_ruid is available in first one but not in second. $T_branch_idx obviously changes so it can not be used. Some registrations do not have *Received* value so source IP address and ports can not be used. *Address* value can be compared with *Contact* header from responce tacket but it is so long that it looks like it's not optimal way to do. What interesting is that $T_reply_ruid is accessible in original replies for branches that have not failed. Does anyone know what variable can be used in this case or how to make sure that $T_reply_ruid will be set? Thanks a lot!

3 6

Pseudo-Variable {$au} is NULL
by Daniel Meyer-Wendt 20 Mar '19

20 Mar '19

Hi All, I am updating our Kamailio from 4.0.6 to the latest 5.2.2, we use kamailio as LB in front of two asterisk server. My problem is that during registration forward to the asterisk servers {$au} is NULL This is the code we have, which is the one you find in most documentations $uac_req(furi)="sip:" + $au + "@" + $var(rip); I logged some Pseudo-Variable to see their contents: {$au} NULL {$aU} NULL {$Au} username(a)domain.com {$fU} username {$oU} NULL {$ru} rU: {sip:domain.com;transport=UDP and ended up doing this which works $uac_req(furi)="sip:" + $fU + "@" + $var(rip); Any idea what could be wrong? Thanks, Daniel

2 2

Kamailio books
by Kevin Olbrich 20 Mar '19

20 Mar '19

Hi! Are there any Kamailio books? I am still struggling with Kamailio on scenarios that need more then REGISTER-offloading (like Kamailio cluster with BLF, custom NOTIFY, DMQ, etc.). Online docs are very limited or use Kamailio as a single tenant PBX. What I need is a high available and high performance proxy in front of asterisk, capable of handling thousands of tenants (each with BLF working). I am perfectly fine with building a solution for several months but I am still unable to understand everything from the docs. Where do the PROs and service companies get their knowledge from? Kind regards Kevin

4 4

Kamailio crashing and infinite-looping when trying to free memory
by Enrico Bandiera 19 Mar '19

19 Mar '19

Hi guys, recently we had some issues with kamailio in production, a proxy at the edge of the infrastructure was crashing seemingly randomly, it happened a couple of times in a timespan of 4-5 days until a point where we found it in an endless loop, unable to process SIP packets anymore and printing in loop messages like these: 50(60) CRITICAL: <core> [core/mem/q_malloc.c:512]: qm_free(): BUG: freeing already freed pointer (0x7ff40a359450), called from core: core/usr_avp.c: destroy_avp_list_unsafe(626), first free core: core/usr_avp.c: destroy_avp_list_unsafe(626) - ignoring 50(60) CRITICAL: <core> [core/mem/q_malloc.c:512]: qm_free(): BUG: freeing already freed pointer (0x7ff409c4fa58), called from core: core/usr_avp.c: destroy_avp_list_unsafe(626), first free core: core/usr_avp.c: destroy_avp_list_unsafe(626) - ignoring We managed to replicate the crash and the loop in a dev environment with a lot of difficulties. It seems not related to the peak load, but to the growing number of processed calls The kamailio version is: version: kamailio 5.2.2 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 5.3.1 Every time this happened it was the timer pid that was crashing or looping, we managed to get 2 core dumps of the crash and 1 of the loop (got it after killing the timer with SIGQUIT). The timer process crashes after attempting to free memory that it's not correctly managed. In particular we saw that it happens inside destroy_avp_list_unsafe() called by the tm timer, when uri_avps_from points to an invalid memory address. We don't use dialog, uac, http_async_client, but we do use topos. In the crash dumps it seems that there's something wrong inside free_cell_helper(), when trying to clean the dead_cell something goes wrong while freeing uri_avps_from, here's the crash log: 61(76) CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 66 0(15) ALERT: <core> [main.c:740]: handle_sigs(): child process 65 exited by a signal 11 0(15) ALERT: <core> [main.c:743]: handle_sigs(): core was generated 0(15) INFO: <core> [main.c:766]: handle_sigs(): terminating due to SIGCHLD <childs getting the SIGTERM signal> 0(15) CRITICAL: <core> [core/mem/q_malloc.c:512]: qm_free(): BUG: freeing already freed pointer (0x7f4d60a2e168), called from htable: ht_api.c: ht_cell_free(217), first free core: core/usr_avp.c: destroy_avp_list_unsafe(626) - ignoring 0(15) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Before the crash we have no warnings on errors about shared memory allocation backtrace: (gdb) bt full #0 0x00000000006371d7 in destroy_avp_list_unsafe (list=0x7f34f7a411b0) at core/usr_avp.c:625 avp = 0x2 foo = 0x2 __func__ = "destroy_avp_list_unsafe" #1 0x00007f351c6909ab in free_cell_helper (dead_cell=0x7f34f7a41018, silent=0, fname=0x7f351c796a02 "timer.c", fline=689) at h_table.c:260 b = 0x0 i = 1 rpl = 0x0 tt = 0x0 foo = 0x11c68daf2 cbs = 0x0 cbs_tmp = 0x7f34f80c3790 __func__ = "free_cell_helper" #2 0x00007f351c7291e6 in wait_handler (ti=1984410416, wait_tl=0x7f34f7a410a0, data=0x7f34f7a41018) at timer.c:689 p_cell = 0x7f34f7a41018 ret = 1 unlinked = 0 rcount = 1 __func__ = "wait_handler" #3 0x00000000004d0f56 in timer_list_expire (t=1984410416, h=0x7f34f6be7850, slow_l=0x7f34f6bea368, slow_mark=2702) at core/timer.c:874 tl = 0x7f34f7a410a0 ret = 0 #4 0x00000000004d13bd in timer_handler () at core/timer.c:939 saved_ticks = 1984410416 run_slow_timer = 0 i = 654 __func__ = "timer_handler" #5 0x00000000004d1845 in timer_main () at core/timer.c:978 No locals. #6 0x0000000000425cc8 in main_loop () at main.c:1727 i = 8 pid = 0 si = 0x0 si_desc = "udp receiver child=7 sock=127.0.0.1:5060 \000\000\000\000q\000\000\000@6y\000\000\000\000\000\000\b\206|\210X\322:\032\301\255\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\002\000\000\000\000\063\275{\000\000\000\000\000>", '\000' <repeats 15 times>, "\320\220\377\226\374\177\000\000\351\022a\000\000\000\000" nrprocs = 8 woneinit = 1 __func__ = "main_loop" #7 0x000000000042ca76 in main (argc=10, argv=0x7ffc96ff9398) at main.c:2696 cfg_stream = 0x25ca010 c = -1 r = 0 tmp = 0x7ffc96ffa4c9 "" tmp_len = -1761635728 port = 32764 proto = -1761635632 options = 0x76c598 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 1492539644 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 2 n_lst = 0x7f351f6f6718 p = 0xffffffff <error: Cannot access memory at address 0xffffffff> st = {st_dev = 2049, st_ino = 1282695, st_nlink = 2, st_mode = 16895, st_uid = 0, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 4096, st_blksize = 4096, st_blocks = 8, st_atim = {tv_sec = 1552931478, tv_nsec = 972761643}, st_mtim = {tv_sec = 1552931478, tv_nsec = 972761643}, st_ctim = {tv_sec = 1552931478, tv_nsec = 972761643}, __glibc_reserved = {0, 0, 0}} __func__ = "main" In the loop dump we have a different situation, there's a loop in the uri_avps_from structure as you can see from the next pointers: (gdb) p *dead_cell->uri_avps_from $3 = {id = 66, flags = 275, next = 0x7ff40a359450, d = {p = 0x7ff40a9ad540, l = 140686126667072, data = "@\325\232\n\364\177\000"}} (gdb) p *dead_cell->uri_avps_from.next $4 = {id = 66, flags = 275, next = 0x7ff409c4fa58, d = {p = 0x7ff40a359480, l = 140686120031360, data = "\200\224\065\n\364\177\000"}} (gdb) p *dead_cell->uri_avps_from.next.next $5 = {id = 66, flags = 275, next = 0x7ff40a359450, d = {p = 0x7ff409c4fa88, l = 140686112651912, data = "\210\372\304\t\364\177\000"}} backtrace: (gdb) bt full #0 0x00007ff43152e67e in _IO_default_xsputn () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00007ff43150150b in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #2 0x00007ff431502ef1 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #3 0x00007ff43150032d in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #4 0x00007ff4315087f7 in fprintf () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #5 0x0000000000686e43 in qm_free (qmp=0x7ff409336000, p=0x7ff409c4fa58, file=0x7e0a75 "core: core/usr_avp.c", func=0x7e2d70 <__func__.8439> "destroy_avp_list_unsafe", line=626, mname=0x7e0a70 "core") at core/mem/q_malloc.c:512 __llevel = -3 qm = 0x7ff409336000 f = 0x7ff409c4fa20 size = 72 next = 0x0 prev = 0x0 __func__ = "qm_free" #6 0x0000000000637209 in destroy_avp_list_unsafe (list=0x7ff409e1b6c8) at core/usr_avp.c:626 avp = 0x7ff40a359450 foo = 0x7ff409c4fa58 __func__ = "destroy_avp_list_unsafe" #7 0x00007ff42ee5d9ab in free_cell_helper (dead_cell=0x7ff409e1b530, silent=0, fname=0x7ff42ef63a02 "timer.c", fline=689) at h_table.c:260 b = 0x0 i = 1 rpl = 0x0 tt = 0x0 foo = 0x12ee5aaf2 cbs = 0x0 cbs_tmp = 0x7ff409c5d420 __func__ = "free_cell_helper" #8 0x00007ff42eef61e6 in wait_handler (ti=89094309, wait_tl=0x7ff409e1b5b8, data=0x7ff409e1b530) at timer.c:689 p_cell = 0x7ff409e1b530 ret = 1 unlinked = 0 rcount = 1 __func__ = "wait_handler" #9 0x00000000004d0f56 in timer_list_expire (t=89094309, h=0x7ff4093b4850, slow_l=0x7ff4093b8058, slow_mark=5981) at core/timer.c:874 tl = 0x7ff409e1b5b8 ret = 0 #10 0x00000000004d13bd in timer_handler () at core/timer.c:939 saved_ticks = 89094309 run_slow_timer = 0 i = 861 __func__ = "timer_handler" #11 0x00000000004d1845 in timer_main () at core/timer.c:978 No locals. #12 0x0000000000425cc8 in main_loop () at main.c:1727 i = 8 pid = 0 si = 0x0 si_desc = "udp receiver child=7 sock=127.0.0.1:5060 \000\000\000\000q\000\000\000@6y\000\000\000\000\000\000\032 t\220\260\242\024\032\301\255\000\000\000\000\000\000\000\000 \000\000\000\000\000\000\000\002\000\000\000\000\063\275{\000\000\000\000\000>", '\000' <repeats 15 times>, "\220\306\336\071\377\177\000\000\351\022a\000\000\000\000" nrprocs = 8 woneinit = 1 __func__ = "main_loop" #13 0x000000000042ca76 in main (argc=10, argv=0x7fff39dec958) at main.c:2696 cfg_stream = 0x2292010 c = -1 r = 0 tmp = 0x7fff39dee4c9 "" tmp_len = 970901552 port = 32767 proto = 970901648 options = 0x76c598 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 2710999419 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 2 n_lst = 0x7ff431ec3718 p = 0xffffffff <error: Cannot access memory at address 0xffffffff> st = {st_dev = 2049, st_ino = 1282695, st_nlink = 2, st_mode = 16895, st_uid = 0, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 4096, st_blksize = 4096, st_blocks = 8, st_atim = {tv_sec = 1552931523, tv_nsec = 918435869}, st_mtim = {tv_sec = 1552994274, tv_nsec = 814438687}, st_ctim = {tv_sec = 1552994274, tv_nsec = 814438687}, __glibc_reserved = {0, 0, 0}} __func__ = "main" We are not sure on how to keep debugging this issue which is causing some serious troubles in our environment, any help is appreciated Here you can find the dumps (beware, 12M download but 1.5G once uncompressed): https://drive.google.com/file/d/1U0LZedyona8jJZHq6HaoqXpfnU83p6Sp/view?usp=… Due thanks to Giacomo Vacca who helped us to dig into this issue. Thanks

2 2

Kamailio 5.1.7 crash
by Jon Bonilla (Manwe) 18 Mar '19

18 Mar '19

Hi all A customer of mine has some crashes every week. We installed the dbg and finally generated a core. Bt full attached. Kamailio installed from kamailio deb 5.1 repos kamailio -V version: kamailio 5.1.7 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 6.3.0 Any hints? thanks, Jon -- https://pekepbx.com https://www.issabel.com/multitenant

3 2

Kamailio as Peer Trunk in Asterisk
by Isravel Raja 18 Mar '19

18 Mar '19

Hi, I wanted to achieve the following scenario with Kamailio and Asterisk/FreeSwitch Kamailio as a trunk for Receiving incoming calls and forward to Asterisk and Make outgoing calls. My current working setup like this VoIP Provider -> Kamailio -> Asterisk Clusters Where Kamailio(NAT for public) and Asterisk in the same local network, So I had to do only one thing just create the SIP trunk in Asterisk for authenticating all the Kamailio Incoming calls and making outgoing calls like this [kamailio] host=172.18.1.1 type=friend disallow=all allow=ulaw context=trunkinbound This is IP based authentication, This is working fine since both servers are in the same local network or having the public IP's What I want is, I want to register the Kamailio Trunk in an asterisk with Username Password authentication, My current setup for making that, VoIP Provider -> Kamailio(Public) -> Asterisk(Randomly Changing Public IP, Broadband Connection) I want to register Kamailio SIP in asterisk trunk so that I can forward the incoming calls to asterisk via SIP extension [kamailio] host=172.18.1.1 user=user secret=password type=friend disallow=all allow=ulaw context=trunkinbound Let me know if anyone doesn't understand my concern This e-mail message and any documents attached to it are confidential and may contain information that is protected from disclosure by various federal and state laws, including the HIPAA privacy rule (45 C.F.R., Part 164). This information is intended to be used solely by the entity or individual to whom this message is addressed. If you are not the intended recipient, be advised that any use, dissemination, forwarding, printing, or copying of this message without the sender's written permission is strictly prohibited and may be unlawful. Accordingly, if you have received this message in error, please notify the sender immediately by return e-mail or call (insert phone number), and then delete this message.

1 0

RFC: rating - ranking system for community
by Daniel-Constantin Mierla 18 Mar '19

18 Mar '19

Hello, starting to continue the discussions here on mailing lists about some of the approached topics during the last IRC meeting -- there will be couple of them. The one now is about finding and deploying a ranking/rating system that could eventually help community members to make decisions easier in regard to what components to use in their voip systems. The need was exemplified by user verticelo with the dificulty to decide what KEMI scripting language to use. While maintaining all the app_xyz are expected to be easy, at least I know that for those I created, the arguments were also from the perspective of the community. Like what others are using, so one can expect good assistance, hints and share of knowledge via community forums. This can be also extended to related tools, like what people use for shared IP high availability of kamailio, preferred database servers, ... This email is to ask if those that didn't participate to IRC devel meeting find such system useful and, if there is a positive feedback, is anyone aware of some OSS that we can deploy on kamailio.org for such purpose? It should be something that allows posting a topic (title and short description) along with a list of answers/options (each can be again like a title and short description) and provide a way to rate the options (like, thumbs up, starts, ...), eventually allowing also comments for each option. I guess it sounds a bit like stackoverflow ... Being users related, the email is sent only to sr-users, let's keep the discussion on this mailing list. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

5 5

Re: [SR-Users] RFC: roadmap to next major release - v5.3.0
by Ilie Soltanici 18 Mar '19

18 Mar '19

Daniel, Sounds good, would be nice to have some improvements on usrloc module, like requested in this topic: https://lists.kamailio.org/pipermail/sr-users/2019-January/104329.html Regards,

2 1

Which RTP addon for RFC4040 Clearmode passthrough support ?
by Olivier 15 Mar '19

15 Mar '19

Hello, I'm looking for a solution to integrate legacy devices to a SIP network. More precisely, I need to forward to and receive Clearmode RTP traffic (see [1]). 1. Do you know any Kamailio-compliant RTP engine (rtpproxy, rtp engine, ..) that support this on a Debian host ? 2. Suggestion ? [1] https://tools.ietf.org/html/rfc4040 Best regards

2 2

rtpengine force-relay
by Vitalii Aleksandrov 15 Mar '19

15 Mar '19

Hi there, Well it's mostly rtpengine question but didn't know where should I send it and probably the answer will be more or less useful for kamailio users. By default if an offer has ICE candidates rtpengine leaves them untouched and just inserts itself as an additional low priority candidate and also rewrites c= line for the callee without ICE support. Using ICE=force-relay rtpengine inserts itself as a "relay" candidate what is great but doesn't touch c= line and callee without ICE have no chance to send RTP to rtpengine. Is it possible somehow to make a third behavior like force-relay + rtpengine IP in c= param? It would allow any callee to send media to rtpengine regardless of ICE support.

3 6

cdp avps issues in kamailio 5.2
by Pavel S 15 Mar '19

15 Mar '19

Hello Mojtava, > Did you use FHOSS or IMS_DIAMETER_SERVER module? No, I am using our own hss server. >Anyway what mandatory parameters do you mean exactly? According to RFC6733 section 5.3.1 - https://tools.ietf.org/html/rfc6733#section-5.3.1 The Capabilities-Exchange-Request (CER), indicated by the Command Code set to 257 and the Command Flags' 'R' bit set, is sent to exchange local capabilities. Upon detection of a transport failure, this message MUST NOT be sent to an alternate peer. When Diameter is run over SCTP [RFC4960] or DTLS/SCTP [RFC6083], which allow for connections to span multiple interfaces and multiple IP addresses, the Capabilities-Exchange-Request message MUST contain one Host-IP-Address AVP for each potential IP address that MAY be locally used when transmitting Diameter messages. Message Format <CER> ::= < Diameter Header: 257, REQ > { Origin-Host } { Origin-Realm } 1* { Host-IP-Address } { Vendor-Id } { Product-Name } [ Origin-State-Id ] * [ Supported-Vendor-Id ] * [ Auth-Application-Id ] * [ Inband-Security-Id ] * [ Acct-Application-Id ] * [ Vendor-Specific-Application-Id ] [ Firmware-Revision ] * [ AVP ] Kamailio 5.1 with loaded cdp, cdr_avp, ims_icsf modules and default configuration described here https://github.com/kamailio/kamailio/tree/master/misc/examples/ims/icscf sends Host-IP-Address but Kamailio 5.2 with the same configuration doesn't. Any idea how to fix it? Regards, Pavel Siderov >Hello, >The CER/CEA messages are used just for connections between two peers >diameter interface. Did you use FHOSS or IMS_DIAMETER_SERVER module? In >both cases, you should not have any issue. Anyway what mandatory parameters >do you mean exactly? >WIth Best Regards. Mojtava ><https://www.kamailio.org/docs/modules/5.1.x/modules/ims_diameter_server.html> >On Tue, Mar 12, 2019 at 8:17 PM Pafel <pafels at gmail.com <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>> wrote: > >>* Hello, *>>>>* I am testing ims setup with kamailio 5.2 using the default configuration *>>* provided here: *>>* https://github.com/kamailio/kamailio/tree/master/misc/examples/ims/ <https://github.com/kamailio/kamailio/tree/master/misc/examples/ims/> . *>>* Тhere is an issue I am facing with cdp avp in request sent to hss. There *>>* are some missing mandatory parameters in capabilities exchange request like *>*> 257 host-ip-address for example. Any idea how to add it via icscf.xml or *>*> kamailio.cfg ? The same parameter is passed to hss with kamailio 5.1 using *>*> default ims configuration. I read cdp and cdp_avp documentation but *>*> couldn't understand if it is possible to add it. *>>>>* Regards, *>>* Pavel Siderov *>>* _______________________________________________ *>>* Kamailio (SER) - Users Mailing List *>>* sr-users at lists.kamailio.org <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> *>*> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> *>>

4 3

Siremis on Kamailio 5.2
by Joel Serrano 15 Mar '19

15 Mar '19

Hi, Just curious if siremis works would work on Kamailio 5.2? The webside might not be updated: Installation Siremis installation is straightforward, being done mostly through a web wizzard. In just a few steps and less than 10 minutes you have your Siremis web site set up and ready to grant you easy administration of your Kamailio SIP server. You need to install first a compatible version of Kamailio SIP Server <https://www.kamailio.org/>. Siremis v5.1.x (devel) *Last release: v5.1.0 (devel version)* *Compatible with: Kamailio 5.1.x, 5.0.x* Thanks! Joel.

2 3

Drop 200OK re-transmissions of suspended transaction
by Marco Capetta 14 Mar '19

14 Mar '19

Hi All, I started playing with async kamailio feature, in particular using "async_route" function provided by ASYNC module (https://www.kamailio.org/docs/modules/5.1.x/modules/async.html#async.f.asyn…). My scenario is the following: - A calls B - B answer the call - inside onreply_route[reply] I catch the 200OK message and I suspend the transaction for X seconds. - after X seconds the transaction is resumed and the call continues as expected Everything looks good, but I encountered an issue trying to drop reply re-transmission messages. My desire is to drop all the messages received from B (basically 200OK re-transmissions) meanwhile the transaction is suspended. I tested "t_is_retr_async_reply" function provided by TM module (https://www.kamailio.org/docs/modules/5.1.x/modules/tm.html#tm.f.t_is_retr_…), but I'm not able to get it worked as expected: - t_is_retr_async_reply() function can be used only inside named 'onreply_route' (no default 'onreply_route' or standard 'reply_route') - drop() function, on the contrary, doesn't allow to drop 200OK messages inside named 'onreply_route' (but only in default 'onreply_route' or standard 'reply_route'). Do you have any suggestion on how I can achieve my task? Thank you very much for your support. Marco

2 2

Kamailio and exporting in-memory dialplan entries to another database
by Olli Attila 14 Mar '19

14 Mar '19

Hello, I was wondering that is there a command / procedure available in Kamailio that would do dialplan.dump on a certain dialplan and then export/write the output to another sql database where another dialplan table is present? This would be a sort of backup procedure that I'm planning. Cheers, Olli

2 1

Kamailio IMS - need help installing and configuring
by Pedro P. 14 Mar '19

14 Mar '19

Hello everyone, I'm starting at Kamailio IMS. However, some tutorials are outdated and the download links did not work. I need help with the installation process, basic settings. Thank you !

1 0

RFC: roadmap to next major release - v5.3.0
by Daniel-Constantin Mierla 14 Mar '19

14 Mar '19

Hello, during the last IRC devel meeting, we approached when the next major release of Kamailio (v5.3.0) should be done, considering two options: 1) before the mid of summer: try to freeze during the second part of May (latest beginning of June) and release during end of June/beginning of July. Afterwards is expected many developers to be in summer vacation (at least July and August are the common holidays months across Europe) 2) during autumn: let the summer pass, allow few weeks so everyone gets sync'ed with what happened during the holidays, freeze by end of September of so, release after 1-1.5 months Right now we have a few new modules, some interesting new features to existing components (e.g., rtpengine ...). If any of you has a strong preference for one option, let us know. This message was sent to both sr-users and sr-dev, you can reply to the one you feel more comfortable with, I will watch both of them and send a summary if we get to some conclusion soon. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

1 0

407 Proxy Authentication Required
by Yağız AYDIN 14 Mar '19

14 Mar '19

Hello, I'm trying to implement Kamailio IMS and registration by using Boghe IMS. Registration profiles are default profiles provided by FHoSS ( Alice & Bob). While trying registration, I am facing some problems. REGISTER message behaves as intended and results with 200 OK. After 200 OK message, Boghe IMS is sending SUBSCRIBE message to S-CSCF (via P-CSCF), this message results with a 407 Proxy Authentication Required, I have some questions about this scenario. 1-) Why do I have this SUBSCRIBE message? Even though i commented out WITH_AUTH function, why do I have 407 Proxy Authentication Required message? 2-) On IMS Client side, when informaion about Alice or Bob is entered, login process results with success, but I can't send any message or do come calls. Is is related about this 407 message? 3-) On FHoSS interface, when I check IMPU values of those users, User-Status is marked as REGISTERED. From this perspective, should I consider registration is successful or not? 4-) How can I handle with this 407 Proxy Authentication Required message? Best Regards, Yağız --

2 4

Add default ports to URIs
by Duarte Rocha 13 Mar '19

13 Mar '19

Greetings, When i receive a message in Kamailio i want to add "5060" to the URI's port info when it's value is not specified. I can do it with pseudovariables but i was wondering if there's any config or setting that would do this automatically? Best Regards, Duarte Rocha

2 2

Kamailio as Peer Trunk in Asterisk
by Isravel Raja 13 Mar '19

13 Mar '19

Hi, I wanted to achieve the following scenario with Kamailio and Asterisk/FreeSwitch Kamailio as a trunk for Receiving incoming calls and forward to Asterisk and Make outgoing calls. My current working setup like this VoIP Provider -> Kamailio -> Asterisk Clusters Where Kamailio(NAT for public) and Asterisk in the same local network, So I had to do only one thing just create the SIP trunk in Asterisk for authenticating all the Kamailio Incoming calls and making outgoing calls like this [kamailio] host=172.18.1.1 type=friend disallow=all allow=ulaw context=trunkinbound This is IP based authentication, This is working fine since both servers are in the same local network or having the public IP's What I want is, I want to register the Kamailio Trunk in an asterisk with Username Password authentication, My current setup for making that, VoIP Provider -> Kamailio(Public) -> Asterisk(Randomly Changing Public IP, Broadband Connection) I want to register Kamailio SIP in asterisk trunk so that I can forward the incoming calls to asterisk via SIP extension [kamailio] host=172.18.1.1 user=user secret=password type=friend disallow=all allow=ulaw context=trunkinbound Let me know if anyone doesn't understand my concern This e-mail message and any documents attached to it are confidential and may contain information that is protected from disclosure by various federal and state laws, including the HIPAA privacy rule (45 C.F.R., Part 164). This information is intended to be used solely by the entity or individual to whom this message is addressed. If you are not the intended recipient, be advised that any use, dissemination, forwarding, printing, or copying of this message without the sender's written permission is strictly prohibited and may be unlawful. Accordingly, if you have received this message in error, please notify the sender immediately by return e-mail or call (insert phone number), and then delete this message.

1 0

radius_www_authorize error code -1
by Denys Pozniak 13 Mar '19

13 Mar '19

Hello! We are using radius_www_authorize() function to authorize incoming SIP REGISTERs, but sometimes happens case -1: for valid credentials (as I could see this in sngrep). And this time I did not detect corresponding Access-Request to RADIUS server side. Setting Kamailio debug level does not help to catch the real reason for this case in syslog. How to investigate this issue? Simple script example: if (!radius_www_authorize("$td")) { switch ($rc) { case -1: send_reply("400", "Bad Request"); exit; default: }; }; # -1 (error) - some error occurred during authorization (see syslog); [root@kamaili]# kamailio -v version: kamailio 4.4.2 (x86_64/linux) 892ad6 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, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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: 892ad6 compiled on 14:33:45 Apr 18 2018 with gcc 4.8.5 [root@kamailio]# rpm -qa | grep freeradius-client freeradius-client-1.1.7-16.el7.centos.x86_64 -- BR, Denys Pozniak

1 0

REGISTRATION ends with 408 Request Timeout
by Yağız AYDIN 13 Mar '19

13 Mar '19

Hello, I am trying to register my Kamailio IMS with Boghe IMS/Client. During registration, I have multiple SUBSCRIBE and NOTIFY requests ends with 408 Request Timeout. Here I provide Kamailio output and SIP traffic. What might be the problem? How can I solve it? Note = On Boghe IMS/Client side, PUBLISH and SUBSCRIBE options are CLOSED. Thanks for helps, Regards ----------P-CSCF----------------- kamailio -f /etc/kamailio/pcscf/kamailio-pcscf-deneme.cfg -Ee loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules 0(30872) INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: 10.3.0.185 [10.3.0.185]:4060 tcp: 10.3.0.185 [10.3.0.185]:4060 Aliases: *: pcscf.mnc001.mcc001.3gppnetwork.org:* WARNING: no fork mode 0(30872) INFO: <core> [core/tcp_main.c:4721]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(30872) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(30872) INFO: rr [rr_mod.c:175]: mod_init(): outbound module not available 0(30872) INFO: ims_usrloc_pcscf [hslot.c:62]: ul_init_locks(): locks array size 512 0(30872) INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(30872) INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 524288 0(30872) WARNING: ims_usrloc_pcscf [usrloc_db.c:61]: connect_db(): DB connection already open... continuing 5(30877) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/30877 0(30872) INFO: <script>: [REGISTER] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: REGISTER (sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, bddf8c98-bdea-229d-3517-3417ec6adcde) 0(30872) ERROR: ims_registrar_pcscf [save.c:342]: save_pending(): Error parsing sec-agree parameters: 4 0(30872) WARNING: ims_usrloc_pcscf [usrloc_db.c:420]: db_update_pcontact_security_temp(): not yet implemented or unknown security type 0(30872) ERROR: ims_usrloc_pcscf [udomain.c:586]: update_temp_security(): Error updating temp security for contact in DB 0(30872) ERROR: ims_registrar_pcscf [save.c:362]: save_pending(): Error updating temp security 0(30872) ERROR: <core> [core/resolve.c:941]: get_record(): unknown type 41 0(30872) INFO: <script>: [REGISTER] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: REGISTER (sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, bddf8c98-bdea-229d-3517-3417ec6adcde) 0(30872) ERROR: ims_registrar_pcscf [save.c:342]: save_pending(): Error parsing sec-agree parameters: 4 0(30872) WARNING: ims_usrloc_pcscf [usrloc_db.c:420]: db_update_pcontact_security_temp(): not yet implemented or unknown security type 0(30872) ERROR: ims_usrloc_pcscf [udomain.c:586]: update_temp_security(): Error updating temp security for contact in DB 0(30872) ERROR: ims_registrar_pcscf [save.c:362]: save_pending(): Error updating temp security 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dfad767b-fcaa-5605-3043-fdab7277afaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0acfa4a0-7899-6d55-4762-e9dd27e7cdd8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, bbef7a73-f999-1250-5310-e8dff2548aa8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ddee4bb5-bcac-26d7-3075-989e77746da9) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, c1dd1520-8cef-5350-3573-8bdf555e77ae) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 8bdb427a-cfbc-521d-6914-8af9744e7fbd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dc8101b5-9f8b-c010-9160-d49a1745f7bd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9ab16525-8c6a-2261-3216-f9ef55729cbb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ab807656-6986-0242-5431-be9f63237878) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9fda4725-fcb8-6457-0576-aefeef0fce6f) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, b8bc1520-fba6-d15c-0744-f955774fcfab) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, faa8a454-669a-0616-5707-f9e85403dcaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0ffe5623-8acd-0762-7058-d9bd0e7eabff) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, acad5a15-efff-1c27-6146-abda7144d6eb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcb4b74-ccbd-6077-4178-a9d83245acad) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, f0af5607-98fa-15d7-6455-988f0e71fadc) 0(30872) ERROR: <core> [core/resolve.c:941]: get_record(): unknown type 41 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, 78277425-cdaf-c80a-ceff-67700e71af89) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcf716a-da9a-6075-3755-8faa2764cfd7) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, f0af5607-98fa-15d7-6455-988f0e71fadc) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dfad767b-fcaa-5605-3043-fdab7277afaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0acfa4a0-7899-6d55-4762-e9dd27e7cdd8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, bbef7a73-f999-1250-5310-e8dff2548aa8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ddee4bb5-bcac-26d7-3075-989e77746da9) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, c1dd1520-8cef-5350-3573-8bdf555e77ae) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 8bdb427a-cfbc-521d-6914-8af9744e7fbd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dc8101b5-9f8b-c010-9160-d49a1745f7bd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9ab16525-8c6a-2261-3216-f9ef55729cbb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ab807656-6986-0242-5431-be9f63237878) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9fda4725-fcb8-6457-0576-aefeef0fce6f) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, b8bc1520-fba6-d15c-0744-f955774fcfab) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, faa8a454-669a-0616-5707-f9e85403dcaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0ffe5623-8acd-0762-7058-d9bd0e7eabff) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, acad5a15-efff-1c27-6146-abda7144d6eb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcb4b74-ccbd-6077-4178-a9d83245acad) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, 78277425-cdaf-c80a-ceff-67700e71af89) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcf716a-da9a-6075-3755-8faa2764cfd7) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dfad767b-fcaa-5605-3043-fdab7277afaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0acfa4a0-7899-6d55-4762-e9dd27e7cdd8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, bbef7a73-f999-1250-5310-e8dff2548aa8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ddee4bb5-bcac-26d7-3075-989e77746da9) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, c1dd1520-8cef-5350-3573-8bdf555e77ae) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 8bdb427a-cfbc-521d-6914-8af9744e7fbd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dc8101b5-9f8b-c010-9160-d49a1745f7bd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9ab16525-8c6a-2261-3216-f9ef55729cbb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ab807656-6986-0242-5431-be9f63237878) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9fda4725-fcb8-6457-0576-aefeef0fce6f) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, b8bc1520-fba6-d15c-0744-f955774fcfab) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, faa8a454-669a-0616-5707-f9e85403dcaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0ffe5623-8acd-0762-7058-d9bd0e7eabff) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, acad5a15-efff-1c27-6146-abda7144d6eb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcb4b74-ccbd-6077-4178-a9d83245acad) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, 78277425-cdaf-c80a-ceff-67700e71af89) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcf716a-da9a-6075-3755-8faa2764cfd7) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dfad767b-fcaa-5605-3043-fdab7277afaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0acfa4a0-7899-6d55-4762-e9dd27e7cdd8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, bbef7a73-f999-1250-5310-e8dff2548aa8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ddee4bb5-bcac-26d7-3075-989e77746da9) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, c1dd1520-8cef-5350-3573-8bdf555e77ae) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 8bdb427a-cfbc-521d-6914-8af9744e7fbd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dc8101b5-9f8b-c010-9160-d49a1745f7bd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9ab16525-8c6a-2261-3216-f9ef55729cbb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ab807656-6986-0242-5431-be9f63237878) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9fda4725-fcb8-6457-0576-aefeef0fce6f) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, b8bc1520-fba6-d15c-0744-f955774fcfab) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, faa8a454-669a-0616-5707-f9e85403dcaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0ffe5623-8acd-0762-7058-d9bd0e7eabff) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, acad5a15-efff-1c27-6146-abda7144d6eb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcb4b74-ccbd-6077-4178-a9d83245acad) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, 78277425-cdaf-c80a-ceff-67700e71af89) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcf716a-da9a-6075-3755-8faa2764cfd7) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dfad767b-fcaa-5605-3043-fdab7277afaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0acfa4a0-7899-6d55-4762-e9dd27e7cdd8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, bbef7a73-f999-1250-5310-e8dff2548aa8) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ddee4bb5-bcac-26d7-3075-989e77746da9) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, c1dd1520-8cef-5350-3573-8bdf555e77ae) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 8bdb427a-cfbc-521d-6914-8af9744e7fbd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dc8101b5-9f8b-c010-9160-d49a1745f7bd) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9ab16525-8c6a-2261-3216-f9ef55729cbb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, ab807656-6986-0242-5431-be9f63237878) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 9fda4725-fcb8-6457-0576-aefeef0fce6f) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, b8bc1520-fba6-d15c-0744-f955774fcfab) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, faa8a454-669a-0616-5707-f9e85403dcaa) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, 0ffe5623-8acd-0762-7058-d9bd0e7eabff) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, acad5a15-efff-1c27-6146-abda7144d6eb) 0(30872) INFO: <script>: [NOTIFY] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: NOTIFY (sip:alice@mnc001.mcc001.3gppnetwork.org ( 10.3.0.187:6060) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcb4b74-ccbd-6077-4178-a9d83245acad) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, 78277425-cdaf-c80a-ceff-67700e71af89) 0(30872) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30872) ERROR: <script>: SUBSCRIBE ( sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.161:49934) to sip:alice@mnc001.mcc001.3gppnetwork.org, dbcf716a-da9a-6075-3755-8faa2764cfd7) ------------------I-CSCF--------------------------------------------------- kamailio -f /etc/kamailio/icscf/kamailio-icscf-deneme.cfg -Ee loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules 0(30791) INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: 10.3.0.186 [10.3.0.186]:4060 tcp: 10.3.0.186 [10.3.0.186]:4060 Aliases: *: icscf.mnc001.mcc001.3gppnetwork.org:* WARNING: no fork mode 0(30791) INFO: <core> [core/tcp_main.c:4721]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(30791) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(30791) INFO: rr [rr_mod.c:175]: mod_init(): outbound module not available 0(30791) INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(30791) INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 524288 0(30791) INFO: cdp [cdp_mod.c:242]: cdp_child_init(): CDiameterPeer child starting ... 5(30797) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/30797 6(30798) INFO: cdp [worker.c:332]: worker_process(): [0] Worker process started... 7(30799) INFO: cdp [worker.c:332]: worker_process(): [1] Worker process started... 8(30800) INFO: cdp [worker.c:332]: worker_process(): [2] Worker process started... 9(30801) INFO: cdp [worker.c:332]: worker_process(): [3] Worker process started... 10(30802) INFO: cdp [worker.c:332]: worker_process(): [4] Worker process started... 11(30803) INFO: cdp [worker.c:332]: worker_process(): [5] Worker process started... 12(30804) INFO: cdp [worker.c:332]: worker_process(): [6] Worker process started... 13(30805) INFO: cdp [worker.c:332]: worker_process(): [7] Worker process started... 14(30806) INFO: cdp [worker.c:332]: worker_process(): [8] Worker process started... 15(30807) INFO: cdp [worker.c:332]: worker_process(): [9] Worker process started... 16(30808) INFO: cdp [worker.c:332]: worker_process(): [10] Worker process started... 17(30809) INFO: cdp [worker.c:332]: worker_process(): [11] Worker process started... 18(30810) INFO: cdp [worker.c:332]: worker_process(): [12] Worker process started... 19(30811) INFO: cdp [worker.c:332]: worker_process(): [13] Worker process started... 20(30812) INFO: cdp [worker.c:332]: worker_process(): [14] Worker process started... 21(30813) INFO: cdp [worker.c:332]: worker_process(): [15] Worker process started... 22(30814) INFO: cdp [receiver.c:449]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... 22(30814) INFO: cdp [receiver.c:454]: receiver_process(): receiver_process(): [] Receiver process starting up... 23(30815) INFO: cdp [receiver.c:449]: receiver_process(): receiver_process(): [hss.mnc001.mcc001.3gppnetwork.org] Receiver process doing init on new process... 23(30815) INFO: cdp [receiver.c:182]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [ hss.mnc001.mcc001.3gppnetwork.org] 24(30816) INFO: cdp [acceptor.c:81]: acceptor_process(): Acceptor process starting up... 0(30791) INFO: cdp [cdp_mod.c:244]: cdp_child_init(): ... CDiameterPeer child started 25(30817) INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... 23(30815) INFO: cdp [receiver.c:454]: receiver_process(): receiver_process(): [hss.mnc001.mcc001.3gppnetwork.org] Receiver process starting up... 24(30816) WARNING: cdp [tcp_accept.c:120]: create_socket(): create_socket(): Trying to open/bind/listen on 10.3.0.186 port 3869 24(30816) WARNING: cdp [tcp_accept.c:145]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.3.0.186 port 3869 24(30816) INFO: cdp [acceptor.c:95]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 25(30817) INFO: cdp [peerstatemachine.c:524]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.mnc001.mcc001.3gppnetwork.org 25(30817) INFO: cdp [receiver.c:868]: peer_connect(): peer_connect(): Trying to connect to 10.3.0.184 port 3868 25(30817) INFO: cdp [receiver.c:937]: peer_connect(): peer_connect(): Peer hss.mnc001.mcc001.3gppnetwork.org:3868 connected 0(30791) INFO: <script>: [REGISTER] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30791) ERROR: <script>: REGISTER (sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.185:4060) to sip:alice@mnc001.mcc001.3gppnetwork.org, bddf8c98-bdea-229d-3517-3417ec6adcde) 0(30791) INFO: ims_icscf [cxdx_uar.c:71]: create_uaa_return_code(): created AVP successfully : [uaa_return_code] 6(30798) INFO: ims_icscf [cxdx_avp.c:137]: cxdx_get_avp(): cxdx_get_result_code: Failed finding avp 6(30798) INFO: ims_icscf [cxdx_uar.c:71]: create_uaa_return_code(): created AVP successfully : [uaa_return_code] 6(30798) ERROR: <core> [core/resolve.c:941]: get_record(): unknown type 41 0(30791) INFO: <script>: [REGISTER] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30791) ERROR: <script>: REGISTER (sip:alice@mnc001.mcc001.3gppnetwork.org (10.3.0.185:4060) to sip:alice@mnc001.mcc001.3gppnetwork.org, bddf8c98-bdea-229d-3517-3417ec6adcde) --------------------------------S-CSCF--------------------------------- kamailio -f /etc/kamailio/scscf/kamailio-scscf-deneme.cfg -Ee loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules 0(30819) INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: 10.3.0.187 [10.3.0.187]:6060 tcp: 10.3.0.187 [10.3.0.187]:6060 Aliases: *: scscf.mnc001.mcc001.3gppnetwork.org:* WARNING: no fork mode 0(30819) INFO: <core> [core/tcp_main.c:4721]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(30819) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(30819) INFO: rr [rr_mod.c:175]: mod_init(): outbound module not available 0(30819) INFO: ims_usrloc_scscf [hslot.c:69]: ul_init_locks(): locks array size 512 0(30819) INFO: ims_usrloc_scscf [contact_hslot.c:67]: init_contacts_locks(): locks array size 512 0(30819) INFO: ims_usrloc_scscf [hslot_sp.c:70]: subs_init_locks(): locks array size 512 0(30819) INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(30819) INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 524288 0(30819) INFO: cdp [cdp_mod.c:242]: cdp_child_init(): CDiameterPeer child starting ... 5(30824) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/30824 6(30825) INFO: cdp [worker.c:332]: worker_process(): [0] Worker process started... 7(30826) INFO: cdp [worker.c:332]: worker_process(): [1] Worker process started... 8(30827) INFO: cdp [worker.c:332]: worker_process(): [2] Worker process started... 9(30828) INFO: cdp [worker.c:332]: worker_process(): [3] Worker process started... 10(30829) INFO: cdp [worker.c:332]: worker_process(): [4] Worker process started... 11(30831) INFO: cdp [worker.c:332]: worker_process(): [5] Worker process started... 12(30833) INFO: cdp [worker.c:332]: worker_process(): [6] Worker process started... 14(30837) INFO: cdp [worker.c:332]: worker_process(): [8] Worker process started... 13(30835) INFO: cdp [worker.c:332]: worker_process(): [7] Worker process started... 15(30838) INFO: cdp [worker.c:332]: worker_process(): [9] Worker process started... 16(30842) INFO: cdp [worker.c:332]: worker_process(): [10] Worker process started... 17(30843) INFO: cdp [worker.c:332]: worker_process(): [11] Worker process started... 19(30847) INFO: cdp [worker.c:332]: worker_process(): [13] Worker process started... 18(30845) INFO: cdp [worker.c:332]: worker_process(): [12] Worker process started... 0(30819) INFO: cdp [cdp_mod.c:244]: cdp_child_init(): ... CDiameterPeer child started 22(30852) INFO: cdp [receiver.c:449]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... 22(30852) INFO: cdp [receiver.c:454]: receiver_process(): receiver_process(): [] Receiver process starting up... 23(30853) INFO: cdp [receiver.c:449]: receiver_process(): receiver_process(): [hss.mnc001.mcc001.3gppnetwork.org] Receiver process doing init on new process... 23(30853) INFO: cdp [receiver.c:182]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [ hss.mnc001.mcc001.3gppnetwork.org] 23(30853) INFO: cdp [receiver.c:454]: receiver_process(): receiver_process(): [hss.mnc001.mcc001.3gppnetwork.org] Receiver process starting up... 25(30858) INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... 24(30854) INFO: cdp [acceptor.c:81]: acceptor_process(): Acceptor process starting up... 20(30849) INFO: cdp [worker.c:332]: worker_process(): [14] Worker process started... 21(30851) INFO: cdp [worker.c:332]: worker_process(): [15] Worker process started... 24(30854) WARNING: cdp [tcp_accept.c:120]: create_socket(): create_socket(): Trying to open/bind/listen on 10.3.0.187 port 3870 24(30854) WARNING: cdp [tcp_accept.c:145]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.3.0.187 port 3870 24(30854) INFO: cdp [acceptor.c:95]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 25(30858) INFO: cdp [peerstatemachine.c:524]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.mnc001.mcc001.3gppnetwork.org 25(30858) INFO: cdp [receiver.c:868]: peer_connect(): peer_connect(): Trying to connect to 10.3.0.184 port 3868 25(30858) INFO: cdp [receiver.c:937]: peer_connect(): peer_connect(): Peer hss.mnc001.mcc001.3gppnetwork.org:3868 connected 0(30819) INFO: <script>: [REGISTER] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: ims_auth [cxdx_mar.c:79]: create_return_code(): created AVP successfully : [maa_return_code] - [-2] 6(30825) INFO: ims_auth [cxdx_avp.c:137]: cxdx_get_avp(): cxdx_get_experimental_result_code: Failed finding avp (avp_code = 297, vendor_id = 0) 6(30825) INFO: ims_auth [cxdx_mar.c:79]: create_return_code(): created AVP successfully : [maa_return_code] - [1] 0(30819) INFO: <script>: [REGISTER] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: ims_auth [authorize.c:827]: authenticate(): uri=sip: mnc001.mcc001.3gppnetwork.org nonce=04cd0652709df5d623429c0dbc8f5f2f response=d3c9e4eb2a533fe48e9569ab128afe53 qop=auth-int nc=00000001 cnonce=b4c66d5473e1da9bf59735657686d706 hbody=d41d8cd98f00b204e9800998ecf8427e 0(30819) INFO: ims_auth [authorize.c:882]: authenticate(): UE said: d3c9e4eb2a533fe48e9569ab128afe53 and we expect d3c9e4eb2a533fe48e9569ab128afe53 ha1 edd6cb70b2ab3a374d5404ac53ea7e55 (REGISTER) 0(30819) WARNING: ims_auth [authorize.c:1006]: authenticate(): NB: Ignoring all failed auth - check your config if you don't expect this 0(30819) INFO: ims_registrar_scscf [cxdx_sar.c:84]: create_return_code(): created AVP successfully : [saa_return_code] - [-2] 7(30826) INFO: ims_registrar_scscf [cxdx_avp.c:138]: cxdx_get_avp(): cxdx_get_experimental_result_code: Failed finding avp 0(30819) INFO: <script>: [REGISTER] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 7(30826) INFO: ims_registrar_scscf [cxdx_sar.c:84]: create_return_code(): created AVP successfully : [saa_return_code] - [1] 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: ims_isc [ims_isc_mod.c:233]: isc_match_filter(): Checking triggers 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: ims_isc [ims_isc_mod.c:233]: isc_match_filter(): Checking triggers 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] 0(30819) INFO: <script>: [SUBSCRIBE] from [ sip:alice@mnc001.mcc001.3gppnetwork.org] to [ sip:alice@mnc001.mcc001.3gppnetwork.org] -----------------------------ngrep------------------------------------------ U 10.3.0.161:62602 -> 10.3.0.185:4060 #1 REGISTER sip:mnc001.mcc001.3gppnetwork.org SIP/2.0..Via: SIP/2.0/UDP 10.3.0 .161:62602;branch=z9hG4bK2293842870;rport..From: <sip:alice@mnc001.mcc001.3 gppnetwork.org>;tag=2293851690..To: <sip:alice@mnc001.mcc001.3gppnetwork.or g>..Contact: <sip:alice@10.3.0.161:62602 ;transport=udp>;expires=600000;+g.o ma.sip-im;language="en,fr";+g.3gpp.smsip;+g.oma.sip-im.large-message;audio; +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-vs";+g.3gpp. cs-voice..Call-ID: 54465103-da8d-a9a9-217a-bd8cabd0a465..CSeq: 5477 REGISTE R..Content-Length: 0..Max-Forwards: 70..Authorization: Digest username="ali ce(a)mnc001.mcc001.3gppnetwork.org",realm="mnc001.mcc001.3gppnetwork.org ",non ce="",uri="sip:mnc001.mcc001.3gppnetwork.org",response=""..Allow: INVITE, A CK, CANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER..Privacy: n one..P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000..User-Agent: I M-client/OMA1.0 Boghe-Win32/v2.0.153.836..P-Preferred-Identity: <sip:alice@ mnc001.mcc001.3gppnetwork.org>..Supported: path.... # U 10.3.0.185:4060 -> 10.3.0.161:62602 #2 SIP/2.0 100 Trying..Via: SIP/2.0/UDP 10.3.0.161:62602 ;branch=z9hG4bK2293842 870;rport=62602;received=10.3.0.161..From: <sip:alice@mnc001.mcc001.3gppnet work.org>;tag=2293851690..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >..Ca ll-ID: 54465103-da8d-a9a9-217a-bd8cabd0a465..CSeq: 5477 REGISTER..Server: K amailio P-CSCF..Content-Length: 0..Warning: 392 10.3.0.185:4060 "Noisy feed back tells: pid=30872 req_src_ip=10.3.0.161 req_src_port=62602 in_uri=sip: mnc001.mcc001.3gppnetwork.org out_uri=sip:mnc001.mcc001.3gppnetwork.org via _cnt==1".... # U 10.3.0.185:4060 -> 10.3.0.161:62602 #3 SIP/2.0 401 Unauthorized - Challenging the UE..Via: SIP/2.0/UDP 10.3.0.161 : 62602;received=10.3.0.161;branch=z9hG4bK2293842870;rport=62602..From: <sip: alice(a)mnc001.mcc001.3gppnetwork.org>;tag=2293851690..To: <sip:alice@mnc001. mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1ae022-78b5..Call-ID: 54465103-da8d-a9a9-217a-bd8cabd0a465..CSeq: 5477 REGISTER..WWW-Authenticat e: Digest realm="mnc001.mcc001.3gppnetwork.org", nonce="f39d692b0ec5f77a16e db779cec82e8e", algorithm=MD5, qop="auth,auth-int"..Server: Kamailio S-CSCF ..Content-Length: 0..Warning: 392 10.3.0.187:6060 "Noisy feedback tells: p id=30827 req_src_ip=10.3.0.186 req_src_port=4060 in_uri=sip: scscf.mnc001.mc c001.3gppnetwork.org:6060 out_uri=sip: scscf.mnc001.mcc001.3gppnetwork.org:6 060 via_cnt==4".... # U 10.3.0.161:62602 -> 10.3.0.185:4060 #4 REGISTER sip:mnc001.mcc001.3gppnetwork.org SIP/2.0..Via: SIP/2.0/UDP 10.3.0 .161:62602;branch=z9hG4bK2293850812;rport..From: <sip:alice@mnc001.mcc001.3 gppnetwork.org>;tag=2293851690..To: <sip:alice@mnc001.mcc001.3gppnetwork.or g>..Contact: <sip:alice@10.3.0.161:62602 ;transport=udp>;expires=600000;+g.o ma.sip-im;language="en,fr";+g.3gpp.smsip;+g.oma.sip-im.large-message;audio; +g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-vs";+g.3gpp. cs-voice..Call-ID: 54465103-da8d-a9a9-217a-bd8cabd0a465..CSeq: 5478 REGISTE R..Content-Length: 0..Max-Forwards: 70..Authorization: Digest username="ali ce(a)mnc001.mcc001.3gppnetwork.org",realm="mnc001.mcc001.3gppnetwork.org ",non ce="f39d692b0ec5f77a16edb779cec82e8e",uri="sip:mnc001.mcc001.3gppnetwork.or g",response="7259db7c12d0cdd550556b25851cc174",algorithm=MD5,cnonce="0a9efc d9c6fca265c8587fd4ea9b75cb",qop=auth-int,nc=00000001..Allow: INVITE, ACK, C ANCEL, BYE, MESSAGE, OPTIONS, NOTIFY, PRACK, UPDATE, REFER..Privacy: none.. P-Access-Network-Info: ADSL;utran-cell-id-3gpp=00000000..User-Agent: IM-cli ent/OMA1.0 Boghe-Win32/v2.0.153.836..P-Preferred-Identity: <sip:alice@mnc00 1.mcc001.3gppnetwork.org>..Supported: path.... # U 10.3.0.185:4060 -> 10.3.0.161:62602 #5 SIP/2.0 100 Trying..Via: SIP/2.0/UDP 10.3.0.161:62602 ;branch=z9hG4bK2293850 812;rport=62602;received=10.3.0.161..From: <sip:alice@mnc001.mcc001.3gppnet work.org>;tag=2293851690..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >..Ca ll-ID: 54465103-da8d-a9a9-217a-bd8cabd0a465..CSeq: 5478 REGISTER..Server: K amailio P-CSCF..Content-Length: 0..Warning: 392 10.3.0.185:4060 "Noisy feed back tells: pid=30872 req_src_ip=10.3.0.161 req_src_port=62602 in_uri=sip: mnc001.mcc001.3gppnetwork.org out_uri=sip:mnc001.mcc001.3gppnetwork.org via _cnt==1".... # U 10.3.0.185:4060 -> 10.3.0.161:56702 #6 NOTIFY sip:alice@10.3.0.161:56702;transport=udp SIP/2.0..Via: SIP/2.0/UDP 1 0.3.0.185:4060;branch=z9hG4bKea02.bd6e4c76e778b145d63e9c39c5faf221.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bKea02.eb9813f500000000000000000000 0000.0..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=1753523419..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1a e022-7ed6..CSeq: 24556 NOTIFY..Call-ID: dfad767b-fcaa-5605-3043-fdab7277afa a..Content-Length: 1398..User-Agent: Kamailio S-CSCF..Contact: <sip:scscf.m nc001.mcc001.3gppnetwork.org:6060>..Event: reg..Max-Forwards: 69..Subscript ion-State: active;expires=59687..Content-Type: application/reginfo+xml....< ?xml version="1.0"?>.<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" versio n="89" state="full">..<registration aor="sip:alice@mnc001.mcc001.3gppnetwor k.org" id="0x7f29e0645ce8" state="active">...<contact id="0x7f29e0647128" s tate="active" event="registered" expires="3136" q="0.000">....<uri>sip:alic e@10.3.0.161:49428;transport=udp</uri>...<unknown-param name="+g.3gpp.smsip "></unknown-param>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.07FFF00 0BDBP-1022urn-70X0.07FFF000BDB9P-10223gpp-application.ims.iari.gsma-vs"</un known-param>...</contact>...<contact id="0x7f29e065aa28" state="active" eve nt="registered" expires="3226" q="0.000">....<uri> sip:alice@10.3.0.161:4993 4;transport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0000 0EBB514F8P-1022urn-70X0.07F29E4A137CBP-10223gpp # U 10.3.0.185 -> 10.3.0.161 +21732@1480:600 #7 -application.ims.iari.gsma-vs"</unknown-param>...<unknown-param name="+g.3g pp.smsip"></unknown-param>...<unknown-param name="expires">"600000"</unknow n-param>...</contact>...<contact id="0x7f29e065ecd0" state="active" event=" registered" expires="3600" q="0.000">....<uri>sip:alice@10.3.0.161:62602 ;tr ansport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0558E280 4FB7P-1022urn-70X0P+03gpp-application.ims.iari.gsma-vs"</unknown-param>...< unknown-param name="+g.3gpp.smsip"></unknown-param>...<unknown-param name=" expires">"600000"</unknown-param>...</contact>..</registration>.</reginfo>. # U 10.3.0.185:4060 -> 10.3.0.161:64088 #8 NOTIFY sip:alice@10.3.0.161:64088;transport=udp SIP/2.0..Via: SIP/2.0/UDP 1 0.3.0.185:4060;branch=z9hG4bK9034.6bdcb80f0efd1d4d8e90e90788523e14.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bK9034.8b235b5600000000000000000000 0000.0..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=1753616070..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1a e022-cc79..CSeq: 24553 NOTIFY..Call-ID: 0acfa4a0-7899-6d55-4762-e9dd27e7cdd 8..Content-Length: 1397..User-Agent: Kamailio S-CSCF..Contact: <sip:scscf.m nc001.mcc001.3gppnetwork.org:6060>..Event: reg..Max-Forwards: 69..Subscript ion-State: active;expires=59792..Content-Type: application/reginfo+xml....< ?xml version="1.0"?>.<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" versio n="86" state="full">..<registration aor="sip:alice@mnc001.mcc001.3gppnetwor k.org" id="0x7f29e0645ce8" state="active">...<contact id="0x7f29e0647128" s tate="active" event="registered" expires="3136" q="0.000">....<uri>sip:alic e@10.3.0.161:49428;transport=udp</uri>...<unknown-param name="+g.3gpp.smsip "></unknown-param>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.07FFF00 0BDBP-1022urn-70X0.07FFF000BDB9P-10223gpp-application.ims.iari.gsma-vs"</un known-param>...</contact>...<contact id="0x7f29e065aa28" state="active" eve nt="registered" expires="3226" q="0.000">....<uri> sip:alice@10.3.0.161:4993 4;transport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0000 0EBB514FP-1022urn-70X0.07F29E4A137CBP-10223gpp- # U 10.3.0.185 -> 10.3.0.161 +21733@1480:599 #9 application.ims.iari.gsma-vs"</unknown-param>...<unknown-param name="+g.3gp p.smsip"></unknown-param>...<unknown-param name="expires">"600000"</unknown -param>...</contact>...<contact id="0x7f29e065ecd0" state="active" event="r egistered" expires="3600" q="0.000">....<uri>sip:alice@10.3.0.161:62602 ;tra nsport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0558E2804 FB7P-1022urn-70X0P+03gpp-application.ims.iari.gsma-vs"</unknown-param>...<u nknown-param name="+g.3gpp.smsip"></unknown-param>...<unknown-param name="e xpires">"600000"</unknown-param>...</contact>..</registration>.</reginfo>. # U 10.3.0.185:4060 -> 10.3.0.161:49483 #10 NOTIFY sip:alice@10.3.0.161:49483;transport=udp SIP/2.0..Via: SIP/2.0/UDP 1 0.3.0.185:4060;branch=z9hG4bK8bbf.b5ae369a8d069d44118b59a4d45a757b.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bK8bbf.34d5484200000000000000000000 0000.0..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=2274225491..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1a e022-b2dc..CSeq: 24511 NOTIFY..Call-ID: c1dd1520-8cef-5350-3573-8bdf555e77a e..Content-Length: 1398..User-Agent: Kamailio S-CSCF..Contact: <sip:scscf.m nc001.mcc001.3gppnetwork.org:6060>..Event: reg..Max-Forwards: 69..Subscript ion-State: active;expires=580374..Content-Type: application/reginfo+xml.... <?xml version="1.0"?>.<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" versi on="44" state="full">..<registration aor="sip:alice@mnc001.mcc001.3gppnetwo rk.org" id="0x7f29e0645ce8" state="active">...<contact id="0x7f29e0647128" state="active" event="registered" expires="3135" q="0.000">....<uri>sip:ali ce@10.3.0.161:49428;transport=udp</uri>...<unknown-param name="+g.3gpp.smsi p"></unknown-param>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.07FFF0 00BDBP-1022urn-70X0.07FFF000BDB9P-10223gpp-application.ims.iari.gsma-vs"</u nknown-param>...</contact>...<contact id="0x7f29e065aa28" state="active" ev ent="registered" expires="3225" q="0.000">....<uri> sip:alice@10.3.0.161:499 34;transport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.000 00EBB514F8P-1022urn-70X0.07F29E4A137CBP-10223gp # U 10.3.0.185 -> 10.3.0.161 +21734@1480:601 #11 p-application.ims.iari.gsma-vs"</unknown-param>...<unknown-param name="+g.3 gpp.smsip"></unknown-param>...<unknown-param name="expires">"600000"</unkno wn-param>...</contact>...<contact id="0x7f29e065ecd0" state="active" event= "registered" expires="3599" q="0.000">....<uri>sip:alice@10.3.0.161:62602 ;t ransport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0558E28 04FB7P-1022urn-70X0P+03gpp-application.ims.iari.gsma-vs"</unknown-param>... <unknown-param name="+g.3gpp.smsip"></unknown-param>...<unknown-param name= "expires">"600000"</unknown-param>...</contact>..</registration>.</reginfo> . # U 10.3.0.185:4060 -> 10.3.0.161:52923 #12 NOTIFY sip:alice@10.3.0.161:52923;transport=udp SIP/2.0..Via: SIP/2.0/UDP 1 0.3.0.185:4060;branch=z9hG4bKadba.ce55b6f7bef3f603cde4a55375dd8c86.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bKadba.d52eaf2600000000000000000000 0000.0..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=2273886730..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1a e022-d59d..CSeq: 24517 NOTIFY..Call-ID: bbef7a73-f999-1250-5310-e8dff2548aa 8..Content-Length: 1398..User-Agent: Kamailio S-CSCF..Contact: <sip:scscf.m nc001.mcc001.3gppnetwork.org:6060>..Event: reg..Max-Forwards: 69..Subscript ion-State: active;expires=580056..Content-Type: application/reginfo+xml.... <?xml version="1.0"?>.<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" versi on="50" state="full">..<registration aor="sip:alice@mnc001.mcc001.3gppnetwo rk.org" id="0x7f29e0645ce8" state="active">...<contact id="0x7f29e0647128" state="active" event="registered" expires="3136" q="0.000">....<uri>sip:ali ce@10.3.0.161:49428;transport=udp</uri>...<unknown-param name="+g.3gpp.smsi p"></unknown-param>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.07FFF0 00BDBP-1022urn-70X0.07FFF000BDB9P-10223gpp-application.ims.iari.gsma-vs"</u nknown-param>...</contact>...<contact id="0x7f29e065aa28" state="active" ev ent="registered" expires="3226" q="0.000">....<uri> sip:alice@10.3.0.161:499 34;transport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.000 00EBB514F8P-1022urn-70X0.07F29E4A137CBP-10223gp # U 10.3.0.185 -> 10.3.0.161 +21735@1480:601 #13 p-application.ims.iari.gsma-vs"</unknown-param>...<unknown-param name="+g.3 gpp.smsip"></unknown-param>...<unknown-param name="expires">"600000"</unkno wn-param>...</contact>...<contact id="0x7f29e065ecd0" state="active" event= "registered" expires="3600" q="0.000">....<uri>sip:alice@10.3.0.161:62602 ;t ransport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0558E28 04FB7P-1022urn-70X0P+03gpp-application.ims.iari.gsma-vs"</unknown-param>... <unknown-param name="+g.3gpp.smsip"></unknown-param>...<unknown-param name= "expires">"600000"</unknown-param>...</contact>..</registration>.</reginfo> . # U 10.3.0.185:4060 -> 10.3.0.161:51090 #14 NOTIFY sip:alice@10.3.0.161:51090;transport=udp SIP/2.0..Via: SIP/2.0/UDP 1 0.3.0.185:4060;branch=z9hG4bKdd46.16bbd8e9fa22e61163e25a1b1cb4da7d.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bKdd46.3f6d5b6200000000000000000000 0000.0..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=2274040838..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1a e022-ca38..CSeq: 24514 NOTIFY..Call-ID: ddee4bb5-bcac-26d7-3075-989e77746da 9..Content-Length: 1397..User-Agent: Kamailio S-CSCF..Contact: <sip:scscf.m nc001.mcc001.3gppnetwork.org:6060>..Event: reg..Max-Forwards: 69..Subscript ion-State: active;expires=580239..Content-Type: application/reginfo+xml.... <?xml version="1.0"?>.<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" versi on="47" state="full">..<registration aor="sip:alice@mnc001.mcc001.3gppnetwo rk.org" id="0x7f29e0645ce8" state="active">...<contact id="0x7f29e0647128" state="active" event="registered" expires="3136" q="0.000">....<uri>sip:ali ce@10.3.0.161:49428;transport=udp</uri>...<unknown-param name="+g.3gpp.smsi p"></unknown-param>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.07FFF0 00BDBP-1022urn-70X0.07FFF000BDB9P-10223gpp-application.ims.iari.gsma-vs"</u nknown-param>...</contact>...<contact id="0x7f29e065aa28" state="active" ev ent="registered" expires="3226" q="0.000">....<uri> sip:alice@10.3.0.161:499 34;transport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.000 00EBB514FP-1022urn-70X0.07F29E4A137CBP-10223gpp # U 10.3.0.185 -> 10.3.0.161 +21736@1480:600 #15 -application.ims.iari.gsma-vs"</unknown-param>...<unknown-param name="+g.3g pp.smsip"></unknown-param>...<unknown-param name="expires">"600000"</unknow n-param>...</contact>...<contact id="0x7f29e065ecd0" state="active" event=" registered" expires="3600" q="0.000">....<uri>sip:alice@10.3.0.161:62602 ;tr ansport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0558E280 4FB7P-1022urn-70X0P+03gpp-application.ims.iari.gsma-vs"</unknown-param>...< unknown-param name="+g.3gpp.smsip"></unknown-param>...<unknown-param name=" expires">"600000"</unknown-param>...</contact>..</registration>.</reginfo>. # U 10.3.0.185:4060 -> 10.3.0.161:60376 #16 NOTIFY sip:alice@10.3.0.161:60376;transport=udp SIP/2.0..Via: SIP/2.0/UDP 1 0.3.0.185:4060;branch=z9hG4bK0274.dd46eeff6c2e63dfce9ab8268123f312.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bK0274.a63fdda300000000000000000000 0000.0..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=2275281208..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1a e022-a078..CSeq: 24505 NOTIFY..Call-ID: dc8101b5-9f8b-c010-9160-d49a1745f7b d..Content-Length: 1398..User-Agent: Kamailio S-CSCF..Contact: <sip:scscf.m nc001.mcc001.3gppnetwork.org:6060>..Event: reg..Max-Forwards: 69..Subscript ion-State: active;expires=581479..Content-Type: application/reginfo+xml.... <?xml version="1.0"?>.<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" versi on="38" state="full">..<registration aor="sip:alice@mnc001.mcc001.3gppnetwo rk.org" id="0x7f29e0645ce8" state="active">...<contact id="0x7f29e0647128" state="active" event="registered" expires="3135" q="0.000">....<uri>sip:ali ce@10.3.0.161:49428;transport=udp</uri>...<unknown-param name="+g.3gpp.smsi p"></unknown-param>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.07FFF0 00BDBP-1022urn-70X0.07FFF000BDB9P-10223gpp-application.ims.iari.gsma-vs"</u nknown-param>...</contact>...<contact id="0x7f29e065aa28" state="active" ev ent="registered" expires="3225" q="0.000">....<uri> sip:alice@10.3.0.161:499 34;transport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.000 00EBB514F8P-1022urn-70X0.07F29E4A137CBP-10223gp # U 10.3.0.185 -> 10.3.0.161 +21737@1480:601 #17 p-application.ims.iari.gsma-vs"</unknown-param>...<unknown-param name="+g.3 gpp.smsip"></unknown-param>...<unknown-param name="expires">"600000"</unkno wn-param>...</contact>...<contact id="0x7f29e065ecd0" state="active" event= "registered" expires="3599" q="0.000">....<uri>sip:alice@10.3.0.161:62602 ;t ransport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0558E28 04FB7P-1022urn-70X0P+03gpp-application.ims.iari.gsma-vs"</unknown-param>... <unknown-param name="+g.3gpp.smsip"></unknown-param>...<unknown-param name= "expires">"600000"</unknown-param>...</contact>..</registration>.</reginfo> . # U 10.3.0.185:4060 -> 10.3.0.161:49513 #18 NOTIFY sip:alice@10.3.0.161:49513;transport=udp SIP/2.0..Via: SIP/2.0/UDP 1 0.3.0.185:4060;branch=z9hG4bKa26e.b002c543e82c8cd2471829e5f2fbb146.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bKa26e.bab0c7d300000000000000000000 0000.0..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=2274232905..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1a e022-bb04..CSeq: 24508 NOTIFY..Call-ID: 8bdb427a-cfbc-521d-6914-8af9744e7fb d..Content-Length: 1397..User-Agent: Kamailio S-CSCF..Contact: <sip:scscf.m nc001.mcc001.3gppnetwork.org:6060>..Event: reg..Max-Forwards: 69..Subscript ion-State: active;expires=580431..Content-Type: application/reginfo+xml.... <?xml version="1.0"?>.<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" versi on="41" state="full">..<registration aor="sip:alice@mnc001.mcc001.3gppnetwo rk.org" id="0x7f29e0645ce8" state="active">...<contact id="0x7f29e0647128" state="active" event="registered" expires="3135" q="0.000">....<uri>sip:ali ce@10.3.0.161:49428;transport=udp</uri>...<unknown-param name="+g.3gpp.smsi p"></unknown-param>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.07FFF0 00BDBP-1022urn-70X0.07FFF000BDB9P-10223gpp-application.ims.iari.gsma-vs"</u nknown-param>...</contact>...<contact id="0x7f29e065aa28" state="active" ev ent="registered" expires="3225" q="0.000">....<uri> sip:alice@10.3.0.161:499 34;transport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.000 00EBB514FP-1022urn-70X0.07F29E4A137CBP-10223gpp # U 10.3.0.185 -> 10.3.0.161 +21738@1480:600 #19 -application.ims.iari.gsma-vs"</unknown-param>...<unknown-param name="+g.3g pp.smsip"></unknown-param>...<unknown-param name="expires">"600000"</unknow n-param>...</contact>...<contact id="0x7f29e065ecd0" state="active" event=" registered" expires="3599" q="0.000">....<uri>sip:alice@10.3.0.161:62602 ;tr ansport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0558E280 4FB7P-1022urn-70X0P+03gpp-application.ims.iari.gsma-vs"</unknown-param>...< unknown-param name="+g.3gpp.smsip"></unknown-param>...<unknown-param name=" expires">"600000"</unknown-param>...</contact>..</registration>.</reginfo>. # U 10.3.0.185:4060 -> 10.3.0.161:59883 #20 NOTIFY sip:alice@10.3.0.161:59883;transport=udp SIP/2.0..Via: SIP/2.0/UDP 1 0.3.0.185:4060;branch=z9hG4bKfe92.82fddde6e4a09dafdade08e6ff2ef6b7.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bKfe92.6cfb0d5700000000000000000000 0000.0..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=2275595571..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1a e022-4f19..CSeq: 24504 NOTIFY..Call-ID: ab807656-6986-0242-5431-be9f6323787 8..Content-Length: 1398..User-Agent: Kamailio S-CSCF..Contact: <sip:scscf.m nc001.mcc001.3gppnetwork.org:6060>..Event: reg..Max-Forwards: 69..Subscript ion-State: active;expires=581765..Content-Type: application/reginfo+xml.... <?xml version="1.0"?>.<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" versi on="37" state="full">..<registration aor="sip:alice@mnc001.mcc001.3gppnetwo rk.org" id="0x7f29e0645ce8" state="active">...<contact id="0x7f29e0647128" state="active" event="registered" expires="3135" q="0.000">....<uri>sip:ali ce@10.3.0.161:49428;transport=udp</uri>...<unknown-param name="+g.3gpp.smsi p"></unknown-param>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.07FFF0 00BDBP-1022urn-70X0.07FFF000BDB9P-10223gpp-application.ims.iari.gsma-vs"</u nknown-param>...</contact>...<contact id="0x7f29e065aa28" state="active" ev ent="registered" expires="3225" q="0.000">....<uri> sip:alice@10.3.0.161:499 34;transport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.000 00EBB514F8P-1022urn-70X0.07F29E4A137CBP-10223gp # U 10.3.0.185 -> 10.3.0.161 +21739@1480:601 #21 p-application.ims.iari.gsma-vs"</unknown-param>...<unknown-param name="+g.3 gpp.smsip"></unknown-param>...<unknown-param name="expires">"600000"</unkno wn-param>...</contact>...<contact id="0x7f29e065ecd0" state="active" event= "registered" expires="3599" q="0.000">....<uri>sip:alice@10.3.0.161:62602 ;t ransport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.0558E28 04FB7P-1022urn-70X0P+03gpp-application.ims.iari.gsma-vs"</unknown-param>... <unknown-param name="+g.3gpp.smsip"></unknown-param>...<unknown-param name= "expires">"600000"</unknown-param>...</contact>..</registration>.</reginfo> . # I 10.3.0.161 -> 10.3.0.185 3:3 #22 ....E..4T...@..f...........~. ..NOTIFY sip:alice@10.3.0.161:56702 ;transport =udp SIP/2.0..Via: SIP/2.0/UDP 10.3.0.185:4060 ;branch=z9hG4bKea02.bd6e4c76e 778b145d63e9c39c5faf221.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bKe a02.eb9813f5000000000000000000000000.0..To: <sip:alice@mnc001.mcc001.3gppne twork.org>;tag=1753523419..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >; tag=9bb9548d48f8c3c628773a7ade1ae022-7ed6..CSeq: 24556 NOTIFY..Call-ID: dfa d767b-fcaa-5605-3043-fdab7277afaa..Content-Length: 1398..User-Agent: Kamail io S-CSCF..Contact: <sip:sc # U 10.3.0.185:4060 -> 10.3.0.161:62602 #23 SIP/2.0 200 OK..Via: SIP/2.0/UDP 10.3.0.161:62602 ;received=10.3.0.161;branc h=z9hG4bK2293850812;rport=62602..From: <sip:alice@mnc001.mcc001.3gppnetwork .org>;tag=2293851690..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb 9548d48f8c3c628773a7ade1ae022-442f..Call-ID: 54465103-da8d-a9a9-217a-bd8cab d0a465..CSeq: 5478 REGISTER..Contact: <sip:alice@10.3.0.161:49428 ;transport =udp>;q=0;expires=2823;language="en";+g.3gpp.smsip;+g.oma.sip-im.large-mess age;audio;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-vs ";+g.3gpp.cs-voice, <sip:alice@10.3.0.161:49934 ;transport=udp>;expires=2904 ;+g.3gpp.cs-voice;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-application.ims.iari .gsma-vs";audio;+g.oma.sip-im.large-message;+g.3gpp.smsip;language="en,fr"; +g.oma.sip-im, <sip:alice@10.3.0.161:62602 ;transport=udp>;expires=3240;+g.3 gpp.cs-voice;+g.3gpp.icsi-ref="urn%3Aurn-7%3A3gpp-application.ims.iari.gsma -vs";audio;+g.oma.sip-im.large-message;+g.3gpp.smsip;language="en,fr";+ g.om a.sip-im..P-Associated-URI: <sip:alice@mnc001.mcc001.3gppnetwork.org >..Serv ice-Route: <sip:orig@scscf.mnc001.mcc001.3gppnetwork.org:6060;lr>..Server: Kamailio S-CSCF..Content-Length: 0..Warning: 392 10.3.0.187:6060 "Noisy fee dback tells: pid=30828 req_src_ip=10.3.0.186 req_src_port=4060 in_uri=sip: scscf.mnc001.mcc001.3gppnetwork.org:6060 out_uri=sip:scscf.mnc001.mcc001.3g ppnetwork.org:6060 via_cnt==4".... # U 10.3.0.185:4060 -> 10.3.0.161:64217 #24 NOTIFY sip:alice@10.3.0.161:64217;transport=udp SIP/2.0..Via: SIP/2.0/UDP 1 0.3.0.185:4060;branch=z9hG4bK061f.f9b5369f276621f592a50ad7d13b620e.0..Via: SIP/2.0/UDP 10.3.0.187:6060 ;branch=z9hG4bK061f.4044cf9700000000000000000000 0000.0..To: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=2275735375..From: <sip:alice@mnc001.mcc001.3gppnetwork.org >;tag=9bb9548d48f8c3c628773a7ade1a e022-58ee..CSeq: 24503 NOTIFY..Call-ID: 9ab16525-8c6a-2261-3216-f9ef55729cb b..Content-Length: 1398..User-Agent: Kamailio S-CSCF..Contact: <sip:scscf.m nc001.mcc001.3gppnetwork.org:6060>..Event: reg..Max-Forwards: 69..Subscript ion-State: active;expires=581888..Content-Type: application/reginfo+xml.... <?xml version="1.0"?>.<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" versi on="36" state="full">..<registration aor="sip:alice@mnc001.mcc001.3gppnetwo rk.org" id="0x7f29e0645ce8" state="active">...<contact id="0x7f29e0647128" state="active" event="registered" expires="3135" q="0.000">....<uri>sip:ali ce@10.3.0.161:49428;transport=udp</uri>...<unknown-param name="+g.3gpp.smsi p"></unknown-param>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.07FFF0 00BDBP-1022urn-70X0.07FFF000BDB9P-10223gpp-application.ims.iari.gsma-vs"</u nknown-param>...</contact>...<contact id="0x7f29e065aa28" state="active" ev ent="registered" expires="3225" q="0.000">....<uri> sip:alice@10.3.0.161:499 34;transport=udp</uri>...<unknown-param name="+g.3gpp.icsi-ref">"urn0X0.000 00EBB51718P-1022urn-70X0.07F29E4A137CBP-10223gp --

1 0

Kamailio Peer Trunk in Asterisk
by Isravel Raja Thangamani 13 Mar '19

13 Mar '19

Hi, I wanted to achieve the following scenario with Kamailio and Asterisk/FreeSwitch Kamailio as a trunk for Receiving incoming calls and forward to Asterisk and Make outgoing calls. My current working setup like this VoIP Provider -> Kamailio -> Asterisk Clusters Where Kamailio(NAT for public) and Asterisk in the same local network, So I had to do only one thing just create the SIP trunk in Asterisk for authenticating all the Kamailio Incoming calls and making outgoing calls like this [kamailio] host=172.18.1.1 type=friend disallow=all allow=ulaw context=trunkinbound This is IP based authentication, This is working fine since both servers are in the same local network or having the public IP's What I want is, I want to register the Kamailio Trunk in an asterisk with Username Password authentication, My current setup for making that, VoIP Provider -> Kamailio(Public) -> Asterisk(Randomly Changing Public IP, Broadband Connection) I want to register Kamailio SIP in asterisk trunk so that I can forward the incoming calls to asterisk via SIP extension [kamailio] host=172.18.1.1 user=user secret=password type=friend disallow=all allow=ulaw context=trunkinbound Let me know if anyone doesn't understand my concern Thanks & Regards, Isravel Raja N. Thangamani Work US: +1 424 354 8443 | Home US: +1 480 588 2008 Mobile PH: +63 998 596 7805 | Off Ext: 7901 Address: 15th Fl., Cebu IT Tower - 1, Cebu Business Park, Cebu City, Philippines 6000 Website: www.azpired.com | Email: iraja(a)ebusinessbpo.com <iraja(a)ebusinessbpo.com> Follow us <https://facebook.com/azpiredinc/>. <https://twitter.com/azpired>. <https://plus.google.com/+AzpiredCebuCity>. <https://www.youtube.com/channel/UCrFkeO0pxugkGMtcTRjGxpQ> The information contained in this email message and any attachments is confidential and intended only for the addressee(s). If you are not an addressee, you may not copy or disclose the information, or act upon it, and you should delete it entirely from your email system. Please notify the sender that you received this email in error.

3 2

cdp avps issues in kamailio 5.2
by Pafel 13 Mar '19

13 Mar '19

Hello, I am testing ims setup with kamailio 5.2 using the default configuration provided here: https://github.com/kamailio/kamailio/tree/master/misc/examples/ims/ . Тhere is an issue I am facing with cdp avp in request sent to hss. There are some missing mandatory parameters in capabilities exchange request like 257 host-ip-address for example. Any idea how to add it via icscf.xml or kamailio.cfg ? The same parameter is passed to hss with kamailio 5.1 using default ims configuration. I read cdp and cdp_avp documentation but couldn't understand if it is possible to add it. Regards, Pavel Siderov

2 1

Re: [SR-Users] ACK not forwarding to Asterisk
by Schneuwly Mathias RUAG 13 Mar '19

13 Mar '19

Hi Yasin Thanks for your reply! That means my setup does not work if Kamailio and Asterisk are sitting on the same IP. Or is there something I can do? Do you have a proposal what I could change? Regards Mathias Config snippet of WITHINDLG: ... # Handle requests within SIP dialogs route[WITHINDLG] { xlog("XXXXXXXXXXXXXXXXXXXXXXX\nWITHINDLG\n"); if (!has_totag()) return; # sequential request withing a dialog should # take the path determined by record-routing if (loose_route()) { xlog("XXXXXXXXXXXXXXXXXXXXXXX\nLoose route\n"); if (is_method("BYE")) { setflag(FLT_ACC); # do accounting ... setflag(FLT_ACCFAILED); # ... even if the transaction fails } else if ( is_method("NOTIFY") ) { # Add Record-Route for in-dialog NOTIFY as per RFC 6665. record_route(); } route(RELAY); exit; } if (is_method("SUBSCRIBE") && uri == myself) { # in-dialog subscribe requests route(PRESENCE); exit; } xlog("XXXXXXXXXXXXXXXXXXXXXXX\nWITHINDLG\n"); if ( is_method("ACK") ) { xlog("XXXXXXXXXXXXXXXXXXXXXXX\nACK\n"); if ( t_check_trans() ) { xlog("XXXXXXXXXXXXXXXXXXXXXXX\nt_check_trans\n"); # no loose-route, but stateful ACK; # must be an ACK after a 487 # or e.g. 404 from upstream server route(RELAY); exit; } else { xlog("XXXXXXXXXXXXXXXXXXXXXXX\nignore\n"); # ACK without matching transaction ... ignore and discard exit; } } sl_send_reply("404","Not here"); exit; } ... Following the log output of the relevant OK and ACK: Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/udp_server.c:492]: udp_rcv_loop(): received on udp socket: (106/100/1091) [[SIP/2.0 200 OK 0D 0A Via: SIP/2.0/UDP 10.40.8.104:5070;branch=z9hG4bK4825.fc814778ec04597ae4759a9771bfef0]] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/msg_parser.c:620]: parse_msg(): SIP Reply (status): Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/msg_parser.c:622]: parse_msg(): version: <SIP/2.0> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/msg_parser.c:624]: parse_msg(): status: <200> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/msg_parser.c:626]: parse_msg(): reason: <OK> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK4825.fc814778ec04597ae4759a9771bfef09.0>; state=6 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 234, <received> = <10.40.8.104>; state=16 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/msg_parser.c:498]: parse_headers(): Via found, flags=2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/msg_parser.c:500]: parse_headers(): this is the first via Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 234, <received> = <10.40.6.188>; state=6 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 235, <rport> = <60223>; state=6 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bKPjBBr32NDnGLx0KwymDtyAXs.rIuFIwAdi>; state=16 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/msg_parser.c:498]: parse_headers(): Via found, flags=78 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/msg_parser.c:511]: parse_headers(): this is the second via Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=as21517b15 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=29 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/msg_parser.c:171]: get_hdr_field(): <To> [44]; uri=[sip:004112345@10.40.8.104] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/msg_parser.c:174]: get_hdr_field(): to body [<sip:004112345@10.40.8.104>], to tag [as21517b15] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/msg_parser.c:152]: get_hdr_field(): cseq <CSeq>: <27457> <INVITE> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/receive.c:245]: receive_msg(): --- received sip message - reply - call-id: [otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy] - cseq: [27457 INVITE] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/msg_parser.c:185]: get_hdr_field(): content_length=271 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: <core> [core/parser/msg_parser.c:89]: get_hdr_field(): found end of header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:1043]: t_check_msg(): msg (0xb72fb410) id=26/18447 global id=25/18447 T start=0xffffffff Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:920]: t_reply_matching(): t_reply_matching: hash 21124 label 0 branch 0 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:974]: t_reply_matching(): reply (0xb72fb410) matched an active transaction (T=0xb4931af4)! Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_hooks.c:258]: run_trans_callbacks_internal(): DBG: trans=0xb4931af4, callback type 2, id 0 entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} acc [acc_logic.c:682]: tmcb_func(): acc callback called for t(0xb4931af4) event type 2, reply code 200 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} acc [acc_logic.c:414]: should_acc_reply(): probing acc state - code: 200 flags: 0x2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} acc [acc_logic.c:446]: should_acc_reply(): acc is on Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_hooks.c:258]: run_trans_callbacks_internal(): DBG: trans=0xb4931af4, callback type 2, id 0 entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:712]: dlg_lookup(): ref dlg 0xb4934aec with 1 -> 3 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:714]: dlg_lookup(): dialog id=8415 found on entry 3438 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_profile.c:536]: set_current_dialog(): setting current dialog [3438:8415] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:957]: dlg_unref_helper(): unref op on 0xb4934aec with 1 from dlg_hash.c:975 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:961]: dlg_unref_helper(): unref dlg 0xb4934aec with 1 -> 2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:1113]: t_check_msg(): msg (0xb72fb410) id=26/18447 global id=26/18447 T end=0xb4931af4 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_reply.c:2243]: reply_received(): transaction found - T:0xb4931af4 branch:0 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_reply.c:2258]: reply_received(): org. status uas=200, uac[0]=200 local=0 is_invite=1) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <script>: incoming reply Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_reply.c:1266]: t_should_relay_response(): ->>>>>>>>> T_code=200, new_code=200 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_reply.c:1271]: t_should_relay_response(): 200 INV after final sent Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_reply.c:1824]: relay_reply(): reply status=1 branch=0, save=0, relay=0 icode=0 msg status=200 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_hooks.c:258]: run_trans_callbacks_internal(): DBG: trans=0xb4931af4, callback type 32, id 0 entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:712]: dlg_lookup(): ref dlg 0xb4934aec with 1 -> 3 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:714]: dlg_lookup(): dialog id=8415 found on entry 3438 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:957]: dlg_unref_helper(): unref op on 0xb4934aec with 1 from dlg_hash.c:975 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:961]: dlg_unref_helper(): unref dlg 0xb4934aec with 1 -> 2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/msg_translator.c:2288]: generate_res_buf_from_sip_res(): old size: 1091, new size: 981 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/msg_translator.c:2306]: generate_res_buf_from_sip_res(): copied size: orig:126, new: 16, rest: 965 msg= SIP/2.0 200 OK^M Via: SIP/2.0/UDP 10.40.6.188:60223;received=10.40.6.188;rport=60223;branch=z9hG4bKPjBBr32NDnGLx0KwymDtyAXs.rIuFIwAdi^M Record-Route: <sip:10.40.8.104:5070;lr;ftag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP;did=e6d.fd02>^M From: <sip:proxydevice@10.40.8.104>;tag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP^M To: <sip:004112345@10.40.8.104>;tag=as21517b15^M Call-ID: otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy^M CSeq: 27457 INVITE^M Server: Asterisk PBX 12.3.2^M Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE^M Supported: replaces, timer^M Session-Expires: 1800;refresher=uas^M Contact: <sip:004112345@10.40.8.104:5060>^M Content-Type: application/sdp^M Require: timer^M Content-Length: 271^M ^M v=0^M o=root 623479861 623479861 IN IP4 10.40.8.104^M s=Asterisk PBX 12.3.2^M Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_reply.c:305]: update_totag_set(): to-tag retransmission Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_reply.c:2016]: relay_reply(): reply buffer sent out Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:441]: receive_msg(): reply-route executed in: 490 usec Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_var.c:97]: cb_dlg_locals_reset(): resetting the local dialog shortcuts on script callback: 2147483652 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN last message repeated 5 times Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/xavp.c:495]: xavp_destroy_list(): destroying xavp list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18447]: DEBUG: {2 27457 INVITE otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:457]: receive_msg(): cleaning up Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: <core> [core/udp_server.c:492]: udp_rcv_loop(): received on udp socket: (106/100/442) [[ACK sip:004112345@10.40.8.104:5060 SIP/2.0 0D 0A Via: SIP/2.0/UDP 10.40.6.188:60223;rport;branch=z9hG4bKP]] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: <core> [core/parser/msg_parser.c:610]: parse_msg(): SIP Request: Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: <core> [core/parser/msg_parser.c:612]: parse_msg(): method: <ACK> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: <core> [core/parser/msg_parser.c:614]: parse_msg(): uri: <sip:004112345@10.40.8.104:5060> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: <core> [core/parser/msg_parser.c:616]: parse_msg(): version: <SIP/2.0> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 235, <rport> = <n/a>; state=6 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bKPjvd1MSxMjv6dfOGdbAVxKz.iPtydNiEtQ>; state=16 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: <core> [core/parser/msg_parser.c:498]: parse_headers(): Via found, flags=2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: <core> [core/parser/msg_parser.c:500]: parse_headers(): this is the first via Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=as21517b15 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=29 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: <core> [core/parser/msg_parser.c:171]: get_hdr_field(): <To> [44]; uri=[sip:004112345@10.40.8.104] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: <core> [core/parser/msg_parser.c:174]: get_hdr_field(): to body [<sip:004112345@10.40.8.104>], to tag [as21517b15] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: <core> [core/parser/msg_parser.c:152]: get_hdr_field(): cseq <CSeq>: <27457> <ACK> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: <core> [core/receive.c:245]: receive_msg(): --- received sip message - request - call-id: [otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy] - cseq: [27457 ACK] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: <core> [core/parser/msg_parser.c:185]: get_hdr_field(): content_length=0 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: <core> [core/parser/msg_parser.c:89]: get_hdr_field(): found end of header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:295]: receive_msg(): preparing to run routing scripts... Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sl [sl_funcs.c:397]: sl_filter_ACK(): too late to be a local ACK! Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=29 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:769]: internal_get_dlg(): ref dlg 0xb4934aec with 1 -> 3 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:772]: internal_get_dlg(): dialog callid='otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy' found on entry 3438, dir=1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_profile.c:536]: set_current_dialog(): setting current dialog [3438:8415] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:1158]: next_state_dlg(): dialog 0xb4934aec changed from state 3 to state 4, due event 6 (ref 3) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_timer.c:110]: insert_dialog_timer_unsafe(): inserting 0xb4934b30 for 12143697 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_handlers.c:1475]: dlg_onroute(): confirming ACK successfully processed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:957]: dlg_unref_helper(): unref op on 0xb4934aec with 1 from dlg_hash.c:975 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:961]: dlg_unref_helper(): unref dlg 0xb4934aec with 1 -> 2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} pv [pv_core.c:1031]: pv_get_useragent(): no User-Agent header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} maxfwd [mf_funcs.c:74]: is_maxfwd_present(): value = 70 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:247]: check_ruri_sip_version(): check_ruri_sip_version entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:270]: check_ruri_sip_version(): check_ruri_sip_version passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:277]: check_ruri_scheme(): check_ruri_scheme entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:297]: check_ruri_scheme(): check_ruri_scheme passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:305]: check_required_headers(): check_required_headers entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:313]: check_required_headers(): check_required_headers passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:479]: check_cseq_method(): check_cseq_method entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:512]: check_cseq_method(): check_cseq_method passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:521]: check_cseq_value(): check_cseq_value entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:549]: check_cseq_value(): check_cseq_value passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:558]: check_cl(): check_cl entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:583]: check_cl(): check_cl passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:595]: check_expires_value(): check_expires_value entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:632]: check_expires_value(): no expires header found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:728]: check_parse_uris(): check_parse_uris entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:732]: check_parse_uris(): parsing ruri Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:746]: check_parse_uris(): looking up From header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:786]: check_parse_uris(): parsing From URI Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:804]: check_parse_uris(): looking up To header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:826]: check_parse_uris(): check_parse_uris(): parsing To URI Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:871]: check_parse_uris(): check_parse_uris passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity_mod.c:254]: w_sanity_check(): sanity checks result: 1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: ERROR: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <script>: XXXXXXXXXXXXXXXXXXXXXXX WITHINDLG Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} siputils [checks.c:123]: has_totag(): totag found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [loose.c:91]: is_preloaded(): is_preloaded: No Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/socket_info.c:564]: grep_sock_info(): checking if host==us: 11==11 && [10.40.8.104] == [10.40.8.104] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/socket_info.c:567]: grep_sock_info(): checking if port 5070 (advertise 5070) matches port 5060 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [loose.c:677]: after_strict(): Next hop: 'sip:10.40.8.104:5070;lr;ftag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP;did=e6d.fd02' is loose router Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [loose.c:727]: after_strict(): The last route URI: 'sip:10.40.8.104:5070;lr;ftag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP;did=e6d.fd02' Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: ERROR: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <script>: XXXXXXXXXXXXXXXXXXXXXXX Loose route Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:1346]: t_newtran(): msg (0xb72fb410) id=25/18442 global id=24/18442 T start=0xffffffff Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:500]: t_lookup_request(): start searching: hash=21124, isACK=1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:458]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bKPjvd1MSxMjv6dfOGdbAVxKz.iPtydNiEtQ] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:682]: t_lookup_request(): no transaction found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_funcs.c:287]: t_relay_to(): forwarding ACK statelessly Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/dns_cache.c:3193]: dns_srv_sip_resolve(): (10.40.8.104, 0, 0), ip, ret=0 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/md5utils.c:67]: MD5StringArray(): MD5 calculated: 29cbe80853cc3d43347f3c0b4b643e4c Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/forward.c:557]: forward_request(): Sending: ACK sip:10.40.8.104:5070;lr;ftag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP;did=e6d.fd02 SIP/2.0^M Via: SIP/2.0/UDP 10.40.8.104:5070;branch=z9hG4bK4825.29cbe80853cc3d43347f3c0b4b643e4c.0^M Via: SIP/2.0/UDP 10.40.6.188:60223;received=10.40.6.188;rport=60223;branch=z9hG4bKPjvd1MSxMjv6dfOGdbAVxKz.iPtydNiEtQ^M Max-Forwards: 69^M From: <sip:proxydevice@10.40.8.104>;tag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP^M To: <sip:004112345@10.40.8.104>;tag=as21517b15^M Call-ID: otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy^M CSeq: 27457 ACK^M Content-Length: 0^M ^M . Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/forward.c:559]: forward_request(): orig. len=442, new_len=517, proto=1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:353]: receive_msg(): request-route executed in: 936 usec Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:712]: dlg_lookup(): ref dlg 0xb4934aec with 1 -> 3 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/udp_server.c:492]: udp_rcv_loop(): received on udp socket: (106/100/517) [[ACK sip:10.40.8.104:5070;lr;ftag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP;did=e6d.fd02 SIP/2.0 0D 0A Via: SIP/2.0]] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:714]: dlg_lookup(): dialog id=8415 found on entry 3438 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:957]: dlg_unref_helper(): unref op on 0xb4934aec with 1 from dlg_hash.c:975 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/msg_parser.c:610]: parse_msg(): SIP Request: Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:961]: dlg_unref_helper(): unref dlg 0xb4934aec with 1 -> 2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/msg_parser.c:612]: parse_msg(): method: <ACK> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/msg_parser.c:614]: parse_msg(): uri: <sip:10.40.8.104:5070;lr;ftag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP;did=e6d.fd02> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/msg_parser.c:616]: parse_msg(): version: <SIP/2.0> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK4825.29cbe80853cc3d43347f3c0b4b643e4c.0>; state=16 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/xavp.c:495]: xavp_destroy_list(): destroying xavp list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18442]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:457]: receive_msg(): cleaning up Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/msg_parser.c:498]: parse_headers(): Via found, flags=2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/msg_parser.c:500]: parse_headers(): this is the first via Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 234, <received> = <10.40.6.188>; state=6 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 235, <rport> = <60223>; state=6 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bKPjvd1MSxMjv6dfOGdbAVxKz.iPtydNiEtQ>; state=16 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/msg_parser.c:498]: parse_headers(): Via found, flags=78 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/msg_parser.c:511]: parse_headers(): this is the second via Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=as21517b15 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=29 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/msg_parser.c:171]: get_hdr_field(): <To> [44]; uri=[sip:004112345@10.40.8.104] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/msg_parser.c:174]: get_hdr_field(): to body [<sip:004112345@10.40.8.104>], to tag [as21517b15] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/msg_parser.c:152]: get_hdr_field(): cseq <CSeq>: <27457> <ACK> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/receive.c:245]: receive_msg(): --- received sip message - request - call-id: [otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy] - cseq: [27457 ACK] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/msg_parser.c:185]: get_hdr_field(): content_length=0 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: <core> [core/parser/msg_parser.c:89]: get_hdr_field(): found end of header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:295]: receive_msg(): preparing to run routing scripts... Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sl [sl_funcs.c:397]: sl_filter_ACK(): too late to be a local ACK! Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=29 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:769]: internal_get_dlg(): ref dlg 0xb4934aec with 1 -> 3 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:772]: internal_get_dlg(): dialog callid='otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy' found on entry 3438, dir=1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_profile.c:536]: set_current_dialog(): setting current dialog [3438:8415] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:1158]: next_state_dlg(): dialog 0xb4934aec changed from state 4 to state 4, due event 6 (ref 3) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_timer.c:110]: insert_dialog_timer_unsafe(): inserting 0xb4934b30 for 12143697 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_handlers.c:1480]: dlg_onroute(): sequential request successfully processed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [record.c:925]: add_rr_param(): rr_param_buf=<;did=e6d.fd02> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:957]: dlg_unref_helper(): unref op on 0xb4934aec with 1 from dlg_hash.c:975 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:961]: dlg_unref_helper(): unref dlg 0xb4934aec with 1 -> 2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} pv [pv_core.c:1031]: pv_get_useragent(): no User-Agent header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} maxfwd [mf_funcs.c:74]: is_maxfwd_present(): value = 69 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:247]: check_ruri_sip_version(): check_ruri_sip_version entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:270]: check_ruri_sip_version(): check_ruri_sip_version passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:277]: check_ruri_scheme(): check_ruri_scheme entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:297]: check_ruri_scheme(): check_ruri_scheme passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:305]: check_required_headers(): check_required_headers entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:313]: check_required_headers(): check_required_headers passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:479]: check_cseq_method(): check_cseq_method entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:512]: check_cseq_method(): check_cseq_method passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:521]: check_cseq_value(): check_cseq_value entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:549]: check_cseq_value(): check_cseq_value passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:558]: check_cl(): check_cl entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:583]: check_cl(): check_cl passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:595]: check_expires_value(): check_expires_value entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:632]: check_expires_value(): no expires header found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:728]: check_parse_uris(): check_parse_uris entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:732]: check_parse_uris(): parsing ruri Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:746]: check_parse_uris(): looking up From header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:786]: check_parse_uris(): parsing From URI Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:804]: check_parse_uris(): looking up To header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:826]: check_parse_uris(): check_parse_uris(): parsing To URI Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:871]: check_parse_uris(): check_parse_uris passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity_mod.c:254]: w_sanity_check(): sanity checks result: 1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: ERROR: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <script>: XXXXXXXXXXXXXXXXXXXXXXX WITHINDLG Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} siputils [checks.c:123]: has_totag(): totag found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [loose.c:114]: find_first_route(): No Route headers found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [loose.c:961]: loose_route(): There is no Route HF Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: ERROR: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <script>: XXXXXXXXXXXXXXXXXXXXXXX WITHINDLG Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: ERROR: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <script>: XXXXXXXXXXXXXXXXXXXXXXX ACK Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:1043]: t_check_msg(): msg (0xb72fb410) id=26/18443 global id=25/18443 T start=0xffffffff Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:500]: t_lookup_request(): start searching: hash=21124, isACK=1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:458]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bK4825.29cbe80853cc3d43347f3c0b4b643e4c.0] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:682]: t_lookup_request(): no transaction found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:1113]: t_check_msg(): msg (0xb72fb410) id=26/18443 global id=26/18443 T end=(nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: ERROR: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <script>: XXXXXXXXXXXXXXXXXXXXXXX ignore Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:353]: receive_msg(): request-route executed in: 737 usec Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:712]: dlg_lookup(): ref dlg 0xb4934aec with 1 -> 3 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:714]: dlg_lookup(): dialog id=8415 found on entry 3438 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:957]: dlg_unref_helper(): unref op on 0xb4934aec with 1 from dlg_hash.c:975 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:961]: dlg_unref_helper(): unref dlg 0xb4934aec with 1 -> 2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN last message repeated 5 times Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/xavp.c:495]: xavp_destroy_list(): destroying xavp list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18443]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:457]: receive_msg(): cleaning up Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: <core> [core/udp_server.c:492]: udp_rcv_loop(): received on udp socket: (106/100/442) [[ACK sip:004112345@10.40.8.104:5060 SIP/2.0 0D 0A Via: SIP/2.0/UDP 10.40.6.188:60223;rport;branch=z9hG4bKP]] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: <core> [core/parser/msg_parser.c:610]: parse_msg(): SIP Request: Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: <core> [core/parser/msg_parser.c:612]: parse_msg(): method: <ACK> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: <core> [core/parser/msg_parser.c:614]: parse_msg(): uri: <sip:004112345@10.40.8.104:5060> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: <core> [core/parser/msg_parser.c:616]: parse_msg(): version: <SIP/2.0> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 235, <rport> = <n/a>; state=6 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bKPjvd1MSxMjv6dfOGdbAVxKz.iPtydNiEtQ>; state=16 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: <core> [core/parser/msg_parser.c:498]: parse_headers(): Via found, flags=2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: <core> [core/parser/msg_parser.c:500]: parse_headers(): this is the first via Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=as21517b15 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=29 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: <core> [core/parser/msg_parser.c:171]: get_hdr_field(): <To> [44]; uri=[sip:004112345@10.40.8.104] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: <core> [core/parser/msg_parser.c:174]: get_hdr_field(): to body [<sip:004112345@10.40.8.104>], to tag [as21517b15] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: <core> [core/parser/msg_parser.c:152]: get_hdr_field(): cseq <CSeq>: <27457> <ACK> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: <core> [core/receive.c:245]: receive_msg(): --- received sip message - request - call-id: [otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy] - cseq: [27457 ACK] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: <core> [core/parser/msg_parser.c:185]: get_hdr_field(): content_length=0 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: <core> [core/parser/msg_parser.c:89]: get_hdr_field(): found end of header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:295]: receive_msg(): preparing to run routing scripts... Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sl [sl_funcs.c:397]: sl_filter_ACK(): too late to be a local ACK! Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: <core> [core/udp_server.c:492]: udp_rcv_loop(): received on udp socket: (106/100/442) [[ACK sip:004112345@10.40.8.104:5060 SIP/2.0 0D 0A Via: SIP/2.0/UDP 10.40.6.188:60223;rport;branch=z9hG4bKP]] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=29 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: <core> [core/parser/msg_parser.c:610]: parse_msg(): SIP Request: Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: <core> [core/parser/msg_parser.c:612]: parse_msg(): method: <ACK> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:769]: internal_get_dlg(): ref dlg 0xb4934aec with 1 -> 3 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: <core> [core/parser/msg_parser.c:614]: parse_msg(): uri: <sip:004112345@10.40.8.104:5060> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: <core> [core/parser/msg_parser.c:616]: parse_msg(): version: <SIP/2.0> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 235, <rport> = <n/a>; state=6 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:772]: internal_get_dlg(): dialog callid='otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy' found on entry 3438, dir=1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bKPjvd1MSxMjv6dfOGdbAVxKz.iPtydNiEtQ>; state=16 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_profile.c:536]: set_current_dialog(): setting current dialog [3438:8415] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:1158]: next_state_dlg(): dialog 0xb4934aec changed from state 4 to state 4, due event 6 (ref 3) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: <core> [core/parser/msg_parser.c:498]: parse_headers(): Via found, flags=2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: <core> [core/parser/msg_parser.c:500]: parse_headers(): this is the first via Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=as21517b15 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_timer.c:110]: insert_dialog_timer_unsafe(): inserting 0xb4934b30 for 12143697 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_handlers.c:1480]: dlg_onroute(): sequential request successfully processed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=29 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: <core> [core/parser/msg_parser.c:171]: get_hdr_field(): <To> [44]; uri=[sip:004112345@10.40.8.104] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [record.c:925]: add_rr_param(): rr_param_buf=<;did=e6d.fd02> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:957]: dlg_unref_helper(): unref op on 0xb4934aec with 1 from dlg_hash.c:975 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: <core> [core/parser/msg_parser.c:174]: get_hdr_field(): to body [<sip:004112345@10.40.8.104>], to tag [as21517b15] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: <core> [core/parser/msg_parser.c:152]: get_hdr_field(): cseq <CSeq>: <27457> <ACK> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:961]: dlg_unref_helper(): unref dlg 0xb4934aec with 1 -> 2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: <core> [core/receive.c:245]: receive_msg(): --- received sip message - request - call-id: [otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy] - cseq: [27457 ACK] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: <core> [core/parser/msg_parser.c:185]: get_hdr_field(): content_length=0 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} pv [pv_core.c:1031]: pv_get_useragent(): no User-Agent header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: <core> [core/parser/msg_parser.c:89]: get_hdr_field(): found end of header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:295]: receive_msg(): preparing to run routing scripts... Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} maxfwd [mf_funcs.c:74]: is_maxfwd_present(): value = 70 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sl [sl_funcs.c:397]: sl_filter_ACK(): too late to be a local ACK! Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:247]: check_ruri_sip_version(): check_ruri_sip_version entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:270]: check_ruri_sip_version(): check_ruri_sip_version passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=29 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:277]: check_ruri_scheme(): check_ruri_scheme entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:769]: internal_get_dlg(): ref dlg 0xb4934aec with 1 -> 3 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:772]: internal_get_dlg(): dialog callid='otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy' found on entry 3438, dir=1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:297]: check_ruri_scheme(): check_ruri_scheme passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_profile.c:536]: set_current_dialog(): setting current dialog [3438:8415] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:1158]: next_state_dlg(): dialog 0xb4934aec changed from state 4 to state 4, due event 6 (ref 3) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:305]: check_required_headers(): check_required_headers entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:313]: check_required_headers(): check_required_headers passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_timer.c:110]: insert_dialog_timer_unsafe(): inserting 0xb4934b30 for 12143697 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_handlers.c:1480]: dlg_onroute(): sequential request successfully processed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:479]: check_cseq_method(): check_cseq_method entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [record.c:925]: add_rr_param(): rr_param_buf=<;did=e6d.fd02> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:957]: dlg_unref_helper(): unref op on 0xb4934aec with 1 from dlg_hash.c:975 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:512]: check_cseq_method(): check_cseq_method passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:961]: dlg_unref_helper(): unref dlg 0xb4934aec with 1 -> 2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} pv [pv_core.c:1031]: pv_get_useragent(): no User-Agent header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} maxfwd [mf_funcs.c:74]: is_maxfwd_present(): value = 70 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:521]: check_cseq_value(): check_cseq_value entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:247]: check_ruri_sip_version(): check_ruri_sip_version entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:549]: check_cseq_value(): check_cseq_value passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:270]: check_ruri_sip_version(): check_ruri_sip_version passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:558]: check_cl(): check_cl entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:277]: check_ruri_scheme(): check_ruri_scheme entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:297]: check_ruri_scheme(): check_ruri_scheme passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:583]: check_cl(): check_cl passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:305]: check_required_headers(): check_required_headers entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:595]: check_expires_value(): check_expires_value entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:313]: check_required_headers(): check_required_headers passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:632]: check_expires_value(): no expires header found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:479]: check_cseq_method(): check_cseq_method entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:728]: check_parse_uris(): check_parse_uris entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:512]: check_cseq_method(): check_cseq_method passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:732]: check_parse_uris(): parsing ruri Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:521]: check_cseq_value(): check_cseq_value entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:746]: check_parse_uris(): looking up From header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:549]: check_cseq_value(): check_cseq_value passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:786]: check_parse_uris(): parsing From URI Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:558]: check_cl(): check_cl entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:804]: check_parse_uris(): looking up To header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:583]: check_cl(): check_cl passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:826]: check_parse_uris(): check_parse_uris(): parsing To URI Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:595]: check_expires_value(): check_expires_value entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:871]: check_parse_uris(): check_parse_uris passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:632]: check_expires_value(): no expires header found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity_mod.c:254]: w_sanity_check(): sanity checks result: 1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:728]: check_parse_uris(): check_parse_uris entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: ERROR: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <script>: XXXXXXXXXXXXXXXXXXXXXXX WITHINDLG Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:732]: check_parse_uris(): parsing ruri Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} siputils [checks.c:123]: has_totag(): totag found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:746]: check_parse_uris(): looking up From header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [loose.c:91]: is_preloaded(): is_preloaded: No Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:786]: check_parse_uris(): parsing From URI Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:804]: check_parse_uris(): looking up To header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/socket_info.c:564]: grep_sock_info(): checking if host==us: 11==11 && [10.40.8.104] == [10.40.8.104] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:826]: check_parse_uris(): check_parse_uris(): parsing To URI Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:871]: check_parse_uris(): check_parse_uris passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/socket_info.c:567]: grep_sock_info(): checking if port 5070 (advertise 5070) matches port 5060 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [loose.c:677]: after_strict(): Next hop: 'sip:10.40.8.104:5070;lr;ftag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP;did=e6d.fd02' is loose router Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity_mod.c:254]: w_sanity_check(): sanity checks result: 1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: ERROR: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <script>: XXXXXXXXXXXXXXXXXXXXXXX WITHINDLG Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [loose.c:727]: after_strict(): The last route URI: 'sip:10.40.8.104:5070;lr;ftag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP;did=e6d.fd02' Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} siputils [checks.c:123]: has_totag(): totag found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: ERROR: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <script>: XXXXXXXXXXXXXXXXXXXXXXX Loose route Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [loose.c:91]: is_preloaded(): is_preloaded: No Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/socket_info.c:564]: grep_sock_info(): checking if host==us: 11==11 && [10.40.8.104] == [10.40.8.104] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:1346]: t_newtran(): msg (0xb72fb410) id=27/18445 global id=26/18445 T start=0xffffffff Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/socket_info.c:567]: grep_sock_info(): checking if port 5070 (advertise 5070) matches port 5060 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:500]: t_lookup_request(): start searching: hash=21124, isACK=1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [loose.c:677]: after_strict(): Next hop: 'sip:10.40.8.104:5070;lr;ftag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP;did=e6d.fd02' is loose router Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [loose.c:727]: after_strict(): The last route URI: 'sip:10.40.8.104:5070;lr;ftag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP;did=e6d.fd02' Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:458]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bKPjvd1MSxMjv6dfOGdbAVxKz.iPtydNiEtQ] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: ERROR: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <script>: XXXXXXXXXXXXXXXXXXXXXXX Loose route Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:682]: t_lookup_request(): no transaction found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:1346]: t_newtran(): msg (0xb72fb410) id=25/18444 global id=24/18444 T start=0xffffffff Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_funcs.c:287]: t_relay_to(): forwarding ACK statelessly Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:500]: t_lookup_request(): start searching: hash=21124, isACK=1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:458]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bKPjvd1MSxMjv6dfOGdbAVxKz.iPtydNiEtQ] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/dns_cache.c:3193]: dns_srv_sip_resolve(): (10.40.8.104, 0, 0), ip, ret=0 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/md5utils.c:67]: MD5StringArray(): MD5 calculated: 29cbe80853cc3d43347f3c0b4b643e4c Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/forward.c:557]: forward_request(): Sending: ACK sip:10.40.8.104:5070;lr;ftag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP;did=e6d.fd02 SIP/2.0^M Via: SIP/2.0/UDP 10.40.8.104:5070;branch=z9hG4bK4825.29cbe80853cc3d43347f3c0b4b643e4c.0^M Via: SIP/2.0/UDP 10.40.6.188:60223;received=10.40.6.188;rport=60223;branch=z9hG4bKPjvd1MSxMjv6dfOGdbAVxKz.iPtydNiEtQ^M Max-Forwards: 69^M From: <sip:proxydevice@10.40.8.104>;tag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP^M To: <sip:004112345@10.40.8.104>;tag=as21517b15^M Call-ID: otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy^M CSeq: 27457 ACK^M Content-Length: 0^M ^M . Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:682]: t_lookup_request(): no transaction found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/forward.c:559]: forward_request(): orig. len=442, new_len=517, proto=1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_funcs.c:287]: t_relay_to(): forwarding ACK statelessly Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/dns_cache.c:3193]: dns_srv_sip_resolve(): (10.40.8.104, 0, 0), ip, ret=0 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/md5utils.c:67]: MD5StringArray(): MD5 calculated: 29cbe80853cc3d43347f3c0b4b643e4c Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/udp_server.c:492]: udp_rcv_loop(): received on udp socket: (106/100/517) [[ACK sip:10.40.8.104:5070;lr;ftag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP;did=e6d.fd02 SIP/2.0 0D 0A Via: SIP/2.0]] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:353]: receive_msg(): request-route executed in: 2883 usec Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/forward.c:557]: forward_request(): Sending: ACK sip:10.40.8.104:5070;lr;ftag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP;did=e6d.fd02 SIP/2.0^M Via: SIP/2.0/UDP 10.40.8.104:5070;branch=z9hG4bK4825.29cbe80853cc3d43347f3c0b4b643e4c.0^M Via: SIP/2.0/UDP 10.40.6.188:60223;received=10.40.6.188;rport=60223;branch=z9hG4bKPjvd1MSxMjv6dfOGdbAVxKz.iPtydNiEtQ^M Max-Forwards: 69^M From: <sip:proxydevice@10.40.8.104>;tag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP^M To: <sip:004112345@10.40.8.104>;tag=as21517b15^M Call-ID: otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy^M CSeq: 27457 ACK^M Content-Length: 0^M ^M . Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/msg_parser.c:610]: parse_msg(): SIP Request: Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:712]: dlg_lookup(): ref dlg 0xb4934aec with 1 -> 3 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:714]: dlg_lookup(): dialog id=8415 found on entry 3438 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/msg_parser.c:612]: parse_msg(): method: <ACK> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/msg_parser.c:614]: parse_msg(): uri: <sip:10.40.8.104:5070;lr;ftag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP;did=e6d.fd02> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:957]: dlg_unref_helper(): unref op on 0xb4934aec with 1 from dlg_hash.c:975 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:961]: dlg_unref_helper(): unref dlg 0xb4934aec with 1 -> 2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/msg_parser.c:616]: parse_msg(): version: <SIP/2.0> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/forward.c:559]: forward_request(): orig. len=442, new_len=517, proto=1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK4825.29cbe80853cc3d43347f3c0b4b643e4c.0>; state=16 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:353]: receive_msg(): request-route executed in: 2527 usec Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:712]: dlg_lookup(): ref dlg 0xb4934aec with 1 -> 3 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/udp_server.c:492]: udp_rcv_loop(): received on udp socket: (106/100/517) [[ACK sip:10.40.8.104:5070;lr;ftag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP;did=e6d.fd02 SIP/2.0 0D 0A Via: SIP/2.0]] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/msg_parser.c:610]: parse_msg(): SIP Request: Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:714]: dlg_lookup(): dialog id=8415 found on entry 3438 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:957]: dlg_unref_helper(): unref op on 0xb4934aec with 1 from dlg_hash.c:975 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/msg_parser.c:612]: parse_msg(): method: <ACK> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/msg_parser.c:498]: parse_headers(): Via found, flags=2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:961]: dlg_unref_helper(): unref dlg 0xb4934aec with 1 -> 2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/msg_parser.c:500]: parse_headers(): this is the first via Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/msg_parser.c:614]: parse_msg(): uri: <sip:10.40.8.104:5070;lr;ftag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP;did=e6d.fd02> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 234, <received> = <10.40.6.188>; state=6 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 235, <rport> = <60223>; state=6 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bKPjvd1MSxMjv6dfOGdbAVxKz.iPtydNiEtQ>; state=16 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/xavp.c:495]: xavp_destroy_list(): destroying xavp list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18445]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:457]: receive_msg(): cleaning up Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/msg_parser.c:616]: parse_msg(): version: <SIP/2.0> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/msg_parser.c:498]: parse_headers(): Via found, flags=78 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK4825.29cbe80853cc3d43347f3c0b4b643e4c.0>; state=16 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/msg_parser.c:511]: parse_headers(): this is the second via Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=as21517b15 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/xavp.c:495]: xavp_destroy_list(): destroying xavp list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/msg_parser.c:498]: parse_headers(): Via found, flags=2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=29 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18444]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:457]: receive_msg(): cleaning up Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/msg_parser.c:500]: parse_headers(): this is the first via Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/msg_parser.c:171]: get_hdr_field(): <To> [44]; uri=[sip:004112345@10.40.8.104] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 234, <received> = <10.40.6.188>; state=6 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 235, <rport> = <60223>; state=6 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/msg_parser.c:174]: get_hdr_field(): to body [<sip:004112345@10.40.8.104>], to tag [as21517b15] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/msg_parser.c:152]: get_hdr_field(): cseq <CSeq>: <27457> <ACK> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bKPjvd1MSxMjv6dfOGdbAVxKz.iPtydNiEtQ>; state=16 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/receive.c:245]: receive_msg(): --- received sip message - request - call-id: [otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy] - cseq: [27457 ACK] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/msg_parser.c:185]: get_hdr_field(): content_length=0 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/msg_parser.c:498]: parse_headers(): Via found, flags=78 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: <core> [core/parser/msg_parser.c:89]: get_hdr_field(): found end of header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/msg_parser.c:511]: parse_headers(): this is the second via Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:295]: receive_msg(): preparing to run routing scripts... Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=as21517b15 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sl [sl_funcs.c:397]: sl_filter_ACK(): too late to be a local ACK! Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=29 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/msg_parser.c:171]: get_hdr_field(): <To> [44]; uri=[sip:004112345@10.40.8.104] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/msg_parser.c:174]: get_hdr_field(): to body [<sip:004112345@10.40.8.104>], to tag [as21517b15] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/msg_parser.c:152]: get_hdr_field(): cseq <CSeq>: <27457> <ACK> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=29 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/receive.c:245]: receive_msg(): --- received sip message - request - call-id: [otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy] - cseq: [27457 ACK] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/msg_parser.c:185]: get_hdr_field(): content_length=0 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:769]: internal_get_dlg(): ref dlg 0xb4934aec with 1 -> 3 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: <core> [core/parser/msg_parser.c:89]: get_hdr_field(): found end of header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:295]: receive_msg(): preparing to run routing scripts... Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:772]: internal_get_dlg(): dialog callid='otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy' found on entry 3438, dir=1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sl [sl_funcs.c:397]: sl_filter_ACK(): too late to be a local ACK! Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_profile.c:536]: set_current_dialog(): setting current dialog [3438:8415] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:1158]: next_state_dlg(): dialog 0xb4934aec changed from state 4 to state 4, due event 6 (ref 3) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=1DoN4DknAgMG5nSNVGynmZgOtY9Ap6nP Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_timer.c:110]: insert_dialog_timer_unsafe(): inserting 0xb4934b30 for 12143697 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=29 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_handlers.c:1480]: dlg_onroute(): sequential request successfully processed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:769]: internal_get_dlg(): ref dlg 0xb4934aec with 1 -> 4 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:772]: internal_get_dlg(): dialog callid='otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy' found on entry 3438, dir=1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [record.c:925]: add_rr_param(): rr_param_buf=<;did=e6d.fd02> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:957]: dlg_unref_helper(): unref op on 0xb4934aec with 1 from dlg_hash.c:975 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:961]: dlg_unref_helper(): unref dlg 0xb4934aec with 1 -> 3 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_profile.c:536]: set_current_dialog(): setting current dialog [3438:8415] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} pv [pv_core.c:1031]: pv_get_useragent(): no User-Agent header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} maxfwd [mf_funcs.c:74]: is_maxfwd_present(): value = 69 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:1158]: next_state_dlg(): dialog 0xb4934aec changed from state 4 to state 4, due event 6 (ref 3) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:247]: check_ruri_sip_version(): check_ruri_sip_version entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_timer.c:110]: insert_dialog_timer_unsafe(): inserting 0xb4934b30 for 12143697 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:270]: check_ruri_sip_version(): check_ruri_sip_version passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_handlers.c:1480]: dlg_onroute(): sequential request successfully processed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [record.c:925]: add_rr_param(): rr_param_buf=<;did=e6d.fd02> Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:277]: check_ruri_scheme(): check_ruri_scheme entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:957]: dlg_unref_helper(): unref op on 0xb4934aec with 1 from dlg_hash.c:975 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:297]: check_ruri_scheme(): check_ruri_scheme passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:961]: dlg_unref_helper(): unref dlg 0xb4934aec with 1 -> 2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:305]: check_required_headers(): check_required_headers entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:313]: check_required_headers(): check_required_headers passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} pv [pv_core.c:1031]: pv_get_useragent(): no User-Agent header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:479]: check_cseq_method(): check_cseq_method entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:512]: check_cseq_method(): check_cseq_method passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} maxfwd [mf_funcs.c:74]: is_maxfwd_present(): value = 69 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:521]: check_cseq_value(): check_cseq_value entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:549]: check_cseq_value(): check_cseq_value passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:247]: check_ruri_sip_version(): check_ruri_sip_version entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:558]: check_cl(): check_cl entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:583]: check_cl(): check_cl passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:270]: check_ruri_sip_version(): check_ruri_sip_version passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:595]: check_expires_value(): check_expires_value entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:277]: check_ruri_scheme(): check_ruri_scheme entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:632]: check_expires_value(): no expires header found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:297]: check_ruri_scheme(): check_ruri_scheme passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:305]: check_required_headers(): check_required_headers entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:728]: check_parse_uris(): check_parse_uris entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:732]: check_parse_uris(): parsing ruri Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:313]: check_required_headers(): check_required_headers passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:479]: check_cseq_method(): check_cseq_method entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:746]: check_parse_uris(): looking up From header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:786]: check_parse_uris(): parsing From URI Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:512]: check_cseq_method(): check_cseq_method passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:521]: check_cseq_value(): check_cseq_value entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:804]: check_parse_uris(): looking up To header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:826]: check_parse_uris(): check_parse_uris(): parsing To URI Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:549]: check_cseq_value(): check_cseq_value passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:558]: check_cl(): check_cl entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:871]: check_parse_uris(): check_parse_uris passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:583]: check_cl(): check_cl passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:595]: check_expires_value(): check_expires_value entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity_mod.c:254]: w_sanity_check(): sanity checks result: 1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:632]: check_expires_value(): no expires header found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: ERROR: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <script>: XXXXXXXXXXXXXXXXXXXXXXX WITHINDLG Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:728]: check_parse_uris(): check_parse_uris entered Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} siputils [checks.c:123]: has_totag(): totag found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [loose.c:114]: find_first_route(): No Route headers found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [loose.c:961]: loose_route(): There is no Route HF Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:732]: check_parse_uris(): parsing ruri Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:746]: check_parse_uris(): looking up From header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: ERROR: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <script>: XXXXXXXXXXXXXXXXXXXXXXX WITHINDLG Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: ERROR: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <script>: XXXXXXXXXXXXXXXXXXXXXXX ACK Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:1043]: t_check_msg(): msg (0xb72fb410) id=24/18448 global id=23/18448 T start=0xffffffff Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:500]: t_lookup_request(): start searching: hash=21124, isACK=1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:786]: check_parse_uris(): parsing From URI Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:458]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bK4825.29cbe80853cc3d43347f3c0b4b643e4c.0] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:804]: check_parse_uris(): looking up To header Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:826]: check_parse_uris(): check_parse_uris(): parsing To URI Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:682]: t_lookup_request(): no transaction found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:1113]: t_check_msg(): msg (0xb72fb410) id=24/18448 global id=24/18448 T end=(nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: ERROR: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <script>: XXXXXXXXXXXXXXXXXXXXXXX ignore Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:353]: receive_msg(): request-route executed in: 1941 usec Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity.c:871]: check_parse_uris(): check_parse_uris passed Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:712]: dlg_lookup(): ref dlg 0xb4934aec with 1 -> 3 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} sanity [sanity_mod.c:254]: w_sanity_check(): sanity checks result: 1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:714]: dlg_lookup(): dialog id=8415 found on entry 3438 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: ERROR: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <script>: XXXXXXXXXXXXXXXXXXXXXXX WITHINDLG Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} siputils [checks.c:123]: has_totag(): totag found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [loose.c:114]: find_first_route(): No Route headers found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} rr [loose.c:961]: loose_route(): There is no Route HF Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:957]: dlg_unref_helper(): unref op on 0xb4934aec with 1 from dlg_hash.c:975 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:961]: dlg_unref_helper(): unref dlg 0xb4934aec with 1 -> 2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: ERROR: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <script>: XXXXXXXXXXXXXXXXXXXXXXX WITHINDLG Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: ERROR: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <script>: XXXXXXXXXXXXXXXXXXXXXXX ACK Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:1043]: t_check_msg(): msg (0xb72fb410) id=27/18446 global id=26/18446 T start=0xffffffff Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:500]: t_lookup_request(): start searching: hash=21124, isACK=1 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:458]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bK4825.29cbe80853cc3d43347f3c0b4b643e4c.0] Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:682]: t_lookup_request(): no transaction found Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} tm [t_lookup.c:1113]: t_check_msg(): msg (0xb72fb410) id=27/18446 global id=27/18446 T end=(nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: ERROR: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <script>: XXXXXXXXXXXXXXXXXXXXXXX ignore Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:353]: receive_msg(): request-route executed in: 2123 usec Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:712]: dlg_lookup(): ref dlg 0xb4934aec with 1 -> 3 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/xavp.c:495]: xavp_destroy_list(): destroying xavp list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18448]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:457]: receive_msg(): cleaning up Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:714]: dlg_lookup(): dialog id=8415 found on entry 3438 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:957]: dlg_unref_helper(): unref op on 0xb4934aec with 1 from dlg_hash.c:975 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} dialog [dlg_hash.c:961]: dlg_unref_helper(): unref dlg 0xb4934aec with 1 -> 2 Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/usr_avp.c:636]: destroy_avp_list(): destroying list (nil) Mar 12 09:21:43 oAN last message repeated 5 times Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/xavp.c:495]: xavp_destroy_list(): destroying xavp list (nil) Mar 12 09:21:43 oAN /usr/sbin/kamailio[18446]: DEBUG: {1 27457 ACK otoEsJ246gIFd.4F3Z6nE7PwA9XsgKCy} <core> [core/receive.c:457]: receive_msg(): cleaning up Mar 12 09:21:43 oAN /usr/sbin/kamailio[18449]: DEBUG: <core> [core/udp_server.c:492]: udp_rcv_loop(): received on udp socket: (106/100/1091) [[SIP/2.0 200 OK 0D 0A Via: SIP/2.0/UDP 10.40.8.104:5070;branch=z9hG4bK4825.fc814778ec04597ae4759a9771bfef0]]

2 1

Replicate REGISTER and save original received value
by Daniel W. Graham 12 Mar '19

12 Mar '19

When forwarding / replicating a REGISTER, is it possible (without using DMQ) for the receiving host to save the contact with the original received parameter? REGISTER > server 1 (received set) > forward > server 2 (received not set) add_rcv_param will set received to server 1 IP, but I'm looking for the original parameter as set on SERVER 1. -dan

3 12

Re: [SR-Users] ACK not forwarding to Asterisk
by Schneuwly Mathias RUAG 12 Mar '19

12 Mar '19

Dear Kamailio mailing list I've a problem with a simple Kamailio-Asterisk setup. I tried to find a solution and found several posts, but was not able to fix my problem! I'm using the following setup: - SIP device registered to Kamailio (IP 10.40.6.188) - Kamailio (port 5070) and Asterisk (port 5060) on the same host (IP 10.40.8.104) - I tried to forward calls from Kamailio to Asterisk with with standard PSTN call routing and dispatcher module, but the result was the same - Asterisk has a trunk to Kamailio - SIP device registered to Asterisk (IP 10.40.6.214) Calls from the Asterisk phone towards the Kamailio phone work without any issue. Calls from the Kamailio phone towards the Asterisk phone are successfully established and the voice works in both directions. The problem here is, that the Kamailio phone sends an ACK upon 200 OK, but the ACK is not forwarded to Asterisk. After 6 seconds, the call is terminated. If I remove record_route() or add a second IP to the same interface for Asterisk (10.40.8.106), then the call signaling works without any issue. Does anyone have an idea what I'm doing wrong here? I'm using more or less a standard Kamailio config file without rtpproxy. Please let me know if I shall post the full config or just some relevant snippets. Best regards Mathias Following are two snippets of the relevant ACK. The first shows the situation where the ACK was not forwarded to Asterisk and the second with a different IP for Asterisk works. No. Time Source Destination Protocol Length Info 752 17.269019 10.40.8.104 10.40.8.104 SIP/SDP 1135 Status: 200 OK | Frame 752: 1135 bytes on wire (9080 bits), 1135 bytes captured (9080 bits) Linux cooked capture Internet Protocol Version 4, Src: 10.40.8.104, Dst: 10.40.8.104 User Datagram Protocol, Src Port: 5060, Dst Port: 5070 Session Initiation Protocol (200) Status-Line: SIP/2.0 200 OK Status-Code: 200 [Resent Packet: False] [Request Frame: 304] [Response Time (ms): 2093] Message Header Via: SIP/2.0/UDP 10.40.8.104:5070;branch=z9hG4bKda4f.48918e0ef9372ba1a38655eb93742e46.0;received=10.40.8.104 Via: SIP/2.0/UDP 10.40.6.188:56960;received=10.40.6.188;rport=56960;branch=z9hG4bKPjVtFCvs26liH-aJoGn8CaLg4kWqml5LH. Record-Route: <sip:10.40.8.104:5070;lr;ftag=NCP2N5E7OZuppblpkCCNZziEmpiTRsQC;did=17a.4f61> From: <sip:proxydevice@10.40.8.104>;tag=NCP2N5E7OZuppblpkCCNZziEmpiTRsQC To: <sip:004112345@10.40.8.104>;tag=as5e5c287c Call-ID: a6T0GAwBL69m5gsc215EgXi61Oorwxik CSeq: 10909 INVITE Server: Asterisk PBX 12.3.2 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Session-Expires: 1800;refresher=uas Contact: <sip:004112345@10.40.8.104:5060> Content-Type: application/sdp Require: timer Content-Length: 271 Message Body No. Time Source Destination Protocol Length Info 764 17.270668 10.40.8.104 10.40.6.188 SIP/SDP 1025 Status: 200 OK | Frame 764: 1025 bytes on wire (8200 bits), 1025 bytes captured (8200 bits) Linux cooked capture Internet Protocol Version 4, Src: 10.40.8.104, Dst: 10.40.6.188 User Datagram Protocol, Src Port: 5070, Dst Port: 56960 Session Initiation Protocol (200) Status-Line: SIP/2.0 200 OK Status-Code: 200 [Resent Packet: False] [Request Frame: 259] [Response Time (ms): 2115] Message Header Via: SIP/2.0/UDP 10.40.6.188:56960;received=10.40.6.188;rport=56960;branch=z9hG4bKPjVtFCvs26liH-aJoGn8CaLg4kWqml5LH. Record-Route: <sip:10.40.8.104:5070;lr;ftag=NCP2N5E7OZuppblpkCCNZziEmpiTRsQC;did=17a.4f61> From: <sip:proxydevice@10.40.8.104>;tag=NCP2N5E7OZuppblpkCCNZziEmpiTRsQC To: <sip:004112345@10.40.8.104>;tag=as5e5c287c Call-ID: a6T0GAwBL69m5gsc215EgXi61Oorwxik CSeq: 10909 INVITE Server: Asterisk PBX 12.3.2 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Session-Expires: 1800;refresher=uas Contact: <sip:004112345@10.40.8.104:5060> Content-Type: application/sdp Require: timer Content-Length: 271 Message Body No. Time Source Destination Protocol Length Info 786 17.402987 10.40.6.188 10.40.8.104 SIP 486 Request: ACK sip:004112345@10.40.8.104:5060 | Frame 786: 486 bytes on wire (3888 bits), 486 bytes captured (3888 bits) Linux cooked capture Internet Protocol Version 4, Src: 10.40.6.188, Dst: 10.40.8.104 User Datagram Protocol, Src Port: 56960, Dst Port: 5070 Session Initiation Protocol (ACK) Request-Line: ACK sip:004112345@10.40.8.104:5060 SIP/2.0 Method: ACK Request-URI: sip:004112345@10.40.8.104:5060 [Resent Packet: False] [Request Frame: 259] [Response Time (ms): 2247] Message Header Via: SIP/2.0/UDP 10.40.6.188:56960;rport;branch=z9hG4bKPjM2GQWjVep2XhpLxJD-cxNh75Qtep-sN3 Max-Forwards: 70 From: <sip:proxydevice@10.40.8.104>;tag=NCP2N5E7OZuppblpkCCNZziEmpiTRsQC To: <sip:004112345@10.40.8.104>;tag=as5e5c287c Call-ID: a6T0GAwBL69m5gsc215EgXi61Oorwxik CSeq: 10909 ACK Route: <sip:10.40.8.104:5070;lr;ftag=NCP2N5E7OZuppblpkCCNZziEmpiTRsQC;did=17a.4f61> Content-Length: 0 No. Time Source Destination Protocol Length Info 787 17.404480 10.40.8.104 10.40.8.104 SIP 561 Request: ACK sip:10.40.8.104:5070;lr;ftag=NCP2N5E7OZuppblpkCCNZziEmpiTRsQC;did=17a.4f61 | Frame 787: 561 bytes on wire (4488 bits), 561 bytes captured (4488 bits) Linux cooked capture Internet Protocol Version 4, Src: 10.40.8.104, Dst: 10.40.8.104 User Datagram Protocol, Src Port: 5070, Dst Port: 5070 Session Initiation Protocol (ACK) Request-Line: ACK sip:10.40.8.104:5070;lr;ftag=NCP2N5E7OZuppblpkCCNZziEmpiTRsQC;did=17a.4f61 SIP/2.0 Method: ACK Request-URI: sip:10.40.8.104:5070;lr;ftag=NCP2N5E7OZuppblpkCCNZziEmpiTRsQC;did=17a.4f61 [Resent Packet: False] Message Header Via: SIP/2.0/UDP 10.40.8.104:5070;branch=z9hG4bKda4f.f914ac9def098ece9a50d53389574f85.0 Via: SIP/2.0/UDP 10.40.6.188:56960;received=10.40.6.188;rport=56960;branch=z9hG4bKPjM2GQWjVep2XhpLxJD-cxNh75Qtep-sN3 Max-Forwards: 69 From: <sip:proxydevice@10.40.8.104>;tag=NCP2N5E7OZuppblpkCCNZziEmpiTRsQC To: <sip:004112345@10.40.8.104>;tag=as5e5c287c Call-ID: a6T0GAwBL69m5gsc215EgXi61Oorwxik CSeq: 10909 ACK Content-Length: 0 In this case I used a second IP on the same interface for Asterisk and this call works without any issue: No. Time Source Destination Protocol Length Info 939 8.849431 10.40.8.106 10.40.6.214 SIP 473 Request: ACK sip:004112345@10.40.6.214:49316;ob | Frame 939: 473 bytes on wire (3784 bits), 473 bytes captured (3784 bits) Linux cooked capture Internet Protocol Version 4, Src: 10.40.8.106, Dst: 10.40.6.214 User Datagram Protocol, Src Port: 5060, Dst Port: 49316 Session Initiation Protocol (ACK) No. Time Source Destination Protocol Length Info 946 8.850293 10.40.8.106 10.40.8.104 SIP/SDP 1136 Status: 200 OK | Frame 946: 1136 bytes on wire (9088 bits), 1136 bytes captured (9088 bits) Linux cooked capture Internet Protocol Version 4, Src: 10.40.8.106, Dst: 10.40.8.104 User Datagram Protocol, Src Port: 5060, Dst Port: 5070 Session Initiation Protocol (200) No. Time Source Destination Protocol Length Info 956 8.851703 10.40.8.104 10.40.6.188 SIP/SDP 1026 Status: 200 OK | Frame 956: 1026 bytes on wire (8208 bits), 1026 bytes captured (8208 bits) Linux cooked capture Internet Protocol Version 4, Src: 10.40.8.104, Dst: 10.40.6.188 User Datagram Protocol, Src Port: 5070, Dst Port: 60223 Session Initiation Protocol (200) No. Time Source Destination Protocol Length Info 989 9.095859 10.40.6.188 10.40.8.104 SIP 485 Request: ACK sip:004112345@10.40.8.106:5060 | Frame 989: 485 bytes on wire (3880 bits), 485 bytes captured (3880 bits) Linux cooked capture Internet Protocol Version 4, Src: 10.40.6.188, Dst: 10.40.8.104 User Datagram Protocol, Src Port: 60223, Dst Port: 5070 Session Initiation Protocol (ACK) No. Time Source Destination Protocol Length Info 991 9.097228 10.40.8.104 10.40.8.106 SIP 516 Request: ACK sip:004112345@10.40.8.106:5060 | Frame 991: 516 bytes on wire (4128 bits), 516 bytes captured (4128 bits) Linux cooked capture Internet Protocol Version 4, Src: 10.40.8.104, Dst: 10.40.8.106 User Datagram Protocol, Src Port: 5070, Dst Port: 5060 Session Initiation Protocol (ACK)

3 2

Planning next IRC devel meeting
by Daniel-Constantin Mierla 11 Mar '19

11 Mar '19

Hello, wondering if we we should do a new IRC devel meeting in the near future to sync on development plans. One of the decisions we should take is whether we should target to release the new major version (5.3) before the summer holidays or we leave it for the autumn. If many wants to do it, then a first proposal for a date would be: March 07, 2019, at 15:00 UTC (16:00 Berlin time). As usual, I created a wiki page to track the availability and the topics that should be approched: * https://www.kamailio.org/wiki/devel/irc-meetings/2019a Feel free to add yourself there, propose topics, etc... Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

3 6

MSRP module. How to generate a REPORT message
by Nacho Garcia 11 Mar '19

11 Mar '19

Hi all, I'm just trying to use Kamailio as an MSRP relay with MSRP module https://www.kamailio.org/docs/modules/5.1.x/modules/msrp.html. I'm trying to set up https://tools.ietf.org/html/rfc4976#section-6.4.1 and https://tools.ietf.org/html/rfc4976#section-6.4.3 behavior. I was able to read the "Failure-Report" header value and using it accordingly with: ``` is_present_hf("Failure-Report") && $hdr(Failure-Report) == "Yes" ``` But the problem I have is, how can I generate a new REPORT message to be sent to the origin? I just can do `msrp_relay` or `msrp_reply`. Thanks for your help! Nacho García Segovia

2 1

Kamailio v5.2.2 Released
by Daniel-Constantin Mierla 11 Mar '19

11 Mar '19

Hello, Kamailio SIP Server v5.2.2 stable release is out. This is a maintenance release of the latest stable branch, 5.2, that includes fixes since the release of v5.2.1. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.2.x. Deployments running previous v5.2.x versions are strongly recommended to be upgraded to v5.2.2. For more details about version 5.2.2 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2019/03/kamailio-v5-2-2-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Looking forward to meeting many of you in Berlin, at Kamailio World Conference 2019! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

1 0

ICSCF and SCSCF Problem
by Rust Cohle 11 Mar '19

11 Mar '19

Hello, I am trying to run all CSCF nodes and I managed to run the PCSCF without any issues with the following: kamailio -f /etc/kamailio/pcscf/kamailio.cfg -Ee When I try to do the same with I-CSCF and S-CSCF, I get lots of errors and could not figure out the reason. I included the terminal logs and also attached the cfg files for both SCSCF and ICSCF. For S-CSCF the terminal log is the following: kamailio -f /etc/kamailio/scscf/kamailio.cfg -Ee loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules 0(6591) ERROR: <core> [sr_module.c:576]: load_module(): could not open module </usr/lib/x86_64-linux-gnu/kamailio/modules/cdp.so>: /usr/lib/x86_64-linux-gnu/kamailio/modules/cdp.so: undefined symbol: log_dp_config 0(6591) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/scscf/kamailio.cfg, line 139, column 12-19: failed to load module 0(6591) ERROR: <core> [sr_module.c:576]: load_module(): could not open module </usr/lib/x86_64-linux-gnu/kamailio/modules/ims_usrloc_scscf.so>: /usr/lib/x86_64-linux-gnu/kamailio/modules/ims_usrloc_scscf.so: undefined symbol: bin_alloc 0(6591) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/scscf/kamailio.cfg, line 142, column 12-32: failed to load module 0(6591) ERROR: <core> [sr_module.c:576]: load_module(): could not open module </usr/lib/x86_64-linux-gnu/kamailio/modules/ims_registrar_scscf.so>: /usr/lib/x86_64-linux-gnu/kamailio/modules/ims_registrar_scscf.so: undefined symbol: cxdx_get_charging_info 0(6591) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/scscf/kamailio.cfg, line 143, column 12-35: failed to load module 0(6591) ERROR: <core> [sr_module.c:576]: load_module(): could not open module </usr/lib/x86_64-linux-gnu/kamailio/modules/ims_auth.so>: /usr/lib/x86_64-linux-gnu/kamailio/modules/ims_auth.so: undefined symbol: cxdx_add_user_name 0(6591) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/scscf/kamailio.cfg, line 144, column 12-24: failed to load module 0(6591) ERROR: <core> [sr_module.c:576]: load_module(): could not open module </usr/lib/x86_64-linux-gnu/kamailio/modules/ims_isc.so>: /usr/lib/x86_64-linux-gnu/kamailio/modules/ims_isc.so: undefined symbol: isc_mark_drop_route 0(6591) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/scscf/kamailio.cfg, line 145, column 12-23: failed to load module 0(6591) ERROR: <core> [sr_module.c:576]: load_module(): could not open module </usr/lib/x86_64-linux-gnu/kamailio/modules/ims_charging.so>: /usr/lib/x86_64-linux-gnu/kamailio/modules/ims_charging.so: undefined symbol: destroy_ro_session 0(6591) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/scscf/kamailio.cfg, line 148, column 12-28: failed to load module 0(6591) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/scscf/kamailio.cfg, line 162, column 46-50: syntax error 0(6591) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/scscf/kamailio.cfg, line 162, column 46-50: Invalid arguments 0(6591) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/scscf/kamailio.cfg, line 162, column 51: ERROR: bad config file (9 errors) 0(6591) WARNING: <core> [ppcfg.c:220]: pp_ifdef_level_check(): different number of preprocessor directives: N(#!IF[N]DEF) - N(#!ENDIF) = 1 0(6591) WARNING: <core> [mem/q_malloc.c:429]: qm_free(): WARNING:qm_free: free(0) called from cdp_avp: mod.c: cdp_avp_destroy(225) 0(6591) INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized For I-CSCF the terminal log is the following: kamailio -f /etc/kamailio/icscf/kamailio.cfg -Ee loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules 0(7707) ERROR: <core> [sr_module.c:576]: load_module(): could not open module </usr/lib/x86_64-linux-gnu/kamailio/modules/cdp.so>: /usr/lib/x86_64-linux-gnu/kamailio/modules/cdp.so: undefined symbol: log_dp_config 0(7707) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 113, column 12-19: failed to load module 0(7707) ERROR: <core> [sr_module.c:576]: load_module(): could not open module </usr/lib/x86_64-linux-gnu/kamailio/modules/ims_icscf.so>: /usr/lib/x86_64-linux-gnu/kamailio/modules/ims_icscf.so: undefined symbol: cxdx_add_user_name 0(7707) : <core> [cfg.y:3432]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 117, column 12-25: failed to load module 0(7707) WARNING: tls [tls_mod.c:265]: mod_register(): tls support is disabled (set enable_tls=1 in the config to enable it) 0(7707) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <cdp> found 0(7707) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 154, column 61: Can't set module parameter 0(7707) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <ims_icscf> found 0(7707) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 161, column 51: Can't set module parameter 0(7707) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <ims_icscf> found 0(7707) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 165, column 53: Can't set module parameter 0(7707) ERROR: <core> [modparam.c:150]: set_mod_param_regex(): No module matching <ims_icscf> found 0(7707) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 170, column 51: Can't set module parameter 0(7707) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command I_scscf_select (params 1) 0(7707) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 325, column 24: unknown command, missing loadmodule? 0(7707) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command I_scscf_drop (params 0) 0(7707) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 337, column 16: unknown command, missing loadmodule? 0(7707) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command I_perform_user_authorization_request (params 2) 0(7707) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 339, column 73: unknown command, missing loadmodule? 0(7707) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command I_scscf_select (params 1) 0(7707) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 350, column 43: unknown command, missing loadmodule? 0(7707) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command I_scscf_drop (params 0) 0(7707) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 358, column 42: unknown command, missing loadmodule? 0(7707) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command I_scscf_drop (params 0) 0(7707) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 386, column 17: unknown command, missing loadmodule? 0(7707) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command I_scscf_select (params 1) 0(7707) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 400, column 25: unknown command, missing loadmodule? 0(7707) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command I_scscf_drop (params 0) 0(7707) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 415, column 17: unknown command, missing loadmodule? 0(7707) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command I_perform_location_information_request (params 2) 0(7707) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 428, column 57: unknown command, missing loadmodule? 0(7707) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command I_scscf_select (params 1) 0(7707) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 433, column 25: unknown command, missing loadmodule? 0(7707) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command I_scscf_drop (params 0) 0(7707) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 444, column 17: unknown command, missing loadmodule? 0(7707) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command I_scscf_drop (params 0) 0(7707) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 463, column 16: unknown command, missing loadmodule? 0(7707) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command I_scscf_select (params 1) 0(7707) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 476, column 25: unknown command, missing loadmodule? 0(7707) ERROR: <core> [cfg.y:3295]: yyparse(): cfg. parser: failed to find command I_scscf_drop (params 0) 0(7707) : <core> [cfg.y:3435]: yyerror_at(): parse error in config file /etc/kamailio/icscf/kamailio.cfg, line 490, column 16: unknown command, missing loadmodule? ERROR: bad config file (20 errors) 0(7707) WARNING: <core> [mem/q_malloc.c:429]: qm_free(): WARNING:qm_free: free(0) called from cdp_avp: mod.c: cdp_avp_destroy(225) 0(7707) INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Thank you

2 1

Releasing Kamailio v5.2.2
by Anthony Joseph Messina 11 Mar '19

11 Mar '19

Daniel would it be possible to backport the rtpengine start/stop forwarding and play/stop media features into 5.2.2? I realize they are not technically "fixes"--not sure how obtrusive these changes would be. Either way, thank you. -A -- Anthony - https://messinet.com F9B6 560E 68EA 037D 8C3D D1C9 FF31 3BDB D9D8 99B6

2 2

Releasing Kamailio v5.2.2
by Daniel-Constantin Mierla 11 Mar '19

11 Mar '19

Hello, I am considering to release a new version from branch 5.2, respectively v5.2.2, on next Monday, March 11. As usual, check if any fixes done on master for issues you reported were backported to 5.2 already or not (I just pushed a bunch of backports earlier today). Also, if you are aware of issues not reported to the bug tracker, register them to get a chance to review and eventually fix. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

3 7

Fwd: Re: [x3d-public] x3d-public Digest, Vol 120, Issue 34
by Valentin Christoph 09 Mar '19

09 Mar '19

Fyi. Sorry for crossposting. P.S.: Today I deleted the "kamailio" clone from my github account http://github.com/christoph-v, because that account is now solely intended for private use (SP-ARK, PS-ARK). I created another account for professional purposes: http://github.com/christoph-v-kapsch Gesendet: Freitag, 08. März 2019 um 16: Von meinem Samsung Galaxy Smartphone gesendet. -------- Ursprüngliche Nachricht -------- Von: Christoph Valentin <christoph.valentin(a)gmx.at> Datum: 09.03.19 01:33 (GMT+01:00) An: Valentin Christoph <Christoph.Valentin(a)kapsch.net> Betreff: Fw: Re: [x3d-public] x3d-public Digest, Vol 120, Issue 34 F.y.i...... -- Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet. Am 08.03.19, 22:49, Christoph Valentin <christoph.valentin(a)gmx.at> schrieb: Hi Andreas, Still some neurons firing, so I send another update. Please feel free to break the "event cascade", when it starts to become boring :-) Everything else inline. Have a nice weekend Christoph P.S.: Today I deleted the "kamailio" clone from my github account http://github.com/christoph-v, because that account is now solely intended for private use (SP-ARK, PS-ARK). I created another account for professional purposes: http://github.com/christoph-v-kapsch Gesendet: Freitag, 08. März 2019 um 16:07 Uhr Von: "Andreas Plesch" <andreasplesch(a)gmail.com> An: "X3D Graphics public mailing list" <x3d-public(a)web3d.org> Betreff: Re: [x3d-public] x3d-public Digest, Vol 120, Issue 34 Thanks. I looked at the network sensor, and BS Collaborate nodes. I think the idea is to explicitly forward all events which need sharing to the server which then distributes those to connected clients. This leaves the definition of the shared state to the scene, and therefore requires careful design and code for MU. Perhaps there is a way that the browser can better assist with making a scene MU capable. What is the complete state a client needs when it is admitted to a shared scene ? Since most fields of most nodes accept input, and can therefore potentially change, complete state probably means just the value of all fields of all root nodes which means all nodes. The complete state may only need to be transferred when a client joins. Plus the offsets of avatars from Viewpoints. And the clock. Perhaps other values. [Christoph:] I think, what you are considering here is the tradeoff between "MU is done completely by the browser" and "MU is done completely by the author". Let's imagine the Web3D Consortium decided "MU was up to the author, everything should be done by EAI/SAI". Then every author had to decide, which nodes of his scene needed synchronization and he had free choice of the network protocol and of the server he would use. His efforts were the maximum, on the other hand his freedom were maximum, too. The opposite extreme would be that the browser vendor did all the MU inherently within the X3D nodes. The efforts of the author to create MU scenes from SU scenes would be zero, but his freedom would be zero, too (given each browser implemented his own MU strategy). So the Network Sensor is the ABSOLUTE MINIMUM, which MUST be standardized (INCLUDING a standard for the network protocol), in order to keep independence from the browser vendor and from the server vendor. I'm with you, when you doubt the Network Sensor would be enough. I am with you, when you insist some additional nodes MUST be standardized to keep the efforts of the authors small. The Network Sensor is not enough (I think I already said that here). If you are interested, I can introduce you to the SMUOS/C3P idea, which I developed throughout my hobby project. Would be a loss of ten years, if everybody had to repeat those experiences. And I guess, there are some projects and products (people) around here, who can help, too, much better than I can do. I was thinking about avatar initiated event cascades since the state of everything else should be deterministic and only depend on time. These other things should update themselves. There are exceptions such as scripts which generate random values. Avatar initiated event cascades generally start with environment sensors. Not sure if there are other ways. The idea would be to just have to transmit this event cascade to other clients which then can replay it to update their scene instances. [Christoph:] I think it will not be necessary to transmit event cascades, only single events and states need to be networked I also was reading some of the github open-dis documentation. Interesting background, and pretty accurate discussion on coordinate systems. It may be possible to set up somewhere a very simple distributed simulation to join and test clients with. [Christoph:] I do not want to comment on HLA/DIS here. Single browser MU: I think an additional touchedByUser field would be required but perhaps there is a way to generalize tracking of Users. [Christoph:] Probably. Each problem can be solved, if you want. Some solutions are beautiful, others are ugly. Cheers, -Andreas Date: Thu, 7 Mar 2019 18:11:15 +0100 From: "Christoph Valentin" <christoph.valentin(a)gmx.at<mailto:christoph.valentin@gmx.at>> To: "x3d-publicweb3d.org<http://x3d-publicweb3d.org>" <x3d-public(a)web3d.org<mailto:x3d-public@web3d.org>> Subject: Re: [x3d-public] Multiplayer strategies Hi Andreas, Please find another 2c inline :-) All the best Christoph ? ? Gesendet:?Donnerstag, 07. M?rz 2019 um 14:02 Uhr Von:?"Andreas Plesch" <andreasplesch(a)gmail.com<mailto:andreasplesch@gmail.com>> An:?"X3D Graphics public mailing list" <x3d-public(a)web3d.org<mailto:x3d-public@web3d.org>> Betreff:?Re: [x3d-public] Multiplayer strategies Hi Christoph, ? I admit that it is somewhat uncomfortable to think about single browser MU requirements but exploring this could be a fertile exercise as it seems orthogonal to sharing by multiple scene instances. [Christoph:] Agree. Maybe I am just prejudiced, because I started with my project from the MU example on Bitmanagement's Homepage (is it still there?), where they used the "sessionId"(SFInt32) to identify the users and their avatars. Now, when we think about single browser MU requirements, then the users should rather be identified by "sessionId + userId" (where userId would be a local identifier of a user of the local scene instance). Next step would be to investigate environment sensors. E.g. touch sensor should not deliver "touchTime"(SFTime) but "touchedByUser"(SFInt32) instead, true? ? What constitutes the state of a scene which needs synchronization across instances ? The main changes which need updating are the progress of time, and avatar state.? [Christoph:] This depends on the use case. If you had a museum like world(with predefined animation), where only the avatars would interactively move, then you were right. I prefer to dream of arbitrary animated and/or simulated interactive worlds/universes with moving models (cars, trains, houses, doors,......), where anything could be an avatar (even a locomotive could be an avatar) ? Perhaps it suffices to synchronize avatar generated event cascades and replay those in the instances ? Would that require an event queue for recording ? [Christoph:] What do you mean by "avatar generated event cascade"? I do not understand this term. When you talk about recording, do you mean LI requirements? I think LI will be a topic, in particular with respect to avatar position, and in particular when it comes to mixed reality. ? Another way to think about state synchronization is to have a very complete description of state and then only with deltas for synchronization and conflict resolution across instances. [Christoph:] I think the complete state must be stored persistently on a server, because anytime a new scene instance can join the session and must receive the complete state for initialization (do you know, how the Network Sensor of Bitmanagement works? I recommend to check it out). ? another 2c :) ? Andreas ? ? ? ? ? -Andreas ? ? Date: Thu, 28 Feb 2019 16:40:24 +0000 From: Valentin Christoph <Christoph.Valentin(a)kapsch.net<mailto:Christoph.Valentin@kapsch.net>[mailto:Christoph.Valentin@kapsch.net<mailto:Christoph.Valentin@kapsch.net>]> To: Andreas Plesch <andreasplesch(a)gmail.com<mailto:andreasplesch@gmail.com>[mailto:andreasplesch@gmail.com<mailto:andreasplesch@gmail.com>]> Cc: X3D Graphics public mailing list <x3d-public(a)web3d.org<mailto:x3d-public@web3d.org>[mailto:x3d-public@web3d.org<mailto:x3d-public@web3d.org>]> Subject: Re: [x3d-public] Multiplayer strategies Message-ID: ? ? ? ? <VI1PR03MB47038C7653CE09362D433D3EE4750(a)VI1PR03MB4703.eurprd03.prod.outlook.com<mailto:VI1PR03MB47038C7653CE09362D433D3EE4750@VI1PR03MB4703.eurprd03.prod.outlook.com>[mailto:VI1PR03MB47038C7653CE09362D433D3EE4750@VI1PR03MB4703.eurprd03.prod.outlook.com<mailto:VI1PR03MB47038C7653CE09362D433D3EE4750@VI1PR03MB4703.eurprd03.prod.outlook.com>]> Content-Type: text/plain; charset="utf-8" Hi Andreas, Maybe another 2 cents from my side. If we want to keep it simple, we should keep a 1:1 relationship between user and scene graph (I call this the ?personal scene instance? PSI). Why? Two reasons. (1) Maybe the scene consists of many ?modules?, which might span a large section of the Virtual Universe, an which are loaded and unloaded into each scene instance on demand. One user is ? for some time ? only interested in module A ? so other modules need not be loaded in ?his? scene instance ? saving memory and CPU resources. Other user is interested in several modules at the same time --> he will need higher performance in his scene instance So the matter of scalability will be easier to handle, if we keep user : PSI = 1 : 1. (2) The scene might provide different ?views? to different ?users?. One user might get a photo realistic 3D graphic, another user might receive a topographic illustration of the scene with only symbolic content. Only the ?shared state? is the same for all scene instances of a multiuser session As I said, just my two cent. All the best. From: x3d-public <x3d-public-bounces(a)web3d.org<mailto:x3d-public-bounces@web3d.org>[mailto:x3d-public-bounces@web3d.org<mailto:x3d-public-bounces@web3d.org>]> On Behalf Of Andreas Plesch Sent: Thursday, February 28, 2019 4:25 PM To: X3D Graphics public mailing list <x3d-public(a)web3d.org<mailto:x3d-public@web3d.org>[mailto:x3d-public@web3d.org<mailto:x3d-public@web3d.org>]> Subject: Re: [x3d-public] Multiplayer strategies Thanks for all the thoughtful response. Various ideas were offered. The DIS component is dedicated to communication and synchronization between browsers in a peer to peer fashion but has its own limitations. Outside of X3D various web technologies such as webRTC, websocket or socket.io<http://socket.io>[http://socket.io]<http://socket.io[http://socket.io]> exist which can be used with ad hoc protocols and SAI or DOM based scene updating. I think Firebase is designed to push realtime updates of a json store to all connected clients, and could fit well. Synchronization of multiple avatars and persistent avatar registration on a dedicated service was suggested. It is a wide field. To narrow the domain, let's perhaps consider the local, single game console/browser with multiple controllers and split screen/multiple headsets case, say up to 4 actors, no servers. Using a projector or a large TV, there is natural sharing which is eliminated with HMDs. Replicating the screen, one mode is just mirroring of a master render to other HMDs but this is very unpleasant in VR. Another mode is one actor with sensing, and other viewers, passive but still moving and looking. Another mode is full access to the scene for all locally connected. WebXR allows for multiple HMDs and controllers. I am not sure if web browsers can deal with multiple mice/keyboards but I suspect they can; there is a gamepad API. Brainstorming a multiple avatar, client only design: - a list of render surfaces, for each avatar, perhaps layout, layer related - a list of active avatars, linked to a render surface - a way to add and remove an avatar - an active viewpoint per avatar - touchsensor, other sensors linked to a list of avatars Very fuzzy but perhaps a start for thinking about such a case. I was looking around castle engine for inspiration from a gaming perspective but could not find much. It may be that dealing with multiple avatars in a single browser is actually more complicated than a local one browser per avatar, plus a synchronized scene from a scene server design which has to deal with updates to the shared scene, the synchronization, and distribution. Was there a VRML approach to shared experiences ? >From a practical standpoint, simply mirroring from a master HMD to a second connected HMD using webVR in x3dom would be a first step to explore. And perhaps exploring Firebase, eg. if it can store a json X3D scene, and how multiple X3DOM or X-ITE instances would receive it, perhaps in an inline. -Andreas On Tue, Feb 26, 2019, 5:33 AM Andreas Plesch <andreasplesch(a)gmail.com<mailto:andreasplesch@gmail.com>[mailto:andreasplesch@gmail.com<mailto:andreasplesch@gmail.com>]<mailto:andreasplesch@gmail.com<mailto:andreasplesch@gmail.com>[mailto:andreasplesch@gmail.com<mailto:andreasplesch@gmail.com>]> wrote: With VR it may become more common to share a live, dynamic experience using multiple headsets and controllers. At first glance this seems to call for multiple, active viewpoints rendered by a single browser. The layering and layout components seem relevant. Another strategy would be having multiple browsers with identical scenes and keeping scenes in sync with an additional process and SAI methods. What are the strategies offered by X3D to support sharing a live, dynamic world ? This came up as a x3dom GitHub issue and I thought may be more generally interesting. Andreas The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20190228/42e8e0…<http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20190228/42e8e0…>> ------------------------------ Subject: Digest Footer _______________________________________________ x3d-public mailing list x3d-public(a)web3d.org<mailto:x3d-public@web3d.org>[mailto:x3d-public@web3d.org<mailto:x3d-public@web3d.org>] http://web3d.org/mailman/listinfo/x3d-public_web3d.org ------------------------------ End of x3d-public Digest, Vol 119, Issue 86 *******************************************_______________________________________________ x3d-public mailing list x3d-public(a)web3d.org<mailto:x3d-public@web3d.org> http://web3d.org/mailman/listinfo/x3d-public_web3d.org[http://web3d.org/mai…<http://web3d.org/mailman/listinfo/x3d-public_web3d.org%5Bhttp://web3d.org/m…> ------------------------------ Message: 2 Date: Thu, 7 Mar 2019 18:29:24 +0000 From: "Brutzman, Donald (Don) (CIV)" <brutzman(a)nps.edu<mailto:brutzman@nps.edu>> To: "semantics(a)web3d.org<mailto:semantics@web3d.org>" <semantics(a)web3d.org<mailto:semantics@web3d.org>>, "X3D Graphics public mailing list" <x3d-public(a)web3d.org<mailto:x3d-public@web3d.org>> Subject: [x3d-public] X3D Semantic Web Working Group 7 MAR 2019: references, geometric properties, MPEG-7 Descriptors Message-ID: <6aa55efc-497c-1813-4bdb-c5843ae2486c(a)nps.edu<mailto:6aa55efc-497c-1813-4bdb-c5843ae2486c@nps.edu>> Content-Type: text/plain; charset="utf-8" 8.0. Eighth meeting of the Semantic Web Working Group Attendees Jakub Flotynski, Athanasios Malamos, Anita Havele, Don Brutzman. Web3D Teleconference Information http://www.web3d.org/member/teleconference-information Prior minutes, Jakub and Athanasios: [x3d-public] X3D Semantic Web Working Group minutes, 17 JAN 2019: structural and conceptual semantics http://web3d.org/pipermail/x3d-public_web3d.org/2019-January/009898.html All information in these minutes is approved for pubic release. ================================================================= 7.0 Last week's meeting included Thanos Jakub Nicholas Anita and Don. Essentially we reviewed website links and kept discussing/improving slides. Unfortunately my minutes got mistakenly deleted. Sorry about that. ================================================================= 8.1 *Working group information* The X3D Semantic Web Working Group is a Web3D Consortium member-only group that does most of its business openly on the x3d-public mailing list. X3D Semantic Web Working Group Charter http://www.web3d.org/working-groups/x3d-semantic-web/charter X3D Semantic Web Working Group http://www.web3d.org/working-groups/x3d-semantic-web "The X3D Semantic Web Working Group mission is to publish models to the Web using X3D in order to best gain Web interoperability and enable intelligent 3D applications, feature-based 3D model querying, and reasoning over 3D scenes." semantics(a)web3D.org http://web3d.org/mailman/listinfo/semantics_web3d.org ================================================================= 8.2 *Working group assets* We have started work on the following website pages to record resources. Many are now present, more will follow. X3D Semantic Web Public Assets http://www.web3d.org/x3d-semantic-web-public-assets X3D Semantic Web Member Assets http://www.web3d.org/member/wiki/x3d-semantic-web-member-assets Working group co-chairs have permission to edit the member-assets page, then results are reviewed and copied over to public-assets page. Inputs welcome to keep building and structuring these important lists of assets. ================================================================= 8.3 *Workshop opportunities* We think that our current activity can likely be a contribution at the upcoming First Eurographics-EuroVR Workshop on Semantic 3D Content 6 May 2019 in Genova Italy as part of EuroGraphics 2019 http://semantic3d.org/workshop Paper/poster/demonstration submission deadline extended: March 10, 2019 We discussed what a good follow-on might be for Web3D 2019 Conference. Perhaps another workshop, or simply a meeting, on X3D Semantic Web Working Group. This could build on the EuroGraphics 2019 momentum, disseminate progress among participants and set us up for much expected work to emerge in the coming year. WEB3D 2019: 24th International ACM Conference on 3D Web Technology 26-28 July 2019, Colocated with SIGGRAPH2019, Los Angeles California USA http://www.web3d.org/event/web3d-conference-2019 http://web3d2019.web3d.org The current work will not be sufficiently mature to be a paper submission by the deadline (~10 days away). Instead we plan to submit a Web3D workshop proposal for this new work. This can build upon the Eurographics-EuroVR Workshop products. Possibly a poster is also appropriate, especially if it describes coherent existing work. Web3D workshop deadline submission: 1 April 2019. This will be next week's topic. ================================================================= 8.4 Primary topic: *slideset Semantic X3D - thoughts and ideas* Much detailed architectural work is in progress, distilled in these slides. https://docs.google.com/presentation/d/1fCMu0V-zRAfJqFId7QIMyLh2EOCr5Qgl63M… _Geometric properties_ (slides 9-10) updated: Thanos said ?sitting in my corner? ... Can we define a property for ?corner? based on geometric relationships? Good to think about. We might suppose multiple candidate geometric properties: * Primitive shapes: Rectangular, Conical, Cylindrical, Spherical, Ellipsoid, Point, Line, Mesh * Side, TopSide BottomSide LeftSide RightSide FrontSide BackSide * ParametricSurface, NURBS, BREP, other types? * Characteristics: Irregular, Open, Closed (Watertight), Corner, Seam, Wall * Angular relationships: Perpendicular, Acute, Obtuse ------ Thanos: corner rdfs:subClassOf str:includes(2) str:triangles; If normal(A) CROSS-PRODUCT normal(B) >0 -> createCorner(C) and includes(C,A) and includes(C,B) ------ TODO: does there already exist a set of 3D property classes related to shape of models? TODO: should we next compare existing 3D ontologies of interest? TODO: build examples that help us determine the best, most reusable elements of an X3D ontology? We discussed relationships and 3D functions for extraction of semantic information from geometric shapes so we could specify possible goals of our works: * Extraction of semantic information from X3D models (re-visit MPEG7) * Generating X3D models on the basis of semantic 3D models (conceptual) * Likely an iterative process, OWL inference can generate more RDF properties * Semantic annotation (description) of X3D (without representation) ================================================================= 8.5 MPEG-7 overview We briefly discussed prior work with MPEG-7. Background: MPEG-7 - Wikipedia https://en.wikipedia.org/wiki/MPEG-7 "MPEG-7 is a multimedia content description standard. It was standardized in ISO/IEC 15938 (Multimedia content description interface). This description will be associated with the content itself, to allow fast and efficient searching for material that is of interest to the user. MPEG-7 is formally called Multimedia Content Description Interface. Thus, it is not a standard which deals with the actual encoding of moving pictures and audio, like MPEG-1, MPEG-2 and MPEG-4. It uses XML to store metadata, and can be attached to timecode in order to tag particular events, or synchronise lyrics to a song, for example. It was designed to standardize: * a set of Description Schemes ("DS") and Descriptors ("D") * a language to specify these schemes, called the Description Definition Language ("DDL") * a scheme for coding the description The combination of MPEG-4 and MPEG-7 has been sometimes referred to as MPEG-47." TODO Thanos will look up whether licensing or patents have been declared. MPEG Licensing Authority https://www.mpegla.com ================================================================= 8.6 MPEG-7 Visual Descriptors: More than MPEG-7 These are draft slides that Thanos has prepared for our discussions. They will be exposed publicly once further developed. https://docs.google.com/presentation/d/11VSFHriBnOXJzsHfYX0XDUMVqO5X9HePUvQ… Back to shared slideset, follow-on slide 11: -------------------------------------- Inclusion of Visual Descriptors in X3D Visual Descriptors are available for color and shape. They seem quite analogous to structure provided by RDF properties. It is an interesting question whether the X3D Specifications are ?ready? for inclusion of visual descriptors. Visual-descriptor properties are primarily metadata about a scene, not directions for rendering. Indeed our current effort is to create such a conceptually coherent ontology for X3D. Thus if we define how to include visual descriptor properties in a scene, * Authors could include Metadata nodes with RDF properties, * Tools could perform geometric inference and similarly add Metadata nodes Attaching semantic information to X3D scenes This working group needs to identify X3D Ontology mappings as * embedded MetadataSet structures * embedded (multi-namespace?) and external RDF files * norms and best practices for including such descriptor files ====================================== 8.7 *W3C Ontology for Media Resources* Really important reference that Jakub identified: Ontology for Media Resources 1.0 W3C Recommendation 09 February 2012 https://www.w3.org/TR/mediaont-10/ This ontology has an amazing number of metadata correlations. Further, aligning an X3D Ontology with this approach would immediately give us a broad number of terms and mappings, all compatible with HTML5. Excerpt from Table of Contents: 5.2.2 Multimedia metadata formats mapping tables 5.2.2.1 CableLabs 1.1 5.2.2.2 DIG35 5.2.2.3 Dublin Core 5.2.2.4 EBUCore 5.2.2.5 EXIF 2.2 5.2.2.6 ID3 5.2.2.7 IPTC 5.2.2.8 LOM 2.1 5.2.2.9 Media RSS 5.2.2.10 MPEG-7 5.2.2.11 OGG 5.2.2.12 QuickTime 5.2.2.13 DMS-1 5.2.2.14 TTML 5.2.2.15 TV-Anytime 5.2.2.16 TXFeed 5.2.2.17 XMP 5.2.2.18 YouTube 5.2.3 Multimedia container formats mapping tables 5.2.3.1 3GP 5.2.3.2 Flash 5.2.3.2.1 FLV 5.2.3.2.2 F4V 5.2.3.3 QuickTime 5.2.3.4 MP4 5.2.3.5 OGG 5.2.3.6 WebM We definitely need to review and study this work further. Wondering if we can invite an expert in that group to give a presentation at Web3D 2019?! ================================================================= 8.8 * Planning Ahead * We plan to meet 14 MAR and 21 MAR. No meeting 28 MAR. Of interest: Prot?g? Short Course: MARCH 27 - 29, 2019 at STANFORD, CA https://protege.stanford.edu/short-courses.php ================================================================= Steady interesting progress, thanks colleagues! 8) 8) 8) all the best, Don -- Don Brutzman Naval Postgraduate School, Code USW/Br brutzman(a)nps.edu<mailto:brutzman@nps.edu> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149 X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman ------------------------------ Subject: Digest Footer _______________________________________________ x3d-public mailing list x3d-public(a)web3d.org<mailto:x3d-public@web3d.org> http://web3d.org/mailman/listinfo/x3d-public_web3d.org ------------------------------ End of x3d-public Digest, Vol 120, Issue 34 ******************************************* _______________________________________________ x3d-public mailing list x3d-public(a)web3d.org http://web3d.org/mailman/listinfo/x3d-public_web3d.org _______________________________________________ x3d-public mailing list x3d-public(a)web3d.org http://web3d.org/mailman/listinfo/x3d-public_web3d.org

1 0

Re: [SR-Users] MySql Deadlock errors in Presence updates but db_mode set to 0
by paul＠irishvoip.com 08 Mar '19

08 Mar '19

Thanks Charles. Yes that helps. My design is flawed I think. I am trying to use both a shared DB (through Galera clustered MariaDB) and DMQ. The benefits of the shared DB are that I can have the same static tables like dispatcher etc but was hoping to be able to move most of my dyamic data logic to DMQ. It is replicating some of the presence data through DMQ because the secondary server is trying to update presence data from users interacting with the primary server. I my need to move to separate DBs for each server then it seems. regards Paul

1 0

MySql Deadlock errors in Presence updates but db_mode set to 0
by paul＠irishvoip.com 08 Mar '19

08 Mar '19

Hi there My config is a primary:secondary DNS srv failover Kamailio 5.2 setup using DMQ for syncing Location, Presence, HTable etc. For Presence db_mode set to 0 on both servers. This works fine on the primary server but on the secondary server I get repeated mysql deadlock errors. I seem to be missing a config setting to turn off db_mode fully for presence but I cant see where. Error seems to occur on message-summary updates from master that are being replicated to slave via DMQ. Mar 08 13:52:39 /usr/sbin/kamailio[17493]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Mar 08 13:52:39 /usr/sbin/kamailio[17493]: ERROR: db_mysql [km_dbase.c:714]: db_mysql_end_transaction(): executing raw_query Mar 08 13:52:39 /usr/sbin/kamailio[17493]: ERROR: presence [presentity.c:1299]: update_presentity(): in end_transaction Mar 08 13:52:40 /usr/sbin/kamailio[17493]: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Deadlock found when trying to get lock; try restarting transaction (1213) I am using the following presence related modules loadmodule "presence.so" loadmodule "presence_mwi.so" loadmodule "presence_xml.so" loadmodule "pua.so" loadmodule "rls.so" loadmodule "xcap_server.so" loadmodule "xcap_client.so" params are set as below loadmodule "presence.so" loadmodule "presence_mwi.so" loadmodule "presence_xml.so" loadmodule "pua.so" loadmodule "rls.so" loadmodule "xcap_server.so" loadmodule "xcap_client.so" params are set as below with PRESENCEDBMODE set to 0 on both servers. #!ifdef WITH_PRESENCE # ----- presence params ----- modparam("presence", "db_url", DBURL) modparam("presence", "db_update_period", 5) modparam("presence", "server_address", "sip:myserver.com") modparam("presence", "subs_db_mode", PRESENCEDBMODE) modparam("presence", "send_fast_notify", 1) modparam("presence", "timeout_rm_subs", 0) modparam("presence", "db_table_lock_type", 0) modparam("presence", "notifier_processes", 3) modparam("presence", "local_log_level", 3) modparam("presence", "publ_cache", 1) #!ifdef WITH_DMQ modparam("presence", "enable_dmq", 1) #!else modparam("presence", "enable_dmq", 0) #!endif #!ifdef WITH_BUDDY # ----- presence_xml params ----- modparam("presence_xml", "db_url", DBURL) modparam("presence_xml", "passive_mode", 1) modparam("presence_xml", "integrated_xcap_server", 1) modparam("presence_xml", "xcap_server", "https://xcap.myserver.com/xcap-root") modparam("presence_xml", "force_dummy_presence", 1) modparam("pua", "db_url", DBURL) modparam("pua", "db_mode", PRESENCEDBMODE) modparam("pua", "db_table_lock_write", 0) modparam("pua", "check_remote_contact", 0) modparam("rls", "db_url", DBURL) modparam("rls", "db_mode", PRESENCEDBMODE) modparam("rls", "notifier_processes", 2) modparam("rls", "integrated_xcap_server", 1) modparam("rls", "xcap_root", "https://xcap.myserver.com/xcap-root") modparam("rls", "server_address", "sip:rls@myserver.com") modparam("rls", "outbound_proxy", "sip:myserver.com") modparam("rls", "disable_remote_presence", 0) modparam("rls", "max_backend_subs", 1000) modparam("rls", "to_presence_code", 10) modparam("rls", "rls_event", "presence") modparam("rls", "rls_event", "presence.winfo") modparam("xcap_server", "db_url", DBURL) modparam("xcap_server", "directory_scheme", -1) modparam("xcap_server", "xcap_root", "/xcap-root/") modparam("xcap_client", "db_url", DBURL) modparam("xcap_client", "query_period", 50) Any ideas? thanks Paul

2 1

Licensing clarification of Kamailio scripting code
by Wei Li Jiang 08 Mar '19

08 Mar '19

Hi, I am aware the Kamailio itself as well as the native C modules are licensed under the GPL. What is the licensing situation with the Kamailio routing scripts, both native and via KEMI? Regards, Wei Li -- *Wei Li Jiang* *Senior Design Engineer* *Tait Communications* *DDI:* 64 3 3570747 *Email:* weili.jiang(a)taitradio.com *www.taitradio.com <http://www.taitradio.com>* -- This Communication is Confidential. We only send and receive email on the basis of the terms set out at www.taitradio.com/email_disclaimer <http://www.taitradio.com/email_disclaimer>

3 2

"invalid cseq for aor" on registrar nodes
by jay binks 08 Mar '19

08 Mar '19

Hi All, I'm getting the ERROR message "invalid cseq for aor" on my registrar nodes that sit behind my load balancers. My LB's take REGISTER messages, perform all the AUTH, and post AUTH, the messages are forwarded to my registrar nodes, and are then saved. what im finding is messages similar to this : ERROR: registrar [save.c:599]: test_max_contacts(): invalid cseq for aor <BLAH> I believe everything is functioning as expected, AOR's are saved and retrieved etc. but at a minimum, this message is filling my logs with messages that look scary! ( my ops team should not be expected to ignore ERROR Level log messages ) -- Sincerely Jay

1 0

Sanity check with default_checks=0
by Denys Pozniak 07 Mar '19

07 Mar '19

Hello! I have Kamailio v4.4 and use (historical) the next param setting to disable sanity check: modparam("sanity", "default_checks", 0) I see that this value 0 is not described in module documentation, but looks like this modparam behaves in another way on Kamailio v5. So my question is how to disable sanity checking in modparam? -- BR, Denys Pozniak

2 2

log_prefix missing
by Joonas Kamailio 07 Mar '19

07 Mar '19

Dear List, I am having a problem where log_prefix is missing on acc_cdr log row when call is canceled. Here is an example of two lines of acc_cdr log file, first one is completed normally and second one is canceled before 200 OK: Mar 6 12:04:48 edge3 kamailio[27669]: NOTICE: {2 1 BYE 23d4e04c0c79ff6950accbd1706b91b1(a)example.com} acc [acc_cdr.c:367]: log_write_cdr(): start_time=1551873885.018; end_time=1551873888.379; duration=3.361; Mar 6 12:03:40 edge3 kamailio[27707]: NOTICE: acc [acc_cdr.c:367]: log_write_cdr(): start_time=1551873809.148; end_time=1551873809.148; duration=0; I tried to take a debug on this matter and noticed that log_prefix is lost at this point: Mar 6 13:54:25 edge3 kamailio[10665]: DEBUG: {1 102 INVITE 6917f51f0955bd8b3a1aa62361a473ce(a)example.com} tm [t_lookup.c:1019]: t_check_msg(): msg (0x7f1a889a8a30) id=0 global id=0 T start=0x7f1a8899b450 Mar 6 13:54:25 edge3 kamailio[10665]: DEBUG: {1 102 INVITE 6917f51f0955bd8b3a1aa62361a473ce(a)example.com} tm [t_lookup.c:1092]: t_check_msg(): T (0x7f1a8899b450) already found for msg (0x7f1a889a8a30)! Mar 6 13:54:25 edge3 kamailio[10665]: DEBUG: {1 102 INVITE 6917f51f0955bd8b3a1aa62361a473ce(a)example.com} dialog [dlg_var.c:97]: cb_dlg_locals_reset(): resetting the local dialog shortcuts on script callback: 2147483650 Mar 6 13:54:25 edge3 kamailio[10665]: DEBUG: tm [t_reply.c:1806]: relay_reply(): branch=0, save=0, relay=0 icode=0 msg status=487 Mar 6 13:54:25 edge3 kamailio[10665]: DEBUG: <core> [core/msg_translator.c:2288]: generate_res_buf_from_sip_res(): old size: 483, new size: 399 On normal call the prefix stays in intact: Mar 6 13:57:29 edge3 kamailio[10670]: DEBUG: {2 103 BYE 03cd8f3464d42b7b01966e6b1154eedc(a)example.com} tm [t_lookup.c:1088]: t_check_msg(): msg (0x7f1a95baad10) id=2 global id=2 T end=0x7f1a8899f8f0 Mar 6 13:57:29 edge3 kamailio[10670]: DEBUG: {2 103 BYE 03cd8f3464d42b7b01966e6b1154eedc(a)example.com} tm [t_reply.c:2237]: reply_received(): org. status uas=0, uac[0]=0 local=0 is_invite=0) Mar 6 13:57:29 edge3 kamailio[10670]: DEBUG: {2 103 BYE 03cd8f3464d42b7b01966e6b1154eedc(a)example.com} tm [t_reply.c:1263]: t_should_relay_response(): ->>>>>>>>> T_code=0, new_code=200 Mar 6 13:57:29 edge3 kamailio[10670]: DEBUG: {2 103 BYE 03cd8f3464d42b7b01966e6b1154eedc(a)example.com} tm [t_reply.c:1806]: relay_reply(): branch=0, save=0, relay=0 icode=0 msg status=200 Mar 6 13:57:29 edge3 kamailio[10670]: DEBUG: {2 103 BYE 03cd8f3464d42b7b01966e6b1154eedc(a)example.com} <core> [core/msg_translator.c:2288]: generate_res_buf_from_sip_res(): old size: 491, new size: 407 The problem exists at least in the following version: version: kamailio 5.2.0 (x86_64/linux) c5216b 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, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: c5216b compiled on 13:05:00 Jan 7 2019 with gcc 6.3. Best Regards, Joonas Keskitalo

3 2

UAC Module OPTIONS requests
by Greg Adams 06 Mar '19

06 Mar '19

Hey there, I'm wondering if any is able to help me. Trying to figure out how one might send OPTIONS request (ie the keepalive module) for registrations originating from the uac module? Have managed to figure out tcp keep alives but for some reason my connection is being closed even though they are sending, so hoping to try sending OPTIONS and see if that does it. It looks like the keepalive module only has an internal api doesn't actually expose the method to enable keepalives on individual TCP connections. Any help would be greatly appreciated!

2 1

Kamailio not recognizing SIP requests
by Sergio Charrua 06 Mar '19

06 Mar '19

Hi all! got a Kamailio doing load balancing to multiple Asterisk boxes. Kamailio is connected to a carrier's SIP trunk, and distributes calls to Asterisk. Receiving calls from carrier's SIP trunk works perfectly: kamailio will use dispatcher module to distribute calls between Asterisk boxes. No problems! Kamailio is also connected to the WWW, receiving calls from any authorized IP (whitelisted in Firewall). The problem is that if I get a call from the WWW and a from whitelisted IP, kamailio does not detect any INVITE (note that the IP address is not registered). here is the SIP Request (IPs are obfuscated) INVITE sip:+351234567890@10.19.139.66 SIP/2.0 Record-Route: <sip:11.22.33.44:5060 ;r2=on;transport=udp;ftag=11592086_6772d868_135fa74b-2c83-4d5f-9882-4125b131c703;l Record-Route: <sip:222.33.44.55:5060 ;r2=on;transport=udp;ftag=11592086_6772d868_135fa74b-2c83-4d5f-9882-4125b131c703r> CSeq: 1 INVITE From: <sip:+351999999999@somewhere.com >;tag=11592086_6772d868_135fa74b-2c83-4d5f-9882-4125b131c703 To: <sip:+351234567890@10.19.139.66> Max-Forwards: 65 P-Asserted-Identity: "+351999999999" <sip:+351999999999@sip.somewhere.com> Date: Tue, 05 Mar 2019 15:55:24 GMT Min-SE: 120 Call-ID: 799ee9a8cd02e066e2811d8052759715(a)0.0.0.0 Via: SIP/2.0/UDP 11.22.33.44:5060;branch=z9hG4bK6b36.f67ca7e4.0 Via: SIP/2.0/UDP 222.33.44.55:5060 ;branch=z9hG4bK135fa74b-2c83-4d5f-9882-4125b131c703_6772d868_106-113479085018764135 Contact: "+351999999999" <sip:+351999999999@222.33.44.55:5060;transport=udp> Allow: INVITE,ACK,CANCEL,OPTIONS,BYE User-Agent: SomeSIPGateway Content-Type: application/sdp X-SIPGW-CallSid: CA6a5691a75bb7b915c09c7931e253f542 Content-Length: 262 v=0 o=root 1219665045 1219665045 IN IP4 55.66.77.88 s=SomeSIPGateway c=IN IP4 55.66.77.88 t=0 0 m=audio 14326 RTP/AVP 0 8 101 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 SIP Messages using SNGrep: 11.22.33.44:5060 10.19.139.66:5060 ----------+--------- ----------+--------- 15:55:25.980727 | INVITE (SDP) | +0.596007 | --------------------------> | 15:55:26.576734 | INVITE (SDP) | +1.003393 | ------------------------>>> | 15:55:27.580127 | INVITE (SDP) | +1.978513 | ------------------------>>> | 15:55:29.558640 | INVITE (SDP) | | ------------------------>>> | I've checked that Kamailio is listennig to all interfaces (OK) and to port 5060 (OK). As we can see above, SNGrep shows the incoming message to Kamailio (10.19.139.66) but it gets stuck there as there are no other messages. Kamailio.log doesn't show anything too, just like if the request (INVITE) is not recognizes a a SIP message. all other use cases work fine : - from SIP Carrier's trunk OK - from registered SIP user OK - from registered SIP Trunk ok only from a not registered SIP trunk I get this behaviour.... Any clue? Thanks in advance, *Sérgio * www.voip.pt

2 1

ACKs + BYEs coming from the wrong interface/ip
by Boden Garman 06 Mar '19

06 Mar '19

Hello list! I am trying to troubleshoot an issue we are having where we sometimes see an ACK in response to a 200 OK (SDP) come from the a different IP address to the rest of dialogue. The client ignore the traffic from the different IP and the call set up fails. Kamailio is multihomed on two IPs and this client is registered with the first IP address. I have done some searching on this and seen a few others with the issue, it seems like it's the ACK in the loose_route() section of WITHINDLG in the default kamailio.cfg file. I tried the force_send_socket solution one other person suggested but this caused issues with other kinds of dialogues, perhaps I did it incorrectly? Thanks for your time Boden Here is my attempt to solve the issue and config snippets mhomed=1 # ----- rr params ----- # set next param to 1 to add value to ;lr param (helps with some UAs) modparam("rr", "enable_full_lr", 1) # do not append from tag to the RR (no need for this script) modparam("rr", "append_fromtag", 1) # Handle requests within SIP dialogs route[WITHINDLG] { if (!has_totag()) return; # sequential request within a dialog should # take the path determined by record-routing if (loose_route()) { route(DLGURI); # this is the attempt to use the right IP if ($(route_uri{uri.host}) == VRRP_IP) { force_send_socket(VRRP_IP); } else if ($(route_uri{uri.host}) == KAM01_IP) { force_send_socket(KAM01_IP); } if (is_method("BYE")) { setflag(FLT_ACC); # do accounting ... setflag(FLT_ACCFAILED); # ... even if the transaction fails } else if (is_method("ACK")) { # ACK is forwarded statelessly route(NATMANAGE); } else if (is_method("NOTIFY")) { # Add Record-Route for in-dialog NOTIFY as per RFC 6665. record_route(); } route(RELAY); exit; } if (is_method("SUBSCRIBE") && uri == myself) { # in-dialog subscribe requests route(PRESENCE); exit; } if (is_method("ACK")) { if (t_check_trans()) { # no loose-route, but stateful ACK; # must be an ACK after a 487 # or e.g. 404 from upstream server route(RELAY); exit; } else { # ACK without matching transaction ... ignore and discard exit; } } sl_send_reply("404", "Not here"); exit; } For example (please excuse formatting) xxx.xx.xxx.97:5060 xxx.xx.xxx.96:5060 yyy.yyy.102.96:58308 xxx.xx.xxx.27:5060 ----------w--------- ----------w--------- ----------w--------- ----------w--------- x INVITE (SDP) x x x x --------------------------> x x x x 100 trying -- your call is x x x x <-------------------------- x x x x x INVITE (SDP) x x x x --------------------------> x x x x 100 Trying x x x x <-------------------------- x x x x 180 Ringing x x x x <-------------------------- x x x 180 Ringing x x x x <-------------------------- x x x x x 200 OK (SDP) x x x x <-------------------------- x x x 200 OK (SDP) x x x x <-------------------------- x x x x ACK x x x x --------------------------> x x x x x x ACK x x x x <-------------------------- x x x 200 OK (SDP) x x x x <<<------------------------ x x

1 0

Kamctl / kamcmd
by Daniel W. Graham 05 Mar '19

05 Mar '19

Are there any known compatibility issues with kamctl and mysql 8.0.x? Getting access denied when executing kamctl command. Kamcmd just hangs when executed. Kamctlrc is setup proper and connection can be made direct from shell to database using the same credentials. -dan

3 11

Selects and KEMI
by Alexandru Covalschi 05 Mar '19

05 Mar '19

Is there any way to use selects in KEMI? I understand it's syntax sugar, but maybe there's a workaround. ________________________________ Regards, Alexandru Covalschi VoIP Engineer and System Administrator tel: +380 97 24 75445

1 0

it's auth module send clear text password?
by PICCORO McKAY Lenz 05 Mar '19

05 Mar '19

if kamailio doe snot use TLS all the mechanish in atuh module are send the pasword nude to the network? Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com

3 4

evapi_async + python3 KEMI
by Alexandru Covalschi 05 Mar '19

05 Mar '19

Hello list, I'm trying to use async evapi with app_python3 KEMI, but I don't know how to get t_suspend variables. What am I doing is connecting to evapi via telnet and making a call, which successfully reaches that point: if KSR.evapi.async_relay(str(KSR.pv.get("$T(id_label)"))): KSR.xlog.xinfo("processing suspended in transaction [" + str(KSR.pv.get("$T(id_index)")) + ":" + str(KSR.pv.get("$T(id_label)")) +"]\n"); I have the id_label in the log, but in telnet I have None. How can I get transaction index and label transferred using python3 KEMI? Shall I use KSR.x.modf (in that case I'm losing almost all KEMI benefits)?.. ________________________________ Regards, Alexandru Covalschi VoIP Engineer and System Administrator tel: +380 97 24 75445

2 3

Cannot start kamailio with TLS
by Adesh Pandey 04 Mar '19

04 Mar '19

Hi Guys, After enabling TLS i am getting following error in Kamailio 5.1 /usr/sbin/kamailio[2214]: ERROR: tls [tls_util.h:42]: tls_err_ret(): load_cert:error:20074002:BIO routines:file_ctrl:system lib /usr/sbin/kamailio[2214]: ERROR: tls [tls_util.h:42]: tls_err_ret(): load_cert:error:140DC002:SSL routines:use_certificate_chain_file:system lib /usr/sbin/kamailio[2214]: ERROR: <core> [core/sr_module.c:940]: init_mod_child(): error while initializing module tls (/usr/lib/x86_64-linux-gnu/kamailio/modules/tls.so) (idx: 0 rank: -127 desc: [main]) My tls.conf is as follows: [server:default] method = TLSv1+ verify_certificate = no require_certificate = no private_key = /etc/kamailio/keys/my.key.pem certificate = /etc/kamailio/keys/my.crt.pem #ca_list = /etc/kamailio/tls/cacert.pem #crl = /etc/kamailio/tls/crl.pem # This is the default client domain, settings # in this domain will be used for all outgoing # TLS connections that do not match any other # client domain in this configuration file. # We require that servers present valid certificate. # [client:default] #method = TLSv1 verify_certificate = yes require_certificate = yes Please hep me to understand and fix the issue.

2 2

tm.so --> segfault at 3135352e36 ip 00007f761bb57ed1 sp 00007fff9db8b1c0 error 4 in tm.so
by Abdoul Osséni 04 Mar '19

04 Mar '19

Hello, Hello dear list, Today, I have had mutiples crashes. It seems it linked to tm.so module. -rw------- 1 root kamailio 4299702272 Feb 25 13:08 core.kamailio.sig11.29204 -rw------- 1 root kamailio 1453023232 Feb 25 13:12 core.kamailio.sig11.29203 -rw------- 1 root kamailio 1416065024 Feb 25 13:12 core.kamailio.sig11.29207 -rw------- 1 root kamailio 4299681792 Feb 25 13:16 core.kamailio.sig11.19047 -rw------- 1 root kamailio 2108506112 Feb 25 13:20 core.kamailio.sig11.19043 -rw------- 1 root kamailio 4299689984 Feb 25 13:34 core.kamailio.sig11.19247 -rw------- 1 root kamailio 4299681792 Feb 25 13:34 core.kamailio.sig11.19246 -rw------- 1 root kamailio 4299698176 Feb 25 13:35 core.kamailio.sig11.19248 -rw------- 1 root kamailio 4299689984 Feb 25 13:35 core.kamailio.sig11.19243 -rw------- 1 root kamailio 4299685888 Feb 25 13:35 core.kamailio.sig11.19244 -rw------- 1 root kamailio 4299689984 Feb 25 13:36 core.kamailio.sig11.19242 root@sbc:/var/cores# gdb /usr/local/sbin/kamailio core.kamailio.sig11.29204 GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html > This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/local/sbin/kamailio...done. [New LWP 29204] warning: .dynamic section for "/lib/x86_64-linux-gnu/libpthread.so.0" is not at the expected address (wrong library or version mismatch?) Warning: couldn't activate thread debugging using libthread_db: Cannot find new threads: generic error warning: File "/lib/x86_64-linux-gnu/libthread_db-1.0.so" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". To enable execution of this file add add-auto-load-safe-path /lib/x86_64-linux-gnu/libthread_db-1.0.so line to your configuration file "/root/.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file "/root/.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell: info "(gdb)Auto-loading safe path" warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. Warning: couldn't activate thread debugging using libthread_db: Cannot find new threads: generic error warning: File "/lib/x86_64-linux-gnu/libthread_db-1.0.so" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load". warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available. Core was generated by `/usr/local/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /usr/local/etc/ka'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f68b9bb4515 in reply_received (p_msg=0x7f693ccd5cc8) at t_reply.c:2240 2240 last_uac_status=uac->last_received; (gdb) Any ideas? Regards Abdoul

3 8

crash at 480 reply to INVITE
by Juha Heinanen 04 Mar '19

04 Mar '19

Kamailio 5.2 crashed when it received 480 reply to INVITE. Below is backtrace from the core file. The crash happens in t_reply.c on the last line of this block: uac=&t->uac[branch]; LM_DBG("org. status uas=%d, uac[%d]=%d local=%d is_invite=%d)\n", t->uas.status, branch, uac->last_received, is_local(t), is_invite(t)); last_uac_status=uac->last_received; Earlier it was checked that the transaction was found. Its uac[0] seems to be broken. -- Juha ----------------------------------------- Program terminated with signal SIGSEGV, Segmentation fault. #0_ 0x00007f1073e234c3 in reply_received (p_msg=0x7f1076b605f0) at t_reply.c:2240 2240_ _ _ t_reply.c: No such file or directory. (gdb) bt full #0_ 0x00007f1073e234c3 in reply_received (p_msg=0x7f1076b605f0) at t_reply.c:2240 _ _ _ _ _ _ _ msg_status = 480 _ _ _ _ _ _ _ last_uac_status = 1590315756 _ _ _ _ _ _ _ ack = 0x50550c4 <error: Cannot access memory at address 0x50550c4> _ _ _ _ _ _ _ ack_len = 4 _ _ _ _ _ _ _ branch = 0 _ _ _ _ _ _ _ reply_status = 29 _ _ _ _ _ _ _ onreply_route = 9941216 _ _ _ _ _ _ _ cancel_data = {cancel_bitmap = 0, reason = {cause = 0, u = {text = {s = 0x0, len = 1590087991}, e2e_cancel = 0x0, packed_hdrs = {s = 0x0, len = 1590087991}}}} _ _ _ _ _ _ _ uac = 0x0 _ _ _ _ _ _ _ t = 0x7f105dfe6480 _ _ _ _ _ _ _ lack_dst = {send_sock = 0x555b5f02720f <buf+431>, to = {s = {sa_family = 29127, sa_data = "XXX"}, sin = {sin_family = 29127, sin_port = 24322, sin_addr = {s_addr = 21851}, sin_zero = "XXX"}, sin6 = { _ _ _ _ _ _ _ _ _ _ _ _ _ sin6_family = 29127, sin6_port = 24322, sin6_flowinfo = 21851, sin6_addr = {__in6_u = {__u6_addr8 = "XXX", __u6_addr16 = {XXX, XXX, XXX, XXX, XXX, XXX, XXX, XXX}, __u6_addr32 = {XXX, XXX, XXX, _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ XXX}}}, sin6_scope_id = 1980563656}}, id = 32528, proto = 112 'p', send_flags = {f = 30268, blst_imask = 32528}} _ _ _ _ _ _ _ backup_user_from = 0x0 _ _ _ _ _ _ _ backup_user_to = 0xXXX <qm_info+46> _ _ _ _ _ _ _ backup_domain_from = 0xXXX _ _ _ _ _ _ _ backup_domain_to = 0xXXX _ _ _ _ _ _ _ backup_uri_from = 0x0 _ _ _ _ _ _ _ backup_uri_to = 0xXXX _ _ _ _ _ _ _ backup_xavps = 0x45ed834e3 _ _ _ _ _ _ _ replies_locked = 1 _ _ _ _ _ _ _ branch_ret = 1593995512 _ _ _ _ _ _ _ prev_branch = 21851 _ _ _ _ _ _ _ blst_503_timeout = 340003632 _ _ _ _ _ _ _ hf = 0x7f1076490810 _ _ _ _ _ _ _ onsend_params = {req = 0x7f10763c4898, rpl = 0x7f10763c4888, param = 0x97b5f0, code = 10751248, flags = 0, branch = 0, t_rbuf = 0xaf95c0, dst = 0x7f1076db4fc0 <__syslog>, send_buf = {s = 0x555b5ed834e3 "INFO", len = 134217728}} _ _ _ _ _ _ _ ctx = {rec_lev = 1593995791, run_flags = 21851, last_retcode = 1593995708, jmp_env = {{__jmpbuf = {48, 139708676767760, 93849330384899, -7479270984431321856, 93850924380609, 139708690288576, 93850921612515, 134217728}, __mask_was_saved = 12582912, __saved_mask = { _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __val = {6, 140720648489936, 139708687844848, 140720648490064, 93850920720905, 93850924380373, 139708676767760, 140720648489904, 139708469727337, 139708679781296, 139708687844848, 139708684105760, 140720648490560, 5888963087, 93849330384896, 11507136}}}}} _ _ _ _ _ _ _ bctx = 0x7f10760d0010 _ _ _ _ _ _ _ keng = 0x0 _ _ _ _ _ _ _ __func__ = "reply_received" #1_ 0x0000555b5eadf4dc in do_forward_reply (msg=0x7f1076b605f0, mode=0) at core/forward.c:747 _ _ _ _ _ _ _ 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 = "XXX"}, 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, blst_imask = 0}} _ _ _ _ _ _ _ new_len = 0 _ _ _ _ _ _ _ r = 1 _ _ _ _ _ _ _ ip = {af = XXX, len = 32528, u = {addrl = {XXX, 95}, addr32 = {XXX, XXX, XXX, 0}, addr16 = {XXX, XXX, XXX, XXX, XXX, XXX, XXX, XXX}, addr = "XXX"}} _ _ _ _ _ _ _ s = 0x7ffc14440c68 "" _ _ _ _ _ _ _ len = 32764 _ _ _ _ _ _ _ __func__ = "do_forward_reply" #2_ 0x0000555b5eae12f9 in forward_reply (msg=0x7f1076b605f0) at core/forward.c:852 No locals. #3_ 0x0000555b5eb5b679 in receive_msg ( _ _ _ buf=0x555b5f027060 <buf> "SIP/2.0 480 Request Terminated\r\nVia: SIP/2.0/UDP XXX;branch=z9hG4bKe951.40cf95b28fe54d0cbda88a8fa4c91d48.0\r\nVia: SIP/2.0/UDP XXX:5060;branch=z9hG4bK04B95fa49ac99a7fa91\r\nTo: <sip:XXX"..., len=431, _ _ _ rcv_info=0x7ffc14440ff0) at core/receive.c:433 _ _ _ _ _ _ _ msg = 0x7f1076b605f0 _ _ _ _ _ _ _ ctx = {rec_lev = 0, run_flags = 0, last_retcode = 1, jmp_env = {{__jmpbuf = {139708690288576, 9004276570109933907, 93850921612515, 134217728, 12582912, 6, 9004276570114128211, 3007006209029601619}, __mask_was_saved = 0, __saved_mask = {__val = {0, 0, 0, 1, _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 139708266465728, 0, 0, 4634971920, 139708266465728, 140720648490768, 93850918093314, 120, 93850918093450, 139708680838560, 139708680838560, 140720648490832}}}}} _ _ _ _ _ _ _ bctx = 0x0 _ _ _ _ _ _ _ ret = 1 _ _ _ _ _ _ _ stats_on = 0 _ _ _ _ _ _ _ tvb = {tv_sec = 0, tv_usec = 0} _ _ _ _ _ _ _ tve = {tv_sec = 0, tv_usec = 0} _ _ _ _ _ _ _ tz = {tz_minuteswest = 0, tz_dsttime = 0} _ _ _ _ _ _ _ diff = 0 _ _ _ _ _ _ _ inb = {s = 0x555b5f027060 <buf> "SIP/2.0 480 Request Terminated\r\nVia: SIP/2.0/UDP XXX;branch=z9hG4bKe951.40cf95b28fe54d0cbda88a8fa4c91d48.0\r\nVia: SIP/2.0/UDP XXX:5060;branch=z9hG4bK04B95fa49ac99a7fa91\r\nTo: <sip:XXX"..., len = 431} _ _ _ _ _ _ _ netinfo = {data = {s = 0x0, len = 0}, rcv = 0x0, dst = 0x0} _ _ _ _ _ _ _ keng = 0x0 _ _ _ _ _ _ _ evp = {data = 0x7ffc14440df0, rcv = 0x7ffc14440ff0, dst = 0x0} _ _ _ _ _ _ _ cidlockidx = 0 _ _ _ _ _ _ _ cidlockset = 0 _ _ _ _ _ _ _ errsipmsg = 0 _ _ _ _ _ _ _ __func__ = "receive_msg" #4_ 0x0000555b5ea30dc4 in udp_rcv_loop () at core/udp_server.c:541 _ _ _ _ _ _ _ len = 431 _ _ _ _ _ _ _ buf = "SIP/2.0 480 Request Terminated\r\nVia: SIP/2.0/UDP XXX;branch=z9hG4bKe951.40cf95b28fe54d0cbda88a8fa4c91d48.0\r\nVia: SIP/2.0/UDP XXX:5060;branch=z9hG4bK04B95fa49ac99a7fa91\r\nTo: <sip:XXX"... _ _ _ _ _ _ _ tmp = 0x8000000 <error: Cannot access memory at address 0x8000000> _ _ _ _ _ _ _ from = 0x7f10764b1da0 _ _ _ _ _ _ _ fromlen = 16 _ _ _ _ _ _ _ ri = {src_ip = {af = 2, len = 4, u = {addrl = {XXX, XXX}, addr32 = {XXX, XXX, XXX, XXX}, addr16 = {XXX, XXX, XXX, XXX, XXX, XXX, XXX, XXX}, addr = "XXX"}}, dst_ip = { _ _ _ _ _ _ _ _ _ _ _ af = 2, len = 4, u = {addrl = {XXX, 0}, addr32 = {XXX, 0, 0, 0}, addr16 = {XXX, XXX, 0, 0, 0, 0, 0, 0}, addr = "XXX", '\000' <repeats 11 times>}}, src_port = 5060, dst_port = 5060, proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = { _ _ _ _ _ _ _ _ _ _ _ _ _ sa_family = 2, sa_data = "XXX"}, sin = {sin_family = 2, sin_port = 50195, sin_addr = {s_addr = XXX}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 1345864889, _ _ _ _ _ _ _ _ _ _ _ _ _ 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 = 0xXXX, proto = 1 '\001'} _ _ _ _ _ _ _ evp = {data = 0x0, rcv = 0x0, dst = 0x0} _ _ _ _ _ _ _ printbuf = "XXX"... _ _ _ _ _ _ _ i = 1981052368 _ _ _ _ _ _ _ j = 5 _ _ _ _ _ _ _ l = 0 _ _ _ _ _ _ _ __func__ = "udp_rcv_loop" #5_ 0x0000555b5e9c8e32 in main_loop () at main.c:1645 _ _ _ _ _ _ _ i = 4 _ _ _ _ _ _ _ pid = 0 _ _ _ _ _ _ _ si = 0x7f1076130940 _ _ _ _ _ _ _ si_desc = "udp receiver child=4 sock=XXX:5060XXX" _ _ _ _ _ _ _ nrprocs = 8 _ _ _ _ _ _ _ woneinit = 1 _ _ _ _ _ _ _ __func__ = "main_loop" #6_ 0x0000555b5e9d0fdd in main (argc=17, argv=0x7ffc14441698) at main.c:2675 _ _ _ _ _ _ _ cfg_stream = 0x555b5fe5c010 _ _ _ _ _ _ _ c = -1 _ _ _ _ _ _ _ r = 0 _ _ _ _ _ _ _ tmp = 0x7ffc14442f30 "" _ _ _ _ _ _ _ tmp_len = 340006256 _ _ _ _ _ _ _ port = 32764 _ _ _ _ _ _ _ proto = 340006352 _ _ _ _ _ _ _ options = 0x555b5ed33020 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" _ _ _ _ _ _ _ ret = -1 _ _ _ _ _ _ _ seed = 1181662442 _ _ _ _ _ _ _ rfd = 4 _ _ _ _ _ _ _ debug_save = 0 _ _ _ _ _ _ _ debug_flag = 0 _ _ _ _ _ _ _ dont_fork_cnt = 0 _ _ _ _ _ _ _ n_lst = 0x0 _ _ _ _ _ _ _ p = 0xffffffff <error: Cannot access memory at address 0xffffffff> _ _ _ _ _ _ _ st = {st_dev = 19, st_ino = 17502, st_nlink = 2, st_mode = 16832, st_uid = 115, st_gid = 123, __pad0 = 0, st_rdev = 0, st_size = 40, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1547850959, tv_nsec = 183989794}, st_mtim = {tv_sec = 1547851014, _ _ _ _ _ _ _ _ _ _ _ tv_nsec = 719730801}, st_ctim = {tv_sec = 1547851014, tv_nsec = 955611149}, __glibc_reserved = {0, 0, 0}} _ _ _ _ _ _ _ __func__ = "main"

2 20

http_event have errors with exec_avp
by logosvlad＠gmail.com 02 Mar '19

02 Mar '19

Hi there! we have an issue, and it's similar to reported in this thread: http://sip-router.1086192.n5.nabble.com/exec-warning-td165448.html We use kamailio 5.0.6. When we call route from http_event by url reguest (code is below) event_route[xhttp:request] { set_reply_close(); set_reply_no_connect(); if ($(hu{url.path}) ==”update”) { route(DO_SMTH); xhttp_reply("200", "OK”, "", ""); } route[DO_SMTH] { exec_avp(“/usr/bin/who”,”$avp(s:user_)”); } we got errors exec like these: Mar 1 10:51:05 test kamailio[21035]: WARNING: exec [exec_hf.c:464]: append_fixed_vars(): uri not parsed Mar 1 10:51:05 test kamailio[21035]: WARNING: exec [exec_hf.c:482]: append_fixed_vars(): orig URI not parsed Mar 1 10:51:05 test kamailio[21035]: ERROR: exec [../../core/char_msg_val.h:51]: char_msg_val(): can't calculate char_value due to a parsing error Mar 1 10:51:05 test kamailio[21035]: WARNING: exec [exec_hf.c:492]: append_fixed_vars(): no tid can be determined Mar 1 10:51:05 test kamailio[21035]: ERROR: exec [exec_hf.c:504]: append_fixed_vars(): no to-tag But when we call route(DO_SMTH) from request_route - there are no such errors We think that it is something related to the nature of event_routes, anything can be done with this? Should I create an issue on github? thanks for insights and ideas

3 3

Re: [SR-Users] How to Absorb First Leg Re-Invites when no Response from Second Leg Invites
by JR Richardson 02 Mar '19

02 Mar '19

Yes, retransmissions of initial INVITE from Carrier. Makes perfect sense, I understand now. Thanks Gentlemen! JR Reinvites are in-dialog requests; they would only be sent within the context of an established dialog (2xx response, end-to-end ACK, the whole works). Perhaps what you are referring to is not reinvites but retransmissions of the initial INVITE? If so, have a look at this option: https://kamailio.org/docs/modules/5.2.x/modules/tm.html#tm.p.cancel_b_method in concert with something like this: failure_route[...] { if(t_is_canceled()) exit; # The scenario you're after. if(t_branch_timeout()) { t_reply("503", "Service Unavailable"); exit; } } -- Alex

1 0

Is there a option to execute multiple command via JSONRPC or XMLRPC
by Vimalesh S 02 Mar '19

02 Mar '19

Hi, I am looking for a option to execute multiple command via JSONRPCS or XMLRPC. To avoid multiple tCP connections . eg: I have multiple kamailio load balancer server running, need to update the dispatcher record in a single command. Regards, Vimalesh S

1 0

How to Absorb First Leg Re-Invites when no Response from Second Leg Invites
by JR Richardson 02 Mar '19

02 Mar '19

Hi All, My mind is not right on this one, need a pointer. Here is the simple scenario: Carrier><kamailio proxy><end device The end device is a static IP, the proxy dips database and knows where to send numbers destined for the end device, but if there is no response from the end device (it's off-line), how do I time-out the transaction and send a 503 'Service Unavailable' back to the first leg for the carrier to stop re-invites? I assume I need a new [FAIL_TWO] route that handles this event. Thanks. JR -- JR Richardson Engineering for the Masses Chasing the Azeotrope

4 3

kamailio/asterisk no call with sound if use rtpproxy/rtpengine
by PICCORO McKAY Lenz 28 Feb '19

28 Feb '19

i have setup asterisk/rtpproxy/kamailio following the guide in https://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb and later NAT traversal with rtpproxy as i understand in simple we must have: phone/caller-->[-->rtpproxy->kamailio->asterisk->kamailio->rtpproxy -]->phone/dest But when you make a call between two phones, there is no sound... ...to make it work and get sound have to open the ports (range 10000 to 30000 udp) in the asterisk exposing them to the public ip whre its the kamailio and rtpproxy. We configured kamailio with rtpproxy (also tried with rtpengine), and when I configure Asterisk and Kamailio in "real time" mode, everything goes well, the extensions are registered, the authentication is in the asterisk side (table sipusers requires ignore the version check parameter if you use kamailio 5+) etc etc .. but there's no sound, we have: kamailio.bindip="10.10.1.1" desc "kamailio.bindip" kamailio.bindport=5060 desc "kamailio.bindport" asterisk.bindip="10.10.1.2" desc "asterisk.bindip" asterisk.bindport=5060 desc "asterisk.bindport" listen=udp:10.10.1.1:5060 advertise 200.1.1.1:5060 at rtpproxy we have: /usr/bin/rtpproxy -s unix:/var/run/rtpproxy/rtpproxy.sock -u kamailio -p /var/run/rtpproxy/rtpproxy.pid -l 10.10.1.1 -A 200.1.1.1 -F -m 10000 -M 30000 why we need to make asterisk open the ports directly to the publlic ip? N]OTE: the public ip are not a real interface in the kamailio/rtppropxy machine, are provided by the service AWS at amazon! a NAT kind i guess! Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com

2 4

Call Terminatted in Mobile Firefox
by Ravikanth Challa 28 Feb '19

28 Feb '19

Hi All, I got call terminated only in mobile Firefox due to tlsv1 alert unknown ca error. If you have any solution on this please respond on this mail. I added kamailio error logs screen shot [cid:image002.jpg@01D4CF9C.92CE04D0] Thanks, Ravikanth Challa. CONFIDENTIALITY NOTICE: This message (including any attachment) is confidential and may be legally privileged. Access to this message by anyone other than the intended recipient(s) listed above is unauthorized. If you are not the intended recipient you are hereby notified that any disclosure, copying, or distribution of the message, or any action taken or omission of action by you in reliance upon it, is prohibited and may be unlawful. Please immediately notify the sender by reply e-mail and permanently delete all copies of the message if you have received this message in error. This e-mail message including attachment(s), if any, is believed to be free of any virus. However, it is the responsibility of the recipient to ensure that it is virus free and sender accepts no liability for any damage caused by any virus transmitted by this email.

1 0

Kamailio behind NAT or With Public IP - Which one is highly recommended
by Pintu Lohar 28 Feb '19

28 Feb '19

Hi Everyone, Which one among the below option is highly recommended for setting up Kamailio (for production) 1. Kamailio behind NAT *or* 2. Setting up Kamailio using public IP? are there any disadvantages if we setup Kamailio behind NAT and use advertise option in listen parameters? We have tested both the options, and both the options work great for us( a. Kamailio behind NAT with advertising in listen parameters b.Kamailio setup with public IP). So wondering which one is best and highly recommended? Some extra info : 1. We use TLS 2. Using coturn for media Thanks Pintu

7 11

Problem with ghost dialogs
by Cyrille Demaret 28 Feb '19

28 Feb '19

Hi, I'm running Kamailio 5.1.4 and I have some problem with some random dialogs sometimes staying in early state and never ends until I restart Kamailio. According to the init_ts, this dialog is there since 11/01/2019. * Do you have an idea how I can diagnose this problem? * Is there a way to kill these dialogs? I have tried with "dlg.end_dlg" but It seems it's not possible to kill dialogs in early states. { h_entry: 3382 h_id: 4069 call-id: d6e6de79-7d55-486f-889f-01b05c003411 from_uri: sip:0037xxxxxxxxxxx@mydomain.com to_uri: sip:1234@mydomain.com state: 2 start_ts: 0 init_ts: 1547195739 timeout: 0 lifetime: 43200 dflags: 1536 sflags: 0 iflags: 0 caller: { tag: a909d6fa-cee9-44ac-ad76-3697fcd5cb0e contact: sip:asterisk@192.168.102.20:5080;alias=192.168.102.20~5080~1 cseq: 7362 route_set: socket: udp:192.168.102.10:5060 } callee: { tag: contact: cseq: route_set: socket: } profiles: { { caller: sip:0037xxxxxxxxxxx@mydomain.com } { callee: sip:1234@mydomain.com } } variables: { } } Thank you for your help. Best regards, Cyrille

4 7

Dispatcher problem $avp(dsattrs) is null
by jaflong jaflong 28 Feb '19

28 Feb '19

I am doing a ds_select_dst call. I think dispatcher did run because $du gets updated The problem is $(avp(dsattrs)) value is null. Any ideas why?

2 2

Masking Contact Header
by Duarte Rocha 28 Feb '19

28 Feb '19

Greetings, Is there an automated way of masking\encoding\encrypting the Contact header once it goes through a Kamailio proxy and have it restored? I'm using uac_replace_from() and uac_replace_to() for changing these values and having them restored automatically. Is there any tool like this for Contact Header? Cheers

6 9

Local Route blocks
by Grant Bagdasarian 28 Feb '19

28 Feb '19

Hi, I noticed some module functions mention "LOCAL_ROUTE", like the Domain module (http://www.kamailio.org/docs/modules/5.2.x/modules/domain.html#domain.f.loo…). I couldn't find anything related to the LOCAL_ROUTE in the docs. What are these used for and how are these declared and used? Regards, Grant CM.com

2 2

double_rr issues
by Roman Dissauer 28 Feb '19

28 Feb '19

I’m experiencing issues with kamailio 5.1 in multihomed config: two machines, latest debian stretch, latest kamailio 5.1, exactly same config (verified with diff) both machines have an internal and an external network interface. Only thing different is that they are in different datacenters. on one machine everything works perfect, on outgoning calls rr parameters are added perfectly right: Record-Route: <sip:yy.yy.yy.yy;transport=tcp;r2=on;lr;nat=yes> Record-Route: <sip:xx.xx.xx.xx;transport=tcp;r2=on;lr;nat=yes> where yy.yy.yy.yy is the external ip and xx.xx.xx.xx is the internal IP on the other machine I only get: Record-Route: <sip:xx.xx.xx.xx;transport=tcp;lr;nat=yes> even if I set enable_double_rr to 2 I get: Record-Route: <sip:xx.xx.xx.xx;transport=tcp;r2=on;lr;nat=yes> Record-Route: <sip:xx.xx.xx.xx;transport=tcp;r2=on;lr;nat=yes> I already checked with traceroute that the routing to the destination IP Adresses are going through the external interface. maybe someone has a hint for me. Thank you all in advance! Roman

3 3

TLS reload
by Patrick Wakano 27 Feb '19

27 Feb '19

Hi list, I've seen the TLS documentation ( https://www.kamailio.org/docs/modules/5.2.x/modules/tls.html#tls.known_limi…) where it states that TLS specific config reloading is not safe, so for now better don't use it, especially under heavy traffic. This note is there since version 3.0 and in 2013 there was some discussion about it but wthout anything conclusive.... What I would like to know if this is still the case. Is anyone running the TLS reload for certificate renovation for example, or is it better to restart Kamailio? Thanks, Kind regards, Patrick Wakano

4 5

SQlite in memory
by Duarte Rocha 27 Feb '19

27 Feb '19

Greetings, I'm trying to use SQlite as my engine in order to improve performance. I would like to have my Database stored in memory for faster access. I see that Kamailio can open the SQlite database as Read-Only, but i can't find a way to open it in memory. Is this possible using Kamailio? What's the best way to do this? Best Regards, Duarte Rocha

4 11

Dispatcher with parameter use_default=1
by Denys Pozniak 27 Feb '19

27 Feb '19

Hello! I use dispatcher with algorithm=1 (hashing over from URI) with module parameter use_default=1. So I am expecting that last string in dispatcher.list for specific set will be the "last hope" for call routing. dispatcher.list .. 4 sip:10.6.3.122:5060 4 sip:10.6.3.1:5060 4 sip:10.6.3.2:5060 4 sip:10.6.3.3:5060 4 sip:10.6.3.4:5060 4 sip:10.6.3.5:5060 But as I see from logs dispatcher module takes first string as the "last hope": xlog("L_WARN", "TEST-- $(avp(AVP_DST)[0]) $(avp(AVP_DST)[1]) $(avp(AVP_DST)[2]) $(avp(AVP_DST)[3]) $(avp(AVP_DST)[4]) $(avp(AVP_DST)[5]) $(avp(AVP_DST)[6]) \n"); Feb 26 16:11:39 kamailio-2 /usr/sbin/kamailio[28156]: WARNING: <script>: TEST-- sip:10.6.3.4:5060 sip:10.6.3.3:5060 sip:10.6.3.2:5060 sip: 10.6.3.1:5060 sip:10.6.3.5:5060 sip:10.6.3.122:5060 <null> Feb 26 16:11:58 kamailio-2 /usr/sbin/kamailio[28156]: WARNING: <script>: TEST-- sip:10.6.3.3:5060 sip:10.6.3.2:5060 sip:10.6.3.1:5060 sip: 10.6.3.5:5060 sip:10.6.3.4:5060 sip:10.6.3.122:5060 <null> Feb 26 16:11:59 kamailio-2 /usr/sbin/kamailio[28156]: WARNING: <script>: TEST-- sip:10.6.3.2:5060 sip:10.6.3.1:5060 sip:10.6.3.5:5060 sip: 10.6.3.4:5060 sip:10.6.3.3:5060 sip:10.6.3.122:5060 <null> Feb 26 16:12:08 kamailio-2 /usr/sbin/kamailio[28156]: WARNING: <script>: TEST-- sip:10.6.3.1:5060 sip:10.6.3.5:5060 sip:10.6.3.4:5060 sip: 10.6.3.3:5060 sip:10.6.3.2:5060 sip:10.6.3.122:5060 <null> According to the module explanation it should be "the last address in destination set is used as a final option to send the request to" version: kamailio 4.4.2 (x86_64/linux) 892ad6 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, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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: 892ad6 compiled on 12:58:38 Aug 28 2017 with gcc 4.8.5 -- BR, Denys Pozniak

2 4

auth_ephemeral too noisy
by Juha Heinanen 27 Feb '19

27 Feb '19

I did some tests with auth_ephemeral. When timestamp has expired, I get to syslog Feb 23 03:53:05 char /usr/bin/sip-proxy[31758]: WARNING: auth_ephemeral [authorize.c:205]: autheph_verify_timestamp(): username has expired Feb 23 03:53:05 char /usr/bin/sip-proxy[31758]: ERROR: auth_ephemeral [authorize.c:260]: digest_authenticate(): invalid timestamp in username In my opinion, the WARNING is enough and the ERROR message should be removed. ERROR is when an error happens. There is no error here, just an expired timestamp. -- Juha

2 2

Using the avp [*] index with jansson module functions
by Enrico Bandiera 26 Feb '19

26 Feb '19

Hello, I would like to use the [*] index for the avps (to overwrite instead of adding to the stack) when passing the variable to jansson module functions. When trying to do so I get this error: 9(35) ERROR: jansson [jansson_funcs.c:219]: janssonmod_set(): result has json error at line 1: end of file expected near ',' I suppose this is unsupported but maybe I'm doing something wrong, any suggestions? Thanks, Enrico.

1 0

How can I put updated sdp body to message in kemi
by Yuriy Gorlichenko 26 Feb '19

26 Feb '19

Hi. On the original config to set body with New data I used set_body() function, exported from sdpops module. But for kamailio 5.1 I can't find something same in case of using kemi Is There is some additional way to do this?

2 2

bad transport for sips uri?
by David Cunningham 26 Feb '19

26 Feb '19

Hello all, We're having an issue with Kamailio not processing an ACK and hope someone can help. A PCAP shows that Kamailio is receiving the ACK, and we believe these log messages are directly related to it: Feb 21 10:54:01 hostname /sbin/kamailio[15854]: ERROR: tm [ut.h:279]: uri2dst2(): ERROR: uri2dst: bad transport for sips uri: 1 Feb 21 10:54:01 hostname /sbin/kamailio[15854]: ERROR: tm [t_fwd.c:1777]: t_forward_nonack(): ERROR: t_forward_nonack: failure to add branches Feb 21 10:54:01 hostname /sbin/kamailio[15854]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unresolvable destination (478/SL) The ACK is as follows. It's from telephone 111111 which is using TLS, which Kamailio listens for on port 5061. Does anyone know which URI has the bad transport as per the error above? Might it be the From URI "sips:111111@es8.example.com" because it doesn't specify port 5061? Thank you in advance. Session Initiation Protocol (ACK) Request-Line: ACK sips:105@70.42.xx.xx:5070 SIP/2.0 Message Header Via: SIP/2.0/TLS 50.78.yy.yy:5061;branch=z9hG4bK741961203 Route: <sips:70.42.xx.xx:5061;transport=tls;r2=on;lr=on> Route: <sips:70.42.xx.xx;r2=on;lr=on> From: ES8 Test 102 <sips:111111@es8.example.com >;tag=Nf5GG!Orq!MSmGfeu66F03F2114df82b To: <sips:105@es8.example.com:5061>;tag=as7a72b209 Call-ID: 222222(a)50.78.yy.yy CSeq: 94679 ACK Contact: <sips:111111@50.78.yy.yy:5061;transport=tls> Max-Forwards: 70 User-Agent: ewb2bua/15.3.0 Content-Length: 0 -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

3 8

Dialog - Kamailio 5.2
by Nicolas Breuer 25 Feb '19

25 Feb '19

Hello the world, Can you give more informations about the new features of Dialog in K5.2 ? https://www.kamailio.org/w/kamailio-v5-2-0-release-notes/ * ability to load dialog records from database on demand * ability to load dialog records from database if they are not yet in memory cache Indeed in 5.1, restart Kamailio doesn't load the dialog data from database but we can see https://www.kamailio.org/docs/modules/5.1.x/modules/dialog.html#dialog.p.db… there is a function : Set db_skip_load to 1, to skip the loading of dialog data from the database. If on restart, the dialogs are not loaded, what this "db skip load " does ?

2 2

Kamailio with oracle database
by eyas barhouk 25 Feb '19

25 Feb '19

Hello community I'm trying to run kamailio with oracle 11g database and applying the needed querys by using Sqlops modules after applying the needed configuration i didn't find any Syntex to execute Oracle function from kamailio sqlops module . So is there any way to execute oracle function from kamailio ?? Best regards

3 3

Kamailio Module Phonenum
by Nicolas Breuer 25 Feb '19

25 Feb '19

Hello, Trying to find the module phonenum using the Kamailio repository but didn't find it. How can I active this module ? Thanks

2 3

How to easily remove top most header and set destination uri
by YASIN CANER 25 Feb '19

25 Feb '19

Hello, I have trouble with REFER method that has to-tag and Route header , more than one. When it pass loose_route() method , loose_route function remove all route headar then sets RURI with top most Route. Is there a function that removing own route header and sets destination uri ($du) with top most uri. Best Regards. Yasin CANER https://tools.ietf.org/html/rfc3515 2.6<https://tools.ietf.org/html/rfc3515#section-2.6> Behavior of SIP Proxies SIP proxies do not require modification to support the REFER method. Specifically, as required by [1<https://tools.ietf.org/html/rfc3515#ref-1>], a proxy should process a REFER request the same way it processes an OPTIONS request. For example, ---------->mykamailio(a)test2.test----------->>nextroute(a)test3.test------> 1 -- REFER : sip:alice@test.test ... Route:<sip:mykamailio-local@test2.test;lr>,<sip:nextroute@test3.test;lr>,<sip:nextroute2@test4.test> To: <>;tag=asdads From:<>;tag=asd123 --- 2 - After Kamailio Process --- REFER : sip:alice@test.test ... <sip:nextroute@test3.test>,<sip:nextroute2@test4.test> To: <>;tag=asdads From:<>;tag=asd123

2 3

Rows return in sql_xquery()
by Duarte Rocha 25 Feb '19

25 Feb '19

Greetings, If I do a query using sql_query() method I can see the number of rows returned with $dbr(ra=>rows). Is there a return with this info using sql_xquery ? Best Regards, Duarte Rocha

1 0

create own packages for some modules
by Sergey Safarov 22 Feb '19

22 Feb '19

Current kamailio package (checked via RPM) is contains lot of modules. Some of this is not important to include in every kamailio installation. May be create own packages for this modules and other in next 5.3 branch? Modules examples: benchmark.so db_cluster.so db_text.so rtpengine.so rtpproxy.so sipcapture.so siptrace.so sipt.so sms.so smsops.so ss7ops.so https://github.com/kamailio/kamailio/issues/1862

4 6

Is DMQ now the recommended way to do things?
by Canuck . 21 Feb '19

21 Feb '19

Before DMQ there were other ways to do similar things. Is DMQ now considered the best way? Assuming I am using recent stable? Are there any good guides on clustering Kamailio? I am not finding a lot of good info on that subject. Specifically, for multi datacenter active active where things like floating IP's and keepalived are not really an option.

5 7

Not able to connect kamailio via SIP Client
by Prabhat Kumar 21 Feb '19

21 Feb '19

hi, I have setup everything in kamailio and i also added dispatcher in my kamailio config. When i try to login via SIP Client(zoiper) i am getting the following error. Feb 21 11:20:26 ip-10-0-0-121 /usr/local/sbin/kamailio[21131]: INFO: <core> [core/parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP Feb 21 11:20:26 ip-10-0-0-121 /usr/local/sbin/kamailio[21131]: ERROR: <core> [core/parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) Feb 21 11:20:26 ip-10-0-0-121 /usr/local/sbin/kamailio[21131]: ERROR: <core> [core/parser/msg_parser.c:675]: parse_msg(): ERROR: parse_msg: message=<�#007�> Feb 21 11:20:26 ip-10-0-0-121 /usr/local/sbin/kamailio[21131]: ERROR: <core> [core/receive.c:199]: receive_msg(): core parsing of SIP message failed (114.241.140.68:4569/1) How can i fix this problem? Thanks. Prabhat

3 2

Parallel Forking
by Jan-Hendrik Dörner 21 Feb '19

21 Feb '19

Hello, I would like to get parallel forking working on my Kamailio installation, but I have trouble to accomplish that. I am running Kamailio 5.1.4 and follow the example in the tm-module as given in https://www.kamailio.org/docs/modules/5.1.x/modules/tm.html#tm.serial_forki… <https://www.kamailio.org/docs/modules/5.1.x/modules/tm.html#tm.serial_forki…> If I run this example nothing is happening, except that I can see that the „t_on_branch“ is executed when stated, but no calls are routed to the destinations appended. (No phones are actually ringing ...) What am I missing / should do to get actual calls routed? (I am getting the seturi- phone to ring, if I remove the break statement, so that the call can get routed „all the way“.) Is there any working Kamailio example-config, where I can actual see the parallel forking working? Regards Jan-Hendrik

2 1

BUG: Error While installing websocket
by Prabhat Kumar 21 Feb '19

21 Feb '19

I am getting the following error while installing websocket modules in kamailio. make -C src/ install-modules-all make[1]: Entering directory '/usr/local/src/kamailio-5.1/kamailio/src' CC (gcc) [M websocket.so] ws_frame.o ws_frame.c:32:10: fatal error: unistr.h: No such file or directory #include <unistr.h> ^~~~~~~~~~ compilation terminated. ../../Makefile.rules:100: recipe for target 'ws_frame.o' failed make[2]: *** [ws_frame.o] Error 1 Makefile:511: recipe for target 'install-modules' failed make[1]: *** [install-modules] Error 1 make[1]: Leaving directory '/usr/local/src/kamailio-5.1/kamailio/src' Makefile:27: recipe for target 'install-modules-all' failed make: *** [install-modules-all] Error 2 *Is this a bug?? How can i fix this problem?* Thanks,

2 1

Regex issue with subst_body
by Kristijan Vrban 21 Feb '19

21 Feb '19

Hi, in a sdp i need to rewrite a a=sendrecv to a=sendonly but onyl for the for the video stream. I made a regex like this: (?<=m=video)(?s)(.*)(a=sendrecv) Full version here: https://regex101.com/r/rovecJ/1 But if have problems to translate this into kamailio config via subst_body function. I always end with ERROR: fix_actions(): fixing failed (code=-3) Somebody sees the mistake? Kristijan

3 2

Default Modules while installing kamailio
by Prabhat Kumar 21 Feb '19

21 Feb '19

Hi, I am installing kamailio from source on my ubuntu 16.04 server. *How would i know the default modules installing automatically with kamailio?* *Also How can i install all modules(if i want to) with kamailio 5.1?* Thanks, Prabhat Kumar

2 1

kamailio-sipcapture-daemon-config package not found for CentOS7
by Patrick Wakano 20 Feb '19

20 Feb '19

Hello list, I was trying to yum install Kamailio 5.2.1 on a CentOS 7 from the http://download.opensuse.org/repositories/home:/kamailio:/v5.2.x-rpms/CentO… repo, but the kamailio-sipcapture-daemon-config can't be installed because it depends on the kamailio-sipcapture package, which can't be found... Is anyone aware of that? Thank you, Kind regards, Patrick Wakano # yum install kamailio-sipcapture-daemon-config Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.optus.net * epel: mirror.optus.net * extras: mirror.intergrid.com.au * updates: mirror.intergrid.com.au Resolving Dependencies --> Running transaction check ---> Package kamailio-sipcapture-daemon-config.x86_64 0:5.2.1-1.el7.centos will be installed --> Processing Dependency: kamailio-sipcapture = 5.2.1 for package: kamailio-sipcapture-daemon-config-5.2.1-1.el7.centos.x86_64 --> Finished Dependency Resolution Error: Package: kamailio-sipcapture-daemon-config-5.2.1-1.el7.centos.x86_64 (home_kamailio_v5.2.x-rpms) Requires: kamailio-sipcapture = 5.2.1 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest # yum deplist kamailio-sipcapture-daemon-config Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.optus.net * epel: mirror.optus.net * extras: mirror.intergrid.com.au * updates: mirror.intergrid.com.au package: kamailio-sipcapture-daemon-config.x86_64 5.2.1-1.el7.centos dependency: /bin/sh provider: bash.x86_64 4.2.46-31.el7 dependency: kamailio-sipcapture = 5.2.1 Unsatisfied dependency

2 2

Topoh disabling
by Nicolas Breuer 20 Feb '19

20 Feb '19

Hello, Using this event route (see doc) event_route[topoh:msg-outgoing] { if($sndto(ip)=="10.1.1.10") { drop; } } Cause Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16417]: ERROR: <core> [core/parser/parse_via.c:2051]: parse_via(): bad char <´> on state 100 Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16417]: ERROR: <core> [core/parser/parse_via.c:2704]: parse_via(): parsing via on: <´#037#027#015#012X> Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16417]: ERROR: <core> [core/parser/parse_via.c:2710]: parse_via(): via parse error Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16417]: ERROR: topoh [th_msg.c:454]: th_unmask_via(): cannot find cookie in via2 Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16416]: ERROR: <core> [core/parser/parse_via.c:2051]: parse_via(): bad char <´> on state 100 Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16416]: ERROR: <core> [core/parser/parse_via.c:2704]: parse_via(): parsing via on: <´#037#027#015#012X> Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16416]: ERROR: <core> [core/parser/parse_via.c:2710]: parse_via(): via parse error Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16416]: ERROR: topoh [th_msg.c:454]: th_unmask_via(): cannot find cookie in via2 Kamailio 5.1.7

2 2

Kamailio Asterisk Retransmitting problem
by Techinnovation 20 Feb '19

20 Feb '19

Hello, Could you please help me correctly to configure Kamailio with load balancing between two asterisk servers and topology hidding with topoh module. In attach sip trace from kamailio and my config. Currently my problem is that after call UP on Asterisk side, Asterisk send 10 times Retransmitting to <-------------> Retransmitting #5 (no NAT) to 37.148.171.162:5060: SIP/2.0 200 OK Via: SIP/2.0/UDP 37.148.171.162;branch=z9hG4bKf534.157d7d1321019895cc6ba367dd3ae94c.0;received=37.148.171.162 Via: SIP/2.0/UDP 37.148.171.162;branch=z9hG4bKsr-mDYdVEts1x8-yJc91MhEVMtOVMhC6pni1uai1uSAQiytLvyKkMqHB5JsSg98PMYayEyHzESE1gdA6E9C From: "testaccount" <sip:37125511039@213.21.197.50>;tag=as7abbf1f1 To: <sip:100@37.148.171.162:5060>;tag=as143173ac Call-ID: !!:1MeMfMhpfGtgfo6MQu6HfMNH1v-515SC1omDQocT1Efc1MhEVMtOVMhC6pni1uai1uSA CSeq: 102 INVITE Server: Asterisk PBX GIT-master-c83a44c Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Session-Expires: 1800;refresher=uas Contact: <sip:100@37.148.171.164:5060> Content-Type: application/sdp Require: timer Content-Length: 267 v=0 o=root 1502512559 1502512559 IN IP4 37.148.171.164 s=Asterisk PBX GIT-master-c83a44c c=IN IP4 37.148.171.164 t=0 0 m=audio 19658 RTP/AVP 8 101 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=maxptime:150 a=sendrecv And no ACK answer from Kamailio. After 32 sec call drops. I have call flow: Provider 213.21.197.50 -> Kamailio 37.148.171.162 -> Asterisk 37.148.171.163. kamailio -v version: kamailio 5.2.0 (x86_64/linux) 535e13 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, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 535e13 compiled on 01:27:51 Dec 16 2018 with gcc 4.8.5 On Asterisk side I have config [general] language=en maxexpirey=3600 defaultexpirey=3600 bindport=5060 subscribecontext=lab allowsubscribe=yes limitonpeers=yes notifyringing=yes notifyhold=yes disallow=all alwaysauthreject=yes allowguest=no allow=alaw bindaddr=37.148.171.163 t38pt_udptl=yes,redundancy faxdetect=yes directmedia=no rtptimeout=60 rtpholdtimeout=300 [kamailio] type=friend host=37.148.171.162 port=5060 nat=no qualify=no canreinvite=yes insecure=invite context=from-pstn ;directmedia=yes Many thanks ! BR, Alex -- Best regards, Techinnovation mailto:techinnovation@inbox.lv

2 2

Installing and setup of RTP engine on kamailio
by Prabhat Kumar 20 Feb '19

20 Feb '19

Hi, How can i install and setup RTP-Engine on ubuntu server? Regards, Prabhat Kumar

3 3

Gracefully dropping all branches
by Andreas Granig 20 Feb '19

20 Feb '19

Hi all, I’ve a scenario where after lookup() I get multiple branches, and I want to drop some or all of them based on some filter criteria in a branch route before sending requests out. Problem is that if all branches are dropped, kamailio replies with some implicitly generated 500 server error since there are no more branches, but I want to send a 404 or 480 instead. Is there a way to determine if I’m processing the last active branch (so all others have been dropped already), so I can send a graceful reply like 404 or 480 instead of dropping this last branch as well if I decide I have to filter that one too? I’m thinking of a hash table table or something to track and decrease the number of branches for a call, and based on a flag (whether one of the previous branches has been sent out or all have been dropped so far) either drop the last branch or reply with an error. However I’m wondering if kamailio comes with a mechanism to determine the branch state out of the box? Thanks, Andreas

2 2

How to setup Kamailio to dispatch SIP client requests to WebRTC enabled Asterisk
by Adesh Pandey 20 Feb '19

20 Feb '19

Hi Guys, I have recently setup a Kamailio server which can accept SIP or WebSocket connections but voice is not coming in the case of SIP client. I have no idea to change avp in the incoming request, please advise how to proceed.

3 3

Topos and subst_hf
by Igor Olhovskiy 19 Feb '19

19 Feb '19

Hi! I'm using subst_hf to add some extra info to contact subst_hf("Contact", "/^(.*)sip:(.*)@(.*)$/\1sip:encei$var(extra_info)-\2@\3/i", "f"); With combination of topos it's giving me strange results like 2(26) WARNING: sanity [sanity.c:282]: check_ruri_scheme(): failed to parse request uri [sip:encei302e3734-btpsh-5c6c00ac-2e-f@172.28.0.74><sip:encei302e3734-btpsh-5c6c00ac-2e-f@172.28.0.74] Seems, it's doubling R-URI on in-dialog requests. If I'm disabling topos - all is ok. What is interesting - this can't be reproduced with remove_hf/append_hf mechanisms.

1 1

Problem with requests routing when topoh is enabled
by Leonid Fainshtein 19 Feb '19

19 Feb '19

Hi, I have Kamailio 5.1 and I'm using the topology hiding module (topoh) that is configured as the following: modparam("topoh", "mask_key", "...") modparam("topoh", "uparam_name", "....") modparam("topoh", "uri_prefix_checks", 0) Unfortunately Fanvil SIP phone modifies the remote party Contact's URI before it puts it as R-URI in the re-INVITE request. For example, The remote party Contact header: Contact: <sip:127.0.0.8;tr=sr-O2Sdn60d3qrt3otz3o7L.6pF.6mUr6lF3qpd> The re-INVITE request line: INVITE sip:127.0.0.8;tr=sr-O2Sdn60d3qrt3otz3o7L.6pF.6mUr6lF3qpd;user=phone SIP/2.0 As you can see, ";user=phone" was added. As result of that Kamailio tries to send the request to 127.0.0.8. If I disable sending 'user=phone' in Fanvil configuration then everything works well. I assumed that if uri_prefix_checks=0 then the topoh module should take rid of such URI modifications. Am I wrong? Is there any way to solve the problem except to modify the endpoint configuration? Best regards, Leonid Fainshtein

1 0

How can i send presence status from Asterisk 13 to kamailio presence module
by PICCORO McKAY Lenz 19 Feb '19

19 Feb '19

i have followed the guie in https://kb.asipto.com/kamailio:presence:k43-blf and asterisk are working (due we connnect the phones directly to asterisk and works) but when connect the phones to the kamailio the led in phones does not work! ther's some info missing or what? Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com

1 0

Re: [SR-Users] TM Module - Unfortunately error on sending to next hop occurred (477/TM)
by Ilie Soltanici 19 Feb '19

19 Feb '19

Hi, Looks that space comes from copy/paste or page formatting - in the log file there is no space within this variable. Thank's

2 3

Detecting end of DNS failover in tm:branch-failure
by Ivan Ribakov 19 Feb '19

19 Feb '19

Hi all, I have a custom routing logic implemented in my module. This routing logic may return a list of 2 or more endpoints where INVITE should be attempted to be routed. Since endpoint URI can contain domain names, I’m also trying to take care of DNS resolution. Based on the documentation found in https://github.com/kamailio/kamailio/blob/master/doc/tutorials/dns.txt <https://github.com/kamailio/kamailio/blob/master/doc/tutorials/dns.txt> current DNS resolver/failover logic takes good care of RFC3263. To support switching between various endpoints returned by custom routing logic I have been using “tm:branch-failure” routing blocks. Problem I’m facing right now is that I am unable to distinguish between a DNS failover branch failure that has more SRV records to try and the “final” DNS failover branch failure (at which point I should be switching to another endpoint). I’ve tried monitoring $T_reply_code values, but it is “408” in both cases. Any ideas on how “final” and “non-final” DNS failover branch failures can be distinguished? Regards, Ivan

1 0

Re: [SR-Users] Issue with UAC restore_mode when restore_dlg is enabled
by Daniel-Constantin Mierla 19 Feb '19

19 Feb '19

Can you check via rpc and looking at database tables if dialog record is there? Cheers, Daniel On Tue, 19 Feb 2019, 08:44 <jenus(a)cyberchaos.nl wrote: > Daniel, > > Yes the uac_replace_from is called from a branch route. > > Jan > > Daniel-Constantin Mierla schreef op 2019-02-19 08:26: > > I do not recall any relevant changes recently in this part of the code, > > so likely to be same result for 5.2. > > > > With restore_dlg set to 1, dialog variables are used for storing the > > headers. When do you call uac_replace_from()/_to()? Is it in a > > branch_route? > > > > Cheers, > > Daniel > > > > On 19.02.19 08:07, jenus(a)cyberchaos.nl wrote: > >> Forgot to mention, i'm running kamailio 5.1.7, did not test yet with > >> the latest 5.2 release. > >> > >> Jan > >> > >> > >> jenus(a)cyberchaos.nl schreef op 2019-02-18 15:22: > >>> Hello, > >>> > >>> I'm running into a issue with restore_mode auto when i enable > >>> restore_dlg in the uac module. I have a feature where i reroute calls > >>> for a subscriber when it is offline. When routing calls to the > >>> subscriber i check the exit status of "lookup("location")" and > >>> re-route the call. This works fine. It seems to fail when i hit the > >>> failure route (subscriber has a usrloc entry but does not respond). > >>> In > >>> the failure route i append_branch and reroute the call. > >>> > >>> The rerouting works fine, but when i receive the ACK on the 200OK on > >>> the re-routed call the "restore" feature seems to fail and i end up > >>> with a header like: > >>> > >>> To: > >>> <sip:+<null>@voip-dev.domain.nl > >;tag=5B8ABC8A-5C6ABE83000EBF35-AB202700 > >>> in the ACK. > >>> > >>> If i disable restore_dlg feature from the UAC module it adds the > >>> vsf/vst to the Record-Route header and all works fine. > >>> > >>> Do i need to do something special when i create a new branch and use > >>> the restore_dlg feature? > >>> > >>> > >>> Thanks, > >>> > >>> Jan Hazenberg > >>> > >>> _______________________________________________ > >>> Kamailio (SER) - Users Mailing List > >>> sr-users(a)lists.kamailio.org > >>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >> > >> > >> _______________________________________________ > >> Kamailio (SER) - Users Mailing List > >> sr-users(a)lists.kamailio.org > >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >

2 2

Issue with UAC restore_mode when restore_dlg is enabled
by jenus＠cyberchaos.nl 19 Feb '19

19 Feb '19

Hello, I'm running into a issue with restore_mode auto when i enable restore_dlg in the uac module. I have a feature where i reroute calls for a subscriber when it is offline. When routing calls to the subscriber i check the exit status of "lookup("location")" and re-route the call. This works fine. It seems to fail when i hit the failure route (subscriber has a usrloc entry but does not respond). In the failure route i append_branch and reroute the call. The rerouting works fine, but when i receive the ACK on the 200OK on the re-routed call the "restore" feature seems to fail and i end up with a header like: To: <sip:+<null>@voip-dev.domain.nl>;tag=5B8ABC8A-5C6ABE83000EBF35-AB202700 in the ACK. If i disable restore_dlg feature from the UAC module it adds the vsf/vst to the Record-Route header and all works fine. Do i need to do something special when i create a new branch and use the restore_dlg feature? Thanks, Jan Hazenberg

2 3

Presence module with external MWI
by Trevor Peirce 19 Feb '19

19 Feb '19

Hello, Looking for pointers as to what I'm missing here. I'm using the presence module to allow UAs to subscribe to message-summary events. I can see the entries appearing in the active_watchers table and I see subscription renewals increment the cseq columns so I'm satisfied this part is working well. I'm having trouble finding out how to tell Kamailio about a change to the message-summary so that it can notify the watchers. The pua module seems to provide a way but it doesn't seem to work with the subscriptions set up by the presence module. The presence module itself does not seem to offer any RPCs capable of doing this. Appreciate any pointers! Thanks, -- Trevor Peirce AcroVoice Solutions Inc

4 5

Integration with mobile oprators
by sina yazdanian 18 Feb '19

18 Feb '19

Dear Kamailio Technical team I’m Sina from a small software development company in Middle-East. We are interested in your product. For R&D research we need some documents about your product. Your support would be appreciated in case of sharing document. We need document about* SIP server integration with Mobile operator*. I would be grateful if you support me and the team to complete research. Best Regards Sina Yazdanian

2 1

how to see banned address after rule it
by PICCORO McKAY Lenz 18 Feb '19

18 Feb '19

i configure rules for routing banned ip and i want to see where i can autdit this issues.. i mean where i can automatically define a cron setup that grep those logs definitios.. where are loggin those all? my rules are: define at begining of kamailio.cfg "#!WITH_ANTIFLOOD", later add: #!ifdef WITH_ANTIFLOOD loadmodule "htable.so" loadmodule "pike.so" modparam("pike", "sampling_time_unit", 2) modparam("pike", "reqs_density_per_unit", 16) modparam("pike", "remove_latency", 4) modparam("htable", "htable", "ipban=>size=8;autoexpire=300;") #!endif later routing definitions: route[REQINIT] { if(src_ip!=myself) { if($sht(ipban=>$si)!=$null) { xdbg("request from blocked IP - $rm from $fu (IP:$si:$sp)\n"); exit; } if (!pike_check_req()) { xlog("L_ALERT","ALERT: pike blocking $rm from $fu (IP:$si:$sp)\n"); $sht(ipban=>$si) = 1; exit; } } if($ua =~ "friendly-scanner|sipcli|VaxSIPUserAgent") { xlog("L_ALERT","ALERT: friendly canings from $fu (IP:$si:$sp)\n"); exit; } if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; } if(is_method("OPTIONS") && uri==myself && $rU==$null) { sl_send_reply("200","Keepalive"); exit; } if(!sanity_check("1511", "7")) { xlog("Malformed SIP message from $si:$sp\n"); exit; } } Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com

3 3

Dispatcher No destinations available
by Cristian Livadaru 18 Feb '19

18 Feb '19

Hi, I have a Kamailio running as Load Balancer and it works great but since a couple of weeks I kept noticing 404s in Homer and when looked into it they came from Kamailio. ``` route[LOADBALANCE] { #ds_select_dst(destination_set, algorithm) function chooses the destination for the call. For this it can use a lot of algorithms. #Alg. 0 is the default one that does the the choosing over the call ID hash #Alg. 4 is a Round-Robin #Alg. 10 is the one that chooses the destination based on the minimum load of all destinations if(!ds_select_dst("1", "4")) { #if we are here that means no destination is available. We notify the user by 404 and exit the script. xlog("L_NOTICE", "No destination available!"); send_reply("404", "No destination"); exit; } xlog("L_NOTICE", "Routing call to <$ru> via <$du>\n"); #set the no_reply_recieved timeout to 2 second ... adjust the value to your need #note: The first value "0" is invite timeout .. we do not need to change it #This means that is the selected media server fails to respond within 2 seconds the failure_route "MANAGE_FAILURE" is called #note: this implies that ale the signaling from media servers on the way back to the user goes through the proxy as well t_set_fr(0,2000); t_on_failure("MANAGE_FAILURE"); return; } ``` The two asterisks behind it seem fine and I can’t really see why this started happening. Also I thing that returning 404 might be misleading, wouldn’t it be better if I would return 503 instead? I enabled debugging in Kamailio but can’t really seem to notice anything wrong here: ``` Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/udp_server.c:491]: udp_rcv_loop(): received on udp socket: (106/100/1104) [[INVITE sip:431230123@213.137.140.230:5060 SIP/2.0 0D 0A Via: SIP/2.0/UDP 196.27.235.76:5060;branch=z9h]] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:604]: parse_msg(): SIP Request: Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:606]: parse_msg(): method: <INVITE> Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:608]: parse_msg(): uri: <sip:431230123@213.137.140.230:5060> Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:610]: parse_msg(): version: <SIP/2.0> Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK0080827005DD9C0D8E963B2EA293>; state=16 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:492]: parse_headers(): Via found, flags=2 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:494]: parse_headers(): this is the first via Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=10 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:171]: get_hdr_field(): <To> [52]; uri=[sip:431230123@213.137.140.230] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:172]: get_hdr_field(): to body ["431230123" <sip:431230123@213.137.140.230> Feb 15 09:50:28 wlb kamailio[6659]: ] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:152]: get_hdr_field(): cseq <CSeq>: <36825> <INVITE> Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/receive.c:200]: receive_msg(): --- received sip message - request - call-id: [2610e00004f5-5c66843f-6400386f-2c1b8100-6c4782(a)127.0.0.1] - cseq: [36825 INVITE] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/receive.c:248]: receive_msg(): preparing to run routing scripts... Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=0080827005DD9C0D8E96C55CF6CD Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=29 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: siptrace [siptrace.c:507]: sip_trace_store_db(): database connection not initialized Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: siptrace [siptrace_hep.c:498]: pipport2su(): the port string is 5060 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: siptrace [siptrace_hep.c:498]: pipport2su(): the port string is 5060 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/proxy.c:264]: mk_proxy(): doing DNS lookup... Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: siptrace [siptrace_hep.c:302]: trace_send_hep2_duplicate(): setting up the socket_info Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) NOTICE: <script>: Tracing 6(6668) DEBUG: maxfwd [mf_funcs.c:74]: is_maxfwd_present(): value = 70 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:183]: get_hdr_field(): content_length=355 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:89]: get_hdr_field(): found end of header Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: sanity [sanity_mod.c:256]: w_sanity_check(): sanity checks result: 1 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/socket_info.c:559]: grep_sock_info(): checking if host==us: 14==9 && [213.137.140.230] == [127.0.0.1] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/socket_info.c:566]: grep_sock_info(): checking if port 5060 (advertise 0) matches port 5060 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/socket_info.c:559]: grep_sock_info(): checking if host==us: 14==14 && [213.137.140.230] == [213.137.140.230] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/socket_info.c:566]: grep_sock_info(): checking if port 5060 (advertise 0) matches port 5060 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) NOTICE: <script>: OPTIONS from 196.27.235.76:5060 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: siputils [checks.c:120]: has_totag(): no totag Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: tm [t_lookup.c:1018]: t_check_msg(): msg (0x7f7e7edd3be8) id=6845 global id=6844 T start=(nil) Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: tm [t_lookup.c:476]: t_lookup_request(): start searching: hash=29308, isACK=0 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: tm [t_lookup.c:435]: matching_3261(): RFC3261 transaction matching failed Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: tm [t_lookup.c:659]: t_lookup_request(): no transaction found Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: tm [t_lookup.c:1087]: t_check_msg(): msg (0x7f7e7edd3be8) id=6845 global id=6845 T end=(nil) Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: rr [loose.c:1209]: is_direction(): param ftag not found Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: dispatcher [dispatch.c:1832]: ds_select_dst_limit(): set [1] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: dispatcher [dispatch.c:1935]: ds_select_dst_limit(): alg hash [1] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) NOTICE: <script>: No destination available! 6(6668) DEBUG: sl [sl.c:282]: send_reply(): reply in stateless mode (sl) ``` My kamailio.cfg ``` #!KAMAILIO # # sample config file for dispatcher module # - load balancing of VoIP calls with round robin # - no TPC listening # - don't dispatch REGISTER and presence requests # # Kamailio (OpenSER) SIP Server v3.2 # - web: http://www.kamailio.org # - git: http://sip-router.org # # Direct your questions about this file to: sr-users(a)lists.sip-router.org # # Refer to the Core CookBook at http://www.kamailio.org/dokuwiki/doku.php # for an explanation of possible statements, functions and parameters. # # Several features can be enabled using '#!define WITH_FEATURE' directives: # # *** To run in debug mode: # - define WITH_DEBUG # ####### Global Parameters ######### #!define WITH_HOMER #!define WITH_DEBUG #!ifdef WITH_DEBUG debug=4 log_stderror=yes #!else debug=2 log_stderror=no #!endif memdbg=5 memlog=5 log_facility=LOG_LOCAL0 fork=yes children=4 /* comment the next line to enable TCP */ disable_tcp=yes /* uncomment the next line to disable the auto discovery of local aliases based on revers DNS on IPs (default on) */ auto_aliases=yes /* add local domain aliases */ port=5060 /* uncomment and configure the following line if you want Kamailio to bind on a specific interface/port/proto (default bind on all available) */ # listen=udp:127.0.0.1:5060 sip_warning=no ####### Modules Section ######## #set module path mpath="/usr/lib/x86_64-linux-gnu/kamailio/modules/" # loadmodule "db_mysql.so" # loadmodule "mi_fifo.so" loadmodule "jsonrpcs.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 "acc.so" loadmodule "counters.so" loadmodule "dispatcher.so" #!ifdef WITH_HOMER loadmodule "siptrace.so" #!endif #loadmodule "kex.so" #loadmodule "tm.so" #loadmodule "tmx.so" #loadmodule "sl.so" #loadmodule "rr.so" #loadmodule "pv.so" #loadmodule "maxfwd.so" #loadmodule "textops.so" #loadmodule "siputils.so" #loadmodule "xlog.so" #loadmodule "sanity.so" ## loadmodule "ctl.so" #loadmodule "mi_rpc.so" #loadmodule "acc.so" # ----- acc params ----- modparam("acc", "log_flag", 1) modparam("acc", "failed_transaction_flag", 3) modparam("acc", "log_extra", "src_user=$fU;src_domain=$fd;dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;src_ip=$si") #!ifdef WITH_HOMER # check IP and port of your capture node modparam("siptrace", "duplicate_uri", "sip:213.136.47.31:9060") modparam("siptrace", "hep_mode_on", 1) modparam("siptrace", "trace_to_database", 0) modparam("siptrace", "trace_flag", 22) modparam("siptrace", "trace_on", 1) #!endif # ----------------- setting module-specific parameters --------------- # modparam("dispatcher", "db_url", DBURL) modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "flags", 2) modparam("dispatcher", "dst_avp", "$avp(AVP_DST)") modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)") modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)") modparam("dispatcher", "sock_avp", "$avp(dssocket)") modparam("dispatcher", "attrs_avp", "$avp(dsattrs)") #set next two parameters if you want to enable balance alg. no. 10 #modparam("dispatcher", "dstid_avp", "$avp(dsdstid)") #modparam("dispatcher", "ds_hash_size", 8) modparam("dispatcher", "ds_ping_interval", 20) modparam("dispatcher", "ds_ping_from", "sip:kamailio@example.com") #modparam("dispatcher", "ds_ping_method", "INFO") modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_probing_threshold", 1) #configure codes or classes of SIP replies to list only allowed replies (i.e. when temporarily unavailable=480) modparam("dispatcher", "ds_ping_reply_codes", "class=2;code=480;code=404") ####### Routing Logic ######## # main request routing logic route { #!ifdef WITH_HOMER #start duplicate the SIP message now sip_trace(); setflag(22); xlog("L_NOTICE","Tracing"); #!endif # per request initial checks route(REQINIT); # handle requests within SIP dialogs route(WITHINDLG); # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) t_relay(); exit; } t_check_trans(); # record routing for dialog forming requests (in case they are routed) # - remove preloaded route headers remove_hf("Route"); if (is_method("INVITE|SUBSCRIBE")) record_route(); #if (is_method("INVITE")) #{ # ds_select_domain("1","4"); # #sl_send_reply("300","Redirect"); # #t_relay(); # exit; #} # account only INVITEs if (is_method("INVITE")) { setflag(1); # do accounting } # handle presence related requests route(PRESENCE); # handle registrations route(REGISTRAR); if ($rU==$null) { # request with no Username in RURI sl_send_reply("484","Address Incomplete"); exit; } route(LOADBALANCE); route(RELAY); } # Per SIP request initial checks route[REQINIT] { if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; } if(!sanity_check("1511", "7")) { xlog("Malformed SIP message from $si:$sp\n"); exit; } # Reply to options if (uri==myself) { xlog("L_NOTICE","OPTIONS from $si:$sp\n"); if ((method==OPTIONS) && (! uri=~"sip:.*[@]+.*")) { xlog("L_NOTICE","answering options $si:$sp\n"); options_reply(); } } } # Handle requests within SIP dialogs route[WITHINDLG] { if (has_totag()) { # sequential request withing a dialog should # take the path determined by record-routing if (loose_route()) { if (is_method("BYE")) { setflag(1); # do accounting ... setflag(3); # ... even if the transaction fails } route(RELAY); } else { if (is_method("SUBSCRIBE") && uri == myself) { # in-dialog subscribe requests route(PRESENCE); exit; } if ( is_method("ACK") ) { if ( t_check_trans() ) { # non loose-route, but stateful ACK; # must be ACK after a 487 or e.g. 404 from upstream server t_relay(); exit; } else { # ACK without matching transaction ... ignore and discard. exit; } } sl_send_reply("404","Not here"); } exit; } } # Handle SIP registrations route[REGISTRAR] { if(!is_method("REGISTER")) return; #sl_send_reply("404", "No registrar"); #t_relay(); if(!ds_select_dst("1", "4")) { sl_send_reply("404", "No registrar"); exit; } forward(); exit; } # Presence server route route[PRESENCE] { if(!is_method("PUBLISH|SUBSCRIBE")) return; sl_send_reply("404", "Not here"); exit; } route[LOADBALANCE] { #ds_select_dst(destination_set, algorithm) function chooses the destination for the call. For this it can use a lot of algorithms. #Alg. 0 is the default one that does the the choosing over the call ID hash #Alg. 4 is a Round-Robin #Alg. 10 is the one that chooses the destination based on the minimum load of all destinations if(!ds_select_dst("1", "4")) { #if we are here that means no destination is available. We notify the user by 404 and exit the script. xlog("L_NOTICE", "No destination available!"); send_reply("404", "No destination"); exit; } xlog("L_NOTICE", "Routing call to <$ru> via <$du>\n"); #set the no_reply_recieved timeout to 2 second ... adjust the value to your need #note: The first value "0" is invite timeout .. we do not need to change it #This means that is the selected media server fails to respond within 2 seconds the failure_route "MANAGE_FAILURE" is called #note: this implies that ale the signaling from media servers on the way back to the user goes through the proxy as well t_set_fr(0,2000); t_on_failure("MANAGE_FAILURE"); return; } # manage failure routing cases failure_route[MANAGE_FAILURE] { # route(NATMANAGE); if (t_is_canceled()) { exit; } xlog("L_NOTICE", "Media server $du failed to answer, selecting other one!"); # next DST - only for 500 reply or local timeout (set by t_set_fr()) if (t_check_status("500") || t_branch_timeout() || !t_branch_replied()) { #we mark the destination Inactive and Probing ds_mark_dst("ip"); #select the new destination if(ds_next_dst()) { #again set local timeout for reply t_set_fr(0,2000); t_on_failure("MANAGE_FAILURE"); route(RELAY); exit; } else { #last available node failed to reply, no other destinations available send_reply("404", "No destination"); exit; } } } route[RELAY] { xlog("L_NOTICE", "going to <$ru> via <$du>"); if (!t_relay()) { sl_reply_error(); } exit; } ``` and my dispatcher.list ``` # line format # id(int,auto) setid(int) destination(string) flags(int) priority(int) attrs(string) description(string) 1 sip:196.27.235.76:5060 1 sip:213.137.140.230:5060 ``` any help to understand these issues would be greatly appreciated. Cris --- Cristian Livadaru LcX IT Solutions Web: http://lcx.at/ Tel: +43 1 37 37 37 Fax: +43 1 37 37 37 - 25 **24/7 Support: 0900 474 455** (1,81€/Min)

2 3

Info: Kamailio World 2019 - First group of speakers
by Daniel-Constantin Mierla 18 Feb '19

18 Feb '19

Hello, a short note to let everybody know that we have published the details for the first group of speakers at Kamailio World 2019 (May 6-8, in Berlin) - you can read more about at: * https://www.kamailioworld.com/k07/2019/02/kamailio-world-2019-first-group-o… * https://www.kamailioworld.com/k07/speakers/ The target is to finish the review of the speaking proposals by end of the month, then start working on the schedule. We received a lot more than it can be accommodated, but we will try to select all that are very interesting by having several short sessions/lightning talks. There will be few new concepts, trying to engage more the participants as well as use better the evening time for social networking with a boat trip at the end of first day, in addition to the cocktail party on the second day. Hoping to meet many of you in Berlin at Kamailio World 2019! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

1 0

Branches Routes
by Nicolas Breuer 18 Feb '19

18 Feb '19

Hello, We have a main route where we try multiple destinations (SIP Providers) one by one in case of failure. We modify the $ru in branch routes. I have to manipulate the $rU in the main route (adding 000 and strip 000) to create the second branch. Otherwise I have an error in Kamailio , is it expected ?? Feb 16 10:29:13 proxy2 /usr/sbin/kamailio[3837]: NOTICE: RU => 0003280033800 (Branch 0) * Adding 000 in main route Feb 16 10:29:13 proxy2 /usr/sbin/kamailio[3837]: NOTICE: RU => 3280033800 (Branch 0) * Strip "000" in main route * Timeout of first provider (going to main route again with an other branch) Feb 16 10:29:15 proxy2 /usr/sbin/kamailio[3840]: NOTICE: RU => 0003280033800 (Branch 1) Feb 16 10:29:15 proxy2 /usr/sbin/kamailio[3840]: NOTICE: RU => 3280033800 (Branch 1) * Call OK I will now remove the prefix & strip command in main route Feb 16 10:32:11 proxy2 /usr/sbin/kamailio[3951]: NOTICE: RU => 3280033800 (Branch 0) Feb 16 10:32:11 proxy2 /usr/sbin/kamailio[3951]: NOTICE: RU => 3280033800 (Branch 0) Feb 16 10:32:11 proxy2 /usr/sbin/kamailio[3951]: NOTICE: Branch to sip:3280033800@XXXXXXXXXXX * Timeout Feb 16 10:32:13 proxy2 /usr/sbin/kamailio[3955]: NOTICE: RU => 3280033800 (Branch 1) Feb 16 10:32:13 proxy2 /usr/sbin/kamailio[3955]: NOTICE: RU => 3280033800 (Branch 1) Feb 16 10:32:13 proxy2 /usr/sbin/kamailio[3955]: ERROR: tm [t_fwd.c:1728]: t_forward_nonack(): no branches for forwarding Feb 16 10:32:13 proxy2 /usr/sbin/kamailio[3955]: ERROR: tm [tm.c:1548]: _w_t_relay_to(): t_forward_noack failed Feb 16 10:32:13 proxy2 /usr/sbin/kamailio[3955]: ERROR: sl [sl_funcs.c:362]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (6/SL) Any suggestions ?

3 4

kamailio with oracle database
by eyas barhouk 17 Feb '19

17 Feb '19

hello dears i'm trying to run kamailio 5.1.7 with Oracle database and after building it from source with the needed module and installing Oracle Instant Client when i'm trying to run kamailio i get the following Error : ERROR: <core> [core/sr_module.c:498]: load_module(): could not open module </usr/local/lib64/kamailio/modules/db_oracle.so>: libclntsh.so.12.1: cannot open shared object file: No such file or directory so is there any way to make the libclntsh.so.12.1 open shared object ?? best regards Eyas

2 2

Re. SRTP configuration Rtpengine
by vinod mn 16 Feb '19

16 Feb '19

Hi I am not able to do SRTP configuration properly this the kamailio configuration *route[NATMANAGE] {* *rtpengine_manage("replace-origin replace-session-connection RTP/SAVP");}* I can see in SDP RTP/SAVP but still the packets are RTP. clients used linphone-android (media-encryption is SRTP ) and 3cx-windows-client

2 1

Log/Alerts Volume
by Daniel Greenwald 15 Feb '19

15 Feb '19

Curious how other folks are dealing with the volume of logs that Kamailio generates. We are currently sending them to syslog and alerting on WARN and above but the amount of alert noise is unbearable. For example (there are many variations): ERROR: <core> [core/tcp_read.c:297]: tcp_read_data(): error reading: Connection reset by peer INVITE:WARNING: sanity [sanity.c:776]: check_parse_uris(): failed to parse >From header INVITE:ERROR: <core> [core/parser/parse_from.c:75]: parse_from_header(): b ad From header The fact that these are WARN/ERROR level and from core makes me wonder how we can possibly make alerts relevant. Any input would be appreciated. Thanks, Daniel G

3 3

Memory allocator was called from cdp: diameter_avp.c:365
by Denys Pozniak 15 Feb '19

15 Feb '19

Hello! I have faced with Kamailio (5.1.7) crashes, probably it is connected to cdp module, please check the source of issue: 14(5649) INFO: cdp [receiver.c:455]: receiver_process(): receiver_process(): [diameter1.dev] Receiver process doing init on new process... 14(5649) INFO: cdp [receiver.c:188]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [diameter1.dev] 14(5649) INFO: cdp [receiver.c:460]: receiver_process(): receiver_process(): [diameter1.dev] Receiver process starting up... 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: -1 Recv.State: 0 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: -1 Recv.State: 0 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 16(5651) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 16 rank 1001: cdp [cdp_timer] 16(5651) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 16 rank 1001: cdp_avp [cdp_timer] 16(5651) DEBUG: cdp_avp [cdp_avp_mod.c:211]: cdp_avp_child_init(): Initializing child in module cdp_avp for rank [1001] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: acc [cdp_acceptor] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: uac [cdp_acceptor] 16(5651) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 16 rank 1001: ims_charging [cdp_timer] 16(5651) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 16 rank 1001: ims_dialog [cdp_timer] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: htable [cdp_acceptor] 15(5650) DEBUG: htable [htable.c:236]: child_init(): rank is (1000) 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: carrierroute [cdp_acceptor] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: dispatcher [cdp_acceptor] 16(5651) INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: cdp [cdp_acceptor] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: cdp_avp [cdp_acceptor] 15(5650) DEBUG: cdp_avp [cdp_avp_mod.c:211]: cdp_avp_child_init(): Initializing child in module cdp_avp for rank [1000] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: ims_charging [cdp_acceptor] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: ims_dialog [cdp_acceptor] 15(5650) INFO: cdp [acceptor.c:81]: acceptor_process(): Acceptor process starting up... 15(5650) DEBUG: cdp [tcp_accept.c:114]: create_socket(): create_sockets: create socket and bind for IPv4... 15(5650) WARNING: cdp [tcp_accept.c:121]: create_socket(): create_socket(): Trying to open/bind/listen on 10.10.10.10 port 38680 15(5650) WARNING: cdp [tcp_accept.c:146]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.10.10.10 port 38680 15(5650) INFO: cdp [acceptor.c:95]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... [root@10-10-10-10 kamailio]# 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: kex [tcp main process] 17(5652) DEBUG: kex [kex_mod.c:157]: child_init(): rank is (-4) 17(5652) DEBUG: <core> [sruid.c:106]: sruid_init(): root for sruid is [srid-5c658bbb-1614-] (0 / 19) 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: corex [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: tm [tcp main process] 17(5652) DEBUG: tm [callid.c:137]: child_init_callid(): callid: ' 46ac84cd57961b27-5652(a)10.10.10.10' 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: tmx [tcp main process] 17(5652) DEBUG: tmx [tmx_mod.c:261]: child_init(): rank is (-4) 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: sl [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: usrloc [tcp main process] 17(5652) DEBUG: <core> [sruid.c:106]: sruid_init(): root for sruid is [ulcx-5c658bbb-1614-] (0 / 19) 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: registrar [tcp main process] 17(5652) DEBUG: <core> [sruid.c:106]: sruid_init(): root for sruid is [uloc-5c658bbb-1614-] (0 / 19) 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: ctl [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: acc [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: uac [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: htable [tcp main process] 17(5652) DEBUG: htable [htable.c:236]: child_init(): rank is (-4) 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: carrierroute [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: dispatcher [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: cdp [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: cdp_avp [tcp main process] 17(5652) DEBUG: cdp_avp [cdp_avp_mod.c:211]: cdp_avp_child_init(): Initializing child in module cdp_avp for rank [-4] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: ims_charging [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: ims_dialog [tcp main process] 17(5652) DEBUG: <core> [core/local_timer.c:61]: init_local_timer(): timer_list between 0xa6e0a8 and 0xab20a8 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 7, 4, 0x7fbdd97d7bec), fd_no=0 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 8, 4, 0x7fbdd97d7c78), fd_no=1 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 9, 4, 0x7fbdd97d7d04), fd_no=2 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 10, 4, 0x7fbdd97d7d90), fd_no=3 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 11, 4, 0x7fbdd97d7e1c), fd_no=4 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 12, 4, 0x7fbdd97d7ea8), fd_no=5 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 13, 4, 0x7fbdd97d7f34), fd_no=6 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 15, 4, 0x7fbdd97d7fc0), fd_no=7 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 4, 4, 0x7fbdd97d804c), fd_no=8 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 16, 4, 0x7fbdd97d80d8), fd_no=9 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 17, 4, 0x7fbdd97d8164), fd_no=10 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 18, 4, 0x7fbdd97d81f0), fd_no=11 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 23, 4, 0x7fbdd97d827c), fd_no=12 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 24, 4, 0x7fbdd97d8308), fd_no=13 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 25, 4, 0x7fbdd97d8394), fd_no=14 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 26, 4, 0x7fbdd97d8420), fd_no=15 5(5640) DEBUG: ims_charging [ro_timer.c:252]: ro_timer_routine(): getting expired ro-sessions 5(5640) DEBUG: ims_charging [ro_timer.c:211]: get_expired_ro_sessions(): my ticks are [32829471] 13(5648) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp receiver peer unknown Serviced Peers: --- 13(5648) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 16(5651) DEBUG: cdp [peermanager.c:263]: peer_timer(): peer_timer(): taking care of peers... 16(5651) DEBUG: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer diameter1.dev State 0 16(5651) DEBUG: cdp [peerstatemachine.c:90]: sm_process(): sm_process(): Peer diameter1.dev State Closed Event Start 16(5651) INFO: cdp [peerstatemachine.c:525]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer diameter1.dev 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: -1 Recv.State: 0 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 16(5651) INFO: cdp [receiver.c:875]: peer_connect(): peer_connect(): Trying to connect to 10.10.10.20 port 3868 16(5651) INFO: cdp [receiver.c:954]: peer_connect(): peer_connect(): Peer diameter1.dev:3868 connected 14(5649) DEBUG: cdp [receiver.c:702]: receive_loop(): select_recv(): There is something on the fd exchange pipe 14(5649) DEBUG: cdp [receiver.c:711]: receive_loop(): select_recv(): fd exchange pipe says fd [8] for peer 0x7fbdd979e368:[diameter1.dev] 14(5649) DEBUG: cdp [peerstatemachine.c:90]: sm_process(): sm_process(): Peer diameter1.dev State Wait_Conn_Ack Event I_Rcv_Conn_Ack 14(5649) DEBUG: cdp [diameter_msg.c:184]: AAANewMessage(): AAANewMessage: param session received null and it's a request!! 14(5649) ERROR: cdp [peerstatemachine.c:634]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket 14(5649) DEBUG: cdp [diameter_msg.c:81]: AAABuildMsgBuffer(): AAABuildMsgBuffer(): len=184 14(5649) DEBUG: cdp [receiver.c:1013]: peer_send_msg(): peer_send_msg(): Pipe push [0x7fbdd97e0788] 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: 8 Recv.State: 0 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 14(5649) DEBUG: cdp [receiver.c:756]: receive_loop(): select_recv(): There is something on the send pipe 14(5649) DEBUG: cdp [receiver.c:769]: receive_loop(): select_recv(): Send pipe says [0x7fbdd97e0788] 8 14(5649) DEBUG: cdp [diameter_msg.c:410]: AAAFreeMessage(): AAAFreeMessage: Freeing message (0x7fbdd97e0788) 257 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: 8 Recv.State: 0 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 16(5651) DEBUG: cdp [peermanager.c:143]: log_peer_list(): --- Peer List: --- 16(5651) DEBUG: cdp [peermanager.c:145]: log_peer_list(): State of peer: Wait_I_CEA FQDN: diameter1.dev Port: 3868 Is dynamic 16(5651) DEBUG: cdp [peermanager.c:149]: log_peer_list(): ------------------ 16(5651) DEBUG: cdp [session.c:396]: cdp_sessions_log(): ------- CDP Sessions ---------------- 16(5651) DEBUG: cdp [session.c:431]: cdp_sessions_log(): ------------------------------------- 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: 8 Recv.State: 1 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 14(5649) DEBUG: cdp [receiver.c:579]: do_receive(): receive_loop(): [diameter1.dev] Recv Version 1 Length 172 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: 8 Recv.State: 2 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 14(5649) DEBUG: cdp [receiver.c:1107]: receive_message(): receive_message(): [diameter1.dev] Recv msg 257 14(5649) DEBUG: cdp [peerstatemachine.c:90]: sm_process(): sm_process(): Peer diameter1.dev State Wait_I_CEA Event I_Rcv_CEA 14(5649) DEBUG: cdp [peerstatemachine.c:698]: count_Supported_Vendor_Id_AVPS(): Found 1 Supported_Vendor AVPS14(5649) DEBUG: cdp [peerstatemachine.c:681]: add_peer_application(): Application 0 of maximum 1 14(5649) DEBUG: cdp [peerstatemachine.c:750]: save_peer_applications(): Found Supported Vendor for Application 0: 10415 14(5649) DEBUG: cdp [peerstatemachine.c:681]: add_peer_application(): Application 1 of maximum 1 14(5649) DEBUG: cdp [diameter_msg.c:410]: AAAFreeMessage(): AAAFreeMessage: Freeing message (0x7fbdd97e0788) 257 14(5649) CRITICAL: <core> [core/mem/q_malloc.c:149]: qm_debug_check_frag(): BUG: qm: prev. fragm. tail overwritten(28af, abcdefed)[0x7fbdd97e0c98:0x7fbdd97e0cd0]! Memory allocator was called from cdp: diameter_avp.c:365. Fragment marked by cdp: diameter_avp.c:142. Exec from core/mem/q_malloc.c:504. 5(5640) DEBUG: ims_charging [ro_timer.c:252]: ro_timer_routine(): getting expired ro-sessions 5(5640) DEBUG: ims_charging [ro_timer.c:211]: get_expired_ro_sessions(): my ticks are [32829472] 13(5648) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp receiver peer unknown Serviced Peers: --- 13(5648) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 15(5650) DEBUG: cdp [tcp_accept.c:221]: accept_loop(): accept_loop(): No connection attempts 5(5640) DEBUG: ims_charging [ro_timer.c:252]: ro_timer_routine(): getting expired ro-sessions 5(5640) DEBUG: ims_charging [ro_timer.c:211]: get_expired_ro_sessions(): my ticks are [32829473] 13(5648) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp receiver peer unknown Serviced Peers: --- 13(5648) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 17(5652) CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 24 17(5652) DEBUG: <core> [core/tcp_main.c:3513]: handle_ser_child(): dead child 14, pid 5649 (shutting down?) 17(5652) DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xa6dee0, 24, -1, 0x0) fd_no=16 called 0(5635) ALERT: <core> [main.c:739]: handle_sigs(): child process 5649 exited by a signal 6 0(5635) ALERT: <core> [main.c:742]: handle_sigs(): core was generated 0(5635) INFO: <core> [main.c:764]: handle_sigs(): terminating due to SIGCHLD 0(5635) DEBUG: <core> [main.c:766]: handle_sigs(): terminating due to SIGCHLD 16(5651) INFO: <core> [main.c:819]: sig_usr(): signal 15 received GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-114.el7 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html > This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/sbin/kamailio...Reading symbols from /usr/lib/debug/usr/sbin/kamailio.debug...done. done. [New LWP 5649] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `kamailio -f kamailio.cfg -E'. Program terminated with signal 6, Aborted. #0 0x00007fbde6015207 in raise () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install glibc-2.17-260.el7_6.3.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-37.el7_6.x86_64 libcom_err-1.42.9-13.el7.x86_64 libgcc-4.8.5-36.el7.x86_64 libselinux-2.5-14.1.el7.x86_64 libstdc++-4.8.5-36.el7.x86_64 libxml2-2.9.1-6.el7_2.3.x86_64 mariadb-libs-5.5.60-1.el7_5.x86_64 openssl-libs-1.0.2k-16.el7.x86_64 pcre-8.32-17.el7.x86_64 xz-libs-5.2.2-1.el7.x86_64 zlib-1.2.7-18.el7.x86_64 (gdb) bt full #0 0x00007fbde6015207 in raise () from /lib64/libc.so.6 No symbol table info available. #1 0x00007fbde60168f8 in abort () from /lib64/libc.so.6 No symbol table info available. #2 0x0000000000673469 in qm_debug_check_frag (qm=0x7fbdd94fd000, f=0x7fbdd97e0c98, file=0x7fbdde6bb992 "cdp: diameter_avp.c", line=365, efile=0x7dc6b7 "core/mem/q_malloc.c", eline=504) at core/mem/q_malloc.c:151 __FUNCTION__ = "qm_debug_check_frag" #3 0x00000000006765ec in qm_free (qmp=0x7fbdd94fd000, p=0x7fbdd97e0cd0, file=0x7fbdde6bb992 "cdp: diameter_avp.c", func=0x7fbdde6bd478 <__FUNCTION__.7016> "AAAFreeAVP", line=365, mname=0x7fbdde6bb7c0 "cdp") at core/mem/q_malloc.c:504 qm = 0x7fbdd94fd000 f = 0x7fbdd97e0c98 size = 140730526467984 next = 0x7a8db8 prev = 0x7a8db8 __FUNCTION__ = "qm_free" #4 0x0000000000680148 in qm_shm_free (qmp=0x7fbdd94fd000, p=0x7fbdd97e0cd0, file=0x7fbdde6bb992 "cdp: diameter_avp.c", func=0x7fbdde6bd478 <__FUNCTION__.7016> "AAAFreeAVP", line=365, mname=0x7fbdde6bb7c0 "cdp") at core/mem/q_malloc.c:1268 No locals. #5 0x00007fbdde696e61 in AAAFreeAVP (avp=0x7ffe610a0860) at diameter_avp.c:365 __FUNCTION__ = "AAAFreeAVP" #6 0x00007fbdde65c88f in AAAFreeAVPList (avpList=0x7fbdd97e07d8) at diameter_msg.c:396 avp_t = 0x7fbdd97e0cd0 avp = 0x7fbdd97e0bb8 #7 0x00007fbdde65cc4c in AAAFreeMessage (msg=0x7ffe610a0910) at diameter_msg.c:416 __FUNCTION__ = "AAAFreeMessage" #8 0x00007fbdde63f05e in Process_CEA (p=0x7fbdd979e368, cea=0x7fbdd97e0788) at peerstatemachine.c:804 avp = 0x7fbdd97e10b0 #9 0x00007fbdde638223 in sm_process (p=0x7fbdd979e368, event=I_Rcv_CEA, msg=0x7fbdd97e0788, peer_locked=0, sock=8) at peerstatemachine.c:166 result_code = -563425872 next_event = 32701 msg_received = 0 __FUNCTION__ = "sm_process" #10 0x00007fbdde6874be in receive_message (msg=0x7fbdd97e0788, sp=0x7fbde59538b0) at receiver.c:1147 avp1 = 0xde6b2c50 avp2 = 0x7fbdd97e0990 __FUNCTION__ = "receive_message" #11 0x00007fbdde67c5bb in do_receive (sp=0x7fbde59538b0) at receiver.c:598 cnt = 152 n = 152 version = 1 dst = 0x7fbdd97e1164 "" dmsg = 0x7fbdd97e0788 __FUNCTION__ = "do_receive" #12 0x00007fbdde68038e in receive_loop (original_peer=0x7fbdd979e368) at receiver.c:805 rfds = {__fds_bits = {256, 0 <repeats 15 times>}} efds = {__fds_bits = {0 <repeats 16 times>}} tv = {tv_sec = 0, tv_usec = 999998} n = 1 max = 21 cnt = 1 msg = 0x0 sp = 0x7fbde59538b0 sp2 = 0x7fbde59538b0 p = 0x7fbdd979e368 fd = 8 fd_exchange_pipe_local = 21 __FUNCTION__ = "receive_loop" #13 0x00007fbdde679aec in receiver_process (p=0x7fbdd979e368) at receiver.c:464 ---Type <return> to continue, or q <return> to quit--- __FUNCTION__ = "receiver_process" #14 0x00007fbdde62a7d5 in diameter_peer_start (blocking=0) at diameter_peer.c:289 pid = 0 k = -1 p = 0x7fbdd979e368 __FUNCTION__ = "diameter_peer_start" #15 0x00007fbdde61c9a8 in cdp_child_init (rank=0) at cdp_mod.c:243 __FUNCTION__ = "cdp_child_init" #16 0x000000000053b6b1 in init_mod_child (m=0x7fbde5885150, rank=0) at core/sr_module.c:943 __FUNCTION__ = "init_mod_child" #17 0x000000000053b353 in init_mod_child (m=0x7fbde5885dc8, rank=0) at core/sr_module.c:939 __FUNCTION__ = "init_mod_child" #18 0x000000000053b353 in init_mod_child (m=0x7fbde5886190, rank=0) at core/sr_module.c:939 __FUNCTION__ = "init_mod_child" #19 0x000000000053b353 in init_mod_child (m=0x7fbde58865d0, rank=0) at core/sr_module.c:939 __FUNCTION__ = "init_mod_child" #20 0x000000000053ba85 in init_child (rank=0) at core/sr_module.c:970 No locals. #21 0x0000000000424fe5 in main_loop () at main.c:1701 i = 4 pid = 5641 si = 0x0 si_desc = "udp receiver child=3 sock=10.10.10.10:5060\000\275\177\000\000\300\023\na\376\177\000\000\022\000\000\000\000\000\000\000\000\000\000\004\000\000\000\000\000\000\200\000\000\000\000\000\263\215z", '\000' <repeats 13 times>, "\220\026\na\376\177\000\000\207\"\003\346\275\177\000\000\260yw\000\000\000\000\000\060;\223\345\275\177\000" nrprocs = 4 woneinit = 1 __FUNCTION__ = "main_loop" #22 0x000000000042b994 in main (argc=4, argv=0x7ffe610a1778) at main.c:2642 cfg_stream = 0x103a020 c = -1 r = 0 tmp = 0x0 tmp_len = 0 port = 0 proto = 0 options = 0x758c10 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 1364069336 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x0 p = 0x0 st = {st_dev = 19, st_ino = 68292, st_nlink = 2, st_mode = 16832, st_uid = 995, st_gid = 994, __pad0 = 0, st_rdev = 0, st_size = 40, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1550156643, tv_nsec = 630000000}, st_mtim = {tv_sec = 1550158563, tv_nsec = 502470819}, st_ctim = {tv_sec = 1550158563, tv_nsec = 502470819}, __unused = {0, 0, 0}} __FUNCTION__ = "main" (gdb) version: kamailio 5.1.7 (x86_64/linux) 567df3 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, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 567df3 compiled on 02:06:09 Feb 2 2019 with gcc 4.8.5 -- BR, Denys Pozniak

2 2

Assemble struct sip_uri back to string?
by Ivan Ribakov 15 Feb '19

15 Feb '19

Hi all, does anyone know if there is a C function available in some module/header that assembles parsed sip_uri struct back into a single buffer? I’ve been looking at msg_parser.h (where sip_uri struct is defined) and parse_uri.h, but I can’t see anything of that kind. Thanks in advance, Ivan

3 3

Fwd: pv_buffer_size config value actually ignored?
by Enrico Bandiera 14 Feb '19

14 Feb '19

---------- Forwarded message --------- From: Enrico Bandiera <enrico.bandiera(a)cloud.timenet.it> Date: mer 13 feb 2019 alle ore 09:18 Subject: Re: [SR-Users] pv_buffer_size config value actually ignored? To: Daniel-Constantin Mierla <miconda(a)gmail.com> Hello Daniel, yes we do use that $avp for a log line which is actually a big json, the $avp is composed by multiple jansson_append calls and at the end an xlog() calls prints it Could it also be that I'm miscalculating because of the encoding? 4K utf8 characters could be more than 4K (but I don't think there are so many multibytes characters to let it reach the 8K limit) Il giorno mer 13 feb 2019 alle ore 09:15 Daniel-Constantin Mierla < miconda(a)gmail.com> ha scritto: > Hello, > > where do you use that avp, because for the avp value itself, that buffer > is not used -- avp values are stored in shared memory. > > Do you use that avp in xlog() or other functions parameters? > > Cheers, > Daniel > On 13.02.19 09:10, Enrico Bandiera wrote: > > Hi, I'm having some strange issues with a somewhat big $avp value, when it > reaches a size of about 4K I get this error: > > 29(47) ERROR: <core> [core/pvapi.c:1452]: pv_printf(): no more space for > spec value > 29(47) ERROR: <core> [core/pvapi.c:1461]: pv_printf(): buffer overflow – > increase the buffer size... > > In the docs I read that the default pv_buffer_size is 8K, I still tried to > enforce it to something bigger and checked the logs to be sure it was set: > > 0(384) DEBUG: <core> [core/pvapi.c:2062]: pv_init_buffer(): PV print > buffer initialized to [40][16384] > > But still when reaching the 4K size inside the $avp that error comes out, > is there any limit I'm not aware of? > > Thanks, > Enrico. > > _______________________________________________ > Kamailio (SER) - Users Mailing Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > -- > Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com > Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com > >

2 6

TM Module - Unfortunately error on sending to next hop occurred (477/TM)
by Ilie Soltanici 14 Feb '19

14 Feb '19

Hi List, Can someone give a hint related to this issue, please? On other messages, I found that this problem may happen why variable $du is empty, but in my case looks that it's present: Config File: if (!t_relay()) { switch ($retcode) { case -1: xlogl("L_ERR", "[$cfg(route)] Generic Internal Error\n"); xlogl("L_ERR", "[$cfg(route)] | $du/$ru |\n"); break; Log File: [RELAY] Generic Internal Error [RELAY] | sip:192.168.180.23:15109/sip:1003@ 192.168.180.23:15109 | sl [sl_funcs.c:372]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (1/SL) Also, as I understand this may happen when there is a problem on the physical network, i'm not sure that is my case - because kamailio and asterisk are 2 VM's running on the same Physical Server, and both their interfaces are connected to the same Virtual Switch. There is no firewalls/selinux on those servers. Can someone help please?

2 1

Kamailio/Dispatcher failure routing to SRV record
by Jesse Strahn 13 Feb '19

13 Feb '19

Hi all, I'm hoping someone can help me with this as I am baffled. I have a server running Kamailio with dispatcher. I am trying to direct calls from kamailio to an SRV record but am receiving a 404 error on the calls. If I instead place one of the hostnames from the SRV record in my dispatcher.list, the call completes fine. Contents of dispatcher.list look like: 1 sip:bvr.production.instance:5060 Nslookup from the Kamailio server for SRV record: nslookup -type=SRV _sip._udp.bvr.production.instance Server: 10.0.0.2 Address: 10.0.0.2#53 Non-authoritative answer: _sip._udp.bvr.production.instance service = 1 10 5060 ip-10-100-79-143.production.instance. _sip._udp.bvr.production.instance service = 1 10 5060 ip-10-100-96-92.production.instance. Again, if I put 1 sip: ip-10-100-96-92.production.instance:5060 into the dispatcher.list, the call routes fine. Is there some configuration within Kamailio required to route to an SRV record in this way? I haven't found anything indicating that is the case. Any help is greatly appreciated. Thanks, Jesse

2 2

Mysql to hastable conversion
by Duarte Rocha 13 Feb '19

13 Feb '19

Greetings, I have Kamailio has an SBC and i'm using a MySQL database to store all the relevant configurations and settings regarding the NAP's, Users, Numbers, etc. That being said, i'm having lots of of performance issues originated by the queries. In order to solve that i think the best way to proceed would be to implement hashtables. However, i would like to keep Sql DB's for easier configuration and having them automatically transformed into hashtables. Is there a simple way to do this? As i see, the htable module is able to load from a DB, but i understand it, the table should be already in "hashtable form". Does kamailio has any way to solve this or should i use external tools? Best Regards, Duarte Rocha

2 1

kamailio with oracle data base
by eyas barhouk 13 Feb '19

13 Feb '19

Hello Community i'm trying to build kamailio on top of oracle D.B so is there any way to configure kamailio to deal with Oracle D.B and call functions from it ? Thanks in advance. Regards Eyas

4 9

Cannot get message routing for websockets "invalid" URI
by Sergey Safarov 13 Feb '19

13 Feb '19

I have configured websocket usage using this module description https://kamailio.org/docs/modules/devel/modules/websocket.html Added registrar and usrloc modules Registration saved using this block route[REGISTRAR] { if(!is_method("REGISTER")) return; if (!save("location")) { xlog("L_INFO", "Location save error\n"); sl_reply_error(); } } Now in database i can see WebRTC client registration { "jsonrpc": "2.0", "result": { "Domains": [{ "Domain": { "Domain": "location", "Size": 1024, "AoRs": [{ "Info": { "AoR": "1000", "HashID": 924766747, "Contacts": [{ "Contact": { "Address": "sips:1000@df7jal23ls0d.invalid ;rtcweb-breaker=no;transport=wss", "Expires": 155, "Q": -1, "Call-ID": "0c818ac1-5e77-bd4c-b7fe-a135d6c6a4bf", "CSeq": 61442, "User-Agent": "IM-client/OMA1.0 sipML5-v1.2016.03.04", "Received": "[not set]", "Path": "[not set]", "State": "CS_SYNC", "Flags": 0, "CFlags": 0, "Socket": "tls:192.168.2.10:7443", "Methods": -1, "Ruid": "uloc-5c643a67-4b56-1", "Instance": "[not set]", "Reg-Id": 0, "Server-Id": 0, "Tcpconn-Id": 2, "Keepalive": 0, "Last-Keepalive": 1550074434, "Last-Modified": 1550074434 } }] } } ], "Stats": { "Records": 1, "Max-Slots": 1 } } }] }, "id": 19493 } Now I try deliver call to WebRTC client. Kamailio receives message INVITE sip:1001@192.168.30.2 SIP/2.0 Via: SIP/2.0/UDP 192.168.30.2:45060;rport;branch=z9hG4bK5gaK3B38egZQH Route: <sip:192.168.2.10> Max-Forwards: 70 From: "" <sip:0000000000@192.168.30.2>;tag=8e7Za8pD6pcKg To: <sip:1001@192.168.30.2> Call-ID: 989274f0-aa4d-1237-08a1-94b86deaeed5 CSeq: 483510 INVITE Contact: <sip:mod_sofia@192.168.30.2:45060> User-Agent: FreeSWITCH-mod_sofia/1.8.4+git-20181228T070140Z~a0377e9677~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, path, replaces Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer Content-Type: application/sdp Content-Disposition: session Content-Length: 621 X-FS-Support: update_display,send_info Remote-Party-ID: <sip:0000000000@192.168.30.2 >;party=calling;screen=yes;privacy=off Expected that Kamailio using follow config block route message to WEbRTC client via websocket. route[FROM_FS] { record_route(); if (!lookup("location")) { $var(rc) = $rc; t_newtran(); switch ($var(rc)) { case -1: case -3: send_reply("404", "Not Found"); exit; case -2: send_reply("405", "Method Not Allowed"); exit; } } route(RELAY); exit; } But really Kamailio try resolve "sips:1000@df7jal23ls0d.invalid" URI via DNS and deliver for non locally connected device 3(19341) exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=238 a=16 n=if 3(19341) exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=231 a=41 n=isflagset 3(19341) exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=232 a=5 n=route 3(19341) exec: *** cfgtrace:request_route=[FROM_FS] c=[/usr/local/etc/kamailio/kamailio.cfg] l=266 a=24 n=record_route 3(19341) exec: *** cfgtrace:request_route=[FROM_FS] c=[/usr/local/etc/kamailio/kamailio.cfg] l=281 a=16 n=if 3(19341) exec: *** cfgtrace:request_route=[FROM_FS] c=[/usr/local/etc/kamailio/kamailio.cfg] l=267 a=25 n=lookup 3(19341) DEBUG: registrar [lookup.c:255]: lookup_helper(): contact for [1000] found by address 3(19341) exec: *** cfgtrace:request_route=[FROM_FS] c=[/usr/local/etc/kamailio/kamailio.cfg] l=281 a=5 n=route 3(19341) exec: *** cfgtrace:request_route=[RELAY] c=[/usr/local/etc/kamailio/kamailio.cfg] l=289 a=16 n=if 3(19341) exec: *** cfgtrace:request_route=[RELAY] c=[/usr/local/etc/kamailio/kamailio.cfg] l=286 a=24 n=t_relay 3(19341) DEBUG: tm [t_lookup.c:1326]: t_newtran(): msg id=2 , global msg id=2 , T on entrance=0 3(19341) DEBUG: tm [t_lookup.c:483]: t_lookup_request(): start searching: hash=7468, isACK=0 3(19341) DEBUG: tm [t_lookup.c:441]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bK72v4614F91BXr] 3(19341) DEBUG: tm [t_lookup.c:666]: t_lookup_request(): no transaction found 3(19341) DEBUG: tm [t_hooks.c:348]: run_reqin_callbacks_internal(): trans=0x7fbb0b1d0d40, callback type 1, id 0 entered 3(19341) DEBUG: <core> [core/md5utils.c:67]: MD5StringArray(): MD5 calculated: 07ad473ba02a6d3a4f8753a378c102e8 3(19341) DEBUG: tm [t_funcs.c:324]: t_relay_to(): new INVITE 3(19341) DEBUG: tm [t_reply.c:596]: _reply_light(): reply sent out. buf=0x7fbb0f256750: SIP/2.0 100 trying -..., shmem=0x7fbb0b1e75d8: SIP/2.0 100 trying - 3(19341) DEBUG: tm [t_reply.c:607]: _reply_light(): finished 3(19341) DEBUG: <core> [core/dns_cache.c:527]: _dns_hash_find(): (_sips._tcp.df7jal23ls0d.invalid(31), 33), h=232 3(19341) DEBUG: <core> [core/resolve.c:967]: get_record(): skipping 1 NS (p=0x561007b83e71, end=0x561007b83ebc) 3(19341) DEBUG: <core> [core/resolve.c:980]: get_record(): parsing 0 ARs (p=0x561007b83ebc, end=0x561007b83ebc) 3(19341) DEBUG: <core> [core/dns_cache.c:761]: dns_cache_mk_bad_entry(): (_sips._tcp.df7jal23ls0d.invalid, 33, 60, 1) 3(19341) DEBUG: <core> [core/dns_cache.c:701]: dns_cache_add(): adding _sips._tcp.df7jal23ls0d.invalid(31) 33 (flags=1) at 232 3(19341) DEBUG: <core> [core/dns_cache.c:527]: _dns_hash_find(): (df7jal23ls0d.invalid(20), 1), h=139 3(19341) DEBUG: <core> [core/resolve.c:967]: get_record(): skipping 1 NS (p=0x561007b83e66, end=0x561007b83eb1) 3(19341) DEBUG: <core> [core/resolve.c:980]: get_record(): parsing 0 ARs (p=0x561007b83eb1, end=0x561007b83eb1) 3(19341) DEBUG: <core> [core/dns_cache.c:761]: dns_cache_mk_bad_entry(): (df7jal23ls0d.invalid, 1, 60, 1) 3(19341) DEBUG: <core> [core/dns_cache.c:701]: dns_cache_add(): adding df7jal23ls0d.invalid(20) 1 (flags=1) at 139 3(19341) ERROR: <core> [core/resolve.c:1698]: sip_hostport2su(): could not resolve hostname: "df7jal23ls0d.invalid" 3(19341) ERROR: tm [ut.h:309]: uri2dst2(): failed to resolve "df7jal23ls0d.invalid" 3(19341) ERROR: tm [t_fwd.c:1735]: t_forward_nonack(): failure to add branches 3(19341) DEBUG: tm [t_funcs.c:334]: t_relay_to(): t_forward_nonack returned error -478 (-478) 3(19341) DEBUG: tm [t_funcs.c:352]: t_relay_to(): -478 error reply generation delayed 3(19341) exec: *** cfgtrace:request_route=[RELAY] c=[/usr/local/etc/kamailio/kamailio.cfg] l=287 a=24 n=sl_reply_error 3(19341) ERROR: sl [sl_funcs.c:372]: sl_reply_error(): stateless error reply used: Unresolvable destination (478/SL) 3(19341) exec: *** cfgtrace:request_route=[RELAY] c=[/usr/local/etc/kamailio/kamailio.cfg] l=289 a=2 n=exit 3(19341) DEBUG: <core> [core/receive.c:353]: receive_msg(): request-route executed in: 12632 usec 3(19341) DEBUG: tm [t_lookup.c:1490]: t_unref(): delayed error reply generation(-478) 3(19341) DEBUG: tm [t_reply.c:1650]: cleanup_uac_timers(): RETR/FR timers reset 3(19341) DEBUG: tm [t_reply.c:596]: _reply_light(): reply sent out. buf=0x7fbb0f2571f0: SIP/2.0 478 Unresolv..., shmem=0x7fbb0b1e7860: SIP/2.0 478 Unresolv 3(19341) DEBUG: tm [t_reply.c:607]: _reply_light(): finished Looks I missed some thing in message routing, But cannot find what. Please point me how to properly route call for this case.

1 0

$HN(d) null when DNS cache is enabled
by Julien Klingenmeyer 13 Feb '19

13 Feb '19

Hello, I have a small question regarding the internal DNS resolver. Here is my current Kamailio DNS configuration: dns_try_naptr=on use_dns_failover=yes use_dns_cache=yes I need the $HN variable inside my script and it appeared while testing that $HN(d) was null (and consequently $HN(f) was only containing the hostname part of the FQDN). I know /etc/hosts file is bypassed when the DNS cache is activated, so I thought Kamailio was using the domain parameter set in the /etc/resolv.conf file in such cases in order to get the domain. But it was not. I figured out Kamailio correctly retrieves the domain name as long as it is explicitly part of the /etc/hostname file. Is my understanding correct or am I wrong somewhere? What if /etc/hostname does not contain the domain name but hostname only? Thanks! Cheers Julien

1 0

pv_buffer_size config value actually ignored?
by Enrico Bandiera 13 Feb '19

13 Feb '19

Hi, I'm having some strange issues with a somewhat big $avp value, when it reaches a size of about 4K I get this error: 29(47) ERROR: <core> [core/pvapi.c:1452]: pv_printf(): no more space for spec value 29(47) ERROR: <core> [core/pvapi.c:1461]: pv_printf(): buffer overflow – increase the buffer size... In the docs I read that the default pv_buffer_size is 8K, I still tried to enforce it to something bigger and checked the logs to be sure it was set: 0(384) DEBUG: <core> [core/pvapi.c:2062]: pv_init_buffer(): PV print buffer initialized to [40][16384] But still when reaching the 4K size inside the $avp that error comes out, is there any limit I'm not aware of? Thanks, Enrico.

2 1

memory issue with jsonrpc
by Benjamin Roy 12 Feb '19

12 Feb '19

Hi, I'm hoping someone can guide me in the right direction. In kamailio 5.2.1 I'm getting the following memory errors after a while (hours or days) of sending messages with jsonrpc. Restarting kamailio clears them for a while. Any suggestions on what I should change, or how to better identify the issue? 24(6177) ERROR: <core> [core/mem/q_malloc.c:291]: qm_find_free(): qm_find_free(0x7f1cbe6fd000, 5712); Free fragment not found! 24(6177) ERROR: <core> [core/mem/q_malloc.c:425]: qm_malloc(): qm_malloc(0x7f1cbe6fd000, 5712) called from tm: h_table.c: build_cell(339), module: tm; Free fragment not found! 24(6177) ERROR: tm [uac.c:422]: t_uac_prepare(): short of cell shmem 24(6177) ERROR: pua [send_publish.c:700]: send_publish(): in t_request tm module function 24(6177) ERROR: pua_rpc [pua_rpc.c:280]: pua_rpc_publish_mode(): pua send_publish failed I have these buffer values in the config file tcp_rd_buf_size=65536 pv_buffer_size=32768 and I'm running kamailio with these memory options "-m 1024 -M 16" The jsonrpc message I'm sending look like this { "jsonrpc": "2.0", "method": "pua.publish", "params": [ "sip:172.1.1.3:5060;transport=tcp", "300", "reg", "application/reginfo+xml", ".", ".", ".", ".", "<?xml version='1.0' ?> <reginfo state='partial' version='0' xmlns='urn:ietf:params:xml:ns:reginfo' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'> <registration aor='sip:55555@uw.edu' id='a19685' state='active'> <contact duration-registered='906' event='registered' id='c19685--1732979172--1829864152-2' q='1.0' state='active'> <uri>sips:55555@172.1.2.4:62270;transport=tls;avaya-sc-enabled</uri> <elin></elin> </contact> </registration> </reginfo> " ], "id": 1 } Thanks, -Ben

2 3

Programmatically modify SIP Requests/Responses in Kamailio
by Filippos Vasilakis 12 Feb '19

12 Feb '19

Hi, First of all I would like to congratulate and thank everyone who has worked in Kamailio. It looks like an awesome tool. I am starting a side project and I am not very familiar with Kamailio although I know SIP and VoIP in general, so I am more looking for answers that tell me if it's possible or not what I am asking along with some hints on how/where to look. Is there a way to filter/forward/modify(through the headers) incoming SIP requests and Kamailio SIP responses programmatically in Kamailio ? I have seen that you can run embedded code like Ruby, but I wonder if this is for simple things or more complex stuff which probably is in my case since there will be plenty of business logic to figure out what action to take with a SIP request. I have also found the EVAPI that is supposed to be handle events through TCP but not much more info available. So to sum up, is there a way to filter/forward/modify incoming SIP requests and create responses programmatically in Kamailio ? If yes, what's the proper way of doing that ? If no, any idea where I should look for that? Thanks, Filippos

2 1

Kamailio modules that can be used in Lua
by Leonid Fainshtein 12 Feb '19

12 Feb '19

Hello, I am checking a possibility to replace the traditional cfg script with a Lua script. In the app_lua module documentation there is a relatively short list of modules that can be registered to Lua. The modules nathelper, rtpproxy, topoh and many others don't appear in the list. Does it mean that it is not possible to use that modules in Lua? Best regards, Leonid Fainshtein Xorcom Ltd

2 1

Repository for automatic deployment of Kamailio
by Gholamreza Sabery 11 Feb '19

11 Feb '19

Hi, A few years ago, I developed an Ansible repository for automatic deployment of Kamailio. Recently, I added some new features, and now you can deploy the playbooks on Docker containers. I think it is a good starting point for anyone who wants to deploy and use Kamailio for the first time. Link of the repository: https://github.com/ghrst/Kamailio-HA Regards Gholamreza Sabery Tabrizy

2 1

Kamailio TOPOS fail
by Marcos Pytel 11 Feb '19

11 Feb '19

Hi, When I activate the TOPOS function, the Kamailio lb fail. This is the traceback Program terminated with signal SIGABRT, Aborted. #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) backtrace #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x00007f66d5aab42a in __GI_abort () at abort.c:89 #2 0x00007f66d5ae7c00 in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f66d5bdb305 "*** %s ***: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:175 #3 0x00007f66d5b701f7 in __GI___fortify_fail (msg=msg@entry=0x7f66d5bdb29c "buffer overflow detected") at fortify_fail.c:30 #4 0x00007f66d5b6e330 in __GI___chk_fail () at chk_fail.c:28 #5 0x00007f66b867e097 in memcpy (__len=<optimized out>, __src=<optimized out>, __dest=0x7f66b8892524 <_tps_redis_cbuf+4>) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #6 tps_redis_load_branch (msg=<optimized out>, md=<optimized out>, sd=0x7ffed3993d30, mode=<optimized out>) at topos_redis_storage.c:744 #7 0x00007f66b88b35c0 in tps_request_received (msg=msg@entry=0x7ffed3995f80, dialog=dialog@entry=1) at tps_msg.c:786 #8 0x00007f66b88b9255 in tps_msg_received (evp=<optimized out>) at topos_mod.c:332 #9 0x000055e1dc07da88 in sr_event_exec (type=<optimized out>, evp=<optimized out>) at core/events.c:211 #10 0x000055e1dc0415f5 in receive_msg ( buf=buf@entry=0x55e1dc511d40 <buf> "BYE sip:atpsh-5c4b0f6e-25b2-9@10.10.10.2 SIP/2.0\r\nVia: SIP/2.0/UDP 10.10.10.1:5060;branch=z9hG4bK898122669\r\nFrom: <sip:2972426338@10.10.10.1>;tag=3296734298\r\nTo: <sip:414533@10.10.10.2>;tag=03D2CCF0-5"..., len=381, rcv_info=rcv_info@entry=0x7ffed3996980) at core/receive.c:157 #11 0x000055e1dbf5e6e3 in udp_rcv_loop () at core/udp_server.c:554 #12 0x000055e1dbef3a9f in main_loop () at main.c:1619 #13 0x000055e1dbeea8cb in main (argc=<optimized out>, argv=0x7ffed3996f38) at main.c:2638 This is a Kamailio error? I can fix it? Thanks. Marcos.

4 6

reg_fetch_contacts and t_relay usage
by Володимир Іванець 11 Feb '19

11 Feb '19

Hello! I'm using *reg_fetch_contacts* function to get information about all contacts. This allows to define which contacts should receive the call. My question is if it's possible to choose only one contact before *t_relay* is called? Or *reg_fetch_contacts* call and verification should be done after *t_relay* in all branches and those which are not needed should be stopped? Thanks a lot!

2 2

rtpengine not listening on specified port range
by Narayan P 11 Feb '19

11 Feb '19

Hello, I am starting the rtpengine through this command,but rtpengine is not listening on the specified port range.It is listening on some other port outside of this.Here first IP is private IP and the second IP is public one.So issue is with audio.Can you please let me know what exactly I am missing. rtpengine --interface=172.20.xx.xxx\!34.209.1.xx -f -m 16384 -M 16884 -E --listen-ng=127.0.0.1:22222 & Any suggestion will be highly appreciated. Thanks, Narayan NP

2 2

trace sip msg topos
by Giuseppe Pandolfi 11 Feb '19

11 Feb '19

Hi All, is it possible print sip msg after stripping by topos module? I have need to print sip msg stripped by topos in syslog. Thanks

4 3

rtpengine not listening on specified port range
by Narayan P 11 Feb '19

11 Feb '19

Hello, I am starting the rtpengine through this command,but rtpengine is not listening on the specified port range.It is listening on some other port outside of this.Here first IP is private IP and the second IP is public one.So issue is with audio.Can you please let me know what exactly I am missing. rtpengine --interface=172.20.xx.xxx\!34.209.1.xx -f -m 16384 -M 16884 -E --listen-ng=127.0.0.1:22222 & Any suggestion will be highly appreciated. Thanks, Narayan

1 0

rat-proxy issue
by aroosa satti 10 Feb '19

10 Feb '19

Hi! I have issue regarding my rtpproxy.I have start it but it does't work and give error like Feb 9 02:46:50 ns1 ./kamailio[3682]: NOTICE: <core> [main.c:692]: handle_sigs(): Thank you for flying kamailio!!! Feb 9 02:46:53 ns1 ./kamailio[4318]: ERROR: <core> [main.c:1165]: parse_phostport(): bad protocol in unix:/var/run/rtpproxy.sock these are the issue I will be grateful for you if you solve this problem. kind regards Aroosa Satti

2 1

how to differentiate branches in parallel call forking
by Koray Vatansever 09 Feb '19

09 Feb '19

Hi, I'm trying to implement parallel call forking scenario. Since target clients have different media profiles, I need to set different rtpengine options for those forked calls. So according to the rtpengine module documentation, I set via-branch option on request and response, '1' and '2' respectively ('auto' option is not working. There is no code implementing this parameter). However all forked branches have the same via branch id which is the incoming INVITE's via branch id. As a result, rtpengine thinks that all the offers belong to the same session I guess. It seems I have only 'extra' option with extra_pv_id variable. In order to use it, I need an elegant way to differentiate forked branches in request and response processing. I would appreciate any suggestion.

1 1

rtpproxy issues
by aroosa satti 08 Feb '19

08 Feb '19

Hi! I have issue regarding my rtpproxy.I have start it but it does't work and give error like Feb 9 02:46:50 ns1 ./kamailio[3682]: NOTICE: <core> [main.c:692]: handle_sigs(): Thank you for flying kamailio!!! Feb 9 02:46:53 ns1 ./kamailio[4318]: ERROR: <core> [main.c:1165]: parse_phostport(): bad protocol in unix:/var/run/rtpproxy.sock these are the issue I will be grateful for you if you solve this problem. kind regards Aroosa Satti

1 0

Kamailio modules that can be used in Lua
by Leonid Fainshtein 08 Feb '19

08 Feb '19

Hello, I am checking a possibility to replace the traditional cfg script with a Lua script. In the app_lua module documentation there is a relatively short list of modules that can be registered to Lua. The modules nathelper, rtpproxy, topoh and many others don't appear in the list. Does it mean that it is not possible to use that modules in Lua? Best regards, Leonid Fainshtein

3 2

Waiting for calls
by Mark Hall 08 Feb '19

08 Feb '19

Hi, I am using Kamailio as a gateway for inbound calls to a group of Asterisk servers. One particular call scenario involves matching pairs of calls. Originally I was just sending the calls through to Asterisk for processing (including the 'matching up'), but there is a further requirement that the first received call must not be answered until its matching call arrives - and this is a little awkward in Asterisk, especially if there will be many calls. I thought of t_suspend/t_continue functionality in Kamailio. I have implemented this: CallA arrives. Send 180-ringing Use ds_select_dst() to choose an Asterisk to handle the paired calls Store destination and other data in an htable so that I can match the call later. Invoke t_suspend() for CallA. What I have implemented when the matching call arrives is this: CallB arrives (and some logic matches it to the suspended CallA). Invoke t_continue('id','label','CONTINUE_CALL'); so that CallA is now released and the route ends in t_relay() to send it on to Asterisk. Set $du on CallB to match the destination, then t_relay() this call to send it on to the same Asterisk. The solution almost works, but there is a problem. The t_relay() for CallA is fine, and the call is forwarded. When the script runs the t_relay() for CallB, I get this logged: ERROR: tm [t_fwd.c:1728]: t_forward_nonack(): no branches for forwarding ERROR: sl [sl_funcs.c:362]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (6/SL) AND after each call I notice an extra transaction stuck in Kamailio (when I use kamctl rpc tm.list). Can anyone point out where my Kamailio/SIP understanding has let me down? Many Thanks, Mark Hall

2 2

Re: [SR-Users] TLS challenge
by Gertjan Wolzak 07 Feb '19

07 Feb '19

Hello Kamailions, Julien, thank you for the help, I have added the letsencrypt ca certificate to the ca list, still no dice. So, still got lots of questions, but after my last booboo going to do some more research and testing. When I have no more hair left will get back to the list. Thanks for now. Rgds, Gertjan Wolzak

2 1

ERROR : EAGAIN and write queue full or failed for tcp Connection
by YASIN CANER 07 Feb '19

07 Feb '19

Hello, Kamailio gave this error that couldnt bind tcp connection other side. Thanks Yasin CANER Kamailio IPv6:TCP: -----> IPv6:TCP Kamailio -----> X ERROR XXXX IPv6:TCP Kamailio IPv6::C IPv6::8 IPv6::5 LOGS: 7(15781) DEBUG: <core> [core/msg_translator.c:2937]: create_via_hf(): id added: <;i=1>, rcv proto=2 7(15781) DEBUG: <core> [core/msg_translator.c:162]: check_via_address(): (FD61:C23C:B3B6:0:0:0:0:C, [FD61:C23C:B3B6:0:0:0:0:C], 0) 7(15781) DEBUG: <core> [core/tcp_main.c:1977]: tcp_send(): no open tcp connection found, opening new one 7(15781) DEBUG: <core> [core/ip_addr.c:242]: print_ip(): tcpconn_new: new tcp connection: fd61:c23c:b3b6:0:0:0:0:5 7(15781) DEBUG: <core> [core/tcp_main.c:1229]: tcpconn_new(): on port 5060, type 2 7(15781) DEBUG: <core> [core/tcp_main.c:1539]: tcpconn_add(): hashes: 507:2382:0, 2 7(15781) DEBUG: <core> [core/tcp_main.c:2873]: tcpconn_1st_send(): pending write on new connection 0x7fd15b5e7c98 (-1/1483 bytes written) (err: 11 - Resource temporarily unavailable) 7(15781) ERROR: <core> [core/tcp_main.c:2891]: tcpconn_1st_send(): [FD61:C23C:B3B6:0:0:0:0:5]:5060: EAGAIN and write queue full or failed for 0x7fd15b5e7c98 7(15781) DEBUG: <core> [core/tcp_main.c:3153]: tcpconn_chld_put(): destroying connection 0x7fd15b5e7c98 (2, -1) flags 0060 7(15781) ERROR: tm [../../core/forward.h:251]: msg_send_buffer(): tcp_send failed 7(15781) DEBUG: tm [t_fwd.c:1549]: t_send_branch(): send to FD61:C23C:B3B6:0:0:0:0:5:5060 (2) failed 7(15781) WARNING: tm [t_fwd.c:1567]: t_send_branch(): sending request on branch 0 failed CONF: dns_try_ipv6=yes dns_retr_time=1 dns_retr_no=1 dns_cache_flags=4 tcp_source_ipv6 = [fd61:c23c:b3b6::8] tcp_async=yes tcp_rd_buf_size=65536 tcp_wq_blk_size=3000 listen=tcp:[fd61:c23c:b3b6::8]:5060 tcp_connection_lifetime=3605 listen=tcp:[fd61:c23c:b3b6::8]:5060 ..... route[]{ remove_hf("Route"); #loose_route(); if (!is_method("INVITE")) return; $du="sip: mykamailio1.test:5060;transport=tcp"; if(!t_newtran()){ xlog("L_WARN"," Couldnt create new transaction \r\n"); sl_send_reply("503", "Service not available"); exit; } if(!t_relay()){ send_reply("503", "Service not available"); exit; } exit; }

4 7

Keep requests order
by Duarte Rocha 07 Feb '19

07 Feb '19

Greetings, I'm having some problems with keeping the order of the messages in Kamailio. In some cases i'm receiving an ACK for the first INVITE and immediately after that a RE-INVITE is sent by the client. What is happening is that the the ACK took double the time of the RE-INVITE to process and as a consequence, the RE-INVITE was relayed before the ACK. I have two questions : 1 - Is there a way to keep the order of the messages in a dialog, and if so, what are the downsides to it? 2 - The machine wasn't in a load state (only one concurrent call) and the ACK and the RE-INVITE should go roughly through the same processing methods and should take took the same time to be be relayed. What can be the reason for this? Best Regards, Duarte Rocha

4 7

Kamailio with RTPengine, allow source port of RTP to change during a call
by Laurent Schweizer 06 Feb '19

06 Feb '19

Hello, I'm using the RTPengine with Kamailio and I have a question for a specific case. I have some customer that are changing the source port of the RTP stream during the call ( no re-invite) I think it's more a NAT issue that a user agent issue... I see in the doc that I can handle this case with the "media handover" but in that case the rtpengine will allow a change of the source port but also of the source IP. Any possibility to allow only a change of the source port so source IP must still be the same ? Thanks BR Laurent

2 1

Kamailio failure routing to SRV Record
by Jesse Strahn 05 Feb '19

05 Feb '19

Hi all, I am trying to route requests from Kamailio to a private SRV record in AWS Route 53. If I setup the record as an A record and put the 3 destination sip server IPs in the record, Kamailio routes perfectly round-robinning between the 3 servers. However, If I switch my dispatcher.list over to the SRV record, the calls do not route and I get a 404 No Destination in my pcap. When I perform a `dig _sip._udp.pool.sip.servers` from the Kamailio server, it properly returns the hostnames of the 3 sip servers that the SRV record points to. I'm not sure if something in the Kamailio routing has to be changed to accommodate SRV record routing rather than A record? I have scoured the internet and can't really find much of anything. Would greatly appreciate any guidance. Thanks, Jesse

3 3

Error UAS
by Nicolas Breuer 05 Feb '19

05 Feb '19

Hello, How can we avoid these errors ? Feb 5 11:21:39 proxy1 /usr/sbin/kamailio[29563]: ERROR: tm [t_reply.c:1301]: t_should_relay_response(): status rewrite by UAS: stored: 408, received: 200 Thanks

2 1

TLS challenge
by Gertjan Wolzak 05 Feb '19

05 Feb '19

Hello Kamailions, Ive beent trying to configure a tls connection between kamailio servers, but looks like Im missing some knowledge. The situation: phone1 <> internet <> kamailio1 <internet> kamailio2<> internet <> phone2 The phones are yealink phones, they are connected using TLS v1.2, phone 1 registers at kamailio1 and phone2 registers at kamailio2. Both kamailio servers have an letsencrypt certificate. When the connection between the two kamailio servers is set as sip, a call from a phone1 to phone2 the singnaling is forwarded and rtp flows. When I set the connection between the two kamailio servers to tls, things go wrong.. or better said I go wrong. The kamailio log on the receiving kamailio(kamailio2) shows that things go wrong and where, but I just cant figure out how to solve it. The log shows that the tls connection will be handled by the TLS Default configuration, the CA certificate is missing, well unknown. 15(7209) DEBUG: <core> [core/ip_addr.c:229]: print_ip(): tcpconn_new: new tcp connection: 116.203.53.212 15(7209) DEBUG: <core> [core/tcp_main.c:999]: tcpconn_new(): on port 44153, type 3 15(7209) DEBUG: <core> [core/tcp_main.c:1309]: tcpconn_add(): hashes: 1805:3331:3809, 3 15(7209) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa77de0, 32, 2, 0x7ff9596d4b10), fd_no=23 15(7209) DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xa77de0, 32, -1, 0x0) fd_no=24 called 15(7209) DEBUG: <core> [core/tcp_main.c:4196]: handle_tcpconn_ev(): sending to child, events 1 15(7209) DEBUG: <core> [core/tcp_main.c:3878]: send2child(): selected tcp worker 1 8(7202) for activity on [tls:kamailio2:5061], 0x7ff9596d4b10 8(7202) DEBUG: <core> [core/tcp_read.c:1759]: handle_io(): received n=8 con=0x7ff9596d4b10, fd=9 8(7202) DEBUG: tls [tls_server.c:199]: tls_complete_init(): completing tls connection initialization 8(7202) DEBUG: tls [tls_server.c:228]: tls_complete_init(): Using initial TLS domain TLSs<default> (dom 0x7ff959498600 ctx 0x7ff9594b6430 sn []) 8(7202) DEBUG: tls [tls_domain.c:724]: sr_ssl_ctx_info_callback(): SSL handshake started 8(7202) DEBUG: <core> [core/tcp_main.c:2460]: tcpconn_do_send(): sending... 8(7202) DEBUG: <core> [core/tcp_main.c:2494]: tcpconn_do_send(): after real write: c= 0x7ff9596d4b10 n=2637 fd=9 8(7202) DEBUG: <core> [core/tcp_main.c:2495]: tcpconn_do_send(): buf= 8(7202) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xac78a0, 9, 2, 0x7ff9596d4b10), fd_no=1 8(7202) ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14094418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca 8(7202) ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7ff9596d4b10 r: 0x7ff9596d4b90 (-1) 8(7202) DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xac78a0, 9, -1, 0x10) fd_no=2 called 8(7202) DEBUG: <core> [core/tcp_read.c:1683]: release_tcpconn(): releasing con 0x7ff9596d4b10, state -2, fd=9, id=3 (kamailio1]:44153 -> [kamailio1]:5061) 8(7202) DEBUG: <core> [core/tcp_read.c:1684]: release_tcpconn(): extra_data 0x7ff9596d2ab0 15(7209) DEBUG: <core> [core/tcp_main.c:3308]: handle_tcp_child(): reader response= 7ff9596d4b10, -2 from 1 15(7209) DEBUG: tls [tls_server.c:667]: tls_h_close(): Closing SSL connection 0x7ff9596d2ab0 I assume I have configured tls.cfg partially correct, as the phones register and can make tls calls. What I find strange is this line: 8(7202) DEBUG: <core> [core/tcp_read.c:1683]: release_tcpconn(): releasing con 0x7ff9596d4b10, state -2, fd=9, id=3 (kamailio1]:44153 -> [kamailio1]:5061) Would the "[kamailio1]:5061" be the client configuration? So, what do I need to configure within the tls.cfg file so when a tls connection is initiated from the other server it will work. I have tried adding the other server as server within the tls.cfg, which does not work as kamailio is not listening on the ip address configured. When I add the server as a client in the tls.cfg as follows, the connection is handled by the default TLS configuration. [server:default] method = TLSv1.2 verify_certificate = no require_certificate = no private_key = /etc/letsencrypt/live/kamailio.kazlow.nl/privkey.pem certificate = /etc/letsencrypt/live/kamailio.kazlow.nl/fullchain.pem #ca_list = /etc/kamailio/tls/cacert.pem #crl = /etc/kamailio/tls/crl.pem [client:kamailio1:5061] method = TLSv1.2 verify_certificate = no require_certificate = yes certificate = /etc/kamailio/tls/fullchain.pem ca_list = /etc/kamailio/tls/cacert.pem # This is the default client domain, settings # in this domain will be used for all outgoing # TLS connections that do not match any other # client domain in this configuration file. # We require that servers present valid certificate. # [client:default] method = TLSv1.2 verify_certificate = no require_certificate = no ca_list = /etc/kamailio/tls/cacert.pem I have tried forcing the socket on the sending kamailio, but that does not work. Any feedback on what I am doing wrong or where I can find information to extend my knowledge would be appreciated. Rgds, Gertjan Wolzak

2 1

How to chain proxies with Route header and loose_route()
by Ivan Ribakov 05 Feb '19

05 Feb '19

Assuming there are several proxies that have to be hopped sequentially to deliver the request and the order is determined dynamically (!), how can one achieve that behaviour in Kamailio? My understanding was that Route header is used for that - it allows to keep R-URI intact but still route the egress message elsewhere. Documentation of the loose_route() from RR module seems to confirm that. But the catch is that loose_route() will not pick up any Route header that I might add in the config via append_hf() due to the delayed lump processing (as explained in https://sourceforge.net/p/openser/bugs/277/#5f42). Thanks in advance for any help or ideas. Regards, Ivan

2 1

TLS traffic visualization HOWTO
by Giovanni Maruzzelli 04 Feb '19

04 Feb '19

# How to TRACE and visualize TLS and non-TLS SIP traffic in real time (thanks to Homer's Lorenzo Mangani for pointing me toward Frida) apt-get install python-pip pip install frida pip install hexdump wget https://raw.githubusercontent.com/google/ssl_logger/master/ssl_logger.py #first ssh terminal # create fifo pipe, then will send the content from fifo pipe to an sngrep without gui, which will be reading pcap from stdin, and sending eep packets to the other sngrep (third terminal) mkfifo /tmp/pipe cat /tmp/pipe | sngrep -N -q -H udp:127.0.0.1:5077 -I - #second ssh terminal # writes as pcap to fifo pipe what freeswitch writes and reads from ssl lib python ssl_logger_giova.py -pcap /tmp/pipe freeswitch #third ssh terminal # sngrep that receives packets from both the Ethernet device, and the eep packets sent by the other sngrep (eg, the tls packets ssl_logger grabs from freeswitch's ssl lib) sngrep -L udp:127.0.0.1:5077 (you may want to edit ssl_logger.py and change 228 to be 101 - LINKTYPE_IPV4 to be LINKTYPE_RAW ) -- Sincerely, Giovanni Maruzzelli OpenTelecom.IT cell: +39 347 266 56 18

2 2

Planning Fosdem 2019
by Daniel-Constantin Mierla 02 Feb '19

02 Feb '19

Hello, Fosdem 2019 is approaching, so I am writing to see if any of you plans to go to the event. If there is interest, we can try to organize again a dinner on Saturday evening, a tradition for our project at the past 10 editions or even more. Henning Westerholt will give a presentation about Kamailio in the RTC Devroom, I will be around as well. I know few more developers that plan to go to the event, so let's see who else from the community wants to join us. As usual, at Fosdem will be developers from other VoIP projects, like Asterisk, Janus, CGRates, Homer, Jitsi, ... At the past editions we typically had two "kamailio" events: 1) an "ad-hoc" developers meeting in the cantina (or other available room around) to discuss about short term plans for Kamailio -- time and place being decided as we meet there between us (expected in the afternoon of Saturday or during Sunday). 2) a dinner at a place nearby, with other VoIP folks joining us Reply if you plan to go to Fosdem and say if you want to join for a dinner. Just be aware that you have to pay for your food and drinks at the dinner, unless we are going to be surprised again by a generous sponsor that covers partially or completely to dinner. If you need more details about Fosdem, the website is: - https://fosdem.org Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

3 5

kamailio + asterisk + webrtc
by arish haque 01 Feb '19

01 Feb '19

Hi Daniel, Within a network above tech stack is working fine for VOIP calls. But when i am trying from outside there is no sign of RTP. Cmd for rtp - /sbin/rtpengine -p /var/run/rtpengine.pid --interface=192.168.1.249\!106.51.78.78 --listen-ng 127.0.0.1:60000 -m 50000 -M 55000 --log-level 6 --log-facility local1 106.51.78.78 - public ip 192.168.1.249 - priv ip (kamailio + RTPEngine) Kamailio config when call is b/w WebRTC --> WebRTC rtpengine_manage("trust-address replace-origin replace-session-connection direction=internal direction=external"); Here is SDP, captured on the client sitting outside. v=0 o=root 1133801452 1133801452 IN IP4 106.51.78.78 s=Asterisk PBX 16.0.0 c=IN IP4 106.51.78.78 t=0 0 m=audio 50196 UDP/TLS/RTP/SAVPF 0 8 111 9 126 a=maxptime:60 a=ice-ufrag:5e13a1292fc0b7163d49328b7516f763 a=ice-pwd:4fa5e003195492fa165020c81eff9346 a=candidate:Hc0a801ac 1 UDP 2130706431 192.168.1.172 46810 typ host a=candidate:Hc0a801ac 2 UDP 2130706430 192.168.1.172 46811 typ host a=connection:new a=setup:active a=fingerprint:SHA-256 AA:5A:51:BD:4C:53:65:E4:2B:EC:EB:BF:A9:07:DD:60:E3:46:D8:26:6D:04:C8:21:8B:B9:81:37:3A:EB:55:C0 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:111 opus/48000/2 a=rtpmap:9 G722/8000 a=rtpmap:126 telephone-event/8000 a=fmtp:126 0-16 a=sendrecv a=rtcp:50196 a=rtcp-mux a=ptime:20 a=candidate:T7Tqd3oKM4NvATH3 1 UDP 2097152255 106.51.78.78 50196 typ host Looking forward for help from you guys. Thanks & Regards, Arish Haque

1 0

dispatcher alg - 8
by Andrew Chen 31 Jan '19

31 Jan '19

Hey all, I need some more clarification on dispatcher alg 8: “8” - use first destination (good for failover). What is meant by "first destination"? How is that defined if I have more than one carrier. More specifically in our case for some PSTN locations we have this setup: primary carrier - 1 sip trunk backup carrier - 4 sip trunks or primary carrier - 4 sip trunks backup carrier - 1 sip trunk the one that have 4 sip trunks is it going to round-robin through it? this is setup on our old 4.1.5 release. thanks -- Andy Chen achen@ <achen(a)thinkingphones.com>fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

2 2

IMS early media
by Tsvetan Filev 31 Jan '19

31 Jan '19

Hi all. I want to use SIP early media to play music to the caller in kamailio IMS installation like this: http://www.sharetechnote.com/html/IMS_SIP_EarlyMedia.html I looked a little bit but didn't find ready solution. The information is vague on this topic. Should this be done through a module or application server ? May I need to handle ringing in onreply_route and send OK with SDP to the caller in SCSCF ? Regards.

2 8

Kamailio/dispatcher routing with SRV record
by Jesse Strahn 31 Jan '19

31 Jan '19

Is it possible to route to the back-end SIP servers via DNS SRV record rather than specifying multiple IP addresses in the dispatcher list on the Kamailio server? Running in AWS and looking to be able to dynamically update my list of available sip servers if a server goes offline or if a server comes online. Have Cloudwatch/Lambda setup to manipulate the SRV record with the IP address additions or subtractions but when I try to put the SRV record as the destination in dispatcher, it fails.

2 2

Kamailio v5.1.7 Released
by Daniel-Constantin Mierla 31 Jan '19

31 Jan '19

Hello, Kamailio SIP Server v5.1.7 stable release is out. This is a maintenance release of the previous stable branch, 5.1, that includes fixes since the release of v5.1.6. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.1.x. Deployments running previous v5.1.x versions are strongly recommended to be upgraded to v5.1.7 or to v5.2.x series. For more details about version 5.1.7 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2019/01/kamailio-v5-1-7-released/ RPM, Debian/Ubuntu packages will be available soon as well. Note: the branch 5.1 is the previous stable branch. The latest stable branch is 5.2, at this time with v5.2.1 being released out of it. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

1 0

Planing the release of Kamailio v5.1.7
by Daniel-Constantin Mierla 31 Jan '19

31 Jan '19

Hello, I am considering to release Kamailio v5.1.7 later this week, likely on Thursday, January 31, 2019. As usual, here come the notice to report any issue that you are aware of and not yet registered on the bug tracker in order to give them a chance to be analyzed and eventually fixed before the release. Also, take a look at the branch 5.1 in git and check if there are any missing commits from those you expected to be backported. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

1 1

Altering received parameter in Contact
by David Cunningham 30 Jan '19

30 Jan '19

Hello, I'm hoping someone can give advice on altering the received parameter in the Contact header on a reply. The situation is that a customer is REGISTERing using TLS, and our Kamailio replies with a 200 OK that includes a Contact header like this: Contact: <sip:123456789@xx.xx.102.10 :5061;transport=tls>;expires=3600;received="sip:xx.xx.102.10:36051;transport=TLS" The customer's device apparently had an issue with this, and the device manufacturer advises that they need the ";transport=TLS" on the received parameter removed. This sounds like a strange requirement, but it's what we've been told. Does anyone know how to alter this in a Kamailio configuration? Our system uses www_authorize to authenticate and is running Kamailio 4.2.1. Thanks in advance for any help! -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

5 9

Kamailio TCP/TLS Connection getting failed
by arish haque 30 Jan '19

30 Jan '19

Hi All, I am running kamailio 5.2.x on CentOS 7. Call is happening but i am getting the below error continuously in kamailio logs. WARNING: websocket [ws_frame.c:228]: encode_and_send_ws_frame(): TCP/TLS connection get failed Jan 30 17:57:01 localhost /usr/local/sbin/kamailio[22097]: ERROR: websocket [ws_frame.c:765]: ping_pong(): sending keepalive Any clue of why this is happening? Thanks, Arish Haque

1 0

TSILO on Kamailio 5.2.0
by Володимир Іванець 29 Jan '19

29 Jan '19

Hello! I am trying to repeat awesome configuration provided by Federico Cabiddu https://www.youtube.com/watch?v=4XIrR9bwUkM but only got it to work partially. So I'm wondering if someone else has same problem as me on latest Kamailio? I have two clients configured on 100-test account. Only one is registered. When *ts_store()* is executed on INVITE I get: *Jan 28 19:17:46 test /usr/sbin/kamailio[11204]: DEBUG: tsilo [ts_store.c:80]: ts_store(): storing transaction 29157:1612520187 for r-uri: 100-test* *Jan 28 19:17:46 test /usr/sbin/kamailio[11204]: DEBUG: tsilo [ts_hash.c:264]: insert_ts_urecord(): urecord entry 0x7f2bfcf7dd78* *Jan 28 19:17:46 test /usr/sbin/kamailio[11204]: DEBUG: tsilo [ts_handlers.c:56]: ts_set_tm_callbacks(): registered TMCB for transaction 29157:1612520187* *Jan 28 19:17:46 test /usr/sbin/kamailio[11204]: DEBUG: tsilo [ts_store.c:103]: ts_store(): transaction 29157:1612520187 (ruri: 100-test) inserted* *# kamcmd ts.dump*: *{* * Size: 2048* * R-URIs: {* * R-URI: 100-thirdlane* * Hash: 451001090* * Transactions: {* * Transaction: {* * Tindex: 29157* * Tlabel: 1612520187* * }* * }* * }* * Stats: {* * RURIs: 1* * Max-Slots: 1* * Transactions: 1* * }* *}* When second UAC registers, *ts_append("location", "$tU")* in route *PUSHJOIN* is executed. It throws following error: *Jan 28 19:18:10 test /usr/sbin/kamailio[11210]: ERROR: tsilo [tsilo.c:199]: ts_check_uri(): bad uri [100-test]* At same time running *kamcmd ts.lookup 100-test* command returns expected result: *{* * Transaction: {* * Tindex: 29157* * Tlabel: 1612520187* * }* *}* Thanks a lot!

2 2

Kamailio IMS Deployment
by Yağız AYDIN 29 Jan '19

29 Jan '19

Hello everyone, I'm new to Kamailio environment, and trying to implement Kamailio IMS services with FHoSS HSS on a single Ubuntu 18.04 . I have followed instructions on the Kamailio website, but faced some issues. I have managed to install FHoSS, but when I try to start HSS, i got following errors: [Thread-24] ERROR de.fhg.fokus.diameter.DiameterPeer.peer.StateMachine - StateMachine: Peer icscf.mnc001.mcc001.3gppnetwork.org:3869 not responding to connection attempt [Thread-24] ERROR de.fhg.fokus.diameter.DiameterPeer.peer.StateMachine - StateMachine: Peer scscf.mnc001.mcc001.3gppnetwork.org:3870 not responding to connection attempt I have started CSCFs by following commands: root@ulak-HP-ZBook-15:/opt/OpenIMSCore/FHoSS/deploy# kamailio -f /etc/kamailio/pcscf/kamailio-pcscf.cfg loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules Listening on udp: 10.3.0.188 [10.3.0.188]:5060 Aliases: *: pcscf.mnc001.mcc001.3gppnetwork.org:* ************************************************ root@ulak-HP-ZBook-15:/opt/OpenIMSCore/FHoSS/deploy# kamailio -f /etc/kamailio/scscf/kamailio-scscf.cfg loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules Listening on udp: 10.3.0.188 [10.3.0.188]:6060 Aliases: *: scscf.mnc001.mcc001.3gppnetwork.org:* *********************************************** root@ulak-HP-ZBook-15:/opt/OpenIMSCore/FHoSS/deploy# kamailio -f /etc/kamailio/icscf/kamailio-icscf.cfg loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules Listening on udp: 10.3.0.188 [10.3.0.188]:4060 tcp: 10.3.0.188 [10.3.0.188]:4060 Aliases: *: icscf.mnc001.mcc001.3gppnetwork.org:* How do I ensure that CSCFs work? And also how can I troubleshoot error that I've faced on FHoSS. I have attached my config files. Any helps will be appreciated. Best regards, Yağız --

2 1

TM Module - Unfortunately error on sending to next hop occurred (477/TM)
by Ilie Soltanici 28 Jan '19

28 Jan '19

Hello, Can someone help me to understand this error given by TM Module? I have a Kamailio SIP Proxy running in front of a few Asterisk boxes. On average, he is processing 70-80 requests per second. The problem is that sometimes (90-100 times/day) - I see such errors in the logs: 500 I'm terribly sorry, server error occurred (1/SL) 477 Unfortunately error on sending to next hop occurred (477/TM) Trying to investigate this error - I found that this is happening randomly and for INVITES coming from the Asterisk Box. For ex, the INVITE below: 192.168.180.10 - Kamailio Server 192.168.180.36 - Asterisk Server INVITE sip:1001@192.168.180.10:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.180.36:5060;branch=z9hG4bK4624ab4e;rport Max-Forwards: 70 From: "Anonymous" <sip:anonymous@192.168.180.10>;tag=as11bed8a6 To: <sip:1001@192.168.180.10:5060> Contact: <sip:anonymous@192.168.180.36:5060> Call-ID: 0ea8535d3a5ecaa6432912a2566c807f(a)192.168.180.10 CSeq: 102 INVITE User-Agent: MYCOMPANY Date: Mon, 28 Jan 2019 16:01:56 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Content-Type: application/sdp Content-Length: 251 v=0 o=SIP 2139556641 2139556641 IN IP4 192.168.180.36 s=MYCOMPANY PBX c=IN IP4 192.168.180.36 t=0 0 m=audio 14674 RTP/AVP 8 0 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=sendrecv Kamailio is replying back with 100 Trying and then with 500/477 errors: SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.180.36:5060 ;branch=z9hG4bK4624ab4e;rport=5060;received=192.168.180.36 From: "Anonymous" <sip:anonymous@192.168.180.10>;tag=as11bed8a6 To: <sip:1001@192.168.180.10:5060> Call-ID: 0ea8535d3a5ecaa6432912a2566c807f(a)192.168.180.10 CSeq: 102 INVITE Server: MYCOMPANY SBC Content-Length: 0 SIP/2.0 500 I'm terribly sorry, server error occurred (1/SL) Via: SIP/2.0/UDP 192.168.180.36:5060 ;branch=z9hG4bK4624ab4e;rport=5060;received=192.168.180.36 From: "Anonymous" <sip:anonymous@192.168.180.10>;tag=as11bed8a6 To: <sip:1001@192.168.180.10:5060>;tag=9dd61ff61e802d8e2bef5f14621ef3c2.2e93 Call-ID: 0ea8535d3a5ecaa6432912a2566c807f(a)192.168.180.10 CSeq: 102 INVITE Server: MYCOMPANY SBC Content-Length: 0 SIP/2.0 477 Unfortunately error on sending to next hop occurred (477/TM) Via: SIP/2.0/UDP 192.168.180.36:5060 ;branch=z9hG4bK4624ab4e;rport=5060;received=192.168.180.36 From: "Anonymous" <sip:anonymous@192.168.180.10>;tag=as11bed8a6 To: <sip:1001@192.168.180.10:5060>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-2e93 Call-ID: 0ea8535d3a5ecaa6432912a2566c807f(a)192.168.180.10 CSeq: 102 INVITE Server: MYCOMPANY SBC Content-Length: 0 And I cannot actually get what is wrong with this INVITE - and why Kamailio cannot process it? Other calls for the same extension are working fine, this is happening randomly and with different extensions. Load on the server is very low: [root@kamailio root]# nproc 8 [root@kamailio root]# uptime 17:49:15 up 8 days, 21:17, 6 users, load average: 0.66, 0.56, 0.52 [root@kamailio root]# free -m total used free shared buff/cache available Mem: 7981 4283 142 818 3556 2581 Swap: 6141 137 6004 [root@kamailio root]# ss -4 -n -l | grep 5060 udp UNCONN 0 0 192.168.180.10 :5060 *:* udp UNCONN 0 0 127.0.0.1:5060 *:* tcp LISTEN 0 128 192.168.180.10 :5060 *:* tcp LISTEN 0 128 127.0.0.1:5060 *:* In the kamailio logs I found that kamailio was able to get the contact address: kamailio[18168]: INFO: {INVITE (1) Contacts loaded for 1001} kamailio[18168]: INFO: {INVITE (1) t_next_contacts - Only one contact found for 1001, calling} kamailio[18168]: INFO: {INVITE (1) Next Hop: <192.168.180.211:3126>} I don't know how to reproduce this - I tried to disconnect the phone from the power source - and made a call to that extension, and it is giving timeouts - like it is supposed to be. What could be the problem and how I can fix it? Thank You.

1 0

Playing with Diameter - Error opening connection to :3868
by Steve Bucklin 28 Jan '19

28 Jan '19

Hello all, I am brand new to this list and I am also on a steep learning curve with Kamailio and Diameter.... so please be gentle as I am just starting! I am trying to look at the Diameter signaling and have a glimpse into the information passed. I have set up a compiled 5.2 on CentOS 7. I suspect that I am missing something obvious, but not sure what. I am seeing this error: INFO: cdp [peerstatemachine.c:525]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer peer_connect(): peer_connect(): Error opening connection to :3868 >Name or service not known It looks like the FQDN in the diameter.xml under 'peer' is not being resolved, as it is seeing port 3868? Any pointers would be greatly taken :-) Here is my diameter: <?xml version="1.0" encoding="UTF-8"?> <DiameterPeer FQDN="mra1.testservers.xxx" Realm="testservers.xxx" Vendor_Id="10415" Product_Name="CDiameterPeer" AcceptUnknownPeers="1" DropUnknownOnDisconnect="1" Tc="30" Workers="16" QueueLength="32" TransactionTimeout="5" SessionsHashSize="128" DefaultAuthSessionTimeout="3600" MaxAuthSessionTimeout="3600" > <peer FGDN="mra2.testservers.xxx" Realm="testservers.xxx" proto="sctp" port="3868"/> <Acceptor port="3868" bind="192.168.1.20"/> <Auth id="16777251" vendor="10415"/>  <SupportedVendor vendor="10415" /> </DiameterPeer> And here is what I am getting on the startup: Jan 28 14:19:35 telco-lon1-02 kamailio: INFO: <core> [core/tcp_main.c:4722]: init_tcp(): using epoll_lt as the io watch method (auto detected) Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22778]: INFO: <core> [main.c:2649]: main(): processes (at least): 29 - shm size: 67108864 - pkg size: 8388608 Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22778]: INFO: cdp [cdp_mod.c:240]: cdp_child_init(): CDiameterPeer child starting ... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22783]: INFO: cdp [worker.c:332]: worker_process(): [1] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22778]: INFO: cdp [cdp_mod.c:242]: cdp_child_init(): ... CDiameterPeer child started Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22790]: INFO: cdp [worker.c:332]: worker_process(): [8] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22784]: INFO: cdp [worker.c:332]: worker_process(): [2] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22786]: INFO: cdp [worker.c:332]: worker_process(): [4] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22793]: INFO: cdp [worker.c:332]: worker_process(): [11] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22794]: INFO: cdp [worker.c:332]: worker_process(): [12] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22796]: INFO: cdp [worker.c:332]: worker_process(): [14] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22788]: INFO: cdp [worker.c:332]: worker_process(): [6] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22799]: INFO: cdp [receiver.c:455]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22799]: INFO: cdp [receiver.c:188]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [] Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22799]: INFO: cdp [receiver.c:460]: receiver_process(): receiver_process(): [] Receiver process starting up... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22791]: INFO: cdp [worker.c:332]: worker_process(): [9] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22792]: INFO: cdp [worker.c:332]: worker_process(): [10] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22785]: INFO: cdp [worker.c:332]: worker_process(): [3] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22787]: INFO: cdp [worker.c:332]: worker_process(): [5] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22795]: INFO: cdp [worker.c:332]: worker_process(): [13] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22782]: INFO: cdp [worker.c:332]: worker_process(): [0] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22789]: INFO: cdp [worker.c:332]: worker_process(): [7] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22797]: INFO: cdp [worker.c:332]: worker_process(): [15] Worker process started... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22798]: INFO: cdp [receiver.c:455]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22798]: INFO: cdp [receiver.c:460]: receiver_process(): receiver_process(): [] Receiver process starting up... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22800]: INFO: cdp [acceptor.c:81]: acceptor_process(): Acceptor process starting up... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22800]: WARNING: cdp [tcp_accept.c:121]: create_socket(): create_socket(): Trying to open/bind/listen on 192.168.1.20 port 3868 Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22800]: WARNING: cdp [tcp_accept.c:146]: create_socket(): create_socket(): Successful socket open/bind/listen on 192.168.1.20 port 3868 Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22800]: INFO: cdp [acceptor.c:95]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22801]: INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... Jan 28 14:19:35 telco-lon1-02 journal: [Diameter Routing Agent][22802]: INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) Jan 28 14:19:36 telco-lon1-02 journal: [Diameter Routing Agent][22801]: INFO: cdp [peerstatemachine.c:525]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer Jan 28 14:19:36 telco-lon1-02 journal: [Diameter Routing Agent][22801]: WARNING: cdp [receiver.c:866]: peer_connect(): peer_connect(): Error opening connection to :3868 >Name or service not known Thanks, Steve

2 2

database reconnection db_unixodbc
by Karthik Srinivasan 27 Jan '19

27 Jan '19

Hello, I am testing how kamailio reacts to various database conditions. One such condition is if the database engine is simply shut down (that is, database server process no longer running, tcp listening socket closed, etc...) I am utilizing the db_unixodbc module to connect to an Informix database engine. I am currently running on Kamailio version 5.0. I have a test query that executes against the database engine every 10 seconds. Here is what i have noticed if i shut down the database engine at some point after i run Kamailio. the first test query that attempts to run against the db engine fails; it tries to reconnect and fails. The second test query (10 seconds after the 1st) results in a SIG_CHILD and shuts down the entire Kamailio process. Has anyone experienced this? Is there a solution to this? Ideally the second query should also fail and return gracefully; and ideally queries continue to fail until the database engine is back up. See logs below: Jan 17 20:07:25 [29297]: INFO: (s) SQL query: FIRST TEST QUERY Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [dbase.c:135]: db_unixodbc_submit_query(): rv=-1. Query= FIRST TEST QUERY Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [connection.c:220]: db_unixodbc_extract_error(): unixodbc:SQLExecDirect=08S01:1:-11020:[Informix][Informix ODBC Driver]Communication link failure. Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [dbase.c:59]: reconnect(): Attempting DB reconnect Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [dbase.c:74]: reconnect(): failed to connect Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [connection.c:220]: db_unixodbc_extract_error(): unixodbc:SQLDriverConnect=08002:1:0:[unixODBC][Driver Manager]Connection name in use Jan 17 20:07:25 [29297]: ERROR: db_unixodbc [connection.c:220]: db_unixodbc_extract_error(): unixodbc:SQLDriverConnect=HY010:2:-11067:[Informix][Informix ODBC Driver]Function sequence error. Jan 17 20:07:25 [29297]: ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query Jan 17 20:07:25 [29297]: ERROR: sqlops [sql_api.c:265]: sql_do_query(): cannot do the query FIRST TEST QUERY Jan 17 20:07:25 [29297]: INFO: (s) [123] SQL ret: fail (-1) Jan 17 20:07:25 [29297]: INFO: (s) [123] SQL res: no rows Jan 17 20:07:35 [29297]: INFO: (s) [123] SQL query: 10 seconds later the SECOND TEST QUERY (it's the same query as the first one) Jan 17 20:07:35 [29301]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 28 Jan 17 20:07:35 [29283]: ALERT: <core> [main.c:744]: handle_sigs(): child process 29297 exited by a signal 11 Jan 17 20:07:35 [29283]: ALERT: <core> [main.c:747]: handle_sigs(): core was not generated Jan 17 20:07:35 [29283]: INFO: <core> [main.c:759]: handle_sigs(): terminating due to SIGCHLD Jan 17 20:07:35 [29301]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29295]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29291]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29288]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29300]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29284]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29286]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29293]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29289]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29287]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29292]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29296]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29298]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29299]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29285]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29294]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29290]: INFO: <core> [main.c:814]: sig_usr(): signal 15 received Jan 17 20:07:35 [29283]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Thank you, Karthik

2 5

Why kamailio can not be a consumer of RabbitMQ?
by CuiGang 26 Jan '19

26 Jan '19

Hello every one. I noticed that module RABBITMQ just implements the publish functions. It means kamailio can only as a producer of RabbitMQ. My question is Why RABBITMQ module not implement consumer functions? As NSQ, let kamailio can be a consumer receive messages from RabbitMQ. Regards. CuiGang cuigang0120(a)aliyun.com

2 1

DMQ errors
by Aleksandar Sosic 25 Jan '19

25 Jan '19

Hi, when I have only one node and dmq enabled I've got this errors: ``` 17(45) ERROR: dmq [notification_peer.c:337]: add_server_and_notify(): error adding notification node 17(45) ERROR: dmq [dmq_funcs.c:516]: ping_servers(): cannot retrieve initial nodelist from sip:dmq-router-service.alex.svc.cluster.local:5062 ``` On the second node booting after this one I don't get any of these errors. Is there any flag/option to turn off this error on the `cannot retrieve initial nodelist` in case I have only one node for a period of time? Thanks, -- Aleksandar Sosic linkedin.com/in/alexsosic/ mail: alex.sosic(a)evosip.cloud

2 2

Re: [SR-Users] kamailio-lb fails after topos enabled.
by Daniel Tryba 25 Jan '19

25 Jan '19

On Fri, Jan 25, 2019 at 10:19:45AM -0300, Marcos Pytel wrote: > Could you help me to catch the coredump file? Please keep the mailinglist in the loop. > When I execute bt full the systems shows "no symbols". What package i need to perform it? I don't know what the sipwise config is, but it if is (anything like) debian the normal kamailio package is strippped of debugging symbols. You'll need to install the debug package (kamailio-dbg in debian).

1 0

kamailio-lb fails after topos enabled.
by Marcos Pytel 25 Jan '19

25 Jan '19

Hi team! I'm using Kamailio version: kamailio 5.1.6 (x86_64/linux). When I enabled topos, after a few minutes i get this erros in the log file and the LB Service goes down.: Jan 24 13:20:21 sipwise lb[30130]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:21:36 sipwise lb[30132]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:29:06 sipwise lb[30135]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:31:36 sipwise lb[30133]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:34:41 sipwise lb[30130]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:43:06 sipwise lb[30134]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:45:21 sipwise lb[30136]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:47:06 sipwise lb[30132]: ERROR: ndb_redis [redis_client.c:903]: redisc_exec_argv(): Redis error: Server closed the connection Jan 24 13:47:21 sipwise lb[30136]: ERROR: topos [tps_storage.c:340]: tps_storage_link_msg(): bad sip message or missing Contact hdr Jan 24 13:47:35 sipwise lb[30163]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 23 Jan 24 13:47:35 sipwise lb[30066]: ALERT: <core> [main.c:738]: handle_sigs(): child process 30120 exited by a signal 6 Jan 24 13:47:35 sipwise lb[30066]: ALERT: <core> [main.c:741]: handle_sigs(): core was generated I attached the coredump file. I tried to get bt full but i think that i need something else to catch it. Thank you! Marcos.

2 2

ERROR while using KEMI - Python
by Prabhat Kumar 25 Jan '19

25 Jan '19

Hi, I am getting this error message while starting kamailio. Enviroment: OS- Ubuntu 16.04.5 LTS (Xenial Xerus) python 2.7 ERROR: app_python [app_python_mod.c:164]: mod_init(): failed to load python script ERROR: <core> [core/sr_module.c:990]: init_mod(): Error while initializing module app_python (/usr/local/lib64/kamailio/modules/app_python.so)

2 2

Error while installing kamailio
by Prabhat Kumar 25 Jan '19

25 Jan '19

I am getting this error while installing kamailio LD (gcc) [U kamcmd] kamcmd /usr/bin/ld: cannot find -lncurses collect2: error: ld returned 1 exit status ../../src//Makefile.rules:191: recipe for target 'kamcmd' failed make[3]: *** [kamcmd] Error 1 ERROR: make --no-print-directory -C ../../../utils/kamcmd install-if-newer failed ../../Makefile.modules:145: recipe for target 'install-utils' failed make[2]: *** [install-utils] Error 1 Makefile:511: recipe for target 'install-modules' failed make[1]: *** [install-modules] Error 1 make[1]: Leaving directory '/usr/local/src/kamailio-5.1/kamailio/src' Makefile:36: recipe for target 'install' failed make: *** [install] Error 2

2 1

Kamailio Ignore Re-INVITE
by Alvaro Araos 25 Jan '19

25 Jan '19

Hi, When receive a Re-INVITE with new Media IP and PORT, kamailio keeps sending RTP to the old IP PORT. Seems kamailio not update info to the rtpproxy. Saludos, ALVARO ARAOS MÉNDEZ Director de Tecnología en FONOIP +56 2 2947 9000 alvaro(a)fonoip.com | www.fonoip.com [1] Moisés Chacón 46, El Monte, RM Links: ------ [1] http://www.fonoip.com

2 1

presence_mwi body check problem
by Володимир Іванець 24 Jan '19

24 Jan '19

Hello! I'm trying to process PUBLISH on Kamailio (v. 5.2.1) but constantly getting "500 Server Internal Error" responce. For packet body: *Messages-Waiting: yes* *Message-Account: sip:100-test@172.16.30.151 <sip%3A100-test(a)172.16.30.151>* *Voice-Message: 1/2* ... debug output is: *kamailio: 2(27127) DEBUG: presence [event_list.c:348]: search_event(): start event= [message-summary/6]* *kamailio: 2(27127) DEBUG: presence [publish.c:351]: ki_handle_publish_uri(): SIP-If-Match header not found* *kamailio: 2(27127) DEBUG: presence [presentity.c:88]: generate_ETag(): etag= a.1548164100.27127.7.0 / 22* *kamailio: 2(27127) DEBUG: presence [publish.c:360]: ki_handle_publish_uri(): new etag = a.1548164100.27127.7.0* *kamailio: 2(27127) DEBUG: presence [publish.c:385]: ki_handle_publish_uri(): Expires header found, value= 16* *kamailio: 2(27127) ERROR: presence_mwi [add_events.c:110]: mwi_publ_handl(): check of body <Messages-Waiting: yes* *kamailio: Message-Account: sip:100-test@172.16.30.151 <sip%3A100-test(a)172.16.30.151>* *kamailio: Voice-Message: 1/2* *kamailio: > failed at character number 22* *kamailio: 2(27127) ERROR: presence [publish.c:480]: ki_handle_publish_uri(): in event specific publish handling* I'm not sure, but it appears to me that check in line 95 from https://github.com/kamailio/kamailio/blob/5.2/src/modules/presence_mwi/add_… is not passing. I was trying to add "\n" and "\r" to the end of each string but I always had failure on character number 22. Does anyone know how exactly PUBLISH packet body should look like? Thanks a lot!

2 4

Problem at Rx Interface - kamailio P-CSCF 5.1.6
by Valentin Christoph 23 Jan '19

23 Jan '19

Hi all, We are using kamailio 5.1.6, configured as P-CSCF, facing following problem. Please refer to the attached tshark trace, too. If during call setup (by simulated UAs) at the terminating P-CSCF the simulated PCRF rejects the Diameter AAR message (frame 46/47 at the attached trace), then the kamailio P-CSCF runs into a questionable behaviour. By calling the Rx_AAR() function in configuration, the processing of the 200 OK (frame 45) is suspended (by the ims_qos module) and then resumed with the receipt of the AAA message (frame 47). Now the ims_dialog module is called with the dlg_terminate("all", "reason") function, but the 200 OK has not yet been sent. The ims_dialog sends CANCEL downstream and 488 upstream. However, the 200 OK is sent additionally. We would rather have expected the ims_dialog module should send BYE in both directions. When we respond the CANCEL with 481 Call/Transaction does not exist (which we MUST according to RFC 3261), then we would expect the ims_dialog module at least now to react with BYE in both directions. Could you help? What's our misunderstanding? How could we proceed to get this issue fixed? Kind regards Christoph ____ Christoph VALENTIN Software Developer | R&D Core / SIP Core P +43 50 811 3785 | M +43 664 628 3785 christoph.valentin(a)kapsch.net<mailto:christoph.valentin@kapsch.net> Kapsch CarrierCom AG | Lehrbachgasse 11 | 1120 Vienna | Austria Company Register at: Commercial Court Vienna FN 223804 z | Registered Office Vienna | www.kapsch.net<http://www.kapsch.net/> [Kapsch Logo]<https://www.kapsch.net/> The information contained in this e-mail message is privileged and confidential and is for the exclusive use of the addressee. The person who receives this message and who is not the addressee, one of his employees or an agent entitled to hand it over to the addressee, is informed that he may not use, disclose or reproduce the contents thereof, and is kindly asked to notify the sender and delete the e-mail immediately.

1 1

MWI notification through pua.publish
by willy 23 Jan '19

23 Jan '19

Hello. Have anyone tried to use pua.publish to send MWI notification? Can it work at all? I'm sending request through jsonrpc server, but it is not dispatched by handle_publish. Thank you, Kirill

6 9

Maximum Number of Probed Gateways
by Duarte Rocha 23 Jan '19

23 Jan '19

Greetings, Is there a limitation to the number of Gateways probed by Dispatcher? I have several gateways configured to be probed, but the OPTIONS is only sent to the first 16? Is there a configuration regarding this? Thanks in advance, Duarte Rocha

2 2

Kamailio v5.1.6 crashes with rtpengine restarts
by Yufei Tao 23 Jan '19

23 Jan '19

Hi, I have been testing one Kamailio v5.1.6 instance with one rtpengine instance, using sipp playing media files at 40 cps (-r 40) with up to 1600 concurrent calls. During the load tests if rtpengine is pkill'ed/restarted a few times Kamailio would crash. It is quite repeatable and every time the backtrace from gdb points to the same place as shown below. However the same tests on Kamailio v5.0.7 with the same cfg files and the same rtpengine instance did not cause any crash. Here’s what I got from gdb backtrace for v5.1.6 using a dbg build: 2 core dump files: 1. UDP receiver processes 14483 {{{ [New LWP 14483] Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007fadfa824d8e in t_should_relay_response (Trans=0x7fadf4207730, new_code=200, branch=0, should_store=0x7ffd5038fce4, should_relay=0x7ffd5038fce0, cancel_data=0x7ffd5038fed0, reply=0x7fadfb545210) at t_reply.c:1282 1282 t_reply.c: No such file or directory. (gdb) bt #0 0x00007fadfa824d8e in t_should_relay_response (Trans=0x7fadf4207730, new_code=200, branch=0, should_store=0x7ffd5038fce4, should_relay=0x7ffd5038fce0, cancel_data=0x7ffd5038fed0, reply=0x7fadfb545210) at t_reply.c:1282 #1 0x00007fadfa829577 in relay_reply (t=0x7fadf4207730, p_msg=0x7fadfb545210, branch=0, msg_status=200, cancel_data=0x7ffd5038fed0, do_put_on_wait=1) at t_reply.c:1786 #2 0x00007fadfa82f54c in reply_received (p_msg=0x7fadfb545210) at t_reply.c:2537 #3 0x000000000054624b in do_forward_reply (msg=0x7fadfb545210, mode=0) at core/forward.c:747 #4 0x0000000000547e4c in forward_reply (msg=0x7fadfb545210) at core/forward.c:852 #5 0x000000000058e186 in receive_msg ( buf=0xa595a0 <buf> "SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP 192.168.70.102;branch=z9hG4bKa042.afac8eb973f1dfad7a549af0ab1a8ccc.0, SIP/2.0/UDP 192.168.60.80:5060;branch=z9hG4bK-3750-978-0\r\nFrom: sipp < sip:Customer68@192.168.60.8"..., len=888, rcv_info=0x7ffd50390480) at core/receive.c:364 #6 0x00000000004af6b1 in udp_rcv_loop () at core/udp_server.c:554 #7 0x00000000004246ac in main_loop () at main.c:1619 #8 0x000000000042bd5c in main (argc=13, argv=0x7ffd50390b38) at main.c:2638 }}} 2. Main process 14468 {{{ [New LWP 14468] Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.'. Program terminated with signal SIGABRT, Aborted. #0 0x00007fadfbc77428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007fadfbc77428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #1 0x00007fadfbc7902a in __GI_abort () at abort.c:89 #2 0x000000000041a029 in sig_alarm_abort (signo=14) at main.c:646 #3 <signal handler called> #4 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:37 #5 0x00007fadf354e67d in futex_get (lock=0x7fadf3e94e50) at ../../core/parser/../mem/../futexlock.h:121 #6 0x00007fadf3561113 in mod_destroy () at rtpengine.c:1810 #7 0x000000000055132b in destroy_modules () at core/sr_module.c:832 #8 0x0000000000418c9f in cleanup (show_status=1) at main.c:521 #9 0x000000000041a313 in shutdown_children (sig=15, show_status=1) at main.c:663 #10 0x000000000041cfa5 in handle_sigs () at main.c:768 #11 0x0000000000425fb5 in main_loop () at main.c:1752 #12 0x000000000042bd5c in main (argc=13, argv=0x7ffd50390b38) at main.c:2638 }}} The parameters for rtpengine: {{{ loadmodule "rtpengine.so" modparam("rtpengine", "db_url", "text:///usr/share/kamailio/dbtext/kamailio") modparam("rtpengine", "hash_table_size", 4) modparam("rtpengine", "setid_default", 1) modparam("rtpengine", "rtpengine_disable_tout", 20) modparam("rtpengine", "rtpengine_retr", 1) modparam("rtpengine", "setid_avp", "$avp(setid)") modparam("rtpengine", "rtp_inst_pvar", "$avp(rtpInstance)") modparam("rtpengine", "rtpengine_tout_ms", 1000) modparam("rtpengine", "read_sdp_pv", "$var(sdpToRtpengine)") modparam("rtpengine", "write_sdp_pv", "$var(sdpFromRtpengine)") }}} I'm using a simplified kamailio.cfg from installation, and here are calls to rtpengine: {{{ ... route[INVITE] { $var(sdpToRtpengine) = $rb; $var(ret) = rtpengine_manage("direction=dirty direction=clean ICE=remove"); xlog("L_INFO", "$ci INVITE: rtpengine chosen: $avp(rtpInstance)"); remove_body(); replace_body(".*", $var(sdpFromRtpengine)); t_on_reply("RESPONSE"); route(RELAY); } onreply_route[RESPONSE] { $var(sdpToRtpengine) = $rb; $var(ret) = rtpengine_manage("direction=clean direction=dirty ICE=remove"); remove_body(); replace_body(".*", $var(sdpFromRtpengine)); xlog("L_INFO", "$ci RESPONSE: $rm - $rs $rr, cseq=$cs, by [$hdr(Server)], from $si:$sp"); } ... }}} When rtpengine is down for a couple of seconds, there were a lot of SIP retransmissions and timeouts. Doing a netstat and I can see Kamailio’s receive buffer is quite filled up. Please let me know if more information is needed. Thank you! Cheers, Yufei

2 3

Additional Param Check in ConsumeCredential Auth
by Prabhat Kumar 22 Jan '19

22 Jan '19

Hi, I want to check additional param in Auth module. For. ex., other than username and secret , i want to validate user by its email address. How can i do that? Regards, Prabhat Kumar

4 8

How to send NOTIFY to UA
by CuiGang 22 Jan '19

22 Jan '19

Hello, Does any one know, how to send a NOTIFY message to a special UA? Why I need to do this? I’m using kamailio integration with Yealink IP Phone. Yealink IP Phone can perform some specified action immediately by accepting a SIP NOTIFY message with the “Event: ACTION-URI” header. I want to use RPC or HTTP or NSQ or some other interface trigger kamailio ROUTE make a NOTIFY message and send it to a special Yealink IP Phone. Thanks! Regards, CuiGang cuigang0120(a)aliyun.com

2 2

Empty presence event NOTIFY
by EDUARDO PASCUAL GALLEGO 22 Jan '19

22 Jan '19

Hello: I am testing the Kamailio Presence Server. I can see when the presence of an user agent expires then the server sends an empty NOTIFY without XML document. Also, when the server receives a SUBSCRIBE it sends a NOTIFY with XML if the UA is present but it sends an empty NOTIFY when the UA is not present. However, if the presence server receive a PUBLISH with Expires header equals cero then it sends a NOTIFY with XML document. I do not understant why it sends empty NOTIFY messages. Especially if the user agent is not present. I tested 4.4.7 version and I can see that it is the best version, because I tested 5.1.6 and 5.2.0 versions and I could see that they sends empty NOTIFY messages even the user agent is present. Then I am using 4.4.7 version, an I am considering as no present when a NOTIFY message is empty. But I think it is not RFC3856 compliant. Kamailio presence server es configured like that: #!ifdef WITH_PRESENCE # ----- presence params ----- modparam("presence", "db_url", DBURL) # ----- presence_xml params ----- modparam("presence_xml", "db_url", DBURL) modparam("presence_xml", "force_active", 1) #!endif Can anyone help me? Thank you very much in advance. *Eduardo Pascual Gallego* *Ingeniero de Desarrollo / Development Engineer.* T. +34 91 807 39 99 · eduardo.pascual(a)nucleocc.com <https://www.nucleocc.com/> *Núcleo HQ* C/Vía de los Poblados, 7 28033 Madrid (Spain) <https://www.google.es/maps/place/DF+N%C3%BAcleo/@40.4747861,-3.6352894,17z/…> *Núcleo USA* 100 Crescent Dr, STE.700 75201 Dallas, Texas (USA) <https://www.google.es/maps/place/100+Crescent+Ct,+Dallas,+TX+75201,+EE.+UU.…> *www.nucleocc.com* <https://www.nucleocc.com/> Este correo electrónico y cualquier fichero adjunto al mismo contienen información de carácter confidencial exclusivamente dirigida a su destinatario o destinatarios. En el caso de haber recibido este correo electrónico por error, le indicamos que no le está permitido por ley la lectura, copia y uso del mismo . En tal caso, le rogamos notifique lo antes posible esta circunstancia mediante reenvío a la dirección electrónica del remitente y destruya el mensaje. Antes de imprimir este correo, piense en su responsabilidad y compromiso con el medio ambiente. -- Advertencia | Este mensaje está destinado únicamente a su destinatario y puede contener información CONFIDENCIAL y/o protegida por secreto profesional cuya revelación está prohibida por la ley. Si usted no es el destinatario a quien va dirigido le informamos que la lectura, la distribución, el copiado o la revelación de este mensaje están prohibidos por la ley. Si ha recibido este mensaje por error le solicitamos que nos notifique por e-mail su recepción equivocada y que borre este mensaje sin conservar copia, al tiempo que le pedimos disculpas por las molestias que le haya ocasionado. El servicio de e-mail por internet no garantiza ni la confidencialidad ni la integridad o la recepción de los mensajes por lo que nuestra Firma no asume ninguna responsabilidad portales circunstancias. De conformidad con lo previsto en el REGLAMENTO (UE) 2016/679 DEL PARLAMENTO EUROPEO Y DEL CONSEJO de 27 de abril de 2016, a continuación facilitamos la información básica en relación con la protección de los datos personales que nos sean suministrados: Responsable: NUCLEO DE COMUNICACIONES Y CONTROL, SLU Finalidad: Cumplimiento de las relaciones jurídicas y obligaciones legales asociadas. Legitimación: Ejecución contractual y cumplimiento de nuestras obligaciones. No se cederán o transferirán los datos personales a terceros, salvo siguiendo sus instrucciones o por obligación legal. Ejercicio de derechos de acceso, rectificación y supresión de los datos, así como el ejercicio de otros derechos, tal y como se explica en la información adicional. Puede consultar la información adicional y detallada en el siguiente enlace a nuestra política de privacidad y *Tratamiento de Datos Personales* <http://www.nucleocc.com/paginas_informativas/proteccin_de_datos_de_carcter_…>*.*

1 1

uri_param function
by Andrew Chen 21 Jan '19

21 Jan '19

Hi all, Question. I'm executing uri_param() function to look for our customized Request-URI parameters generated by our client. However, it keeps saying the param is not there even though my client logs shows the param was generated. Below is an example Request-URI from a test call I made: sips:<some long string>@sjomainkamavip50.fuzemeeting.com:443;FN= sjomainfn92.a.fuzemeeting.com;BR=sjomainfn91.a.fuzemeeting.com;AK=<some key>;transport=wss" And here is my line of code to check it: if(uri_param("AK") ||uri_param("ak")) { xlog("L_INFO", "[CSeq $cs] AK value detected"); } else { xlog("L_INFO", "[CSeq $cs] AK value not detected. Aborting call"); drop(); } Am I misusing this function somehow? I'm running 5.1.2. Thanks Regards, -- Andy Chen -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

2 4

Radius Accounting with Kamailio 5.1 (On-line Charging)
by Yazar Lwin 21 Jan '19

21 Jan '19

Hi All, I've Kamailio 5.1 running with Mysql as local DB. I've configured Siremis as well. I completed accounting configuration as per the instruction. Now I can see the accounting list, CDR list and as well as missed calls in Siremis But I can't integrate with free radius server to trigger the accounting, just like Diameter transaction in IMS. Kindly advise which doc I should check. I would like to enable Radius server as an online charging. Best regards Yazar

2 3

Dynamic UAC Registration
by Mack Hendricks 20 Jan '19

20 Jan '19

Hey All, So, I want to use the UAC module to handle Digest Auth to upstream carriers. But, I don’t know which carrier will be selected until another module (dRouting in this case) tells the logic which carrier to use. I can see in the logs that the uac_auth function can capture the Auth Realm. But, I need to access it from the Kamailio script so that I can lookup the credentials for that realm and then call uac_auth. I’ve tried getting the info from $ar, but that gives me the realm of the inbound request versus the realm of the upstream carrier. Also, I’ve tried using $T_rpl($ar), but that returns 0. Here’s my logic from the Kamailio file: if(t_check_status("401|407")) { $var(reply_realm) = $T_rpl($ar); $var(query)="select auth_username,auth_password from uacreg where realm='" + $var(reply_realm) + "'"; sql_xquery("cb","$var(query)","rb"); xlog("L_DEBUG","[MANAGE_FAILURE: Proxy Auth]: The query is $var(query) auth realm is $var(reply_realm) and the user name is $xavp(rb=>auth_username)"); $avp(auser) = $xavp(rb=>auth_username); $avp(apass) = $xavp(rb=>auth_password); uac_auth(); t_relay(); exit;` } A snippet of the log file is below: Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: exec: *** cfgtrace:failure_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=1616 a=63 n=assign Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: exec: *** cfgtrace:failure_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=1617 a=63 n=assign Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: exec: *** cfgtrace:failure_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=1618 a=24 n=uac_auth Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth.c:409]: uac_auth(): picked reply is 0x7f900cb7eaf0, code 407 Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth.c:225]: get_autenticate_hdr(): looking for header "Proxy-Authenticate" Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth.c:429]: uac_auth(): header found; body=<Digest realm="sip.flowroute.com", nonce="XERJMlxESAbDNCK3INmBfoET1GGxpcyr", qop="auth"> Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth_hdr.c:209]: parse_authenticate_body(): <realm>="sip.flowroute.com" state=2 Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth_hdr.c:209]: parse_authenticate_body(): <nonce>="XERJMlxESAbDNCK3INmBfoET1GGxpcyr" state=3 Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth_hdr.c:209]: parse_authenticate_body(): <qop>="auth" state=1 Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: DEBUG: uac [auth.c:449]: uac_auth(): no credential for realm "sip.flowroute.com" Jan 20 10:05:58 dsiprouter /usr/sbin/kamailio[2871]: exec: *** cfgtrace:failure_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=1619 a=24 n=t_relay Thanks in advance for any help Mack Hendricks dSIPRouter

4 4

Kamailio Docker 5.2.1
by Grant Bagdasarian 20 Jan '19

20 Jan '19

Hello, I was wondering when the Kamailio Docker image will be updated to use 5.2.1 and be available through the Docker public repository ( https://hub.docker.com/r/kamailio/kamailio)? Thanks and regards, Grant

4 10

Mysql
by Nicolas Breuer 20 Jan '19

20 Jan '19

Hello, Working on sip_trace table produce this error WARNING: db_mysql [km_res.c:142]: db_mysql_get_columns(): unhandled data type column (Msg_text) type id (250), use DB1_STRING as default

5 16

segfault error - process stopped
by AL RSM 20 Jan '19

20 Jan '19

Hi We are running Kamailio 3.7 on our production servers. The Kamailio process stopped running on one of the 4 servers. Log shows "segfault error". No core file generated. Any suggestion on how to verify the issue would be appreciated. kernel: [63574875.776269] kamailio[1558]: segfault at 0 ip 000000000055933a sp 00007fffd4ca6700 error 4 in kamailio[400000+211000] /usr/sbin/kamailio[1545]: ALERT: <core> [main.c:785]: child process 1558 exited by a signal 11 /usr/sbin/kamailio[1545]: ALERT: <core> [main.c:788]: core was not generated CRON[21436]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Thanks, AL

3 2

Mid-Registrar
by Mark Thomas 20 Jan '19

20 Jan '19

I’m currently and OpenSIPS user and I really want to be able to use their software on OpenWRT, but I have found it really hard to cross-compile. Is there a possibility to run Kamailio as a mid-registrar? For my application this is required, and I haven’t been able to find any information on this.

3 3

handling BYEs generated by dialog-timeout
by * Paolo Visintin - evosip.cloud 19 Jan '19

19 Jan '19

Hello! I'm wondering if someone have experience in changing $du on local kamailio generated packets (like BYE generated at the dialog-timeout) I'm trying to manipulate in `event_route[tm:local-request]` with no success. In the end I have it working using the `forward()` function and then using `exit;` but in this case instead of having 2 BYEs , kamailio sends 4 BYEs (2 with original $du, 2 with new $du) this an example : event_route[tm:local-request] { if ($rm == "BYE") { route(SELECT_OUTBOUND_PROXY); forward(); exit; } } I'm using a kamailio proxy on top with no record-route (we want to have multiple instances of proxy that can change ip address). Thanks in advance! Paolo

2 6

Dev documentation on implementing event_route events in custom module
by Ivan Ribakov 19 Jan '19

19 Jan '19

Is there any documentation for module developers that lays out API for registering and triggering events from a custom Kamailio module (similar to https://kamailio.org/docs/modules/5.0.x/modules/tm.html#tm.event_routes)? I have been referring to https://www.kamailio.org/docs/kamailio-devel-guide/ <https://www.kamailio.org/docs/kamailio-devel-guide/> up until now but it doesn’t seem to cover event_routes. Thanks in advance, Ivan

3 5

Diameter (CDP) crashes on startup. ERROR: cdp [peerstatemachine.c:634]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket
by Denys Pozniak 18 Jan '19

18 Jan '19

Hello! Please help me to find the issue with CDP module as it blocks Kamailio to start. [root@10-10-10-10 kamailio]# cat diameter.xml <?xml version="1.0" encoding="UTF-8"?> <DiameterPeer FQDN="10-10-10-10.ams.proxy.dev" Realm="proxy.dev" Product_Name="Diameter Credit Control" Vendor_Id="10415" AcceptUnknownPeers="1" DropUnknownOnDisconnect="1" Tc="30" Workers="4" QueueLength="32"> <Peer FQDN="dev-diameter-1.ams.proxy.dev" Realm="proxy.dev" port="3868"/> <Acceptor port="3868" bind="10.10.10.10"/> <Auth id="16777216" vendor="10415"/> <Acct id="16777216" vendor="0" /> <Auth id="16777216" vendor="10415"/> <Auth id="16777216" vendor="0" /> <SupportedVendor vendor="10415"/> <Realm name="proxy.dev"> <Route FQDN="dev-diameter-1.ams.proxy.dev" metric="1"/> </Realm> <DefaultRoute FQDN="dev-diameter-1.ams.proxy.dev" metric="10"/> </DiameterPeer> 38(7825) INFO: cdp [worker.c:332]: worker_process(): [1] Worker process started... 37(7824) INFO: cdp [worker.c:332]: worker_process(): [0] Worker process started... 39(7826) INFO: cdp [worker.c:332]: worker_process(): [2] Worker process started... 40(7827) INFO: cdp [worker.c:332]: worker_process(): [3] Worker process started... 41(7828) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... 41(7828) INFO: cdp [receiver.c:455]: receiver_process(): receiver_process(): [] Receiver process starting up... 42(7829) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [dev-diameter-1.ams.proxy.dev] Receiver process doing init on new process... 42(7829) INFO: cdp [receiver.c:184]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [dev-diameter-1.ams.proxy.dev] 42(7829) INFO: cdp [receiver.c:455]: receiver_process(): receiver_process(): [dev-diameter-1.ams.proxy.dev] Receiver process starting up... 43(7830) INFO: cdp [acceptor.c:81]: acceptor_process(): Acceptor process starting up... 0(7787) INFO: cdp [cdp_mod.c:244]: cdp_child_init(): ... CDiameterPeer child started 43(7830) WARNING: cdp [tcp_accept.c:121]: create_socket(): create_socket(): Trying to open/bind/listen on 10.10.10.10 port 3868 43(7830) WARNING: cdp [tcp_accept.c:146]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.10.10.10 port 3868 43(7830) INFO: cdp [acceptor.c:95]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 44(7831) INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... [root@10-10-10-10 kamailio]# 44(7831) INFO: cdp [peerstatemachine.c:525]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer dev-diameter-1.ams.proxy.dev 44(7831) INFO: cdp [receiver.c:869]: peer_connect(): peer_connect(): Trying to connect to 10.10.10.20 port 3868 44(7831) INFO: cdp [receiver.c:937]: peer_connect(): peer_connect(): Peer dev-diameter-1.ams.proxy.dev:3868 connected 42(7829) ERROR: cdp [peerstatemachine.c:634]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket 42(7829) CRITICAL: <core> [core/mem/q_malloc.c:149]: qm_debug_check_frag(): BUG: qm: prev. fragm. tail overwritten(0, abcdefed)[0x7f3ecb7ef018:0x7f3ecb7ef050]! Memory allocator was called from cdp: diameter_avp.c:365. Fragment marked by cdp: diameter_avp.c:142. Exec from core/mem/q_malloc.c:504. 45(7832) CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 52 0(7787) ALERT: <core> [main.c:739]: handle_sigs(): child process 7829 exited by a signal 6 0(7787) ALERT: <core> [main.c:742]: handle_sigs(): core was generated 0(7787) INFO: <core> [main.c:764]: handle_sigs(): terminating due to SIGCHLD DNS record dev-diameter-1.ams.proxy.dev is pointed to 10.10.10.20 NU gdb (GDB) Red Hat Enterprise Linux 7.6.1-114.el7 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html > This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/sbin/kamailio...Reading symbols from /usr/lib/debug/usr/sbin/kamailio.debug...done. done. [New LWP 7829] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `kamailio -f kamailio.cfg -DDDD -E'. Program terminated with signal 6, Aborted. #0 0x00007f3ed7dc0207 in raise () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install glibc-2.17-260.el7.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-34.el7.x86_64 libcom_err-1.42.9-13.el7.x86_64 libgcc-4.8.5-36.el7.x86_64 libselinux-2.5-14.1.el7.x86_64 libstdc++-4.8.5-36.el7.x86_64 libxml2-2.9.1-6.el7_2.3.x86_64 mariadb-libs-5.5.60-1.el7_5.x86_64 openssl-libs-1.0.2k-16.el7.x86_64 pcre-8.32-17.el7.x86_64 xz-libs-5.2.2-1.el7.x86_64 zlib-1.2.7-18.el7.x86_64 (gdb) bt #0 0x00007f3ed7dc0207 in raise () from /lib64/libc.so.6 #1 0x00007f3ed7dc18f8 in abort () from /lib64/libc.so.6 #2 0x000000000067d5f7 in qm_debug_check_frag (qm=0x7f3ecb4d0000, f=0x7f3ecb7ef018, file=0x7f3ed068d932 "cdp: diameter_avp.c", line=365, efile=0x7df137 "core/mem/q_malloc.c", eline=504) at core/mem/q_malloc.c:151 #3 0x000000000068077a in qm_free (qmp=0x7f3ecb4d0000, p=0x7f3ecb7ef050, file=0x7f3ed068d932 "cdp: diameter_avp.c", func=0x7f3ed068f418 <__FUNCTION__.7016> "AAAFreeAVP", line=365, mname=0x7f3ed068d760 "cdp") at core/mem/q_malloc.c:504 #4 0x000000000068a2d6 in qm_shm_free (qmp=0x7f3ecb4d0000, p=0x7f3ecb7ef050, file=0x7f3ed068d932 "cdp: diameter_avp.c", func=0x7f3ed068f418 <__FUNCTION__.7016> "AAAFreeAVP", line=365, mname=0x7f3ed068d760 "cdp") at core/mem/q_malloc.c:1268 #5 0x00007f3ed06691c8 in AAAFreeAVP (avp=0x7ffd86bdd300) at diameter_avp.c:365 #6 0x00007f3ed0636d66 in AAAFreeAVPList (avpList=0x7f3ecb7eea40) at diameter_msg.c:396 #7 0x00007f3ed0637123 in AAAFreeMessage (msg=0x7ffd86bdd3b0) at diameter_msg.c:416 #8 0x00007f3ed06088ec in Process_CEA (p=0x7f3ecb7a00d8, cea=0x7f3ecb7ee9f0) at peerstatemachine.c:804 #9 0x00007f3ed0601ab1 in sm_process (p=0x7f3ecb7a00d8, event=I_Rcv_CEA, msg=0x7f3ecb7ee9f0, peer_locked=0, sock=8) at peerstatemachine.c:166 #10 0x00007f3ed0659825 in receive_message (msg=0x7f3ecb7ee9f0, sp=0x7f3ed76feec8) at receiver.c:1128 #11 0x00007f3ed064f295 in do_receive (sp=0x7f3ed76feec8) at receiver.c:593 #12 0x00007f3ed0653068 in receive_loop (original_peer=0x7f3ecb7a00d8) at receiver.c:800 #13 0x00007f3ed064c7c6 in receiver_process (p=0x7f3ecb7a00d8) at receiver.c:459 #14 0x00007f3ed05fd7de in diameter_peer_start (blocking=0) at diameter_peer.c:289 #15 0x00007f3ed05ef9b1 in cdp_child_init (rank=0) at cdp_mod.c:243 #16 0x0000000000544e31 in init_mod_child (m=0x7f3ed7630170, rank=0) at core/sr_module.c:943 #17 0x0000000000544ad3 in init_mod_child (m=0x7f3ed7630e90, rank=0) at core/sr_module.c:939 #18 0x0000000000544ad3 in init_mod_child (m=0x7f3ed7631290, rank=0) at core/sr_module.c:939 #19 0x0000000000544ad3 in init_mod_child (m=0x7f3ed7631700, rank=0) at core/sr_module.c:939 #20 0x0000000000545205 in init_child (rank=0) at core/sr_module.c:970 #21 0x0000000000424f85 in main_loop () at main.c:1701 #22 0x000000000042b87e in main (argc=5, argv=0x7ffd86bde218) at main.c:2638 (gdb) bt full #0 0x00007f3ed7dc0207 in raise () from /lib64/libc.so.6 No symbol table info available. #1 0x00007f3ed7dc18f8 in abort () from /lib64/libc.so.6 No symbol table info available. #2 0x000000000067d5f7 in qm_debug_check_frag (qm=0x7f3ecb4d0000, f=0x7f3ecb7ef018, file=0x7f3ed068d932 "cdp: diameter_avp.c", line=365, efile=0x7df137 "core/mem/q_malloc.c", eline=504) at core/mem/q_malloc.c:151 __FUNCTION__ = "qm_debug_check_frag" #3 0x000000000068077a in qm_free (qmp=0x7f3ecb4d0000, p=0x7f3ecb7ef050, file=0x7f3ed068d932 "cdp: diameter_avp.c", func=0x7f3ed068f418 <__FUNCTION__.7016> "AAAFreeAVP", line=365, mname=0x7f3ed068d760 "cdp") at core/mem/q_malloc.c:504 qm = 0x7f3ecb4d0000 f = 0x7f3ecb7ef018 size = 140726864040496 next = 0x7df14b prev = 0x7f3ed067f329 __FUNCTION__ = "qm_free" #4 0x000000000068a2d6 in qm_shm_free (qmp=0x7f3ecb4d0000, p=0x7f3ecb7ef050, file=0x7f3ed068d932 "cdp: diameter_avp.c", func=0x7f3ed068f418 <__FUNCTION__.7016> "AAAFreeAVP", line=365, mname=0x7f3ed068d760 "cdp") at core/mem/q_malloc.c:1268 No locals. #5 0x00007f3ed06691c8 in AAAFreeAVP (avp=0x7ffd86bdd300) at diameter_avp.c:365 __FUNCTION__ = "AAAFreeAVP" #6 0x00007f3ed0636d66 in AAAFreeAVPList (avpList=0x7f3ecb7eea40) at diameter_msg.c:396 avp_t = 0x7f3ecb7ef050 avp = 0x7f3ecb7eef40 #7 0x00007f3ed0637123 in AAAFreeMessage (msg=0x7ffd86bdd3b0) at diameter_msg.c:416 __FUNCTION__ = "AAAFreeMessage" #8 0x00007f3ed06088ec in Process_CEA (p=0x7f3ecb7a00d8, cea=0x7f3ecb7ee9f0) at peerstatemachine.c:804 avp = 0x7f3ecb7ef440 #9 0x00007f3ed0601ab1 in sm_process (p=0x7f3ecb7a00d8, event=I_Rcv_CEA, msg=0x7f3ecb7ee9f0, peer_locked=0, sock=8) at peerstatemachine.c:166 result_code = -798486160 next_event = 32574 msg_received = 0 __FUNCTION__ = "sm_process" #10 0x00007f3ed0659825 in receive_message (msg=0x7f3ecb7ee9f0, sp=0x7f3ed76feec8) at receiver.c:1128 avp1 = 0xd0684fc0 avp2 = 0x7f3ecb7eed10 __FUNCTION__ = "receive_message" #11 0x00007f3ed064f295 in do_receive (sp=0x7f3ed76feec8) at receiver.c:593 cnt = 184 n = 184 version = 1 dst = 0x7f3ecb7ef4f4 "" dmsg = 0x7f3ecb7ee9f0 __FUNCTION__ = "do_receive" #12 0x00007f3ed0653068 in receive_loop (original_peer=0x7f3ecb7a00d8) at receiver.c:800 rfds = {__fds_bits = {256, 0 <repeats 15 times>}} efds = {__fds_bits = {0 <repeats 16 times>}} tv = {tv_sec = 0, tv_usec = 999998} n = 1 max = 49 cnt = 1 msg = 0x0 sp = 0x7f3ed76feec8 sp2 = 0x7f3ed76feec8 p = 0x7f3ecb7a00d8 fd = 8 fd_exchange_pipe_local = 49 __FUNCTION__ = "receive_loop" #13 0x00007f3ed064c7c6 in receiver_process (p=0x7f3ecb7a00d8) at receiver.c:459 ---Type <return> to continue, or q <return> to quit--- __FUNCTION__ = "receiver_process" #14 0x00007f3ed05fd7de in diameter_peer_start (blocking=0) at diameter_peer.c:289 pid = 0 k = -1 p = 0x7f3ecb7a00d8 __FUNCTION__ = "diameter_peer_start" #15 0x00007f3ed05ef9b1 in cdp_child_init (rank=0) at cdp_mod.c:243 __FUNCTION__ = "cdp_child_init" #16 0x0000000000544e31 in init_mod_child (m=0x7f3ed7630170, rank=0) at core/sr_module.c:943 __FUNCTION__ = "init_mod_child" #17 0x0000000000544ad3 in init_mod_child (m=0x7f3ed7630e90, rank=0) at core/sr_module.c:939 __FUNCTION__ = "init_mod_child" #18 0x0000000000544ad3 in init_mod_child (m=0x7f3ed7631290, rank=0) at core/sr_module.c:939 __FUNCTION__ = "init_mod_child" #19 0x0000000000544ad3 in init_mod_child (m=0x7f3ed7631700, rank=0) at core/sr_module.c:939 __FUNCTION__ = "init_mod_child" #20 0x0000000000545205 in init_child (rank=0) at core/sr_module.c:970 No locals. #21 0x0000000000424f85 in main_loop () at main.c:1701 i = 32 pid = 7821 si = 0x0 si_desc = "udp receiver child=31 sock=10.10.10.10:5060\000\177\000\000`\336\275\206\375\177\000\000A\307g\000\000\000\000\000`\202A\000\000\000\000\000ȖP\313>\177", '\000' <repeats 14 times>, "\001\000\000\000\260\336\275\206\375\177\000\000\234\240h\000\000\000\000\000 \243w\000\000\000\000\000H\361m\327>\177\000" nrprocs = 32 woneinit = 1 __FUNCTION__ = "main_loop" #22 0x000000000042b87e in main (argc=5, argv=0x7ffd86bde218) at main.c:2638 cfg_stream = 0x2b13020 c = -1 r = 0 tmp = 0x0 tmp_len = 0 port = 0 proto = 0 options = 0x758490 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 4201223303 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 4 n_lst = 0x0 p = 0x0 st = {st_dev = 19, st_ino = 82198, st_nlink = 2, st_mode = 16832, st_uid = 995, st_gid = 2, __pad0 = 0, st_rdev = 0, st_size = 60, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1547739314, tv_nsec = 582000000}, st_mtim = {tv_sec = 1547743303, tv_nsec = 194148453}, st_ctim = {tv_sec = 1547743303, tv_nsec = 194148453}, __unused = {0, 0, 0}} __FUNCTION__ = "main" (gdb) -- BR, Denys Pozniak

1 1

event_route[usrloc:contact-expired]
by Javier Valencia 18 Jan '19

18 Jan '19

Hi there! I'm using Kamailio 4.4.3, and I add this code to my Kamailio: event_route[usrloc:contact-expired] { xlog("L_INFO", "EXPIRED CONTACT START\n"); xlog("L_INFO", "EXPIRED CONTACT for $ulc(exp=>aor)\n"); xlog("L_INFO", "EXPIRED CONTACT END\n"); } I can't see this entries in the log. I read many times the docs and code, but I don't understand why it's not working. I have two phone with 60 and 300 expiry seconds, if then expire, when it's event_route[usrloc:contact-expired] triggered? Why this event route it's named as usrloc but it's documented in registrar module? I need to provide more info about? Thank you very much.

3 11

segfault at 0 - process stopped
by AL RSM 18 Jan '19

18 Jan '19

3 2

rtpengine_manage() in async tasks
by Alex Balashov 18 Jan '19

18 Jan '19

Hi, I've run into an issue with handling reinvites in async task workers--which I need to do in order to introduce a small delay to avoid a UA race condition--in which some state that is necessary for rtpengine_manage() to do the right thing seems to be lost. Specifically, if I do this: -- loadmodule "mqueue" loadmodule "rtimer" ... modparam("rtimer", "timer", "name=reinvite_q1;interval=10000u;mode=1;") modparam("rtimer", "exec", "timer=reinvite_q1;route=REINVITE_DEQUEUE") modparam("mqueue", "mqueue", "name=reinvite_q"); ... route { ... if(has_totag()) { if(loose_route()) { ... if(is_method("INVITE")) { if(!t_suspend()) { sl_send_reply("500", "Server Internal Error"); exit; } mq_add("reinvite_q", "$T(id_index):$T(id_label)", ""); } else route(IN_DLG_REQ); exit; } ... } route[REINVITE_DEQUEUE] { while(mq_fetch("reinvite_q")) { $var(id) = $(mqk(reinvite_q){s.select,0,:}{s.int}); $var(label) = $(mqk(reinvite_q){s.select,1,:}{s.int}); t_continue("$var(id)", "$var(label)", "IN_DLG_REQ"); } } route[IN_DLG_REQ] { handle_ruri_alias(); if(is_method("BYE")) rtpengine_manage(); else if(is_method("INVITE") && sdp_content()) rtpengine_manage("replace-origin replace-session-connection ICE=remove") t_on_reply("MAIN_REPLY"); if(!t_relay()) sl_reply_error(); } onreply_route[MAIN_REPLY] { if(is_method("INVITE") && sdp_content()) rtpengine_manage("replace-origin replace-session-connection ICE=remove"); } -- What I find is that if I generate a reinvite from either side, rtpengine_manage() passes through the SDP offer in the reinvite unadulterated, although the answer returns properly adulterated by RTPEngine. The same thing occurs if I use 'async', which as I gather is just a wrapper of convenience around t_suspend/t_continue() anyway. That module won't do for my purposes because I need a millisecond-level delay resolution rather than second-level, anyhow. Anyway, surely enough, this is because the execution context is one that insinuates a stream deletion. When the reinvite offer comes across and I call rtpengine_manage(), the command sent is 'delete': -- Jan 14 20:24:23 staccato.evaristesys.com rtpengine[33830]: INFO: [c94347dcf92e7ccc10dee84c4e0d1c8a]: Received command 'delete' from 209.51.167.66:39788 -- The RTPEngine module documentation actually warns about this: https://kamailio.org/docs/modules/5.2.x/modules/rtpengine.html#rtpengine.f.… But this insight is buried in the fourth bullet point: "If BYE or CANCEL, or called within a FAILURE_ROUTE[], then call rtpengine_delete(). Be careful with calling this function after resuming a suspended transaction (e.g., after t_continue()), because the context of executed route is FAILURE ROUTE (in other words, rtpengine_manage() in the route block of t_continue() does the same as in failure_route)." This would lead one to believe that it applies only in the context of handling a BYE or CANCEL in a resumed transaction, when in fact it seems to hold true of non-BYE/CANCEL and non-failure contexts as well, as can be clearly seen with the reinvite. The behaviour is exactly as expected if I don't use rtpengine_manage() and instead manually call rtpengine_offer()/rtpengine_answer(). And expected behaviour comes from rtpengine_manage() if I don't handle the request in a resumed transaction context. This yields the fundamental question: Is there any way to have my cake and eat it too? I really want to use rtpengine_manage() because I need to handle a potential SDP offer-in-ACK scenario and don't want to do a bunch of state-keeping in order to use the correct choice of rtpengine_{offer|answer}() in the right context, which is a problem rtpengine_manage() solves beautifully. At the same time, I absolutely need the slight reinvite delay that can be accomplished via async processing; a UA on this side has a nasty habit of sending a reinvite almost simultaneously to the 2xx answer for the INVITE transaction, leading to indeterminate egress velocity for those respective messages out of Kamailio worker threads. Many thanks in advance! -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

2 1

authentification issue when nb user increase
by Laurent Schweizer 18 Jan '19

18 Jan '19

Hello, I have a proxy with Kamailio 5.0.6 working since few month without any issue. Around 4500 locations and 5300 contacts This weekend we move a very old proxy (Kamailio 3.3.2 with an old server )to this new one, adding around 14’000 users and 15’000 contacts. Yesterday when calls was starting we get an big issue with this new proxy, lot of phones was disconnected and some calls was rejected. I see that the issue was the authentication (done via a mysql DB with the cluster db module) many phone get a failure and was disconnected, mostly phone connected via TCP or TLS we see less issue with UDP even we have much more . The issue was not the number of TCP/TLS connection as we see the REGISTER and the 401 going back, so connection was correctly done Currently it’s working but I don’t know exactly why ☹, I mean I have done a change but it has really no relation … , during the same time I get another issue, some calls have no voice… We are using rtpengine (on the old proxy we was using rtpproxy) and with the rtproxy we already face a long time ago such case and to solve it we setup multiple rtpproxy (on the same host) So I try to do the same, I setup a second rtpengine on the same host and when I reload the config with : kamcmd rtpengine.reload all registration was working perfectly ... As they is no relation with the registration end the rtpengine I don't know why now it's working. Any idea ? BR Laurent

2 1

Limitation in Dispatcher Probing
by Duarte Rocha 17 Jan '19

17 Jan '19

Greetings, I have a question about Dispatcher's probing. I have it configured with ds_probing_mode = 3 and ds_ping_interval = 60. Currently i have 35 Gateways with state = 8, meaning they will be probed. However, when i do a SIP capture i get a different scenario. Altough Kamailio sends OPTIONS at every 60 seconds it only sends to 16 destinations. Is there a configuration that limits this? What can i do to have every gateway probed? Best Regards, Duarte Rocha

1 0

Dispatcher Probing
by Duarte Rocha 17 Jan '19

17 Jan '19

Greetings, I have a question about Dispatcher's probing. I have it configured with ds_probing_mode = 3 and ds_ping_interval = 60. Currently i have 35 Gateways with state = 8, meaning they will be probed. However, when i do a SIP capture i get a different scenario. Altough Kamailio sends OPTIONS at every 60 seconds it only sends to 16 destinations. Is there a configuration that limits this? What can i do to have every gateway probed? Best Regards, Duarte Rocha

1 0

AWS binat external -> internal routing and record_route
by Dmitry Sytchev 17 Jan '19

17 Jan '19

Hi all! I have a question that arises in mailing list sometimes, but it is still not clear for me how to work with this. We have AWS instance with standard Amazon bi-nat, so basically communication with external hosts works with listen udp:ip:port advertise ip:port But in case when we need to send external call to internal network by internal ip addresses, we want to have internal host in record-route. As far as I understand, basic recommendation is to use separate port or internal address and select it with appropriate function. Maybe it is more theoretical question, but can we do something to generate correct record-routes and VIA for calls coming from external network to make their softswitches happy, and still maintain internal address in messages going to internal hosts, using single host and port on Kamailio behind nat? Thanks! -- Best regards, Dmitry Sytchev, IT Engineer

3 6

Invalid sqlops parameter
by Yağız AYDIN 17 Jan '19

17 Jan '19

Hello, I'm trying to install Kamailio IMS for my Ubuntu 18.04 device. I have followed the configuration files which are provided by installation, but I have a problem about sqlops module. While I'm trying to execute pcscf module, following errors appear: root@yagiz-HP-ZBook-15:/usr/local/src/kamailio# kamailio -f /etc/kamailio/pcscf/kamailio.cfg -c loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules 0(12536) ERROR: sqlops [sql_api.c:669]: sql_parse_param(): invalid sqlops parameter [mysql://Mysql@localhost/pcscf] at [29] 0(12536) CRITICAL: <core> [core/cfg.y:3449]: yyerror_at(): parse error in config file /etc/kamailio/pcscf/kamailio.cfg, line 278, column 60: Can't set module parameter 0(12536) INFO: pv [pv_shv.c:60]: shvar_init_locks(): locks array size 16 0(12536) CRITICAL: <core> [core/cfg.lex:1599]: sr_push_yy_state(): cannot open included file: route/register.cfg (/etc/kamailio/pcscf/route/register.cfg) 0(12536) : <core> [core/cfg.lex:1308]: yylex(): error at /etc/kamailio/pcscf/kamailio.cfg line 907 I have set my sqlops parameter as : #!define SQLOPS_DBURL "mysql://Mysql@localhost/pcscf" PS: I have created necessary databases and tables which are mentioned on usrloc files ( which are ims_usrloc_pcscf-create.sql and ims_usrloc_scscf-create.sql) Here is my pcscf.cfg file # IP-Adress for incoming SIP-Traffic, in the following format: # SIP / UDP listen=udp:10.3.0.188:5060 # SIP / TCP #listen=tcp:11.22.33.44:5060 # SIP / TCP/TLS #listen=tls:11.22.33.44:5061 alias=pcscf.mnc001.mcc001.3gppnetwork.org #!define MY_WS_PORT 80 #!define MY_WSS_PORT 443 #!define PCSCF_URL "sip:pcscf.mnc001.mcc001.3gppnetwork.org" #!define TCP_PROCESSES 8 #!subst "/NETWORKNAME/mnc001.mcc001.3gppnetwork.org/" #!subst "/HOSTNAME/pcscf.mnc001.mcc001.3gppnetwork.org/" # SIP-Address of capturing node, if not set, capturing is disabled. ##!define CAPTURE_NODE "sip:127.0.0.1:9060" # Allowed IPs for XML-RPC-Queries ##!define XMLRPC_WHITELIST_1 "127.0.0.1" ##!define XMLRPC_WHITELIST_2 "127.0.0.1" ##!define XMLRPC_WHITELIST_3 "127.0.0.1" #!define RTPPROXY_ADDRESS "udp:10.1.2.186:22222" # Databases: #!define DB_URL "mysql://Mysql@localhost/pcscf" ##!define DB_URL "mysql://kamailio:kamailiorw@localhost/kamailio/pcscf" ##!define DB_URL2 "con2=>mysql://pcscf:heslo@127.0.0.1/pcscf" #!define SQLOPS_DBURL "mysql://Mysql@localhost/pcscf" ##!define SQLOPS_DBURL "mysql://root@localhost/pcscf" #! Optional: Server-URL for Websocket-Requests ##!define WEBSOCKET_WEBSERVER "phone.ng-voice.com" ##!define TRF_FUNCTION "trf.mnc001.mcc001.3gppnetwork.org" # # Several features can be enabled using '#!define WITH_FEATURE' directives: # # *** To run in debug mode: # - define WITH_DEBUG # # *** To enable nat traversal execute: # - define WITH_NAT # - define the connection to the RTP-Proxy: RTPPROXY_ADDRESS # # *** To force alls calls through the RTP-Proxy # - this will automagically enable NAT-Traversal # - define FORCE_RTPRELAY # # *** To enable IPv4/IPv6 Translation (RTPProxy) # - this will automagically enable NAT-Traversal # - define WITH_RTPIPV4 # # *** To enable TCP support execute: # - define WITH_TCP # # *** To enable TLS support execute: # - adjust CFGDIR/tls.cfg as needed # - define WITH_TLS # - this will automagically enable TCP # # *** To enable XMLRPC support execute: # - define WITH_XMLRPC # - this will automagically enable TCP # # *** To enable anti-flood detection execute: # - adjust pike and htable=>ipban settings as needed (default is # block if more than 16 requests in 2 seconds and ban for 300 seconds) # - define WITH_ANTIFLOOD # # *** To enable the Rx-Interface: # - Configure Rx-Diameter-Interface in pcscf.xml # - define WITH_RX # # *** To enable a Homer SIP-Capter-Node: # - define CAPTURE_NODE with a proper address # # *** To enable support for the SEMS-SBC # - define WITH_SBC # - configure dispatcher-list with a set of SBC's # # Enabled Features for this host: ##!define WITH_DEBUG #!define WITH_NAT #!define WITH_NATPING #!define FORCE_RTPRELAY ##!define WITH_TLS ##!define WITH_XMLRPC ##!define WITH_IPBLOCK ##!define WITH_ANTIFLOOD ##!define WITH_RX ##!define WITH_RX_REG ##!define WITH_RX_CALL ##!define WITH_TCP ##!define WITH_RTPIPV4 ##!define WITH_SBC ##!define WITH_SBC_CALL ##!define WITH_REGINFO ##!define WITH_RTPPING ##!define WITH_WEBSOCKET Any helps would be appreciated, Regards, Yağız --

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