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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Modular Messaging ELA

Status
Not open for further replies.

cjwoerner

MIS
Sep 21, 2011
3
US
We have 4 MM systems worldwide and are able to send messages back and forth between the systems.

We tried our first "broadcast" message this week and it was not received by all locations.

The message was sent from a system admin mailbox. The enhanced list to which the message was sent contains 4 enhanced lists - one for each of the 4 MM locations. Only users on the enchanced list who are on the system from which the message was sent received the message. The users in the other 3 enhanced lists did not receive the message.

The Community ID of the sending mailbox is 5 and the enhanced lists have a community ID of 12. For all MM systems, the corresponding box on the sending restrictions table is NOT checked when the sending row 5 intersects with the recipient column 12.

Any suggestions as to why the message was not received by all locations would be appreciated.

Cathy
 
No, they are not listed as trusted servers. The remote systems are listed as networked machines.
I have a ticket open with Avaya and so far they can tell that the message made it to the remote system broadcast mailbox, but was stopped at that point.
 
Well i am not sure that that will work that way. If the message was sent from a different system then the broadcast mailbox may not allow it to be sent out on the remote system.

I will do some checking but i need to know what software level the MM's. Also it would help to get a snapshot of the OHV on the remote systems when the message was sent as well as the vserever log.



Ken Means

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
 
Ken,

Avaya was able to determine the cause. I had to update the sending restriction tables on the "remote" systems so the CID of the recipient broadcast shadow mailboxes could receive messages from the CID of the "broadcast" mailbox on the sending system.

Thanks for your efforts.

Cathy
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top