sr-users March 2006

sr-users@lists.kamailio.org

223 participants
505 discussions

[Users] OT - Cisco IP Phone and PC in diferent VLANs (with 802.1x)

by Joao Pereira

Hello to all I would like to know If some of you have already configured an Cisco IP Phone (7940 or 7960) to work in a different VLAN than the PC that is connected through the phone switch? I know that this can be done with the Skinny firmware, but I dont if it works with the SIP firmware. The Cisco technical staff told me that these phones dont support 802.1x but can work as pass-through. This way I can still use the PCs with 802.1x and the phones in the same Ethernet plug. Did someone made it with the Cisco IP phones? What configuration do I need in the phones and in the switch? Thanks Joao Pereira

18 years, 8 months

[Users] NEW Functionality: pseudo-variables in authentication modules

by Bogdan-Andrei Iancu

Hi, the devel branch support the usage of pseudo variables for the "realm" parameter of all auth functions - www/proxy-challenge/authorize. This allow dynamic injection of realm name from outside the SIP message. This feature was originally requested by Martin Koenig <martin.koenig(a)toplink.de>. For details, see: http://www.openser.org/pipermail/devel/2006-January/001815.html CVS and online docs are updated. regards, bogdan

18 years, 8 months

[Users] MySQL5.0.18 + OpenSER1.0.1 - Looking on HowTo...

by Edson

