sr-users March 2008

sr-users@lists.kamailio.org

169 participants
237 discussions

by Nuno Ribeiro

Hi all, I'm having a problem related with the "early" CANCEL's. The scenario is the following one : A PSTN call to a SIP phone. When the PSTN decides to cancel the call only a right after initiating, the PSTN will send the CANCEL message to the SER but this is discarded and not forwarded to the correct path to the SIP Phone. So what happens is that we have a ghost call.... The PSTN has already cancelled the call but the SIP phone continues to ring. The code that I have in the SER script is really simple: if(subst_uri('/^sip:(\+[0-9]+)@ 192.168.20.69.*user=phone$/sip:\1@ptinovacao.pt/i')){ record_route(); loose_route(); t_relay_to_udp("192.168.20.5", "5060"); break; } In the log file I see that: RFC3261 transaction matching failed t_lookup_request: no transaction found e2e_cancel: e2e cancel proceeding Could you help me? Thanks in advance. Best Regards, -- Nuno Ribeiro

16 years, 1 month

[OpenSER-Users] WeSIP ans Openser configurations problems

by bsb093

Hi, I am new in this area and as expected I am having real problem with setting up the Openser with WeSIP . I have installed OpenSER 1.2.0 on debian platform and download WeSIP from WeSIP website. When trying to run Openser I get an error that fifo="tmp/openser_fifo" line has parse error (in the openser.cfg). Therefore I remove this line and instead I added "modparam("mi_fifo", "fifo_name", "/tmp/openser_fifo")". Why do I get the error message if that is the same in the examples? Second, "modparam("seas", "listen_sockets", "192.168.2.100:5080");" has parse error. I can't see why the IP is correct and if I change it to localhost/127.0.0.1 I get the same error. What can be the problem in this line? Everywere I checked it is just the same. Third, when trying to run WeSIP with WeSIP/bin/startup.sh I get the following Java exceptions: -Dlog4j.configuration=file:/usr/local/src/wesip/conf/log4j.properties org.apache.catalina.startup.Bootstrap -config /usr/local/src/wesip/conf/server.xml start Catalina.start using /usr/local/src/wesip/conf/server.xml: java.lang.IllegalArgumentException: This container is not a StandardHost java.lang.IllegalArgumentException: This container is not a StandardHost at org.apache.commons.digester.Digester.createSAXException(Digester.java:2792) at org.apache.commons.digester.Digester.createSAXException(Digester.java:2818) at org.apache.commons.digester.Digester.endElement(Digester.java:1070) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633) at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:221) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:872) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1693) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242) at org.apache.commons.digester.Digester.parse(Digester.java:1572) at org.apache.catalina.startup.Catalina.start(Catalina.java:428) at org.apache.catalina.startup.Catalina.execute(Catalina.java:358) at org.apache.catalina.startup.Catalina.process(Catalina.java:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:156) Please advise. Thanks in advance Shine -- View this message in context: http://www.nabble.com/WeSIP-ans-Openser-configurations-problems-tp15826527p… Sent from the OpenSER Users Mailing List mailing list archive at Nabble.com.

16 years, 1 month

[OpenSER-Users] Problem in Installing OpenSER-1.3.x

by srinivas.banda＠wipro.com

Hi all, I am new to OpenSER, I want to install OpenSER on my Redhat Linux machine. I had downloaded OpenSER latest1.3.x. I have some doubts regarding installation of openser 1. is mysql is to be installed before installing openser?? 2. I had installed openser1.3.x with installation procedure given in the openser.org, ( I did make all) 3. if it is mandatory to have mysql running before installing openser1.3 please tell where can I get mysql compatible for redhat linux?? 4. if any body have complete step by step installation procedure and what are all pre required software is to be installed plz give me suggestion. Please give suggestions to my queries as soon as possible because it is very urgent.. Thanks in advance Regards Srinivas The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

16 years, 1 month

[Serusers] SER + Fax service

by roayu

Good day! I just brought an ATA that support Fax and I would like to know does SER able to handle the fax service as well? My environment is as the following: Fax machine A --> ATA --> SER --> ATA --> Fax machine B Is there any issue to perform the above transaction? Or is there any setting that I need to configure on SER ? Thanks. Best regards, Roa Yu

16 years, 1 month

Re: [Serusers] Variables in the Log command

by Jiri Kuthan

use xlog module for formattable logging. -jiri At 21:44 05/03/2008, Davis, Al wrote: >Content-Language: en-US >Content-Type: multipart/alternative; > boundary="_000_8F86FF097D265D4EB4D9D2F29DB00AA83F9797253DEXVMBX0152exc_" > > >Is there a way to output variables such as SIP_SRCIP and SIP_RURI to /var/log/messages using the log command? >_______________________________________________ >Serusers mailing list >Serusers(a)lists.iptel.org >http://lists.iptel.org/mailman/listinfo/serusers -- Jiri Kuthan http://iptel.org/~jiri/

16 years, 1 month

[Serusers] Variables in the Log command

by Davis, Al

Is there a way to output variables such as SIP_SRCIP and SIP_RURI to /var/log/messages using the log command?

16 years, 1 month

Re: [Serusers] [Sems] Poll on dropping unix socket interface ("unixsockctrl")

by Stefan Sayer

