It actually stems from having to use an AMI in Virginia, because of the Route header issue with the latest install. So when that is fixed, I can bring up the IMS local to the App Server.
Kevin Kevin Heath High Solution Architect Tropo, Inc. [email protected] Skype: kevin.heath.high Mobile: +1 (650) 798-4772 From: Eleanor Merry <[email protected]> Date: Friday, December 20, 2013 at 1:57 PM To: Kevin High <[email protected]>, "[email protected]" <[email protected]> Cc: Jose de Castro <[email protected]> Subject: RE: NAT'ng Spout Route header to AS server Hi Kevin, We don¹t support having application servers that are on a different subnet to the Clearwater deployment - this hadn¹t been clearly documented before so we¹ve updated the Application Server Guide (https://github.com/Metaswitch/clearwater-docs/wiki/Application-Server-Guide ). The main reason we don¹t support this is that it potentially breaks our current security model; sprout expects all of its connections to be with devices that are inside the IMS core, with access to the core being controlled by the P-CSCF. While I can see that an application server can be part of your conceptual core while not being in the same subnet, the current Clearwater code doesn¹t support this topology. An upshot of this model is that all-in-one nodes (which are always behind a NAT) cannot easily interoperate with application servers; however these nodes are only really intended for testing of basic function. Is this (application servers on a separate subnet) the topology that you expect service providers to use in the field? Or does your request stem from testing with an all-in-one node? Would it be possible for you to move the application server into the same subnet as the Clearwater deployment? Or, if you are using an all-in-one node, to switch to a full Clearwater deployment (in the same subnet as the application server)? Ellie From: [email protected] [mailto:[email protected]] On Behalf Of Kevin High Sent: 20 December 2013 05:15 To: [email protected] Cc: Jose de Castro Subject: [Clearwater] NAT'ng Spout Route header to AS server I have an application server residing on another network that I want to send calls to. The problem is that Sprout adds its private IP address to the Route header when sending the INVITE to the AS. I need sprout to add the Public IP instead so the Application server can route the call back to Sprout. How do I define NAT in the configuration? Thanks Kevin Kevin Heath High Solution Architect Tropo, Inc. [email protected] Skype: kevin.heath.high Mobile: +1 (650) 798-4772
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
