sr-users July 2012

sr-users@lists.kamailio.org

64 participants
92 discussions

by Andrew Pogrebennyk

At least some links at http://www.kamailio.org/wiki/ don't work at the moment: Install Kamailio v3.3.x From GIT Upgrade Kamailio v3.1.x to v3.2.0 Upgrade Kamailio v3.2.x to v3.3.0 you are redirected to some instruction from DokuWiki Installer when trying to visit them. Could somebody please check it? Thanks. Andrew

11 years, 11 months

routing based on username

by Richard Zheng

Hi, We are trying to follow http://kb.asipto.com/asterisk:realtime:kamailio-3.1.x-asterisk-1.6.2-astdbto setup Kamailio as front end and multiple PBXs as back end. We need to forward sip messages to the respective servers based on the contact. For example, users 101, 102 go to PBX at 1.1.1.1 and users 201, 202 go to PBX at 1.1.1.2. Where is a good place to save this info and how to route them in the config? Also we have some users with fixed IP addresses which don't use authentication. How do we route the calls based on source IP? Since we have plenty of these users, we'd like to save them in database too. Any advice is appreciated! Richard

11 years, 11 months

Add Own Plug-in

by Ananth Kollipara

Hi, Can you please provide the steps to add a plug-in? Regards, Ananth

11 years, 11 months

ACK not relayed

by David Notivol

In a UAC-Kamailio-UAS scenario, we've found a case where the ACK coming from uac is not relayed by our proxy to the uas. This is the log for the ACK message: Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [parser/msg_parser.c:624]: SIP Request: Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [parser/msg_parser.c:626]: method: <ACK> Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [parser/msg_parser.c:628]: uri: <sip:59138553189@79.170.68.157> <sip:59138553189@79.170.68.157> Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [parser/msg_parser.c:630]: version: <SIP/2.0> Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [parser/parse_via.c:1286]: Found param type 235, <rport> = <n/a>; state=6 Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [parser/parse_via.c:1286]: Found param type 232, <branch> = <z9hG4bKKc4gKXyemS9HD>; state=16 Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [parser/parse_via.c:2561]: end of header reached, state=5 Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [parser/msg_parser.c:511]: parse_headers: Via found, flags=2 Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [parser/msg_parser.c:513]: parse_headers: this is the first via Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [receive.c:149]: After parse_msg... Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [receive.c:190]: preparing to run routing scripts... Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: sl [sl_funcs.c:396]: DEBUG : sl_filter_ACK: to late to be a local ACK! Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: maxfwd [mf_funcs.c:85]: value = 65 Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [parser/parse_to.c:178]: DEBUG: add_param: tag=6ne1x6d6-CC-23 Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [parser/parse_to.c:802]: end of header reached, state=29 Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [parser/msg_parser.c:188]: DEBUG: get_hdr_field: <To> [52]; uri=[sip:59138553189@79.170.68.157] Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [parser/msg_parser.c:190]: DEBUG: to body [ <sip:59138553189@79.170.68.157> <sip:59138553189@79.170.68.157>] Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [parser/msg_parser.c:168]: get_hdr_field: cseq <CSeq>: <31362871> <ACK> Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [parser/msg_parser.c:202]: DEBUG: get_hdr_body : content_length=0 Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [parser/msg_parser.c:104]: found end of header Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [parser/parse_to.c:178]: DEBUG: add_param: tag=0cS8trtaF196F Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: <core> [parser/parse_to.c:802]: end of header reached, state=29 Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: sanity [mod_sanity.c:255]: sanity checks result: 1 Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: siputils [checks.c:106]: totag found Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: ERROR: <script>: ESTAMOS EN WITHIN Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: rr [loose.c:108]: No Route headers found Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: DEBUG: rr [loose.c:829]: There is no Route HF Jul 27 10:04:59 theseus-test /usr/local/kamailio/sbin/kamailio[17358]: ERROR: <script>: NO LOOSE ROUTE However, in a pcap trace I clearly see the Route header: This is the Record-Route in the 200 message Record-Route: <sip:79.170.68.157;lr;ftag=330cdf48-co1022-INS033> And this is the Route header in the ACk: Route: <sip:79.170.68.157;lr;ftag=330cdf48-co1022-INS033> I haven't been able to figure out what's going on. We have plenty of traffic working in that proxy. What am I missing? Thanks in advance David.

11 years, 11 months

BYE Race Condition

by Brandon Armstead

Hello, I am running into an issue where there is a race condition happening. I am looking for opinions / ideas on how to handle the following below scenario. Scenario. UAC places an outbound call -> upstream carrier. The call is disconnected on both ends at the exact same time, UAC -> sends BYE upstream Upstream Carrier -> sends BYE downstream Upstream 200 OK's the BYE UAC sends 481 back to Upstream Carrier for their generated BYE. The upstream carrier is complaining about receiving the relayed 481 responses -- so my first thought was simply to drop() these from relaying upstream. I am curious how other people are handling this? Would you suggest simply dropping the relay from being sent back upstream on the 481? Would you simply always 200 OK a downstream BYE from trusted carriers regardless of UAC response, and create separate transaction to send BYE downstream? Thank you as always. Look forward to your thoughts / suggestions / ideas. Sincerely, Brandon Armstead

11 years, 11 months

Error 403 not relaying

by Tayeb Meftah

