I have a 7100 MP10a that I put in about six months ago, the cabinet was used, but updated to latest software, had a 16DLi, a TEPRIa and a 4 station DLi on the CPU.

A couple days ago we webbed in to make a new mailbox and create a Zero destination for the voicemail.

The customer had said the day before that he was getting an error that the voicemail was full but nothing wrong could be seen on webbing in and there was no further complaint that the voicemail was full.

Now a couple days later it seems the power would go off, no display and about ten minutes later it would be back on.

I pretty much doubt that the VM work had anything to do with the power supply now but I'm throwing in all the info.

I replaced the cabinet with another used cabinet, it took about ten minutes to power up and all seemed well, then I got a call about a half hour later that it had died again.

I've got a dozen 24 button and six 28 button phones, don't think that would kill the power.

Kinda hard to believe that two KSUs that had been working fine would BOTH have a bad power supply.

Any ideas???

Thanks, Bracha

Make sure this sytem is behind a firewall as samsung released a bulletin about some type of DOS attacks. I would personally unplug the lan port until a firewall is installed. I had two go down this week. One I put in a firewall the other I had to replace the MP20s as it completely crashed.

We have had 2 systems in the past 2 days reboot due to being in the dmz of the router (they both have sip trunks).


once we removed the system from the dmz and put in the required port forwards the problem went away.

But it does sound like either a db corruption or something on the customers lan causing an issue (had servers running management software keep hitting the system as it didn't respond correctly to its probe)

It's a *really* bad idea to connect any Officeserv to the public internet:

1. You can crash them by doing a port scan (using Nmap or similar)

2. You can telnet into them using the root account, or admin account if you haven't changed it's password

(I've tried this on 7030s and 7100s with MP10 upto 4.46e)

Unlike the old DCS/iDCS systems the Officeserv systems are linux servers with some special telephony peripherals so network security shouldn't be treated differently to any other servers.

Even if you change the admin password the default password still works. at least it did as far as 4.53 haven't tried on 4.60 with the new password they implemented.

I've been doing a bunch of testing here with different systems and found its fairly easy to crash a system even when behind a firewall with port forwards in place. You really need to make sure you block all traffic on those ports except for known IP addresses such as your office. I've been battling one location where they have figured out a way to crash the phone system so bad the voicemail corrupts and will not boot back up (7200s). When i go to login to the system after they crash it, OSDM tells me someone else is logged in from IP address XXXXXXXX but the tech programming logs do not reflect so they are not using OSDM to do it.

Hello!

I just had a client who emailed me about this problem. I have nothing to do with their phones, so if I can get a little information from you folks, I would appreciate it.

Genesiscomm, when you refer to the port forwards, are those only needed from the VoIP provider's IP addresses, or do public systems need to hit those ports? I assume that some ports need to be open always, at least to/from the VoIP provider's IPs, and some may only be needed for management.

On my firewalls, I can set up port forwarding that requires the remote site to log into the firewall first before the needed port is exposed. I do that with all sites that use RDP to their networks. That way, port scans show nothing open.

All I know about their phone system is that the WAN side is on a different IP and not touching their firewall, and there is a LAN connection that they have disconnected for now. I am not sure of the LAN connection's purpose.

Any help is appreciated!

Gregg

I have the Samsung Technical Bulletin 2012-10-16 I can email you, it won't let me copy the text and paste.

Send a real email address to phones at dock period net

I spelled out the email to avoid spammers, replace the at with @ and the period as .

Oh, and THANK YOU SO MUCH.

Customer unplugged the cable from the LAN port and all rebooting has stopped, system is fine.

Sometimes I am posting to help others and I'm really grateful you all came through to help me when I need help.

Thanks again, Bracha

G-Man
Providers or techs that need to access the system need the ports forwarded, ie 5060, 5003, 5090.... Depending on your firewall you can restrict it down to certain IP's that can access those ports. With linksys or DD-WRT you want your first entry to be the DENY ALL then after add your ALLOW ip's. Your only downside to this will be if your SIP provider regularly changes IP addresses, mine for the most part stay the same and they notify me before they change.

As far as your customer with the LAN on a public, you want to put a firewall in front of that as all ports are exposed to anyone and as said before certain passwords you cannot change so the system is very vulnerable.

With the sip port, there is a carrier-exclusive option that will make the system reject and sip packets that don't come from the server defined in the carrier options (or that resolves by a DNS lookup in the case of a dns name for the proxy/auth server address's)

Indeed, you can change the admin account password via the web interface, but the root account is still lurking on the system. I've not checked anything after 4.6 to see if the root account password was changed along with the admin password.

It's shocking how bad the implementation is if some random packets to the IP stack can cause the entire system to fall over, there are other implementaion fails too - not being able to install certificates to prevent man-in-the-middle attacks is near the top of the list.

I too have come across this issue, with a client that has 5 7100's and 1 7200S, I'm proposing a VPN solution to the client, they only use SPNet between sites so SIP trunks are not an issue, I'm planning on using PC Engines ALIX 2D13 single board computers at all locations, running pfSense and utilizing OpenVPN for the tunnels. I've successfully run about 8 tunnels at a time on these little router boxes without issue....

The idea being, make it so the Samsungs are only reachable from WITHIN the VPN tunnels, NO Port Forwards. For remote admin access, I'll simply enable the PPTP VPN server on each of the firewalls, so the only way to access the Samsung switches from outside would be to establish a PPTP VPN session with the router at that site.