diameter-developers Mailing List for Open Diameter

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hello,
I am looking for a library to use Diamater as an authenticating server in apache, something exactly like the mod_auth_radius in apache. Is something like this exist ?

Thanx
Med

http://mymindovermatter.com/components/com_banners/models/Inacio.php

Thanks Mark....

Your reply helped.. we enquired the server guys.. and they registered our
node.
Thereafter, things worked fine.

Thanks and Regards,
Ajay

On Mon, Jun 30, 2014 at 8:02 PM, Mark Erickson <mer...@ya...> wrote:

> You do not have to 'ack the ACK' other than what TCP will do to indicate
> successful transmission/reception of the CEA.  Did you look to see why your
> server is aborting the session?  Perhaps you're not responding to DWRs?
>
>   ------------------------------
>  *From:* Ajay Garg <aja...@gm...>
> *To:* dia...@li...
> *Sent:* Monday, June 30, 2014 10:21 AM
> *Subject:* Re: [Diameter-developers] (Conceptual) doubt in sending
> Diameter messages
>
> After receiving CEA, do we need to send  "something" that indicates  that
> CEA has been processed (before sending the CCR)?
>
>
>
>
> On Mon, Jun 30, 2014 at 7:20 PM, Ajay Garg <aja...@gm...> wrote:
>
> Any ideas,  please?
>
>
> Thanks and Regards,
> Ajay
>
>
> On Sun, Jun 29, 2014 at 5:32 PM, Ajay Garg <aja...@gm...> wrote:
>
> Hi all.
>
> We are trying to write a diameter-client, that communicates with an
> external diameter-server for event-based CCR.
>
>
>
> We are doing the following ::
>
> SCENARIO 1
> ==========
>
> 1.
> Client connects through a vanilla AF_INET + SOCK_STREAM TCP-socket to the
> server.
>
> 2.
> Client sends CER (successfully).
>
> 3.
> Client receives CEA (successfully).
>
> 4.
> Client sends CCR.
>
> However, at step 4, we get a "Connection reset by Peer" from the server,
> even though CEA showed successful validation.
>
>
>
> SCENARIO 2
> ==========
>
> a)
> Client connects through a vanilla AF_INET + SOCK_STREAM TCP-socket to the
> server.
>
> b)
> Client sends CER (successfully).
>
> c)
> Client receives CEA (successfully).
>
> d)
> Client closes the socket of step a), and instantiates a new socket.
>
> e)
> Client sends CCR through new socket (successfully).
>
> f)
> Client receives CCA (successfully at protocol level), but the charging is
> not done, because the server did not find a prior CER (on the same socket
> presumably).
>
>
> Note that at all times, the CER and CCR contents are exactly the same.
>
>
> So, what could be the reason of connection-reset in scenario 1? Are we
> doing some mistake at the client-side at a control-flow level? Do we need
> to send something "in between" CER and CCR?
>
>
> We will be thankful for any pointers.
>
>
>
> Thanks and Regards,
> Ajay
>
>
>
>
> --
> Regards,
> Ajay
>
>
>
>
> --
> Regards,
> Ajay
>
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
>
> _______________________________________________
> Diameter-developers mailing list
> Dia...@li...
> https://lists.sourceforge.net/lists/listinfo/diameter-developers
>
>
>

-- 
Regards,
Ajay

You do not have to 'ack the ACK' other than what TCP will do to indicate successful transmission/reception of the CEA.  Did you look to see why your server is aborting the session?  Perhaps you're not responding to DWRs?

________________________________
 From: Ajay Garg <aja...@gm...>
To: dia...@li... 
Sent: Monday, June 30, 2014 10:21 AM
Subject: Re: [Diameter-developers] (Conceptual) doubt in sending Diameter	messages

After receiving CEA, do we need to send  "something" that indicates  that CEA has been processed (before sending the CCR)?

On Mon, Jun 30, 2014 at 7:20 PM, Ajay Garg <aja...@gm...> wrote:

