[Serusers] Forwarding source address

Alistair Cunningham acunningham at integrics.com
Wed May 3 17:28:51 CEST 2006


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 at integrics.com> wrote:
>> 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 at lists.iptel.org
>> http://lists.iptel.org/mailman/listinfo/serusers
>>
> 
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
> 
> 




More information about the sr-users mailing list