We have experienced issues with upgrading 7200 MCP systems, specifically SPnet'd systems, to 4.46d. Odd bugs, etc.

Tonight we attempted an upgrade on a networked system and calling between sites/nodes was faulty; partially shows ext number on near end display, but no operation/audio. The MGI card is fine because external IP phones still work.

7200 MCP 4.46d to a 7100 MP10 4.46d (the 7100 seems ok)

Samsung told us to default the 7200 and program just enough to try the SPnet, we did, still would not work.

So, we were forced to go back to 4.30, upload the saved 4.30 database and now it is working fine again. Our motivation to go to 4.46d was they want some of the new features, UC, etc.

A dealer friend has told me he had similar problems and ended up going to an MP-20.

Maybe the MCP can't handle 4.46d so well? Especially on a networked system.

Anyone have any experiences to share? The reason Samsung went to the MP-20 was that the MCP had wimpy processing power, right?

Thanks!

(yes, when we went to 4.46d, we uploaded the proper SPnet license)

Got exactly the same problem! We tried to upgrade 2 7400, 2 7200 and 1 7100 to 4.46d but after upgrading the 7400 and 1 7200 (with mcp of course) we stopped everything.

Finnally tech support told us to try a downgrade to 4.30i. So we done a downgrade on 1 7400 and the 7200 and spnet come back to normal.

The bizarre thing is we still have 1 7400 running 4.46d and spnet works!!

Mario

That makes sense though because the 7200 MCP (not MP20) has the weakest processor of the bunch.

I think Samsung needs to get on this and offer some sort of MCP to MP20 upgrade.

Did you get the SPNET license when you went to 4.46?

Try turning MPS off

OFF is the default setting for MPS service in 4.46D

Verified it was off.

Have you tried running 4.42 on the 7200 MCP?
Are you running a SM or MMC style?
Did you upload the file(s) via IT Tool or via a card reader on laptop/pc?

The release notes we got stated that 4.46d fixed a clicking problem with 7200MCP SM style and ISDN BRI lines.

So based on that it should work.
I havn't put any of the 4.4x sw releases on a 7200MCP so can't help much more

Have you tried running 4.42 on the 7200 MCP? No, we hopped from 4.30 to 4.46d, or I should say tried.

Are you running a SM (IT Tool?) or MMC style? Prog both ways.

Did you upload the file(s) via IT Tool or via a card reader on laptop/pc? IT Tool - Samsung recommends that because of the .ini file updates.

We completely initialize the 7200 MCP with v4.46d and it still had the same exact problem talking to the 7100 far end v4.46d.

Without a doubt, if you have a large (this is a two cabinet system) 7200 MCP networked and you go to 4.46d, you will not be a happy camper.

We are convinced that problem is with the MCP's inferior processor as opposed to the 7200 MP-20 and other OfficeServ systems. Even the 7100 MP10a is more robust.

In our office we have two MCPs so we tried a quick test here and the result was the same; failure to call between the systems. Display shows partial info, but no audio or the phone locks up.

It is our hope that Samsung will come out with some sort of MCP to MP-20 trade-in upgrade like they did with the MP10 to MP10a.

We have contacted Samsung regarding this need.

Didn't do any, but was not the MP10 to MP10a upgrade offer VERY expensive when compared to just buying another kit and getting the phones and cards.

I'm not positive but I seem to remember the upgrade and it made sense to buy a new kit and just throw the old frame and MP10 away.

Bunnie, you need to edit out the price on public threads.

The difference between the MP10 to MP10a upgrade vs this one is the 7200 MCP simply doesn't work. Hopefully Samsung will take that into account when pricing it out, if they indeed offer an upgrade.

Otherwise, any of our networked systems will have to stay at earlier s/w levels and not be able to get UC/Messenger, etc. The MP-20 card itself is spendy, no doubt.

You can run messenger/UC phones,etc off any 4.4x software, though with the new firmware on the SMT-ixxxx phones they want you to run 4.46d software.

Because of freeing up the OAS/MGI card and SVMi20 real estate with a 7200-S, I guess going to a 7200-S with some of these would be a possible option. The MCP just doesn't cut it unless you are talking about a single, small site.

Besides the networking failure, the processor speed being so slow is very noticeable with the MCP.

There may be a solution. It appears when the upgrade takes place it forgets how to communicate with the other node via a private network. There is no more private w/ public setting.

So, it gets jumbled or clears the data. The problem does not happen on upgrades where the SPNET is talking out over the public network.

Really good news if true.

I have two 7200's with MCP cards, one 7200 with a MP20 card and just upgraded them all to 4.46d and my systems work just fine. I also upgrade my MGI card firmware to 1.26 at the same time. Since the MGI card controls the networking, maybe that is your problem.

The MGI card doesn't control the networking, the MPxx (MCP) card does.

The MGI card is responsible wholey and solely for voice only.

The private with public was only removed for IP phones, the LAN and MGI options still have private only and private with public under 4.4x software.

Sorry for wrong information. I was told by my previous dealer that it was the MGI card because it goes out on the MGI channels when we networked the systems together.

No worries, it seems to be a common misconception

Problems here as well. changed out the system link id to a real world address. Spnet works. Change back to local ip. Doesn't work. SO I guess it is ok for those that have real world assigned. But if there is no real world then no go on the set I did,

Noisy Cow and Telcom-

Any resolution to this item? Getting ready to upgrade apx. 20 OS 7200s (most with MCPs) all using SPNet with Private Networking / Private IP addresses.

Wondering if I should just get everything to 4.30 and leave it at that vs. 4.46.

Any updates, advice and/or suggestions appreciated.

Sorry, so long and missed this post; we gave up and just let MCP sites sitting at 4.30. Maybe someone else here can say if it is safe to go to 4.46d on SPNet'd MCP 7200 systems. Or if the 'pending' 4.46e fixes the IP problem.

Finally - the solution my friends. We went out to the about site we attempted back in June. Upgraded the MCP to an MP20, upgraded the PRI to 4.28, the LCP to 4.18; etc. Then it did it to us again.

Calling the other nodes got 'no user response.'

Tech support had us initialize the system and get up just the basics for a test. Then again, 'no user response.' Port 6100 was responding via telnet on both sides.

Finally my tech and the Samsung tech had a revelation. MMC 838. Set it to match the private IP range on the other side. For instance, the MP10a on node site 001 was 192.168.1.44. So we entered 192.169.1.255.

Problem solved. Damn.

I'm going to guess that you have private with public set in MMC830/831.

If so this explains why MMC838 fixed your issue, and also why leaving it at 4.30 worked, as you manually set the private/public option in MMC820 in this and earlier firmwares.

They really need todo something about the autodetection of private/public and private ip wan's

Si Senior, that is exactly what was happening. Just happy to know we can do ahead and do our other MCP-MP20 upgrades and know that they will work now.