sr-users November 2014

sr-users@lists.kamailio.org

91 participants
128 discussions

by Siddhardha Garige

Hello all, Just wondering if anyone know any tutorial on setting up HA+DRBD solution for kamailio. Especially creating partitions, DRBD devices and mount points. Thanks in advance, -Sid "May the light be with you." ______________________________________________ Siddhardha Garige www.luminepixels.com

9 years, 4 months

Kamailio: MI Command: 'trusted_dump' and 'trusted_reload'

by José Luis Millán

Hi, I'm using 'allow_trusted()' from Permissions module without a problem in a Kamailio 4.0 routing logic. It does just work, but the MI command 'trusted_dump' tells me that the module is not in use: ''' server:/home/jmillan# kamctl fifo trusted_dump 500 Trusted-module not in use ''' Doing a 'trusted_reload' does neither make any query to database to retrieve the data. Other MI commands of same module do work correctly. ie: 'address_reload' or 'address_dump' Note: I have tested in a Kamailio 1.5 and the result is the same. Regards. -- José Luis Millán

9 years, 7 months

Recommendation for toggling MSILO m_store auto-notification reply on/off

by Anthony Messina

Using Kamailio 4.2-dev and MSILO, is it possible to "toggle" the auto- notification reply MESSAGE using something similar to the following where "$var(msilo_reply)" is emtpy at startup (or are there suggestions for a better method): modparam("msilo", "from_address", "$var(msilo_reply)") ... if(CONDITION WHERE I WANT THE AUTO-REPLY RETURNS POSITIVE) { $var(msilo_reply)="$rU(a)example.net"; } m_store($rU) ... My use case is that I would like the auto-notification reply to occur in some instances, but not others. I also do not want to create a loop where the auto-notification replies are also stored. I was originally using a simple test: if(src_ip!=myself), but I have begun to use the IMC module as well as the EXEC module and these MESSAGEs appear to originate from "myself." Looking at the MSILO documentation I see there is "extra_hdrs(string)," but this appears to be designed to add headers to dumped MESSAGEs. I was hoping there would be a way to add a custom header to the auto-notification, on which I could filter/drop generated replies earlier in the route, but it doesn't appear that this exists. My preference for the best-case scenario would be to control the generation of the auto-notification reply in the first place rather than having to add a control to detect the reply and drop it. Thanks in advance for any recommendations. -- Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery 8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E

9 years, 7 months

File transferring issue

by Wingsravi R

Dear Kamailio'ns, I am working on kamailio Server (V 4.0) installed on Ubuntu 12.04 system. Currently i am trying file transfer feature using IMSDroid SIP clients. file transferring is fine between two IMSDroid clients but at the receiving end (file recipient) i cont see the sender identity/ sender name. it is just displaying as 'null' (Screen shot is attached). But the full file is transferring to destination address without any problem. I have configured MSRP module related script in my kamailio configuration file (find the attachment). but i guess it is not invoking anyway when file transferring and the file transferring is negotiating client-to-client basis. And also find Sip capture of file transfer (ngrep based) for better understanding. What could be the problem? Why at the file recipient side it is not displaying sender's identity (instead it is 'null')? how can i resolve this issue? Anyone please help me in resolving this issue. Any help will greatly appreciate. Regards, Ravi.

9 years, 8 months

why do not support tcp:eth1:5062，only support eht1:5062

by 张顺通

why do not support tcp:eth1:5062，only support eht1:5062? I need to bind on eth1 only tcp.

9 years, 9 months

gruu within dialog

by samuel

Hi all, I'm having some issues treating requests within dialogs with gruu enabled with kamailio 4.1.2. I've got the "standard" configuration of WITHIN route with the adition of the next lines: if(is_gruu()){ route(LOCATION); }; before the the RELAY route call in the loose_route section. The "problem" is that the ACK with a pub-gruu on the Req-URI is not properly lookup. In the logs I can see the following statements: 2(4232) DEBUG: registrar [lookup.c:123]: lookup(): looking up pub gruu [urn:uuid:d63b1c4f-d7dc-4f4e-87f1-948123266dc0] 2(4232) DEBUG: registrar [lookup.c:158]: lookup(): 'sam(a)A.B.C.D' Not found in usrloc Where A.B.C.D is the local IP of the UA. Looking at the code, this last line looks like is looking for the "standard" URI (username@domain) instead of using the pub gruu. Am I right with this assumption or am I missing something from the code? As far as I could look, it looks like there's an exit -1 statement in the line 158 of lookup.c which disables the following gruu treatment. Since the username with IP is not registered, this ACK is lost and the sesion is not stablished (lost ACK). Can anyone provide some hints why is this failing? Thanks a lot in advance! Samuel.

9 years, 9 months

Fwd: Need a support for Siremis and kamailio server

by Gaurav Rai

Hi I am using a siremis and *kamailio * hosted server with lylix.net and they give a link for getting a support about Siremis. I need a support to how to make OUT call on PSTN with registered subscriber on Softphone. Currently we have registered user on subscriber table with their location and can make a PEER to PEER audio call and text messaging also. To make OUT call on PSTN we had create a LCR gateway and LCR rule with Prefix but still can not make a OUT call getting a error 404 can u please help me out to make a PSTN call Waiting for your reply Thanks Gaurav Rai +919716238804

9 years, 10 months

presence - Error deleting subscription

by Jan Gaida