In a previous e-mail I described that I only had success on compiling OpenSER 1.0.0-tls against MySQL 4.1.13. Not against MySQL 5.0.18. With the release of 1.0.1, I return to give a try, but didn't have success. Looking at Google, I find the kind of problem on SER-DEV discussion list (http://mail.iptel.org/pipermail/serdev/2005-April/004343.html), but it didn't work for me, so I move looking. Than I find a bug-report on MySQL (number 13159 - http://bugs.mysql.com/bug.php?id=13159) and try they last advise: include '-fPIC' on /usr/lib/rpm/rpmrc and rebuild MySQL RPMs. After that the compilation finished well, as the installation. The problem now is on module load. I got this message complaining on a 'floor' reference: 0(19939) ERROR: load_module: could not open module </usr/lib/openser/modules/mysql.so>: /usr/lib/openser/modules/mysql.so: undefined symbol: floor I'm running out of ideas.. :'-( Has anybody got to install OpenSER on a Xeon machine with MySQL 5.0.18 support? Any help would be appreciated. Edson.

18 years, 8 months

[Users] pseudo-variables notation update

by Daniel-Constantin Mierla

Hello, in order to allow names with different length, the pseudo-variables notation is similar with the one in make. You can enclose the name in between '(' and ')', e.g. $ru is the same with $(ru). This comes with the support of registering new pseudo-variables dynamically from modules. As an example, tm module exports $T_branch_idx which refers to the branch index for which is executed the branch_route[]. In case when parenthesis are not used, the name of the pseudo variable is considered to end at the first character which is not digit, letter, "." or "_". Also, the notation for avp names has changed to avoid confusions (see:http://openser.org/pipermail/devel/2006-February/001943.html ). Now the following notation must be used: - $avp(s:avp_name) - refers to the avp having the string name 'avp_string' - $avp(i:avp_id) - refers to the avp having the integer id 'avp_id' - $avp(avp_alias) - refers to the avp defined by the alias 'avp_alias' Cheers, Daniel

18 years, 8 months

[Serusers] SER Manual

by Marcio Sousa

Hi, Where can I find some manual for SER wich can explain how to work with SER srcipts? Thnks.

18 years, 8 months

RE: [Serusers] Saving historical registration information

by Vitaly Nikolaev

Or to use exec command that will get REGISTER as stdin, parse it and save... if you do not have thousands of customers which register every 40 sec then it should work though it not a nice solution, I agree, just easiest to do :) using avpops you can only do that for customer who really wants it. -----Original Message----- From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Dr Rodney G. McDuff Sent: Wednesday, March 01, 2006 6:40 AM To: serusers Subject: Re: [Serusers] Saving historical registration information Jan Janak wrote: > Unfortunately this is not possible without usrloc module modifications. > Use a database backend that has triggers. When a new entry is added to the location table write the record somewhere else. > Jan. > > Alistair Cunningham wrote: > >> We've been asked by a customer to keep the last registration >> information, even after expiry. >> >> They want to be able to look at the database and see where and when a >> phone last registered from, even if it was months ago. Only the last >> registration is important; they don't care about older ones. >> >> This could be done using various methods such as a trigger in the >> database to update another table any time location is written to, but >> this is ugly. >> >> Does any one know of a simple way to do it, preferably in ser.cfg? >> >> > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org > http://lists.iptel.org/mailman/listinfo/serusers > -- Dr. Rodney G. McDuff |Ex ignorantia ad sapientiam Manager, Strategic Technologies Group| Ex luce ad tenebras Information Technology Services | The University of Queensland | EMAIL: mcduff(a)its.uq.edu.au | TELEPHONE: +61 7 3365 8220 | _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

18 years, 8 months

[Serusers] CFP: Third VoIP Security Workshop, Deadline extended

by Sven Ehlert

Third Annual VoIP Security Workshop In Cooperation with ACM SIGCOMM Berlin, Germany 01, 02 June 2006 www.iptel.org/voipsecurity Submission Deadline: 15.03.06 This security workshop is the third following successful events in Dallas 2004 and Washington 2005. The workshop addresses the challenges, advanced technologies and regulations for providing secure VoIP services in the Internet as well as in third generation networks. The 2006 workshop will extend the scope of VoIP security to IMS services and present the latest advances in denial of service and SPIT detection and protection mechanisms. The format of the workshop is based on two-day single-track sessions, with presentations of invited and regular papers from academia and industry. The papers solicited in the Third VoIP Security workshop cover a variety of topics including but not limited to: * Intrusion and anomaly detection of VoIP and IMS systems * SPIT/SPIM detection and prevention * Threat and vulnerability analyses of VoIP and IMS systems * Regulatory aspects of VoIP and IMS communication * Securing Peer-to-peer systems * Securing service creation environments * Privacy and anonymity * Monitoring and testing tools for VoIP and IMS infrastructures * Security of VoIP supporting systems such as AAA and ENUM * Support of lawful interception and securing emergency services in VoIP and IMS services * High availability solutions for VoIP and IMS systems The Third VoIP Security workshop is a two day workshop with a special session of invited papers from industry and government. The program committee will referee all papers, and accepted papers will be published in the conference proceedings Important Dates: ======================= * Full paper submission deadline: March 15, 2006 * Notification of acceptance: April 10, 2006 * Camera ready submission: May 01, 2006 General Chair: ======================= Radu Popescu-Zeletin Fraunhofer Fokus Program Chairs: ======================= Dorgham Sisalem Tekelec Ram Dantu University of North Texas Henning Schulzrinne Columbia University Local Organization Chair: ======================= Sven Ehlert Fraunhofer Fokus Technical Program Committee ======================= Ralf Ackermann TU Darmstadt Hossam Afifi INT Evry Elisa Bertino Purdue University George Carle Tübingen University Jasson Casey Alcatel Ram Dantu University of North Texas Sven Ehlert Fraunhofer Fokus Sonia Fahmy Purdue University Dipak Ghosal University of California Davis Günter Müller University of Freiburg Saverio Niccolini NEC Labs Europe Jörg Ott Helsinki University of Technology Ozgur Gurleyen Vodafone Basavaraj Patil Nokia Neeli Rashmi Prasad University of Aalborg Pradeep Samudra Samsung Peter Schoo DoCoMo Euro-Labs Henning Schulzrinne Columbia University Dorgham Sisalem Tekelec Jeff Smith DHS Burkhard Stiller University of Zurich and ETH Zurich Duminda Wijesekeara George Mason University

18 years, 8 months

[Serusers] How to remove Contact HF in 200 reply for REGISTER

by Arek Bekiersz

Hi, How to disable sending Contact HF in OK send to a successful (i.e. authenticated) REGISTER request? Just use remove_hf() from textops or there is other option? I've got stupid UA that behaves badly when working behind NAT. First it sends REGISTER without anything (no Contact, Expires). On successful authentication SER responds 200 OK with Contact HF, set to public IP, exactly how SER sees UA behind NAT (like some_IP:61001). Then the stupid UA sends another REGISTER message, this time with Contact and Via HF set to this public value (i.e. some_IP:61001). It spoils my nathelper/rtpproxy detection of devices behind NAT. Of course I can enable it by regexp on User-Agent HF, but his is not an option, as plenty of those UAs runs not behind NAT. -- Regards, Arek Bekiersz

18 years, 8 months

[Users] openser & sems memory error

by Ibrahim TUNALI

Hi, i installed openser (1.0 stable) and sems (0.9 stable). I recive "ERROR:tm:write_to_fifo: writev failed: Cannot allocate memory" error when openser send request to sems voice mail. Is it compile error or do you have any solution for this. regards openser voicemail seciton; -------------------------- # switch to stateful mode: if (!t_newtran()){ sl_send_reply("500","could not create transaction"); return; }; # prevent timeout on the other side: t_reply("100","Trying - just wait a minute !"); # actively absorb ACKs if (method == "ACK") { t_relay(); return; } if (method=="INVITE"){ # no service number, redirect to voicemail. # do not forget to load AVPs so that voicemail gets the # callee's email address. avp_db_load("$ruri","i:34/$email_scheme"); if(!t_write_req("/tmp/am_fifo","voicemail/vm_email")) { t_reply("500","error contacting sems"); }; return; } else if (method=="BYE" || method=="CANCEL") { # Sems should already know which plug-in is handling that # call. "bye" is no plug-in name. It is a reserved name which # tells Sems to terminate the call. if(!t_write_req("/tmp/am_fifo","bye")) { t_reply("500","error contacting sems"); }; }; openser log; ------------ Feb 23 17:18:17 voip /usr/sbin/openser[28398]: ERROR:tm:write_to_fifo: writev failed: Cannot allocate memory Feb 23 17:18:17 voip /usr/sbin/openser[28398]: ERROR:tm:t_write_req: write_to_fifo failed Feb 23 17:18:17 voip /usr/sbin/openser[28396]: Warning: sl_send_reply: I won't send a reply for ACK!! Feb 23 17:18:18 voip /usr/sbin/openser[28392]: Warning: sl_send_reply: I won't send a reply for ACK!! Feb 23 17:18:20 voip /usr/sbin/openser[28396]: Warning: sl_send_reply: I won't send a reply for ACK!! Feb 23 17:18:24 voip /usr/sbin/openser[28398]: Warning: sl_send_reply: I won't send a reply for ACK!! Feb 23 17:18:28 voip /usr/sbin/openser[28394]: Warning: sl_send_reply: I won't send a reply for ACK!! Feb 23 17:18:32 voip /usr/sbin/openser[28398]: Warning: sl_send_reply: I won't send a reply for ACK!! Feb 23 17:18:36 voip /usr/sbin/openser[28394]: Warning: sl_send_reply: I won't send a reply for ACK!! Feb 23 17:18:40 voip /usr/sbin/openser[28398]: Warning: sl_send_reply: I won't send a reply for ACK!! Feb 23 17:18:44 voip /usr/sbin/openser[28394]: Warning: sl_send_reply: I won't send a reply for ACK!! sems log; ------------ Feb 23 17:19:45 voip Sems[28477]: Error: (AmUtils.cpp)(str2i)(147): str2i: unexpected char s in ser Feb 23 17:19:45 voip Sems[28477]: Error: (AmUtils.cpp)(str2i)(147): str2i: unexpected char s in ser Feb 23 17:19:45 voip Sems[28480]: Debug: (sems.cpp)(main)(386): Loading application plug-ins Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(load)(87): loading /usr/lib/sems/plug-in/apps/announcement.so ... Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(loadAppPlugIn)(281): application 'announcement' loaded. Feb 23 17:19:45 voip Sems[28480]: Debug: (SemsConfiguration.cpp)(reloadModuleConfig)(70): using inline configuration for module announcement Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(load)(87): loading /usr/lib/sems/plug-in/apps/bot.so ... Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(loadAppPlugIn)(281): application 'bot' loaded. Feb 23 17:19:45 voip Sems[28480]: Debug: (AmServer.cpp)(registerFct)(401): AmUnServer::registerFct: function 'bot_start' has been registered. Feb 23 17:19:45 voip Sems[28480]: Debug: (AmServer.cpp)(registerFct)(208): AmFifoServer::registerFct: function 'bot_start' has been registered. Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(load)(87): loading /usr/lib/sems/plug-in/apps/conference.so ... Feb 23 17:19:45 voip Sems[28482]: Debug: (AmThread.cpp)(_start)(63): Thread 28482 is starting. Feb 23 17:19:45 voip Sems[28480]: Debug: (AmThread.cpp)(start)(85): Thread 28482 is just created. Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(loadAppPlugIn)(281): application 'conference' loaded. Feb 23 17:19:45 voip Sems[28480]: Debug: (SemsConfiguration.cpp)(reloadModuleConfig)(70): using inline configuration for module conference Feb 23 17:19:45 voip Sems[28480]: Warning: (Conference.cpp)(onLoad)(77): no join_sound specified in configuration Feb 23 17:19:45 voip Sems[28480]: Warning: (Conference.cpp)(onLoad)(78): file for module conference. Feb 23 17:19:45 voip Sems[28480]: Warning: (Conference.cpp)(onLoad)(84): no drop_sound specified in configuration Feb 23 17:19:45 voip Sems[28480]: Warning: (Conference.cpp)(onLoad)(85): file for module conference. Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(load)(87): loading /usr/lib/sems/plug-in/apps/echo.so ... Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(loadAppPlugIn)(281): application 'echo' loaded. Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(load)(87): loading /usr/lib/sems/plug-in/apps/isdngw.so ... Feb 23 17:19:45 voip Sems[28480]: Info: (IsdnConfiguration.cpp)(reload)(91): isdngw version 0.2 loading (supported backends: isdn4linux) ... Feb 23 17:19:45 voip Sems[28480]: Warning: (SemsConfiguration.cpp)(reloadModuleConfig)(66): no configuration found for module isdngw, maybe you want to specify config.isdngw in config file. Feb 23 17:19:45 voip Sems[28480]: Info: (IsdnGatewayFactory.cpp)(IsdnGatewayFactory)(81): isdngw: isdn4linux support disabled in configuration Feb 23 17:19:45 voip Sems[28480]: Info: (IsdnGatewayFactory.cpp)(IsdnGatewayFactory)(148): isdngw initialization successful. Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(loadAppPlugIn)(281): application 'isdngw' loaded. Feb 23 17:19:45 voip Sems[28480]: Debug: (IsdnGatewayFactory.cpp)(onLoad)(199): registering fifo function isdninfo for web access... Feb 23 17:19:45 voip Sems[28480]: Debug: (AmServer.cpp)(registerFct)(208): AmFifoServer::registerFct: function 'isdninfo' has been registered. Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(load)(87): loading /usr/lib/sems/plug-in/apps/number_reader.so ... Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(loadAppPlugIn)(281): application 'number_reader' loaded. Feb 23 17:19:45 voip Sems[28480]: Debug: (SemsConfiguration.cpp)(reloadModuleConfig)(70): using inline configuration for module number_reader Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(load)(87): loading /usr/lib/sems/plug-in/apps/voicemail.so ... Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(loadAppPlugIn)(281): application 'voicemail' loaded. Feb 23 17:19:45 voip Sems[28480]: Debug: (SemsConfiguration.cpp)(reloadModuleConfig)(70): using inline configuration for module voicemail Feb 23 17:19:45 voip Sems[28480]: Debug: (AnswerMachine.cpp)(loadEmailTemplates)(103): loading /etc/sems//default.template ... Feb 23 17:19:45 voip Sems[28480]: Debug: (sems.cpp)(main)(390): Loading audio plug-ins Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(load)(87): loading /usr/lib/sems/plug-in/audio/gsm.so ... Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(loadAudioPlugIn)(218): codec id 3 inserted Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(loadAudioPlugIn)(233): payload 'GSM'inserted with id 3 Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(load)(87): loading /usr/lib/sems/plug-in/audio/ilbc.so ... Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(loadAudioPlugIn)(218): codec id 4 inserted Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(loadAudioPlugIn)(237): payload 'iLBC'inserted with id 96 Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(loadAudioPlugIn)(257): file format iLBC inserted Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(load)(87): loading /usr/lib/sems/plug-in/audio/speex.so ... Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(loadAudioPlugIn)(218): codec id 6 inserted Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(loadAudioPlugIn)(237): payload 'speex'inserted with id 96 Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(load)(87): loading /usr/lib/sems/plug-in/audio/wav.so ... Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(loadAudioPlugIn)(218): codec id 1 inserted Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(loadAudioPlugIn)(218): codec id 2 inserted Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(loadAudioPlugIn)(233): payload 'PCMU'inserted with id 0 Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(loadAudioPlugIn)(233): payload 'PCMA'inserted with id 8 Feb 23 17:19:45 voip Sems[28480]: Debug: (AmPlugIn.cpp)(loadAudioPlugIn)(257): file format Wav inserted Feb 23 17:19:45 voip Sems[28480]: Debug: (sems.cpp)(main)(394): Starting session container Feb 23 17:19:45 voip Sems[28486]: Debug: (AmThread.cpp)(_start)(63): Thread 28486 is starting. Feb 23 17:19:45 voip Sems[28480]: Debug: (AmThread.cpp)(start)(85): Thread 28486 is just created. Feb 23 17:19:45 voip Sems[28480]: Debug: (sems.cpp)(main)(397): Starting mailer Feb 23 17:19:45 voip Sems[28480]: Debug: (AmThread.cpp)(start)(85): Thread 0 is just created. Feb 23 17:19:45 voip Sems[28480]: Debug: (sems.cpp)(main)(400): Starting RTP scheduler Feb 23 17:19:45 voip Sems[28480]: Debug: (AmThread.cpp)(start)(85): Thread 0 is just created. Feb 23 17:19:45 voip Sems[28480]: Debug: (sems.cpp)(main)(403): Starting ICMP watcher Feb 23 17:19:45 voip Sems[28480]: Debug: (AmThread.cpp)(start)(85): Thread 0 is just created. Feb 23 17:19:45 voip Sems[28480]: Debug: (AmThread.cpp)(start)(85): Thread 0 is just created. Feb 23 17:19:45 voip Sems[28480]: Info: (AmServer.cpp)(run)(147): FIFO server started Feb 23 17:19:45 voip Sems[28487]: Debug: (AmThread.cpp)(_start)(63): Thread 28487 is starting. Feb 23 17:19:45 voip Sems[28488]: Debug: (AmThread.cpp)(_start)(63): Thread 28488 is starting. Feb 23 17:19:45 voip Sems[28489]: Debug: (AmThread.cpp)(_start)(63): Thread 28489 is starting. Feb 23 17:19:45 voip Sems[28489]: Error: (AmIcmpWatcher.cpp)(run)(47): ICMP Watcher: could not create RAW socket: Operation not permitted Feb 23 17:19:45 voip Sems[28489]: Error: (AmIcmpWatcher.cpp)(run)(48): ICMP Watcher: try to run SEMS as root or suid. Feb 23 17:19:45 voip Sems[28489]: Debug: (AmThread.cpp)(_start)(68): Thread 28489 is ending. Feb 23 17:19:45 voip Sems[28490]: Debug: (AmThread.cpp)(_start)(63): Thread 28490 is starting. Feb 23 17:19:45 voip Sems[28490]: Info: (AmServer.cpp)(run)(321): Unix socket server started

18 years, 8 months

[Serusers] Proposal for new features

by Arek Bekiersz

Hi, As my current work may be interesting for the rest, I wonder if you will find those new features useful. Every opinion is appreciated. Some time ago I commited a small 'ldap' module, all-in-one. As there was some (small :-) ) feedback from people using this module, I propose to split it into following modules: 1) auth_ldap: set of authentication routines, working with standard or user-defined Ldap schemas 2) group_ldap: group membership module based on Ldap backend 3) uri_ldap: uri mangling module, based on ldap backend 4) avp_ldap: (new) module for operating on AV-pairs from Ldap, working with both user-defined or standard dbase schemas Later, it is possible to write small SER 'soap' modules, using one of freely available C/C++ soap libraries. Those modules will perform various tasks: 5) soap_ipdr: module for reporting service usage information (billing) in XML, to be used by external billing systems. Information will include all call attempts (also failed ones like CC,CAD,UCN,UCI and possibly CID completion codes from IPDR's VoIP service definition). It will return following XML documents (using SOAP as transport): * IPDRDoc - usage for specific user (user@domain) * IPDRSettlementDoc - usage for domain NOTE: that using IPDRSettlementDoc for domain is based on model where our cooperants have one virtual SIP domain. it is then easiest way to make settlement using IPDRSettlementDoc for one domain. 6) soap_parlayx: Such module would act as a gateway between SER and external Parlay X Web Services software. When called, this module will analyze SIP request and forward it to external Parlay X software. That software will fulfill request and return ReturnValue, with specific Action. Then SER soap_parlayx module will perform desired action on SIP request. More on Parlay X Web services v.2.0 can be found at: http://www.parlay.org/en/specifications/ NOTE: This behaviour mimics a hypothetic SIP-CGI gateway, but this time it is a SIP-SOAP gateway. EXAMPLE: could be the HandleBusy operation from "Part 3: Call Notification" of Parlay X Web services: 1. SIP encounters "486 Busy" situation 2. SER Script writer calls parlayx_handle(HandleBusy) function from soap_parlayx module 3. soap_parlayx module calls external software, sending handleBusyRequest, containing CallingParty, CalledParty 4. external software returns handleBusyResponse with Action structure, containing ActionToPerform (like 'route' on not route), RoutingAddress, Charging (charge for using of service) 5. SER soap_parlayx module modifies SIP request and forwards it to voicemail_SIP location. In addition it stores relevant info in IPDR data recorder for later use. External Parlay X software will be basically a SOAP engine, it can be written in any language. Unlike a soap_parlayx module itself, that engine will not be a part of SER. 7) SIP SOAP initiative Seems that IP world is slowly evolving in direction of service enabled architecture, usually based on SOAP/UDDI standards. For this reason maybe it is worth to initiate work on SIP SOAP draft standard? It would basically mimic existing IETF SIP CGI draft standard, but with far greater opportunities for creating new services, that SOAP standard brings. It will beautifuly fulfil current work in progress in my company and an European project, codename VISP (Virtual Internet Service Provider), that we are coordinator of. Project is focusing on enabling smooth company-to-company interoperability in mutual creation of new services in fast changing IP world. Including VoIP. More information can be found on Web site: http://www.visp-project.org/ -- Regards, Arek Bekiersz

18 years, 8 months

Jump to page:

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 2006