[SR-Users] Asterisk cluster behind kamailio natted to pubic IP, presenting internal ip addresses in From tag

[Tim Chubb]

Hi All

I'm scratching my head on this one, I have set everything up in the following configuration:

Public ip natted to DMZ via Cisco ASA 5510  <= DMZ => Kamailio & RTP Proxy <= Voice DMZ => Asterisk

My kamailio configuration is based heavily on the one found here: http://saevolgo.blogspot.co.uk/2013/08/rtpproxy-revisited-kamailio-40.html  & http://saevolgo.blogspot.co.uk/2011/11/how-to-increasing-voip-services.html

So far everything is working fine, I can register via the public IP address, IM & presence is working, and as does audio, however when I dial an extension the caller id comes up like this 12345 at 172.16.15.123:5080<mailto:12345 at 172.16.15.123:5080> which is the ip addresses of the asterisk server that the dispatcher has assigned to the call, I have tried setting the P-Asserted-Identity, P-Preferred-Identity & Remote-Party-ID headers to no effect.  What I would like to achieve is that the public IP or domain name comes up when I call an extension.  From examining the sip traffic traversing the kamailio box, it seems that the From and Contact headers sent by asterisk are the source of the internal implementation information reaching the end-user.

How can I prevent implementation information like this leaking out?  I consider this to be a security risk as I don't want anyone to be able to enumerate the number of servers that comprise a given cluster as easily as placing a few calls, ideally I only want data relating to the public side of the network getting out. But I would be happy if it takes digging into the sip traffic to glean any details initially.

I'm getting the feeling that this could well be an asterisk configuration issue, so apologies if this is a little off topic, however I have been unable to find a similar configuration to try and achieve my desired results.

Tim.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20140828/2505e4a7/attachment.html>