sr-users March 2007

sr-users@lists.kamailio.org

192 participants
380 discussions

[Serusers] Capturing all messages for testing purposes
by POON Ben 11 May '07

11 May '07

Hi, I am setting up a testing environment with about 100 users. I would like to see who is online/registered, conversation times, protocols, etc. Basically I want to be able to capture all the messages for troubleshooting purposes, durability, compatibility, reliability, etc. Will the acc module do that for me, how do I set it up to capture the data? Thank you very much, Ben

4 6

[Users] 183 early media and NATed clients
by Jeff Williams 07 May '07

07 May '07

Guys, I'm wondering what solutions there are to this problem. We have some NATed clients making outgoing calls. The NAT traversal is done using mediaproxy and works fine. However, we have a problem with 183 responses and early media ringing sounds. The problem is that before the NATed client starts sending out RTP data, mediaproxy doesn't know which IP and port to send the RTP traffic to. Some of the NETed clients don't start sending out RTP traffic until the call is connected, therefore none of the early media (ringing sounds) reaches the user - making it sound like dead air. Any ideas? Jeff

4 7

[Users] Proxy Route Processing
by Victor Gamov 20 Apr '07

20 Apr '07

Hi guys! I have a question about "Proxy Route Processing" I have following request comes to my OpenSER (xxx.xxx.xxx.xxx is IP of this OpenSER): PRACK sip:1111@xxx.xxx.xxx.xxx:5060;nat=yes SIP/2.0 Via: SIP/2.0/UDP 192.168.100.77:5060;branch=z9hG4bK_00179A52BC45_T59048F1A From: "Vit-Horosho" <sip:vit-horosho@xxx.xxx.xxx.xxx>;tag=00179A52BC45_T1304371222 To: <sip:1111@xxx.xxx.xxx.xxx:5060>;tag =0015E9A0D47D_T1002915332 Call-ID: CALL_ID3_00179A52BC45_T2098965184(a)192.168.100.77 RAck: 1909013112 135588358 INVITE CSeq: 135588359 PRACK Contact: <sip:vit-horosho@192.168.100.77:5060> Route: <sip:xxx.xxx.xxx.xxx;lr=on;ftag=00179A52BC45_T1304371222> Content-Length: 0 As we reading in RFC3261 "16.12 Summary of Proxy Route Processing" part: 1. Request-URI must be rewrited based on location service 2. Route header must be removed because it indicate this proxy 3. Proxy will forward the request to the resource indicated by the URI in the topmost Route header field value (but we have not this Route after step 2) or in the Request-URI if no Route header field is present (so it must be forwarded to URI getted on step 1) But when I inspect OpenSER debug messages I found the following: 0(99796) parse_headers: flags=200 0(99796) is_preloaded: No 0(99796) grep_sock_info - checking if host==us: 11==11 && [xxx.xxx.xxx.xxx] == [xxx.xxx.xxx.xxx] 0(99796) grep_sock_info - checking if port 5060 matches port 5060 0(99796) after_strict: Next hop: 'sip:xxx.xxx.xxx.xxx;lr=on;ftag=00179A52BC45_T1304371222' is loose router 0(99796) parse_headers: flags=ffffffffffffffff 0(99796) rewrite_uri: Rewriting Request-URI with 'sip:xxx.xxx.xxx;lr=on;ftag=00179A52BC45_T1304371222' 0(99796) after_strict: The last route URI: 'sip:xxx.xxx.xxx.xxx;lr=on;ftag=00179A52BC45_T1304371222' 0(99796) parse_headers: flags=ffffffffffffffff So request is not forwarded as I expect Is it my misconfiguration or my misunderstood of RFC3261 ? (the part of openser.cfg followed): ----------- cut here ---------------- # we record-route all messages -- to make sure that # subsequent messages will go through our proxy; that's # particularly good if upstream and downstream entities # use different transport protocol record_route(); #xdbg("\n\troute[0]: before loose_route() ou=$ou; ru=$ru\n"); # subsequent messages withing a dialog should take the # path determined by record-routing if ( loose_route() ) { # mark routing logic in request append_hf("P-hint: rr-enforced\r\n"); # route(1); }; force_rport(); [ request processing with lookup() and actually route(1) followed ] ----------- /cut here ----------------

4 15

[Users] Using OpenSER as SIP Proxy over NAT
by Saar Carmi 19 Apr '07

19 Apr '07

Hi I need to use the SER proxy over NAT. For that, I only need that all SIP communcation between SER and other Sip Server will always work on a single port - altough the SIP client that connects SER use different port for REGISTER and INVITE Is it possible? Thank you Saar Carmi -- Saar Carmi Mobile: 054-7782417 Email: saarcarmi(a)gmail.com

2 1

[Users] NEW FEATURE: DNS-based failover
by Bogdan-Andrei Iancu 19 Apr '07

19 Apr '07

