sr-users May 2019

sr-users@lists.kamailio.org

84 participants
97 discussions

by Mary Honey

Hello everyone, I install and setup an IMS Network by kamailio-5.2.2 . I have p-cscf, i-cscf and s-cscf in three different systems . my Hss is Fokus. Registration and call between subscribers of network work successfully . now I want to define IP Trunk in my network which can pass external calls through my IMS network. I don't know how to define IP Trunk and changes in which element(pcscf, icscf or scscf) should be done.

5 years, 6 months

Rewrite contact header

by R, Rajkumar (Raj)

Hello, We are using alias routing from NATHelper module and I've a case where the alias part 'alias=ip~port~transport' needs to be removed from the contact header in 2xx message. There's contact header reference "$ct" pseudo variable but it is read only. Is there any approach available to achieve this as I haven't found anything in the forum archive search so far. thanks, raj

5 years, 6 months

Unable to CDRs on "Busy Here 486" from remote side and save start and end time on successful call in table

by Shahid Mehmood

Hello, i want to save the status each call into the database. but failed to 1. record CDRs for "Busy Here 486/ service unavailable 503 " from remote side in database. 2. on successful call unable to record total time of call in database. Version of Kamailio Is *version: kamailio 4.4.7 (x86_64/linux) 35d8abflags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RESADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MBpoll method support: poll, epoll_lt, epoll_et, sigio_rt, select.id: 35d8ab* *Also Attached Config File* *Thanks*

5 years, 6 months

kamailio Early IMS security

by eyas barhouk

hello community Does kamailio support Early IMS security authentication schema to be able to integrate with Huawei HSS ?? and if it's does how to configure it? B.R Eyas

5 years, 6 months

Plans for next major release - v5.3.0

by Daniel-Constantin Mierla

Hello, a while ago, during the last IRC devel meeting, it was proposed to either do the next major release (5.3.0) before the usual summer holidays or leave it for autumn. Given that time is approaching, we have to decide. If it is going to happen before the summer holidays, probably we should freeze the development in 2-3 weeks, then do 3-4 weeks of testing and release during the first part of July. It would be a shorter development cycle, so I do not expect much needs for testing. Only a few new modules and plenty of work to consolidate and enhance the existing code. Any preference for one of the two options? Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

5 years, 6 months

Kamailio usrloc mode 3 using mongodb

by José Seabra

Hello there, I'm testing usrloc module with mongodb and i have a couple of questions to do. What i would like to know/have confirmation is if the fields that are specified in the following link https://kamailio.org/docs/db-tables/kamailio-db-5.2.x.html#gen-db-location-… can be used to create indexes in mongodb? I'm noticing that when a register is updated/deleted or expires kamailio prints the following INFO logs: *db_mongodb [mongodb_dbase.c:526]: db_mongodb_get_columns(): unhandled data type column (methods) type id (10), use DB1_STRING as default* *db_mongodb [mongodb_dbase.c:526]: db_mongodb_get_columns(): unhandled data type column (instance) type id (10), use DB1_STRING as default* These fields (*methods and **instance*) are stored in mongodb document with a null string, e.g: *{* * "_id" : ObjectId("5cdc775a6472740055289a11"),* * "username" : "x1000",* * "contact" : "sip:x1000@192.168.1.1:5674;transport=UDP",* * "expires" : ISODate("2019-05-15T20:33:26Z"),* * "q" : -1,* * "callid" : "sipp-ci2-edge-sip-proxy1-20190515203220-1-21(a)172.31.2.61 <sipp-ci2-edge-sip-proxy1-20190515203220-1-21(a)172.31.2.61>",* * "cseq" : 2,* * "flags" : 0,* * "cflags" : 0,* * "user_agent" : "sipp",* * "received" : "sip:191.30.10.23:8888 <http://191.30.10.23:8888>",* * "path" : "<sip:172.31.2.61:5060;received=sip:191.30.10.23:8888;lr>",* * "socket" : "udp:172.31.2.11:5060 <http://172.31.2.11:5060>",* * "methods" : null,* * "last_modified" : ISODate("2019-05-15T20:32:26Z"),* * "ruid" : "uloc-15-5cdc7756-55-1",* * "instance" : null,* * "reg_id" : 0,* * "server_id" : 21,* * "connection_id" : -1,* * "keepalive" : 0,* * "partition" : 0* *}* Should i be concerned about that log msg? how can i avoid it? Thanks Regards -- Cumprimentos José Seabra

