sillejo

It matters if you want to light the to light on the IP Tel phones on the Cisco side. If the MWI comes from the Xpressions vm box to the Hicom 300 then routed over the QSIG trunk to CallManager, it would still need to support the MWI options for inband, otherwise CallManager will not know which phone to light or possible that it is a light on/off command at all.

Is Xpressions doing in-band with the Hicom or is it using SMDI integration? you can use a VG248 to replicate the SMDI to both PBX's if needed. We have done this before and it took a bit to figure out the signaling cable but then everything worked.

Is PRI available? THis would also be an option instead of simply a QSIG link. There is a particulare featurset needed within QSIG to get this to work I believe. Plain old QSIG won't do it.

__________________
Deus ex machina

sherlockphones

Thanks for the reply. Currently the Xpressions sits behind the HiCom and the HiCom is also connect to a Siemens HiPath. The MWI lights on the HiPath seem to work pretty well and they are using QSIG from the HiCom. The Call Manager will be connected in roughly the same way, although I think Siemens uses a different flavor of QSIG when going from Siemens to Siemens.

I'm the customer on this one and all of my experience is in the Avaya world, so I don't know Siemens or Cisco. It seems to me, though, that it should work. The Cisco vendor seems to also think it should work, but Siemens says it won't even though they can't document why. I guess we'll have to wait and see how it comes out.

~Rod

sillejo

QSIG has several flavors and there is nothing that tells me a HiCom to HiPath connection will verify the hook to the Cisco. We had a similar issue with Fujitsu where their flavor allowed them to pass MWI but it would not allow the same across to the Cisco Router.

From CM 4-1-2 Sys Admin guide:

"Message Waiting Indication (MWI) Service
In a QSIG network, when a PINX has a connected voice-messaging system that
services users in another PINX, the message center PINX can send the following
message waiting indication (MWI) signals to the other PINX:
• MWI Activate—Send a signal to another PINX to activate MWI on the served
user's phone after the voice-messaging system receives a message for that
phone.
• MWI De-activate—Send a signal to deactivate the MWI after the user listens
to messages in the associated voice-messaging system.
Note Cisco CallManager does not support the MWI interrogation service.
A PINX that is not a message center can receive MWI signals and perform the
following tasks:
• MWI Activate—Receive a signal from another PINX to activate MWI on the
served user's phone.
37-19
Cisco CallManager System Guide
OL-6504-01
Chapter 37 Understanding IP Telephony Protocols
Digital Telephony Protocols
• MWI De-activate—Receive a signal to deactivate the MWI on the served user
phone.
If the voice-messaging system connects to Cisco CallManager by using QSIG
connections or by using the Cisco Messaging Interface (CMI), the message
waiting indicators get set based on QSIG directives.
When a call is forwarded to a number and then diverted to a voice-messaging
system, QSIG supplementary services can provide the information to place the
voice message in the originally called party voice mailbox.
The Message Waiting Indication service, which uses the existing dial number for
message waiting that is set up in Cisco CallManager Administration, does not
require any additional configuration. "

__________________
Deus ex machina

sillejo

Another note in there is that full QSIG support will need the gateway to be an MGCP gateway and backhaul the QSIG to CallManager vs not doing this with an H323 config that will only support the basics of QSIG like CLID and DID

So double check that the Cisco integrator is using MGCP on that gateway (enviornements can be a mix of gateway types with no major issues)

__________________
Deus ex machina

sillejo

Also worth noting:

As of version 4.0, Cisco CallManager supports the ISO variant of QSIG that provides connections and some feature transparency between these tested QSIG PBXs:
• Avaya Definity
• Nortel Meridian
• Alcatel 4400
• Siemens Hicom
• Ericsson MD110
• IPC IPMX trading turret key system
• BT Syntegra trading turret system

__________________
Deus ex machina

rlsnelling

Just to be sure everyone understands, it does not make any sense to connect a Hicom 300 to a Hipath 3xxx, 5xxx, or 8xxx system together using Qsig. Siemens uses their own version of Qsig signalling between Siemens to Siemens systems called CorNet (short for Corporate Networking) - It was released in the 9006 systems and is only supported between 9006 and newer systems (4K, all 9006's, and most of the HiPath offerings) - Hence you can send MWI between Siemens Hicom 300 and the HiPath your connected to. Siemens uses a special signalling to the phone within the ISDN signalling that would probably prevent you from getting a MWI functional. I have been testing connecting a Siemens Phonemail 7655SE to a Cisco Call Manager using analog ports in a 1760 router and setup the SE as Analog integration. I do get the MWI lights on the Cisco phones, but I am still working out the call fwd greeting issues, but this would lend one to use LDN software between the Xpressions and the SE to be sure eveyone got lights..... a thought is a thought... Good Luck.