sr-users November 2006

sr-users@lists.kamailio.org

189 participants
307 discussions

[Serusers] SER pre-release - PRESENCE ISSUES
by SER LIST 10 Nov '06

10 Nov '06

I installed the SER pre-release along w/ all modules. The problem is that presence now does not run (it was working w/ the presence-release-10.99). The errors I get are: ---------------------------------------------------------------------------------------------------------- set_mod_param_regex: parameter <xcap_root> not found in module <rls> ser: parse error (82,20-21): Can't set module parameter set_mod_param_regex: parameter <auth_xcap_root> not found in module <pa> parse error (97,20-21): Can't set module parameter ser: parse error (186,24-25): unknown command, missing loadmodule? parse error (255,26-27): unknown command, missing loadmodule? ERROR: bad config file (4 errors) ------------------------------------------------------------------------------------------------------------- I checked the pa module code and also the rls code and the parameters auth_xcap_root and xcap_root are NOT defined !!!! The error on line 185 and 255 refer to the "Lookup_domain" function. I verified that the domain module has been compiled and included in the ser.cfrg file >From: "Greger V. Teigre" <greger(a)teigre.com> >To: Jiri Kuthan <jiri(a)iptel.org> >CC: SER developer mailing list <serdev(a)iptel.org>, serusers(a)iptel.org >Subject: Re: [Serusers] new major SER pre-release, Ottendorf,is out for >testing >Date: Tue, 07 Nov 2006 15:37:17 +0100 > >Just a bit more info on this pre-release adding to Jiri's long post (if you >can take it ;-): > >* The mentioned http://www.iptel.org/ser/doc/010whatsnew will be updated as >we go with new documentation. Any registered user on iptel.org can add to >or modify documentation and all help is welcome. If you are uncertain about >how to proceed, send me an email > >* As Jiri mentioned, any input and help is appreciated. If you want to >contribute, but don't know what to do, have a look at the to-dos page: >http://www.iptel.org/todos > >* This pre-release is, without basic documentation, a bit for the die-hard. >This is an overview of what we are working (and need help) on to make it >easier accessible: - A tar source package ready for simple update from >CVS (similar to the ONsip.org source package) > - Better "kickstart" instructions, including more details in What's new >0.10 (above link) > - Updated SER - Getting Started configuration files and updated SER - >Getting Started document > - Database migration script (contact me if you want to try out an >existing python migration script and test/improve) > >* Also, in addition to the ser.cfg and Nils recently commited ser-basic.cfg >in CVS, take a look at an example config file: >http://www.iptel.org/basic_changes_in_configuration_file_0 > >*An optimized NAT-handled config file can be found here: >http://www.iptel.org/ser/howtos/optimizing_the_use_of_rtp_proxy > >Happy testing! >g-) > >Jiri Kuthan wrote: >>Ladies and gentlemen, girls and boys, >> >>the new testing pre-release of the best SIP proxy server ever, SER, is >>out! >> >>This major pre-release, codenamed Ottendorf, includes fundamental >>improvements to the software. The improvements allow SER users to achieve >>significantly higher managability and reliability by better data mode, >>interop features, security, etc. They recollect voluminous feedback we >>have received from iptel customers and open source users. In particular, >>the new features include but are not limited to: >>- improved data model which eliminates any possible ambiguities. >>- key under-the-hood changes with impact on performance: timer subsystem >> overhaul (now fast, with fine resolution, high accuracy and >>variability), TCP processing overhaul (higher scalability) >>- key reliability changes: DNS cache and IP blacklisting >>- key interop changes: support for STUN-bis, presence server aligned to >>latest >> IETF development, sanity module for early detection of invalid messages >>- more management: management features are now available via XML-RPC >>remotely, >> as well as via an alternative binary protocol >>- more security: ratelimit module, more check types in permissions module >>- scripting features: select operator in combination with revised AVPs, >> named flags and routes, more types of routes (onsend, timer, branch) >>- applications: presence has been greatly updated to keep pace with >>development in the IETF/SIMPLE (includes asynchronous subscription >> authorization, extended PIDF); web interface includes many new >>managibility >> features (multidomain, templates and multilanguage to name some). New >> scripting flexibility allows safely for features like individual >>ringing >> timers and direct access to SIP message elements. >>- new tools: Nils's script execution tree tool >> http://lists.iptel.org/pipermail/serdev/2006-October/008124.html >> and refurbished ser_ctl >>see the following links for some additional details: >>- http://www.iptel.org/ser/doc/010whatsnew - >>http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/NEWS?rev=HEAD >> >> >>Accompanying software, SEMS and SERWEB have been greatly overhauled as >>well. >>SEMS now features improved performance (single-threaded model now), >>service >>composition via python-IVR-scripting and B2BUA, adaptive playout buffer >>for >>better voice quality, and more. SERWEB features new multilevel >>administrative >>access system, multidomain support, per-domain customization, remote >>xml-rpc >>access, multilanguage support, and more. The new command-line utility, >>SER_CTL, provides also many great improvements over the previous tool. >> >>Interop >>------- >>Shortly, we have been keeping the bar high through our participation in >>the IETF >>and SIPITs. SER implements latest interop changes from the IETF (STUN-bis, >>presence >>+ XCAP, to name the most important ones) and both new features and legacy >>features were extensively and successfully tested middle of October in >>SIPit. >> >>Next Steps >>----------- >>Keep in mind, this is a pre-release for testing purposes. It is now call >>on >>users to test the software hard and provide feedback. In the meantime, the >>codebase remains frozen and we only commit patches fixing various bugs. >>Once >>we get good confidence that Ottendorf has stabilized and is being >>adequately >>documented, we will declare the final release. No date has been determined >>yet. >>Also, we consider changing CVS to SVN. >> >>Again, and this is very important: the final release will be as good as >>the >>feedback we obtain for this pre-release. Please do spend your time sending >>solid feedback back to [serusers]. >> >> >>Roadmap >>------- >>We keep rolling. We are still debating with our generous contributors what >>is the next possible good things to work on, the topics include but are >>not limited >>to as of now: >>- documentation. >>- databases are important. LDAP and BDB, DB-API revision. >>- interop: identity, TLS revision >>- advanced scripting (scripting engine, vars returns, AVPs) >>- uncountable improvements (futex, dev/rtc, tm/refcnts, tcp fd cache, >>.....) >> >>Trivia >>-------- >>The release name Ottendorf is coming from a place in Saxonian Switzerland, >>where many iptel fellows and their friends spent a weekend during this >>Indian summer. >>http://www.iptel.org/jan/gallery/saxonian_switzerland_2006/ >>http://www.iptel.org/~andi/2006-09-22-Ottendorf/ >>http://www.iptel.org/~vlada/saxon_switzerland/index.html >>http://www.ohlmeier.de/albums/ottendorf_2006/index.html >> >> >>Acknowledgments >>--------------- >>This grand achievement is result of extremely many folks who did lot >>of hard work. Out of folks affiliated with iptel, Andrei and Jan spent >>immense effort on moving SER forward, with great support from Hallik >>(command-line tool), Michal, Miklos, Nils, Tomas, Vaclav (presence), Vlada >>(new STUN). In this context, I would like to thank to our company for the >>great support. Recently, Bogdan Pintea greatly helped to make the upcoming >>release better and more stable under sponsorship of his company, iptego. >>transnexus provided osp support. >> >>SEMS has been greatly improved thanks to Stefan and Raphael. >>Credits for serweb go to Karel. >> >>Same importantly, SER has been immensely benefitting of contributors, >>to name in alphabetic order at least the 'top-of-the-iceberg' fellows: >>Bogdan Pintea, Cesc Santa, Greg Fausak, Greger Teigre, Hendrik Scholz, >><http://tutpro.com/>Juha Heinänen, Klaus Darilion, Maxim Sobolev, Peter >>Nixon, Uli Abend. >> >>Great support on the mailing list has been provided by Greger V. Teigre, >>Java Rockx, Klaus Darilion, Zeus Ng, and more. >> >>Simply, this list is too short and incomplete to capture all the >>generous contributions that came in -- my appologies for everyone >>else I have missed. >> >> >>Warnings and Disclaimers >>------------------------ >>This is a TESTING version. We are encouraging people to give it intense >>testing and provide us with feedback, so that we can properly assess >>what it takes to declare it final. The volume and number of changes >>is big, caution is advised. >> >>All GPL warnings and disclaimers apply. >> >>This is SER, which is not the derivate software known as openser. We have >>no ideas of in what extent and timeline derivate projects follow >>(or not) SER. >> >>------------------------------------------------------------------------------- >> >>To Give it a Try >>----------------- >>warning: this is just a 'jump-start' for black-belt users. It is not a >>replacement for documentation or a detailed step-by-step installation >>guide. It assumes knowledge of operating system, SIP, and SER. >> >> >>PREPARATION >>- make sure mysql is running. In the default configuration, SER assumes it >> to be running on localhost, if this does not hold, you need to change >> ser.cfg. >>- make sure python is installed (needed for new command-line utilities) >>SER INSTALLATION FROM CVS >>- Download from CVS/HEAD using instructions at >>http://www.iptel.org/downloads >>- Compile it: make include_modules="mysql xmlrpc" all >>- Install it the default way of your administrative privileges allow to: >> make include_modules="mysql xmlrpc" install >>- Download command-line tool (see more documentation under >> >>http://cvs.berlios.de/cgi-bin/viewcvs.cgi/*checkout*/ser/serctl/README?rev=…) >> - cvs co serctl >>- Initiate database: >> ./scripts/mysql/ser_mysql.sh create >>START >>- Start it. Call: ser >>- Begin provisioning users with the new serctl (the capital word are just >>place holders) >> # ser_ctl domain add DOMAINNAME >> # ser_ctl user add USERNAME@DOMAINNAME -p PASSWORD >> # If you want to have Asserted Identity header for your user >> # - ser_attr add uid=UID asserted_id="PID" >> # If you want to have gateway support >> # - ser_db add attr_types name=gw_ip rich_type=string raw_type=2 \ >> description="The gateway IP for the default ser.cfg" >>default_flags=33 >> # - ser_attr add global gw_ip=GATEWAY-IP >>- more things you may wish to do: >> - familiarize yourself with current ser.cfg >> - send us feedback. >> >> >> >> >> >>-- >>Jiri Kuthan http://iptel.org/~jiri/ >> >>_______________________________________________ >>Serusers mailing list >>Serusers(a)lists.iptel.org >>http://lists.iptel.org/mailman/listinfo/serusers >> >> >> >_______________________________________________ >Serusers mailing list >Serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers _________________________________________________________________ Experience Live Search from your PC or mobile device today. http://www.live.com/?mkt=en-ca

