- sr-users - kamailio.org

UAC authentication challenge response using KEMI/app_ruby
by Andrew White 05 Apr '19

05 Apr '19

Hi all, I’m continuing on my quest to use app_ruby for my logic - it’s working very well so far! The last major hurdle I’ve come across is UAC response to WWW challenge. On my outbound path, the correct URIs for From and To are set based on provider requirements, and the INVITE is sent using t_relay(): def ksr_route_to_trunk() KSR.info("Route to trunk") if KSR::TM.t_is_set("failure_route") < 0 then KSR::TM.t_on_failure("ksr_failure_manage_trunk") end # Relay KSR::PV.sets("$fu", "sip:#{$uacs[trunk]['r_username']}@#{$uacs[trunk]['r_domain']}") KSR::PV.sets("$fn", '') new_uri = "sip:61400123123@#{uacs[trunk]['r_domain']}" KSR.info("New URI is #{new_uri}") KSR.seturi(uri) KSR::UAC.uac_replace_to('', uri) KSR::TM.t_relay() exit end I’ve stripped it back, but this function is great and works perfectly. An INVITE is sent to the correct place, and the trunk receives the INVITE. It then responds with a 401/WWW-Authenticate. My failure route is called fine. Below is the stripped down code: def ksr_failure_manage_trunk() exit if KSR::TM.t_is_canceled() > 0 KSR.info("Hit trunk failure manage route") KSR::PV.sets("$avp(auser)", 'user') KSR::PV.sets("$avp(apass)", 'pass') KSR::PV.sets("$avp(arealm)", 'test.local') KSR.info("AVPs: #{KSR::PV.gete("$avp(auser)")} #{KSR::PV.gete("$avp(apass)")} #{KSR::PV.gete("$avp(arealm)")}") if KSR::UAC.uac_auth() then KSR.info("UAC authed, relaying") KSR::TM.t_relay() else KSR.info("UAC NOT authed, no relay") end exit end Also the AVP values are set (I believe) correctly: modparam("uac", "auth_username_avp", "$avp(auser)") modparam("uac", "auth_password_avp", "$avp(apass)") modparam("uac", "auth_realm_avp", "$avp(arealm)") This throws the following complaint, and doesn’t send a new response back to the trunk: Apr 5 02:55:22 ip-10-0-0-2 /usr/local/sbin/kamailio[26870]: ERROR: {1 102 INVITE 3a84da15272da66e527a79144c48516c@10.0.0.20:5060} tm [t_fwd.c:1728]: t_forward_nonack(): no branches for forwarding Apr 5 02:55:22 ip-10-0-0-2 /usr/local/sbin/kamailio[26870]: ERROR: {1 102 INVITE 3a84da15272da66e527a79144c48516c@10.0.0.20:5060} tm [tm.c:1619]: _w_t_relay_to(): t_forward_noack failed I don’t understand branches very well, however after some digging around, I appended KSR::COREX.append_branch() in before the t_relay() in the failure. This stops the error and now we send an ACK and a new INVITE, but still without the expected authorisation header. I feel like my lack of understanding about branches is the issue here - I seem to be sending an INVITE, but not adding the auth header that I suspect is being generated somewhere! Thanks for your help. ________________________________ Andrew White - Director uConnected Email: andrew(a)uconnected.com.au Web: www.uConnected.com.au

2 2

Statistics of received replies
by Duarte Rocha 04 Apr '19

04 Apr '19

Greetings, Does Kamailio have statistics like the sl.stats but for received replies instead of locally generated ones? I want to be able to look at how many "491" replies i'm receiving, for example. Best Regards, Duarte Rocha

2 1

Kamailio v5.0.8 Released
by Daniel-Constantin Mierla 04 Apr '19

04 Apr '19

Hello, Kamailio SIP Server v5.0.8 stable release is out. This is a maintenance release of the old stable branch 5.0, that includes fixes since the release of v5.0.7. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.0.x. Deployments running previous v5.0.x versions are strongly recommended to be upgraded to v5.0.8 or even better directly to v5.1.x or v5.2.x because v5.0.x is getting out of the official maintenance time frame. Important note: this is the last planned release from branch5.0. For more details about version 5.0.8 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2019/04/kamailio-v5-0-8-released/ RPM, Debian/Ubuntu packages will be available soon as well. Note: the latest stable branch is 5.2, at this moment with its latest release v5.2.2. See more details about it at: * https://www.kamailio.org/w/kamailio-v5-2-0-release-notes/ 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

1 0

Kamailio-error reading: Connection reset by peer
by Mangesh Kharade 04 Apr '19

04 Apr '19

