hmmm. I have an SV8100 that two service providers are trying to get Call Accounting to work with. I configured the PBX to talk nice with the Call accounting software now it needs to talk to the Property Management software. These guys are going round and round with each other and the final verdict is:

The interface guy on the other end has no clue what that means...nor do I.

In the interest of expedition and stopping the incessant game of hot potato...What the hell does that mean? And what program number can I find that in?

The way he put quotes around "Model 90" makes me think he's messing with the other guy, like it's made up like an "ID-10T" error.

If Call Accounting and PMS aren't playing nicely together, arrange a vendor meet. Get everyone in one room, where nobody can say, "Oh, it's the guy who's not here." You can also do this on a conference call or skype.

So long as the PBX talks to CA, the PBX is doing its job.

Now, I had a problem way back in the dark ages with a Maxial PMS that looked at a string ^J xxxxxxxxx xxx xxx ^M^J^L and misread it because ^J was start-of-text and ^M was end-of-text, so the second ^J started a new text input that never closed and locked the port. I had them change EOT to ^L and everything was fine.

So this might be something like that. In theory, the CA provider will have tested with most major PMS providers...

well, that's my thought as well, but it's no different being in between say Verizon and our phone tech. Phone tech insists it's Verizon (which it usually is) and Verizon saying it's the switch. Progress is halted and both parties give up.
I'm not entirely sure it's Call Accounting tey're talking about. I made sure PBX was talking to CA myself with the CA vendor and some tweaking. I think they're actually referring more to the Hotel/Motel functionality in the switch Check In/Check Out, Clean/Dirty etc.
From what I understand the will communicate with the PMS in the NEAX Model 90 protocol, but doesn't do so natively. I'm curious what program controls how the 8100 speaks to the PMS. There's nothing in 42-xx except port assignment etc.

The 8100 is supposed to have the licenses and the box that nec makes to accomplish this. It's an interface box that can be configured to talk to the phones system/voicemail (the correct one)/and the PMS system of the end user.

SV8100 to PMS is model 90 or model 60 done via a PVA card in the SV8100. If you have a UM8000 VM this is also handled by the PVA on the same connection to the PMS. The SMDR out of the 8100 is IP data sent to the call accounting. The call accounting will send it to the PMS via a comport using HX (Holidex) or HB (Hobic) interface. But all setups are different & can be hard to troubleshoot.

Apparently there's a PMS-U10 stand alone configurator. And of course I've long lost the disk. But reading through the manual that's where one sets the protocol for communication with the PMS, one of which is NEAX90.

The PMS-U10 is usually for the Asprire and UX and other NEC switches.

There is an SV8100 PMS devepolers guide that has all of the info on the protocols ant it shows the sv8100 hooked up to the PMS-U10.

I think the default is KTSi protocol

Generally The SV8100 uses a PVA card that is confiured via an IP connection and it has a web interface.

As far as someone calling it a Verizon problem - there is No Way.

The PMS-U10 was for use on the SV8100 as well but was a dog to keep working. We did one here and that was our last and it has been bypassed..
Most PMS systems installed down here justs use the Hotel/PMS license and have the PMS connected via IP in PRG42.. Plus how many hotel guests these days use in-house voicemail. Most use their cell fones.,.

I am fighting an uphill battle to get an SV to talk to the Um8000 reliably. They use the VM for wakeup calls primarily.

We were told it's not really supported and unreliable and to use the fone system wakeup..

sorry, i let this lapse, but for posterity...

turns out there wasn't a PMS-U10 at all here. The PMS interface was on CF in the CD-PVAA blade. so a bit of mucking around in 10-55 to assign it an IP then setting the license code and I could hit it from a browser. Not much you do in the interface itself except, of course tell it what language to speak...in this case set it to NEAX90 and all is well.