Greetings,
We inherited a system running 4.46d MCP OS7200/ The trouble is all sets are IP some local some remote. all calls between sets are fine. if you transfer a call from one set to another there is one way audio. If you make a conference call two inside one outside both IP sets can hear the outside party the outside party can hear both IP sets the two IP sets can't hear one another. Tested with the local IP sets all on the same network and subnet. The MGI16 is release 1.14 the notes say 4.46d should be release 1.26 tried to upgrade the MGI card using the included procedure for 1.26 I can log in to the MGI card follow the procedure the software upgrade never starts to run. I'm using a laptop running windows 7 and turned off the firewall and virus protection and connected directly to the MGI card with no luck. Spoke to tech support their suggestion upgrade the system completely to an OS7200s since it would be cheaper than changing the MGI16 and MCP card. Any suggestions? Question 2 can I use the OS7200 backup to program the new OS7200s? The 7200 is a SVMI20 e and the OS7200s would be the embedded mail so that may be a small issue.
Thanks in Advance,
John
You could always send your mgi16 in and have it upgraded. That has to be cheaper then a new 20s minus the down time. What tftp program are you using solarwinds or the free set up samsung has handed out for years. I have had better luck with solarwinds but the tftp32 works ok most of the time. The problem most have is setting up their laptop as the server for the upgrade but if everything is in range it should work.
Do you see the connection from the mgi card ip in your tftp server?
Connect your laptop via SIO to the MGI card (same cable as SVMi-20e) as well so you can see what is happening.
I use the TFTP32 I login to the MGI16 see the correct IP address and type allset press enter I verify all the correct information and type reboot after that I get nothing I don't see the upgrade start or run on the screen. I don't have hyperterminal so I've used both telnet and putty. Ive also verified my pc address as the telnet server. After talking to the customer again he said this problem started over a year ago when the previous vendor upgraded to 4.46d from a 2. something release. Is there any better upgrade documentation for the MGI16 than what comes with the 1.26 software from GSBN? The customer also wants to upgrade to the latest software so he would have to replace the processor anyway and at that point Samsung recommends swapping out the MGI16 to an OAS. Ater all that the customer thinks he might go for the new 7200s to get the 5 year warranty.
Thanks
hi john I know the problem I had major issue with it.
go buy a cheap unmanaged switch plug your PC into that and the the MGI card into it and do the upgrade.
had lots of issues with CISCO, HP, Lucent switches and some intel PC cards.
Issue is during the startup the MGI looks for the upgrade server however if the Switch takes to long to neg. The Connection the MGI times out and just boots.
No need to upgrade the system just yet.
Thank you for the suggestion I did try to just direct connect to the MGI card with an ethernet cable. I was able to log in to the card and the upgrade still wouldn't launch. Not sure what I'm missing?
Upgrade the MGI 16 using an unmanaged switch as andma suggested.
Doesn't work correctly through many switches nor via direct connection (i.e. crossover cable).
Use a switch and you should be good to go.
Thank You All for your responses. As soon as the customer gives me a date to retry the upgrade I will let you know how it goes.
Thanks,
John
Update. Client decided to forklift upgrade to OS7200-s 4.70 hand programmed the new box comparing to original database. OAS card replaced MGI 16. I have the original OS7200 on the bench with the MGI 16 and SVMI 20e. Reused the PRI and 8 trk in the new system. In the new box the original problem of transfers and conference calls disappeared. Time to play, I'll try the MGI upgrade to clear the problem if that doesn't work I'll default the system and reprogram and see if that clears it. The reason for the upgrade to 7200-s? They wanted the latest and greatest software and a new 5 year warranty.
On the 7200-s the customer said for the remote IP phones he had to forward UDP 6000 to the MPS UDP 9000-9001 to the OAS and UDP 30000-30031 to the OAS. The Samsung cheat sheet I have shows both UDP 6000 and 9000 forwarded to the MPS. If that is the case is UDP 9000 supposed to be forwarded to the card where the MGI channels physically reside? Is bulletin No.: 2012-10-16 wrong? Thank you for being patient with me I harken back to the simpler times of 1A2. Sometimes this IP stuff gets me cross eyed.
Thanks,
John
udp 9000 should be forwarded to MGI/OAS
UDP 9000-9001 are used by the itp/smt ip phone for RTP/RTCP traffic respectively.
You do not need to forward these ports.
All you need is UDP 6000 to the MP20S card.
Since you have an OAS card you then need to forward 30000-30031 to that.
Since you don't have IP trunks you shouldn't need to worry about the 40000 and 45000 range of ports.
If you are still having issues i can send you the changes you will need to make to the programming due to having onboard MPS/RTG and OAS MPS/RTG and the required port forwards.
Thanks Nameless all seems good now. However if you would still like to send along the information I'm sure I could use it.
Thanks again,
John