2 1

[Serusers] New developer
by Gustavo Passos Tourinho 10 Nov '06

10 Nov '06

Hello There! I'm trying to develop some new functions to be used at ser.cfg. I was looking the serdev.pdf but I didn't figure out how can I integrate my new function with ser.cfg. Is there some sort of "how to develop new modules for ser"? Thanks in advanced, Tourinho

2 1

[Serusers] Problem in using ser_ctl
by Ajay Kolambekar 10 Nov '06

10 Nov '06

Hi, I have installed SER on Redhat Linux 9 machine. I want to use ser_ctl to add/view users or domains. When I give command set_ctl user show I am getting an error like ser_ctl: /root/Python-2.5/lib/python2.5/site-packages/_mysql.so: undefined symbol: mysql_set_character_set: ImportError'> Does anybody know how to solve this problem? Thanks in advance, Ajay DISCLAIMER ========== This e-mail may contain privileged and confidential information which is the property of Persistent Systems Pvt. Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Pvt. Ltd. does not accept any liability for virus infected mails.

2 2

[Serusers] new major SER pre-release, Ottendorf, is out for testing
by Jiri Kuthan 10 Nov '06

10 Nov '06

Ladies and gentlemen, girls and boys, the new testing pre-release of the best SIP proxy server ever, SER, is out! This major pre-release, codenamed Ottendorf, includes fundamental improvements to the software. The improvements allow SER users to achieve significantly higher managability and reliability by better data mode, interop features, security, etc. They recollect voluminous feedback we have received from iptel customers and open source users. In particular, the new features include but are not limited to: - improved data model which eliminates any possible ambiguities. - key under-the-hood changes with impact on performance: timer subsystem overhaul (now fast, with fine resolution, high accuracy and variability), TCP processing overhaul (higher scalability) - key reliability changes: DNS cache and IP blacklisting - key interop changes: support for STUN-bis, presence server aligned to latest IETF development, sanity module for early detection of invalid messages - more management: management features are now available via XML-RPC remotely, as well as via an alternative binary protocol - more security: ratelimit module, more check types in permissions module - scripting features: select operator in combination with revised AVPs, named flags and routes, more types of routes (onsend, timer, branch) - applications: presence has been greatly updated to keep pace with development in the IETF/SIMPLE (includes asynchronous subscription authorization, extended PIDF); web interface includes many new managibility features (multidomain, templates and multilanguage to name some). New scripting flexibility allows safely for features like individual ringing timers and direct access to SIP message elements. - new tools: Nils's script execution tree tool http://lists.iptel.org/pipermail/serdev/2006-October/008124.html and refurbished ser_ctl see the following links for some additional details: - http://www.iptel.org/ser/doc/010whatsnew - http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/NEWS?rev=HEAD Accompanying software, SEMS and SERWEB have been greatly overhauled as well. SEMS now features improved performance (single-threaded model now), service composition via python-IVR-scripting and B2BUA, adaptive playout buffer for better voice quality, and more. SERWEB features new multilevel administrative access system, multidomain support, per-domain customization, remote xml-rpc access, multilanguage support, and more. The new command-line utility, SER_CTL, provides also many great improvements over the previous tool. Interop ------- Shortly, we have been keeping the bar high through our participation in the IETF and SIPITs. SER implements latest interop changes from the IETF (STUN-bis, presence + XCAP, to name the most important ones) and both new features and legacy features were extensively and successfully tested middle of October in SIPit. Next Steps ----------- Keep in mind, this is a pre-release for testing purposes. It is now call on users to test the software hard and provide feedback. In the meantime, the codebase remains frozen and we only commit patches fixing various bugs. Once we get good confidence that Ottendorf has stabilized and is being adequately documented, we will declare the final release. No date has been determined yet. Also, we consider changing CVS to SVN. Again, and this is very important: the final release will be as good as the feedback we obtain for this pre-release. Please do spend your time sending solid feedback back to [serusers]. Roadmap ------- We keep rolling. We are still debating with our generous contributors what is the next possible good things to work on, the topics include but are not limited to as of now: - documentation. - databases are important. LDAP and BDB, DB-API revision. - interop: identity, TLS revision - advanced scripting (scripting engine, vars returns, AVPs) - uncountable improvements (futex, dev/rtc, tm/refcnts, tcp fd cache, .....) Trivia -------- The release name Ottendorf is coming from a place in Saxonian Switzerland, where many iptel fellows and their friends spent a weekend during this Indian summer. http://www.iptel.org/jan/gallery/saxonian_switzerland_2006/ http://www.iptel.org/~andi/2006-09-22-Ottendorf/ http://www.iptel.org/~vlada/saxon_switzerland/index.html http://www.ohlmeier.de/albums/ottendorf_2006/index.html Acknowledgments --------------- This grand achievement is result of extremely many folks who did lot of hard work. Out of folks affiliated with iptel, Andrei and Jan spent immense effort on moving SER forward, with great support from Hallik (command-line tool), Michal, Miklos, Nils, Tomas, Vaclav (presence), Vlada (new STUN). In this context, I would like to thank to our company for the great support. Recently, Bogdan Pintea greatly helped to make the upcoming release better and more stable under sponsorship of his company, iptego. transnexus provided osp support. SEMS has been greatly improved thanks to Stefan and Raphael. Credits for serweb go to Karel. Same importantly, SER has been immensely benefitting of contributors, to name in alphabetic order at least the 'top-of-the-iceberg' fellows: Bogdan Pintea, Cesc Santa, Greg Fausak, Greger Teigre, Hendrik Scholz, <http://tutpro.com/>Juha Heinänen, Klaus Darilion, Maxim Sobolev, Peter Nixon, Uli Abend. Great support on the mailing list has been provided by Greger V. Teigre, Java Rockx, Klaus Darilion, Zeus Ng, and more. Simply, this list is too short and incomplete to capture all the generous contributions that came in -- my appologies for everyone else I have missed. Warnings and Disclaimers ------------------------ This is a TESTING version. We are encouraging people to give it intense testing and provide us with feedback, so that we can properly assess what it takes to declare it final. The volume and number of changes is big, caution is advised. All GPL warnings and disclaimers apply. This is SER, which is not the derivate software known as openser. We have no ideas of in what extent and timeline derivate projects follow (or not) SER. ------------------------------------------------------------------------------- To Give it a Try ----------------- warning: this is just a 'jump-start' for black-belt users. It is not a replacement for documentation or a detailed step-by-step installation guide. It assumes knowledge of operating system, SIP, and SER. PREPARATION - make sure mysql is running. In the default configuration, SER assumes it to be running on localhost, if this does not hold, you need to change ser.cfg. - make sure python is installed (needed for new command-line utilities) SER INSTALLATION FROM CVS - Download from CVS/HEAD using instructions at http://www.iptel.org/downloads - Compile it: make include_modules="mysql xmlrpc" all - Install it the default way of your administrative privileges allow to: make include_modules="mysql xmlrpc" install - Download command-line tool (see more documentation under http://cvs.berlios.de/cgi-bin/viewcvs.cgi/*checkout*/ser/serctl/README?rev=…) - cvs co serctl - Initiate database: ./scripts/mysql/ser_mysql.sh create START - Start it. Call: ser - Begin provisioning users with the new serctl (the capital word are just place holders) # ser_ctl domain add DOMAINNAME # ser_ctl user add USERNAME@DOMAINNAME -p PASSWORD # If you want to have Asserted Identity header for your user # - ser_attr add uid=UID asserted_id="PID" # If you want to have gateway support # - ser_db add attr_types name=gw_ip rich_type=string raw_type=2 \ description="The gateway IP for the default ser.cfg" default_flags=33 # - ser_attr add global gw_ip=GATEWAY-IP - more things you may wish to do: - familiarize yourself with current ser.cfg - send us feedback. -- Jiri Kuthan http://iptel.org/~jiri/

