Let me preface this by telling you that I have little to no experience with Samsung systems. I'm primarily a network guy but I do wholly manage a Toshiba CTX670 and CTX100 so I'm not completely ignorant when it comes to phone systems.

We had an OfficeServ 7400 installed at one of our locations in Atlanta with ~30 users back in March. There is a small office with 3 users in SC that has VOIP phones connecting to the 7400. Both locations have single T1 lines for all WAN data traffic. The Atlanta site is protected by a firewall and also hosts an Exchange server and Terminal Server for remote users. Internet browsing traffic is pretty light overall. The SC site just has a Linksys router NATing the LAN traffic to the T1.

When the 7400 was installed, we set two static IPs on the system, .42 for the MP40 and .32 for the MGI. Based on the ports given to me from the installer, we setup DNAT policies on the firewall to route inbound WAN traffic on ports 5000, 5003, 5090, 5200, 6000, 6100, and 8080 to .42. Ports 9000, 9001, and 30000-30012 are forwarded to .43. We also have SNAT policies to translate .42 and .43 to the WAN IP for outbound traffic.

At the time, the installer said QoS was not necessary when we asked, so it was not set up. We ended up setting up QoS a short time later due to issues with voice quality. However, since we have no QoS control over the inbound traffic to either location, the QoS did not completely eliminate the quality issues.

This past week, we installed a second WAN connection at the Atlanta location. The above configuration remained identical, except that we have now set the new DSL connection as the default gateway for the firewall, and are using policy-based routing to force only the VOIP traffic across the T1. We did this by specifying any traffic from either .42 or .43, or matching any of the ports listed above should use the T1 IP as the default gateway.

That all seemed to work fine, but the issue now is that occasionally, when the remote IP phone users make a call out, they get connected to the call but there is no voice on either side. Four or five tries later it finally works. Calls incoming to the VOIP phones work fine. Overall, the call quality does seem better than before due to the reduced traffic, but it's still not perfect.

Sorry for the wall of text but it's a very complicated situation. If anyone has any idea what could be causing this new problem it would really help. It did not exist at all prior to installing the DSL.

Sorry, that should read:

.42 for the MP40 and .43 for the MGI

Mavaks, if you decide you need tech help with this issue, Cox Communications (not that Cox) & Electronics has been in business since 1958. We are an authorized Samsung reseller and will be happy to assist you. We are located in Gainesville, about 50 miles north of Atlanta, but work in the Metro area daily.

Give us a call at 770-503-0000 and we will dispatch at least two techs immediately.

Thanks,

Josh Poole

Thanks for the offer, but there is already a Samsung dealer contracted on this system. Since the issues appears to be network related, I'm the one that has to work on that.

You should have ports 30000 thru 30031 opened up and pointed to the mgi card.

Have you changed the public ip address on the MP/MGI cards? since you now have a new internet connection, it will have a different static ip address then your T1 connection.

Otherwise you will need to get a wireshark trace when the failed call happens.

Ideally from both ends, but start with the system end, so you can see what ports its trying to send the traffic to the IP phone on.

Also what software version is the system running?

***edit***

Also you shouldn't need to SNAT unless you have multiple WAN ip's and you are trying to use one of these for the voip traffic.

Have you removed the SNAT entries since you are now routing via the DSL rather then the firewall they shouldn't be required anymore

You stated occasionally this happens. That suggests that correct samsung system programming is in place and the snag does lay on the Lan/Wan somewhere. Because this is intermittent i would be throwing a sniffer such as Wireshark on the Lan and proceeding down that route.

I changed the ports on Friday to reflect the full range 30000-30031. I'm not sure why the installer only gave me 30000-30012. I thought I mentioned it, but we are still using the original T1 for VOIP, so those WAN IPs have not changed. We didn't have to touch the remote phones at all...it was a pretty simple firewall reconfiguration to include the new additional WAN connection and point the traffic in the right directions. It works correctly most of the time, but once or twice per day they'll have to make 5 calls before they get voice in either direction.

I suspect it could have been the ports, since those are used to carry voice. I'll have to see if the problem has gone away today before I really know for sure.