sr-users August 2016

sr-users@lists.kamailio.org

80 participants
105 discussions

by Jay Li

Dear All, I just have a basic SIP question on re-invite. I wonder if "ACK" is required in a re-invite scenario, like re-invite -> 200 OK -> ACK. What I've seen is for some reason, my PSTN doesn't send a "ACK" back to me after my 200 OK response to their re-invite. I don't know if not sending an ACK in a re-invite is an allowed behavior. Thanks. Regards,Jay

8 years, 1 month

kamailio TLS mod_register failed

by wanmon wanmon

8 years, 1 month

Via in locally generated PUBLISH (using different presence server address)

by Asgaroth

Hi All, I have a configuration where we run a multi-homed proxy/loadbalancer and a seperate internal presence server. We then use pua/pua-dialoginfo on the proxies to publish dialog state to the internal presence server. The proxies listen on udp:external_ip:5062 and udp:internal_ip1:5060. The presence server listens on udp:internal_ip2:5060 on a seperate server. The problem I am coming accross is that when kamailio generates a PUBLISH message for some dialogs it creates the via header with address external:ip:5062, however the pua module is configured to send to the presence server address on internal_ip2:5060. I have a route which forces the sending socket ($fs) to be udp:internal_ip1:5060. What happens then is that the presence server tries to send the 200 reply to the PUBLISH message back to internal_ip1:5062 (when it should be internal_ip1:5060), I'm thinking this is because the Via header has host as external_ip:5062. Is it possible, from event-route[tm:local-request] to rewrite the via header so that it reflects internal_ip1:5060 instead of external_ip:5062? I did try the following snippet from event-route[tm:local-request], but I got module parse errors on the Via header: if (is_method("PUBLISH")) { subst_hf("Via", "/ 1\.2\.3\.[0-9]+:5062;/ $sel(cfg_get.socket.internal_ip);/", "f"); } [7370]: ERROR: <core> [parser/parse_via.c:2607]: parse_via(): ERROR:parse_via on <1> state 5 (default) [7370]: ERROR: <core> [parser/parse_via.c:2708]: parse_via(): ERROR: parse_via on: <SIP/2.0/UDP external_ip:5062;branch=z9hG4bK96eb.0f014ae4000000000000000000000000.0#015#012 internal_ip1; [7370]: ERROR: <core> [parser/parse_via.c:2712]: parse_via(): ERROR: parse_via parse error, parsed so far:<SIP/2.0/UDP external_ip:5062;branch=z9hG4bK96eb.0f014ae4000000000000000000000000.0#015#012 > [7370]: ERROR: <core> [parser/msg_parser.c:125]: get_hdr_field(): ERROR: get_hdr_field: bad via [7370]: INFO: <core> [parser/msg_parser.c:338]: parse_headers(): ERROR: bad header field [Via: SIP/2.0/UDP 1] [7370]: ERROR: <core> [parser/msg_parser.c:690]: parse_msg(): ERROR: parse_msg: message=<PUBLISH sip:user@domain;transport=UDP SIP/2.0#015#012Via: SIP/2.0/UDP external_ip:5062;branch=z9hG4bK96eb.0f014ae4000000000000000000000000.0#015#012 internal_ip1;To: <sip:user@domain;transport=UDP>#015#012From: <sip:user@domain;transport=UDP>;tag=3e8fdaca277026bf3e6d75c5e5313096-f162#015#012CSeq: 10 PUBLISH#015#012Call-ID: 5634294b786134b3-7370@external_ip#015#012Content-Length: 692#015#012User-Agent: kamailio (bfievklb04)#015#012Max-Forwards: 70#015#012Event: dialog#015#012Expires: 10901#015#012Content-Type: application/dialog-info+xml#015#012#015#012<?xml version="1.0"?>#012<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" entity="sip:user@domain;transport=UDP">#012 <dialog id="mvqXXaAr24DHdfsffYKZeA.." call-id="mvqXXaAr24DHdfsffYKZeA.." direction="initiator">#012 <state>Trying</state>#012 <remote>#012 <identity>sip:1234567@domain;transport=UDP</identity>#012 <target uri="sip:1234567@domain;transport=UDP"/>#012 </remote>#012 <local>#012 <identity>sip:user@domain;transport=UDP</identity>#012 <target uri="sip:user@domain;transport=UDP"/>#012 </local>#012 </dialog>#012</dialog-info>#012> [7370]: ERROR: <core> [msg_translator.c:3057]: build_sip_msg_from_buf(): parsing failed [7370]: ERROR: tm [uac.c:163]: uac_refresh_hdr_shortcuts(): failed to parse msg buffer [7370]: ERROR: tm [uac.c:487]: t_uac_prepare(): failed to refresh header shortcuts [7370]: ERROR: pua [send_publish.c:700]: send_publish(): in t_request tm module function [7370]: ERROR: pua_dialoginfo [dialog_publish.c:358]: dialog_publish(): while sending publish To me, it looks like the replace section of the subst_hf sub expression is being appended to the end of the via header instead of replacing the address section found. I have sanitized the above output to not show internal details, but if you need it, I can send it on to you privately. Am I going about this issue in the correct way, and, if so, where am I going wrong with the subst_hf snippet above? Kamailio version is 4.3.6. Any pointers/tips/trciks are greatly appreciated. Thanks