Hello, We are upgrading our servers to Kamailio 4.2 and we see a lot of error messages "Failed to delete subscription from memory". Scenario: This happens every time there is a Notify Timeout (408) and Kamailio tries to delete the subscription. Consequences: I don't know whether the delete fails because the entry did never exist, was already deleted or because the comparison (to_tag, callid or from_tag) is incorrect. It would be nice to at least have some details in the log message. I have not noticed any consequences to general functionality. I suspect the commit (74d73953327ad7702922b27ba37c71e3283659c3) to be responsible for this error because it introduced some extra checks on deletion. Does this happen to anybody else? What may be configured incorrectly on our system? Kind regards *Jan **Gaida* Ingeniero Desarrollo Software C/ Marconi 3 (PTM) 28760 Tres Cantos Spain jan.gaida(a)grupoamper.com | www.grupoamper.com -- This message and any attachments are intended only for the use of the individual to whom they are addressed and it may contain information that is privileged or confidential. If you have received this communication by mistake, please notify us immediately by e-mail or telephone.The storage, recording, use or disclosure of this e-mail and its attachments by anyone other than the intended recipient is strictly prohibited. This message has been verified using antivirus software; however, the sender is not responsible for any damage to hardware or software resulting from the presence of any virus. Este mensaje y cualquier anexo son exclusivamente para la persona a quien van dirigidos y pueden contener información privilegiada o confidencial. Si usted ha recibido esta comunicación por error, le agradecemos notificarlo de inmediato por esta misma vía o por teléfono. Está prohibida su retención, grabación, utilización o divulgación con cualquier propósito. Este mensaje ha sido verificado con software antivirus; sin embargo, el remitente no se hace responsable en caso de que en éste o en los archivos adjuntos haya presencia de algún virus que pueda generar daños en los equipos o programas del destinatario.

9 years, 10 months

RFC: infrastructure upgrade - git, tracker, ...

by Daniel-Constantin Mierla

Hello, as most of you know, we have a rather distributed infrastructure, with servers provided from different companies or persons. We came to the time when one of the servers is too old and considered to be decommisioned, so we have to decide how to move on. It is about sip-router.org, who was offered/sponsored by courtesy of Jan Janak. From project point of view, the server hosts: - git repository - bug tracker - website and wiki under domain sip-router.org Given that no matter what we like, there is work to do, I am looking to see what are the best options out there for everyone involved in the project. The sip-router.or wbesite and wiki, which are not really updated anyhow, will be relocated as virtual host in kamailio.org server and made static for historic purposes. For git and tracker, I thought of two variants: 1) move to use an external hosting service - the first candidate and perhaps the only to be considered is GitHub, we have there already a real time mirror of git repository. Then we should get a read only mirror to kamailio.org. If the tracker on github is good enough for everyone, then we will use it. I could see quickly that lot of kamailio developers already have an account on github. 2) get a new server and relocate those components there. It will need to be configured from scratch and the components eventually updated to use latest versions. In case of tracker, we have eventually to re-evaluate if flyspray worth keeping, as we had several discussions, due to the fact that the project doesn't seem to be very active. My personal preference at this moment is 1), given that offloads administration works from project. For 2) we will need someone to commit to a sysadmin job for long time. As probably you noticed lately, serious security vulnerabilities can appear and someone needs to take care of proper maintenance of the server. I don't want to get all services on kamailio.org, as it has other critical components (mailing lists, releases, website, ...) and messing it or overloading doesn't make sense. There is no real pressure to come to a decision, we can still rely on the server for a while, but I would rather not postpone it for long. While users are encouraged to give their opinion, I feel that existing developers should have the main role in decision, being something that impacts them directly. Your preference? Any other opinions? Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Nov 24-27, Berlin - http://www.asipto.com

9 years, 11 months

Kamailio Crash when modifying username of Request Uri

by Timo Klecker

Hi all! Our Kamailio (3.1.4) crashed when modifying the username-Part of a Request URI using: $rU = $(rU{s.strip,6}); Initial Request URI: /sbin/kamailio[40658]: NOTICE: <script>: [ INVITE ] Got new Packet to sip:123456:pass@sip.custom.com The config-script now removed the first 6 chars from the username part and would replace them in one of the following lines, but Kamailio had problems here: /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40658]: NOTICE: <script>: Strip from Head: Request Username: <null> // $rU /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40658]: ERROR: <core> [action.c:801]: ERROR: do_action: bad uri <sip::passsip.custom.com>, dropping packet Is there maybe a error when modifying a uri with password this way? Do we have to change this? Ultimately Kamailio crashed: /sbin/kamailio[40658]: ERROR: <core> [action.c:1513]: run action error at: :0 /sbin/kamailio[40658]: ERROR: pv [pv_core.c:1761]: do action failed /sbin/kamailio[40658]: ERROR: <core> [lvalue.c:358]: setting pvar failed /sbin/kamailio[40658]: ERROR: <core> [lvalue.c:411]: assignment failed at pos: (319,10-319,34) /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI Like 5000 lines more of /sbin/kamailio[40658]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI Due to rerouting internal and trying to remove more parts of the request Uri using $rU = $(rU{s.strip,6}); Which then concluded to the following: /sbin/kamailio[40656]: ALERT: <core> [main.c:741]: child process 40660 exited by a signal 11 /sbin/kamailio[40656]: ALERT: <core> [main.c:744]: core was generated /sbin/kamailio[40656]: INFO: <core> [main.c:756]: INFO: terminating due to SIGCHLD /sbin/kamailio[40659]: ERROR: pv [pv_core.c:251]: failed to parse the R-URI /sbin/kamailio[40682]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40677]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40676]: INFO: <core> [main.c:807]: INFO: signal 15 received /sbin/kamailio[40678]: INFO: <core> [main.c:807]: INFO: signal 15 received [...] I will try to recreate this using the new version (4.1.6) on monday. Kind regards Timo Klecker

9 years, 11 months

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 November 2014