sr-users June 2014

sr-users@lists.kamailio.org

86 participants
144 discussions

Replys though onsend_route?
by Jöran Vinzens 03 Jul '14

03 Jul '14

Hi all, is there a possibility to pass reply and failure though onsend_route as well? We try to capture via siptrace the incoming and outgoing packet. So far this is only possible with Requests. I've found this: http://lists.sip-router.org/pipermail/sr-users/2012-May/073224.html Can anybody confirm this is still the behavior? Does anybody have a solution passing reply though onsend_route or any other way to capture the outgoing reply via siptrace? Thanks a lot for your help. BR Jöran Vinzens -- Jöran Vinzens - vinzens[at]sipgate.de <vinzens(a)sipgate.de> sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391 www.sipgate.de - www.sipgate.at - www.sipgate.co.uk

2 3

Making RLS presence work with Blink and Kamailio 4.1.4
by Alex Villacís Lasso 02 Jul '14

02 Jul '14

I am having trouble making all of the supposed features of Blink work with Kamailio 4.1.4. My kamailio.cfg file is attached. Specifically, what I am having trouble is with presence (the way Blink wants to implement it), and MSRP. Ordinary voice calls work correctly. With presence, I have managed to make XCAP storing and retrieval work, in the sense that a document that is being stored with PUT can be later retrieved with GET on the same URL. However, I cannot make Blink use this support in order to actually monitor presence. As far as I understand, when user A subscribes to the presence state of user B, and user B is registered, user B is supposed to receive a notification that user A requests authorization for presence subscription. However, this is not working so far when both A and B use Blink. From what I can see through a packet capture, neither adding a new contact on the Blink window or having existing contacts result in any SUBSCRIBE packets for the contact users being sent to the Kamailio instance. If the subscription is meant to be performed some other way, I am not seeing it being done either. Of course, this results in presence changes not being exchanged between contacts. The only SUBSCRIBE packet I see from Blink is the one for the SIP account used for Blink. With MSRP, I have copied the example from the msrp.so documentation, but I have replaced the authentication shown with a static password, with an actual query using auth_db.so, the very same query used to authenticate other SIP packets. Through the packet capture, when user A tries starting a MSRP chat with user B, an INVITE is sent from user A to Kamailio, which has a special check to NOT send this invite to Asterisk, but rather route it itself, and it gets "correctly" routed to user B. Then user B attempts to start a MSRP session with Kamailio (not user A) without authentication credentials, Kamailio challenges user B for the credentials, and... that's it. User B makes no attempt to repeat the MSRP session with the required credentials, and the communication eventually times out. The presence failure might have something to do with the following exchange I see in the packet capture: GET /xcap-root/pidf-manipulation/users/sip:avillacisIM@pbx.elastix.com/index HTTP/1.1 Accept-Encoding: identity Authorization: Digest username="avillacisIM", realm="pbx.elastix.com", nonce="U6xFz1OsRKNuU11dgljLCgGppv5lK6Eu", uri="/xcap-root/pidf-manipulation/users/sip:avillacisIM@pbx.elastix.com/index", response="3dfdf556c9812f4bebb8b0cc82578ef9", algorithm="MD5" Host: pbx.elastix.com:5060 Connection: close Accept: application/pidf+xml User-Agent: Blink 0.8.2 (Linux) HTTP/1.1 404 Not found Via: SIP/2.0/TCP 192.168.3.2:55567 Server: kamailio (4.1.4 (x86_64/linux)) Content-Length: 0 That is, the Blink client tries to fetch the pidf-manipulation document, and Kamailio answers with a 404. In other cases Blink has responded with a PUT of a minimal document at the required URI (which gets stored to the database), but in this case (pidf-manipulation) this is not done. I am not sure of what is supposed to happen here. This 404 is the same regardless of whether there are other (Blink or otherwise) SIP clients connected. I think this has been asked before, but is there a working implementation of MSRP+presence for Kamailio that works with Blink? Or failing that, a complete kamailio.cfg that has been shown to work with at least one MSRP implementation?

2 5

TCP rest by peer
by Rob Moore 02 Jul '14

02 Jul '14