Hi Team, We are facing issue with kamailio application , we are not able to communicate to kamailio application getting below error. Can you please suggestion us how to resolved this issue issue, it production servers and we did not get any clue to resolve it. Error1:- Apr 2 06:53:54 urcmcs /usr/local/sbin/kamailio[2240]: ERROR: <core> [tcp_read.c:299]: tcp_read_data(): error reading: Connection reset by peer (104) Apr 2 06:53:54 urcmcs /usr/local/sbin/kamailio[2240]: ERROR: <core> [tcp_read.c:1326]: tcp_read_req(): ERROR: tcp_read_req: error reading Apr 2 06:54:12 urcmcs /usr/local/sbin/kamailio[2244]: ERROR: <core> [tcp_read.c:299]: tcp_read_data(): error reading: Connection reset by peer (104) Apr 2 06:54:12 urcmcs /usr/local/sbin/kamailio[2244]: ERROR: <core> [tcp_read.c:1326]: tcp_read_req(): ERROR: tcp_read_req: error reading Apr 2 06:54:17 urcmcs /usr/local/sbin/kamailio[2244]: ERROR: <core> [tcp_read.c:299]: tcp_read_data(): error reading: Connection reset by peer (104) Apr 2 06:54:17 urcmcs /usr/local/sbin/kamailio[2244]: ERROR: <core> [tcp_read.c:1326]: tcp_read_req(): ERROR: tcp_read_req: error reading Error1:- Apr 2 06:54:26 urcmcs /usr/local/sbin/kamailio[2179]: INFO: <script>: WebSocket connection from ###################:3008 has closed Apr 2 06:54:26 urcmcs /usr/local/sbin/kamailio[2179]: INFO: <script>: WebSocket connection from ###################:3009 has closed Apr 2 06:54:26 urcmcs /usr/local/sbin/kamailio[2179]: INFO: <script>: WebSocket connection from ###################:3010 has closed Apr 2 06:54:26 urcmcs /usr/local/sbin/kamailio[2179]: INFO: <script>: WebSocket connection from ###################:3011 has closed Apr 2 06:54:26 urcmcs /usr/local/sbin/kamailio[2179]: INFO: <script>: WebSocket connection from ###################:3012 has closed Please let us know if you need more help from our end. Thanks and Regards, Mangesh Kharade Consultant - Microsoft Azure | Managed Services [cid:image003.png@01D15FFB.27B1AA80] Pune IT Park, 34 Aundh Road Bhau Patil Marg, Pune 411020 Tel: +91.20.30204000 | Extn. 9694 VOIP: +1.713.353.7464 Mobile: +91.9168181166 Mangesh.kharade(a)silicus.com<mailto:Mangesh.kharade@silicus.com>| www.silicus.com<http://www.silicus.com/> The information in this email is confidential and may be legally privileged. It is intended solely for the addressee and access to it by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken based on it, is strictly prohibited and may be unlawful.

2 2

Releasing Kamailio v5.0.8
by Daniel-Constantin Mierla 04 Apr '19

04 Apr '19

Hello, I am considering to release v5.0.8 to mark the end of official maintenance for branch 5.0 on Thursday, April 4. If no major regression will be introduced, this will be the last release from branch 5.0. Afterwards, the stable branches maintained will be 5.1 and 5.2. In case you have in mind some specific commits that should get into 5.0 branch, then reply and list them to be sure they are not missed. 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

2 2

Kamailio & asterisk integration
by ayoub krari 04 Apr '19

04 Apr '19

Good morning, I want to Loadbalance calls equally to asterisk servers, i have already tried with opensips but didnt work for me, i want to try kamailio now, i have tried with the tutorial of " Kamailio 4.0.x and Asterisk 11.3.0 Realtime Integration using Asterisk Database" but i got some errors and packages missing during the installation and the configuration, my Linux distro is Debian 8.7.0 and i’m using Asterisk v 13, i want really to implement Kamailio , any one can help me with steps or anything , Thanks in advance !

2 1

dispatcher "failover feature disabled"
by David Villasmil 03 Apr '19

03 Apr '19

Hello guys, In my config i have: # ----- dispatcher params ----- 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", "dstid_avp", "$avp(dsdstid)") modparam("dispatcher", "attrs_avp", "$avp(dsattrs)") # PVs for hashing modparam("dispatcher", "hash_pvar", "$fU@$ci") # PVs to store results when calling ds_is_from_list modparam("dispatcher", "setid_pvname", "$var(setid)") modparam("dispatcher", "attrs_pvname", "$var(attrs)") # method to probe the gateways modparam("dispatcher", "ds_ping_method", "OPTIONS") modparam("dispatcher", "ds_ping_from", " sip:dispatcher@proxy.voice-proxy.singlecommand.com") modparam("dispatcher", "ds_ping_interval", 10) modparam("dispatcher", "ds_probing_threshold", 1) modparam("dispatcher", "ds_ping_reply_codes","class=2") modparam("dispatcher", "ds_probing_mode", 1) # size of hash table storing data for call load dispatching, power of two modparam("dispatcher", "ds_hash_size", 10) # expiration time in seconds to remove the load on a destination if no BYE was received modparam("dispatcher", "ds_hash_expire", 3600) # expiration time in seconds to remove the load on a destination if no 200 OK for INVITE was received # and state updated with ds_load_update modparam("dispatcher", "ds_hash_initexpire", 60) modparam("dispatcher", "ds_hash_check_interval", 30) But i'm getting on startup: ds_warn_fixup(): failover functions used, but required AVP parameters are NULL -- feature disabled What avp am I missing? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 3

Re: [SR-Users] Adding presentity_uri prefix for multi-tenanted presence/dialoginfo configuration
by Rhys Hanrahan 03 Apr '19

03 Apr '19

Hi All, I managed to solve my need to re-write NOTIFY packets with help from this thread: https://www.mail-archive.com/sr-users@lists.kamailio.org/msg08088.html This seems to work well. I am re-writing the packets as shown below… I guess my only question is, is this relatively safe/smart to do? I basically copied what our standalone Asterisk PBXes are doing in my captures, so I guess so? But I’m not confident enough to say it won’t cause some weird edge case issues. I can only say it works fine with the Snom and Yealink handsets I am testing with. I’m just concerned because it feels a bit like a hack. For SUBSCRIBE I re-write: * Request URI and To header from 101@ sent by the handset to tenant101@ (to match the SIP username of the handset - tenant101@) For NOTIFY I re-write: * From and Contact header to remove the tenant prefix, to go back to 101@ to match the BLF key configuration on the handsets. Any advice would be appreciated on if this is a bad idea, and there’s a better way. Thanks! 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 From: sr-users <sr-users-bounces(a)lists.kamailio.org> on behalf of Rhys Hanrahan <rhys(a)nexusone.com.au> Reply-To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Date: Tuesday, 26 March 2019 at 8:56 pm To: "sr-users(a)lists.kamailio.org" <sr-users(a)lists.kamailio.org> Subject: [SR-Users] Adding presentity_uri prefix for multi-tenanted presence/dialoginfo configuration 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

uac_replace_from/to, msg_apply_changes and Re-INVITE
by Henning Westerholt 03 Apr '19

03 Apr '19

Hello, I am currently debugging a strange issue related to the usage of uac_replace_from/to() after msg_apply_changes(). It works all fine, but in a Re-INVITE case it inserts the wrong headers for the 100 - Trying case. The calle side gets then a reply with wrong From/To. This happens all the time with this particular cfg. I already checked for the usual issues: - msg_apply_changes() called several times - msg_apply_changes() called after transactions created/async processing etc.. Any ideas what else could be the problem? The msg_apply_changes() is needed for some SDP filtering logic in the cfg. Thanks and regards, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services

3 8

TOPOS Call-ID masking
by Cinthia Leung 02 Apr '19

02 Apr '19

Greetings, Call-ID masking is not available, although the modparam is there. Just wondering if there are any plans to get that in soon. Thanks. Cindy

2 2

ENUM for CNAM dips
by Spencer Thomason 02 Apr '19

02 Apr '19

Hi all, I’m interested in extending the ENUM module to add support for draft-ietf-enum-cnam-08 CNAM queries using ENUM. I’m looking for high level guidance as to the best way to implement this and any feedback on naming of exported functions and parameters. Maybe something like enum_cnam_query("pvar", "destination", [,"suffix" [,"service"]]) ? Best regards, Spencer

2 1

Info: Kamailio World 2019 – Participation Grants
by Daniel-Constantin Mierla 02 Apr '19

02 Apr '19

Hello, we continue our tradition to give away 3 free passes to students and underrepresented people at Kamailio World Conference (www.kamailioworld.com) – thanks to the sponsors, we are able to offer them in 2019 as well. The passes cover the entire registration fee for all three days and the social networking events – costs with travel and accommodation have to be covered by the participants. Anyone enrolled in an academic activity (including master and PhD programs) as well as underrepresented people can apply for one of the passes via email to me or to: * conference [at] kamailioworld.com or by contacting us via web form at: * https://www.kamailioworld.com/k07/contact-us/ Applications done until April 15, 2019, will be selected by April 18, 2019. Afterwards, if there are still available passes, they will be allocated in the first come first served policy. The details for most of the presentations were published, the full agenda is expected to be ready in a matter of a few days. You can see more details at: * https://www.kamailioworld.com/k07/schedule/ Looking forward to meeting many of you in Berlin, at Kamailio World 2019! It’s going to be another great event about open source real time communications! * https://www.kamailioworld.com/k07/registration/ 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

