Mitel RAD using embedded voice mail port, hears nothing but ringback

[wyeee]

I tried to set up an RAD Hunt Group and use it for my ACD path.

This is what I did:
(ACD Path Directory Number: 8199; RAD Hunt Group: 6000; RAD VM Port Directory Number: 6001)

Detailed provisioning:

* COS:
   COS Number: 4;
   Comment: RAD
   COV/ONS/E&M Voice Mail Port:   No
   Recorded Announcement Device: Yes
   Recorded Announcement Device - Advanced: Yes
   Answer Plus Delay to Message Timer: 5
   Answer Plus Expected Off-hook Timer: 128
   Answer Plus Message Length Timer: 15     (Actual recorded announcement length is between 5-10 sec)
   Ringing Timer: 60
 
* VM Ports:
   Port ID: 20     Primary Directory Number: 6001
   (6001 is taken OUT OF embedded voice mail Hunt Group)

* Station Attributes:
   Number: 6001
   Intercept Number: 1 (default)
   COS(Day/Night1/Nigh2): 4
   COR(Day/Night1/Nigh2): 1 (default)

* Hunt Group:
  Hunt Group: 6000
  Hunt Group Mode: Terminal
  COS(Day/Night1/Nigh2): 4
  Priority: 64
  Hunt Group Type: RAD
  Phase Timer Ring: 1

  Member:
  Index: 1
  Number: 6001
  Presence: Present

* VM RAD Greetings
   RAD Set: 10
   Greeting 1: 1
   Greeting 2: 2
   Greeting 3: 3
   Times to Play: 1
(I've verified using the System Admin mailbox tool that the RAD number 1-3 are recorded/uploaded correctly).

* VM Greetings:
  Port ID: 20
  Greeting: RAD Set 10

* ACD Path:
  Path Directory Number: 8199
  Path Reporting Number: 251

  Path Options:
  Priority: 64
  Primary Agent Skill Group ID: 1 (ACD group 1 is working, without RAD/MOH though)
  Recording 1 Delay to Start Minutes:  empty
  Recording 1 Delay to Start Seconds: 10
  Recording 1 Directory Number: 6000
  Audio Settings:
   Audio Source: None
 
  Rest are default values

Now I tried the following
 1. Dial DID for 8199 from outside through SIPT
 2. Dial 6000 from internal phone
 3. Dial 6001 from internal phone

All I get were nothing but ringback tones. Looks like the RAD voice mail port (6001) is never opened. I adjusted my timer to avoid the DND situation (mentioned in some other posts). I've been trying this for a day and still can't get my RAD working.

Am I missing anything or did anything wrong? Or is there any System Options I need to adjust?

BTW, I don't have Analog License on my 3300 but I don't think it should matter. Also, Embedded voice mail/MLAA works fine.

Thanks a lot

[v2win]

What type of system? Are you sure you have 20 ports some of them only have 4 or 16 depending on the DSP resources.

Can you call port 19 does it answer?

Try calling all the ports in the voice mail system see if they answer.

Also you really shouldn't use the last 2 ports in the voice mail they are used for other things like message waiting. I usually try and use the firs set of ports.

[wyeee]

3300 running 4.2

It is confirmed that 6001 is never opened (I used a generic sip phone on 3300 to dial 6001 and there is no 200OK back).

I have 20 VM ports (I used to have all of them for VM and they worked fine). Now I am trying to use Port 20 for RAD.
All the remaining ports for embedded VM (1-19) woks fine.

OK, I'll try to change to the first port and see what happens.

Thanks

[v2win]

Did you change the ext number of the port if you did you need to restart the voicemail.
 

[wyeee]

I changed RAD to port 1 and it all starts to work now. Thanks a lot!!!!!
I don't know why the system treats port 1 and port 20 differently.

Yes, I did change the ext. I restored port 20 for regular VM and looks like it needs a restart.

How do you restart the VM? Anything beside reboot/reset the box?

[v2win]

If you change the port number back it will probably start to answer

To restart only the voicemail

Use putty to connect to the RTC on the 3300 on port 2002 connection type as raw
 
When asked enter your login credentials. This will be the same as if you were logging on via the web browser.
 
Enter the command;
 
iPVM_Stop()

After a few seconds the 3300 will respond with iPVM stopped
 
Enter the command;
 
iPVM_Start ()

After a few seconds the 3300 will respond with iPVM starting version x.xx.xx.x

[Mattmayn]

The last port on the VM handles MWI. It is a good practice to leave it alone and use other ports for applications like this.

[wyeee]

Thanks a lot guys!

I had a weird thing happening to me yesterday. 2 of my phones (1 5212, 1 generic sip) has the MWI on all the time even if there is no message in the mailbox. Drove me crazy trying to check my provisioning.

What happened was I tried couple of days ago to use my last VM port for RAD and it failed terribly. Later I changed RAD to 1st port and it worked. So I returned the last port to embedded VM. And that somehow messed MWI up (even after rebooting the box).

I tried *91+extn (FAC: Message Waiting - Deactivate) from any extn and it worked. MWIs are not blinking anymore.

On the flip side, it is very interesting that any extn can dial *90 (FAC: Message Waiting - Activate)+target extn and turn target station's MWI on and drive the other guy crazy...

[ralph]

The MWI errors would make sense if you were changing things around on port 20.

Good to hear it's working ok now.

Ralph

[sxwizard]

Note on MWI best practice. In the COS for all devices except voicemail MWI ports set Message Waiting to Off. It defaults to On and is a hold over from the old SX2000 days. Trust me - this will stop a lot of your "My light blinks but I have no message" calls. The cause of these false MW indications is someone accidentally dialing the code to turn on a MWI from a non-voicemail MWI port. The old use of this MW option was for companies that had actual "Message Centers" with operators before voicemail was widely used. (Tells how long I have been working on these systems).

[ralph]

Good tip SXwizard.
This is one of those things where you say "I knew that" but can never remember to actually turn it off.
We still get a lot of calls for "when I press my message button I ring <somebody else>"

Ralph