Hi All, Since we've been using sipPhones as a proxy for registrations and calls to phones over TCP. I've been seeing a couple of these crop up in the logs. /usr/sbin/kamailio[4255]: ERROR: <core> [tcp_read.c:1131]: ERROR: tcp_read_req: error reading /usr/sbin/kamailio[4255]: ERROR: <core> [tcp_read.c:293]: error reading: Connection reset by peer (104) We haven't had any complaints of problems with the phones so if these are not a problem I'd like to know how to clean them up. Any suggestions on cause or solution would be fantastic. Thanks in advance. Rob Kind regards, Robert Moore Telephony System Architect [Description: Aeriandi] m. +44 (0)7766 838 040 t. +44 (0)845 108 0308 [cid:image002.png@01CF8C82.823C49E0]<http://www.retailweektechnologyawards.com/winners-2014> Aeriandi Ltd / Prama House, 267 Banbury Road, Oxford OX2 7HT / +44 (0)845 108 0308 / info(a)aeriandi.com<mailto:info@aeriandi.com> / aeriandi.com<http://www.aeriandi.com/> This transmission is intended solely for the addressee and may be confidential. If you are not the named addressee, or if the message has been addressed to you in error, you must not read, disclose, reproduce, distribute or use this transmission. Please delete the message or contact the sender. Delivery of this message to any person other than the named addressee is not intended in any way to waive confidentiality. Please note that neither Aeriandi Ltd nor the sender accepts any responsibility for any viruses, which may be transmitted, and it is your responsibility to scan attachments (if any).

2 3

msilo possible bug
by Kelvin Chua 02 Jul '14

02 Jul '14

Hi guys, i think i have stumbled on an msilo bug. m_dump() is not working. kamctl fifo get_statistics all | grep mess msilo:dumped_messages = 0 msilo:failed_messages = 0 msilo:stored_messages = 1 so here we can see there is a message to be delivered. i turned on debug mode, then the intended destination of message logs in. then this is what i see on logs DEBUG: msilo [msilo.c:1082]: m_dump(): dumping [1] messages for <sip:XX85X80X74@1X8.1X9.1X7.1X3>!!! DEBUG: msilo [ms_msg_list.c:169]: msg_list_check_msg(): checking msgid=405 DEBUG: msilo [ms_msg_list.c:207]: msg_list_check_msg(): msg already in sent list. DEBUG: msilo [msilo.c:1089]: m_dump(): message[0] mid=405 already sent. using ngrep, no message was ever seen on the wire. then, kamctl fifo get_statistics all | grep mess msilo:dumped_messages = 0 msilo:failed_messages = 0 msilo:stored_messages = 1 still the same. anybody experienced this? Kelvin Chua

2 2

installation siremis error
by Hossein Aghaie 01 Jul '14

01 Jul '14

hi after install kamailio 4.1.0 on ubuntu server,I try to install siremis-4.1.0 of this Doc : http://kb.asipto.com/siremis:install41x:main but to end setup,show this error : http://paste.fedoraproject.org/114029/ how to solved this problem? tnx

3 5

Kamailio Development Workshop, July 9-10, 2014, Paris, France
by Daniel-Constantin Mierla 01 Jul '14

01 Jul '14

Hello, I want to announce the next Kamailio Development Workshop, to take place in Paris, France, during July 9-10, 2014. This event is the next in its series targeting to show the internals of Kamailio and enable more people to become developers as well as let users of Kamailio to get more knowledge about the design of the application which can have relevant impact in operating deployment. Be aware that it is not a workshop about Kamailio installation and administration. Its content is about writing C code to extend Kamailio. More details can be found at: - http://www.kamailio.org/w/2014/06/kamailio-development-workshop-july-9-10-2… Similar to the past events, we are considering to have a social networking event in the evening of July 9 (most probably a dinner meetup at a nice place in Paris), which is open for everyone, each participant taking care of own expenses. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

1 2

how to compile module db_oracle on Centos 6.5
by Konstantin Khatskevich 01 Jul '14

01 Jul '14