Hi everybody, OpenSER 1.2.0 has now the capability to do DNS based failover, according to RFC3263 (http://www.ietf.org/rfc/rfc3263.txt). The SIP resolver was enhanced to to be able to save and resume later the DNS queries in order to get all possible IP destinations. The resolving process is step-by-step done (get next IP only on demand) to minimize the total number of DNS queries. So having this support does not imply, in normal processing, more load on the DNS server. Additional queries are done only when needed (after failure detected). The scanning for new IP destinations is done by the SIP resolver on all DNS levels: NAPTR, SRV, A. Both core and TM are using this new feature. In core, the stateless forwarding can do only DNS-based failover at transport level (if no egress interface found or send operation failed due whatever reason). In TM, the DNS-based failover is extended to transaction level. If the transaction completes with 503 or 408 with no reply, automatically, a new branch will be fork if any destination IP can be found by the DNS resolver. Read more here http://www.openser.org/docs/modules/1.2.x/tm.html#AEN103 For controlling this feature use: - newly added core parameter "disable_dns_failover" - use to generally disable the DNS-based failover. By default is false. - in TM, t_relay() take a new flag for turning off the DNS-based failover. This setting is per transaction. By default, the failover is done. Any feedback is appreciated. regards, Bogdan

4 9

RE: [Serusers] SIP SER
by Goh, Tee-Yong 14 Apr '07

14 Apr '07

Hi Karim, Yes you are right. Please advice. Thank you. Regards, Howard -----Original Message----- From: karim basraoui [mailto:basraouik@gmail.com] Sent: Saturday, March 03, 2007 8:01 PM To: Goh, Tee-Yong Cc: serusers(a)lists.iptel.org Subject: Re: [Serusers] SIP SER So if i understand, when a clint registers, SER will automatically send invites to the other clients and make connections with them? 2007/3/3, Goh, Tee-Yong < <mailto:gohty@m1.com.sg> gohty(a)m1.com.sg>: Dear Karim, Thank you for your reply. Yes you are right. I have having difficulty searching for this for past 2 months. Yes. Here is what i want. Once i receive the REGISTER messages, my SER will send out "INVITE" message to my other clients. This is what i am intended to do. However, i could not search for the right coding inside the ser-0.9.6. Please advice and apologies if any inconvenience caused for you. Thanks. Regards, Howard -----Original Message----- From: karim basraoui [mailto: basraouik(a)gmail.com] Sent: Saturday, March 03, 2007 7:18 PM To: Goh, Tee-Yong Subject: Re: [Serusers] SIP SER Hi, Do you want to make changes on SER behaviour when it receives REGISTER messages. If it's the case you can make a condition in the "ser.cfg" file, in the bloc "route{ ... }". for example: route { if (method == "REGISTER") { #what you want to do}; } 2007/3/3, Goh, Tee-Yong < gohty(a)m1.com.sg <mailto:gohty@m1.com.sg> >: Hi, May i know from the SER-0.9.6, where can i look for and make changes for the SER when receiving "REGISTER" message and responsing " 200 OK" back to the corresponding node or clients? Would appreciate your assistance and advice as soon as possible as i have difficultly locating the coding. Please advice where i can find the script to edit the above mentioned messages. Apologies for the inconvenience caused. Thank you. Regards, Howard _____ This email (including any attachment) is subject to the following disclaimer: http://m1.com.sg/M1/misc/disclaimer <http://m1.com.sg/M1/misc/disclaimer> _____ _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers -- BASRAOUI Karim www.basraouik.afrikart.net _____ This email (including any attachment) is subject to the following disclaimer: http://m1.com.sg/M1/misc/disclaimer <http://m1.com.sg/M1/misc/disclaimer> _____ -- BASRAOUI Karim www.basraouik.afrikart.net This email (including any attachment) is subject to the following disclaimer: http://m1.com.sg/M1/misc/disclaimer

4 5

[Serusers] using SER
by gabrielyans 13 Apr '07

13 Apr '07

Hi I was looking for a softswitch and found that SER could be usefull for what I am going to implement. I want to have a Signalling GW (I think it will be SER) who will receive calls and then direct them according to his routing table. SER will transfer calls to Asterisk, and then Asterisk (together with A2billing) will make the accounting for that call. Is it the right choise to use SER? Actually, I cannot find any forum concerning SER to check if there are already someone who is using SER as I am planning to use. Also, concerning WEB interface - it seams that SERWeb gives only user-management interface and not administrator interface - am I right? Please advise. gabrielyans

3 2

[Users] "detached" timer
by T.R. Missner 10 Apr '07

10 Apr '07

Does anyone know what causes this? */set_timer for 1 list called on a "detached" timer -- ignoring /* I also see */set_timer for 3 list called on a "detached" timer -- ignoring /* When this happens Openser seems to lock up for 10 seconds or so. From searching it appears this is caused by a race but I am not sure what the race is or why this results in an unresponsive openser instance for multiple seconds. Transaction expiration racing reply? Desperately need to understand how this could be triggered so I can get customer to adjust system. Any way to adjust? tried tweaking fr_inv_timer but no joy. TR

6 32

[Serusers] problem with compiling the new CVS release
by İlker Aktuna (Koç.net) 10 Apr '07

10 Apr '07

Hi, I have a working SER installation which includes presence modules etc. Today I tried to compile the latest CVS version because of a requirement to the reigstrar module. (NAT support with mediaproxy) unfortunately, the "make" process did not comlete. I got these errors: make[1]: Entering directory `/root/yeni/sip_router/modules/acc_db' gcc -fPIC -DPIC -g -O9 -funroll-loops -Wcast-align -minline-all-stringops -falign-loops -ftree-vectorize -mtune=athlon64 -Wall -DNAME='"ser"' -DVERSION='"2.1.0-dev2"' -DARCH='"i386"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 4.1.0"' -D__CPU_i386 -D__OS_linux -DSER_VER=2001000 -DCFG_DIR='"/root/ser2/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP -DDNS_IP_HACK -DUSE_IPV6 -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLACKLIST -DDBG_QM_MALLOC -DUSE_TLS -DTLS_HOOKS -DFAST_LOCK -DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DCC_GCC_LIKE_ASM -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKARROUND -DHAVE_SELECT -c acc_db.c -o acc_db.o acc_db.c:164: error: expected â€˜=â€™, â€˜,â€™, â€˜;â€™, â€˜asmâ€™ or â€˜__attribute__â€™ before â€˜acc_dbfâ€™ acc_db.c:172: error: expected â€˜=â€™, â€˜,â€™, â€˜;â€™, â€˜asmâ€™ or â€˜__attribute__â€™ before â€˜keysâ€™ acc_db.c:173: error: expected â€˜=â€™, â€˜,â€™, â€˜;â€™, â€˜asmâ€™ or â€˜__attribute__â€™ before â€˜valsâ€™ acc_db.c: In function â€˜init_dataâ€™: acc_db.c:406: error: â€˜keysâ€™ undeclared (first use in this function) acc_db.c:406: error: (Each undeclared identifier is reported only once acc_db.c:406: error: for each function it appears in.) acc_db.c:407: error: â€˜valsâ€™ undeclared (first use in this function) acc_db.c: In function â€˜fmt2strarâ€™: acc_db.c:594: error: â€˜valsâ€™ undeclared (first use in this function) acc_db.c: In function â€˜log_requestâ€™: acc_db.c:755: error: â€˜acc_dbfâ€™ undeclared (first use in this function) acc_db.c:760: error: â€˜keysâ€™ undeclared (first use in this function) acc_db.c:760: error: â€˜valsâ€™ undeclared (first use in this function) acc_db.c: In function â€˜child_initâ€™: acc_db.c:974: error: â€˜acc_dbfâ€™ undeclared (first use in this function) acc_db.c: In function â€˜mod_destroyâ€™: acc_db.c:989: error: â€˜acc_dbfâ€™ undeclared (first use in this function) acc_db.c: In function â€˜mod_initâ€™: acc_db.c:1014: warning: implicit declaration of function â€˜bind_dbmodâ€™ acc_db.c:1014: error: â€˜acc_dbfâ€™ undeclared (first use in this function) acc_db.c:1020: warning: implicit declaration of function â€˜DB_CAPABILITYâ€™ acc_db.c:1020: error: â€˜DB_CAP_INSERTâ€™ undeclared (first use in this function) make[1]: *** [acc_db.o] Error 1 make[1]: Leaving directory `/root/yeni/sip_router/modules/acc_db' make: *** [modules] Error 1 # Does anyone have any idea what the problem is ? Thanks, ilker

8 25

[Users] Advanced OpenSER Programming Course, Paris, INRIA, June 4-6, 2007
by Daniel-Constantin Mierla 05 Apr '07

05 Apr '07

Hello, following some discussions started during first OpenSER Summit, we are happy to announce that first Advanced Programming Course will happen very soon. Courtesy of INRIA (many thanks to Philippe Sultan) we have the room and a good connected location. There will be three full days of deep analysis and survey of internal architecture and structures, best practices to add new features, optimizations and OpenSER's specific components (memory manager, locking system, ...). The course is dedicated to people willing to develop OpenSER extensions. It will be a class of 14 persons. The participation fee will be just to cover the logistic required for this event, estimated to be about 150-200Euro per person, for the full course (mainly is subject of how many participants will be registered). Teachers will be Bogdan-Andrei Iancu and Daniel-Constantin Mierla, from OpenSER development team, and the primary goal is to attract more developers to core components of OpenSER and build a higher development squad. Also, there will be open discussions to improve existing code and functionalities. If the interest for this event is high, the primary selection criteria will include the level of contributions so far and willingness to contribute in the future. New similar events will be scheduled if the number of people showing interest is enough for another one or more classes. For this one, we expect to have people with pretty good knowledge of SIP and OpenSER operation, to avoid long introduction lessons. If you are interested in this course, please send an email to team(a)openser.org. <mailto:team@openser.org.> News link: http://www.openser.org/mos/view/News/NewsItem/Advanced-OpenSER-Programming-… Cheers, Daniel

1 1

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 March 2007