I have a client with that I had up and running just fine pt-2-pt, and then they hired an new IT guy who wants *3* sites taking over DSL (to save $$). They gave me fixed IP addresses, and I thought I'd set up the 8 series programming correctly...but I get "A remote channel cannot be found"...There are sonicwall firewalls, and they are open for the UDP traffic...but heck if I know what else he should have open (they changed all the internet facing configurations on me...)

Help Help - what's a "known good" config for this type of installation? :shrug:

Were they public IP's ? Need to be unless all are on a private network

They don't necessarily have to be public IP's if you use port forwarding, but you do need the public IP address info. I would bet that something is not right in either the routers or the system 8-series programming. Can you get any of the cabinets to talk to each other?

I have made sure the client procures public IPs, and I am thinking that perhaps an address is not being routed/allowed thru the SonicWall; I'm just not certain that all addresses are open - I am only certain of UDP (59001-64000)...anyone have any thoughts on what else should be permitted? It annoys me as my pt-to-pt was perfect and ran for a couple of years over a T-1, and I had no issues with it...grrr.

If anyone has a know good config (as in - network map) I'd appreciate the insights. I don't think there are individual cisco routers in place anymore like I used to have, just modems and firewalls. :bang:

I've had issues in the past with Sonic Wall and port forwarding. Are you able to update to the newest firmware on the sonicwall's?

Next, are you have to ping the WAN IP of any of the cabs from the other locations?

Call David O'Brian @ ESI and ask him to fax you over one of his worksheets, they can be very helpful in making sure everything is set up correctly

You can view traffic in the log files on the Sonic Wall - you should be able to see if you are getting packets - either from the IP address of the other 2 sites or on the UDP ports you are using.

I have also seen issues with Sonic Walls - everything was configured right on them but they didn't forward the traffic properly. Eventually Sonic Wall tech support resolved it.

Have ESI tech support dial in and verify your programming is correct as well. Also have them make sure all of your licenses show as active.

Sonicwalls should have a two week course on how to program them. The help of Sonicwall tech support is a must if you're doing anything out of the ordinary (i.e. voice traffic that's that's not SIP or H323) The licensing on Sonicwalls can be an issue as well, because I believe they will only support the number of LAN IP's that they are licensed for.

Just open up a Access Rule under Firewall Source/Destination and you will need to create a Service under Firewall (UDP) on the Sonic wall for the Remote Phone or ESI - Link. Done this several times with no issues.

You all have been extremely helpful. As it turns out, your collective SonicWall advice, along with my ESI tech support guy (in Plano) turned out to be just the ticket - I convinced the IT guy to talk to SonicWall and reconfigure them to the correct spec for voice traffic (allowing 59001 as an example). I figure I'll have this up and running today... thanks all! :bow: