[OpenSIPS-Users] Media-dispatcher
Hello I have installed media-proxy 2.3.8 using http://www.smartvox.co.uk/serfaq_install_mediaproxy2.htm But when i start media-dispatcher/media-relay it gives following error [r...@users ~]# media-dispatcher Traceback (most recent call last): File /usr/bin/media-dispatcher, line 12, in ? from application.process import process, ProcessError File build/bdist.linux-i686/egg/application/process.py, line 12, in ? File build/bdist.linux-i686/egg/application/log/__init__.py, line 12, in ? File /usr/lib/python2.4/site-packages/python_application-1.2.1-py2.4.egg/application/log/extensions/twisted/__init__.py, line 4 SyntaxError: future feature absolute_import is not defined -- Regards, Chandrakant Solanki ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Media-dispatcher
Hi, On 31/12/09 9:52 AM, Chandrakant Solanki wrote: Hello I have installed media-proxy 2.3.8 using http://www.smartvox.co.uk/serfaq_install_mediaproxy2.htm But when i start media-dispatcher/media-relay it gives following error [r...@users ~]# media-dispatcher Traceback (most recent call last): File /usr/bin/media-dispatcher, line 12, in ? from application.process import process, ProcessError File build/bdist.linux-i686/egg/application/process.py, line 12, in ? File build/bdist.linux-i686/egg/application/log/__init__.py, line 12, in ? File /usr/lib/python2.4/site-packages/python_application-1.2.1-py2.4.egg/application/log/extensions/twisted/__init__.py, line 4 SyntaxError: future feature absolute_import is not defined Python 2.4 doesn't support absolute_import, it's only available from version 2.5 onwards, we should add a note on that, thanks for the pointer. However Python 2.4 is getting quite old now so you better upgrade to version 2.5 at least because at some future point Python 2.4 support will be dropped. Kind 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] Media-dispatcher
On Thursday 31 December 2009 09:24:51 Saúl Ibarra Corretgé wrote: However Python 2.4 is getting quite old now so you better upgrade to version 2.5 at least because at some future point Python 2.4 support will be dropped. Umm ... it had been dropped, since it doesn't run on python 2.4 ... so no will be dropped, better .. it had been dropped ... ;-) -- Raúl Alexis Betancor Santana Dimensión Virtual ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] re-REGISTER with To tag gets 404
Please, see RFC 3261 - Section 10.2: A REGISTER request does not establish a dialog -Victor On Wed, Dec 30, 2009 at 7:28 PM, Jeff Pyle jp...@fidelityvoice.com wrote: Hello, The default config of Opensips takes any packet with a To tag but that doesn't fall into the loose_route() category and responds with a 404 Not here. My config is based largely on the default one and contains this portion. I'm testing the SIP capabilities of a Mitel 5000 PBX. The initial registration is fine, but re-registrations contain To tag presented to the Mitel in the 200 OK of the initial registration. These re-registrations receive the 404 Not here response. Looking into RFC3261 I don't see anything specific to REGISTERs, only that (paraphrased) subsequent transactions within a dialog should contain the tags of the initial transaction. Is the Mitel doing something wrong according to the RFC, or is the default config mistreating this somehow? Should an exception be added for REGISTERs? Thanks, Jeff ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Victor Pascual Ávila ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] re-REGISTER with To tag gets 404
31 dec 2009 kl. 12.12 skrev Victor Pascual Avila: Please, see RFC 3261 - Section 10.2: A REGISTER request does not establish a dialog Right, but there are many servers that request that you reuse the same dialog identifiers as the challenged transaction when you authenticate. /O ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] re-REGISTER with To tag gets 404
Is there any danger in adapting the default config from:
if (has_totag()) {
...
}
to:
if (has_totag() !is_method(REGISTER)) {
...
}
- Jeff
On 12/31/09 7:46 AM, Olle E. Johansson o...@edvina.net wrote:
31 dec 2009 kl. 12.12 skrev Victor Pascual Avila:
Please, see RFC 3261 - Section 10.2: A REGISTER request does not
establish a dialog
Right, but there are many servers that request that you reuse the same dialog
identifiers as the challenged transaction when you authenticate.
/O
___
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] Need help to forward Access number
Hi, I want to forward an Access Number from OpenSIPS to Asterisk machine. Kindly advise how can i do that? Which modules/functions are use to forward by INVITE section? -- Regards, Ahmed Munir ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Need help to forward Access number
Rewrite Request URI ($ru) and t_relay(). -- Sent from mobile device On Jan 1, 2010, at 1:40 AM, Ahmed Munir ahmedmunir...@gmail.com wrote: Hi, I want to forward an Access Number from OpenSIPS to Asterisk machine. Kindly advise how can i do that? Which modules/functions are use to forward by INVITE section? -- Regards, Ahmed Munir ___ 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
