sr-users June 2019

sr-users@lists.kamailio.org

63 participants
93 discussions

Start a nNew thread

does kamailio support graph database ??
by Gaurav Bmotra 26 Jun '19

26 Jun '19

hi i m using kamailio 5.1 , does kamailio support graph database ?? thank you -- *Regards:* Gaurav Kumar

2 1

MongoDB for Kamailio
by Gaurav Bmotra 26 Jun '19

26 Jun '19

hi i m using kamailio 5.1 , on Ubuntu 18.4 and right now i m using Maria DB for kamailio , but i want to migrate my Maria data to MingoDB ,, plz help me how can i use MOngoDB with kamailio thanks -- *Regards:* Gaurav Kumar

2 1

Presence publish manipulation
by Gertjan Wolzak 26 Jun '19

26 Jun '19

Hello Kamailions, I'm running into the following challenge. A kamailio setup where phones register with their mac address as uid and a password. Users have to login to the system by dialing a special number where they have to enter their internal extension and a pin code. Now the system knows which extension(number) is logged in on which phone(macaddress). This is done with from updates, just a type of hotdesking. Now I want to use presence.... When a phone makes a phone call, kamailio generates a publish message where the "local" part of the xml code contains the mac address. How can I manipulate the Publish xml information? I mean the manipulation can be done with textops, but which variables to use and where in the configuration? Im asking because when I disable the presence route and do not call it in my configuration, but with presence enabled, I still get Publish messages.... I have tried adding a Sender header which contains the "extension" of the phone and then call the publish in the PRESENCE route like this: handle_publish("$hdr(Sender)"); But this does not change the xml information. Am I doing things wrong? Below the first publish message that is send, where 10.88.77.172 is the kamailio server. U 2019/06/26 14:54:37.233345 10.88.77.172:5060 -> 10.88.77.172:5060 #7 PUBLISH sip:0015659a9931@10.88.77.172:5060 SIP/2.0. Via: SIP/2.0/UDP 10.88.77.172;branch=z9hG4bK1a87.5510d093000000000000000000000000.0. To: <sip:0015659a9931@10.88.77.172:5060>. From: <sip:0015659a9931@10.88.77.172:5060>;tag=a2652bb825a097f3b7285d4c70edd51a-5c5d. CSeq: 10 PUBLISH. Call-ID: 173009c21f4e3c77-94480(a)10.88.77.172. Content-Length: 579. User-Agent: kamailio (5.1.8 (x86_64/linux)). Max-Forwards: 70. Event: dialog. Expires: 125. Content-Type: application/dialog-info+xml. . <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" entity="sip:0015659a9931@10.88.77.172:5060"> <dialog id="0_2285997339(a)10.88.77.184" call-id="0_2285997339(a)10.88.77.184" direction="initiator"> <state>Trying</state> <remote> <identity>sip:604113@10.88.77.172:5060</identity> <target uri="sip:604113@10.88.77.172:5060"/> </remote> <local> <identity>sip:0015659a9931@10.88.77.172:5060</identity> <target uri="sip:0015659a9931@10.88.77.172:5060"/> </local> </dialog> </dialog-info> I would like to change the local identity and target uri into the extension assigned to that phone, for example 604114.... So that subscribers to the extension 604114 get informed about the state of the phone with the used uid 0015659a9931. Feedback would be appricated. Pointers to where I am going wrong as well, ... that's feedback too. Rgds, Gertjan

1 0

TOPOS uid in contact param instead of username
by Thomas Weber 26 Jun '19

26 Jun '19

Hello, we're using topos/redis since some time and it's working quite well for most situations. It's used to route asterisk traffic to sip providers. Some providers, however, are validating the contact header strictly against i.e. the accounts username and so we have to disable topos by using event_route[topos:msg-sending]. Now i'm wondering if it would be useful to other people to add a mode to topos where the topos uid is not forwarded as contact username but instead added as a contact uri param. So instead of e.g. Contact: <sip:btpsh-5abcdef5-374-1@x.x.x.x:5060;transport=tcp> it would use Contact: <sip:+49......@x.x.x.x:5060;transport=tcp;line=btpsh-5abcdef5-374-1>. What do you think? Would it make sense? Is it a lot of effort? Cheers, Thomas

4 4

Apache version for FHoSS
by Woscek, Martin W. 26 Jun '19

26 Jun '19

Hello all, What is the version of Apache that FHoSS was built to? Thanks, Martin

2 1

Info: ClueCon Weekly - Kamailio Project Updates
by Daniel-Constantin Mierla 25 Jun '19

25 Jun '19

Hello, later today I will join ClueCon Weekly for a discussion about what is new for Kamailio project and the plans for the future. ClueCon Weekly is a web video conference organized by the FreeSwitch project team. They announced recently a revamp of the format, however, I expect that other people can still join live if they want to listen and ask questions, couple of ways to connect being listed at: * https://freeswitch.org/confluence/display/FREESWITCH/ClueCon+Weekly+Confere… If joining live is no longer possible, I will post a link to the recording and if someone has any questions following my presentation, I can answer here. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

