Revision: 5911
http://openser.svn.sourceforge.net/openser/?rev=5911&view=rev
Author: henningw
Date: 2009-08-11 15:22:17 +0000 (Tue, 11 Aug 2009)
Log Message:
-----------
- fix stupid bug related to the (legacy..) prime_route function
Modified Paths:
--------------
branches/1.4/modules/carrierroute/carrierroute.c
branches/1.5/modules/carrierroute/carrierroute.c
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
sobomax 2009/08/11 01:24:06 CEST
SER CVS Repository
Modified files:
. main.c rtpp_command.c rtpp_defines.h
rtpp_network.c rtpp_network.h
Log:
Introduce automatic bridging functionality. The way it works is that
the RTPproxy expects signalling layer (B2BUA, Sip Proxy etc) to let it
know either local IP for media or remote IP for this particular call
leg. If the local IP is specified, then it will be used verbatim,
otherwise the local address will be determined automatically based
on remote IP and result of dummy connect(2)/getsockname(2) calls.
Both IPv6 and IPv4 addresses are supported.
Internally feature is implemented as an extension to the U/L command.
option "l" should be used for local addresses, or option "r" for remote,
with IPv6 address enclosed into square brackets. For example:
Ul[abcd:efgh:0:1] callid remote_ip remote_port fromtag
Lr1.2.3.4 callid remote_ip remote_port fromtag totag
Changes to OpenSIPS, Kamalio/SER and Sippy B2BUA are to follow.
Sponsored by: Evision GmbH
Revision Changes Path
1.92 +8 -8 rtpproxy/main.c
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/rtpproxy/main.c.diff?r1=1.91&…
1.29 +76 -6 rtpproxy/rtpp_command.c
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/rtpproxy/rtpp_command.c.diff?…
1.27 +7 -1 rtpproxy/rtpp_defines.h
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/rtpproxy/rtpp_defines.h.diff?…
1.16 +97 -2 rtpproxy/rtpp_network.c
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/rtpproxy/rtpp_network.c.diff?…
1.21 +8 -2 rtpproxy/rtpp_network.h
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/rtpproxy/rtpp_network.h.diff?…
Module: sip-router
Branch: master
Commit: 20747a3a7ce264b8f6bef5e79d2d49ba107c6259
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=20747a3…
Author: Jan Janak <jan(a)iptel.org>
Committer: Jan Janak <jan(a)iptel.org>
Date: Fri Aug 7 14:19:36 2009 +0200
auth_identity: Add -lrt and -ldap to the list of libraries
Two more libraries are needed when compiling auth_identity module
statically, -lrt and -lldap.
Reported by MÉSZÁROS Mihály <misi(a)niif.hu>
---
modules_s/auth_identity/Makefile | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/modules_s/auth_identity/Makefile b/modules_s/auth_identity/Makefile
index 9828cbe..f4974b0 100644
--- a/modules_s/auth_identity/Makefile
+++ b/modules_s/auth_identity/Makefile
@@ -13,7 +13,7 @@ LIBS+= -L$(LOCALBASE)/lib -L$(LOCALBASE)/ssl/lib -lssl -lcrypto -lcurl
#
# Static linking, if you'd like to use TLS and AUTH_IDENTITY at the same time
#
-#LIBS+= /usr/lib/libcurl.a /usr/lib/libssl.a /usr/lib/libcrypto.a -lkrb5 -lidn -lz -lgssapi_krb5
+#LIBS+= /usr/lib/libcurl.a /usr/lib/libssl.a /usr/lib/libcrypto.a -lkrb5 -lidn -lz -lgssapi_krb5 -lrt -lldap
DEFS+=-DSER_MOD_INTERFACE
Hi, does/will SR implement TEL URI properly? This is: OpenSer/Kamailio doesn't
support it (just a very basic support).
Also, some useful funtions would be:
- "is_sip?": returns true if RURI has SIP URI.
- "is_sips?": returns true if RURI has SIPS URI.
- "is_sip_ips?": returns true if RURI has SIP or SIPS URI.
- "is_tel?": returns true if RURI has TEL URI.
Regards.
--
Iñaki Baz Castillo <ibc(a)aliax.net>
Revision: 5910
http://openser.svn.sourceforge.net/openser/?rev=5910&view=rev
Author: henningw
Date: 2009-08-06 17:08:30 +0000 (Thu, 06 Aug 2009)
Log Message:
-----------
- fix error in auth_db documentation for calc_ha1 parameter
Modified Paths:
--------------
branches/1.3/modules/auth_db/README
branches/1.3/modules/auth_db/doc/auth_db_user.sgml
branches/1.4/modules/auth_db/README
branches/1.4/modules/auth_db/doc/auth_db_admin.xml
branches/1.5/modules/auth_db/README
branches/1.5/modules/auth_db/doc/auth_db_admin.xml
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Revision: 5909
http://openser.svn.sourceforge.net/openser/?rev=5909&view=rev
Author: anomarme
Date: 2009-08-05 11:34:36 +0000 (Wed, 05 Aug 2009)
Log Message:
-----------
- fix memory leak
Modified Paths:
--------------
branches/1.5/modules/rls/notify.c
branches/1.5/modules/rls/resource_notify.c
branches/1.5/modules/rls/subscribe.c
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Revision: 5908
http://openser.svn.sourceforge.net/openser/?rev=5908&view=rev
Author: anomarme
Date: 2009-08-04 15:47:21 +0000 (Tue, 04 Aug 2009)
Log Message:
-----------
- fixed supported header name
Modified Paths:
--------------
branches/1.5/modules/rls/subscribe.c
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
Hello,
I committed in branch tmp/core_events a simple framework to execute
callbacks by core in various cases. So far there are two defined events:
for network data in and data out.
I used it for implementing a topo-hiding module that is transparent for
script writer and cope with stateless/stateful module in the same way.
Now, about the new event framework.
The core stores a structure with pointers to event manager callbacks.
typedef int (*sr_event_cb_f)(void *data);
typedef struct sr_event_cb {
sr_event_cb_f net_data_in;
sr_event_cb_f net_data_out;
} sr_event_cb_t;
The event manager can be implemented elsewhere, but the execution of
call manager and implementation must be very tied. The event manager
callback gets only one parameter, which is a void* and is specific per
event, thus the implementation must know what is the content.
So far, only one listener is needed for network data in/out events, thus
the event manager does the processing, but if the event should trigger
more functions from different parts of code, then the manager must take
of handling them (registration, execution, etc...).
You can download the branch and test the topoh module. It will be merged
once we discuss and decide whether the new core events framework is the
best for now, if something is missing, a.s.o.
Feedback is very much appreciated.
Cheers,
Daniel
--
Daniel-Constantin Mierla
* SIP Router Bootcamp
* Kamailio (OpenSER) and Asterisk Training
* Berlin, Germany, Sep 1-4, 2009
* http://www.asipto.com/index.php/sip-router-bootcamp/