sr-users July 2008

sr-users@lists.kamailio.org

147 participants
206 discussions

[OpenSER-Users] Need Help..
by Marcio 07 Jul '08

07 Jul '08

Hi, Anyone would know?......how i can through of the perl(module perl v1.3) connect to database Mysql to execute DML's commands SQL...? Examples are welcome.. best regards, Marcio

2 1

[Serusers] iptel.org: where do you go: SLAMP and "SIP Akamai"
by Jiri Kuthan 06 Jul '08

06 Jul '08

Hello all, I wanted to share with everyone else my opinion on where SER and/or iptel.org is going, and ask folks for opinion and testing the new features mentioned bellow. Shortly I think the key goals on the software side are SLAMP bundling, security and performance. On the operational side, the technology is getting to a place which I like to call "akamai of sip" ... world-wide distributed reliable SIP network. - BUNDLING. I'm a strong believer in SLAMP ... SER/SEMS/SERWEB -- Linux -- Apache -- Mysql -- Perl/Python/PHP. It is the software mesh-up that actually allows to build a variety of web applicatons. We now have SIPSAK, SERWEB and SEMS well synchronized and working with each other. SER has advanced on the packaging side to provide out-of-the-box experience: we have a very complete configuration file (OOB) dealing with most common real-word scenarios, we have all-in-one packaging that puts all the pieces in a single box. (see bellow for more). - SECURITY: Enormous attention has been paid to it. Actually I have contracted a security review, TCP code known to be easily vulnerable to blocking attacks has been made more robust, and SER now implements predictive nonces to deal with replay attacks mounted on digest authentication. Support for Identity (see bellow and RFC4474) has been extensively tested in Sipits. In fact, I consider lack of Internet-wide notion of identity one of the greatest hassles in the Internet and this is our modest contribution to address that. - PERFORMANCE. This can be never appreciated enough. While SER can easily serve quite large populations on commodity hardware, the real challenge is in fact dealing with abnormalities. This includew boot avalanches of SIP telephones, misconfigurations, unsolicited traffic, simply all the things you never wish to happen. Still they do. Currently the bottleneck turned out to be database, which has been greatly improved. It is worthwile mentioned we eat our own dog's food ... the public iptel.org service is powered by SLAMP. I'm working with my collegues on advance concepts that allow to deal with massive geographic dispersion (akamai-like experience), routing, etc. See bellow for more. OOB ----- * Features First -- OOB, which stands for out-of-the-box, and is a very exhaustive configuration of SER (we might have called it all-you-can-eat) , dealing with most of common features/problems: - NAT traversal - basic call services (variants of call forwarding, speed-dial) - multidomain hosting - gateway routing and gateway protection * Requirements OOB is available for SER 2.0 and higher, as it leverages some of the key SER features coming up with this thoroughly overhauled version. There is also OOB debian package for it -- not that it only includes SER without supporting packages such as mysql and rtp proxy. * Roadmap - even more security (rate-limit, identity, permissions) Most important to me appears Identity support. Given that lack of some credible notion of identity is causing a lot of mess, I think it is time to begin using verifiable identity with SIP. SER supports Identity (RFC4474) since quite a while and has been tested in sipits for it. Also on the security page, I think the famous module rate-limit shall appear in OOB rather soon than late. * Source: http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/etc/ser-oob.cfg?re… ai1 ---- * Features All-in-one is an attempt to bring all related packages on a single box using a simple installation procedure. The metapackage includes SER, SEMS, SERWEB, SER_CTL. It is in its very early stage, so please help by testing it. * Requirements debian. There is currently no other system supported. * To use it: - put the iptel.org debian package repository in your source.list: deb http://ftp.iptel.org/debian etch main cvs - update package list and repositories: apt-get update; apt-get upgrade - set appropriate reconfiguration level to *medium* dpkg-reconfigure - install ai1 apt-get install ai1 * Known limitations It is really just finished and only little tested. Please help testing and collecting the initial experience. Other semi-news --------------- While there are interesting periodic Talmudic discussion when 2.0 shall be labeled as "released", there is lot of good work going on with SER 2.1 (the "HEAD version"). Let me make a "sales pitch" for at least some parts of it which have so far made it to CVS. A very important change is the DB-API overhaul. For those of you who are running deployments which are a bit "dense", it is certainly no secret that database matters. In fact, it it not unusual to have about seven database transactions for a single SIP invite transaction. Thus database has a huge impact on performance, and if database is for whatever reason lame, so will be soon everything else. A large portion of all major failures I have witnessed were someway related to databases. The DB-API performs very well and is ready to be used with real-time databases. Also a new LDAP module has been contributed (single DB driver for all modules, not like at this moment yet radius-based modules for different functionalities). It is also important to realize that well-done database engine is the key instrument for integrating applications (or if you wish to use this horrible buzzword, databases are great *middleware*.) The thing is that in reality it is mysql and other noble databases that connect applications (such as SER) with web-front-ends (such as SERWEB), CLIs (such as SERCTL) and any other thinkable applications. Personally I think that middleware technologies such as "corba" have actually not achieved such an impact as good open databases did -- long live SLAMP. On the "aplication-mash-up side", another step is going to be single-sign-on. I believe this will be very useful in integrating SIP, and serweb with other applications, such as address books. Our esteemed serweb author is working on it hard right now. New configuration framework is extremelly useful thing -- now many things can be easily managed in SER in real-time without the need to restart the server. http://sip-router.org/browser/ser/doc/cfg.txt?rev=6627%3A746a56c7a1f4 An extremely long list of useful features and fixes have appeared on CVS, be blessed all who have contributed to keeping SER a well-oiled machine by adding all these laborious changes. I apologize to all the authors for not mentioning all the important contributions, this email just began to be more lengthy than I hoped for. http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/NEWS?rev=HEAD&cont… Also as you know, there is a SER book, alas only in German now: http://www.amazon.de/Internet-Telefonie-VoIP-mit-Asterisk-SER/dp/3937514163 iptel.org setup ---------------- I think the iptel.org running SIP service deserves some extra attention. In the future I actually plan to "fork" a new mainling list, so that folks can better separate debates related to the software and to the running service. In the heart of the service, there is SER running (CVS/HEAD version). With SER, we have many useful features: - have-my-domain ... folks can claim, administer and run their own domains - BETA: Akamai-like services for selected hosted domains. Briefly, it allows subscribers to be served by a server close to them. Particularly beneficial for media relay. - media services: 1000(a)iptel.org ... voicemail, 000777 prefix ... conference bridge; there is also zRTP-secured confidential conferencing service - subscriber provisioning (domain owners can largely manipulate structure user profiles) - multiple identities (00 prefix) allows you to terminate SIP calls using alternate accounts preconfigured in user profile - monitoring (administrator tool which is essential to keep the service healthy) - massive routing administrator provisioning Of course not all of it is achieved using SER alone -- that's where the SLAMP concept comes in. Media services are powered by SEMS, Web-provisioning is achieved using SERWEB. Even proprietary components fit in very well, such as the monitoring box (palladion), load-balancer and one private SER extension (the massive route provisioning). notes to openser users ---------------------- stay tuned. whereas all the development mentioned here relates to SER, I'm confident they will make their way to openser as well. We had recently a very open (:-)) meeting with openser advocate, Henning W. and there was quite lot of good will to exchange. See http://openser.org/pipermail/devel/2008-June/013880.html

