3 May
2006
3 May
'06
4:07 p.m.
You can use (with the CVS head version) functions from avp and xlog
modules:
xlset_attr("source","%si");
append_avp_hf("X-Source-Address","source");
Michal
On Wed, May 03, 2006 at 04:28:51PM +0100, Alistair Cunningham wrote:
Andrey,
We'll be using it for authentication, so can't trust anything from the
client. We only care about INVITEs.
SDP seems the best so far.
Alistair Cunningham,
Integrics Ltd,
+44 (0)7870 699 479
http://integrics.com/
Andrey Kouprianov wrote:
Hi,
1. Which requests will you apply this rule for? If it's a INVITE, then
you can always utilize existing Contact header, which is attached to
every INVITE request.
2. SDP is definitely not an ugly way to extract source address. So,
you can use this method without any doubt.
3. Why dont you attach a header at the client-side? (though SER might
as well strip it off after forwarding)
On 5/3/06, Alistair Cunningham <acunningham(a)integrics.com> wrote:
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers We'd like to forward the source address that a
request came from in a
header, something like:
X-Source-Address: 192.168.1.1
Is there a neat way to do this? An append_sourcehf( "X-Source-Address" )
would be ideal. If worst comes to worst, we can always extract it from
the c= after doing fix_nated_sdp(), but we'd prefer something less ugly!
--
Alistair Cunningham,
Integrics Ltd,
+44 (0)7870 699 479
http://integrics.com/
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers