bump?
On Tue, Jul 26, 2011 at 12:21 PM, Ryan Revels wrote:
> I am attempting to install OpenSIPS 1.7 using PostgreSQL as the DB. I'm
> using the latest OpenSIPS 1.7 subversion on Debian Squeeze and
> postgresql-9.0.
>
> After configuring opensipsctlrc, I first encounter this error:
> root@core-d
Hi,
I am using Opensips 1.7 where we can configure the db_mode param for the b2b
modules. The db_mode param works but it still expects the db_url param
defined for the b2b modules.
Is the db_url param required when db_mode is configured as 0?? If the db_url
is not defined I get the following errors
Hi Chris,
I guess the "incorrect port 0" errors appear in the OpenSIPS logs. Do
you also receive errors in the RTPProxy logs?
OpenSIPS doesn't delete the dialogs because, perhaps, the RTPProxy
timeout notification is never received.
Regards,
Razvan Crainea
OpenSIPS Developer
On 01.08.201
Hi Razvan,
Thanks for the quick response.
I am using 8189.
One other thing, I have been getting individual calls hanging as well
resulting in calls never clearing down. When I track the times of these
calls they always coincide to the second with errors on the opensips log
associated wi
Hi Chris,
What svn revision are you using? I remember you reported this issue, but
I think this should be fixed in the latest svn.
Regards,
Razvan Crainea
OpenSIPS Developer
On 01.08.2011 10:51, Chris Martineau wrote:
Hi,
I have raised this issue before but now I have had it cause the sy
Hello,
It seems that you somehow loop the traffic to your server, because that
error means the message has over 64 Route headers.
Please check your config file for the source of this bad routing.
Regards,
--
Vlad Paiu
OpenSIPS Developer
On 07/30/2011 06:28 AM, nguyen khue wrote:
Hi all,
Hi,
I have raised this issue before but now I have had it cause the system
to go offline overnight.
I noticed the problem initially when you disable an rtpproxy instance
from the cache screen on opensips-cp. Basically the system would block
whilst doing a timeout/proxy does not respond proc
