Hi,
I am trying to enable the app_python module in Kamailio to run a simple python script externally parallel with Kamailio proxy,
While I try to load the module "app_python.so" in configuration file, the Kamailio server fails to start.. I can't see what is the problem ..
The steps, I am following are that:
- Script written in python saved in home directory.
- Loadmodule "app_python.so" statement in configuration file.
- Modparam("app_python", "script_name", "location of script")
- Python_exec("function", "parameters list") ..
I have also tried to check the Kamailio configuration option, It gives following warning,
0(2942) WARNING: <core> [sr_module.c:584]: /usr/local/lib64/kamailio/modules/app_python.so: exports dlflags interface is deprecated and it will not be supported in newer versions; consider using mod_register() instead
I am wandering if any one can please help in this matter, I shall be very thankful ..
With many thanks ..
Kind Regards,
Nasir
Muhammad Nasir Bhutta
Solutions Architect
Britannic Technologies Ltd
t: +44 1483 544812
f: +44 845 0501001
mbhutta(a)btlnet.co.uk<mailto:mbhutta@btlnet.co.uk>
www.btlnet.co.uk<http://www.btlnet.co.uk>
[cid:image001.jpg@01CC881F.1EA78300]<http://www.linkedin.com/company/britannic-technologies/products>[cid:image002.jpg@01CC881F.1EA78300]<http://www.twitter.com/BritannicTech>[cid:image003.jpg@01CC881F.1EA78300]<http://www.facebook.com/pages/Britannic-Technologies/202957249732198>[cid:image004.jpg@01CC881F.1EA78300]<http://www.youtube.com/user/BritannicTech>
________________________________
[cid:image007.jpg@01CC881F.4A995BF0]<http://www.btlnet.co.uk/>
Watch the Telegraph Business Club video about Britannic at our educational TV site - britannictech.tv<http://britannictech.tv>
Our 8th Annual Convergence Summit is being held at Silverstone on 17th November 2011. Book your place now<http://www.btlnet.co.uk/news--events/2011/convergence-summit-2011/register> and discover the world of Hosting and Cloud Services.
________________________________
This email and any files transmitted with it are confidential and intended for the addressee only. If you are not the intended recipient please notify the sender and delete this email. The views expressed in this email are personal, and do not constitute a commitment by Britannic Technologies Ltd unless specified by a separate, written agreement.
Registered Office: Britannic House, Merrow Business Park, Guildford, Surrey GU4 7WA. Registered in England no. 2090797.
________________________________
On Wednesday 12 October 2011, Miklos Tirpak wrote:
> Module: sip-router
> Branch: master
> [...]
> message shooter module added
Hi Miklos,
did you planned to add this to the master branch? IMHO we're still in the
feature freeze for 3.2 and want to release soon. Maybe you can add this to a
branch for now?
Best regards,
Henning
Hi!
Carsten, Jason, I wonder what is the main motivation for you to have IMS
components?
Are you using Kamailio in an mobile operator environment and thus have
to support all the IMS interfaces, or do you plan to use those modules
also in "normal" VoIP provider scenarios (benefits?)
Thanks
Klaus
Hi,
i just noticed, that the names of the Parameters for CDR-Generation
(for the Kamailio-ACC module) arent up-to-date (both docbook and
readme).
According to Docs: "cdr_start_when_confirmed", According to acc_mod.c:
"cdr_start_on_confirmed"According to Docs: "cdr_log_extra", According
to acc_mod.c: "cdr_extra"According to Docs: "cdr_log_facility",
According to acc_mod.c: "cdr_facility"
I don't know, if either the docs or the module should be changed; so
that's why i leave this to the developers.
Kind regards,Carsten Bock
--
Carsten Bock
CEO (Geschäftsführer)
ng-voice GmbH i. Gr.
Schomburgstr. 80
D-22767 Hamburg / Germany
http://www.ng-voice.com
mailto:carsten@ng-voice.com
Mobile +49 179 2021244
Office +49 40 34927219
Fax +49 40 34927220
Hier finden Sie unsere handelsrechtlichen Pflichtangaben:
http://www.ng-voice.com/imprint/
Module: sip-router
Branch: master
Commit: 8c9681ac3ba42287b060fc1b5472cbac7d579cb8
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=8c9681a…
Author: Alexandr Dubovikov <alexandr.dubovikov(a)gmail.com>
Committer: Alexandr Dubovikov <alexandr.dubovikov(a)gmail.com>
Date: Tue Oct 11 15:51:12 2011 +0200
modules:sipcapture: IPIP raw socket has moved to the sipcapture.
fixed source(from) structure in IPIP mode
fixed port and port range in monitoring/ipip mode.
---
modules/sipcapture/README | 30 +++++---
modules/sipcapture/doc/sipcapture_admin.xml | 20 ++++-
modules/sipcapture/sipcapture.c | 114 ++++++++++++++++++---------
3 files changed, 112 insertions(+), 52 deletions(-)
Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=8c9…
Hi, Internet is changing and now devices which are sporadically
connected (TCP) are very common. I mean, of course, movile devices.
RFC 5626 (AKA "Outbound) is the solution for those scenarios under SIP
protocol. Features of RFC 5626:
- NAT solved (at signaling level) without hacks in the proxy side (no
more "Contact" replacements, please).
- Allow re-registration of a client (after loosing the TCP connection)
by indicating the registrar to replace the previous binding with the
new one (for this, a Contact param ";+sip.instance" and ";reg-id" are
used). Avoid mantaining dozens of unreachable registration bindings in
the registrar.
- RFC 5626 is for clients, outbound proxies ("edge proxies") and
registrars (which could be behind the edge(s) proxy). Path support is
required in both the edge proxy and registrar (already implemented in
Kamailio!).
- If the registrar tries to route a request to a client registered
using RFC 5626 and it gets a connection error or timeout, the
registrar MUST remove such binding.
- If the registrar tries to route a request to a client registered
though an outbound/edge proxy and receives a "430 Flow Failed", the
registrar MUST remove such binding.
- The client could mantain two different registrations (by using two
separate edge proxies that route the REGISTER to the same registrar
behind them). Both registration have the same ";+sip.instance" value
but different ";reg-id" value. When the registrar (or inbound proxy)
has to route a request to that AoR, and in case there are various
bindings with same ";+sip.instance", it just tries the one with lowest
";reg-id" value. If it fails (430 "Flow Failed" replied by the edge
proxy) it would try the next one. Yeah, failover for incoming calls, a
cool and *needed* feature now.
- When a UAC sends a REGISTER announcing support for RFC 5626
("Supported: outbound"), the binding matching changes: Now the
registrar must check for other bindings with same ";+sip.instance"
rather than matching the Contact URI (which is useless as the client
is supposed to be natted).
Some other collateral changes needed for the above to work properly:
- 430 status code MUST have less priority than any other 4XX response
since such 430 response can only be replied by edge proxies and means
"the TCP/TLS connection with the user is closed".
- We need two new fields in the registration backend for storing the
";+sip.instance" and ";reg-id" param.
- When a TCP connection is made from a client, Kamailio has to create
a flow token identifier for such connection.
- We need a new "loose_route_outbound()" function that adds a
Record-Route whose URI username matches the flow token associated to
the connection from which the request comes.
- When a request arrives to Kamailio and contains a Route header
pointing to us and containing a Route with username, then Kamailio
must inspect the URI username to know which connection to use for
routing such request (don't trust the RURI as it would be the private
URI of a Contact header). Don't mangle the Contact header please, no
more request/response mangling.
- Summarizing, RFC 5626 requires additions to:
- registrar module
- location module
- rr module
So, RFC 5626 is the solution for lot of common problems today and IMHO
it's a good specification. Many devices are already implementing them.
Let's forget the "Contact mangling" hacks and other not-so-ellegant
solutions already present in Kamailio/SIP-Router for this purpose. RFC
5626 was published in October 2009, it's not a new and exotic
specification.
Is there interest in implementing this? I know the specification and could help.
Cheers.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#166 - CDR generation from acc module doesn't show label
User who did this - Sven Knoblich (sknoblich)
Reason for closing: Fixed
Additional comments about closing: fixed with commit:
d22d6d3f57d2fde13456eb365f42fd035980faed
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=166
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.