1 0

Port 5060 omitted in Record-Route
by Lợi Đặng 02 Apr '19

02 Apr '19

Hi all, i was using kamailio 4.2.1 located in 2 networks > listen = tcp:MY_ADDR:5060 advertise MY_ADDR:5060 > listen = tls:MY_ADDR:5061 advertise PUBLIC_NAT_ADDR:5061 when the call made from the inside network to out side, running `record_route()` resulted in 2 Record-Route headers added (enable_double_rr=1) Record-Route: PUBLIC_NAT_ADDR:5061;transport=tls;lr > Record-Route: MY_ADDR;transport=tcp;lr That was totally fine omitting the port in the first Record-Route when using tcp (or udp) on the first realm, but when i start switching to tls, it caused trouble Record-Route: PUBLIC_NAT_ADDR:5061;transport=tls;lr > Record-Route: MY_ADDR;transport=tls;lr The client is then told to send ACK/BYE to `MY_ADDR;transport=tls` located at `MY_ADDR:5061` as per rfc3263, then the call would failed. I had another try with `record_route_preset("PUBLIC_NAT_ADDR:5061;transport=tls", "MY_ADDR:5060;transport=tls");`, it really did add what i want with explicit 5060 port on RR, `ACK/BYE` travel on the correct path, but `loose_route()` only consumes the local `Route` header (it should consume 2). So my assumption is to stick with `record_route()` function to make `loose_route()` work properly. I tried using another port on the local realm, e.g: 5062 and the port is explicitly added to the Record-Route header `MY_ADDR:5062;transport=tls;lr` So is `5060` couldn't be explicitly added to the inbound Record-Route, or i just missed something? Any help will be appreciated. P/S: I also tried 4.4.7 and it still omit my 5060 port in the RR. rgds, Loi Dang Thanh Phone : +84. 774.735.448 Email : loi.dangthanh(a)gmail.com

3 5

Compressing SIP messages
by Igor Olhovskiy 01 Apr '19

01 Apr '19

Hi! Was looking on some way to compress SIP signalling between internal servers. But found out, there are no some pre-defined or recommended mechanism of doing this. Yes, I found gzcompress module, but it will help only in case of big body, but not whole message itself. Like in some cases you can have 4-5 RR headers, which is already a lot of info. What I googled is SigComp Compact Header form As I found, SigComp is really not widely-used method and it support along opensource SIP servers/PBXes is not documented. For Compact Header form - is there any way of using Kamailio to compress message this way? Maybe also there is a way of having some intermediate proxy-layer software, that will gzip/gunzip SIP signalling in realtime? All of this actually cause info in SIP/SDP grows rapidly, unfortunately MTU size is not.

8 11

presence_dialoginfo module not sending publish on dialogue change
by Richard Nunley 01 Apr '19

01 Apr '19

To whom can be of assistance, I’m am working towards enabling presence on my Kamailio proxy but have hit a bit of a brick wall. I’m seeing dialogues being created and persisted to the database, subscriptions are being handled and rows are being written to the active_watchers table but no PUBLISH is ever being received by the server to kickoff the sending of NOTIFY to the active watchers. Further, I’m never seeing a row in the watchers table though I don’t know that this isn’t expect behavior. I’ve attached my current config for review. Any help will be greatly appreciated! Thank in advance!

3 2

Use Kamailio as forward proxy between two networks
by Lauritz 01 Apr '19

01 Apr '19

Hello, I am trying to implement the following network setup using Kamailio and RTPProxy, but was not able to find any recent documentation or blog posts with hints: > local_net1 : local_net2 > 10.250.10.* : 10.250.11.* > : > (1) (2) : > +-------------+ +--------------+ +--------------+ > ! !.11 .12 ! Proxy !.21 ! Debian Host !.22 > ! Starface !---------------! + Kamailio !<<--------------! + Linphone !.23 > ! ! ! + RTPProxy ! ! ! > +-------------+ +--------------+ +--------------+ > eth0 : eth1 > : > : > As you can see, the proxy has two interfaces and its purpose is to forward traffic from the client's network to the Starface's network. Has anyone experience to share or got any other hints where to start? Thank you very much for your help :) Kind regards, Lauritz

2 1

Kamailio Managed Cloud
by Alex Balashov 01 Apr '19

01 Apr '19

