Sorry to bother you but I'm getting One Way Audio for some of my customers while when I was using OpenSIPS everything was OK...The issue behind that is the rtp proxy....The rtp proxy is not fully forced for all nat types or for all users...I need you please to have a look to my route defined under kamailio.cfg and let me know if I did something wrong:
On Mon, Dec 27, 2010 at 9:43 PM, michel freiha <michofr@gmail.com> wrote:
Thanks Daniel for help...Everything seems OK now...
Regard
On Fri, Dec 24, 2010 at 12:07 PM, Daniel-Constantin Mierla <miconda@gmail.com> wrote:s
Hello,
On 12/23/10 8:29 PM, michel freiha wrote:
Daniel,
The crash has been fixed...It was a database issue...
good to know. Anything specific you can tell that may help in the
future to identify similar cases?
Now I have another issue...After some time of run
we are getting a message "too many hopes" on dialers like x-Lite
while if we use IP address to register to Kamailio, everything
works fine
Any tips?
Add:
alias=yoursipdomain
in configuration file. In this way you tell kamailio to consider the
sip domain as local domain. At startup, kamailio does reverse dns
query to discover hostnames, but it might not be returned, ending up
in a loop, resulting in too many hops.
Cheers,
Daniel
Regards
Dear
On Tue, Dec 14, 2010 at 12:48 PM,
Daniel-Constantin Mierla <miconda@gmail.com>
wrote:
Hello,
On 12/13/10 3:48 PM, michel freiha wrote:
Hello Daniel,
We are not facing any database problem even we are
not using DNS anywhere in Kamailio config...The only
thing is that the debug level is 2 and syslog was
not configured asynchronous...Do you think if we
configure it as asynchronous, our issue will be
solved?
debug=2 should be that verbose to influence the
performances in this way. Anyhow is good to have syslog
asynchonous. You can start with log_stderror=yes to see if
there is any improvement -- in this way you know whether
is an logging speed issue or not.
The solution to identify which piece of config is slow is
to use benchmark module.
Cheers,
Daniel
Regards
On Mon, Dec 13, 2010 at
1:08 PM, Daniel-Constantin Mierla <miconda@gmail.com>
wrote:
Hello,
On 12/10/10 4:15 PM, michel freiha wrote:
Hello Sir,
The crash issue has been successfully fixed
after using GIT for the version 3.1.0.
thanks for reporting back.
Now
we have another problem..>When the number
of registered users exceeded 2500 concurrent
registered users, the kamailio stuck and
each call will take up to 1 minute to be
established
Any comment on that?
Do you have high debug level? If yes, is your
syslog configured asynchronously?
Other than that, you can use benchmark module to
spot which of your config actions takes so long
to execute. Normally, such cases can happen when
you have queries to slow database or dns
servers.
Cheers,
Daniel
--
Daniel-Constantin Mierla
Kamailio (OpenSER) Advanced Training
Jan 24-26, 2011, Irvine, CA, USA http://www.asipto.com
--
Daniel-Constantin Mierla
Kamailio (OpenSER) Advanced Training
Jan 24-26, 2011, Irvine, CA, USA
http://www.asipto.com
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list