5 years, 6 months

BYE relays Digest and others in Proxy-Authorization header

by Sergiu Pojoga

Hi ppl, Noticed BYE requests relayed from caller to callee have the *Proxy-Authorization* header including *Digest*, *nonce* and *response*. Is that by SIP definition or am I doing something wrong? My concern is the callee gets to see caller's authentication credentials. Thanks.

5 years, 6 months

Centos7 Packages

by Matt Lamer

I am trying to install the kam server on centos7. When running the install I get the following: Install 5 Packages (+2 Dependent packages) Total size: 14 M Total download size: 14 M Installed size: 63 M Downloading packages: Delta RPMs disabled because /usr/bin/applydeltarpm not installed. kamailio-debuginfo-5.2.2-7.el7 FAILED http://download.opensuse.org/repositories/home%3A/kamailio%3A/v5.2.x-rpms/C…: [Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable Anyone else having this issue?

5 years, 6 months

"If you're struggling with your Tele callers to improve sales? you're not alone.

by Prakash

http://www.doocti.com +919790776655 Doocti Next Generation CTI for Smarter Sales Teams http://www.doocti.com Dear Customer, Greeting from Tevatel. Hope this mail finds you well. We are happy to announce the launch of our new product Doocti - Call center connector for crm What is Doocti? Doocti is a Computer telephony integration platform that can integrate your communication devices with your Helpdesk, CRM, and Other Key Tools. Increase agent productivity, improve customer experience and enable personalized service through deep customer insights at the point of interaction. Features of Doocti Single click Dial On-Screen Customer Profile Build on the Customer Profile Efficient Call Disposition Auto Dial Sticky Agent Feedback from the clients Reduce call time by 10-20 seconds per call Instantly retrieves and screen-pops customer related information Provides a better and more immediate response to the customers Offers a more personalized experience to the caller Dials out automatically and faster with a single mouse click Handles higher call volumes Increases first call resolution Intergrated with Currently we have associated with more than 20 brands. Curious to see what's under the hood? Enjoy a detailed look at the Doocti experience in a demo guided by a member of our team. Get a meeting on the calendar today. mailto:prakash.n@tevatel.com?subject=Need More Information about Doocti Request for a Demo [ mailto:prakash.n@tevatel.com?subject=Need More Information about Doocti ] Communications Simplified Contact Us: +919790776655 | prakash.n(a)tevatel.com No:76, Swamibakthan Street, Nammalwarpet, Chennai - 600012. www.tevatel.com | www.doocti.com http://viewstripo.email/?utm_source=templates&utm_medium=email&utm_campaign… ---------------------------------------------------------------------- This email was sent by prakash.n(a)tevatel.com to sr-users(a)lists.sip-router.org Not interested?Unsubscribe - https://tihk.maillist-manage.com/ua/optout?od=27218d28c96aa859ed0ac1287be0e… Update profile - https://tihk.maillist-manage.com/ua/upc?upd=164d3589027540e5&r=164d35890275… Asterfone technologies pvt ltd | Swamibakthan St, Thiruvalluvar Nagar, Nammalwarpet, Ayanavaram, Chennai, Tamil Nadu 600010 Our Privacy Policy [ ] and Terms of Use. [ ]

5 years, 6 months

rtpengine sessions on timeout not freeing up RTP ports

by Istvan Mogyorosi

Hello Another rtpengine related question after having successfully implemented a dispatcher configuration. Call flow is ok, everything works well until I tried to increase call volume. Kamailio log showing "proxy replied with error: Ran out of ports" In the beginning both channels are up, then I can see a teardown on the incoming channel loosing the ability to collect DTMF. Using the CLI tool I have statistics showing that none (!) of the calls are "regular terminated", they are on timeout. After experimenting with handling BYE, I ended up could getting a "regular terminated" call by using route[RELAY] .... if (is_method("BYE")) { rtpengine_delete(); } and then I can see some good things! Received command 'delete' from 127.0.0.1:58538 Scheduling deletion of call branch 'as65b95845' (via-branch '') in 5 seconds Replying to 'delete' from 127.0.0.1:58538 (elapsed time 0.000216 sec) Please correct me if I'm doing wrong this way! cheers Istvan

5 years, 6 months

← Newer
1
2
3
4
5
6
7
8
9
10
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 May 2019