atcomsystems.ca/forum Forums TDM Business Telephone Systems Samsung Telephones & Systems 7200 MCP (not MP20) and Ver 4.46d

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.