« previous next »
Pages: [1]   Go Down

Author Topic: Voicemail Stops working  (Read 5899 times)

Offline JasonTL

  • Sr. Member
  • ****
  • Posts: 208
  • Country: us
  • Karma: +0/-1
    • View Profile
Voicemail Stops working
« on: April 17, 2014, 12:53:03 PM »
I have a location that is reporting vm is not working. they cannot forward to vm and if I dial a vm port (ie. 1101) I get a busy. If I use the vxworks commands (iPVM_Stop/Start) it does not help, but a system reboot corrects the issue. I have 30 trunks available and only 9 vm users at this site. They do have another location but they have 30 trunks also and more users (35+) but are not having any issues.


Jason
Logged

Offline acejavelin

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4100
  • Country: us
  • Karma: +133/-0
  • High-tech, heavy metal redneck!
    • View Profile
    • Like what I do and wanna help out? Send me a donation!
Re: Voicemail Stops working
« Reply #1 on: April 17, 2014, 01:22:36 PM »
What controller and DSP resources do they have, depending on the configuration of the system and the type of system, you may have to many ports assigned?
Logged

Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: Voicemail Stops working
« Reply #2 on: April 17, 2014, 01:29:58 PM »
What do you get if you stat a VM port from command line?

Ralph
Logged

Offline JasonTL

  • Sr. Member
  • ****
  • Posts: 208
  • Country: us
  • Karma: +0/-1
    • View Profile
Re: Voicemail Stops working
« Reply #3 on: April 17, 2014, 02:35:50 PM »
They have a 3300 MXe running 5.0 software load 11.0.0.102.

I don't have cmd line access at the moment, is their a maint. cmd I can run to give you the correct info?


Jason

Logged

Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: Voicemail Stops working
« Reply #4 on: April 17, 2014, 03:17:15 PM »
I'd like to know if the ports are busy or out of service.
So use the maint command stat ext <VM Port>
Note that you're stating the port and not the pilot number to VM.

Ralph
Logged

Offline JasonTL

  • Sr. Member
  • ****
  • Posts: 208
  • Country: us
  • Karma: +0/-1
    • View Profile
Re: Voicemail Stops working
« Reply #5 on: April 17, 2014, 03:26:56 PM »
VM pilot is 1100. Ports started at 1101. Here is 1101 through 1103

  Location    | Device               | State         |  Owner  | ID   |Status   
----------------------------------------------------------------------------   
 1 4 27   1  1| Superset 4150        |Idle           |         |      |         
 1 4 27   1  2| Unassigned           |Not applicable |         |      |         
 1 4 27   1  2| Alternate Codec      |Idle           |         |      |         
----------------------------------------------------------------------------   
  Location    | Device               | State         |  Owner  | ID   |Status   
----------------------------------------------------------------------------   
 1 4 27   2  1| Superset 4150        |Idle           |         |      |         
 1 4 27   2  2| Unassigned           |Not applicable |         |      |         
 1 4 27   2  2| Alternate Codec      |Idle           |         |      |         
----------------------------------------------------------------------------   
  Location    | Device               | State         |  Owner  | ID   |Status   
----------------------------------------------------------------------------   
 1 4 27   3  1| Superset 4150        |Idle           |         |      |         
 1 4 27   3  2| Unassigned           |Not applicable |         |      |         
 1 4 27   3  2| Alternate Codec      |Idle           |         |      |         
----------------------------------------------------------------------------   
Logged

Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: Voicemail Stops working
« Reply #6 on: April 17, 2014, 03:36:53 PM »
looks like it's working now.
We'll need to see it when it fails.

Also,
When it fails I'd like you to enter and post the results for this command:
reso 1 4 27 1 2

Ralph
Logged

Offline JasonTL

  • Sr. Member
  • ****
  • Posts: 208
  • Country: us
  • Karma: +0/-1
    • View Profile
Re: Voicemail Stops working
« Reply #7 on: April 21, 2014, 11:13:47 AM »
If/when we have the issue again, I will get the correct output for you. Thanks for the help.

Jason

Logged

Offline Mattmayn

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1069
  • Country: vi
  • Karma: +14/-0
    • View Profile
Re: Voicemail Stops working
« Reply #8 on: April 23, 2014, 02:18:17 PM »
What do you mean by 30 trunks? Are you talking about VM ports? If not, how many VM ports are configured on the system?
Logged

Offline JasonTL

  • Sr. Member
  • ****
  • Posts: 208
  • Country: us
  • Karma: +0/-1
    • View Profile
Re: Voicemail Stops working
« Reply #9 on: April 23, 2014, 03:20:05 PM »
yes 30 VM ports, sorry. I am a networking guy and new to the telephony side.
Logged

Offline JasonTL

  • Sr. Member
  • ****
  • Posts: 208
  • Country: us
  • Karma: +0/-1
    • View Profile
Re: Voicemail Stops working
« Reply #10 on: April 30, 2014, 11:34:34 AM »
We had this issue again, I am copying the output you requested. The last two entries are the RESO command outputs.

----------------------------------------------------------------------------   
  Location    | Device               | State         |  Owner  | ID   |Status   
----------------------------------------------------------------------------   
 1 4 27   2  1| Superset 4150        |Idle           |         |      |         
 1 4 27   2  2| Unassigned           |Not applicable |         |      |         
 1 4 27   2  2| Alternate Codec      |Idle           |         |      |         
----------------------------------------------------------------------------   
  Location    | Device               | State         |  Owner  | ID   |Status   
----------------------------------------------------------------------------   
 1 4 27   5  1| Superset 4150        |Out of Service |         |      |         
 1 4 27   5  2| Unassigned           |Not applicable |         |      |         
 1 4 27   5  2| Alternate Codec      |Out of Service |         |      |         
----------------------------------------------------------------------------   
  Location    | Device               | State         |  Owner  | ID   |Status   
----------------------------------------------------------------------------   
 1 4 27   6  1| Superset 4150        |Out of Service |         |      |         
 1 4 27   6  2| Unassigned           |Not applicable |         |      |         
 1 4 27   6  2| Alternate Codec      |Out of Service |         |      |         
----------------------------------------------------------------------------   
  Location    | Device               | State         |  Owner  | ID   |Status   
----------------------------------------------------------------------------   
 1 4 27   7  1| Superset 4150        |Out of Service |         |      |         
 1 4 27   7  2| Unassigned           |Not applicable |         |      |         
 1 4 27   7  2| Alternate Codec      |Out of Service |         |      |         
----------------------------------------------------------------------------   
  Location    | Device               | State         |  Owner  | ID   |Status   
----------------------------------------------------------------------------   
 1 4 27   8  1| Superset 4150        |Out of Service |         |      |         
 1 4 27   8  2| Unassigned           |Not applicable |         |      |         
 1 4 27   8  2| Alternate Codec      |Out of Service |         |      |         
----------------------------------------------------------------------------   
Circuit not owned by an active Call Process - RESOURCES Aborted                 
Circuit not owned by an active Call Process - RESOURCES Aborted                 


Logged

Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: Voicemail Stops working
« Reply #11 on: April 30, 2014, 11:47:44 AM »
Not what I expected to see.  I expected to see ports tied together.

I don't know on this one.   Could be a hardware fault.  Could be a software fault.
I can't think of anything possible in programming that would cause the ports to go OS.

I couldn't find an known issue on MOL.
It might be worth upgrading or simply re-installing the software.

Ralph

Logged

Offline JasonTL

  • Sr. Member
  • ****
  • Posts: 208
  • Country: us
  • Karma: +0/-1
    • View Profile
Re: Voicemail Stops working
« Reply #12 on: April 30, 2014, 12:14:09 PM »
Thanks for the reply. Even the ports that were in an idle state could not be used. Dialing any VM port gave one ring and then busy. I rebooted the system for the customer and it is now working fine.

They are currently on 5.0 so I am scheduling the upgrade to 6.0 SP3 in the next few days.
Logged

Offline Mattmayn

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1069
  • Country: vi
  • Karma: +14/-0
    • View Profile
Re: Voicemail Stops working
« Reply #13 on: May 08, 2014, 08:15:21 PM »
This is a little old but do you have the DSP resources for 30 VM ports? Is the VM hunt group circular or terminal?


Sent from my iPhone using Tapatalk
Logged

Offline JasonTL

  • Sr. Member
  • ****
  • Posts: 208
  • Country: us
  • Karma: +0/-1
    • View Profile
Re: Voicemail Stops working
« Reply #14 on: May 28, 2014, 12:55:18 PM »
Sorry, just seen the reply. We upgraded from 5.0 to 6.0 SP3 and have not had the issue yet.

J
Logged

Pages: [1]   Go Up
« previous next »
 

Sitemap 1 2 3 4 5 6 7 8 9 10