10 Aug
2007
10 Aug
'07
9:56 a.m.
Yes, add $si to the list of extra Radius attributes logged in
accounting, for example:
modparam("acc", "radius_extra", "Sip-RPid=$avp(s:rpid); \
Source-IP=$si; \
Source-Port=$sp; \
Canonical-URI=$avp(can_uri); \
Billing-Party=$avp
(billing_party); \
Divert-Reason=$avp
(s:divert_reason); \
X-RTP-Stat=$avp
(s:rtp_statistics); \
From-Header=$hdr(from); \
User-Agent=$hdr(user-agent); \
Contact=$hdr(contact); \
Event=$hdr(event); \
SIP-Proxy-IP=$avp
(s:sip_proxy_ip)")
Adrian
>>
Andreas Sikkema andreas.sikkema at bbeyond.nl
Thu Aug 9 17:39:12 CEST 2007
Previous message: [OpenSER-Users] [Openser Users]Differences between
SIP Server andPBX
Next message: [OpenSER-Users] Saving public IP in CDR
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
I'm trying to do add accounting to our OpenSER
server. Getting accounting to work is easy but
I'm having trouble saving client IP addresses with
every CDR.
Most of our SIP UAs are behind some form of
NAT and to "prove" that calls have originated at
the client I want to save the public IP address
and as extra service also the private IP
address of the UA.
Saving the private IP address is easy, $Ri
contains this value. I'm having trouble finding out
what to do to save the public IP address. I thought
that since I'm using fix_contact() I could save the
contact header body, but $ct still contained the
private IP address.
Is this even possible?
--
Andreas Sikkema
10 Aug
10 Aug
12:47 p.m.
Adrian,
Yes, add $si to the list of extra Radius attributes
logged in
accounting, for example:
Unfortunately, as far as I can see (but I'm using a slightly
outdated OpenSER version) $si contains the reported remote IP
address, not the public IP address that the message has been
received from.
--
Andreas Sikkema
12:56 p.m.
Andreas,
another option in your case could be $src_ip
DanB
On 8/10/07, Andreas Sikkema <andreas.sikkema(a)bbeyond.nl> wrote:
Adrian,
Yes, add $si to the list of extra Radius
attributes logged in
accounting, for example:
Unfortunately, as far as I can see (but I'm using a slightly
outdated OpenSER version) $si contains the reported remote IP
address, not the public IP address that the message has been
received from.
--
Andreas Sikkema
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
1:03 p.m.
Andreas,
What is the version you are using (openser -V). Would it be possible to upgrade?
DanB
On 8/10/07, Andreas Sikkema <andreas.sikkema(a)bbeyond.nl> wrote:
Dan-Cristian,
another option in your case could be $src_ip
Unfortunately the version I'm using doesn't
support it. I get a parse error during configuration
load...
--
Andreas Sikkema BBeyond
Software Engineer Planeetbaan 4
+31 (0)23 7074342 2132 HZ Hoofddorp
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
1:05 p.m.
El Friday 10 August 2007 11:47:07 Andreas Sikkema escribió:
Adrian,
Received IP address
$Ri - reference to IP address of the interface where the request has been
received
--
Iñaki Baz Castillo
ibc(a)in.ilimit.es
Yes, add $si to the list of extra Radius
attributes logged in
accounting, for example:
Unfortunately, as far as I can see (but I'm using a slightly
outdated OpenSER version) $si contains the reported remote IP
address, not the public IP address that the message has been
received from.
1:18 p.m.
El Friday 10 August 2007 12:07:37 Andreas Sikkema escribió:
Yes, that is, I comment it to you because you said:
"Unfortunately [...] $si contains the reported remote IP address, not the
public IP address that the message has been received from."
I think you are trying to get something impossible: the last router IP through
which the packet arrieved to your OpenSer. That's not possible, note that
layer 3 (IP) doesn't notify the intermediary IP address in the received
message, you just can see the source and destination.
--
Iñaki Baz Castillo
ibc(a)in.ilimit.es
Received IP
address
$Ri - reference to IP address of the interface where the
request has been
received
This refers to the interface on the server, not the client
unfortunately...
1:23 p.m.
Yes, that is, I comment it to you because you said:
"Unfortunately [...] $si contains the reported remote IP
address, not the
public IP address that the message has been received from."
I think you are trying to get something impossible: the last
router IP through
which the packet arrieved to your OpenSer. That's not
possible, note that
layer 3 (IP) doesn't notify the intermediary IP address in
the received
message, you just can see the source and destination.
No, I'm trying to get to the public IP address of a NATted
SIP UA. This address is not found in the SIP message, but
OpenSER knows it otherwise it couldn't reply to it ;-)
--
Andreas Sikkema
1:42 p.m.
El Friday 10 August 2007 12:23:43 Andreas Sikkema escribió:
Ok, then that is $si. But I've already read that in your case it means the
privati IP of the source. Hummm...
--
ilimit...
*Iñaki Baz Castillo*
ibc(a)in.ilimit.es
ÀREA SISTEMES
0034 937 333 375
VOLTA 1, PIS 5
08224 TERRASSA.BCN
Aquest enviament és confidencial i està destinat únicament a la persona a qui
s'ha enviat.
Pot contenir informació privada sotmesa al secret professional, la distribució
de la qual està prohibida per la legislació vigent.
Yes, that is,
I comment it to you because you said:
"Unfortunately [...] $si contains the reported remote IP
address, not the
public IP address that the message has been received from."
I think you are trying to get something impossible: the last
router IP through
which the packet arrieved to your OpenSer. That's not
possible, note that
layer 3 (IP) doesn't notify the intermediary IP address in
the received
message, you just can see the source and destination.
No, I'm trying to get to the public IP address of a NATted
SIP UA. This address is not found in the SIP message, but
OpenSER knows it otherwise it couldn't reply to it ;-) 
2:36 p.m.
On Friday 10 August 2007 12:23, Andreas Sikkema wrote:
You could try to parse the Via headers to find the correct IP.
--
Greetings,
Alex Hermann
Yes, that is,
I comment it to you because you said:
"Unfortunately [...] $si contains the reported remote IP
address, not the
public IP address that the message has been received from."
I think you are trying to get something impossible: the last
router IP through
which the packet arrieved to your OpenSer. That's not
possible, note that
layer 3 (IP) doesn't notify the intermediary IP address in
the received
message, you just can see the source and destination.
No, I'm trying to get to the public IP address of a NATted
SIP UA. This address is not found in the SIP message, but
OpenSER knows it otherwise it couldn't reply to it ;-)
6315
days inactive
6315
days old
10 comments
5 participants
participants (5)
-
Adrian Georgescu -
Alex Hermann -
Andreas Sikkema -
Dan-Cristian Bogos -
Iñaki Baz Castillo