8 years, 1 month

Installation question on ubuntu xenial / undefined symbol: EVP_sha1

by Christian Lox

Hi. I am trying to install kamailio 4.4.2 on ubuntu xenial, for use with kazoo. Using source and compiling just went fine, but /usr/local/sbin/kamailio -c throws ERROR: <core> [sr_module.c:582]: load_module(): could not open module </usr/local/lib64/kamailio/modules/outbound.so>: /usr/local/lib64/kamailio/modules/outbound.so: undefined symbol: EVP_sha1 any hint appreciated! Thanks, Christian

8 years, 1 month

Re: [SR-Users] undefined symbol: EVP_sha1 when using outbound module

by Christian Lox

Hi. Same problem here; undefined symbol : EVP_sha1 in outbound.so pkg-config was available when compiled from source. Tried installing several dev packages and so on but always the same error. How do i link it against libssl/libcrypto? Thanks, Christian

8 years, 1 month

access header variables in failure route

by jaflong jaflong

On an 302 message caught in failure_route Is it possible to get to access $hdr(xxx) of the 302. When I do this $hdr(xxx) it is null.

8 years, 1 month

Struggling at 1000 Concurrent Calls

by Jack Stevens

Hi Guys, I have built an SBC using kamailio with the dispatcher module and rtpengine and when I run a sip test I find it struggles to go past 1000 calls at 20cps would really like some help on how to resolve this. As I am very new to this I am stuggeling to work out where to start from. I have found when running this sort of load the debian box drops pings any ideas Kind Regards -- CONFIDENTIAL EMAIL FROM NETCALL TELECOM LIMITED This email, and any attachments, is intended only for the above addressee. It may contain private and/or confidential information. If you have received this email in error you are on notice of its status, please immediately notify the sender by return email then delete this message and any attachments. If you are not the addressee, except to notify the sender, you must not use, disclose, copy or distribute this email and/or its attachments. Netcall Telecom accepts no responsibility for any changes made to this message after it has been sent by the original author. Opinions or views expressed in this email may be those of the individual sender and not Netcall Telecom. Nothing in this email shall bind Netcall Telecom in any contract or obligation Netcall Telecom Ltd Registered in England 2831215. Registered Office : 3rd Floor, Hamilton House, 111 Marlowes, Hemel Hempstead, Herts, HP1 1BB

8 years, 1 month

CDP Error S-CSCF Kamailio

by Rodrigo Moreira

