- sr-users - kamailio.org

xhttp_prom Metric Naming Issue
by ENGIN ESIN 12 Dec '19

12 Dec '19

Hi everyone, I am trying to use xhttp_prom and there are some issues that i want to share with you. Metric Naming: I get warning at prometheus side like as follows, WARN[0659] append failed err="no token found" source="scrape.go:648" target="{__address__="192.168.42.1:9080", __metrics_path__="/metrics", __scheme__="http", instance="192.168.42.1:9080", job="vmm"}" With respect to prometheus documentation, metric names need to fullfill following naming requirement -> "It must match the … [View More]regex [a-zA-Z_:][a-zA-Z0-9_:]*" (source: https://prometheus.io/docs/concepts/data_model/#metric-names-and-labels) However, kamailio gives unmatch outputs as follows because they have '-' char, (related discussion: https://github.com/prometheus/prometheus/issues/3154 ) * kamailio_usrloc_location-contacts 0 1576046310669 * kamailio_usrloc_location-expires 0 1576046310669 * kamailio_usrloc_location-users 0 1576046310669 whit that naming, prometheus can not parse values of any metrics. Documentation: Example 1.1. Set xhttp_prom_buf_size parameter ... modparam("xhttp", "xhttp_prom_buf_size", 1024) ... For that example, it should be as follows, ... modparam("xhttp_prom", "xhttp_prom_buf_size", 1024) ... [http://www.turkcell.com.tr/downloads/bireysel/img/Tcelldis.gif] <http://turkcell.li/iyaani> Bu elektronik posta ve onunla iletilen butun dosyalar sadece gondericisi tarafindan almasi amaclanan yetkili gercek ya da tuzel kisinin kullanimi icindir. Eger soz konusu yetkili alici degilseniz bu elektronik postanin icerigini aciklamaniz, kopyalamaniz, yonlendirmeniz ve kullanmaniz kesinlikle yasaktir ve bu elektronik postayi derhal silmeniz gerekmektedir. TURKCELL bu mesajin icerdigi bilgilerin do?rulu?u veya eksiksiz oldugu konusunda herhangi bir garanti vermemektedir. Bu nedenle bu bilgilerin ne sekilde olursa olsun iceriginden, iletilmesinden, alinmasindan ve saklanmasindan sorumlu degildir. Bu mesajdaki gorusler yalnizca gonderen kisiye aittir ve TURKCELLin goruslerini yansitmayabilir Bu e-posta bilinen butun bilgisayar viruslerine karsi taranmistir. ________________________________ This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient you are hereby notified that any dissemination, forwarding, copying or use of any of the information is strictly prohibited, and the e-mail should immediately be deleted. TURKCELL makes no warranty as to the accuracy or completeness of any information contained in this message and hereby excludes any liability of any kind for the information contained therein or for the information transmission, reception, storage or use of such in any way whatsoever. The opinions expressed in this message belong to sender alone and may not necessarily reflect the opinions of TURKCELL. This e-mail has been scanned for all known computer viruses. [View Less]

2 1

Please Help
by Sharath 12 Dec '19

12 Dec '19

Dear Team, If we want add a free-pbx as a trunk then what are configuration we need to do in admin panel of siremis. * SHARATH. O.M.** *

2 1

Kamailio delayed reponse in case of database load
by Ali Taher 10 Dec '19

10 Dec '19

Hello, I have Kamailio installed as SIP redirect for an SBC to make routing decisions. I'm using SQLOps module with postgresql 11.5 where I have multiple tables containing each around 6M record of routing codes: Code options ----------------------- 392342 sup1|sup2|sup3 Where code field is of prefix_range data type and has a gist index. I'm sending traffic of 300 CPS to SBC which is forwarding it to Kamailio, and Kamailio respond with 300 multiple choice with the routing decision. In … [View More]

4 6

authcheck and fd variable
by Robert Lieback 10 Dec '19

10 Dec '19

Hello, i'm looking into kamalio (btw: thanks to asipto for the great book) and i hope someone can push me in the right direction. I have a question/problem with some lines in the default config (kamailio.cfg) around line 754: ... if (is_method("REGISTER") || from_uri==myself) { # authenticate requests if (!auth_check("$fd", "subscriber", "1")) { … [View More]

2 2

Kamailio management group updates
by Daniel-Constantin Mierla 09 Dec '19

09 Dec '19

Hello, Jesus Rodrigues and Inaki Baz Castillo changed their work roles a while ago, so they no longer deal with Kamailio and they do not expect to do it in the near future. To keep the Management group with members connected as much as possible with the project, Fred Posner and Victor Seva were proposed to replace them. For the new members in the public lists: the management group of Kamailio is not involved in the daily development or administration of the project -- all those are done on … [View More]

1 0

duplicated registrations
by Liu, Charles 08 Dec '19

08 Dec '19

Hi All, Does this look correct? I am using Zoiper client and did multiple registration/re-registration, but I saw duplicated contacts in the database for the same user/device(alice). I was expecting to see only one. Is this a bug? How do I prevent this happening? "select * from scscf.contact" id contact params path received user_agent expires callid 49 sip:bob@192.168.10.201:60944;rinstance=44b4024df17bd284;transport=UDP NULL <sip:term@pcscf.mnc001.mnc001.… [View More]

2 2

ul.dump empty
by Liu, Charles 07 Dec '19

07 Dec '19

Hi All, I am running Kamailio v5.2.4 with P/S/I-cscf instances on 3 different machines with default IMS example configurations. Kamcmd ul.dump show empty, but I can make calls... any idea what is the problem? root@pcscf:/# kamcmd ulpcscf.status { Domain: location Size: 512 AoRs: { Stats: { Records: 7 Max-Slots: 6 } } } root@pcscf:/# kamcmd ul.dump { Domains: { } } … [View More]

1 1

Pike module never release IP
by Andrew Chen 06 Dec '19

06 Dec '19

Hi all, Have anyone ever experienced pike module not releasing the IP after "remove_latency" period? We ran a load test and this is what happened to one of the two paired nodes and I had to restart kamailio process to release it. I'm running Kam 5.2.5 Thanks. -- Andy Chen Sr. Telephony Lead Engineer achen@ <achen(a)thinkingphones.com>fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended … [View More]

2 6

How can I make calls between the two domains?
by Yanko 06 Dec '19

06 Dec '19

Hello: I have two virtual machines with two kamailo domains VM1: Domain: 172.16.16.1 Users:2000, 2001, 2002... VM2: Domain: 172.16.16.2 Users:3000, 3001, 3002... In each domain I can make calls. For example, user 2000 can call 2001. User 3000 can call 3001. How can I make calls between the two domains? What modules do I need to load? How to configure the kamailio.cfg file? Thanks, YANKO.

2 1

Scripts still valid?
by David Villasmil 05 Dec '19

05 Dec '19

Hello guys, Is this still valid? https://github.com/kamailio/kamailio/blob/master/misc/examples/scripts/ctd.… Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

3 4

call disconnected between 15 to 45 minutes
by Liu, Charles 05 Dec '19

05 Dec '19

Hi all, I am still looking for some help to debug why S-CSCF send BYE to caller and callee after a call was connected. from wireshark, I just saw S-CSCF send BYE to both caller and callee. That matched the S-CSCF debug output. But the question is why S-CSCF delete contact and send BYE to a active call? There was no timer expire or something like that in the log... Anyone can help? Thanks, --Charles 19(24) DEBUG: <core> [core/mem/q_malloc.c:519]: qm_free(): freeing frag. … [View More]0x7fb09413e6d0 alloc'ed from cdp: diameter_msg.c: AAATranslateMessage(484) 19(24) DEBUG: tm [t_lookup.c:1618]: t_lookup_ident(): transaction found 19(24) DEBUG: <core> [core/mem/q_malloc.c:367]: qm_malloc(): qm_malloc(0x7fb093db6000, 6872) called from core: core/sip_msg_clone.c: sip_msg_shm_clone(496) 19(24) DEBUG: <core> [core/mem/q_malloc.c:412]: qm_malloc(): qm_malloc(0x7fb093db6000, 6872) returns address 0x7fb09414d450 frag. 0x7fb09414d418 (size=6872) on 1 -th hit 19(24) ERROR: *** cfgtrace:failure_route=[REG_SAR_REPLY] c=[/etc/kamailio/kamailio.cfg] l=767 a=26 n=xlog 19(24) DEBUG: <script>: saa_return code is 1 19(24) ERROR: *** cfgtrace:failure_route=[REG_SAR_REPLY] c=[/etc/kamailio/kamailio.cfg] l=769 a=26 n=xlog 19(24) DEBUG: <script>: saa_return code (for scscf_save on register) is 1 19(24) ERROR: *** cfgtrace:failure_route=[REG_SAR_REPLY] c=[/etc/kamailio/kamailio.cfg] l=783 a=21 n=switch 19(24) ERROR: *** cfgtrace:failure_route=[REG_SAR_REPLY] c=[/etc/kamailio/kamailio.cfg] l=772 a=26 n=xlog 19(24) DEBUG: <script>: SAR success - 200 response sent from module 19(24) ERROR: *** cfgtrace:failure_route=[REG_SAR_REPLY] c=[/etc/kamailio/kamailio.cfg] l=773 a=2 n=exit 19(24) DEBUG: <core> [core/mem/q_malloc.c:475]: qm_free(): qm_free(0x7fb093db6000, 0x7fb09414d450), called from tm: t_reply.c: free_faked_req(948) 19(24) DEBUG: <core> [core/mem/q_malloc.c:519]: qm_free(): freeing frag. 0x7fb09414d418 alloc'ed from core: core/sip_msg_clone.c: sip_msg_shm_clone(496) 19(24) DEBUG: <core> [core/mem/q_malloc.c:475]: qm_free(): qm_free(0x7fb093db6000, 0x7fb09413e978), called from ims_registrar_scscf: cxdx_sar.c: free_saved_transaction_data(94) 19(24) DEBUG: <core> [core/mem/q_malloc.c:519]: qm_free(): freeing frag. 0x7fb09413e940 alloc'ed from ims_registrar_scscf: save.c: save(1414) 19(24) DEBUG: <core> [core/mem/q_malloc.c:475]: qm_free(): qm_free(0x7fb093db6000, 0x7fb09413e0b0), called from ims_registrar_scscf: reply.c: free_contact_buf(830) 19(24) DEBUG: <core> [core/mem/q_malloc.c:519]: qm_free(): freeing frag. 0x7fb09413e078 alloc'ed from ims_registrar_scscf: reply.c: build_contact(443) 19(24) DEBUG: <core> [core/mem/q_malloc.c:475]: qm_free(): qm_free(0x7fb093db6000, 0x7fb094145218), called from ims_registrar_scscf: reply.c: free_contact_buf(835) 19(24) DEBUG: <core> [core/mem/q_malloc.c:519]: qm_free(): freeing frag. 0x7fb0941451e0 alloc'ed from ims_registrar_scscf: reply.c: build_contact(435) 19(24) DEBUG: <core> [core/mem/q_malloc.c:475]: qm_free(): qm_free(0x7fb093db6000, 0x7fb094147dc0), called from ims_registrar_scscf: cxdx_sar.c: free_saved_transaction_data(98) 19(24) DEBUG: <core> [core/mem/q_malloc.c:519]: qm_free(): freeing frag. 0x7fb094147d88 alloc'ed from ims_registrar_scscf: save.c: save(1396) 19(24) DEBUG: <core> [core/mem/q_malloc.c:475]: qm_free(): qm_free(0x7fb093db6000, 0x7fb09415b4c8), called from cdp: transaction.c: cdp_free_trans(182) 19(24) DEBUG: <core> [core/mem/q_malloc.c:519]: qm_free(): freeing frag. 0x7fb09415b490 alloc'ed from cdp: transaction.c: cdp_add_trans(110) 19(24) DEBUG: <core> [core/mem/q_malloc.c:475]: qm_free(): qm_free(0x7fb093db6000, 0x7fb0941442a0), called from cdp: transaction.c: cdp_free_trans(183) 19(24) DEBUG: <core> [core/mem/q_malloc.c:519]: qm_free(): freeing frag. 0x7fb094144268 alloc'ed from cdp: transaction.c: cdp_add_trans(105) 13(18) DEBUG: ims_usrloc_scscf [ims_usrloc_scscf_mod.c:481]: timer(): Syncing cache 13(18) DEBUG: ims_usrloc_scscf [udomain.c:291]: mem_timer_udomain(): *** mem_timer_udomain - checking contacts - START *** 13(18) DEBUG: ims_usrloc_scscf [udomain.c:301]: mem_timer_udomain(): We have a [3gpp=0] contact in the new contact list in slot 95 = [sip:bob@ims.mnc001.mnc001.3gppnetwork.org] (sip:bob@192.168.164.248:50448;rinstance=989f943bd5098a11;transport=UDP) which expires in -60.000000 seconds and has a ref count of 0 (state: Contact with delayed delete) 13(18) DEBUG: ims_usrloc_scscf [udomain.c:309]: mem_timer_udomain(): contact in state CONTACT_DELATED_DELETE is about to be deleted13(18) DEBUG: ims_usrloc_scscf [udomain.c:301]: mem_timer_udomain(): We have a [3gpp=0] contact in the new contact list in slot 464 = [sip:alice@ims.mnc001.mnc001.3gppnetwork.org] (sip:alice@192.168.164.203:44640;rinstance=e35e9704884c3208;transport=UDP) which expires in 50.000000 seconds and has a ref count of 1 (state: Contact valid) 13(18) DEBUG: ims_usrloc_scscf [udomain.c:301]: mem_timer_udomain(): We have a [3gpp=0] contact in the new contact list in slot 478 = [sip:bob@ims.mnc001.mnc001.3gppnetwork.org] (sip:bob@192.168.164.248:50448;rinstance=9e742618a5f6bcae;transport=UDP) which expires in 56.000000 seconds and has a ref count of 1 (state: Contact valid) 13(18) DEBUG: ims_usrloc_scscf [udomain.c:353]: mem_timer_udomain(): *** mem_timer_udomain - checking contacts - FINISHED *** 13(18) DEBUG: ims_usrloc_scscf [udomain.c:359]: mem_timer_udomain(): *** mem_timer_udomain - checking IMPUs - START *** 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:372]: process_impurecord(): Checking validity of IMPU: <sip:alice@ims.mnc001.mnc001.3gppnetwork.org> registration subscriptions 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:404]: process_impurecord(): Public Identity sip:alice@ims.mnc001.mnc001.3gppnetwork.org, Barred: [0], State: [registered], contacts [1], 3gppcontacts [0] 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:441]: process_impurecord(): Contact #0 - sip:alice@192.168.164.203:44640;rinstance=e35e9704884c3208;transport=UDP, Ref [1] (expires in 50 seconds) (State: 0) 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:372]: process_impurecord(): Checking validity of IMPU: <sip:bob@ims.mnc001.mnc001.3gppnetwork.org> registration subscriptions 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:404]: process_impurecord(): Public Identity sip:bob@ims.mnc001.mnc001.3gppnetwork.org, Barred: [0], State: [registered], contacts [1], 3gppcontacts [0] 3(18) DEBUG: ims_usrloc_scscf [impurecord.c:441]: process_impurecord(): Contact #0 - sip:bob@192.168.164.248:50448;rinstance=9e742618a5f6bcae;transport=UDP, Ref [1] (expires in 56 seconds) (State: 0) 3(18) DEBUG: ims_usrloc_scscf [udomain.c:384]: mem_timer_udomain(): *** mem_timer_udomain - checking IMPUs - FINISHED *** 3(18) DEBUG: ims_usrloc_scscf [udomain.c:406]: mem_timer_udomain(): deleting contact [sip:bob@ims.mnc001.mnc001.3gppnetwork.org] 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:598]: delete_scontact(): Deleting contact: [sip:bob@192.168.164.248:50448;rinstance=989f943bd5098a11;transport=UDP] 13(18) DEBUG: ims_usrloc_scscf [usrloc_db.c:370]: db_delete_ucontact(): Deleting ucontact [sip:bob@192.168.164.248:50448;rinstance=989f943bd5098a11;transport=UDP] 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:310]: mem_delete_ucontact(): Checking if dialog_data is there and needs to be torn down 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:314]: mem_delete_ucontact(): first dialog is not 0 13(18) DEBUG: ims_usrloc_scscf [impurecord.c:317]: mem_delete_ucontact(): Going to tear down dialog with info h_entry [1694] h_id [3889] 13(18) DEBUG: ims_dialog [dlg_hash.c:887]: lookup_dlg(): ref dlg 0x7fb09414ce40 with 1 -> 3 13(18) DEBUG: ims_dialog [dlg_hash.c:889]: lookup_dlg(): dialog id=3889 found on entry 1694 13(18) DEBUG: ims_dialog [dlg_hash.c:1066]: unref_dlg(): unref dlg 0x7fb09414ce40 with 1 -> 2 13(18) DEBUG: ims_dialog [dlg_req_within.c:379]: dlg_terminate(): terminating confirmed dialog 13(18) DEBUG: <core> [core/mem/q_malloc.c:367]: qm_malloc(): qm_malloc(0x7fb09b5ae010, 18) called from ims_dialog: dlg_req_within.c: build_extra_hdr(229) 13(18) DEBUG: <core> [core/mem/q_malloc.c:412]: qm_malloc(): qm_malloc(0x7fb09b5ae010, 24) returns address 0x7fb09b640c30 frag. 0x7fb09b640bf8 (size=64) on 1 -th hit 13(18) DEBUG: <core> [core/mem/q_malloc.c:367]: qm_malloc(): qm_malloc(0x7fb09b5ae010, 248) called from ims_dialog: dlg_req_within.c: build_dlg_t(81) 13(18) DEBUG: <core> [core/mem/q_malloc.c:412]: qm_malloc(): qm_malloc(0x7fb09b5ae010, 248) returns address 0x7fb09b74b100 frag. 0x7fb09b74b0c8 (size=248) on 1 -th hit 13(18) DEBUG: <core> [core/mem/q_malloc.c:367]: qm_malloc(): qm_malloc(0x7fb09b5ae010, 72) called from core: core/parser/parse_rr.c: do_parse_rr_body(68) 13(18) DEBUG: <core> [core/mem/q_malloc.c:412]: qm_malloc(): qm_malloc(0x7fb09b5ae010, 72) returns address 0x7fb09b74b048 frag. 0x7fb09b74b010 (size=80) on 1 -th hit 13(18) DEBUG: ims_dialog [dlg_req_within.c:272]: send_bye(): sending BYE to caller 13(18) DEBUG: ims_dialog [dlg_hash.c:1047]: ref_dlg(): ref dlg 0x7fb09414ce40 with 1 -> 3 CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient and may contain material that is proprietary, confidential, privileged or otherwise legally protected or restricted under applicable government laws. Any review, disclosure, distributing or other use without expressed permission of the sender is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies without reading, printing, or saving. [View Less]