For immediate release: ATLANTA, GA (1 April 2019)--Following its long tradition of forward-thinking innovation in open-source Real-Time Communications (RTC), the leadership of the Kamailio SIP server project (formerly known as OpenSER) has launched the Kamailio Managed Cloud (KMC). Alex Balashov of Evariste Systems and Fred Posner of The Palner Group were among several key North American stakeholders on hand to discuss it further. As Posner told us, "Kamailio Managed Cloud is a new, best-of-breed managed Kamailio hosting environment. We provide elasticity by leveraging human capital. Using our patent-pending Orchestration Turk system, our managed cloud technicians will purchase your SuperMicro bare-metal server, known as a KamBox, drive to the data centre, and rack-and-stack it on demand -- all in response to a SOAP API call! And when you want to remove your on-demand KamBox, just issue a 'delete' operation and we will decommission the hardware -- live!" "Dedicated KamBox colocation really puts the Management in Managed Cloud," emphasised Balashov. "But that doesn't mean we keep the customer out of the loop. We are using the most modern XMLHttpRequest and 'AJAX' techniques to provide a real-time dashboard with KamBox status to all users, though it will not work with Internet Explorer 6 -- we're addressing that." "Anyway, there are numerous other cloud platforms out there, many of which rely on virtualisation and automated orchestration and the like. It really takes the human touch out of the equation and gives the short shrift to quality, while also taking away jobs. And besides, how can a so-called 'virtual' machine be truly carrier-grade?" Kamailio Managed Cloud launched in two principal regions today -- US-EAST-1, located in Jacksonville, Florida, USA, and EU-CENTRAL-1, based in the booming tech hub of central Europe and birthplace of OpenSER: Berlin, Germany. Unnamed sources tell us that strategic expansion is planned for several other regions, including Flint, Michigan, USA. The mechanics of Kamailio Managed Cloud have invited questions about how other elastic cloud resources are managed, more especially elastic storage. According to KMC senior management, storage is provided via a mechanism developed by ASIPTO StorageWorks. ASIPTO chief Daniel-Constantin Mierla was on hand at the KMC launch to explain: "It's very easy. When a customer requests more space with a simple and lightweight SOAP call with just a little custom XML namespaces, then depending on the region, Fred or I receive an SMS on our smartphones from our advanced PHP backend and drive to the data centre to insert another hard drive into one of the KamBox's several drive bays. We are using the latest in advanced mobile communications, SMS, to ensure fastest response time. Of course our service level is comprehensive and includes Managed Partition Table Labelling and Managed LVM Insertion. Also there is optional Managed Filesystem Formatting for a complete portfolio of managed services. ASIPTO StorageWorks moves at the speed of global e-business. Just text us your desired filesystem layout and partitioning scheme. It is really that easy!" When asked about business focus, marketing turnaround veteran Henning Westerholt, Executive Vice President of Business Development for KMC responded: "Our target customer is a socially conscious Millennial-run corporation or start-up who see value in the unique blend of managed services and an artisanal, hand-crafted, organic approach that is compatible with social justice and takes a people-centric view." Asked to elaborate upon his vision of social justice, Westerholt added: "Virtualisation, orchestration and auto-scaling take the people out of the equation, and Kamailio is, in the end, about people, as communication in general is about people. What would it be without the people? Moreover, these mechanisms take away gainful opportunities from hard-working university graduates. Kubernetes, Docker Swarm, VMWare, and KVM contravene the social policy objective of full employment." At press time, Posner, who also heads up KMC Labs North America, was said to be lending his pioneering business vision and knack for seeing around technology trend corners to intensive work on next-generation, bleeding-edge functionality for KMC. While Posner was tight-lipped about the specifics, he did state that the 'dispatcher' module is slated to be deprecated in favour of a "human load-balancing approach to SIP requests that is both cloud-native and eco-conscious". Industry analysts agree that protocol-aware load-balancing strategies are complicated and that the application of human judgment to the problem represents a fertile field for dynamic innovation and investment. Reports from regional press confirm that KMC Labs are in the process of building a fullfilment centre for this innovative offering, said to be branded "Central Switchboard", at an undisclosed site in Bangladesh, where thousands of "Load Balance Operator" jobs have been advertised in and around the Dhaka market. -- 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/

1 0

db_redis and user
by Joan Salvatella 01 Apr '19

01 Apr '19

