[Spce-user] Masking provider IP

[Jon Bonilla (Manwe)]

El Tue, 26 Feb 2013 00:39:30 +1100
Andrew Yager <andrew at rwts.com.au> escribió:

> On 26/02/2013, at 12:30 AM, Jon Bonilla (Manwe) <jbonilla at sipwise.com> wrote:
> 
> > El Tue, 26 Feb 2013 00:09:01 +1100
> > Andrew Yager <andrew at rwts.com.au> escribió:
> > 
> >>> 
> >>> It should work out of the box. The provider has a b2bua (sems) performing
> >>> topology hiding. Each leg shouldn't see the other leg's IP address. 
> >>> 
> >>> Can you see your provider's IP while performing a ngrep capture in the
> >>> subscriber network?
> >> 
> >> Yes I can - and I thought it should just be working, both in the from and
> >> the P-Asserted-ID.
> >> 
> >> The providers address doesn't appear in the record-route however.
> >> 

> > So, the IP address of the peer is shown in the TO and From headers? 
> > 
> 
> It appears in three locations below in the invite message:
> 
> INVITE sip:61283554154 at 10.211.55.6:5060 SIP/2.0.
> Max-Forwards: 10.
> Record-Route:
> <sip:114.141.98.50;r2=on;lr=on;ftag=0AC5FA91-512B6906000214BC-F3D87700;ngcplb=yes>.
> Record-Route:
> <sip:127.0.0.1;r2=on;lr=on;ftag=0AC5FA91-512B6906000214BC-F3D87700;ngcplb=yes>.
> Via: SIP/2.0/UDP
> 114.141.98.50;branch=z9hG4bKe229.bab2eeb0417d38076670ec9e08c94a29.0. Via:
> SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bK.QyNRaB9;rport=5080. From: <sip:
> 0405152568@ **** PROVIDER IP **** >;tag=0AC5FA91-512B6906000214BC-F3D87700.
> To: <sip:61283554154 at syd03.voice.thecore.net.au>. CSeq: 10 INVITE. Call-ID:
> 3d92-4c2-125201313379-SYYP_IMG01-2-**** PROVIDER IP ****_b2b-1. Allow:
> INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,INFO.
> P-Asserted-Identity: <sip:0405152568@ **** PROVIDER IP **** >. Content-Type:
> application/sdp. Content-Length: 400. Contact:
> <sip:ngcp-lb at 114.141.98.50:5060;ngcpct='sip:127.0.0.1:5080'>. .
> v=0.
> o=- 1859228012 1859228012 IN IP4 114.141.98.50.
> s=ENSResip.
> c=IN IP4 114.141.98.50.
> t=0 0.
> m=audio 30116 RTP/AVP 18 2 8 0 4 101.
> a=rtpmap:18 G729/8000.
> a=rtpmap:2 G726-32/8000.
> a=rtpmap:8 PCMA/8000.
> a=rtpmap:0 PCMU/8000.
> a=rtpmap:4 G723/8000.
> a=rtpmap:101 telephone-event/8000.
> a=fmtp:18 annexb=no.
> a=fmtp:4 bitrate=6.3.
> a=fmtp:101 0-15.
> a=silenceSupp:off - - - -.
> a=sendrecv.
> a=nortpproxy:yes.
> 

Hi Andrew. 

Thanks for the INVITE. You'll have to take a look to a template file:

/etc/ngcp-config/templates/etc/sems/etc/ngcp.sbcprofile.conf.tt2 (create the
customtt file)

Check out sems' documentation regarding the sbc capabilities:

http://bit.ly/YrV7gX


Another option would be to add a preference for peer/domain/subscriber and
modify the behaviour in the proxy to modify the From and the API/PPI...
headers. This would be more powerful but more complicated.