[OpenSIPS-Users] http://www.openxcap.org/wiki/Installation - error
Hello, I think you have an error in the OpenXCAP Install guide, there is written: python-gnutls =1.8.1, but on the package site the last version is 1.2.1. Regards, Liviu___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] http://www.openxcap.org/wiki/Installation - error
On Jun 10, 2011, at 8:47 AM, Barsan Liviu wrote: Hello, I think you have an error in the OpenXCAP Install guide, there is written: python-gnutls =1.8.1, but on the package site the last version is 1.2.1. That should read 1.1.9, I just changed it, thanks! -- Saúl Ibarra Corretgé AG Projects ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] MSRPRelay install problem
Hello, I installed the msrprelay with apt-get install ..., and I got the following error: Unpacking msrprelay (from .../msrprelay_1.0.5_all.deb) ... Setting up msrprelay (1.0.5) ... Starting MSRP Relay: msrprelayTraceback (most recent call last): File /usr/bin/msrprelay, line 16, in module import msrp ImportError: No module named msrp . Processing triggers for python-support ... I notice the following: - I have in /etc/apt/sources.list the following: # AG Projects software debhttp://ag-projects.com/debian stable main deb-src http://ag-projects.com/debian stable main , thus not the ...unstable main as it is written in the install guide. - all other servers, modules were installed without problems. I have the following system: Debian 6.0.1 Squeeze, python 2.6.6 and all required prerequisites installed. Thanks, Liviu ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] MSRPRelay install problem
Hi, On Jun 10, 2011, at 9:08 AM, Barsan Liviu wrote: Hello, I installed the msrprelay with apt-get install ..., and I got the following error: Unpacking msrprelay (from .../msrprelay_1.0.5_all.deb) ... Setting up msrprelay (1.0.5) ... Starting MSRP Relay: msrprelayTraceback (most recent call last): File /usr/bin/msrprelay, line 16, in module import msrp ImportError: No module named msrp . Processing triggers for python-support ... I notice the following: - I have in /etc/apt/sources.list the following: # AG Projects software deb http://ag-projects.com/debian stable main deb-src http://ag-projects.com/debian stable main , thus not the ...unstable main as it is written in the install guide. - all other servers, modules were installed without problems. I have the following system: Debian 6.0.1 Squeeze, python 2.6.6 and all required prerequisites installed. We just made a new MSRPRelay release for addressing those: http://lists.ag-projects.com/pipermail/sipbeyondvoip/2011-June/001960.html Regards, -- Saúl Ibarra Corretgé AG Projects ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Opensips-mi-proxy unable to start
Hi, Thank you for the info. I downloaded python-application version 1.2.7 as suggested. I manually removed the python-application 1.2.8 version files from /usr/lib/python2.5/site-packages/application/ directory. I installed python-application version1.2.7 But I end up in an import module error this time, when I attempt to start opensips-mi-proxy Logs: Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: Starting OpenSIPS MI Proxy 1.0.4 Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: Traceback (most recent call last): Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: File /usr/bin/opensips-mi-proxy, line 59, in module Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: from miproxy.proxy import MIProxy Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: File /usr/lib/python2.5/site-packages/miproxy/proxy.py, line 15, in module Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: from twisted.internet import reactor Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: File /usr/lib/python2.5/site-packages/application/log/extensions/twisted/twisted.py, line 14, in module Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: import twisted Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: ImportError: No module named twisted Please can you assist to resolve this issue. Thanks in advance. On Thu, Jun 9, 2011 at 7:16 PM, Dan Pascu d...@ag-projects.com wrote: The MI proxy needs to be adapted to some code changes in pyhton-application and it'll work in the next release. Use an older version of python-application for the time being (1.2.7 will do). use darcs get --to-patch release-1.2.7 http://devel.ag-projects.com/repositories/python-application to get python-application version 1.2.7 On 9 Jun 2011, at 16:16, Nethra Chander wrote: Hi, I am unable to start opensips-mi-proxy module successfully. The logs below: Jun 9 13:09:38 ip-10-56-67-103 opensips-mi-proxy[16278]: Starting OpenSIPS MI Proxy 1.0.4 Jun 9 13:09:38 ip-10-56-67-103 opensips-mi-proxy[16278]: error: Traceback (most recent call last): Jun 9 13:09:38 ip-10-56-67-103 opensips-mi-proxy[16278]: error: File /usr/bin/opensips-mi-proxy, line 59, in module Jun 9 13:09:38 ip-10-56-67-103 opensips-mi-proxy[16278]: error: from miproxy.proxy import MIProxy Jun 9 13:09:38 ip-10-56-67-103 opensips-mi-proxy[16278]: error: File /usr/lib/python2.5/site-packages/miproxy/proxy.py, line 12, in module Jun 9 13:09:38 ip-10-56-67-103 opensips-mi-proxy[16278]: error: from application.system import default_host_ip Jun 9 13:09:38 ip-10-56-67-103 opensips-mi-proxy[16278]: error: ImportError: cannot import name default_host_ip Please assist as to how I can resolve the issue above. I installed python-application from the repositories using darcs get http://devel.ag-projects.com/repositories/python-application while opensips-mi-proxy is installed from the tar archive. Not sure if this has something to do with the error reported. Appreciate any help. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Dan ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Dispatcher module setting to probing
I am testing with the dispatcher module at the moment, one of the options is
to set the probing mode to 1 which means the module will automatically
disable a gateway if it receives a 408.
Is it possible to make this only set to probing if a *locally* generated 408
is received? At the moment it disables even if the downstream gateway
returns a 408 which seems wrong to me. If the gateway has responded then it
is not inactive.
The code looks like this but I am not sure if it's easy to derive if the 408
is locally generated from the tmcb_params
struct tmcb_params *ps
if(ds_probing_mode==1 ps-code == 408)
{
if (ds_set_state(group, uri, DS_PROBING_DST, 1) != 0)
{
LM_ERR(Setting the probing state failed (%.*s,
group %d)\n,
uri.len, uri.s, group);
}
}
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Opensips-mi-proxy unable to start
On Jun 10, 2011, at 12:39 PM, Nethra Chander wrote: Hi, Thank you for the info. I downloaded python-application version 1.2.7 as suggested. I manually removed the python-application 1.2.8 version files from /usr/lib/python2.5/site-packages/application/ directory. I installed python-application version1.2.7 But I end up in an import module error this time, when I attempt to start opensips-mi-proxy Logs: Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: Starting OpenSIPS MI Proxy 1.0.4 Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: Traceback (most recent call last): Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: File /usr/bin/opensips-mi-proxy, line 59, in module Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: from miproxy.proxy import MIProxy Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: File /usr/lib/python2.5/site-packages/miproxy/proxy.py, line 15, in module Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: from twisted.internet import reactor Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: File /usr/lib/python2.5/site-packages/application/log/extensions/twisted/twisted.py, line 14, in module Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: import twisted Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: ImportError: No module named twisted A new OpenSIPS-MI-Proxy package has been uploaded to our debian repository, please update your system (python-application will also be updated). -- Saúl Ibarra Corretgé AG Projects ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] New CDRTool release 8.1.1
Hello, There is a new release of CDRTool with bug fixes. cdrtool (8.1.1) unstable; urgency=low * Fixed link to individual calls when group by canonical uri * Fixed export for OpenSIPS CDRs to csv file For how to upgrade your installation see: http://cdrtool.ag-projects.com/wiki/Install Regards, Adrian ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Opensips-mi-proxy unable to start
Hi, I will try with the new version. To download the tar archives, the new version is not listed in the download URL http://download.ag-projects.com/XCAP/ mentioned in the installation wiki page. Can you check, please? To download code from the source, can you point me to the repository URL or the name for opensips-mi-proxy, please? I tried, darcs get http://devel.ag-projects.com/repositories/opensips-mi-proxy and it returned error. Thanks in advance. On Fri, Jun 10, 2011 at 1:55 PM, Saúl Ibarra Corretgé s...@ag-projects.comwrote: On Jun 10, 2011, at 12:39 PM, Nethra Chander wrote: Hi, Thank you for the info. I downloaded python-application version 1.2.7 as suggested. I manually removed the python-application 1.2.8 version files from /usr/lib/python2.5/site-packages/application/ directory. I installed python-application version1.2.7 But I end up in an import module error this time, when I attempt to start opensips-mi-proxy Logs: Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: Starting OpenSIPS MI Proxy 1.0.4 Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: Traceback (most recent call last): Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: File /usr/bin/opensips-mi-proxy, line 59, in module Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: from miproxy.proxy import MIProxy Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: File /usr/lib/python2.5/site-packages/miproxy/proxy.py, line 15, in module Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: from twisted.internet import reactor Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: File /usr/lib/python2.5/site-packages/application/log/extensions/twisted/twisted.py, line 14, in module Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: import twisted Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: ImportError: No module named twisted A new OpenSIPS-MI-Proxy package has been uploaded to our debian repository, please update your system (python-application will also be updated). -- Saúl Ibarra Corretgé AG Projects ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Opensips-mi-proxy unable to start
On Jun 10, 2011, at 1:10 PM, Nethra Chander wrote: Hi, I will try with the new version. To download the tar archives, the new version is not listed in the download URL http://download.ag-projects.com/XCAP/ mentioned in the installation wiki page. Can you check, please? Packages are being uploaded there right now. If you use a Debian system you may use our repository for installing them. To download code from the source, can you point me to the repository URL or the name for opensips-mi-proxy, please? I tried, darcs get http://devel.ag-projects.com/repositories/opensips-mi-proxy and it returned error. Thanks in advance. On Fri, Jun 10, 2011 at 1:55 PM, Saúl Ibarra Corretgé s...@ag-projects.com wrote: On Jun 10, 2011, at 12:39 PM, Nethra Chander wrote: Hi, Thank you for the info. I downloaded python-application version 1.2.7 as suggested. I manually removed the python-application 1.2.8 version files from /usr/lib/python2.5/site-packages/application/ directory. I installed python-application version1.2.7 But I end up in an import module error this time, when I attempt to start opensips-mi-proxy Logs: Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: Starting OpenSIPS MI Proxy 1.0.4 Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: Traceback (most recent call last): Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: File /usr/bin/opensips-mi-proxy, line 59, in module Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: from miproxy.proxy import MIProxy Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: File /usr/lib/python2.5/site-packages/miproxy/proxy.py, line 15, in module Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: from twisted.internet import reactor Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: File /usr/lib/python2.5/site-packages/application/log/extensions/twisted/twisted.py, line 14, in module Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: import twisted Jun 10 10:31:50 ip-10-56-67-103 opensips-mi-proxy[17366]: error: ImportError: No module named twisted A new OpenSIPS-MI-Proxy package has been uploaded to our debian repository, please update your system (python-application will also be updated). -- Saúl Ibarra Corretgé AG Projects ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Saúl Ibarra Corretgé AG Projects ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Opensips-mi-proxy unable to start
Try again To download code from the source, can you point me to the repository URL or the name for opensips-mi-proxy, please? I tried, darcs get http://devel.ag-projects.com/repositories/opensips-mi-proxy and it returned error. Thanks in advance. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Opensips-mi-proxy unable to start
Hi, The tar file repository is updated and I downloaded opensips-mi-proxy-1.0.5. I installed this version. I also installed python-application 1.2.8 from the repositories. However, i am still not able to start opensips-mi-proxy successfully. The logs point to the same import twisted module error. Starting OpenSIPS MI Proxy 1.0.5 Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: Traceback (most recent call last): Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: File /usr/bin/opensips-mi-proxy, line 59, in module Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: from miproxy.proxy import MIProxy Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: File /usr/lib/python2.5/site-packages/miproxy/proxy.py, line 15, in module Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: from twisted.internet import reactor Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: File /usr/lib/python2.5/site-packages/application/log/extensions/twisted/twisted.py, line 14, in module Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: import twisted Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: ImportError: No module named twisted Can you assist, please? Thanks On Fri, Jun 10, 2011 at 2:20 PM, Adrian Georgescu a...@ag-projects.comwrote: Try again To download code from the source, can you point me to the repository URL or the name for opensips-mi-proxy, please? I tried, darcs get http://devel.ag-projects.com/repositories/opensips-mi-proxy and it returned error. Thanks in advance. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Opensips-mi-proxy unable to start
Hi, On Jun 10, 2011, at 1:44 PM, Nethra Chander wrote: Hi, The tar file repository is updated and I downloaded opensips-mi-proxy-1.0.5. I installed this version. I also installed python-application 1.2.8 from the repositories. However, i am still not able to start opensips-mi-proxy successfully. The logs point to the same import twisted module error. Starting OpenSIPS MI Proxy 1.0.5 Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: Traceback (most recent call last): Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: File /usr/bin/opensips-mi-proxy, line 59, in module Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: from miproxy.proxy import MIProxy Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: File /usr/lib/python2.5/site-packages/miproxy/proxy.py, line 15, in module Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: from twisted.internet import reactor Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: File /usr/lib/python2.5/site-packages/application/log/extensions/twisted/twisted.py, line 14, in module Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: import twisted Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: ImportError: No module named twisted Can you assist, please? You don't seem to have twisted properly installed. Since you installed from sources you need to install the dependencies manually. OpenSIPS-MI-Proxy depends on python-twisted-core and python-twisted-web2, so you'll need those 2. Or you can install opensips-mi-proxy package from our repository and dependencies will automatically be installed. Regards, -- Saúl Ibarra Corretgé AG Projects ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] MySQL connection error
Hello, We re-installed from sources the OpenSIPs server to Debian and copied back to /etc/opensips the configuration files saved from the previous working OpenSIPs. When I start the server with opensips start then we receive the error in the log: Jun 10 18:03:12 P4302 opensips[18307]: ERROR:db_mysql:db_mysql_connect: driver error(1045): Access denied for user 'opensips'@'localhost' (using password: YES) Jun 10 18:03:12 P4302 opensips[18307]: ERROR:db_mysql:db_mysql_new_connection: initial connect failed Jun 10 18:03:12 P4302 opensips[18307]: ERROR:core:db_do_init: could not add connection to the pool For sure we do not have db_url in opensips.cfg or other files which contains username 'opensips'. Checked and from command line we can connect from mysql with the credentials we set in opensips.cfg. To be sure we put back the initial opensips.cfg comming with the sources, changed the db credentials to ours and still receive this error. Do you have any suggestion? Thanks, Liviu___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] MySQL connection error
Liviu, Could it be that opensips is installed in /usr/local and is therefore using db_url from /usr/local/etc/opensips.cfg ? It's my best guess. On 10.06.2011 15:22, Barsan Liviu wrote: Hello, We re-installed from sources the OpenSIPs server to Debian and copied back to /etc/opensips the configuration files saved from the previous working OpenSIPs. When I start the server with opensips start then we receive the error in the log: Jun 10 18:03:12 P4302 opensips[18307]: ERROR:db_mysql:db_mysql_connect: driver error(1045): Access denied for user 'opensips'@'localhost' (using password: YES) Jun 10 18:03:12 P4302 opensips[18307]: ERROR:db_mysql:db_mysql_new_connection: initial connect failed Jun 10 18:03:12 P4302 opensips[18307]: ERROR:core:db_do_init: could not add connection to the pool For sure we do not have db_url in opensips.cfg or other files which contains username 'opensips'. Checked and from command line we can connect from mysql with the credentials we set in opensips.cfg. To be sure we put back the initial opensips.cfg comming with the sources, changed the db credentials to ours and still receive this error. Do you have any suggestion? Thanks, Liviu -- Sincerely, Andrew Pogrebennyk ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Opensips-mi-proxy unable to start
Hi, I am sorry for bothering again but using apt-get install for opensips-mi-proxy is unsuccessful as well. apt-get install opensips-mi-proxy shows below error. The following packages have unmet dependencies: opensips-mi-proxy : Depends: python (= 2.6.6-3+squeeze3~) but 2.5.2-3 is to be installed Depends: python-application (= 1.2.8) but it is not going to be installed I try to update python by trying apt-get install python lists python to be the latest version. I am confused as to what my next steps be. I am fairly new to Linux environments as well as VOIP servers. Please, can someone assist? Thanks On Fri, Jun 10, 2011 at 3:03 PM, Saúl Ibarra Corretgé s...@ag-projects.comwrote: Hi, On Jun 10, 2011, at 1:44 PM, Nethra Chander wrote: Hi, The tar file repository is updated and I downloaded opensips-mi-proxy-1.0.5. I installed this version. I also installed python-application 1.2.8 from the repositories. However, i am still not able to start opensips-mi-proxy successfully. The logs point to the same import twisted module error. Starting OpenSIPS MI Proxy 1.0.5 Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: Traceback (most recent call last): Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: File /usr/bin/opensips-mi-proxy, line 59, in module Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: from miproxy.proxy import MIProxy Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: File /usr/lib/python2.5/site-packages/miproxy/proxy.py, line 15, in module Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: from twisted.internet import reactor Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: File /usr/lib/python2.5/site-packages/application/log/extensions/twisted/twisted.py, line 14, in module Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: import twisted Jun 10 11:39:43 ip-10-56-67-103 opensips-mi-proxy[17455]: error: ImportError: No module named twisted Can you assist, please? You don't seem to have twisted properly installed. Since you installed from sources you need to install the dependencies manually. OpenSIPS-MI-Proxy depends on python-twisted-core and python-twisted-web2, so you'll need those 2. Or you can install opensips-mi-proxy package from our repository and dependencies will automatically be installed. Regards, -- Saúl Ibarra Corretgé AG Projects ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] MySQL connection error
*Hello, Can you check the default parameter values for the modules that you load in the opensips.cfg file and for which you have not explicitly configured modparams? By default, the db_url parameter for the modules have the value* * mysql://opensips:opensipsrw@localhost/opensips So, in your case, the opensips@localhost and the password used might not be from your opensips.cfg but rather coming from the default parameter values atleast for one of the modules I ran into similar issue and was able to resolve by explicitly configuring db_url params for all the applicable modules. Thanks. * On Fri, Jun 10, 2011 at 3:22 PM, Barsan Liviu bars...@yahoo.com wrote: Hello, We re-installed from sources the OpenSIPs server to Debian and copied back to /etc/opensips the configuration files saved from the previous working OpenSIPs. When I start the server with opensips start then we receive the error in the log: Jun 10 18:03:12 P4302 opensips[18307]: ERROR:db_mysql:db_mysql_connect: driver error(1045): Access denied for user 'opensips'@'localhost' (using password: YES) Jun 10 18:03:12 P4302 opensips[18307]: ERROR:db_mysql:db_mysql_new_connection: initial connect failed Jun 10 18:03:12 P4302 opensips[18307]: ERROR:core:db_do_init: could not add connection to the pool For sure we do not have db_url in opensips.cfg or other files which contains username 'opensips'. Checked and from command line we can connect from mysql with the credentials we set in opensips.cfg. To be sure we put back the initial opensips.cfg comming with the sources, changed the db credentials to ours and still receive this error. Do you have any suggestion? Thanks, Liviu ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] MySQL connection error
Liviu, On 10.06.2011 15:45, Barsan Liviu wrote: Last installation was from sources, something like: 1. Copy the tar to /usr/src 2. untar 3. cd opensips-1.6.2-tls 4. make prefix=/ make prefix=/ modules make prefix=/ install As far as I know this is the standard installation. Please reply to the mailing list or keep it in the CC field. IIRC I was using the following build commands: make prefix=/usr cfg-target=/etc/opensips/ all make prefix=/usr cfg-target=/etc/opensips/ install Run opensips -h, what does the -f option tell you? Like: $ opensips -h version: opensips 1.6.1-notls (i386/linux) Usage: opensips -l address [-l address ...] [options] Options: -f file Configuration file (default /usr/local/etc/opensips/opensips.cfg) Maybe can help the output from *find / -name 'opensips*'*: /lib/opensips /lib/opensips/opensipsctl /lib/opensips/opensipsctl/opensipsctl.sqlbase /lib/opensips/opensipsctl/opensipsdbctl.dbtext /lib/opensips/opensipsctl/opensipsctl.dbtext /lib/opensips/opensipsctl/opensipsctl.fifo /lib/opensips/opensipsctl/opensipsctl.unixsock /lib/opensips/opensipsctl/opensipsctl.base /lib/opensips/opensipsctl/opensipsctl.ctlbase /lib/opensips/opensipsctl/opensipsdbctl.base /etc/init.d/opensips-mi-proxy /etc/opensips-mi-proxy /etc/opensips /etc/opensips/opensips.cfg /etc/opensips/opensipsctlrc /usr/lib/python2.5/site-packages/xcap/interfaces/opensips.py /usr/lib/python2.5/site-packages/xcap/interfaces/backend/opensips.py /usr/lib/python2.6/dist-packages/xcap/interfaces/opensips.pyc /usr/lib/python2.6/dist -packages/xcap/interfaces/opensips.py /usr/lib/python2.6/dist-packages/xcap/interfaces/backend/opensips.pyc /usr/lib/python2.6/dist-packages/xcap/interfaces/backend/opensips.py /usr/lib/pymodules/python2.6/mediaproxy/interfaces/opensips.pyc /usr/lib/pymodules/python2.6/mediaproxy/interfaces/opensips.py /usr/lib/pymodules/python2.6/opensips_mi_proxy-1.0.4.egg-info /usr/lib/pymodules/python2.6/miproxy/opensips.pyc /usr/lib/pymodules/python2.6/miproxy/opensips.py /usr/src/opensips-cp /usr/src/opensips-cp/config/tools/system/cdrviewer/opensips_cdrs_1_6.pgsql /usr/src/opensips-cp/config/tools/system/cdrviewer/opensips_cdrs_1_6.mysql /usr/src/opensips-1.6.4-2-tls /usr/src/opensips-1.6.4-2-tls/opensipsdbctl.8 /usr/src/opensips-1.6.4-2-tls/etc/opensips.cfg /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-permissions.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-uri_db.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-rls.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-closeddial.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-registrar.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-alias_db.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-imc.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-standard.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-pdt.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-presence.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-carrierroute.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-dialog.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-domainpolicy.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-extensions.xml /usr/src/opensips-1.6.4-2-tls/ db/schema/opensips-userblacklist.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-siptrace.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-cpl.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-dispatcher.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-lcr.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-b2b.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-usrloc.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-auth_db.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-nathelper.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-group.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-drouting.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-speeddial.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-msilo.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-dialplan.xml /usr /src/opensips-1.6.4-2-tls/db/schema/opensips-domain.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-avpops.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-load_balancer.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-acc.xml /usr/src/opensips-1.6.4-2-tls/utils/opensipsunix /usr/src/opensips-1.6.4-2-tls/utils/opensipsunix/opensipsunix.8 /usr/src/opensips-1.6.4-2-tls/utils/opensipsunix/opensipsunix.c /usr/src/opensips-1.6.4-2-tls/utils/opensipsunix/opensipsunix.d /usr/src/opensips-1.6.4-2-tls/utils/opensipsunix/opensipsunix.o /usr/src/opensips-1.6.4-2-tls/utils/opensipsunix/opensipsunix /usr/src/opensips-1.6.4-2-tls/doc/doxygen/opensips-doxygen /usr/src/opensips-1.6.4-2-tls/opensips.cfg.5 /usr/src/opensips-1.6.4-2-tls/packaging/fedora/opensips.spec /usr/src/opensips-1.6.4-2-tls/packaging/fedora/opensips.init /usr/src/opensips-1.6.4-2-tls/packaging/debian/opensips.default
Re: [OpenSIPS-Users] Opensips-mi-proxy unable to start
On Jun 10, 2011, at 2:47 PM, Nethra Chander wrote: Hi, I am sorry for bothering again but using apt-get install for opensips-mi-proxy is unsuccessful as well. apt-get install opensips-mi-proxy shows below error. The following packages have unmet dependencies: opensips-mi-proxy : Depends: python (= 2.6.6-3+squeeze3~) but 2.5.2-3 is to be installed Depends: python-application (= 1.2.8) but it is not going to be installed What distribution are you running? -- Saúl Ibarra Corretgé AG Projects ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] MySQL connection error
Hello, The opensips -h returns what is expected: root@P4302:~# opensips -h version: opensips 1.6.4-2-notls (i386/linux) Usage: opensips -l address [-l address ...] [options] ... I haven't any file in /usr/local/atc And I see now the first time that cfg-target can be given at make. Thanks, Liviu From: Andrew Pogrebennyk andrew.pogreben...@portaone.com To: Barsan Liviu bars...@yahoo.com Cc: opensipusers Users@lists.opensips.org Sent: Fri, June 10, 2011 3:55:43 PM Subject: Re: [OpenSIPS-Users] MySQL connection error Liviu, On 10.06.2011 15:45, Barsan Liviu wrote: Last installation was from sources, something like: 1. Copy the tar to /usr/src 2. untar 3. cd opensips-1.6.2-tls 4. make prefix=/ make prefix=/ modules make prefix=/ install As far as I know this is the standard installation. Please reply to the mailing list or keep it in the CC field. IIRC I was using the following build commands: make prefix=/usr cfg-target=/etc/opensips/ all make prefix=/usr cfg-target=/etc/opensips/ install Run opensips -h, what does the -f option tell you? Like: $ opensips -h version: opensips 1.6.1-notls (i386/linux) Usage: opensips -l address [-l address ...] [options] Options: -f file Configuration file (default /usr/local/etc/opensips/opensips.cfg) Maybe can help the output from *find / -name 'opensips*'*: /lib/opensips /lib/opensips/opensipsctl /lib/opensips/opensipsctl/opensipsctl.sqlbase /lib/opensips/opensipsctl/opensipsdbctl.dbtext /lib/opensips/opensipsctl/opensipsctl.dbtext /lib/opensips/opensipsctl/opensipsctl.fifo /lib/opensips/opensipsctl/opensipsctl.unixsock /lib/opensips/opensipsctl/opensipsctl.base /lib/opensips/opensipsctl/opensipsctl.ctlbase /lib/opensips/opensipsctl/opensipsdbctl.base /etc/init.d/opensips-mi-proxy /etc/opensips-mi-proxy /etc/opensips /etc/opensips/opensips.cfg /etc/opensips/opensipsctlrc /usr/lib/python2.5/site-packages/xcap/interfaces/opensips.py /usr/lib/python2.5/site-packages/xcap/interfaces/backend/opensips.py /usr/lib/python2.6/dist-packages/xcap/interfaces/opensips.pyc /usr/lib/python2.6/dist -packages/xcap/interfaces/opensips.py /usr/lib/python2.6/dist-packages/xcap/interfaces/backend/opensips.pyc /usr/lib/python2.6/dist-packages/xcap/interfaces/backend/opensips.py /usr/lib/pymodules/python2.6/mediaproxy/interfaces/opensips.pyc /usr/lib/pymodules/python2.6/mediaproxy/interfaces/opensips.py /usr/lib/pymodules/python2.6/opensips_mi_proxy-1.0.4.egg-info /usr/lib/pymodules/python2.6/miproxy/opensips.pyc /usr/lib/pymodules/python2.6/miproxy/opensips.py /usr/src/opensips-cp /usr/src/opensips-cp/config/tools/system/cdrviewer/opensips_cdrs_1_6.pgsql /usr/src/opensips-cp/config/tools/system/cdrviewer/opensips_cdrs_1_6.mysql /usr/src/opensips-1.6.4-2-tls /usr/src/opensips-1.6.4-2-tls/opensipsdbctl.8 /usr/src/opensips-1.6.4-2-tls/etc/opensips.cfg /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-permissions.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-uri_db.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-rls.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-closeddial.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-registrar.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-alias_db.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-imc.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-standard.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-pdt.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-presence.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-carrierroute.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-dialog.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-domainpolicy.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-extensions.xml /usr/src/opensips-1.6.4-2-tls/ db/schema/opensips-userblacklist.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-siptrace.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-cpl.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-dispatcher.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-lcr.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-b2b.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-usrloc.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-auth_db.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-nathelper.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-group.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-drouting.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-speeddial.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-msilo.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-dialplan.xml /usr /src/opensips-1.6.4-2-tls/db/schema/opensips-domain.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-avpops.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-load_balancer.xml /usr/src/opensips-1.6.4-2-tls/db/schema/opensips-acc.xml /usr/src/opensips-1.6.4-2-tls/utils/opensipsunix
Re: [OpenSIPS-Users] MySQL connection error
Hi Liviu, I think Nethra is right about the modparams, please check. On 10.06.2011 16:03, Barsan Liviu wrote: Hello, The opensips -h returns what is expected: root@P4302:~# opensips -h version: opensips 1.6.4-2-notls (i386/linux) Usage: opensips -l address [-l address ...] [options] ... I haven't any file in /usr/local/atc And I see now the first time that cfg-target can be given at make. Thanks, Liviu -- Sincerely, Andrew Pogrebennyk ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] B2B module and CANCEL
Hello!
I have a such problem opensips1.6.4-2
There are two proxies of version 1.6.4.-2 which has been installed on the same
server.
One proxy (proxy1) using B2B “top hiding” and located in /usr/local/sbc and
using one signaling port
Another proxy (proxy2) is just SIP proxy and located in
/usr/local/opensips1.6.4/ and using another signaling port
Both proxies using the same ip address of the server
Call flow:
some UA – proxy1 – proxy2 – some gateway
When UA generate CANCEL then proxy1 does some strange things with FROM or TO
uri headers (you can see it in attachment). Because of this proxy2 cannot
parse CANCEL properly and transaction in proxy2 cannot be canceled.
Thank you for any help.
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:parse_msg: SIP
Request:
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:parse_msg:
method: CANCEL
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:parse_msg:
uri: sip:88123364021@1.1.1.1:5063;transport=UDP
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:parse_msg:
version: SIP/2.0
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:parse_headers:
flags=2
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]:
DBG:core:parse_via_param: found param type 232, branch =
z9hG4bK-d8754z-816e76605de1b275-1---d8754z-; state=6
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]:
DBG:core:parse_via_param: found param type 235, rport = n/a; state=17
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:parse_via: end
of header reached, state=5
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:parse_headers:
via found, flags=2
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:parse_headers:
this is the first via
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:receive_msg:
After parse_msg...
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:receive_msg:
preparing to run routing scripts...
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:parse_headers:
flags=
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:parse_to: end
of header reached, state=10
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:parse_to:
display={}, ruri={sip:88123364021@1.1.1.1:5063;transport=UDP}
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:get_hdr_field:
To [52]; uri=[sip:88123364021@1.1.1.1:5063;transport=UDP]
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:get_hdr_field:
to body [sip:88123364021@1.1.1.1:5063;transport=UDP#015#012]
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:get_hdr_field:
cseq CSeq: 2 CANCEL
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:get_hdr_field:
content_length=0
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:get_hdr_field:
found end of header
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]:
DBG:b2b_entities:b2b_prescript_f: start - method = CANCEL
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]:
DBG:core:parse_to_param: tag=2e1b1846
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:parse_to: end
of header reached, state=29
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:parse_to:
display={}, ruri={sip:8123364079@1.1.1.1:5063;transport=UDP}
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]:
DBG:b2b_entities:b2b_parse_key: Does not have b2b_entities prefix
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]:
DBG:b2b_entities:b2bl_search_iteratively: Search for record with callid=
MzBhYzkyODA2YjEzZGEyZTFhNjAxMzBhMjI1NWU3ZmU., tag= 2e1b1846
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]:
DBG:b2b_entities:b2bl_search_iteratively: Found callid=
MzBhYzkyODA2YjEzZGEyZTFhNjAxMzBhMjI1NWU3ZmU., tag= 2e1b1846
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:tm:t_newtran:
transaction on entrance=0x
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:parse_headers:
flags=
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:parse_headers:
flags=78
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]:
DBG:tm:t_lookup_request: start searching: hash=49978, isACK=0
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:tm:matching_3261:
RFC3261 transaction matching failed
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]:
DBG:tm:t_lookup_request: no transaction found
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:parse_headers:
flags=
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]:
DBG:core:check_ip_address: params 192.168.18.55, 192.168.18.55, 0
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]: DBG:core:_shm_resize:
resize(0) called
Jun 10 17:40:47 kam /usr/local/sbc/sbin/opensips[1814]:
DBG:tm:cleanup_uac_timers:
Re: [OpenSIPS-Users] MediaProxy installation error
Hello Saul, This is what I was trying actually, but I receive the following errors: mediaproxy/interfaces/system/_conntrack.c:132: warning: implicit declaration of function âPy_VISITâ mediaproxy/interfaces/system/_conntrack.c:132: error: âForwardingRuleâ has no member named âdictâ mediaproxy/interfaces/system/_conntrack.c: In function âForwardingRule_clearâ: mediaproxy/interfaces/system/_conntrack.c:140: warning: implicit declaration of function âPy_CLEARâ mediaproxy/interfaces/system/_conntrack.c:140: error: âForwardingRuleâ has no member named âdictâ mediaproxy/interfaces/system/_conntrack.c: At top level: mediaproxy/interfaces/system/_conntrack.c:145: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before â*â token mediaproxy/interfaces/system/_conntrack.c: In function âForwardingRule_deallocâ: mediaproxy/interfaces/system/_conntrack.c:180: warning: implicit declaration of function âPyObject_GC_UnTrackâ mediaproxy/interfaces/system/_conntrack.c:183: error: âForwardingRuleâ has no member named âis_activeâ mediaproxy/interfaces/system/_conntrack.c:184: error: âForwardingRuleâ has no member named âconntrackâ mediaproxy/interfaces/system/_conntrack.c:186: error: âPy_BEGIN_ALLOW_THREADSâ undeclared (first use in this function) mediaproxy/interfaces/system/_conntrack.c:186: error: (Each undeclared identifier is reported only once mediaproxy/interfaces/system/_conntrack.c:186: error: for each function it appears in.) mediaproxy/interfaces/system/_conntrack.c:187: error: expected â;â before âct_handleâ mediaproxy/interfaces/system/_conntrack.c:189: error: âForwardingRuleâ has no member named âconntrackâ mediaproxy/interfaces/system/_conntrack.c:192: error: âPy_END_ALLOW_THREADSâ undeclared (first use in this function) mediaproxy/interfaces/system/_conntrack.c:193: error: expected â;â before â}â token mediaproxy/interfaces/system/_conntrack.c:194: error: âForwardingRuleâ has no member named âconntrackâ mediaproxy/interfaces/system/_conntrack.c:196: error: âForwardingRuleâ has no member named âob_typeâ mediaproxy/interfaces/system/_conntrack.c:196: error: âPyObjectâ undeclared (first use in this function) mediaproxy/interfaces/system/_conntrack.c:196: error: expected expression before â)â token mediaproxy/interfaces/system/_conntrack.c: At top level: mediaproxy/interfaces/system/_conntrack.c:201: error: expected declaration specifiers or â...â before âPyObjectâ And I think I'm near to give up this environment for SIP. I notice that before I installed MediaProxy to Ubuntu 10.04 and at least the build and install were running OK. Liviu From: Saúl Ibarra Corretgé s...@ag-projects.com To: OpenSIPS users mailling list users@lists.opensips.org Sent: Fri, June 10, 2011 4:49:51 PM Subject: Re: [OpenSIPS-Users] MediaProxy installation error Hi, On Jun 10, 2011, at 3:25 PM, Barsan Liviu wrote: Hello, We were installing the mediaproxy from your repository with apt-get ... , including all prerequisites and we can not run media relay because we receive the error: fatal error: failed to create MediaProxy Relay: cannot import name default_host_ip Jun 10 19:09:05 P4302 media-relay[2333]: Traceback (most recent call last): Jun 10 19:09:05 P4302 media-relay[2333]: File /usr/bin/media-relay, line 61, in module Jun 10 19:09:05 P4302 media-relay[2333]: from mediaproxy.relay import MediaRelay Jun 10 19:09:05 P4302 media-relay[2333]: File /usr/lib/pymodules/python2.6/mediaproxy/relay.py, line 33, in module Jun 10 19:09:05 P4302 media-relay[2333]: from application.system import default_host_ip Jun 10 19:09:05 P4302 media-relay[2333]: ImportError: cannot import name default_host_ip As we think this comes from some incompatibility with the python-application package. By uninstalling the python-application package, all related packages were uninstalled, thus we can start again from installing from sources. Would be welcome a tested configuration including which versions of the prerequisites to install. We are currently working on new packages, but that will take time. In the meanwhile, you may fetch the source code and build MediaProxy yourself: darcs get http://devel.ag-projects.com/repositories/mediaproxy cd mediaproxy debuild -us -uc Regards, -- Saúl Ibarra Corretgé AG Projects ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] MySQL connection error
Hello, Very likely this is the problem, is the only one possibility to have an unset user trying to connect to the db. I notice that is a strange design to have some default DB connection params. Thanks, Liviu From: Nethra Chander netchan...@gmail.com To: OpenSIPS users mailling list users@lists.opensips.org Sent: Fri, June 10, 2011 3:54:32 PM Subject: Re: [OpenSIPS-Users] MySQL connection error Hello, Can you check the default parameter values for the modules that you load in the opensips.cfg file and for which you have not explicitly configured modparams? By default, the db_url parameter for the modules have the valuemysql://opensips:opensipsrw@localhost/opensips So, in your case, the opensips@localhost and the password used might not be from your opensips.cfg but rather coming from the default parameter values atleast for one of the modules I ran into similar issue and was able to resolve by explicitly configuring db_url params for all the applicable modules. Thanks. On Fri, Jun 10, 2011 at 3:22 PM, Barsan Liviu bars...@yahoo.com wrote: Hello, We re-installed from sources the OpenSIPs server to Debian and copied back to /etc/opensips the configuration files saved from the previous working OpenSIPs. When I start the server with opensips start then we receive the error in the log: Jun 10 18:03:12 P4302 opensips[18307]: ERROR:db_mysql:db_mysql_connect: driver error(1045): Access denied for user 'opensips'@'localhost' (using password: YES) Jun 10 18:03:12 P4302 opensips[18307]: ERROR:db_mysql:db_mysql_new_connection: initial connect failed Jun 10 18:03:12 P4302 opensips[18307]: ERROR:core:db_do_init: could not add connection to the pool For sure we do not have db_url in opensips.cfg or other files which contains username 'opensips'. Checked and from command line we can connect from mysql with the credentials we set in opensips.cfg. To be sure we put back the initial opensips.cfg comming with the sources, changed the db credentials to ours and still receive this error. Do you have any suggestion? Thanks, Liviu ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] MediaProxy installation error
Hi, On Jun 10, 2011, at 3:53 PM, Barsan Liviu wrote: Hello Saul, This is what I was trying actually, but I receive the following errors: mediaproxy/interfaces/system/_conntrack.c:132: warning: implicit declaration of function âPy_VISITâ mediaproxy/interfaces/system/_conntrack.c:132: error: âForwardingRuleâ has no member named âdictâ mediaproxy/interfaces/system/_conntrack.c: In function âForwardingRule_clearâ: mediaproxy/interfaces/system/_conntrack.c:140: warning: implicit declaration of function âPy_CLEARâ mediaproxy/interfaces/system/_conntrack.c:140: error: âForwardingRuleâ has no member named âdictâ mediaproxy/interfaces/system/_conntrack.c: At top level: mediaproxy/interfaces/system/_conntrack.c:145: error: expected â=â, â,â, â;â, âasmâ or â__attribute__â before â*â token mediaproxy/interfaces/system/_conntrack.c: In function âForwardingRule_deallocâ: mediaproxy/interfaces/system/_conntrack.c:180: warning: implicit declaration of function âPyObject_GC_UnTrackâ mediaproxy/interfaces/system/_conntrack.c:183: error: âForwardingRuleâ has no member named âis_activeâ mediaproxy/interfaces/system/_conntrack.c:184: error: âForwardingRuleâ has no member named âconntrackâ mediaproxy/interfaces/system/_conntrack.c:186: error: âPy_BEGIN_ALLOW_THREADSâ undeclared (first use in this function) mediaproxy/interfaces/system/_conntrack.c:186: error: (Each undeclared identifier is reported only once mediaproxy/interfaces/system/_conntrack.c:186: error: for each function it appears in.) mediaproxy/interfaces/system/_conntrack.c:187: error: expected â;â before âct_handleâ mediaproxy/interfaces/system/_conntrack.c:189: error: âForwardingRuleâ has no member named âconntrackâ mediaproxy/interfaces/system/_conntrack.c:192: error: âPy_END_ALLOW_THREADSâ undeclared (first use in this function) mediaproxy/interfaces/system/_conntrack.c:193: error: expected â;â before â}â token mediaproxy/interfaces/system/_conntrack.c:194: error: âForwardingRuleâ has no member named âconntrackâ mediaproxy/interfaces/system/_conntrack.c:196: error: âForwardingRuleâ has no member named âob_typeâ mediaproxy/interfaces/system/_conntrack.c:196: error: âPyObjectâ undeclared (first use in this function) mediaproxy/interfaces/system/_conntrack.c:196: error: expected expression before â)â token mediaproxy/interfaces/system/_conntrack.c: At top level: mediaproxy/interfaces/system/_conntrack.c:201: error: expected declaration specifiers or â...â before âPyObjectâ And I think I'm near to give up this environment for SIP. I notice that before I installed MediaProxy to Ubuntu 10.04 and at least the build and install were running OK. What Linux distribution are you using? This is a known issue which we are going to address, it has to do with an API change in the libraries we use for creating iptables conntrack rules. Regards, -- Saúl Ibarra Corretgé AG Projects ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] MySQL connection error
Hello Nethra, Your suggestion worked, indeed wasn't set the db_url. I mention again that in my opinion the design should be changed, a module db connection should not have default credentials. Thanks, Liviu From: Nethra Chander netchan...@gmail.com To: OpenSIPS users mailling list users@lists.opensips.org Sent: Fri, June 10, 2011 3:54:32 PM Subject: Re: [OpenSIPS-Users] MySQL connection error Hello, Can you check the default parameter values for the modules that you load in the opensips.cfg file and for which you have not explicitly configured modparams? By default, the db_url parameter for the modules have the valuemysql://opensips:opensipsrw@localhost/opensips So, in your case, the opensips@localhost and the password used might not be from your opensips.cfg but rather coming from the default parameter values atleast for one of the modules I ran into similar issue and was able to resolve by explicitly configuring db_url params for all the applicable modules. Thanks. On Fri, Jun 10, 2011 at 3:22 PM, Barsan Liviu bars...@yahoo.com wrote: Hello, We re-installed from sources the OpenSIPs server to Debian and copied back to /etc/opensips the configuration files saved from the previous working OpenSIPs. When I start the server with opensips start then we receive the error in the log: Jun 10 18:03:12 P4302 opensips[18307]: ERROR:db_mysql:db_mysql_connect: driver error(1045): Access denied for user 'opensips'@'localhost' (using password: YES) Jun 10 18:03:12 P4302 opensips[18307]: ERROR:db_mysql:db_mysql_new_connection: initial connect failed Jun 10 18:03:12 P4302 opensips[18307]: ERROR:core:db_do_init: could not add connection to the pool For sure we do not have db_url in opensips.cfg or other files which contains username 'opensips'. Checked and from command line we can connect from mysql with the credentials we set in opensips.cfg. To be sure we put back the initial opensips.cfg comming with the sources, changed the db credentials to ours and still receive this error. Do you have any suggestion? Thanks, Liviu ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Dispatcher module setting to probing
Try something like this
if (t_check_status(486|408) t_local_replied(all)) {
On Fri, Jun 10, 2011 at 4:52 AM, Pete Kelly pke...@gmail.com wrote:
I am testing with the dispatcher module at the moment, one of the options
is to set the probing mode to 1 which means the module will automatically
disable a gateway if it receives a 408.
Is it possible to make this only set to probing if a *locally* generated
408 is received? At the moment it disables even if the downstream gateway
returns a 408 which seems wrong to me. If the gateway has responded then it
is not inactive.
The code looks like this but I am not sure if it's easy to derive if the
408 is locally generated from the tmcb_params
struct tmcb_params *ps
if(ds_probing_mode==1 ps-code == 408)
{
if (ds_set_state(group, uri, DS_PROBING_DST, 1) != 0)
{
LM_ERR(Setting the probing state failed (%.*s,
group %d)\n,
uri.len, uri.s, group);
}
}
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Robert
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