Any ideas,  please?
>
>
>Thanks and Regards,
>Ajay
>
>
>
>
>On Sun, Jun 29, 2014 at 5:32 PM, Ajay Garg <aja...@gm...> wrote:
>
>Hi all.
>>
>>We are trying to write a diameter-client, that communicates with an external diameter-server for event-based CCR.
>>
>>
>>
>>We are doing the following ::
>>
>>SCENARIO 1
>>==========
>>
>>1.
>>Client connects through a vanilla AF_INET + SOCK_STREAM TCP-socket to the server.
>>
>>2.
>>Client sends CER (successfully).
>>
>>3.
>>
>>Client receives CEA (successfully).
>>
>>
>>4. 
>>
>>Client sends CCR.
>>
>>
>>However, at step 4, we get a "Connection reset by Peer" from the server, even though CEA showed successful validation.
>>
>>
>>
>>
>>SCENARIO 2
>>==========
>>
>>
>>
>>a)
>>
>>Client connects through a vanilla AF_INET + SOCK_STREAM TCP-socket to the server.
>>
>>
>>b)
>>
>>Client sends CER (successfully).
>>
>>
>>c)
>>
>>Client receives CEA (successfully).
>>
>>
>>d)
>>
>>Client closes the socket of step a), and instantiates a new socket.
>>
>>
>>e)
>>Client sends CCR through new socket (successfully).
>>
>>
>>f)
>>
>>Client receives CCA (successfully at protocol level), but the charging is not done, because the server did not find a prior CER (on the same socket presumably).
>>
>>
>>
>>Note that at all times, the CER and CCR contents are exactly the same.
>>
>>
>>
>>So, what could be the reason of connection-reset in scenario 1? Are we doing some mistake at the client-side at a control-flow level? Do we need to send something "in between" CER and CCR?
>>
>>
>>
>>
>>We will be thankful for any pointers.
>>
>>
>>
>> 
>>Thanks and Regards,
>>Ajay
>>
>
>
>-- 
>Regards,
>Ajay
>

-- 
Regards,
Ajay

------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft

_______________________________________________
Diameter-developers mailing list
Dia...@li...
https://lists.sourceforge.net/lists/listinfo/diameter-developers
After receiving CEA, do we need to send  "something" that indicates  that
CEA has been processed (before sending the CCR)?

On Mon, Jun 30, 2014 at 7:20 PM, Ajay Garg <aja...@gm...> wrote:

> Any ideas,  please?
>
>
> Thanks and Regards,
> Ajay
>
>
> On Sun, Jun 29, 2014 at 5:32 PM, Ajay Garg <aja...@gm...> wrote:
>
>> Hi all.
>>
>> We are trying to write a diameter-client, that communicates with an
>> external diameter-server for event-based CCR.
>>
>>
>>
>> We are doing the following ::
>>
>> SCENARIO 1
>> ==========
>>
>> 1.
>> Client connects through a vanilla AF_INET + SOCK_STREAM TCP-socket to the
>> server.
>>
>> 2.
>> Client sends CER (successfully).
>>
>> 3.
>> Client receives CEA (successfully).
>>
>> 4.
>> Client sends CCR.
>>
>> However, at step 4, we get a "Connection reset by Peer" from the server,
>> even though CEA showed successful validation.
>>
>>
>>
>> SCENARIO 2
>> ==========
>>
>> a)
>> Client connects through a vanilla AF_INET + SOCK_STREAM TCP-socket to the
>> server.
>>
>> b)
>> Client sends CER (successfully).
>>
>> c)
>> Client receives CEA (successfully).
>>
>> d)
>> Client closes the socket of step a), and instantiates a new socket.
>>
>> e)
>> Client sends CCR through new socket (successfully).
>>
>> f)
>> Client receives CCA (successfully at protocol level), but the charging is
>> not done, because the server did not find a prior CER (on the same socket
>> presumably).
>>
>>
>> Note that at all times, the CER and CCR contents are exactly the same.
>>
>>
>> So, what could be the reason of connection-reset in scenario 1? Are we
>> doing some mistake at the client-side at a control-flow level? Do we need
>> to send something "in between" CER and CCR?
>>
>>
>> We will be thankful for any pointers.
>>
>>
>>
>> Thanks and Regards,
>> Ajay
>>
>
>
>
> --
> Regards,
> Ajay
>

-- 
Regards,
Ajay

Any ideas,  please?

Thanks and Regards,
Ajay

On Sun, Jun 29, 2014 at 5:32 PM, Ajay Garg <aja...@gm...> wrote:

