what is a Q.SIG trunk and how do I know if I have one? 1

[RenegadeTech]

Hello all,

We are moving toward integrating with Microsoft OCS but we have older NEC hardware.

We have a NEAX 2400 IMS that I believe was upgraded to an IMX. I also believe that we are at R5 REL:03.17.033 but I am unsure how to verify this.

Right now we are just in the planning stages of the integration and the vendor is asking us to "confirm if we can get a standard T1-Q.SIG trunk off of the NEC PBX." They might as well be speaking Greek to me, but I know that some of you guys will know what this is and how I can verify this.

Thank you so much in advanced!

 

[belevedere]

If you are at rel 5, then Q-Sig is available. If you have a MAT terminal you can verify the rel with CMD DISS, Main.
Q-Sig is an industry spec special ISDN span that can connect different manufacturer systems. The integration features are somewhat limited depending on the release version and the manufacturer.

 

[gmannatl]

You can integrate using Q-Sig, but there are better integrations than this. The new OW5000 platform from NEC integrates via the OAI link (LAN CTI Link) with the 2400 and offers middleware to MS OCS. This is a much more robust integration then what they are proposing. I would talk to your dealer about integrating this way, because there would be no capacity issue to deal with on the Q-Sig trunks. Also, the OW5000 would give some other added ability. Go to the NEC website at necunified.com and perform a search for OW5000.

 

[flyingdutchmanVA]

If you do use Q-sig,you must make sure the PRT card is the right rev. as well.Older trunk cards won't do Q-sig.

 

[mtknepper]

gmannatl, all I could find was basic information around the OW5000 on NEC's website, do you know if there are any details on specific features supported such as remote call control versus call forking? Are there any technical docs that describe the integration and what is required?

 

[gmannatl]

I have not done a lot of work with LCS/OCS as I mainly work with NEC's UC products (Zeacom / UCB). I have done some installations of the older OpenWorx, but the new OW5000 has it's own client the UC700 which looks pretty nice. However, with that said this should provide for Dual Forking with RCC. It basically uses the OAI interface on the 2400 (which is actually an enhanced version of the industry standard CSTA), and "converts" this to an IP version of CSTA. It can then communicate the status of all the lines and extensions to the OCS and allows the OCS to pass commands to the PBX.

There are several UC Platforms that utilize NEC's OAI interface directly and do not need the "middleware". Also, as I mentioned the OW5000 has it's own UC client as well as some SDK's and enables features like the Mobile Client (Office extension on a windows mobile device).

Just to put in my 2 cents, I would at least take a look at what NEC has to offer in the UC arena. I don't know how many users you have, but the UCB (Zeacom) product is VERY rich with features, and the OW5000 with the new UC700 client looks pretty strong as well. The one advantage OCS is going to have is it's strong integration to MS Office, although both UCB and OW integrate nicely with Exchange for calendering, contacts, unified messaging etc. MS's products will stand out in this area.