sr-users

sr-users@lists.kamailio.org

36 participants
37545 discussions

[Serusers] NAT Solution
by Asep Saifudin 06 Sep '06

06 Sep '06

Hi, Does anyone can help me to choose best NAT solution for SER/OpenSER ?NatHelper or Mediaproxy ? And if they compare with STUN, TURN, ICE technology Nathelper or Mediaproxy better than them ? My target is I want my SIP Server can pass all NAT/Firewall just like SkyPE which hard to be block by firewall and can pass all NAT system. ~Asep

2 1

[Serusers] SER not responding
by Henry Duan 06 Sep '06

06 Sep '06

hi, I'm new to SER. I downloaded SER0.9.6 source to my local Fedora Core 5. I run make all and make prefix=/ install, and then set SIPDOMAIN, and run ser. However it didn't respond with incomging Registration(it showed incoming Registration from Ethereal). (I used default ser.cfg). Can anybody tell me what's the problem, or how to debug? Thanks so much! Henry

3 2

[Users] OSS on openSER and Redriect .
by raviprakash sunkara 06 Sep '06

06 Sep '06

Hi Users, Can any one tell about OSS ( Operation Support System) on openSER, Why we need ? But i think to reduce the load balance on openSER server, Suppose is I use 3 OSS's on SIP server. Sip users should also insert in to 3 OSS sip. And other doubt is ? Suppose if we using the redirect , that forwording into other openser system, When openSER redirect to other openSER, the user should also insert, But i think that .... OSS and redirect on openSER are the same. Please for me in English, I know its naughty questioin, please excuse me ! -- -- Thanks and Regards with cheers Sunkara Ravi Prakash (Voip Developer) Hyperion Technology www.hyperion-tech.com +91-9985077535

1 0

[Serusers] Free DNS Service
by Tracy Lofton 06 Sep '06

06 Sep '06

Hi All, I am new to OpenSER/SER but have been receiving quite a bit of help and would like to express my gratitude by letting you all know of the FREE DNS Service that I am offering to the Internet Community. Go to http://www.t4tm.net to find out more, signup and enjoy the benefits. Tracy _________________________________________________________________ Get the new Windows Live Messenger! http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=…

1 0

[Serusers] Preregistering a sip address?
by Ignacio Mas Ivars 06 Sep '06

06 Sep '06

Hi all! I have just started using the SIP Express Router and I am looking for a way to have a user preregistered when the router starts. Is there any way to configure that user1 should be registered by default at an IP address without needing to send the registration? I guess it will have to do with messing a bit with the routing engine, but I don't dare to touch it so far and I don't know how to do it. Any help would be very much appreciated! Thanks very much for any help! /Nacho --- ,,, (o o) --ooO--(_)---Ooo----------- Three may keep a secret, if two of them are dead.- --oo0--------0oo-----------

2 1

[Serusers] Free DNS Service
by Tracy Lofton 06 Sep '06

06 Sep '06

Hi All, I am new to SER/OpenSER and I have received much help and in return, I am offering free Dynamic DNS services to whoever is interested. To find out more go to http://www.t4tm.net, signup and enjoy the benefits. Tracy _________________________________________________________________ Got something to buy, sell or swap? Try Windows Live Expo ttp://clk.atdmt.com/MSN/go/msnnkwex0010000001msn/direct/01/?href=http://exp…

1 0

[Serusers] delay to write things in DB when using serctl
by Ricardo Carvalho 06 Sep '06

06 Sep '06

When I add with serctl some alias to the DB, only after some time it appears written in the aliases table of DB. How can I force that to be simultaneously written in DB? Any parameter I have to tune in ser.cfg? Regards, Ricardo.

2 1

[Users] Re: Request for discussion: t_relay() internal error processing
by Mark Kent 05 Sep '06

05 Sep '06

>> 2) t_relay will return several error codes: >> -1 = no transaction created -> need to use sl_* functions >> -2 = transaction created, relay failed -> may destroy If I understand this correctly, the difference between these two return codes really has to do with who it is that cares about it... -2 relates to this exact call, at this exact moment, chances are the very next call the openser box handles will be OK. It looks to me like -1 means serious trouble, for the entire call switching platform. It sounds like it could happen because of a resource shortage (memory), possibly because of a bug in openser, or a bug in the openser.cfg. If you get -1 once, then the chances that you'll get the same code on the next call are very high. Let's say we've run out of memory. Then, what tools are available at the openser.cfg script level that can handle this? Is there a way to force some internal garbage collection? Or to do a warm-restart (e.g., trash all transactions, but not registrations)? My point here is this: if I'm right about -1 meaning serious trouble that is likely to mean serious problems from now on, then this is a more general problem than just t_relay, and much bigger than just handling this one call or a call to one particular neighbour. It's true that the application may halt and catch fire, but there are plenty of errors that are catchable by openser and the larger question seems to be: what do we do then? If there were script-level tools that could be used to try to manage the failure, possibly clean up (in a large way) and try to keep going, then maybe we should have openser_failure route blocks that the user can register with openser to handle various errors. Thanks, -mark

2 1

[Users] Request for discussion: t_relay() internal error processing
by Bogdan-Andrei Iancu 05 Sep '06

05 Sep '06

Hi all, there are some topics largely discussed lately on the mailing list; in order to fix them problems first we need to find a solution for logical point of view - and here I think that several opinions are better than one :) In order to have failover based on serial forking, it is mandatory to be able to detect from script if the initial t_relay() fails. The problem is that now t_relay() masks any error by internally generating an error SIP reply. Of course, it can be internal errors (like lack of memory), msg errors (parse errors) or transport errors (DNS failed, send/connect failed, etc). Now, disabling the auto replying in case of error is not a problem. The problem is how to handle the errors from the script; two make distinction between the error classes a listed above will not be the purpose of this email ( I will open another one for this ;) ). What is important here is to be able to properly resume from the point were the error popped up. What I mean is: the t_relay() function builds the transaction and sends the requests. If the error occurred during transaction creation, from script, you will had to use only stateless functions to send err. replies. If the transaction was already created and the error popped up during relaying stage, you will need from the script to take care of the transaction and either destroy it, either reply it. Based on this, here is what I suggest: 1) have a new param for disabling the auto reply in t_relay() 2) t_relay will return several error codes: -1 = no transaction created -> need to use sl_* functions -2 = transaction created, relay failed -> may destroy transaction, reply via TM with error, trigger failover. any comments on this ? regards, bogdan

4 4

[Users] mediaproxy error
by Richard Z 05 Sep '06

05 Sep '06

Hi, I tried the lateset mediaproxy. When starting, got these errors and dispatcher won't start, /var/log/syslog:Sep 5 10:45:57 sip-1 proxydispatcher[4227]: File "/usr/local/mediaproxy/proxydispatcher.py", line 65, in ? /var/log/syslog:Sep 5 10:45:57 sip-1 proxydispatcher[4227]: File "/usr/local/mediaproxy/modules/dispatcher.py", line 39, in ? /var/log/syslog:Sep 5 10:45:57 sip-1 proxydispatcher[4227]: File "/usr/local/mediaproxy/modules/accounting.py", line 14, in ? /var/log/syslog:Sep 5 10:45:57 sip-1 proxydispatcher[4227]: File "/usr/local/mediaproxy/modules/mysql.py", line 8, in ? #ls /usr/local/mediaproxy/modules/ accounting.py daemon.py dispatcher.py mysql.py request.py serialize.py version.pyc accounting.pyc daemon.pyc dispatcher.pyc mysql.pyc request.pyc utilities.py configuration.py datatypes.py external options.py rtphandler.py utilities.pyc configuration.pyc datatypes.pyc formatting.py options.pyc rtphandler.pyc version.py Any suggestion? Thanks, Richard

1 0

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