> Hi all.
>
> We are trying to write a diameter-client, that communicates with an
> external diameter-server for event-based CCR.
>
>
>
> We are doing the following ::
>
> SCENARIO 1
> ==========
>
> 1.
> Client connects through a vanilla AF_INET + SOCK_STREAM TCP-socket to the
> server.
>
> 2.
> Client sends CER (successfully).
>
> 3.
> Client receives CEA (successfully).
>
> 4.
> Client sends CCR.
>
> However, at step 4, we get a "Connection reset by Peer" from the server,
> even though CEA showed successful validation.
>
>
>
> SCENARIO 2
> ==========
>
> a)
> Client connects through a vanilla AF_INET + SOCK_STREAM TCP-socket to the
> server.
>
> b)
> Client sends CER (successfully).
>
> c)
> Client receives CEA (successfully).
>
> d)
> Client closes the socket of step a), and instantiates a new socket.
>
> e)
> Client sends CCR through new socket (successfully).
>
> f)
> Client receives CCA (successfully at protocol level), but the charging is
> not done, because the server did not find a prior CER (on the same socket
> presumably).
>
>
> Note that at all times, the CER and CCR contents are exactly the same.
>
>
> So, what could be the reason of connection-reset in scenario 1? Are we
> doing some mistake at the client-side at a control-flow level? Do we need
> to send something "in between" CER and CCR?
>
>
> We will be thankful for any pointers.
>
>
>
> Thanks and Regards,
> Ajay
>

-- 
Regards,
Ajay

Hi all.

We are trying to write a diameter-client, that communicates with an
external diameter-server for event-based CCR.

We are doing the following ::

SCENARIO 1
==========

1.
Client connects through a vanilla AF_INET + SOCK_STREAM TCP-socket to the
server.

2.
Client sends CER (successfully).

3.
Client receives CEA (successfully).

4.
Client sends CCR.

However, at step 4, we get a "Connection reset by Peer" from the server,
even though CEA showed successful validation.

SCENARIO 2
==========

a)
Client connects through a vanilla AF_INET + SOCK_STREAM TCP-socket to the
server.

b)
Client sends CER (successfully).

c)
Client receives CEA (successfully).

d)
Client closes the socket of step a), and instantiates a new socket.

e)
Client sends CCR through new socket (successfully).

f)
Client receives CCA (successfully at protocol level), but the charging is
not done, because the server did not find a prior CER (on the same socket
presumably).

Note that at all times, the CER and CCR contents are exactly the same.

So, what could be the reason of connection-reset in scenario 1? Are we
doing some mistake at the client-side at a control-flow level? Do we need
to send something "in between" CER and CCR?

We will be thankful for any pointers.

Thanks and Regards,
Ajay

Hi,

Instead of casting all constant character strings to (char*) I think the 
better solution would be to change the methods accepting a char* to 
accept a const char*.

Johnny

On 06/25/2014 09:35 PM, Ron Brash wrote:
> Large checkin including updates for the newer version of boost, verified
> that OpenSSL 1.0.0m works, Autotools changes (includes new defines) etc...
>
> Lets get some testing and input.
>
> --
>
>
> Ron Brash
> Embedded Developer
> ------------------------------------------------------------------
>
> Email ron...@gm... <mailto:ron...@gm...>
> Web http://www.pacificsimplicity.ca
> LinkedIn http://ca.linkedin.com/in/ronbrash/
>
>
>
> This communication is intended for the use of the recipient to which it is
> addressed, and may contain confidential, personal, and or privileged
> information. Please contact the sender immediately if you are not the
> intended recipient of this communication, and do not copy, distribute, or
> take action relying on it. Any communication received in error, or
> subsequent reply, should be deleted or destroyed.
>
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
>
>
>
> _______________________________________________
> Diameter-developers mailing list
> Dia...@li...
> https://lists.sourceforge.net/lists/listinfo/diameter-developers
>

Large checkin including updates for the newer version of boost, verified
that OpenSSL 1.0.0m works, Autotools changes (includes new defines) etc...

Lets get some testing and input.

-- 

Ron Brash
Embedded Developer
------------------------------------------------------------------

Email  ron...@gm...
Web http://www.pacificsimplicity.ca
LinkedIn http://ca.linkedin.com/in/ronbrash/

This communication is intended for the use of the recipient to which it is
addressed, and may contain confidential, personal, and or privileged
information. Please contact the sender immediately if you are not the
intended recipient of this communication, and do not copy, distribute, or
take action relying on it. Any communication received in error, or
subsequent reply, should be deleted or destroyed.

