Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MWIs Across Networked Option 11Cs

Status
Not open for further replies.

ba7389

IS-IT--Management
Feb 25, 2004
72
US
Can Message Waiting Indicators be set from a central PBX/unified messaging location on networked remote (SL-1 ISL) branch location PBX stations?

Situation - Using an Nortel Meridian Option 11C, Exchange 2007 Unified Messaging, a Dialogic T1 QSIG gateway, and a Geomant MWI server at the HQ location. Would like to consolidate unified messaging for four locations at this building, but have not yet found a way to control MWIs at the remote sites through the single gateway. Can do this if we add a gateway at each branch PBX, but would prefer not to.
 
You will need to have the NMS PKG 175 in the PBXs. Also onthe Q.Sig links you need to provision QMWI in the RCAP to allow Q.Sig Message Waiting.

Should be no problem at all.

911Guru
 
Thanks for quick response...will give it a try.
 
Have the package and already had QMWI set on the T1 QSIG connecting the Dialogic gateway and the central PBX. The links between the central and remote PBXs are currently ISL. Are you suggesting that MWIs could be set if the inter-switch links are configured as QSIG vs. ISL? Appreciate the assistance.
 
Am set for Meridian-to-Meridian MCDN SL1 on the inter-switch links already. Are there specific RCAPs required for links needing to set MWIs between SL-1s like there is between an SL-1 and a DMS-100?

We are using the QSIG link only for the connection between the PBX and the gateway at the central location.
 
Nothing special on the MCDN Links, but you will HAVE to have QMWI on the Q.Sig link.

Also make sure you have PKG 175 NMS.

911Guru
 
Still no luck.

One of the remotes does not have PKG 175 NMS, but the HQ location and other remotes do. I think that 175 is only required for the central site anyway, but have the same indications on the remotes, regardless of presence of that package.

Do you have this working across sites in a similar or identical environment? Is so, would appreciate a dump of the settings on the routes and D-channels. Will probably just go with additional gateways pointing back to the same UM server, since that seems to work very cleanly. Would still like to figure out why it isn't working this way, however. Thanks for help and patience.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top