2 4

Carrier Route installation Failed
by Amar Tinawi 24 Jun '19

24 Jun '19

Hello i'm facing a dependency error when trying to install kamailio 5.2.3+xenial with carrier route module using apt package installer The following packages have unmet dependencies: kamailio-carrierroute-modules : Depends: kamailio (= 4.3.4-1.1ubuntu2) but 5.2.3+xenial is to be installed E: Unable to correct problems, you have held broken packages. all other modules installed fine any suggestions? thanks in advance

4 5

Kamailio routing BYE back to originator
by Andrew White 24 Jun '19

24 Jun '19

Hi team! I’ve recently found an issue in my Kamailio setup. It appears when the trunk replies to call in progress with a BYE, we relay it immediately back to them: https://i.imgur.com/h5fusau.png <https://i.imgur.com/h5fusau.png> The only differences in the second BYE is the Route header is removed and replaced with a Via header referencing the Kamailio machine, and the From URI is rewritten to show the Kamailio hostname. I’m unsure what steps I can take here, as all of my out of dialog messages (180, 200, ACK) are forwarded along with no issue. It seems only the in dialog are having this issue. Here’s my WITHINDLG and RELAY: def ksr_route_relay() if KSR.is_method_in("IBSU") then if KSR::TM.t_is_set("branch_route") < 0 then KSR::TM.t_on_branch("ksr_branch_manage") end end if KSR.is_method_in("ISU") then if KSR::TM.t_is_set("onreply_route") < 0 then KSR::TM.t_on_reply("ksr_onreply_manage") end #KSR.info("Onreply route: #{KSR::TM.t_is_set("onreply_route")}") end if KSR.is_INVITE() then if KSR::TM.t_is_set("failure_route") < 0 then KSR::TM.t_on_failure("ksr_failure_manage") end end if KSR::TM.t_relay() < 0 then KSR::SL.sl_reply_error() end exit end def ksr_route_withindlg() return if KSR::SIPUTILS.has_totag() < 0 if KSR::RR.loose_route() > 0 then ksr_route_dlguri() if KSR.is_BYE() then #KSR.setflag($myenv['FLT_ACC'].to_i) #KSR.setflag($myenv['FLT_ACCFAILED'].to_i) elsif KSR.is_ACK() then ksr_route_natmanage() elsif KSR.is_NOTIFY() then KSR::RR.record_route() end ksr_route_relay() exit end if KSR.is_ACK() then #KSR.info("Handling an ACK within dialog") if KSR::TM.t_check_trans() > 0 then ksr_route_relay() exit else exit end end #KSR.info("404ing within dialog") KSR::SL.sl_send_reply(404, "Not here"); exit end I suspect I must be sending this to the wrong branch somehow, but I’m unsure how to correct this. The call gets originally initiated from Kamailio writing a custom RURI and To header before calling t_relay(). I’m wondering if I’m somehow initiating the dialog incorrectly and as such the BYE doesn’t know where to go. Thanks! Andrew

2 3

Kamailio config file flow chart
by Gaurav Bmotra 22 Jun '19

22 Jun '19

hi i m looking for kamailio config file flow chart ,,, if any one have plz provide thanks -- *Regards:* Gaurav Kumar

2 1

5.2.3 - dispatcher module looses setid
by Andrew Chen 21 Jun '19

21 Jun '19

Hi all, For a few times now I've noticed Kamailio 5.2.3 dispatcher module looses view of setid destination and this system been up and running for 13 days: root:~# kamcmd dispatcher.list | grep ash.tpgw.service To work around it, we have to reload the module again: root:~# kamcmd dispatcher.reload root:~# kamcmd dispatcher.list | grep ash.tpgw.service URI: sip:<some host>:5062 URI: sip:<some host>:5060 root:~# Process been running for several days: root:~# ps -elf | grep kam 0 S root 8484 6520 0 80 0 - 3714 pipe_w 16:04 pts/0 00:00:00 grep --color=auto kam 5 S kamailio 32086 1 0 80 0 - 214845 pause Jun17 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio 1 S kamailio 32164 32086 0 80 0 - 233341 skb_wa Jun17 ? 00:00:02 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio 1 S kamailio 32165 32086 0 80 0 - 233342 skb_wa Jun17 ? 00:00:02 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio 1 S kamailio 32166 32086 0 80 0 - 233341 skb_wa Jun17 ? 00:00:02 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio 1 S kamailio 32167 32086 0 80 0 - 233341 skb_wa Jun17 ? 00:00:02 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio 1 S kamailio 32168 32086 0 80 0 - 214875 skb_wa Jun17 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio 1 S kamailio 32169 32086 0 80 0 - 214875 skb_wa Jun17 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio 1 S kamailio 32170 32086 0 80 0 - 214875 skb_wa Jun17 ? 00:00:00 /usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 512 -M 64 -u kamailio -g kamailio Anyone seen this? 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 recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

2 3

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

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 June 2019