I am trying to compile the latest version of opendiameter.

./configure ACE_ROOT=/blah/blah BOOST_ROOT=/blah/blah2
make

results in missing config.h error.

so I created an empty config.h in ACE_ROOT.

Now it gives following errors while compiling.

/usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/backward/backward_warning.h:32:2:
warning: #warning This file includes at least one deprecated or antiquated
header. Please consider using one of the 32 headers found in section
17.4.1.2 of the C++ standard. Examples include substituting the <X> header
for the <X.h> header for C++ includes, or <iostream> instead of the
deprecated header <iostream.h>. To disable this warning use -Wno-deprecated.
/root/ACE_wrappers/ace/os_include/sys/os_types.h:122: error: conflicting
declaration 'typedef int ssize_t'
/usr/include/sys/types.h:110: error: 'ssize_t' has a previous declaration
as 'typedef __ssize_t ssize_t'
/root/ACE_wrappers/ace/os_include/os_ucontext.h:40: error: conflicting
declaration 'typedef int ucontext_t'
/usr/include/sys/ucontext.h:143: error: 'ucontext_t' has a previous
declaration as 'typedef struct ucontext ucontext_t'
/root/ACE_wrappers/ace/os_include/sys/os_socket.h:44: error: redefinition
of 'struct msghdr'
/usr/include/bits/socket.h:216: error: previous definition of 'struct
msghdr'
/root/ACE_wrappers/ace/os_include/os_dirent.h:47: error: redefinition of
'struct dirent'
/usr/include/bits/dirent.h:24: error: previous definition of 'struct dirent'
/root/ACE_wrappers/ace/os_include/os_dirent.h:87: error: conflicting
declaration 'typedef struct DIR ACE_DIR'
/root/ACE_wrappers/ace/os_include/os_dirent.h:46: error: 'ACE_DIR' has a
previous declaration as 'typedef int ACE_DIR'
/root/ACE_wrappers/ace/OS_NS_dirent.h: In function 'void
ace_rewinddir_helper(ACE_DIR*)':
/root/ACE_wrappers/ace/OS_NS_dirent.h:73: error: cannot convert 'ACE_DIR*'
to 'DIR*' for argument '1' to 'void rewinddir(DIR*)'
/root/ACE_wrappers/ace/OS_NS_signal.h: At global scope:
/root/ACE_wrappers/ace/OS_NS_signal.h:129: error: using typedef-name
'siginfo_t' after 'struct'
/usr/include/bits/siginfo.h:108: error: 'siginfo_t' has a previous
declaration here
/root/ACE_wrappers/ace/os_include/os_stropts.h:93: error: redefinition of
'struct strbuf'
/usr/include/bits/stropts.h:181: error: previous definition of 'struct
strbuf'
/root/ACE_wrappers/ace/os_include/os_time.h:58: error: redefinition of
'struct timespec'
/usr/include/time.h:122: error: previous definition of 'struct timespec'
/root/ACE_wrappers/ace/os_include/os_time.h:64: error: invalid type in
declaration before ';' token
/root/ACE_wrappers/ace/os_include/os_sched.h:47: error: conflicting
declaration 'typedef struct cpu_set_t cpu_set_t'
/usr/include/bits/sched.h:114: error: 'cpu_set_t' has a previous
declaration as 'typedef struct cpu_set_t cpu_set_t'
make[1]: *** [src/od_utl_rbtree.lo] Error 1
make[1]: Leaving directory `/root/opendiameter-1.0.7-i/libodutl'

It is conflicting with standard definitions. So it seems there will be some
macros in config.h that would be required to compile.

Need your help Guys..

Thanks
Durgesh O Mishra

http://www.mcscreative.com/pddcmdmj/8trn2e2o91v5pfcwh4125cb5utr8nw5pjjlbqxf50z0lu.koub8t15zegrs27f0wn4xy8zupubt91rxwb2lj !!!

antoni milton

http://yahoo.com
%.nxg21a8np0yo
> 
> 
> Dear All,
> 
> Can any one tell me whether OfflineCharging is available in OpenBlox and which is written in Java.
> 
> If yes, Kindly let me know the sample example for execution.
> If Not,Please suggest me a good implementation for offline chaarging.
> 
> Thanks for your reply.
Please do the needful.
> 
> Thanks,
> Krish

Hi,

I'm trying to make it work on Mac OS X

I have:
xerces-c: stable 3.1.1
ace: stable 6.1.3
boost: stable 1.51.0
openssl: stable 1.0.1c
autoconf: stable 2.69
automake: stable 1.12.4

Compiler:
LLVM-GCC: build 2336
Clang: 4.1 build 421

export XERCESCROOT=/usr/local
export ACE_ROOT=/usr/local
export BOOST_ROOT=/usr/local
./configure --prefix=/usr/local --disable-dependency-tracking --enable-odbc --enable-mpa --with-eap-tls

Aside from failing with: Unsupported OS I am getting these: rm: conftest.dSYM: is a directory

If would appreciate if somebody would help me get it work on OS X.

Aslo with --enable-eap-archie is asking for EAP_ARCHIE_ROOT is this in separate library ?

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i386-apple-darwin12.2.0
checking host system type... i386-apple-darwin12.2.0
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ld used by gcc... /usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld
checking if the linker (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) is GNU ld... no
checking for /usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgfortran... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking for nagfor... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether  accepts -g... no
checking the maximum length of command line arguments... 196608
checking command to parse /usr/bin/nm output from gcc object... rm: conftest.dSYM: is a directory
ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
rm: conftest.dSYM: is a directory
rm: conftest.dSYM: is a directory
checking if gcc supports -fno-rtti -fno-exceptions... rm: conftest.dSYM: is a directory
no
checking for gcc option to produce PIC... -fno-common
checking if gcc PIC flag -fno-common works... rm: conftest.dSYM: is a directory
yes
checking if gcc static flag -static works... rm: conftest.dSYM: is a directory
no
checking if gcc supports -c -o file.o... rm: conftest.dSYM: is a directory
yes
checking whether the gcc linker (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) supports shared libraries... yes
checking dynamic linker characteristics... darwin12.2.0 dyld
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
rm: conftest.dSYM: is a directory
rm: conftest.dSYM: is a directory
checking for ld used by g++... /usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld
checking if the linker (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) is GNU ld... no
checking whether the g++ linker (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fno-common
checking if g++ PIC flag -fno-common works... rm: conftest.dSYM: is a directory
yes
checking if g++ static flag -static works... rm: conftest.dSYM: is a directory
no
checking if g++ supports -c -o file.o... rm: conftest.dSYM: is a directory
yes
checking whether the g++ linker (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) supports shared libraries... yes
checking dynamic linker characteristics... darwin12.2.0 dyld
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking existence of ACE_ROOT variable... yes
checking existence of BOOST_ROOT variable... yes
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) gcc3
checking whether gcc and cc understand -c and -o together... rm: conftest.dSYM: is a directory
yes
checking ifaddrs.h usability... yes
checking ifaddrs.h presence... yes
checking for ifaddrs.h... yes
checking net/if_dl.h usability... yes
checking net/if_dl.h presence... yes
checking for net/if_dl.h... yes
checking shadow.h usability... no
checking shadow.h presence... no
checking for shadow.h... no
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for getifaddrs... yes
configure: error: Unsupported OS

Hi all
I followed the Shakthi Kannan's
guide<http://www.shakthimaan.com/installs/opendiameter.html> about
Opendiameter installation and testing, but now I need to write my own code
about a simple server and client communication with diameter protocol using
opendiameter classes, because I need to exchange a customized AVP between
two peers.
But I didn't find a clear documentation and a simple tutorial about server
code (like AAAserver.cpp and AAAclient.cpp).
I found something in main
documentation<http://diameter.sourceforge.net/diameter-api/index.html>
 and obsolete documentation<http://diameter.sourceforge.net/diameter-api-obsolete/index.html>,
but I found hard writing a source code just for begin a clear
implementation.
Any suggestions?

With Regards,
Tommaso Nicoletti

Hi ,
 you can try Seagull
http://gull.sourceforge.net/ 

Thanks
Antoni Milton.

________________________________
 From: sobhanadri.dandamudi <so...@gm...>
To: dia...@li... 
Sent: Wednesday, January 25, 2012 2:41 PM
Subject: [Diameter-developers] Requried URL for diameter base protocol source code with C langauge

Hi,

  This is sobhanadri. Working with Diameter Development.

 Do u have any open source code for Diameter Base Protocol supporting C langauge.

If so pls provide, corresponding URL.

With Regards,
D.Sobhanadri. 
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Diameter-developers mailing list
Dia...@li...
https://lists.sourceforge.net/lists/listinfo/diameter-developers
Hi,

  This is sobhanadri. Working with Diameter Development.

 Do u have any open source code for Diameter Base Protocol supporting C
langauge.

If so pls provide, corresponding URL.

With Regards,
D.Sobhanadri.

Hi All,

I am using OpenDiameter for my application. I want the functionality that when I receive any request from Diameter Clients,
I want to know the source IP address of the client. When I see the DiameterMsg class as pasted below, I find "Sender IP address" and "Originator IP address". I tried to use this but didnt get success. Can anyone help me how to get the IP address from which any request is received???
class DiameterMsg
{
    public:
        DiameterMsgHeader     hdr;                  /**< Message header */
        AAAAvpContainerList   acl;                  /**< AVP container list */
        DiameterErrorCode     status;               /**< Error status */
        AAAIpAddr             originator;           /**< Originator IP address  */
        AAAIpAddr             sender;               /**< Sender IP address */
        time_t                secondsTillExpire;    /**< Expiration time of message */
        time_t                startTime;            /**< Time of transmission */
};

Regards,
Gajanan Raut
Hi ,
  Check whether your sending all required AVPs in ErrorMsg. ( DiameterErrorMsg::Gernerate(  .... ) function  )

Thanks
Antoni Milton.

________________________________
From: Abhijeet Raut <gaj...@ya...>
To: "dia...@li..." <dia...@li...>
Sent: Friday, November 4, 2011 11:51 AM
Subject: [Diameter-developers] Fw:  Regarding Diameter Error conditions

Hi All,

Please help me on the following question. I want to implement following things in my application.
I

----- Forwarded Message -----
From: Abhijeet Raut <gaj...@ya...>
To: "dia...@li..." <dia...@li...>
Sent: Thursday, 27 October 2011 9:38 PM
Subject: [Diameter-developers] Regarding Diameter Error conditions

Hi,

Can anyone help me about error conditions that Diameter Server handles. 
I want to know does Diameter Server respond back to client with error code DIAMETER_MISSING_AVP 
if it receives any request which does not conatain the required AVPs. 
Beacuse I have created a scenario where I am not sending required AVP to the Server but at the server side,
I get an error saying that "missing required avp" and Parse error but it doesn no send any answer back to the client. 
Can any one help me how to sort out this problem. Because in RFC3588 it is written that openDiameter library supports this. 
Let me know if I am wrong.......

Regards,
Gajanan Raut
------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
Diameter-developers mailing list
Dia...@li...
https://lists.sourceforge.net/lists/listinfo/diameter-developers

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Diameter-developers mailing list
Dia...@li...
https://lists.sourceforge.net/lists/listinfo/diameter-developers

Hi All,

Please help me on the following question. I want to implement following things in my application.
I

----- Forwarded Message -----
From: Abhijeet Raut <gaj...@ya...>
To: "dia...@li..." <dia...@li...>
Sent: Thursday, 27 October 2011 9:38 PM
Subject: [Diameter-developers] Regarding Diameter Error conditions

Hi,

Can anyone help me about error conditions that Diameter Server handles. 
I want to know does Diameter Server respond back to client with error code DIAMETER_MISSING_AVP 
if it receives any request which does not conatain the required AVPs. 
Beacuse I have created a scenario where I am not sending required AVP to the Server but at the server side,
I get an error saying that "missing required avp" and Parse error but it doesn no send any answer back to the client. 
Can any one help me how to sort out this problem. Because in RFC3588 it is written that openDiameter library supports this. 
Let me know if I am wrong.......

Regards,
Gajanan Raut
------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
Diameter-developers mailing list
Dia...@li...
https://lists.sourceforge.net/lists/listinfo/diameter-developers
Hi,

Can anyone help me about error conditions that Diameter Server handles. I want to know does Diameter Server respond back to client with error code DIAMETER_MISSING_AVP if it receives any request which does not conatain the required AVPs. Beacuse I have created a scenario where I am not sending required AVP to the Server but at the server side I get an error saying that "missing required avp" and Parse error but it doesn no send any answer back to the client. Can any one help me how to sort out this problem. Because in RFC3588 it is written that openDiameter library supports this. Let me know if I am wrong.......

Regards,
Gajanan Raut
Hi,

I've just compiled Open Diameter using library dependencies from the
OS repository.  I had to make a bunch of simple changes to get it to
compile without warnings or errors.

How do I submit my changes?

OpenDiameter:	1.0.7
OS:			Ubuntu 10.04
g++:			4.4.3
ACE:			5.6.3
Xerces:		2.8.0
Boost:		1.40.0
Autoconf:		2.65
Automake:		1.11

Thanks,
Jamie Royer

http://gbasistemas.com.br/jos/modules/mod_swmenufree/images/superfish/klopd.htm

http://alenajo.com/wp-content/klopd.htm

http://nbwtsn.com/admin/js/tinymce-3.3.8/plugins/spellchecker/includes/mrdrc.htm

Hi Diameter team,

I am using opendiameter-1.0.7 to create my DCC client. I create a class :

class DiameterClient : public AAAClientSession

In main function:

        AAA_Task task;
task.Start(5);
int msgCountPerSession = 3;
char *cfgFile = "config/dcc.client.xml";
std::auto_ptr<DiameterMsg> CcrMsg (new DiameterMsg);
AAAApplicationCore appCore(cfgFile, task);
DiameterClient diameterClient(appCore,1);
diameterClient.Begin("My_Client");

        //create CcrMsg message
       diameterClient.Send(CcrMsg);

after that, I set AVPs for CcrMsg and Send it to my server. But, It doesn't
send to my server because it " Stopping diameter core" immediately.

Please help me and guide me how I can write a DCC Client with opendiameter.

Thank you very much
Khue Nguyen.

2002	Jan (32)	Feb (5)	Mar	Apr (6)	May	Jun	Jul (5)	Aug	Sep (2)	Oct	Nov (15)	Dec (18)
2003	Jan (3)	Feb (2)	Mar (17)	Apr (30)	May (10)	Jun (4)	Jul (12)	Aug (23)	Sep (7)	Oct (9)	Nov (9)	Dec
2004	Jan	Feb (43)	Mar (61)	Apr (63)	May (45)	Jun (19)	Jul (38)	Aug (24)	Sep (44)	Oct (48)	Nov (30)	Dec (42)
2005	Jan (22)	Feb (33)	Mar (60)	Apr (36)	May (62)	Jun (55)	Jul (98)	Aug (115)	Sep (127)	Oct (156)	Nov (53)	Dec (46)
2006	Jan (112)	Feb (72)	Mar (145)	Apr (175)	May (69)	Jun (43)	Jul (110)	Aug (45)	Sep (53)	Oct (66)	Nov (96)	Dec (85)
2007	Jan (73)	Feb (45)	Mar (47)	Apr (28)	May (28)	Jun (35)	Jul (29)	Aug (17)	Sep (17)	Oct (44)	Nov (30)	Dec (35)
2008	Jan (34)	Feb (27)	Mar (12)	Apr (15)	May (17)	Jun (10)	Jul (6)	Aug (11)	Sep (2)	Oct (8)	Nov (5)	Dec (6)
2009	Jan	Feb (9)	Mar (5)	Apr (1)	May (2)	Jun (5)	Jul (8)	Aug (1)	Sep	Oct (4)	Nov (3)	Dec (4)
2010	Jan (1)	Feb	Mar	Apr (3)	May	Jun	Jul (1)	Aug (1)	Sep (5)	Oct	Nov	Dec
2011	Jan	Feb (1)	Mar	Apr (2)	May	Jun	Jul	Aug (7)	Sep (7)	Oct (1)	Nov (2)	Dec (1)
2012	Jan (2)	Feb	Mar	Apr	May (1)	Jun	Jul	Aug	Sep	Oct (1)	Nov (1)	Dec
2013	Jan	Feb (1)	Mar	Apr	May	Jun (1)	Jul	Aug	Sep	Oct	Nov	Dec
2014	Jan	Feb	Mar	Apr	May	Jun (6)	Jul (1)	Aug	Sep (1)	Oct	Nov	Dec
2016	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug (1)	Sep	Oct	Nov	Dec
2019	Jan	Feb	Mar	Apr (1)	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

diameter-developers Mailing List for Open Diameter

diameter-developers — Developers' Mailing List