sr-users January 2019

sr-users@lists.kamailio.org

84 participants
104 discussions

IMS early media
by Tsvetan Filev 31 Jan '19

31 Jan '19

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

2 8

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

31 Jan '19

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

2 2

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

31 Jan '19

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

1 0

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

31 Jan '19

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

1 1

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

30 Jan '19

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

5 9

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

30 Jan '19

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

1 0

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

29 Jan '19

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

2 2

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

29 Jan '19

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

2 1

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

28 Jan '19

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

1 0

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

28 Jan '19

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

2 2

2026

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