Hello Carsten Bock, I got to advance in the event REGISTER, but now face the following problem: When I type the command: */etc/init.d/kamailio restart* Aug 10 20:40:52 scscf /usr/sbin/kamailio[2639]: INFO: cdp [diameter_peer.c:428]: diameter_peer_destroy(): destroy_diameter_peer(): Terminating all children... Aug 10 20:40:52 scscf /usr/sbin/kamailio[2639]: INFO: cdp [diameter_peer.c:447]: diameter_peer_destroy(): destroy_diameter_peer(): All processes terminated....aning up. Aug 10 20:40:52 scscf /usr/sbin/kamailio[2639]: INFO: cdp [worker.c:140]: worker_destroy(): Unlocking workers waiting on empty queue... Aug 10 20:40:52 scscf /usr/sbin/kamailio[2639]: INFO: cdp [worker.c:143]: worker_destroy(): Unlocking workers waiting on full queue... Aug 10 20:40:52 scscf /usr/sbin/kamailio[2639]: CRITICAL: cdp [diameter_peer.c:487]: diameter_peer_destroy(): destroy_diameter_peer(): Bye Bye from C Diameter Peer test Aug 10 20:40:52 scscf /usr/sbin/kamailio[2639]: INFO: cdp [mod.c:244]: cdp_exit(): ... CDiameterPeer child stoped Aug 10 20:40:52 scscf /usr/sbin/kamailio[2639]: INFO: <core> [sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Aug 10 20:40:52 scscf systemd[1]: kamailio.service: control process exited, code=exited status=255 Aug 10 20:40:52 scscf systemd[1]: Failed to start Kamailio (OpenSER) - the Open Source SIP Server. Aug 10 20:40:52 scscf systemd[1]: Unit kamailio.service entered failed state. I can not start the Kamailio, I used the examples codes available in the repository (GIT). You suggest something I may be doing wrong? Can you help me? I attached my config files. Thank you very much. Regards. -- Rodrigo M. (37) 9132-4539 (34) 9889-3069 rodrigo.moreira2007

8 years, 1 month

Kamailio 4.4 Dispatcher on Debian 8 with MongoDB

by Jonathan Hunter

Hi Guys, I am integrating kamailio with MongoDB, and it works well with subscriber/location tables. However when using the dispatcher module I am getting the following error even though the IP Im trying to get to is routeable; /usr/local/kamailio-4.4/sbin/kamailio[2998]: ERROR: dispatcher [dispatch.c:1403]: ds_get_index(): destination set [1] not foundAug 11 17:01:47 ip-172-31-43-8 /usr/local/kamailio-4.4/sbin/kamailio[2998]: ERROR: dispatcher [dispatch.c:1832]: ds_select_dst_limit(): destination set [1] not found I created the table as below; db.getCollection("version").insert({table_name: "dispatcher", table_version: NumberInt(4) }) And the entry Im routing to is; db.dispatcher.find().pretty(){ "_id" : ObjectId("57acadc81e7e803fa565bce3"), "setid" : "1", "destination" : "sip:1.1.1.1:5080;transport=tcp", "flags" : "0", "priority" : "100", "attrs" : "name=labfS", "description" : "FreeSWITCH1"} Is there something I am missing ? Has anyone else got it working with Mongo? Thanks Jon

8 years, 1 month

Kamailio CDP Error - SCSCF

by Rodrigo Moreira

Hello, I can not make the S-CSCF module work, is giving CDP error. CRITICAL: cdp [diameter_peer.c: 485]: diameter_peer_destroy (): destroy_diameter_peer (): Bye Bye from C Diameter Peer test I am using the examples available in the repository still occur errors that prevent Kamailio to boot. Can someone help me? Someone has the kamailio.cfg, scscf.cfg and scscf.xml files to share? Regards. -- Rodrigo M. (37) 9132-4539 (34) 9889-3069 rodrigo.moreira2007

8 years, 1 month

← Newer
1
...
4
5
6
7
8
9
10
11
Older →

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 August 2016