Hello, Raphael Coeffic wrote: > Hi Srinivas, > > this is a very good question you are bringing! I forgot to describe these > aspects. So i will try to describe the experience we gathered in the last > weeks. > > binrpcctrl: > - increases signaling performance (100% according to Stefan's measurements) this is not correct, its much more: http://lists.iptel.org/pipermail/semsdev/2008-January/002015.html The relation is about 750 cps vs 80 cps, which is ~ 9 times performance increase. > - increases flexibility (all the informations passed between SER and SEMS are > configurable). > > sipctrl: > - increases signaling performance (80% against binrpcctrl according to > Stefan's measurements) I don't know where this figure comes from, it is as well much more (I said this: http://lists.iptel.org/pipermail/semsdev/2008-February/002221.html , 1000 cps on lo on a laptop, versus a quad xeon over lan). > - reduces configuration and run-time complexity > > Concerning the stability, it is clear that the next weeks as well as the > community will show us what those new control plug-in are worth. From my > knowledge i would say that we are close to completion for both new plug-ins. you can help by trying out your application with the new plugins and report any possible issues. > > Dropping the support does not mean that we will remove it from SVN, that just > means that future version should not use it. Existing installations are not > concerned by those measures. i.e. i would say it should be part of 1.0 release, but marked as deprecated. After that release I would move for removing it, in favor of more flexibility that new control plugins provide. Stefan > > Cheers > Raphael. > > On Wednesday 05 March 2008 15:08, Srinivas Kotamarti wrote: >> Hi Raphael, >> What are the advantages of binrpcctrl and sipctrl over the unixsockctrl? >> >> Has enough testing done on them? We are currently using SEMS with SER0.9.6 >> (with unixsockctrl) and it is working OK for us. IF we move to the >> binrpcctrl or sipctrl would we get a better performance? >> >> Thanks >> >> --Srinivas >> >> -----Original Message----- >> From: sems-bounces(a)lists.iptel.org [mailto:sems-bounces@lists.iptel.org] On >> Behalf Of Raphael Coeffic Sent: Wednesday, March 05, 2008 7:00 AM >> To: sems(a)lists.iptel.org >> Cc: serusers(a)lists.iptel.org >> Subject: [Sems] Poll on dropping unix socket interface ("unixsockctrl") >> >> >> Hi *! >> >> with the emergence of the binary RPC interface for SER2 ("binrcpctrl" >> plug-in), and SEMS' own sip stack ("sipctrl" plug-in), Stefan and I believe >> that the unix socket control interface is defeated. >> >> That's why we would like to know who is in favor of dropping support for >> the unix socket interface. >> >> Cheers and happy polling! >> >> Stefan & Raphael. >> _______________________________________________ >> Sems mailing list >> Sems(a)lists.iptel.org >> http://lists.iptel.org/mailman/listinfo/sems > -- Stefan Sayer VoIP Services stefan.sayer(a)iptego.com www.iptego.com iptego GmbH Am Borsigturm 40 13507 Berlin Germany Amtsgericht Charlottenburg, HRB 101010 Geschaeftsfuehrer: Alexander Hoffmann

16 years, 2 months

[OpenSER-Users] Openser HA

by Cosimo Fadda

Hi, I want to setup two openser in a HA enviroment; So, correct me if I'm wrong, I need three IP addresses, one for each box and a shared one, My question is, I have to set the advertised_address= <shared-IP> in both openser servers? Thanks in advance, Cosimo Fadda *Ing. Cosimo Fadda System Engineer Klarya s.r.l.* ____

16 years, 2 months

Re: [Serusers] [Sems] Poll on dropping unix socket interface ("unixsockctrl")

by Srinivas Kotamarti

Hi Raphael, What are the advantages of binrpcctrl and sipctrl over the unixsockctrl? Has enough testing done on them? We are currently using SEMS with SER0.9.6 (with unixsockctrl) and it is working OK for us. IF we move to the binrpcctrl or sipctrl would we get a better performance? Thanks --Srinivas -----Original Message----- From: sems-bounces(a)lists.iptel.org [mailto:sems-bounces@lists.iptel.org] On Behalf Of Raphael Coeffic Sent: Wednesday, March 05, 2008 7:00 AM To: sems(a)lists.iptel.org Cc: serusers(a)lists.iptel.org Subject: [Sems] Poll on dropping unix socket interface ("unixsockctrl") Hi *! with the emergence of the binary RPC interface for SER2 ("binrcpctrl" plug-in), and SEMS' own sip stack ("sipctrl" plug-in), Stefan and I believe that the unix socket control interface is defeated. That's why we would like to know who is in favor of dropping support for the unix socket interface. Cheers and happy polling! Stefan & Raphael. _______________________________________________ Sems mailing list Sems(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/sems

16 years, 2 months

[OpenSER-Users] Why every body return "404 Not Found" instead of "480 Not Available"?

by Iñaki Baz Castillo

Hi, after a large discussion in sip-implementros maillist I realize that a proxy/location server shouldn't reply "404" if a callee DOES exist but it's not registered in that moment. In fact: 480 Temporarily Unavailable [...] This status is also returned by a redirect or proxy server that recognizes the user identified by the Request-URI, but does not currently have a valid forwarding location for that user. 404 Not Found The server has definitive information that the user does not exist at the domain specified in the Request-URI. [...] Why then every body suggest to reply "404 Not Found" when "lookup(location)" returns -1? For example, the "registrar" module doc suggests it: Example 1-22. lookup usage lookup("location"); switch ($?) { case -1: case -3: sl_send_reply("404", "Not Found"); exit; case -2: sl_send_reply("405", "Not Found"); exit; }; Best regards. -- Iñaki Baz Castillo ibc(a)in.ilimit.es

16 years, 2 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 2008