Hello, We are working on a project that's using two active-active Kamailio 5.2 instances that redirect traffic to several Asterisk 15.4 instances. Kamailio is acting as a registrar and should store the location information of the registered terminals. The backend database is db_redis. Phone terminals get registered and the information gets looked up from the subscriber schema in redis (That's cool) but we are having problems with the locations. This is the related code: modparam("db_redis", "keys", "location=entry:ruid&usrdom:username,domain&timer:partition,keepalive") if(ds_is_from_list("1", "2", "sip:$fd:5080")) { record_route(); route(INVITE_ASTERISK); exit; } route[INVITE_ASTERISK] { xlog("L_INFO", "[R-INVITE-RESOLVER:$ci] Entering ASTERISK INVITE resolver\n"); if (!lookup("location")) { sl_send_reply("404", "User Not Found"); return; } route(INVITE_POSTROUTE); } route[INVITE_POSTROUTE] { rtpproxy_manage(); t_on_reply("MAIN_REPLY"); if(!t_relay()) sl_reply_error(); } When looking up the location schema this errors appear: 9(39) WARNING: db_redis [redis_dbase.c:1098]: db_redis_perform_query(): performing full table scan on table 'location' while performing query 9(39) WARNING: db_redis [redis_dbase.c:1101]: db_redis_perform_query(): scan key 0 is 'expires' 9(39) WARNING: db_redis [redis_dbase.c:1101]: db_redis_perform_query(): scan key 1 is 'expires' 9(39) ERROR: <core> [db_ut.c:92]: db_str2int(): Unexpected characters: [-03-29 18:16:36] 9(39) ERROR: <core> [db_val.c:76]: db_str2val(): error while converting integer value from string 9(39) ERROR: db_redis [redis_dbase.c:1062]: db_redis_convert_row(): Failed to convert redis column 'expires' to db value 9(39) ERROR: db_redis [redis_dbase.c:1231]: db_redis_perform_query(): Failed to convert redis reply for row 9(39) ERROR: db_redis [redis_dbase.c:1243]: db_redis_perform_query(): failed to perform the query 9(39) ERROR: db_redis [redis_dbase.c:1829]: db_redis_query(): failed to do the query 9(39) ERROR: usrloc [udomain.c:981]: udomain_contact_expired_cb(): db_query failed Any hints? Thanks and regards,

3 2

Kamailio v5.2 kamctl alias add problem
by Igor Potjevlesch 01 Apr '19

01 Apr '19

Hi kamailios, I meet a problem with the " kamctl alias add" command in the 5.2 version, I saw that the module used to add an alias had changed, and now the command result with an error : [kamailio]# kamctl alias add XXXX@XXXX sip:XXXXX@XXXX { "jsonrpc": "2.0", "error": { "code": 500, "message": "Not enough parameters or wrong format" }, "id": XXXXX } I read the function who return this message " static void ul_rpc_add(rpc_t* rpc, void* ctx)" in the ul_rpc.c in the usr_loc module. I tried to pass the command with two more parameters : # kamctl alias add 0175951068(a)trunk7.bornsip.fr sip:0175951068@trunk7.bornsip.fr NULL NULL { "jsonrpc": "2.0", "result": { }, "id": 29200 } And this time it works correctly, but I saw thaht the test prameters was in the field "path" , do you know why we have to indicate a path ? Are we obliged to indicate this two more parameters ? What is the utility of this field ? Thank you in advance, Igor

2 2

where to find the cfg languaje for program on it?
by PICCORO McKAY Lenz 01 Apr '19

01 Apr '19

recently i wrote a portion of my cfg file but i found that i based my code in other sources and results of try/tach experiments i cannot found the documents for the languaje of the core i only found the link: https://www.kamailio.org/wiki/cookbooks/devel/core but in that link there's no references about languaje per see only about how to write portions of the file and sections.. maybe i wrong or the document are wrote in different way? by example how to evaluate the output of a custom function/section? Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com

2 1

drop before exit and send ok reply first can be done?
by PICCORO McKAY Lenz 01 Apr '19

01 Apr '19

h have this for a custom rule agains spoecific messages: sl_send_reply("200", "OK"); drop(); exit; my question are if that rules are correct: i want to drop but send firts to client a ok response.. i mean client receive "all are ok dont worry" and then drop the rest packets.. that's correct? Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com

3 2

kamailio and rtpengine
by David Villasmil 01 Apr '19

01 Apr '19

Hello guys, i'm trying to configure rtpengine, but when starting kamailio (with an empty table) i'm getting ```build_rtpp_socks(): no more pkg memory for rtpp_socks``` Can anyone help? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

3 5

kamailio 5.2.0 with empty table of rtpengine - kamailio doesn't start
by * Paolo Visintin - evosip.cloud 31 Mar '19

31 Mar '19

