sr-users December 2014

sr-users@lists.kamailio.org

84 participants
123 discussions

How to Fix the RTP Engine SDP Rewriting direction.
by Mahmoud Ramadan Ali 16 Dec '14

16 Dec '14

Hi Dears, I'm working on integrating the rtpengine to work with Kamailio as RTP proxy and i have successfully configured the rtpengine in multi home mode to proxy the media and rewrite the SDP message whenever it passes trough the Kamailio internal interface to the external interface and vice versa using this command. root@debian:/usr/local/etc/kamailio# rtpengine --interface=Kamailio-Internal/192.168.100.1 --interface=Kamailio-External/ 192.168.50.1 --listen-ng=127.0.0.1:22222 --pidfile=/var/run/ngcp-rtpengine-daemon.pid Also i have configured the "i" and "e" flags in the route[NATMANAGE] to take care of the SDP rewriting direction the same way it worked before with my rtpproxy module configuration. But the issue now is that whenever i make a call from the external to the internal the rtpengine can NOT detect the right direction as colored in red below so my question now is : How to set the direction of the rtpengine to designate that the interface 192.168.50.1 is the external and 192.168.100.1 is the internal ? Dec 16 09:28:09 debian rtpengine[4714]: Got valid command from 127.0.0.1:50639: offer - { "sdp": "v=0#015#012o=- 13063213690566395 1 IN IP4 192.168.50.2#015#012s=X-Lite release 4.7.1 stamp 74247#015#012c=IN IP4 192.168.50.2#015#012t=0 0#015#012m=audio 56078 RTP/AVP 125 100 0 9 8 101#015#012a=rtpmap:125 opus/48000/2#015#012a=fmtp:125 useinbandfec=1#015#012a=rtpmap:100 speex/16000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101 0-15#015#012a=sendrecv#015#012", "direction": [ "internal", "external" ], "flags": [ "asymmetric", "trust-address", "symmetric" ], "replace": [ "session-connection", "orig ... Best Regards and Thanks in advance.

2 1

IPv6 socket issues
by Kees Meijs - SIGNET B.V. 16 Dec '14

16 Dec '14

Good evening, During pre-production testing, we discovered quite odd IPv6 socket issues. Problems arise when a SIP dialog is initiated from within Kamailio (e.g. a SIP INVITE message). Using ngrep, it seems very odd IPv6 sockets are opened, for example: > U 2001:beef:34a:10::234:5060 -> 2001:beef:285:1::3:5060 1573541542@0:1440 > U 2001:beef:34a:10::234 -> 2001:beef:285:1::3 +1573541542@1448:17 Obviously the "1573541542@0:1440" part is bogus, I expect output similar to: > U 2001:beef:34a:10::234:5060 -> 2001:beef:285:1::3:5060 > INVITE sip:s@[2001:beef:285:1::3]:5060 SIP/2.0. When I do a REGISTER from UA using IPv6, the dialog (and return packets) seem completely normal. Using IPv4, there's no problem at all. It seems the socket problems are triggered when: 1. Using the topoh module. 2. When altering From: headers e.g. using uac_replace_from(). When topoh is disabled and no headers are altered, IPv6 works as good as IPv4. We could reproduce the problem using Kamailio 4.1.4, 4.1.5 and 4.2.0 on Debian (64-bit). Please advice what to do. Thanks in advance! Best regards, Kees

2 4

Re: [SR-Users] sr-users Digest, Vol 115, Issue 15
by Kees Meijs - SIGNET B.V. 16 Dec '14

16 Dec '14

Hi Daniel, Thank you very much for your prompt response. The output mentioned is generated by ngrep and can be seen by tcpdump as well. It seems a "space" and the bogus part ends up after the port used in the socket opened. For example "5060" becomes "5060 yadieyaboguspartdrdfg5r3245234". Obviously sending a packet towards an IPv6 address using such a port doesn't work. For the time being, we disabled the topoh.so module and rewrote code using uac_replace_from() and substituded the code with $fn = "string", $fd = "otherstring" equivalents. Thanks again! Cheers, Kees

