Topic: OfficeServ 7200, ip phones and MGI

[mfield]

Hi

I upgraded our 7100 to a 7200 a while back as we were moving over to PRI and I needed more slots. I have successfully installed and configured PRI, SVM, and all of our stations and trunks work fine. When TWBC finally ported our primary number the other day i was finally able to remove the analog trunk card to make room for the MGI card so I could get the two remote IP phones working again.

I got the MGI card in and initialized, assigned numbering etc and the IP phone, either when connected to the local network at the office or here in my house can successfully register with the system. It can receive calls fine, either from other extensions or from external calls. It can make calls to other extensions no problem. What it can't do is place external calls. I can pick up a line no problem and get a dial tone but once dialed i get a "CO Hung Up" message after a couple of seconds. They worked fine on the 7100 although that was using the MP10 and not MGI.

I have searched through OSM for something I might have missed, but the extension appears to be in all the same groups and have all the same preferences as every other station.

Its a 7200 with MCP, TEPRI, 16DLI2, SVMi20E, 8COMBO and MIG16 installed. MCP is currently on a dedicated external IP which is DMZ'd, MGI is connected to the internal network and has public and private IPs defined. Port 30000 is forwarded to the MGI card.

Can anyone point me in the right direction, are there ports that need to be forwarded to the MGI card? I am a little unclear (obviously) on the interaction between the MCP and the MGI.

thanks in advance

Matt

[MacGyver]

Hi Matt, and welcome the board. 

I have a few thoughts, but unfortunately I'm not a Samsung tech so I'd rather not send you on blind rabbit chase.  The fact that the IP phone isn't working from inside the LAN is telling.  However, the fact that the IP phones did work previously certainly does point back to the MGI. Unfortunatley I have no experience with the Samsung MGI.

It's normally pretty dead around here on the weekends, but Larry is one of our Samsung brains and he does usually check in several times a day.  Hopefully he'll have some thoughts.  I think Dave has some Samsung experience too and he checks in daily.

[CMDL_GUY]

Most likely a programming issue regarding the PRI and MGI channels.  It may be an issue of inter digit timing on the PRI channels.  I'll bet you get the same message from a digital station if you pause long enough between digits.

I do have to wonder why you went from the 7100 right to the 7200 without opting for the 7200s!

[mfield]

Thanks for the welcome

Went from the 7100 to the 7200 because i managed to pick one up, fully populated with cards for $800 on ebay. By the time i sell the 7100 and the unused cards i'll have turned a decent profit for a vastly better system. Nothing more to the decision than that. I wasn't even aware there was a 7200-s to be honest.

I have not seen the same message at all on any of the DCS stations, the PRI part has been functioning with them happily for over a month and no user has experienced any issues. Likewise, there's no issues with calling other extensions at all, only trying to dial out over the PRI. As such it does seem to be something to do with the MGI>PRI interface, but that is where my experience ends given that the whole MGI thing is new to me.

[mfield]

Actually i just managed to resolve it. I remembered that I had seen that CO Hung Up message on when initially setting up the PRI, until I had filled the PRI numbers with valid CLI numbers.

So on a hunch i checked 2.4.3 and the IP phone numbers range were all defaulted to sending their extension. Changing to the master 10 digit number instead resolves the issue.

[Keighlar]

Nice detective work.   

[MacGyver]

That's awesome, Matt.  Thanks for updating the thread, and please don't be a stranger.  It's always nice to have real techs on the board. 

[CMDL_GUY]

So it was the PRI failing on an error code.  I didn't think about the outpulsed number, but that will cause the condition.


Good job!   

[mfield]

Thanks, I am definitely going to become a regular visitor here, I kind of walked into the whole OfficeServ thing a few years back when I started in my current position. The company had a 7100 system that they had purchased a few years prior. My position as VP Technology, covers everything on the tech side we do as a small growing company, from component level repair to database programming, whilst supporting a multi platform network and a rental business that supplies interpretation and meeting technology. For us the phone system isn't just a general business tool. One of our lines of business is multilingual conference calls and we have in house systems that connect over multiple lines to enable this.

Came a point where I needed to add a bunch of analog ports to interface with this system. I had already had some brief and expensive dealings with our phone vendor who seemed to be fumbling around. I figured, given my background it, it was foolish to remain in the dark as to the operation of the system when i spend my days programming all manner of other technology professionally, and our business depends on it working. Consequently we are now our own telecoms vendor.

Back to the 7200 though, I have a few other niggling issues I am going to work through now I have found this font of knowledge. Hopefully I can contribute something in return.

Matt