Hello, I noticed that , with kamailio ver. 5.2.1 starting with empty rtpengine table causes strange messages in kamailio and it doesn't start modparam("rtpengine", "db_url", "text:///tmp/kamailio/dbtext") cat /tmp/kamailio/dbtext/rtpengine id(int,auto) setid(int) url(string) weight(int) disabled(int) stamp(int) 0(2856) WARNING: tm [tm.c:760]: mod_init(): reparse_on_dns_failover is enabled on a multihomed host -- check the readme of tm module! 0(2856) WARNING: rtpengine [rtpengine_db.c:100]: rtpp_load_db(): No rtpproxy instances in database 0(2856) ERROR: rtpengine [rtpengine.c:2768]: select_rtpp_set(): no rtpp_set_list->rset_first 0(2856) NOTICE: rtpengine [rtpengine.c:1664]: mod_init(): Default rtpp set 0 NOT found 1(2857) NOTICE: usrloc [udomain.c:434]: preload_udomain(): filtered by server_id[0] 2(2858) ERROR: rtpengine [rtpengine.c:1722]: build_rtpp_socks(): no more pkg memory for rtpp_socks 2(2858) ERROR: <core> [core/sr_module.c:847]: init_mod_child(): error while initializing module rtpengine (/usr/lib/x86_64-linux-gnu/kamailio/modules/rtpengine.so) (idx: 2 rank: 2 desc: [udp receiver child=1 sock=172.28.0.120:5060]) 2(2858) ERROR: <core> [core/pt.c:342]: fork_process(): init_child failed for process 2, pid 2858, "udp receiver child=1 sock=172.28.0.120:5060" 2(2858) CRITICAL: <core> [main.c:1633]: main_loop(): Cannot fork 4(2860) ERROR: rtpengine [rtpengine.c:1722]: build_rtpp_socks(): no more pkg memory for rtpp_socks 4(2860) ERROR: <core> [core/sr_module.c:847]: init_mod_child(): error while initializing module rtpengine (/usr/lib/x86_64-linux-gnu/kamailio/modules/rtpengine.so) (idx: 4 rank: 4 desc: [udp receiver child=3 sock=172.28.0.120:5060]) 4(2860) ERROR: <core> [core/pt.c:342]: fork_process(): init_child failed for process 4, pid 2860, "udp receiver child=3 sock=172.28.0.120:5060" 4(2860) CRITICAL: <core> [main.c:1633]: main_loop(): Cannot fork any hint on what could be wrong ? (5.2.0 works perfectly) many thanks! Paolo

6 7

app_ruby - KSR::PV.sets method not found
by Andrew White 31 Mar '19

31 Mar '19