hello, i'm using Kamailio with a simple registrare configuration i used the apt repository to install the developmant package of kamailio domain sip.tmvoip.net have 2 records, A record and AAA record (dual stacked) i configured it in my kamailio using siremis and in the kamctlrc config below: Kamailio.cfg: http://paste.debian.net/180972/ Kamctlrc: http://paste.debian.net/180973/ siptrace: http://paste.debian.net/180974/ note that 172.28.0.0/21 and 41.221.20.12/30 is routed, no nat. my current issue is if i register or i invite, i get error 403 not relaying trying to investigate this issu but i have no clue thank you everyone, -- Voice of the blind ™ broadcast freedom Phones: Algeria: +213-660-347746 USA, NewYork: +1(347)759-5883 iNum: +883510001288000 we're blind, but not deaf!

11 years, 11 months

Re: [SR-Users] Can't initialize shared memory

by Uri Shacked

> > this is the log when debug is 4... > > Jul 24 10:19:37 RNDSRV kamailio: : <core> [cfg.y:3532]: parse error in > config file /usr/local/etc/kamailio/global_params.cfg, line 121, column 54: > Can't initialize shared memory > Jul 24 10:19:37 RNDSRV kamailio: ERROR: mi_fifo [mi_fifo.c:271]: FIFO stat > failed: Bad address > > > not much. > line 121 on the file is the modparam for mi_fifo indication the > /tmp/kamailio_fifo file. > > # ----- mi_fifo params ----- > modparam("mi_fifo", "fifo_name", "/tmp/kamailio_fifo") > any ideas? > > >

11 years, 11 months

Reply to one topic correctly

by Duong Manh Truong

Hi list, I am a newbie of the maillist, I'm wondering that whenever i reply to a specific topic with the subject of "RE: [SR-Users]....", my email come to maillist in the way dislike what i wish, my email appears like a NEW topic instead of SUB topic (reply message form) I try several ways but still not get the correct method of reply, please help me to fix this, thanks.

11 years, 11 months

Re: [SR-Users] Kamailio with APNS

by Duong Manh Truong

Thank Klaus, I've try with t_suspend() and t_continue() as your guide, *#Failure route to react with negative messages failure_route[1] { if (t_check_status("5[0-9][2-9]")) { if(t_suspend()) { xlog("proceesing suspended in trasaction [$T(id_index):$T(id_label)]\n"); xlog("before sleep \n"); } if(async_sleep("20")) xlog("After sleep 20s \n"); if(t_continue('1','1','MYROUTE')) xlog("Continuation successfully \n"); exit; };* And i found that t_suspend() and async_sleep() runnung ok but t_continue() seems not running. I read about TMX module and TMX module Pseudo-Variables but still can not figure out it :( Secondly, in case of t_continue() runs successfully , please tell me how to let Kamailio resend the INVITE message to client B (before the t_continue(), i think so ) - while client B is waking up ? Which functions and modules that i need to do this? Thanks. ----------------------------------------------------------------- Hi! You have to use a failure route (http://kamailio.org/docs/modules/3.3.x/modules/tm.html#t_on_failure). In the failure route check if the reply code is 404 and if yes, trigger the APNS logic and then put the call e.g. on a stack and resume e.g. every second and ofrward to the "SIP server" again to see if the client is registered meanwhile. For the asynchronous processing take a look at these functions: t_suspend(),t_resume()[1]. For example you can call t_resume in a timer route every second. For the timer route, to know which transactions are currently suspended and are waiting for further processing, you could put the transaction identifiers in a message-queue [2] and read the queue from the timer route. regards Klaus [1] http://kamailio.org/docs/modules/3.3.x/modules_k/tmx.html#id2535968 [2] http://kamailio.org/docs/modules/3.3.x/modules/mqueue.html On 24.07.2012 06:02, Duong Manh Truong wrote: >* Hi list,*>**>* My team are developing a SIP client for mobile running iOS ,*>**>* then having to deal with the "back ground mode" problem while this soft*>* is installed on mobiles*>**>* One of the solutions is using APNS. (Apple Push Notification Service)*>**>* I wanna to use Kamailio as SIP Redirect / Proxy for my current SIP server*>**>* The model is like that:*>**>* User A <---------> Kamailio <---------> SIP server <--------> User B*>**>* IF UserA call UserB, UserB is not available now (not registered yet),*>* normally, SIP server will reply Kamailio with "404 Not found"*>**>* In that case, i want to set up Kamailio do the communication with APNS*>* and waiting for UserB "Wake up" then RESEND the Invite message ......*>* (instead of forwarding this 404 message to UserA)*>**>* I am getting stuck at how Kamailio can control "404 Not found" message*>* which it receives from SIP server .*>**>* I do searching around several days but still can not get any clearer*>* points.*>**>* Please help me with some instruction/ configuration of Kamailio for this*>* case !*>**>* Thank you very much.*>**>**>* _______________________________________________*>* SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list*>* sr-users at lists.sip-router.org <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>*>* http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users*>**

11 years, 11 months

How to change _only_ next hop and dpn't touch content of message?

by intel＠intrans.baku.az

I want retransmit some me ssages to other sip server as is. f.e server sip1.com receives invite message INVITE user(a)somewhere.org i want to send it to server sip2.com as is. Unfortunately, if i use rewritehostport() function, or modify $rp $rd pseudovariables fe $rp='sip2.com', kamailio changes invite uri, and send to sip2.com INVITE user(a)sip2.com The To: filed left untouched How can I resend message without modifications? I've tried also modify $dp and $dd pseudovariables, but then message wasn't sent anywhere,and in log I can see this message: Jul 27 15:44:54 dsdb01 /usr/sbin/kamailio[17786]: ERROR: tm [t_fwd.c:1523]: ERROR: t_forward_nonack: no branches for forwarding Jul 27 15:44:54 dsdb01 /usr/sbin/kamailio[17786]: ERROR: tm [tm.c:1375]: ERROR: w_t_relay_to: t_relay_to failed What else can I try? --

11 years, 11 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 July 2012