Hello! 5. Installation Because it dependes on an external library, the oracle module is not compiled and installed by default. You can use one of the next options. * - edit the "Makefile" and remove "db_oracle" from "excluded_modules" list. Then follow the standard procedure to install Kamailio: "make all; make install". * - from command line use: 'make all include_modules="db_oracle"; make install include_modules="db_oracle"'. But "db_oracle: requires non-free Oracle client SDK" (http://lists.sip-router.org/pipermail/sr-dev/2013-October/021803.html) What can I do? -- Best regards, Konstantin Khatskevich

2 2

Child Processes Stopped kamailio 4.0.6
by Jonathan Hunter 30 Jun '14

30 Jun '14

Hi Guys, Sorry thought I better raise this in new stream to avoid confusion. We have another crash today, not sure if the below is of much use without debug? Thanks Jon Jun 26 09:38:09 pbx /usr/sbin/kamailio[18529]: ALERT: <core> [main.c:788]: handle_sigs(): child process 18532 exited by a signal 11Jun 26 09:38:09 pbx /usr/sbin/kamailio[18529]: ALERT: <core> [main.c:791]: handle_sigs(): core was not generatedJun 26 09:38:09 pbx /usr/sbin/kamailio[18529]: INFO: <core> [main.c:803]: handle_sigs(): INFO: terminating due to SIGCHLDJun 26 09:38:09 pbx /usr/sbin/kamailio[18531]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:09 pbx9 /usr/sbin/kamailio[18529]: ALERT: <core> [main.c:788]: handle_sigs(): child process 18532 exited by a signal 11Jun 26 09:38:09 pbx9 /usr/sbin/kamailio[18529]: ALERT: <core> [main.c:791]: handle_sigs(): core was not generatedJun 26 09:38:09 pbx9 /usr/sbin/kamailio[18529]: INFO: <core> [main.c:803]: handle_sigs(): INFO: terminating due to SIGCHLDJun 26 09:38:09 pbx9 /usr/sbin/kamailio[18531]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:09 pbx9 /usr/sbin/kamailio[18533]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:09 pbx9 /usr/sbin/kamailio[18537]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:09 pbx9 /usr/sbin/kamailio[18534]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:09 pbx9 /usr/sbin/kamailio[18535]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:09 pbx9 /usr/sbin/kamailio[18538]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:09 pbx9 /usr/sbin/kamailio[18530]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:09 pbx9 /usr/sbin/kamailio[18539]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:09 pbx9 /usr/sbin/kamailio[18536]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:09 pbx9 kamailio[2076]: ERROR: <script>: Failed Reg Block Traffic from 194.72.34.18Jun 26 09:38:09 pbx kamailio[2075]: ERROR: <script>: Failed Reg Block Traffic from 194.72.34.18Jun 26 09:38:09 pbx kamailio[2074]: ERROR: <script>: Routing Call To Asterisk serverJun 26 09:38:09 pbx kamailio[2074]: INFO: <script>: Routing Call to Dispatcher group 1 -Asterisk Media ServersJun 26 09:38:10 pbx kamailio[2072]: ALERT: <core> [main.c:788]: handle_sigs(): child process 2075 exited by a signal 11Jun 26 09:38:10 pbx kamailio[2072]: ALERT: <core> [main.c:791]: handle_sigs(): core was generatedJun 26 09:38:10 pbx kamailio[2072]: INFO: <core> [main.c:803]: handle_sigs(): INFO: terminating due to SIGCHLDJun 26 09:38:10 pbx kamailio[2074]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:10 pbx kamailio[2078]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:10 pbx kamailio[2076]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:10 pbx kamailio[2077]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:10 pbx kamailio[2079]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:10 pbx kamailio[2073]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:10 pbx kamailio[2080]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:10 pbx kamailio[2081]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:10 pbx kamailio[2082]: INFO: <core> [main.c:854]: sig_usr(): INFO: signal 15 receivedJun 26 09:38:10 pbx kamailio[2072]: ERROR: ctl [ctl.c:379]: mod_destroy(): ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: No such file or directory (2)Jun 26 09:43:33 pbx kamailio: INFO: <core> [tcp_main.c:4846]: init_tcp(): init_tcp: using epoll_lt as the io watch method (auto detected)

2 2

How to extract information from location table
by aawaise 30 Jun '14

30 Jun '14

I want to know is there any indirect method to extract information from location table that is kept by Usrloc module ?? I want to know about the username and domain name of users from Location Table on arrival of INVITE packet. How can it be done ? -- View this message in context: http://sip-router.1086192.n5.nabble.com/How-to-extract-information-from-loc… Sent from the Users mailing list archive at Nabble.com.

2 1

route [Location] Documentation
by aawaise 30 Jun '14

30 Jun '14

I want to know that how route [Location] works when an INVITE packet approaches kamailio server. Basically route [Location] gathers information whether callee is a valid user or not. Secondly if it is online or not. I want to understand this whole procedure. Any help will be appreciated. Thanks. -- View this message in context: http://sip-router.1086192.n5.nabble.com/route-Location-Documentation-tp1286… Sent from the Users mailing list archive at Nabble.com.

2 1

← Newer
1
2
3
4
5
6
7
...
15
Older →

Jump to page:

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 2014