2 2

Question regarding priority in dispatcher module
by Floimair Florian 05 Dec '19

05 Dec '19

Dear all! After reading the documentation on dispatcher module I still have a question that isn't really documented. Regarding the priority value of an entry in a dispatcher list: Is a lower numerical priority value regarded as higher priority or is it the other way around? Hopefully someone can help me to clarify this. With best regards FLORIAN FLOIMAIR Software Development Commend International GmbH Saalachstrasse 51 5020 Salzburg, Austria commend.com LG Salzburg / FN 178618z

2 2

Re: [SR-Users] RTPengine with rejected RE-INVITE when port is changing
by Daniel Tryba 05 Dec '19

05 Dec '19

On Thu, Dec 05, 2019 at 09:37:51AM +0000, Laurent Schweizer wrote: > Hello, > > I already see old post about this : > https://opensips.org/pipermail/users/2014-November/030451.html > > but I???m interested to know if now they is a solution ???? > > so the issue is a RE-INVITE rejected (415 Unsupported Media or 488 ) and the RTP port is changing. > Is that case the old RTP relay (I???m using RTPengine) is destroyed after 30sec. > Any way to restore them ? I'm … [View More]

3 2

siputils: how does sip_p_charging_vector generate the header
by George Diamantopoulos 05 Dec '19