Hi all, I’m trying to set a pseudovariable via app_ruby. I’m able to retrieve pseudovariables using PV.gete as such: However trying to set these using sets, I get “No method found”: KSR::PV.sets("$fu", "sip:#{$uacs[trunk]['r_username']}@#{$uacs[trunk]['r_domain']}") Mar 30 04:44:59 ip-10-0-0-2 /usr/local/sbin/kamailio[28421]: ERROR: {1 102 INVITE 0fae8097312bec2b5ec79ada30c227e7@127.0.0.1:5060} app_ruby [app_ruby_api.c:107]: app_ruby_print_last_exception(): exception: undefined method `[]' for nil:NilClass PV.seti appears to work correctly. Am I calling the wrong method? Thanks! ________________________________ Andrew White - Director uConnected Email: andrew(a)uconnected.com.au Web: www.uConnected.com.au

2 4

Low %
by Loan Offer 30 Mar '19

30 Mar '19

Apply Now!!!

1 0

[--SPAM--] Low %
by Loan Offer 30 Mar '19

30 Mar '19

Apply Now!!!

1 0

Lost connection to MySQL server during query
by JR Richardson 29 Mar '19

29 Mar '19

Hey Folks, Getting some annoying logs, pretty certain these are false positives. I'm running kamailio 4.4.7 using localhost mysql 5.5.60 on debian 7.11. Pretty simple setup, have acc and collecting cdrs. Relevant kamailio.cfg: loadmodule "acc.so" loadmodule "rtimer.so" loadmodule "sqlops.so" # ----- acc params ----- modparam("acc", "db_url", DBURLRW) modparam("acc", "db_flag", 1) modparam("acc", "db_missed_flag", 2) modparam("acc", "db_extra", "src_user=$fU;src_domain=$fd;src_ip=$si;" "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;" "accountcode=$avp(s:acctcode)") modparam("rtimer", "timer", "name=cdr;interval=300;mode=1;") modparam("rtimer", "exec", "timer=cdr;route=CDRS") modparam("sqlops", "sqlcon", "cb=>mysql://rwuser:rwpass@localhost/kamailio") route[CDRS] { sql_query("cb","call kamailio_cdrs()","rb"); } Logs: ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013) ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query ERROR: sqlops [sql_api.c:265]: sql_do_query(): cannot do the query [call kamailio_cdrs()] CDRs are working fine, no issues with the results, just the log messages. Errors occur every 5 minutes so this is related to the rtimer cycle, mode=1 is set for new connection so there really wouldn't be a lost connection, the old connection should have been relieved on last cycle. I've seen some other post talking about this issue but could not find any resolution or work around. Any help is appreciated. Thanks. JR -- JR Richardson Engineering for the Masses Chasing the Azeotrope

3 3

log timestamp granularity
by Patrick Murphy 28 Mar '19

28 Mar '19

Hello - Is there a way I can print current timestamp in milli or microseconds in the log file? Something like: 2019-03-28 04:50:15.379 would be ideal The closest thing I could find was $TV(Sn) but it doesn't suit the purpose here since its not human readable. Thanks Pat

2 1

flags definition in kamailio.cfg + 5.2 documentation
by Joel Serrano 27 Mar '19

27 Mar '19

Hi, I saw in the Kazoo default.cfg this: ... ####### Flags ####### flags FLAG_INTERNALLY_SOURCED: 1, FLAG_ASSOCIATE_SERVER: 2, FLAG_SKIP_NAT_CORRECTION: 3, FLAG_ASSOCIATE_USER: 4, FLAG_TRUSTED_SOURCE: 5, FLAG_SESSION_PROGRESS: 6, FLAG_IS_REPLY: 7, FLAG_SIP_TRACE: 8; ... So then I went here to read about it: https://www.kamailio.org/wiki/cookbooks/5.2.x/core#flags I found out it's not documented... is this a drop-in alternative for a: #!define FLAG_NAME FLAG_BIT? Sorry, first time I see this if not I would update the docs myself... :( Thanks, Joel.

4 8

Uri's user part parameters
by Duarte Rocha 27 Mar '19

27 Mar '19

Greetings, Does Kamailio have a way of identifying the user-part parameters of an URI? I have situations where i have sip:user;parameter=yes@host. Best Regards, Duarte Rocha

2 1

Manipulating User Agent header in dispatcher OPTIONS
by Andrew White 27 Mar '19

27 Mar '19

Hi all, I’ve set the server_header variable in my primary config, and I’ve got a catch in the default reply route to modify headers where required. I’m masking this value for security reasons, and filling it with my own value for vanity reasons :). I’ve noticed that the OPTIONS packet that is send via the dispatcher module when probing mode is on contains a User-Agent field which has the full version and OS type. Unfortunately I don’t necessarily have trust of the end destination being dispatcher to, nor the packet switchers in-between. How can I catch this OPTIONS packet to manipulate the value? It doesn’t appear to go through the REQUEST route or the ONSEND route. Thanks! ________________________________ Andrew White - Director uConnected Email: andrew(a)uconnected.com.au Web: www.uConnected.com.au

2 2

accounting and db_redis
by Daniel Tryba 27 Mar '19

27 Mar '19

Under https://www.kamailio.org/docs/modules/5.2.x/modules/db_redis.html#db_redis.… there is an example for using db_redis for accounting. This doesn't appear to work (5.2.2) modparam("db_redis", "keys", "acc=entry:callid,time_hires&cid:callid") results in: db_redis [redis_dbase.c:1886]: db_redis_insert(): inserting to prefix (table) 'acc' db_redis [redis_dbase.c:382]: db_redis_build_entry_keys(): build entry keys db_redis [redis_dbase.c:295]: db_redis_find_query_key(): checking for existence of ent db_redis [redis_dbase.c:306]: db_redis_find_query_key(): found key in entry key db_redis [redis_dbase.c:133]: db_redis_val2str(): converting str value '1db9c0bc57291e db_redis [redis_dbase.c:338]: db_redis_find_query_key(): entry key so far is 'acc:entr db_redis [redis_dbase.c:295]: db_redis_find_query_key(): checking for existence of entry key 'time_hires' in query db_redis [redis_dbase.c:346]: db_redis_find_query_key(): key 'time_hires' for type 'entry' not found, unable to use this type db_redis [redis_dbase.c:405]: db_redis_build_entry_keys(): Failed to create direct entry key, no matching key definition db_redis [redis_dbase.c:1892]: db_redis_insert(): failed to build entry keys db_redis [redis_dbase.c:1976]: db_redis_insert(): failed to do the insert What does work is "time" instead of "time_hires". Since I have no idea what values are available (I guess the table names?) and time only has a 1 sec resolution, what is a correct version of time_hires?

1 2

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

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