6 9

[Users] auth_radius - Initializing problem
by exploiz 10 Nov '06

10 Nov '06

Hello all, I am install openSER follow (http://www.openser.org/docs/openser-radius-1.0.x.html). I have problem when run openser, below is a debug. And when remove *_radius.so the program can work. what's going wrong Thank you for all advice. BR, exploiz -------------------------------- LOG --------------------------------------------------- textops - initializing 0(0) DEBUG: init_mod: xlog 0(0) XLOG: initializing ... 0(0) DEBUG: init_mod: acc 0(0) ACC - initializing 0(0) find_export: found <load_tm> in module tm [/usr/local/lib/openser/modules/tm.so] 0(0) DEBUG: init_mod: auth 0(0) AUTH module - initializing 0(0) find_export: found <sl_send_reply> in module sl_module [/usr/local/lib/openser/modules/sl.so] 0(0) DEBUG: init_mod: auth_radius 0(0) auth_radius - Initializing 0(0) auth_radius: No `Cisco' vendor in Radius dictionary 0(0) find_export: found <bind_auth> in module auth [/usr/local/lib/openser/modules/auth.so] 0(0) ERROR: auth_radius: can't get code for the Digest-Response attribute 0(0) init_mod(): Error while initializing module auth_radius ERROR: error while initializing modules 0(0) XLOG: destroy module ... 0(0) DEBUG: tm_shutdown : start 0(0) DEBUG: unlink_timer_lists : emptying DELETE list 0(0) DEBUG: tm_shutdown : emptying hash table 0(0) DEBUG: tm_shutdown : releasing timers 0(0) DEBUG: tm_shutdown : removing semaphores 0(0) DEBUG: tm_shutdown : destroying tmcb lists 0(0) DEBUG: tm_shutdown : done 0(81840) shm_mem_destroy 0(81840) destroying the shared memory lock --------------------------------------------------------------------------- -------openser.cfg-------------------------------------------- .... loadmodule "/usr/local/lib/openser/modules/sl.so" loadmodule "/usr/local/lib/openser/modules/tm.so" loadmodule "/usr/local/lib/openser/modules/rr.so" loadmodule "/usr/local/lib/openser/modules/maxfwd.so" loadmodule "/usr/local/lib/openser/modules/avpops.so" loadmodule "/usr/local/lib/openser/modules/usrloc.so" loadmodule "/usr/local/lib/openser/modules/registrar.so" loadmodule "/usr/local/lib/openser/modules/textops.so" loadmodule "/usr/local/lib/openser/modules/xlog.so" loadmodule "/usr/local/lib/openser/modules/uri.so" loadmodule "/usr/local/lib/openser/modules/acc.so" # Uncomment this if you want digest authentication # mysql.so must be loaded ! loadmodule "/usr/local/lib/openser/modules/auth.so" loadmodule "/usr/local/lib/openser/modules/auth_radius.so" loadmodule "/usr/local/lib/openser/modules/group_radius.so" loadmodule "/usr/local/lib/openser/modules/avp_radius.so" #loadmodule "/usr/local/lib/openser/modules/auth_db.so" .... ---------------------------------------------------------------------------------------------- -- บุญรักษาทุกทั่น exploiz

3 3

Re[2]: [Users] pstn-to-openser, 403 Forbiden
by Ion Minzu 09 Nov '06

09 Nov '06

Hello Norman, thanks, Norman after I have closed the domain authorisation (proxy_authorize), everything works. It looks for me too sophisticated to use permission and domain module. I will try another method. now I want to make restrictions for voip users, I mean who has the right to make a call to pstn and who has not. someone has some ideeas? Wednesday, November 8, 2006, 2:35:34 PM, you wrote: > Hello Ion, > Perhaps the "pstn" device is not responding to the authorization > request. A SIP trace will show you if this is happening. > "ngrep -W byline port 5060" should be all you need to trace SIP messages > (if you're listening on eth1, then you might want to add "-d eth1" when > invoking ngrep). Older versions of ngrep did not have the "-W byline" > option. If this is your case, you probably should upgrade ngrep. > A possible solution to you problem might be to use the "permissions" > module and the "trusted" table. Then, instead of > (www_authorize/www_challenge or in addition to, depending on your > particular situation) you might want to use the "allow_trusted()" > command to authenticate incoming INVITEs. > Below is a little example > <snip> > if (!is_from_local() && !allow_trusted()) { > if (!proxy_authorize("","subscriber")) { > proxy_challenge("","0"); > exit; > } else if (!check_from()) { > sl_send_reply("403", "Use From=ID"); > exit; > }; > }; > </snip> > Regards, > Norm > Ion Minzu wrote: >> Hello , >> >> I have connected openser with pstn through cisco. when I make a >> call from voip network to pstn it's ok. >> but from pstn to voip I have a problem:openser answers 403 forbiden. >> in openser I do the authorisation on mysql, I have disabled authorisation on sip >> gateway: >> >> if (src_ip!=X.X.X.X) { >> if (!www_authorize("DOMAIN.COM","subscriber")) { >> www_challenge("DOMAIN.COM","0"); >> exit; >> } >> }; >> >> What is the problem? >> >> X.X.X.X is cisco >> >> U X.X.X.X:54177 -> 172.17.6.2:5060 >> INVITE sip:820022@172.17.6.2:5060 SIP/2.0..Via: SIP/2.0/UDP >> X.X.X.X:5060..From: >> <sip:022250699@X.X.X.X>;tag=1A0FBC30-1472..To: <sip:820022@172.1 >> 7.6.2>..Date: Wed, 08 Nov 2006 11:03:14 GMT..Call-ID: >> 906DA628-6E4F11DB-9034EA4F-E981BA1F@X.X.X.X..Supported: >> timer,100rel..Min-SE: 1800..Cisco-Guid >> : 2422905184-1850675675-2419190351-3917593119..User-Agent: >> Cisco-SIPGateway/IOS-12.x..Allow: INVITE, OPTIONS, BYE, CANCEL, >> ACK, PRACK, COMET, REFER, SUBS >> CRIBE, NOTIFY, INFO..CSeq: 101 INVITE..Max-Forwards: >> 6..Remote-Party-ID: >> <sip:022250699@X.X.X.X>;party=calling;screen=yes;privacy=off..Timestamp: >> 116 >> 2983794..Contact: <sip:022250699@X.X.X.X:5060>..Expires: >> 180..Allow-Events: telephone-event..Content-Type: >> application/sdp..Content-Length: 235....v= >> 0..o=CiscoSystemsSIP-GW-UserAgent 1226 5023 IN IP4 X.X.X.X..s=SIP >> Call..c=IN IP4 X.X.X.X..t=0 0..m=audio 16642 RTP/AVP 18 19..c=IN IP4 >> X.X.X.X..a=rtpmap:18 G729/8000..a=fmtp:18 >> annexb=no..a=rtpmap:19 CN/8000..a=ptime:20.. >> # >> U 172.17.6.2:5060 -> X.X.X.X:5060 >> SIP/2.0 403 Use From=ID..Via: SIP/2.0/UDP X.X.X.X:5060..From: >> <sip:022250699@X.X.X.X>;tag=1A0FBC30-1472..To: >> >> <sip:820022@172.17.6.2>;tag=329cfeaa6ded039da25ff8cbb8668bd2.13ec..Call-ID: >> 906DA628-6E4F11DB-9034EA4F-E981BA1F@X.X.X.X..CSeq: 101 >> INVITE..Server: OpenSer (1.1.0-tls (x86_64/linux))..C >> ontent-Length: 0..Warning: 392 172.17.6.2:5060 "Noisy >> feedback tells: pid=32240 req_src_ip=X.X.X.X req_src_port=54177 >> in_uri=sip:820022@172.17.6.2:5 >> 060 out_uri=sip:820022@172.17.6.2:5060 via_cnt==1".... >> # >> U X.X.X.X:54177 -> 172.17.6.2:5060 >> ACK sip:820022@172.17.6.2:5060 SIP/2.0..Via: SIP/2.0/UDP >> X.X.X.X:5060..From: >> <sip:022250699@X.X.X.X>;tag=1A0FBC30-1472..To: <sip:820022@172.17.6 >> .2>;tag=329cfeaa6ded039da25ff8cbb8668bd2.13ec..Date: Wed, 08 Nov >> 2006 11:03:14 GMT..Call-ID: >> 906DA628-6E4F11DB-9034EA4F-E981BA1F@X.X.X.X..Max-Forward >> s: 6..Content-Length: 0..CSeq: 101 ACK.... >> >> >> Best regards, >> Ion Minzu, >> Specialist Tehnologii Informationale, >> Administrator de sistem al Centrului de certificare, >> Administrator VoIP, >> I.S."Centrul de Telecomunicatii Speciale", >> tel:250-517 (office), 069501208 (mob), 382869185 (ICQ) >> mailto:ion.minzu@cts.md >> >> >> _______________________________________________ >> Users mailing list >> Users(a)openser.org >> http://openser.org/cgi-bin/mailman/listinfo/users >> >> >> -- Best regards, Ion mailto:ion.minzu@cts.md

3 2

[Users] OpenSER Summit - BoF slides
by Daniel-Constantin Mierla 09 Nov '06

09 Nov '06

Hello, the slides presented Tuesday, during BoF, are now available online: http://www.openser.org/events/2006-OpenSER-Summit/slides/ Those from the Wednesday, need to be collected in the final version and will show up there as they arrive. Also, we are collecting photos/videos and any other story about the summit, please sent them to us (team(a)openser.org) to make them available. For the pictures/videos will be good if you can make them available for download somewhere, rather than sending via email. Photo albums will be generated and uploaded these days, to be easier to browse. Briefings will be posted as well on the web site. Thanks to all participants there, many of them resisted the marathon of slides, the event lasting one more hour than VoN conference, being the ones locking up the ICC at the end of the day :-) . Cheers, Daniel

1 0

[Serusers] Problem in using ser_ctl
by Ajay Kolambekar 09 Nov '06

09 Nov '06

1 0

[Users] openser + presence module (presence.so) is not compiling
by prateek kapoor 09 Nov '06

09 Nov '06

Hi All, I have installed openser version from 1.1.0 debian package installer and it is working fine. But when I am trying to include the presence module (presence.so), it is not there. When I am trying to recompile it from source tarball I am getting a lot of dependency errors. So can anyone tell me from where I can get the 'presence.so' ? I can see a 'pa' (presence agent) module. I would also like to know what is the difference between 'pa' and 'presence' modules ? Any help will be really appreciated. Regards, Prateek --------------------------------- Everyone is raving about the all-new Yahoo! Mail beta.

2 1

[serusers]: Presence Module
by Kamal.Mann＠t-systems.com 09 Nov '06

09 Nov '06

Hi All I need to use SER as a stand alone presence server. How to install/configure ser as presence server? Any kind of related links, documents etc. Do I need some external libraries too for compiling SER code to run it as presence server or any binary package for all? Is their any proper document is already present? Thanks in anticipation Kamal Mann

2 2

← Newer
1
...
19
20
21
22
23
24
25
...
31
Older →

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 November 2006