7 Jan
2003
7 Jan
'03
6:06 a.m.
Dear Sirs,
Our company is currently evaluating several freely available SIP
proxy/registrars to extend our VoIP billing engine, which currently
only supports H323, to support SIP as well. We found SER to be one of
the best for our needs: speed, documentation, flexibility - everything
is great. Hovewer, since our billing engine uses Radius for AAA, we need
to get Radius modules working. Unfortunately, we can't compile radius
modules with virgin radiusclient 0.3.2 as suggested in documentation - it
seems that some SIP-specific changes need to be applied to radiusclient
headers, see the following log:
gcc -fPIC -DPIC -pipe -O -mpreferred-stack-boundary=2 -march=pentium2 -funroll-loops
-Wcast-align -Wall -minline-all-stringops -malign-double -falign-loops
-DNAME='"ser"' -DVERSION='"0.8.10"'
-DARCH='"i386"' -DOS='"freebsd"'
-DCOMPILER='"gcc 3.2"' -D__CPU_i386
-DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP
-DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DUSE_IPV6 -DDBG_QM_MALLOC
-DFAST_LOCK -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD
-DHAVE_SOCKADDR_SA_LEN -I/usr/local/include -c acc.c -o acc.o
acc.c: In function `radius_log_reply':
acc.c:125: `PW_SIP_METHOD' undeclared (first use in this function)
acc.c:125: (Each undeclared identifier is reported only once
acc.c:125: for each function it appears in.)
acc.c:136: `PW_SIP_RESPONSE_CODE' undeclared (first use in this function)
acc.c:156: `PW_SIP_FROM_TAG' undeclared (first use in this function)
acc.c:189: `PW_SIP_TO_TAG' undeclared (first use in this function)
acc.c:213: `PW_SIP_CSEQ' undeclared (first use in this function)
acc.c:288: `PW_SIP_TRANSLATED_REQ_URI' undeclared (first use in this function)
acc.c: In function `radius_log_ack':
acc.c:434: `PW_SIP_METHOD' undeclared (first use in this function)
acc.c:442: `PW_SIP_RESPONSE_CODE' undeclared (first use in this function)
acc.c:461: `PW_SIP_FROM_TAG' undeclared (first use in this function)
acc.c:491: `PW_SIP_TO_TAG' undeclared (first use in this function)
acc.c:514: `PW_SIP_CSEQ' undeclared (first use in this function)
acc.c:588: `PW_SIP_TRANSLATED_REQ_URI' undeclared (first use in this function)
acc.c: In function `rad_acc_request':
acc.c:733: `PW_SIP_METHOD' undeclared (first use in this function)
acc.c:744: `PW_SIP_RESPONSE_CODE' undeclared (first use in this function)
acc.c:764: `PW_SIP_FROM_TAG' undeclared (first use in this function)
acc.c:797: `PW_SIP_TO_TAG' undeclared (first use in this function)
acc.c:821: `PW_SIP_CSEQ' undeclared (first use in this function)
acc.c:904: `PW_SIP_TRANSLATED_REQ_URI' undeclared (first use in this function)
Would you be so kind to provide us with your changes for radiusclient or
point out where that modified version can be downloaded?
Thank you in advance!
On a separate note I would like to ask you to let me know if there is
any progress on pre-paid module discussed on this list recently. Since we
will also need this functionality, perhaps we can team-up to implement it.
Sincerely,
Maxim Sobolev
PortaOne Ltd
7 Jan
7 Jan
8:16 p.m.
New subject: [Serusers] Re: Problems compiling SER with radius support
At 12:06 PM 1/7/2003, Maxim Sobolev wrote:
Dear Sirs,
Our company is currently evaluating several freely available SIP
proxy/registrars to extend our VoIP billing engine, which currently
only supports H323, to support SIP as well. We found SER to be one of
the best for our needs: speed, documentation, flexibility - everything
is great.
Thank you -- I am really flattered :-)
Hovewer, since our billing engine uses Radius for AAA,
we need
to get Radius modules working. Unfortunately, we can't compile radius
modules with virgin radiusclient 0.3.2 as suggested in documentation - it
seems that some SIP-specific changes need to be applied to radiusclient
headers, see the following log:
Unfortunately, the radius_acc module is currently in middle of
a reconstruction. It is being merged with acc module and some
shortcomings in it are being fixed. The updated version will
be available in the next release of ser. In the meantime, you
can try using the version on CVS (available as a tarball at
http://www.iptel.org/~jiri/etc/radius/) at your risk.
Thank you in advance!
On a separate note I would like to ask you to let me know if there is
any progress on pre-paid module discussed on this list recently. Since we
will also need this functionality, perhaps we can team-up to implement it.
That sounds appealing. We have currently no development cycles as everybody
is busy with maintaining the currently available software. However, if
anyone is willing to volunteer and implement a B2BUA, we will be glad
to provide guidance on that.
-Jiri
8 Jan
8 Jan
5:03 a.m.
Hello,
there is sip_dictionary file in ser-0.8.10/etc directory which contains
all the missing definitions. You can find a description how to use it in
ser-0.8.10/modules/radius_acc/project.txt
Radius related modules need to be refurbished and we are currently working
on it.
Jan.
On 07-01 13:06, Maxim Sobolev wrote:
Dear Sirs,
Our company is currently evaluating several freely available SIP
proxy/registrars to extend our VoIP billing engine, which currently
only supports H323, to support SIP as well. We found SER to be one of
the best for our needs: speed, documentation, flexibility - everything
is great. Hovewer, since our billing engine uses Radius for AAA, we need
to get Radius modules working. Unfortunately, we can't compile radius
modules with virgin radiusclient 0.3.2 as suggested in documentation - it
seems that some SIP-specific changes need to be applied to radiusclient
headers, see the following log:
gcc -fPIC -DPIC -pipe -O -mpreferred-stack-boundary=2 -march=pentium2 -funroll-loops
-Wcast-align -Wall -minline-all-stringops -malign-double -falign-loops
-DNAME='"ser"' -DVERSION='"0.8.10"'
-DARCH='"i386"' -DOS='"freebsd"'
-DCOMPILER='"gcc 3.2"' -D__CPU_i386
-DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP
-DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DUSE_IPV6 -DDBG_QM_MALLOC
-DFAST_LOCK -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD
-DHAVE_SOCKADDR_SA_LEN -I/usr/local/include -c acc.c -o acc.o
acc.c: In function `radius_log_reply':
acc.c:125: `PW_SIP_METHOD' undeclared (first use in this function)
acc.c:125: (Each undeclared identifier is reported only once
acc.c:125: for each function it appears in.)
acc.c:136: `PW_SIP_RESPONSE_CODE' undeclared (first use in this function)
acc.c:156: `PW_SIP_FROM_TAG' undeclared (first use in this function)
acc.c:189: `PW_SIP_TO_TAG' undeclared (first use in this function)
acc.c:213: `PW_SIP_CSEQ' undeclared (first use in this function)
acc.c:288: `PW_SIP_TRANSLATED_REQ_URI' undeclared (first use in this function)
acc.c: In function `radius_log_ack':
acc.c:434: `PW_SIP_METHOD' undeclared (first use in this function)
acc.c:442: `PW_SIP_RESPONSE_CODE' undeclared (first use in this function)
acc.c:461: `PW_SIP_FROM_TAG' undeclared (first use in this function)
acc.c:491: `PW_SIP_TO_TAG' undeclared (first use in this function)
acc.c:514: `PW_SIP_CSEQ' undeclared (first use in this function)
acc.c:588: `PW_SIP_TRANSLATED_REQ_URI' undeclared (first use in this function)
acc.c: In function `rad_acc_request':
acc.c:733: `PW_SIP_METHOD' undeclared (first use in this function)
acc.c:744: `PW_SIP_RESPONSE_CODE' undeclared (first use in this function)
acc.c:764: `PW_SIP_FROM_TAG' undeclared (first use in this function)
acc.c:797: `PW_SIP_TO_TAG' undeclared (first use in this function)
acc.c:821: `PW_SIP_CSEQ' undeclared (first use in this function)
acc.c:904: `PW_SIP_TRANSLATED_REQ_URI' undeclared (first use in this function)
Would you be so kind to provide us with your changes for radiusclient or
point out where that modified version can be downloaded?
Thank you in advance!
On a separate note I would like to ask you to let me know if there is
any progress on pre-paid module discussed on this list recently. Since we
will also need this functionality, perhaps we can team-up to implement it.
Sincerely,
Maxim Sobolev
PortaOne Ltd
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
1:42 p.m.
On Wed, Jan 08, 2003 at 11:03:42AM +0100, Jan Janak wrote:
Hello,
there is sip_dictionary file in ser-0.8.10/etc directory which contains
all the missing definitions. You can find a description how to use it in
ser-0.8.10/modules/radius_acc/project.txt
Radius related modules need to be refurbished and we are currently working
on it.
Thanks! I was able to compile it just fine using attached patch for
radiusclient, perhaps you can put it somewhere on your site and add
a note to documentation, so that other users will not be stucking to
the same problem
-Maxim
Jan.
On 07-01 13:06, Maxim Sobolev wrote:
> Dear Sirs,
>
> Our company is currently evaluating several freely available SIP
> proxy/registrars to extend our VoIP billing engine, which currently
> only supports H323, to support SIP as well. We found SER to be one of
> the best for our needs: speed, documentation, flexibility - everything
> is great. Hovewer, since our billing engine uses Radius for AAA, we need
> to get Radius modules working. Unfortunately, we can't compile radius
> modules with virgin radiusclient 0.3.2 as suggested in documentation - it
> seems that some SIP-specific changes need to be applied to radiusclient
> headers, see the following log:
>
> gcc -fPIC -DPIC -pipe -O -mpreferred-stack-boundary=2 -march=pentium2 -funroll-loops
-Wcast-align -Wall -minline-all-stringops -malign-double -falign-loops
-DNAME='"ser"' -DVERSION='"0.8.10"'
-DARCH='"i386"' -DOS='"freebsd"'
-DCOMPILER='"gcc 3.2"' -D__CPU_i386
-DCFG_DIR='"/usr/local/etc/ser/"' -DPKG_MALLOC -DSHM_MEM -DSHM_MMAP
-DADAPTIVE_WAIT -DADAPTIVE_WAIT_LOOPS=1024 -DDNS_IP_HACK -DUSE_IPV6 -DDBG_QM_MALLOC
-DFAST_LOCK -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD
-DHAVE_SOCKADDR_SA_LEN -I/usr/local/include -c acc.c -o acc.o
> acc.c: In function `radius_log_reply':
> acc.c:125: `PW_SIP_METHOD' undeclared (first use in this function)
> acc.c:125: (Each undeclared identifier is reported only once
> acc.c:125: for each function it appears in.)
> acc.c:136: `PW_SIP_RESPONSE_CODE' undeclared (first use in this function)
> acc.c:156: `PW_SIP_FROM_TAG' undeclared (first use in this function)
> acc.c:189: `PW_SIP_TO_TAG' undeclared (first use in this function)
> acc.c:213: `PW_SIP_CSEQ' undeclared (first use in this function)
> acc.c:288: `PW_SIP_TRANSLATED_REQ_URI' undeclared (first use in this function)
> acc.c: In function `radius_log_ack':
> acc.c:434: `PW_SIP_METHOD' undeclared (first use in this function)
> acc.c:442: `PW_SIP_RESPONSE_CODE' undeclared (first use in this function)
> acc.c:461: `PW_SIP_FROM_TAG' undeclared (first use in this function)
> acc.c:491: `PW_SIP_TO_TAG' undeclared (first use in this function)
> acc.c:514: `PW_SIP_CSEQ' undeclared (first use in this function)
> acc.c:588: `PW_SIP_TRANSLATED_REQ_URI' undeclared (first use in this function)
> acc.c: In function `rad_acc_request':
> acc.c:733: `PW_SIP_METHOD' undeclared (first use in this function)
> acc.c:744: `PW_SIP_RESPONSE_CODE' undeclared (first use in this function)
> acc.c:764: `PW_SIP_FROM_TAG' undeclared (first use in this function)
> acc.c:797: `PW_SIP_TO_TAG' undeclared (first use in this function)
> acc.c:821: `PW_SIP_CSEQ' undeclared (first use in this function)
> acc.c:904: `PW_SIP_TRANSLATED_REQ_URI' undeclared (first use in this function)
>
> Would you be so kind to provide us with your changes for radiusclient or
> point out where that modified version can be downloaded?
>
> Thank you in advance!
>
> On a separate note I would like to ask you to let me know if there is
> any progress on pre-paid module discussed on this list recently. Since we
> will also need this functionality, perhaps we can team-up to implement it.
>
> Sincerely,
>
> Maxim Sobolev
> PortaOne Ltd
> _______________________________________________
> Serusers mailing list
> serusers(a)lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>
1:52 p.m.
On 08-01 20:42, Maxim Sobolev wrote:
Thanks! I was able to compile it just fine using
attached patch for
radiusclient, perhaps you can put it somewhere on your site and add
a note to documentation, so that other users will not be stucking to
the same problem
Thanks, we will include it.
Jan.
8075
days inactive
8076
days old
4 comments
3 participants
participants (3)
-
Jan Janak -
Jiri Kuthan -
Maxim Sobolev