Shoretel SIP Trunks failing to work after migrating internet/firewall
Hi
Need some guidance on this please. Have a Small Business edition shoretel setup, running HQ, SG90, SG90BRI, E1k and an ingate siperator.
We've migrated the internet and replaced the firewall (cisco asa 5505) and rebuild the config so essentially the same apart from it has new external IP addresses. However the SIP trunks failed to come online.
It transpired that the old firewall had an additional wan IP address allocated to the firewall, and this IP was stored in the gamma portal. So
We've tried using an additional IP address to the firewall and using the current WAN IP of the firewall to Gamma portal, but no joy.
The config on the ingate appears to be configured to point traffic direct to Gamma. The old and new firewalls had/has an inbound NAT rule from WAN IP internal ingate e.g: nat (inside,outside) source static a-172.16.10.35 a-*.*.*.*
Ideas?
Need some guidance on this please. Have a Small Business edition shoretel setup, running HQ, SG90, SG90BRI, E1k and an ingate siperator.
We've migrated the internet and replaced the firewall (cisco asa 5505) and rebuild the config so essentially the same apart from it has new external IP addresses. However the SIP trunks failed to come online.
It transpired that the old firewall had an additional wan IP address allocated to the firewall, and this IP was stored in the gamma portal. So
We've tried using an additional IP address to the firewall and using the current WAN IP of the firewall to Gamma portal, but no joy.
The config on the ingate appears to be configured to point traffic direct to Gamma. The old and new firewalls had/has an inbound NAT rule from WAN IP internal ingate e.g: nat (inside,outside) source static a-172.16.10.35 a-*.*.*.*
Ideas?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
correct.
not sure, think the version of the software is newer on the new fwall.
No, the new WAN IPs are completely different, as new ISP.
Thanks for links.
not sure, think the version of the software is newer on the new fwall.
No, the new WAN IPs are completely different, as new ISP.
Thanks for links.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes thats one thing we changed. It now looks like it might be port related.
Have you made the changes on your firewall?
ASKER
Tonight
ASKER
Is this a valid command to NAT inbound traffic to the Ingate?