3 4

[OpenSER-Users] Handle 302 Moved Temporarily
by Dmitry Lyubimkov 05 Jul '08

05 Jul '08

We need process 302 redirection Message in our OpenSER (ver 1.3) script. we use failure_route failure_route[1] { append_hf("Transfer-code: $T_reply_code\r\n"); if t_check_status("(302)|(301)"){ append_hf("Original-URI: $ru\r\n"); get_redirects("*"); rewritehostport("172.16.2.6"); # append_branch(); route(1); } else if t_check_status("(408)|(486)"){ rewritehostport("172.16.2.6"); append_branch(); route(1); }; } All fails with 4xx code (Timeout, Busy) work right. OpenSER send them to asterisk (172.16.2.6). But we cannot do the same with 301 and 302 code, because there is a header Contact in their replies. And we need to change our URI according this field. Using Tcpdump I get some diagnostic: Invite to UA: 18:48:31.898163 IP 78.36.60.131.sip > 172.16.76.4.53568: SIP, length: 1258 E.....@.@...N$<...L....@....INVITE sip:loft@172.16.76.4:53568;rinstance=87e2d8d91648c3bf SIP/2.0 Record-Route: <sip:78.36.60.131;lr;ftag=2D551EE4-2538;nat=yes> Via: SIP/2.0/UDP voapp.ru:5060;branch=z9hG4bK8b81.6f656603.0 Via: SIP/2.0/UDP 78.36.60.129:5060;rport=52061;x-route-tag="tgrp:m200" From: <sip:78142722856@78.36.60.129>;tag=2D551EE4-2538 To: <sip:78142599298@78.36.60.131> Date: Fri, 04 Jul 2008 14:39:48 GMT Call-ID: E338E8F0-490D11DD-834CC831-1B0A3D9F(a)78.36.60.129 Supported: timer,100rel Min-SE: 1800 Cisco-Guid: 3812117704-1225593309-2202650673-453655967 User-Agent: Cisco-SIPGateway/IOS-12.x Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO CSeq: 101 INVITE Max-Forwards: 5 Timestamp: 1215182388 Contact: <sip:78142722856@78.36.60.129:5060> Expires: 180 Allow-Events: telephone-event Content-Type: application/sdp Content-Length: 375 Reply witn 302 code: 18:48:32.019255 IP 172.16.76.4.53568 > 78.36.60.131.sip: SIP, length: 474 E...\...}.]+..L.N$<..@.... .SIP/2.0 302 Moved Temporarily Via: SIP/2.0/UDP voapp.ru:5060;branch=z9hG4bK8b81.6f656603.0;received=78.36.60.131 Via: SIP/2.0/UDP 78.36.60.129:5060;rport=52061;x-route-tag="tgrp:m200" Contact: <sip:78142705353@voapp.ru> To: <sip:78142599298@78.36.60.131>;tag=e3040a33 From: <sip:78142722856@78.36.60.129>;tag=2D551EE4-2538 Call-ID: E338E8F0-490D11DD-834CC831-1B0A3D9F(a)78.36.60.129 CSeq: 101 INVITE User-Agent: X-Lite release 1011s stamp 41150 Content-Length: 0 Our acknoledgement: 18:48:32.019395 IP 78.36.60.131.sip > 172.16.76.4.53568: SIP, length: 395 E.....@.@..yN$<...L....@...`ACK sip:loft@172.16.76.4:53568;rinstance=87e2d8d91648c3bf SIP/2.0 Via: SIP/2.0/UDP voapp.ru:5060;branch=z9hG4bK8b81.6f656603.0 From: <sip:78142722856@78.36.60.129>;tag=2D551EE4-2538 Call-ID: E338E8F0-490D11DD-834CC831-1B0A3D9F(a)78.36.60.129 To: <sip:78142599298@78.36.60.131>;tag=e3040a33 CSeq: 101 ACK Max-Forwards: 70 User-Agent: OpenSER (1.3.1-notls (i386/linux)) Content-Length: 0 And new Invite: 18:48:32.019762 IP 78.36.60.131.sip > 172.16.76.4.53568: SIP, length: 1327 E..K..@.@...N$<...L....@.7..INVITE sip:78142705353@172.16.76.4:53568 SIP/2.0 Record-Route: <sip:78.36.60.131;lr;ftag=2D551EE4-2538;nat=yes> Via: SIP/2.0/UDP voapp.ru:5060;branch=z9hG4bK8b81.6f656603.1 Via: SIP/2.0/UDP 78.36.60.129:5060;rport=52061;x-route-tag="tgrp:m200" From: <sip:78142722856@78.36.60.129>;tag=2D551EE4-2538 To: <sip:78142599298@78.36.60.131> Date: Fri, 04 Jul 2008 14:39:48 GMT Call-ID: E338E8F0-490D11DD-834CC831-1B0A3D9F(a)78.36.60.129 Supported: timer,100rel Min-SE: 1800 Cisco-Guid: 3812117704-1225593309-2202650673-453655967 User-Agent: Cisco-SIPGateway/IOS-12.x Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO CSeq: 101 INVITE Max-Forwards: 5 Timestamp: 1215182388 Contact: <sip:78142722856@78.36.60.129:5060> Expires: 180 Allow-Events: telephone-event Content-Type: application/sdp Content-Length: 375 Transfer-code: 302 Original-URI: sip:loft@172.16.76.4:53568;rinstance=87e2d8d91648c3bf But why sip:78142705353@172.16.76.4:53568? Why not 172.16.2.6 (rewritehostport("172.16.2.6");) or sip:78142705353@voapp.ru (Contact: <sip:78142705353@voapp.ru>)? Where is error? I need to sent all 3xx redirects to dedicated server but I also need to get Contact header from UA reply and put it in outgoung message. What commands must I use? Can anybody help me and get fragment of openser script? Thx Dmitry

2 1

[OpenSER-Users] How to cancel a branch
by Zappasodi Daniele 05 Jul '08

05 Jul '08

Hello, I need something similar to the t_uac_cancel fifo command, but when there are more branches (parallel forking) it should offer the opportunity to select the branch to cancel. Is there a way (with openser.cfg or with a fifo command or a with a tm exported api or ...) to choose the branches to cancel? regards Daniele ********************************************************************** The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message inerror. **********************************************************************

2 1

[OpenSER-Users] Help please: OpenSer as RLS.
by Noble Antony T 04 Jul '08

04 Jul '08

Hi, I have compiled the Openser with RLS module in my desktop, and it seems installation went fine... But when I try to start the openser, I am getting the following error..... * Jul 3 10:11:49 [10721] ERROR:core:table_version: invalid type (2) or nul (0) version columns for xcap Jul 3 10:11:49 [10721] DBG:core:db_free_rows: freeing 1 rows Jul 3 10:11:49 [10721] DBG:core:db_free_rows: row[0]=0x815d530 Jul 3 10:11:49 [10721] DBG:core:db_free_rows: 0x815d530=pkg_free() RES_ROWS Jul 3 10:11:49 [10721] ERROR:presence_xml:mod_init: Wrong version v-1 for table <xcap>, need v3 Jul 3 10:11:49 [10721] ERROR:core:init_mod: failed to initialize module presence_xml Jul 3 10:11:49 [10721] ERROR:core:main: error while initializing modules Jul 3 10:11:49 [10721] DBG:rls:destroy: start* But my MySQL shows, the version of XCAP as *mysql> select * from version where table_name="xcap" ; +------------+---------------+ | table_name | table_version | +------------+---------------+ | xcap | 3 | +------------+---------------+ 1 row in set (0.00 sec) mysql> * Though the version information is present for the xcap table, this error is coming. I have created the database using the following * stinbng46:/home/nthattil/tmp/src_openser_install# /usr/local/sbin/openserdbctl /usr/local/sbin/openserdbctl $Revision: 3540 $ usage: openserdbctl create <db name or db_path, optional> .....(creates a new database) openserdbctl drop <db name or db_path, optional> .......(!entirely deletes tables!) openserdbctl reinit <db name or db_path, optional> .....(!entirely deletes and than re-creates tables!) openserdbctl backup <file> .................................(dumps current database to file) openserdbctl restore <file> ................................(restores tables from a file) openserdbctl copy <new_db> .................................(creates a new db from an existing one) openserdbctl migrate <old_db> <new_db> .....................(migrates DB from 1.2 to 1.3, not implemented yet!) openserdbctl presence ......................................(adds the presence related tables) openserdbctl extra .........................................(adds the extra tables) openserdbctl serweb ........................................(adds the SERWEB specific tables) * The Version of Openser I used is *stinbng46:/home/nthattil/tmp/src_openser_install# /usr/local/sbin/openser -V version: openser 1.3.2-notls (i386/linux) flags: STATS: Off, EXTRA_DEBUG, USE_IPV6, USE_TCP, DISABLE_NAGLE, USE_MCAST, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. svnrevision: unknown @(#) $Id: main.c 3590 2008-01-28 17:46:56Z bogdan_iancu $ main.c compiled on 03:33:43 Jul 3 2008 with gcc 4.2.3 *I downloaded the entire source-code from the location below * http://www.openser.org/pub/openser/latest/src/openser-1.3.2-notls_src.tar.gz * I wanted to use the integrated XCAP server, which will use the mysql database for itself, instead of HTTP protocol. My Configuration file, I am including along with this mail... also the Openser Log file.... *Somebody please help me....... *Please point out, if something I am missing to configure..... -- Thanks & Regards, Noble Antony Thattil.

2 5

[OpenSER-Users] Need Help: OpenSer as RLS.
by Noble Antony T 04 Jul '08

04 Jul '08

1 0

[OpenSER-Users] Load Balancing
by Guilherme Loch Waltrick Góes 03 Jul '08

03 Jul '08

What's the best way of doing OpenSER load balancing and failover ? I'm trying to do a DNS Round Robin with two OpenSER 1.3.2 but sometimes when a user registered on server1 tries to call a user at server2 the call is not completed. In this scenario I have a common MySQL cluster serving both OpenSER servers. Any help ? Best Regards, -- Guilherme Loch Góes Visite nossa loja virtual: http://www.shopvoip.com.br Notícias e Fórum sobre VoIP com software livre: http://www.asteriskexperts.com.br

2 1

[Serusers] reply to port 5060
by David Lubarski 03 Jul '08

03 Jul '08

Hi, I have a problem using SER, i have a client behind CheckPoint FW, when the client tries to register, SER receives the SIP REGISTER message and SER reply to the source IP and source PORT, but because the client is behind CheckPoint FW if the source port is not 5060 the FW blocks it, so i need SER to reply not to the source port of the client but to port 5060. i'll attach ngrep on the SER server: client sends REGISTER to the SER server at 192.168.0.161:5060. U 2008/06/12 21:36:01.654005 10.6.67.10:31472 -> 192.168.0.161:5060 REGISTER sip:213.8.57.218 SIP/2.0..Via: SIP/2.0/UDP 10.6.67.10:31472;branch=z9hG4bK-d87543-de5ac063e 9293020-1--d87543-;rport..Max-Forwards: 70..Contact: <sip:200@10.6.67.10:31472;rinstance=82602d40693 d48a6>;expires=0..To: "test1"<sip:200@213.8.57.218>..From: "test1"<sip:200@213.8.57.218>;tag=5c6b793 a..Call-ID: NmI4MTUyMWY5MTEwYTI3ZjY2ZTE2ZTMzNzk5ZGFmZWI...CSeq: 5 REGISTER..Allow: INVITE, ACK, CANC EL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO..User-Agent: X-Lite release 1011s stamp 41 150..Authorization: Digest username="200",realm="localhost",nonce="48516daafb5a3406078621 <http://www.snapanumber.com/>9a55fdb4908 9064386",uri="sip:213.8.57.218",response="b8501a2d0c096b934320be23363dee32",algorithm=MD5..Content-L ength: 0.... # SER server response to the source IP and source port U 2008/06/12 21:36:01.654992 192.168.0.161:5060 -> 10.6.67.10:31472 SIP/2.0 200 OK..Via: SIP/2.0/UDP 10.6.67.10:31472;branch=z9hG4bK-d87543-de5ac063e9293020-1--d87543-; rport=31472..To: "test1"<sip:200@213.8.57.218>;tag=40c9dbfbe83fe4e1cec231af33432933.321f..From: "tes t1"<sip:200@213.8.57.218>;tag=5c6b793a..Call-ID: NmI4MTUyMWY5MTEwYTI3ZjY2ZTE2ZTMzNzk5ZGFmZWI...CSeq: 5 REGISTER..Server: OpenSER (1.3.2-notls (i386/linux))..Content-Length: 0.... but i need to response to port 5060 and not the source port , i'm not using rport, i also talk to CheckPoint service and they claim that they are working according RFC 3261, and that my SER server should reply to port 5060 any suggestions? Thanks In Advance, David Lubarski,

3 4

[Serusers] ser2-sasi : how to send instant message from shell script
by Rafael 03 Jul '08

03 Jul '08

Hi all, i have running ser2-sasi. is there a possibility to send instant message from a shell script like in the older versions with the follow example ? #!/bin/sh # cat > /tmp/ser_fifo <<EOF :t_uac_dlg:hh NOTIFY sip:receiver@127.0.0.1 . From: sip:originator@foo.bar To: sip:receiver@127.0.0.1 foo: bar_special_header x: y p_header: p_value Contact: <sip:devnull@192.168.0.100:9> 65 Chapter 4. Application Writing Content-Type: text/plain; charset=UTF-8 . Hello world!!!! $@ . EOF regards rafael

2 1

[OpenSER-Users] Help with snmpstats setup
by mayamatakeshi 03 Jul '08

03 Jul '08

Hello, I'm trying to test with snmpstats following instruction from http://www.openser.org/docs/modules/1.3.x/snmpstats.html >From snmpd output, I can see openser is connecting to it, but i don't see openser uploading any info (I'm running "snmpd -f -Dagentx -x localhost:705 2>&1 | less"). Then, when I try to get any openser info using snmpget or snmpwalk, nothing shows up. Maybe I am missing something (I confirmed snmpd finds and loads openser MIBs). Regards, takeshi

3 4

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 July 2008