1 0

Kamailio AVPs Radius
by Kalala Alexander 16 Dec '14

16 Dec '14

Radius server sends a response containing an attribute (Session-Timeout (27): 2342). How is the value saved in the AVPs using module auch_radius? Config: modparam("auth_radius", "radius_config","/etc/radiusclient-ng/radiusclient.conf") modparam("auth_radius", "service_type",15) modparam("auth_radius", "use_ruri_flag", 22) modparam("auth_radius", "auth_extra", "Calling-Station-Id=$fU;Called-Station-Id=$tU;Acct-Session-Id=$ci") if (is_method("REGISTER")) { # authenticate the REGISTER requests (uncomment to enable auth) if (!radius_www_authorize("$td")) { www_challenge("$td", "0"); exit; } if ($au!=$tU) { sl_send_reply("403","Forbidden auth ID"); exit; } } ............................... if (from_uri==myself) { if (!radius_proxy_authorize("$fd", "$fU")) { proxy_challenge("$fd", "0"); exit; } -- С уважением Инженер по телекоммуникациям Калала Александр vel: 375291146285 life: 375256819996 skype: klistrod VoIP Network Engineer dCAP, CCNAVoice Kalala Alexander http://callcenters.by/ http://skytel.by/ http://voiplab.by/ http://asterisk-pbx.by/

3 10

New reminder: about private emails
by Daniel-Constantin Mierla 16 Dec '14

16 Dec '14

Given that I noticed still a lot of emails sent directly after a discussion started on public mailing lists (subject with mailing lists prefix, but the sender header is not the mailing list daemon), I would like to remind that, at least in my case, writing emails directly without cc-ing the mailing list is highly not recommended. The rule is also suggested in the mailing lists presentation page: - http://www.kamailio.org/w/mailing-lists/ Unless I asked explicitly for a private email with some specific details, the message will not be noticed in decent time and therefore not replied. I use this email address for many public mailing lists and it is intended only for that usage, I am reacting based on the filters I created, unmatched messages getting the lowest priority. Therefore if you wrote me and expect a response, re-send the message to the appropriate public mailing list. Checking and answering the messages on Kamailio mailing lists are among the top of priorities on my daily activity, so it is high chance you get the response faster when you write there. Note that you can always mask sensitive data (e.g., replace passwords, IP addresses) before sending logs or config file. There are several common sense as well as technical reasons for keeping the discussion on public mailing lists. Here are some along with other suggestions to improve the likeliness of getting an answer: - we are not answering questions on mailing lists to help only one person, but also other people that may have similar issues in the future -- they can find the answers in the archive with a search engine. Also, other people subscribed to the list can learn from conversation or contribute to the discussion, resulting in better outcome - the amount of unexpected messages is very high -- it is practically a zero chance to get to the folder with messages that didn't match any filter (thus your message is not going to be replied) - whenever I find time, the first emails I answer are those coming on mailing lists. They are many there as well, people are traveling or having other personal or business projects, so sometime is good to send a reminder if a question does not get an answer - starting with negative approach or no technical content, like you are going to use something else if you don't get this instantly, or this application is missing what so ever tutorial giving exactly the solution you need, or simply asking for full config of complex requirements, is not helping at all, but actually making people to ignore your messages. Start with what you tried and where you got stuck. Everything you get is for free, have appropriate expectation and behavior. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Email notifications from Github commits
by Daniel-Constantin Mierla 15 Dec '14

15 Dec '14

Hello, those on sr-dev mailing list probably noticed the last commit notification - the email format can be seen at: - http://lists.sip-router.org/pipermail/sr-dev/2014-December/026513.html As discussed in the past, it tries to stay as close as possible to the old notification message, but it has some differences. I published the php script I use for generating this notification as well as synchronizing the git repository mirror on kamailio.org. It is available at: - https://github.com/miconda/gitpushub If people prefer, we can make a clone inside kamailio organization and tailor it to be more specific for kamailio repository, with more people having direct access to update it. On the other hand, any contribution to the script to make it better or more useful is welcome! Eventually it is going to be useful for various people with their other projects. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

Error when configuring RTPProxy-NG.
by Mahmoud Ramadan Ali 15 Dec '14

15 Dec '14

Hi Dears, I'm following this link https://github.com/sipwise/rtpengine to configure rtpproxy-ng with Kamailio BUT i'm reciving the following errors in the Kamailio log file. Dec 14 17:58:34 debian /usr/local/sbin/kamailio[6198]: ERROR: rtpproxy-ng [rtpproxy.c:1425]: rtpp_test(): proxy responded with invalid response Dec 14 17:58:34 debian rtpengine[6160]: Failed to properly parse UDP command line '6188_1 d7:command4:pinge' from 127.0.0.1:36681, using fallback RE Dec 14 17:58:34 debian /usr/local/sbin/kamailio[6188]: ERROR: rtpproxy-ng [rtpproxy.c:1425]: rtpp_test(): proxy responded with invalid response Dec 14 17:58:34 debian rtpengine[6160]: Failed to properly parse UDP command line '6202_1 d7:command4:pinge' from 127.0.0.1:38342, using fallback RE Dec 14 17:58:34 debian /usr/local/sbin/kamailio[6202]: ERROR: rtpproxy-ng [rtpproxy.c:1425]: rtpp_test(): proxy responded with invalid response Dec 14 17:58:34 debian rtpengine[6160]: Failed to properly parse UDP command line '6200_1 d7:command4:pinge' from 127.0.0.1:33265, using fallback RE My configuration as follows: root@debian:/usr/local/etc/kamailio# rtpengine --interface=Kamailio-Internal/192.168.100.1 --interface=Kamailio-External/ 192.168.50.1 --listen-udp=127.0.0.1:12222 --pidfile=/var/run/ngcp-rtpengine-daemon.pid root@debian:/usr/local/etc/kamailio# kamctl fifo nh_enable_rtpp udp: 127.0.0.1:12222 1 root@debian:/usr/local/etc/kamailio# kamctl fifo nh_show_rtpp udp:localhost:12222:: set=0 index:: 0 disabled:: 1 weight:: 1 recheck_ticks:: 0 loadmodule "rtpproxy-ng.so" modparam("rtpproxy-ng", "rtpproxy_sock", "udp:127.0.0.1:12222") modparam("rtpproxy-ng", "rtpproxy_disable_tout", 20) modparam("rtpproxy-ng", "rtpproxy_tout", 2) modparam("rtpproxy-ng", "rtpproxy_retr", 2) modparam("rtpproxy-ng", "extra_id_pv", "$avp(extra_id)") /etc/default/ngcp-rtpengine-daemon RUN_RTPENGINE=yes LISTEN_TCP=25060 LISTEN_UDP=12222 LISTEN_NG=22222 # ADDRESS=... # ADV_ADDRESS=... # ADDRESS_IPV6=... # ADV_ADDRESS_IPV6=... TIMEOUT=60 SILENT_TIMEOUT=3600 PIDFILE=/var/run/ngcp-rtpengine-daemon.pid FORK=yes # TOS=184 TABLE=0 Any ideas about how to solve this please ?! Thanks in advance and Best Regards

3 4

How to get account code
by Juned Khan 15 Dec '14

15 Dec '14

Hi All, I am using Kamailio for signalling purpose. In my current setup I am handling sip registration in Kamailio server and forwarding call to Freeswitch server , and registration and call forwarding to FS server is working. But at Freeswitch side I need accountcode to elstablish a call. I am using this to setup https://wiki.freeswitch.org/wiki/Kamailio_basic_setup_as_proxy_for_FreeSWIT… I am using Kamailio 4.2.1 and Freeswitch 1.4.14 on CentOS 6.5. I have also attached my Kamalio.cfg file. So how do I store and send accountcode variable to Freeswitch? Regards Juned Khan / Network Engineer +91 9974740823/ juned.khan(a)inextrix.com iNextrix Technologies Pvt Ltd. www.inextrix.com <http://htmlsig.com/www.inextrix.com> [image: Facebook] <https://www.facebook.com/junedkhan23> [image: Twitter] <https://twitter.com/juned23> [image: Google Plus] <https://plus.google.com/+JunedKhan> [image: Linkedin] <http://htmlsig.com/in.linkedin.com/in/junedk> This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. Company Name is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.

2 1

Main GIT repository now on Github - https://github.com/kamailio/kamailio
by Daniel-Constantin Mierla 15 Dec '14

15 Dec '14

Hello, the main GIT repository for Kamailio project is now hosted on Github - the web link to it is: * https://github.com/kamailio/kamailio For users (read only access -- ie, you cloned from git.sip-router.org) should be no change, just be sure that DNS has been updated, because git.sip-router.org is pointing now to another server which has a real-time clone of Github repository. To know if DNS was updated on your side, browse to: * http://git.sip-router.org an you must be directed to Gitlist web interface: * http://git.kamailio.org/gitlist/index.php If you end up in an url with gitweb on it, DNS is pointing to the old server. The listed kamailio and sip-router projects are the same (the second is a symlink to the first). Gitweb is also running on the mirror, so the links from the email notifications of old commits are valid: * http://git.sip-router.org/gitweb/ Gitweb can be made the main web interface for the mirror, if people like it more. For now I let Gitlist in order to be easy to detect the DNS update. Once the DNS is updated, pulling/fetching in an existing clone done from git.sip-router.org should just work. For developers, you need to change the remote URL of your local clone to point to Githup repository. Github provides several access methods (git/ssh or https) -- as an example of switching the remote URL to github repository and do the push via https, got you your local clone directory and do: git remote set-url origin https://github.com/kamailio/kamailio.git Check the change with: git remote -v You should see: origin https://github.com/kamailio/kamailio.git (push) origin https://github.com/kamailio/kamailio.git (fetch) When you try to push, it should ask you for your github username and password. For github repository access, see more details at: - https://help.github.com/articles/which-remote-url-should-i-use/ I sent invitations to some of the developers that I found quickly on github, but there are still some of them very active that I didn't spot on github. Send me the github user id to allow you write access. >From now on all commits must be pushed to github! For fetching/pulling in an existing clone, wait for a little more or check the DNS update on your side with the above guidelines - there is already a commit I pushed there, which is no longer on the old repository (which will be decommissioned soon, but still can take a bit for the DNS to propagate, so some of you might end up to it if using git.sip-router.org). New read-only clones can be done from Github as well. Hopefully the migrations is going to be smooth for everyone! Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 0

rtpengine offer does not replace o and c line addresses
by jh＠tutpro.com 15 Dec '14

15 Dec '14

while doing some webrtc tests, i noticed that for some reason rtpengine_offer replace-session-connection replace-origin flags don't have any effect on the ip address (0.0.0.0) at o and c lines of the sdp. the debug is below. what is it that i'm missing? -- juha Dec 15 08:26:29 rautu /usr/bin/sip-proxy[12597]: INFO: ===== rtpengine_offer(ICE=force replace-session-connection replace-origin via-branch=1) Dec 15 08:26:29 rautu rtpengine[10473]: Got valid command from 127.0.0.1:38653: offer - { "sdp": "v=0#015#012o=Mozilla-SIPUA-34.0 24971 0 IN IP4 0.0.0.0#015#012s=SIP Call#015#012t=0 0#015#012a=ice-ufrag:fb2938b0#015#012a=ice-pwd:eb43995297ab91228db0dec8949497ed#015#012a=fingerprint:sha-256 D9:DD:0F:CE:C2:D5:6A:D3:9A:C7:24:00:76:24:EA:66:ED:97:9F:E3:2D:25:23:60:67:7C:54:CF:04:8A:DB:F7#015#012m=audio 9 RTP/SAVPF 109 9 0 8 101#015#012c=IN IP4 0.0.0.0#015#012a=rtpmap:109 opus/48000/2#015#012a=ptime:20#015#012a=rtpmap:9 G722/8000#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:101 telephone-event/8 ... Dec 15 08:26:29 rautu rtpengine[10473]: ... 000#015#012a=fmtp:101 0-15#015#012a=sendonly#015#012a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level#015#012a=setup:actpass#015#012a=rtcp-mux#015#012a=candidate:0 1 UDP 2122187007 192.98.102.30 58681 typ host#015#012a=candidate:2 1 UDP 2122252543 192.168.1.194 42724 typ host#015#012a=candidate:0 2 UDP 2122187006 192.98.102.30 53515 typ host#015#012a=candidate:2 2 UDP 2122252542 192.168.1.194 34867 typ host#015#012", "ICE": "force", "replace": [ "session-connection", "origin" ], "call-id": "dgp00b8p8q45f0vba38o", "via-branch": "z9hG4bK8492226", "rec ... Dec 15 08:26:29 rautu rtpengine[10473]: ... eived-from": [ "IP4", "192.98.102.30" ], "from-tag": "a4dr7vb4on", "command": "offer" } Dec 15 08:26:29 rautu rtpengine[10473]: [dgp00b8p8q45f0vba38o] Creating new call Dec 15 08:26:29 rautu rtpengine[10473]: [dgp00b8p8q45f0vba38o] Opened ports 50110..50111 for media relay Dec 15 08:26:29 rautu rtpengine[10473]: [dgp00b8p8q45f0vba38o] Opened ports 50118..50119 for media relay Dec 15 08:26:29 rautu rtpengine[10473]: [dgp00b8p8q45f0vba38o] Returning to SIP proxy: d3:sdp717:v=0#015#012o=Mozilla-SIPUA-34.0 24971 0 IN IP4 0.0.0.0#015#012s=SIP Call#015#012t=0 0#015#012a=ice-lite#015#012m=audio 50110 RTP/SAVPF 109 9 0 8 101#015#012c=IN IP4 0.0.0.0#015#012a=rtpmap:109 opus/48000/2#015#012a=ptime:20#015#012a=rtpmap:9 G722/8000#015#012a=rtpmap:0 PCMU/8000#015#012a=rtpmap:8 PCMA/8000#015#012a=rtpmap:101 telephone-event/8000#015#012a=fmtp:101 0-15#015#012a=sendonly#015#012a=rtcp:50111#015#012a=rtcp-mux#015#012a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:vSMhw6pr2O+DWrL+7O1chSiCrSZ5YJW4esLlgNv/#015#012a=setup:actpass#015#012a=fingerprint:sha-1 42:C4:38:DC: ... Dec 15 08:26:29 rautu rtpengine[10473]: [dgp00b8p8q45f0vba38o] ... A6:4A:A6:70:49:6A:96:81:BE:9A:17:7D:FE:02:00:2C#015#012a=ice-ufrag:GL0QSUR3#015#012a=ice-pwd:X1irWG0YUiMpcTLgHo9OHgNl1NbT#015#012a=candidate:Wz1BLNSFenkyID4v 1 UDP 2130706431 0.0.0.0 50110 typ host#015#012a=candidate:Wz1BLNSFenkyID4v 2 UDP 2130706430 0.0.0.0 50111 typ host#015#0126:result2:oke

2 1

← Newer
1
...
5
6
7
8
9
10
11
12
13
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 December 2014