05 Dec '19

Hello, I've been looking at the sip_p_charging_vector() function of siputils. From the documentation it is not evident how the PCV header is generated. Are the exported $pcv pseudovariables writable, so that the function canl use those when generating the header? Thanks! BR, George

2 3

anycast + dmq_usrloc
by Nuno Miguel Reis 05 Dec '19

05 Dec '19

Hi guys. I'm setting up an anycast scenario with several kamailios sharing an active state and I've noticed that the dmq_usrloc module is not replication the usrloc socket_info attribute when a register comes in through one of the kamailio nodes. Is there a reason behind this? I'm thinking on adding the replication for that attribute in the code. Another way of address this woud be by having a modparam to replicate the socket. What do you think? This is what I'm seeing: *anycast node that … [View More]actually gets the SIP REGISTER:* $ kamcmd ul.dump { Domains: { Domain: { Domain: location Size: 32768 AoRs: { Info: { AoR: 309(a)nmreis.test HashID: -35263718 Contacts: { Contact: { Address: sip:309@192.168.150.158:55060;transport=udp;registering_acc=nmreis_test Expires: 585 Q: -1.000000 Call-ID: 6e7635ce4604e16400ee763b2ead55b2@0:0:0:0:0:0:0:0 CSeq: 4 User-Agent: Jitsi2.11.5602Linux Received: sip: 2.2.2.2:31171 Path: [not set] State: CS_SYNC Flags: 1 CFlags: 192 Socket: udp: 1.1.1.1:5060 Methods: -1 Ruid: uloc-5de8056d-22ab-f Instance: [not set] Reg-Id: 0 Server-Id: 0 Tcpconn-Id: -1 Keepalive: 1 Last-Keepalive: 1575487540 Last-Modified: 1575487540 } } } } Stats: { Records: 1 Max-Slots: 1 } } } } *anycast node that gets the USRLOC update via KDMQ:* $ kamcmd ul.dump { Domains: { Domain: { Domain: location Size: 32768 AoRs: { Info: { AoR: 309(a)nmreis.test HashID: -35263718 Contacts: { Contact: { Address: sip:309@192.168.150.158:55060;transport=udp;registering_acc=nmreis_test Expires: 574 Q: -1.000000 Call-ID: 6e7635ce4604e16400ee763b2ead55b2@0:0:0:0:0:0:0:0 CSeq: 4 User-Agent: Jitsi2.11.5602Linux Received: sip: 2.2.2.2:31171 Path: [not set] State: CS_SYNC Flags: 1 CFlags: 192 Socket: [not set] Methods: -1 Ruid: uloc-5de7ff7b-4617-3 Instance: [not set] Reg-Id: 0 Server-Id: 0 Tcpconn-Id: -1 Keepalive: 1 Last-Keepalive: 1575487540 Last-Modified: 1575487540 } } } } Stats: { Records: 1 Max-Slots: 1 } } } } *the actual KDMQ message:* *KDMQ sip:usrloc@10.100.100.21:5060 <http://sip:usrloc@10.100.100.21:5060> SIP/2.0 Via: SIP/2.0/UDP 10.100.100.22;branch=z9hG4bK6034.290e4186000000000000000000000000.0 To: <sip:usrloc@10.100.100.21:5060 <http://sip:usrloc@10.100.100.21:5060>> From: <sip:usrloc@10.100.100.22:5060 <http://sip:usrloc@10.100.100.22:5060>>;tag=3393f0703fb0ccaca74109ff37de39f5-1e4c092b CSeq: 10 KDMQ Call-ID: 0cfde4d32a31addc-8875(a)127.0.0.1 <0cfde4d32a31addc-8875(a)127.0.0.1> Content-Length: 433 Max-Forwards: 1 Content-Type: application/json {"action":1,"aor":"309(a)nmreis.test","ruid":"uloc-5de8056d-22ab-f","c":"sip:309@192.168.150.158:55060;transport=udp;registering_acc=nmreis_test","received":"sip:2.2.2.2:31171 <http://2.2.2.2:31171>","path":"","callid":"6e7635ce4604e16400ee763b2ead55b2@0:0:0:0:0:0:0:0","user_agent":"Jitsi2.11.5602Linux","instance":"","expires":1575487600,"cseq":2,"flags":1,"cflags":192,"q":-1,"last_modified":1575487000,"methods":4294967295,"reg_id":0,"server_id":0}* -- Nuno Miguel Reis Departamento de Engenharia Informática Faculdade de Ciências e Tecnologia Universidade de Coimbra mobile: +351 918519145 -- get my PGP key @ http://pgp.dei.uc.pt:11371/pks/lookup?op=get&search=0x750296EECEAD2B6D [View Less]

