We are switching to a dedicated Server for our SIP Provider. Currently we are on a server of theirs that is shared among several of their customers and are moving to the dedicated to help with some issues.
With the Current connection we are NOT using STUN, we have all Inspection on the Cisco ASA turned off and are connected via LAN1 through the Firewall. The Remote SIP switch needs to deal with converting out Internal IP to a Public IP when it issues the re-invites and a few other things.
When Connecting to a SIP Provider over a regular internet connection (non-dedicated to the ISP) What is the Best practice for connecting to them?
Seems like the easiest is to Assign the LAN2 a Public IP and let the SIP Provider Communicate Directly to that and have an Access List on the Edge Router to Prevent Traffic from other sources/ports.
Any information would be appreciated.
Thank you!
Scott<-
With the Current connection we are NOT using STUN, we have all Inspection on the Cisco ASA turned off and are connected via LAN1 through the Firewall. The Remote SIP switch needs to deal with converting out Internal IP to a Public IP when it issues the re-invites and a few other things.
When Connecting to a SIP Provider over a regular internet connection (non-dedicated to the ISP) What is the Best practice for connecting to them?
Seems like the easiest is to Assign the LAN2 a Public IP and let the SIP Provider Communicate Directly to that and have an Access List on the Edge Router to Prevent Traffic from other sources/ports.
Any information would be appreciated.
Thank you!
Scott<-