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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Program Message Key to work with Nupoint UM
- Thread starter vlevalois
- Start date
- Thread starter
- #3
No messages is being displayed because the EMEM is setting the message and the port setting the message is not a member of a hunt group and as such it is setting a "Dialed Message Waiting" Find out why the EMEM is setting the message and correct said issue. There is a FAQ on MWI's and how to clear them if you need it.
Best if you provide information on how you have set up the message waiting for the nupoint. I am assuming you've set it up a Mitai MWI using a HCI reroute as this would be by the book but I try not to make too many assumptions.
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
Best if you provide information on how you have set up the message waiting for the nupoint. I am assuming you've set it up a Mitai MWI using a HCI reroute as this would be by the book but I try not to make too many assumptions.
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
- Thread starter
- #5
The light is being lit by the Nupoint, not the EMEM. I don't need to turn the light off, that happens on its own when I check my VM in the Nupoint.
I checked the EMEM ports and I have 1 hunt group with 20 ports, terminal.
Here's the MWI config for the Nupoint:
Group #2: "MWI"
Module 1: Lines 0:17
Fax Conn: <none>
Voice Recognition Conn: <none>
Application = [DTMF TO PBX DIALER]
Initial Dialtone Detect = [y]
Access dial string = [], Dial tone confirmation = [n]
Pre-DN ON dial string = [*90], Pre-DN OFF dial string = [*91]
Post-DN ON dial string = [], Post-DN OFF dial string = []
Suppress message light updates = [n], Wait for dial tone = [n]
Alternate Code = [n]
AT&T MWI = [y]
Max PBX Message Count = []
I checked the EMEM ports and I have 1 hunt group with 20 ports, terminal.
Here's the MWI config for the Nupoint:
Group #2: "MWI"
Module 1: Lines 0:17
Fax Conn: <none>
Voice Recognition Conn: <none>
Application = [DTMF TO PBX DIALER]
Initial Dialtone Detect = [y]
Access dial string = [], Dial tone confirmation = [n]
Pre-DN ON dial string = [*90], Pre-DN OFF dial string = [*91]
Post-DN ON dial string = [], Post-DN OFF dial string = []
Suppress message light updates = [n], Wait for dial tone = [n]
Alternate Code = [n]
AT&T MWI = [y]
Max PBX Message Count = []
The Port type MWI you've set up is not typical for a newer IP based system.
The Type you've set up will cause the issues you've described if the port is not a member of the hunt group.
You could try to make the MWI port work as is but I would recommend using the Mitai Method as decribed in the Tech Handbook.
The IP based Nupoint does not require a dedicated port setup for MWI as you have done, leaving all of the ports available for messaging instead.
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
The Type you've set up will cause the issues you've described if the port is not a member of the hunt group.
You could try to make the MWI port work as is but I would recommend using the Mitai Method as decribed in the Tech Handbook.
The IP based Nupoint does not require a dedicated port setup for MWI as you have done, leaving all of the ports available for messaging instead.
*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
- Status
Similar threads