2 2

anycast + dmq_usrloc
by Nuno Miguel Reis 04 Dec '19

04 Dec '19

Hi guys. I'm setting up an anycast scenario with several kamailios sharing an active state and I've noticed that the dmq_usrloc module is not replicating the usrloc socket_info attribute when a register comes in through one of the kamailio nodes. Is there a reason behind this? I'm thinking on adding the replication for that attribute in the code. Another way of address this woud be by having a modparam to replicate the socket. What do you think? This is what I'm seeing: anycast node that … [View More]actually gets the SIP REGISTER: $ kamcmd ul.dump { Domains: { Domain: { Domain: location Size: 32768 AoRs: { Info: { AoR: 309(a)nmreis.test HashID: -35263718 Contacts: { Contact: { Address: sip:309@192.168.150.158:55060;transport=udp;registering_acc=nmreis_test Expires: 585 Q: -1.000000 Call-ID: 6e7635ce4604e16400ee763b2ead55b2@0:0:0:0:0:0:0:0 CSeq: 4 User-Agent: Jitsi2.11.5602Linux Received: sip: 2.2.2.2:31171 [http://2.2.2.2:31171/] Path: [not set] State: CS_SYNC Flags: 1 CFlags: 192 Socket: udp: 1.1.1.1:5060 [http://1.1.1.1:5060/] Methods: -1 Ruid: uloc-5de8056d-22ab-f Instance: [not set] Reg-Id: 0 Server-Id: 0 Tcpconn-Id: -1 Keepalive: 1 Last-Keepalive: 1575487540 Last-Modified: 1575487540 } } } } Stats: { Records: 1 Max-Slots: 1 } } } } anycast node that gets the USRLOC update via KDMQ: $ kamcmd ul.dump { Domains: { Domain: { Domain: location Size: 32768 AoRs: { Info: { AoR: 309(a)nmreis.test HashID: -35263718 Contacts: { Contact: { Address: sip:309@192.168.150.158:55060;transport=udp;registering_acc=nmreis_test Expires: 574 Q: -1.000000 Call-ID: 6e7635ce4604e16400ee763b2ead55b2@0:0:0:0:0:0:0:0 CSeq: 4 User-Agent: Jitsi2.11.5602Linux Received: sip: 2.2.2.2:31171 [http://2.2.2.2:31171/] Path: [not set] State: CS_SYNC Flags: 1 CFlags: 192 Socket: [not set] Methods: -1 Ruid: uloc-5de7ff7b-4617-3 Instance: [not set] Reg-Id: 0 Server-Id: 0 Tcpconn-Id: -1 Keepalive: 1 Last-Keepalive: 1575487540 Last-Modified: 1575487540 } } } } Stats: { Records: 1 Max-Slots: 1 } } } } the actual KDMQ message: KDMQ sip:usrloc@10.100.100.21:5060 [http://sip:usrloc@10.100.100.21:5060/] SIP/2.0 Via: SIP/2.0/UDP 10.100.100.22;branch= z9hG4bK6034.290e4186000000000000000000000000.0 To: < sip:usrloc@10.100.100.21:5060 [http://sip:usrloc@10.100.100.21:5060/] > From: < sip:usrloc@10.100.100.22:5060 [http://sip:usrloc@10.100.100.22:5060/] >;tag= 3393f0703fb0ccaca74109ff37de39f5-1e4c092b CSeq: 10 KDMQ Call-ID: 0cfde4d32a31addc-8875(a)127.0.0.1 [mailto:0cfde4d32a31addc-8875@127.0.0.1] Content-Length: 433 Max-Forwards: 1 Content-Type: application/json {"action":1,"aor":"309(a)nmreis.test","ruid":"uloc-5de8056d-22ab-f","c":"sip:309@192.168.150.158:55060;transport=udp;registering_acc=nmreis_test","received":"sip: 2.2.2.2:31171 [http://2.2.2.2:31171/] ","path":"","callid":"6e7635ce4604e16400ee763b2ead55b2@0:0:0:0:0:0:0:0","user_agent":"Jitsi2.11.5602Linux","instance":"","expires":1575487600,"cseq":2,"flags":1,"cflags":192,"q":-1,"last_modified":1575487000,"methods":4294967295,"reg_id":0,"server_id":0} Looking forward to hear from you. BR, -- Nuno Miguel Reis Departamento de Engenharia Informática Faculdade de Ciências e Tecnologia Universidade de Coimbra [View Less]

1 0

Vendor Specific RBT Call Flow
by Hamid Hashmi 04 Dec '19

04 Dec '19

Dear Users Can the following call flow be implemented, if yes, can you give some suggestions with modules information? [cid:d15f60e7-73ec-4cd8-8954-92f472a94ef7] Regards Hamid R. Hashmi

3 2

siremis help and usage index?
by PICCORO McKAY Lenz 04 Dec '19

04 Dec '19

it's there some help manual usage for siremis? the only KB source i have are asipto.. and only are install manuals!! Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com

3 2

Re: [SR-Users] kamailio IMS supporting VOLTE
by Shubhendu Das 04 Dec '19

04 Dec '19

Hi , Does Kamailio has its own HSS supporting CX Interface ? BR, Shubhendu From: sr-users [mailto:sr-users-bounces@lists.kamailio.org] On Behalf Of Mojtaba Sent: Saturday, November 23, 2019 4:37 PM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] kamailio IMS supporting VOLTE Hello, Running the IMS network for supporting VoLTE with Kamailio module and FHOSS is challenging. THe Kamailio works great in IMS network but You have to optimise your own database. … [View More]Using FHOSS without any support or development is very risky. In general speaking, running VoLTE have three main section and the IMS network is one of them. You might have some challenges in EPC and RAN access. WIth Best Regards. Mojtaba On Thu, Nov 21, 2019 at 3:23 PM Shubhendu Das <shubhendu.das(a)azcom.in> wrote: Hi , I have a query regarding Kamailio open source SIP server. Does it have any release, where its supports the feature of IMS supporting VOLTE with real commercial mobile phones(IMSI based) ? If so, what is the release number ? Please also let me know about the supported mobile phones list. BR, Shubhendu Disclaimer: This email and any files transmitted along with it may contain Azcom confidential and proprietary information. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action based on the contents of the information contained herein is strictly prohibited. If you are not an intended recipient of this transmission and you received it in error, please inform the sender by reply e-mail and destroy this and all other copies of this transmission to which you have access. The sender of this email or Azcom does not accept liability for any errors or omissions in the contents of this message that may occur as a result._______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- --Mojtaba Esfandiari.S -- _Disclaimer: This email and any files transmitted along with it may contain Azcom confidential and proprietary information. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action based on the contents of the information contained herein is strictly prohibited. If you are not an intended recipient of this transmission and you received it in error, please inform the sender by reply e-mail and destroy this and all other copies of this transmission to which you have access. The sender of this email or Azcom does not accept liability for any errors or omissions in the contents of this message that may occur as a result._ [View Less]

2 1

Fwd: app-ads.txt monetization proposal
by Joel Serrano 04 Dec '19

04 Dec '19

Not sure if this is BS or worth exploring, it's not my expertise area so I'm forwarding to you all just in case ---------- Forwarded message --------- From: Lorenzo from Instal <lorenzo.tacchio(a)instal.com> Date: Tue, Dec 3, 2019 at 8:56 AM Subject: app-ads.txt monetization proposal To: <joel(a)textplus.com> app-ads.txt monetization proposal Hello , I am Lorenzo, Senior Account Manager at Instal; we are currently buying your app's traffic via DSPs. We thought would be … [View More]

1 1

secfilter usage
by Aymeric Moizard 03 Dec '19

03 Dec '19

Hi all, I'm testing and moving my kamailio script to use the newer secfilter module. In the past, I was replying "200 Ok" to "friendly scanners"... With the newer secfilter module, it looks like I can't send a reply with "sl_send_reply("200", "OK")" secf_check_ua(); if ($? == -2) { sl_send_reply("200", "OK"); exit; } I have read the code of the secfilter, but I was not able to see any specific code to silently discard the SIP request. I can see in the documentation about "… [View More]

2 5

kamailio IMS supporting VOLTE
by Shubhendu Das 03 Dec '19

03 Dec '19

Hi , I have a query regarding Kamailio open source SIP server. Does it have any release, where its supports the feature of IMS supporting VOLTE with real commercial mobile phones(IMSI based) ? If so, what is the release number ? Please also let me know about the supported mobile phones list. BR, Shubhendu -- _Disclaimer: This email and any files transmitted along with it may contain Azcom confidential and proprietary information. If you are not the intended recipient, you … [View More]

2 2

Contact header requirement
by David Villasmil 02 Dec '19

02 Dec '19

Hello guys, I'm connecting to a provider who requires the contact contains the proxy's IP... I know this is weird and totally off-rfc... I setup the topoh module and used modparam("topoh", "mask_ip", "[PROXY_IP]:5060") but this makes the contact: Contact: <sip:[PROXY_IP]:5060;line=sr-Z213nshDqt98-2qiIoT8GFf. y8PWype.SRy0nRo3nCT*> I know this is how it works, but they don't like the additional ";line=...." Has anyone faced this kind of thing? is there any other way to set this to … [View More]

3 7

$null + 0 is not int
by Juha Heinanen 02 Dec '19

02 Dec '19

Why is it that $null + 0 is 0 but not int? What is it? -- Juha $avp(test) = $null + 0; if (is_int("$avp(test)")) INFO(test $avp(test) IS int); else INFO(test $avp(test) IS NOT int); Dec 1 02:46:01 salmon /usr/bin/sip-proxy[10138]: INFO: test 0 IS NOT int

2 5

Kamailio World 2020 - Call For Presentations
by Daniel-Constantin Mierla 02 Dec '19

02 Dec '19

Hello, I would like to announce that Call for Presentations at Kamailio World 2020 is now open. You can submit your proposal or see more details at: - https://www.kamailioworld.com/k08/call-for-speakers/ The 8th edition of the event takes place again in Berlin, Germany, during April 27-29, 2020. Expect over 150 participants, developers and community members as well as representatives of other popular open source VoIP projects such as Asterisk or FreeSwitch. Looking forward to meeting … [View More]

1 0

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