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

Modular Messaging 2

Status
Not open for further replies.

shandy11

Technical User
Dec 11, 2003
20
SG
I have a modular messaging installed recently on ver 2.0
There is a problem that the voice messaging. Whenever user dial the pilot number of the MM it will not prompt the "text to speech on the user name" but rather prompt user to key in the user's mailbox instead. There must be some programming wrong somewhere either in the PABX or the MM. Can someone assist? Thanks.
 
What type of boards in the MM, analog, DSE, E1/T1, or using IP ? Did you use the configuration notes from the Avaya support website? Do calls on a Busy or RNA work OK?
 
Not sure about the speech part, but You must have the extension number in the Name field of the PBX station form. I know it sounds stupid, but If you dont include the extension in the name field MM will never recognize the station the call is coming from. (at least that's how it is in 1.1)

RTMCKEE

CM 2.1.1
Prologix R9.05
Modular Messaging 1.1
 
Hi Joe,

The integration is IP and I have used the H.323 integration manual from Avaya but seems like the problem is hidden somewhere. I am using a S8700 pabx CM 2.2

RTMCKEE,
Nope. It didn't work. Thanks anyway.
 
Hi Shandy11,

Just installed mine this week and had the same problem. in the trunk group form on page 2 do you have "numbering format unk-pvt"? if so I changed mine to "unknown" and changed the "ch public-unknown table" and entered my extension length, extension code, trunk group and CPN length (extension length)

this solved the problem for me.

Good luck

 
Lifeisloud has the correct answer without the public-unknown table populated the system does not send the correct digits to the MM, so it doesn't know what extension is calling it, so as a result it plays the un-integrated answer.

The instructions above should resolve the issue, if not ensure you followed all of the steps in the H.323 Integration notes that can be found at:
Thanks,

Thank you,
VOIPEng
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top