Re: [OpenSIPS-Users] B2B module and CANCEL
Hi Denis, We hit this problem also some time ago, it was indeed a bug when applying lumps in local_route. We were just waiting for the fix to get enough testing. It is stable now. I have just committed the fix in tm module in both trunk and 1.6. Please upgrade and check. Regards, Anca On 06/14/2011 06:57 AM, Denis Putyato wrote: Hello I found that this problem appears when I use append_hf() to add some header in local route of the proxy1 before sending INVITE to proxy2. Without this adding problem disappears. *From:*users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] *On Behalf Of *Denis Putyato *Sent:* Friday, June 10, 2011 5:52 PM *To:* 'OpenSIPS users mailling list' *Subject:* [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. ___ 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] LB resources are not getting released after the call ends.
Dear All, I am trying to use OpenSIPs LB, but dont know where I am making mistake. Initially the LB works, will connect calls( connected calls== no. of total resources allotted). after that when I try to make new calls(old calls are disconnected) it keeps on trying but calls are not connected until unless I restart the OpenSIPs. Here is the LB list usage, you can see right now load for both the services are maximum though there is no call in opensips. root@opensips:~# opensipsctl fifo lb_list database engine 'MYSQL' loaded Control engine 'FIFO' loaded entering fifo_cmd lb_list Destination:: sip:OpenSIPs@x.x.x.36 id=1 group=2 enabled=yes auto-re=on Resource:: sip max=1 load=1 Destination:: sip:OpenSIPs@x.x.x.37 id=2 group=2 enabled=yes auto-re=on Resource:: sip max=4 load=4 FIFO command was: :lb_list:opensips_receiver_5197 What can be done to release the resources after the call disconnects. -- Regards Tushar Jain two roads diverged in a wood, and I - I took the one less traveled by, and that has made all the difference --Robert Frost ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] 'RROR: database engine not loaded - tried 'MYSQL
Hello, I'm having some problems with opensips [root@siproxy-slimpia opensips]# opensipsctl add 1000 1000 : command not foundipsctlrc: line 8: : command not foundipsctlrc: line 11: : command not foundipsctlrc: line 14: : command not foundipsctlrc: line 20: : command not foundipsctlrc: line 23: : command not foundipsctlrc: line 26: : command not foundipsctlrc: line 29: : command not foundipsctlrc: line 32: : command not foundipsctlrc: line 35: : command not foundipsctlrc: line 38: : command not foundipsctlrc: line 41: : command not foundipsctlrc: line 44: : command not foundipsctlrc: line 47: : command not foundipsctlrc: line 48: : command not foundipsctlrc: line 53: : command not foundipsctlrc: line 60: : command not foundipsctlrc: line 61: : command not foundipsctlrc: line 64: : command not foundipsctlrc: line 67: : command not foundipsctlrc: line 70: : command not foundipsctlrc: line 73: : command not foundipsctlrc: line 74: : command not foundipsctlrc: line 79: : command not foundipsctlrc: line 82: : command not foundipsctlrc: line 85: : command not foundipsctlrc: line 90: : command not foundipsctlrc: line 95: : command not foundipsctlrc: line 98: : command not foundipsctlrc: line 99: : command not foundipsctlrc: line 103: : command not foundipsctlrc: line 107: : command not foundipsctlrc: line 110: : command not foundipsctlrc: line 116: : command not foundipsctlrc: line 119: : command not foundipsctlrc: line 123: : command not foundipsctlrc: line 126: : command not foundipsctlrc: line 130: : command not foundipsctlrc: line 134: : command not foundnsipsctlrc: line 8: : command not foundnsipsctlrc: line 11: : command not foundnsipsctlrc: line 14: : command not foundnsipsctlrc: line 20: : command not foundnsipsctlrc: line 23: : command not foundnsipsctlrc: line 26: : command not foundnsipsctlrc: line 29: : command not foundnsipsctlrc: line 32: : command not foundnsipsctlrc: line 35: : command not foundnsipsctlrc: line 38: : command not foundnsipsctlrc: line 41: : command not foundnsipsctlrc: line 44: : command not foundnsipsctlrc: line 47: : command not foundnsipsctlrc: line 48: : command not foundnsipsctlrc: line 53: : command not foundnsipsctlrc: line 60: : command not foundnsipsctlrc: line 61: : command not foundnsipsctlrc: line 64: : command not foundnsipsctlrc: line 67: : command not foundnsipsctlrc: line 70: : command not foundnsipsctlrc: line 73: : command not foundnsipsctlrc: line 74: : command not foundnsipsctlrc: line 79: : command not foundnsipsctlrc: line 82: : command not foundnsipsctlrc: line 85: : command not foundnsipsctlrc: line 90: : command not foundnsipsctlrc: line 95: : command not foundnsipsctlrc: line 98: : command not foundnsipsctlrc: line 99: : command not foundnsipsctlrc: line 103: : command not foundnsipsctlrc: line 107: : command not foundnsipsctlrc: line 110: : command not foundnsipsctlrc: line 116: : command not foundnsipsctlrc: line 119: : command not foundnsipsctlrc: line 123: : command not foundnsipsctlrc: line 126: : command not foundnsipsctlrc: line 130: : command not foundnsipsctlrc: line 134: 'ARNING: database engine not found - tried 'MYSQL ERROR: This command requires a database engine - none was loaded You have new mail in /var/spool/mail/root What is happening? db_mysql is loaded, opensipsctlrc has DBENGINE=MYSQL... Hope you can help ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] how to set openxcap port
Hello, I'm trying to set port for OpenXCAP (80 is used by Apache) by: address = 80.97.161.39:8000 In the syslog I receive error: fatal error: failed to create OpenXCAP 2.0.1: Couldn't listen on 80.97.161.39:8000:80: [Errno -5] No address associated with hostname. Since no distinct entry in config.ini for the port I don't know how to set up the port. Thanks, Liviu___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] B2B module and CANCEL
Hi Denis, Sorry, I have to make a correction - I forgot that the fix that is committed on svn is partial and works only if body lumps are applied. So your case will still not work and needs another fix. I suggest you to open a bug report in svn. Regards, Anca On 06/14/2011 02:35 PM, Anca Vamanu wrote: Hi Denis, We hit this problem also some time ago, it was indeed a bug when applying lumps in local_route. We were just waiting for the fix to get enough testing. It is stable now. I have just committed the fix in tm module in both trunk and 1.6. Please upgrade and check. Regards, Anca On 06/14/2011 06:57 AM, Denis Putyato wrote: Hello I found that this problem appears when I use append_hf() to add some header in local route of the proxy1 before sending INVITE to proxy2. Without this adding problem disappears. *From:*users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] *On Behalf Of *Denis Putyato *Sent:* Friday, June 10, 2011 5:52 PM *To:* 'OpenSIPS users mailling list' *Subject:* [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. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] 'RROR: database engine not loaded - tried 'MYSQL
Bw, on my opensips logs i see this messages every 10 seconds Jun 14 14:25:01 siproxy /sbin/opensips[4991]: DBG:mi_fifo:mi_parse_tree: adding node ; val all Jun 14 14:25:01 siproxy /sbin/opensips[4991]: DBG:mi_fifo:mi_parse_node: end of input tree Jun 14 14:25:01 siproxy /sbin/opensips[4991]: DBG:mi_fifo:mi_fifo_server: done parsing the mi tree 2011/6/14 Toyima Dias toyim...@gmail.com Hello, I'm having some problems with opensips [root@siproxy-slimpia opensips]# opensipsctl add 1000 1000 : command not foundipsctlrc: line 8: : command not foundipsctlrc: line 11: : command not foundipsctlrc: line 14: : command not foundipsctlrc: line 20: : command not foundipsctlrc: line 23: : command not foundipsctlrc: line 26: : command not foundipsctlrc: line 29: : command not foundipsctlrc: line 32: : command not foundipsctlrc: line 35: : command not foundipsctlrc: line 38: : command not foundipsctlrc: line 41: : command not foundipsctlrc: line 44: : command not foundipsctlrc: line 47: : command not foundipsctlrc: line 48: : command not foundipsctlrc: line 53: : command not foundipsctlrc: line 60: : command not foundipsctlrc: line 61: : command not foundipsctlrc: line 64: : command not foundipsctlrc: line 67: : command not foundipsctlrc: line 70: : command not foundipsctlrc: line 73: : command not foundipsctlrc: line 74: : command not foundipsctlrc: line 79: : command not foundipsctlrc: line 82: : command not foundipsctlrc: line 85: : command not foundipsctlrc: line 90: : command not foundipsctlrc: line 95: : command not foundipsctlrc: line 98: : command not foundipsctlrc: line 99: : command not foundipsctlrc: line 103: : command not foundipsctlrc: line 107: : command not foundipsctlrc: line 110: : command not foundipsctlrc: line 116: : command not foundipsctlrc: line 119: : command not foundipsctlrc: line 123: : command not foundipsctlrc: line 126: : command not foundipsctlrc: line 130: : command not foundipsctlrc: line 134: : command not foundnsipsctlrc: line 8: : command not foundnsipsctlrc: line 11: : command not foundnsipsctlrc: line 14: : command not foundnsipsctlrc: line 20: : command not foundnsipsctlrc: line 23: : command not foundnsipsctlrc: line 26: : command not foundnsipsctlrc: line 29: : command not foundnsipsctlrc: line 32: : command not foundnsipsctlrc: line 35: : command not foundnsipsctlrc: line 38: : command not foundnsipsctlrc: line 41: : command not foundnsipsctlrc: line 44: : command not foundnsipsctlrc: line 47: : command not foundnsipsctlrc: line 48: : command not foundnsipsctlrc: line 53: : command not foundnsipsctlrc: line 60: : command not foundnsipsctlrc: line 61: : command not foundnsipsctlrc: line 64: : command not foundnsipsctlrc: line 67: : command not foundnsipsctlrc: line 70: : command not foundnsipsctlrc: line 73: : command not foundnsipsctlrc: line 74: : command not foundnsipsctlrc: line 79: : command not foundnsipsctlrc: line 82: : command not foundnsipsctlrc: line 85: : command not foundnsipsctlrc: line 90: : command not foundnsipsctlrc: line 95: : command not foundnsipsctlrc: line 98: : command not foundnsipsctlrc: line 99: : command not foundnsipsctlrc: line 103: : command not foundnsipsctlrc: line 107: : command not foundnsipsctlrc: line 110: : command not foundnsipsctlrc: line 116: : command not foundnsipsctlrc: line 119: : command not foundnsipsctlrc: line 123: : command not foundnsipsctlrc: line 126: : command not foundnsipsctlrc: line 130: : command not foundnsipsctlrc: line 134: 'ARNING: database engine not found - tried 'MYSQL ERROR: This command requires a database engine - none was loaded You have new mail in /var/spool/mail/root What is happening? db_mysql is loaded, opensipsctlrc has DBENGINE=MYSQL... Hope you can help ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] MSRPRelay start error
Hello, I installed MSRP 1.0.6 with apt-get install ... as stated in the last mail received from ag-projects.com. The server does not start and in the syslog I found: Jun 14 18:24:53 P4302 msrprelay[3553]: Starting MSRP Relay 1.0.5 Jun 14 18:24:53 P4302 msrprelay[3553]: error: /usr/local/lib/python2.6/dist-packages/application/python/util.py:18: DeprecationWarning: importing Singleton from application.pyhton.util has been deprecated and will be removed in version 1.3.0. Singleton has been moved to application.python.types Jun 14 18:24:53 P4302 msrprelay[3553]: error: warnings.warn(importing Singleton from application.pyhton.util has been deprecated and will be removed in version 1.3.0. Singleton has been moved to application.python.types, DeprecationWarning) Jun 14 18:24:53 P4302 msrprelay[3553]: fatal error: failed to create MSRP Relay: cannot import name default_host_ip Jun 14 18:24:53 P4302 msrprelay[3553]: Traceback (most recent call last): Jun 14 18:24:53 P4302 msrprelay[3553]: File /usr/bin/msrprelay, line 60, in module Jun 14 18:24:53 P4302 msrprelay[3553]: from msrp.relay import Relay Jun 14 18:24:53 P4302 msrprelay[3553]: File /usr/local/lib/python2.6/dist-packages/msrp/relay.py, line 27, in module Jun 14 18:24:53 P4302 msrprelay[3553]: from application.system import default_host_ip Jun 14 18:24:53 P4302 msrprelay[3553]: ImportError: cannot import name default_host_ip If I make in python: import smrp print msrp.__version__ then 1.0.5 is displayed. Can you suggest what to do? version wasn't updated from sources? Or should I install from tar sources instead of apt-get install... Thanks, Liviu ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] 'RROR: database engine not loaded - tried 'MYSQL
I think this is also important: *#opensipsctl fifo ps 'ARNING: database engine not found - tried 'MYSQL ERROR: Error opening OpenSIPS's FIFO /tmp/opensips_fifo )' in your configou have the line 'modparam(mi_fifo, fifo_name, /tmp/opensips_fifo ERROR: and also have loaded the mi_fifo module.* On my opensips.cfg i have: *modparam(mi_fifo, fifo_name, /tmp/opensips_fifo) modparam(mi_fifo, fifo_mode, 0666)* * On my opensipsctlrc: SIP_DOMAIN=172.30.140.20 DBENGINE=MYSQL DBHOST=localhost DBNAME=opensips DBRWUSER=opensips DBRWPW=opensipsrw DBROUSER=opensipsro DBROPW=opensipsro DBROOTUSER=root INSTALL_EXTRA_TABLES=ask INSTALL_PRESENCE_TABLES=ask ALIASES_TYPE=DB OSIPS_FIFO=/tmp/opensips_fifo * 2011/6/14 Toyima Dias toyim...@gmail.com Bw, on my opensips logs i see this messages every 10 seconds Jun 14 14:25:01 siproxy /sbin/opensips[4991]: DBG:mi_fifo:mi_parse_tree: adding node ; val all Jun 14 14:25:01 siproxy /sbin/opensips[4991]: DBG:mi_fifo:mi_parse_node: end of input tree Jun 14 14:25:01 siproxy /sbin/opensips[4991]: DBG:mi_fifo:mi_fifo_server: done parsing the mi tree 2011/6/14 Toyima Dias toyim...@gmail.com Hello, I'm having some problems with opensips [root@siproxy-slimpia opensips]# opensipsctl add 1000 1000 : command not foundipsctlrc: line 8: : command not foundipsctlrc: line 11: : command not foundipsctlrc: line 14: : command not foundipsctlrc: line 20: : command not foundipsctlrc: line 23: : command not foundipsctlrc: line 26: : command not foundipsctlrc: line 29: : command not foundipsctlrc: line 32: : command not foundipsctlrc: line 35: : command not foundipsctlrc: line 38: : command not foundipsctlrc: line 41: : command not foundipsctlrc: line 44: : command not foundipsctlrc: line 47: : command not foundipsctlrc: line 48: : command not foundipsctlrc: line 53: : command not foundipsctlrc: line 60: : command not foundipsctlrc: line 61: : command not foundipsctlrc: line 64: : command not foundipsctlrc: line 67: : command not foundipsctlrc: line 70: : command not foundipsctlrc: line 73: : command not foundipsctlrc: line 74: : command not foundipsctlrc: line 79: : command not foundipsctlrc: line 82: : command not foundipsctlrc: line 85: : command not foundipsctlrc: line 90: : command not foundipsctlrc: line 95: : command not foundipsctlrc: line 98: : command not foundipsctlrc: line 99: : command not foundipsctlrc: line 103: : command not foundipsctlrc: line 107: : command not foundipsctlrc: line 110: : command not foundipsctlrc: line 116: : command not foundipsctlrc: line 119: : command not foundipsctlrc: line 123: : command not foundipsctlrc: line 126: : command not foundipsctlrc: line 130: : command not foundipsctlrc: line 134: : command not foundnsipsctlrc: line 8: : command not foundnsipsctlrc: line 11: : command not foundnsipsctlrc: line 14: : command not foundnsipsctlrc: line 20: : command not foundnsipsctlrc: line 23: : command not foundnsipsctlrc: line 26: : command not foundnsipsctlrc: line 29: : command not foundnsipsctlrc: line 32: : command not foundnsipsctlrc: line 35: : command not foundnsipsctlrc: line 38: : command not foundnsipsctlrc: line 41: : command not foundnsipsctlrc: line 44: : command not foundnsipsctlrc: line 47: : command not foundnsipsctlrc: line 48: : command not foundnsipsctlrc: line 53: : command not foundnsipsctlrc: line 60: : command not foundnsipsctlrc: line 61: : command not foundnsipsctlrc: line 64: : command not foundnsipsctlrc: line 67: : command not foundnsipsctlrc: line 70: : command not foundnsipsctlrc: line 73: : command not foundnsipsctlrc: line 74: : command not foundnsipsctlrc: line 79: : command not foundnsipsctlrc: line 82: : command not foundnsipsctlrc: line 85: : command not foundnsipsctlrc: line 90: : command not foundnsipsctlrc: line 95: : command not foundnsipsctlrc: line 98: : command not foundnsipsctlrc: line 99: : command not foundnsipsctlrc: line 103: : command not foundnsipsctlrc: line 107: : command not foundnsipsctlrc: line 110: : command not foundnsipsctlrc: line 116: : command not foundnsipsctlrc: line 119: : command not foundnsipsctlrc: line 123: : command not foundnsipsctlrc: line 126: : command not foundnsipsctlrc: line 130: : command not foundnsipsctlrc: line 134: 'ARNING: database engine not found - tried 'MYSQL ERROR: This command requires a database engine - none was loaded You have new mail in /var/spool/mail/root What is happening? db_mysql is loaded, opensipsctlrc has DBENGINE=MYSQL... Hope you can help ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] MSRPRelay start error
Latest msrprelay version is 1.0.6 and the dependencies are listed here:
package_requirements = {'python-application': '1.2.8',
'python-gnutls': '1.1.8',
'twisted':'2.5.0'}
You seem to be running an old version probably you have installed it manually.
Adrian
On Jun 14, 2011, at 2:32 PM, Barsan Liviu wrote:
Hello,
I installed MSRP 1.0.6 with apt-get install ... as stated in the last mail
received from ag-projects.com.
The server does not start and in the syslog I found:
Jun 14 18:24:53 P4302 msrprelay[3553]: Starting MSRP Relay 1.0.5
Jun 14 18:24:53 P4302 msrprelay[3553]: error:
/usr/local/lib/python2.6/dist-packages/application/python/util.py:18:
DeprecationWarning: importing Singleton from application.pyhton.util has been
deprecated and will be removed in version 1.3.0. Singleton has been moved to
application.python.types
Jun 14 18:24:53 P4302 msrprelay[3553]: error: warnings.warn(importing
Singleton from application.pyhton.util has been deprecated and will be
removed in version 1.3.0. Singleton has been moved to
application.python.types, DeprecationWarning)
Jun 14 18:24:53 P4302 msrprelay[3553]: fatal error: failed to create MSRP
Relay: cannot import name default_host_ip
Jun 14 18:24:53 P4302 msrprelay[3553]: Traceback (most recent call last):
Jun 14 18:24:53 P4302 msrprelay[3553]: File /usr/bin/msrprelay, line 60,
in module
Jun 14 18:24:53 P4302 msrprelay[3553]: from msrp.relay import Relay
Jun 14 18:24:53 P4302 msrprelay[3553]: File
/usr/local/lib/python2.6/dist-packages/msrp/relay.py, line 27, in module
Jun 14 18:24:53 P4302 msrprelay[3553]: from application.system import
default_host_ip
Jun 14 18:24:53 P4302 msrprelay[3553]: ImportError: cannot import name
default_host_ip
If I make in python:
import smrp
print msrp.__version__
then 1.0.5 is displayed.
Can you suggest what to do? version wasn't updated from sources? Or should I
install from tar sources instead of apt-get install...
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] B2B module and CANCEL
Hello Anca I opened bug report on bug tracker Thank you for help From: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] On Behalf Of Anca Vamanu Sent: Tuesday, June 14, 2011 4:25 PM To: users@lists.opensips.org Subject: Re: [OpenSIPS-Users] B2B module and CANCEL Hi Denis, Sorry, I have to make a correction - I forgot that the fix that is committed on svn is partial and works only if body lumps are applied. So your case will still not work and needs another fix. I suggest you to open a bug report in svn. Regards, Anca On 06/14/2011 02:35 PM, Anca Vamanu wrote: Hi Denis, We hit this problem also some time ago, it was indeed a bug when applying lumps in local_route. We were just waiting for the fix to get enough testing. It is stable now. I have just committed the fix in tm module in both trunk and 1.6. Please upgrade and check. Regards, Anca On 06/14/2011 06:57 AM, Denis Putyato wrote: Hello I found that this problem appears when I use append_hf() to add some header in local route of the proxy1 before sending INVITE to proxy2. Without this adding problem disappears. From: users-boun...@lists.opensips.org [mailto:users-boun...@lists.opensips.org] On Behalf Of Denis Putyato Sent: Friday, June 10, 2011 5:52 PM To: 'OpenSIPS users mailling list' Subject: [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. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] MSRPRelay start error
Hello,
Indeed an 1.0.5 MSRPRelay was first time installed and this was started
instead
of 1.0.6. Deleting the files manually then re-install with apt-get install ...
worked.
Thanks,
Liviu
From: Adrian Georgescu a...@ag-projects.com
To: OpenSIPS users mailling list users@lists.opensips.org
Sent: Tue, June 14, 2011 3:57:36 PM
Subject: Re: [OpenSIPS-Users] MSRPRelay start error
Latest msrprelay version is 1.0.6 and the dependencies are listed here:
package_requirements = {'python-application': '1.2.8',
'python-gnutls': '1.1.8',
'twisted':'2.5.0'}
You seem to be running an old version probably you have installed it manually.
Adrian
On Jun 14, 2011, at 2:32 PM, Barsan Liviu wrote:
Hello,
I installed MSRP 1.0.6 with apt-get install ... as stated in the last mail
received from ag-projects.com.
The server does not start and in the syslog I found:
Jun 14 18:24:53 P4302 msrprelay[3553]: Starting MSRP Relay 1.0.5
Jun 14 18:24:53 P4302 msrprelay[3553]: error:
/usr/local/lib/python2.6/dist-packages/application/python/util.py:18:
DeprecationWarning: importing Singleton from application.pyhton.util has been
deprecated and will be removed in version 1.3.0. Singleton has been moved to
application.python.types
Jun 14 18:24:53 P4302 msrprelay[3553]: error: warnings.warn(importing
Singleton from application.pyhton.util has been deprecated and will be removed
in version 1.3.0. Singleton has been moved to application.python.types,
DeprecationWarning)
Jun 14 18:24:53 P4302 msrprelay[3553]: fatal error: failed to create MSRP
Relay:
cannot import name default_host_ip
Jun 14 18:24:53 P4302 msrprelay[3553]: Traceback (most recent call last):
Jun 14 18:24:53 P4302 msrprelay[3553]: File /usr/bin/msrprelay, line 60,
in
module
Jun 14 18:24:53 P4302 msrprelay[3553]: from msrp.relay import Relay
Jun 14 18:24:53 P4302 msrprelay[3553]: File
/usr/local/lib/python2.6/dist-packages/msrp/relay.py, line 27, in module
Jun 14 18:24:53 P4302 msrprelay[3553]: from application.system import
default_host_ip
Jun 14 18:24:53 P4302 msrprelay[3553]: ImportError: cannot import name
default_host_ip
If I make in python:
import smrp
print msrp.__version__
then 1.0.5 is displayed.
Can you suggest what to do? version wasn't updated from sources? Or should I
install from tar sources instead of apt-get install...
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] how to set openxcap port
Hello, I found myself the solution, by setting in the root=http://example.com:8080 Liviu From: Barsan Liviu bars...@yahoo.com To: Opensips UserList users@lists.opensips.org Sent: Tue, June 14, 2011 3:07:33 PM Subject: how to set openxcap port Hello, I'm trying to set port for OpenXCAP (80 is used by Apache) by: address = 80.97.161.39:8000 In the syslog I receive error: fatal error: failed to create OpenXCAP 2.0.1: Couldn't listen on 80.97.161.39:8000:80: [Errno -5] No address associated with hostname. Since no distinct entry in config.ini for the port I don't know how to set up the port. Thanks, Liviu___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] CDRTool billing of internal calls
Hi, We have setup CDRTool version 8.0.15 with an Asterisk multitenant PBX. We want to be able to log and bill the internal calls in CDRTool. All the calls are sent from Asterisk to OpenSIPS and the call is sent back to the same Asterisk on the same IP-address. If it´s a external call, there is no problem. The problem occurs when the called number is a local customer, then it can´t log or bill the call in CDRTool. From FreeRadius log: Acct-Status-Type = Failed Service-Type = Sip-Session Sip-Response-Code = 408 Sip-Method = Invite Event-Timestamp = Jun 14 2011 16:02:47 CEST Sip-From-Tag = as16538a8e Acct-Session-Id = 18375a0e058480f5626c94293975f7cf@x User-Name = a@x Calling-Station-Id = sip:a@x Called-Station-Id = sip:b@y Sip-Translated-Request-URI = sip:b@ip Source-IP = ip Source-Port = 5060 Billing-Party = sip:a@x Canonical-URI = sip:b@y User-Agent = Asterisk PBX Contact = sip:a@ip NAS-Port = 5060 Acct-Delay-Time = 0 NAS-IP-Address = 127.0.0.1 Acct-Unique-Session-Id = 89f0c9014ba0a2f9 Timestamp = 1308060167 Request-Authenticator = Verified Best regards, Tony Tyler ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] nathelper memory error
Hi, We are using OpenSIPs (opensips-1.4.3-tls yes I know we should upgrade...) and it seems that ever since we set db_mode to 3 we started getting the erros below: Jun 14 20:12:14 peter /sbin/opensips[4434]: ERROR:db_mysql:db_mysql_convert_rows: no private memory left Jun 14 20:12:15 peter /sbin/opensips[4434]: ERROR:nathelper:nh_timer: out of pkg memory Jun 14 20:12:16 peter /sbin/opensips[4434]: ERROR:nathelper:nh_timer: out of pkg memory Jun 14 20:12:20 peter /sbin/opensips[4434]: ERROR:nathelper:nh_timer: out of pkg memory Jun 14 20:12:51 peter /sbin/opensips[4434]: ERROR:nathelper:nh_timer: out of pkg memory We have fork set to 24 and modparam( usrloc, fetch_rows, 500 ). TIA. Dovid ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
