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!

Register Log in
  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Voicemail Pro Modules not working? 4

Status
Not open for further replies.
whiteEEnerd

whiteEEnerd

Programmer
Feb 19, 2008
225
US
I am having some trouble getting my Voicemail Pro Modules working. I am using an IP500 4.1(12) with VMPro 4.1(40).

I have a module created in VMPro, and a shortcode created in Manager. Whenever I use the shortcode, instead of being taken to the module, I am taken to the default location for retrieving your messages. Interestingly, this is the same location I am taken if I change the shortcode to point to a module that does not exist.

The Voicemail boxes on this system work fine, but I cannot get the modules to work for anything. Any help is greatly appreciated!

Screenshot of Module:
Screenshot of Shortcode:
 
Sort by date Sort by votes
Did you do a save and make live?

is the voicemail busy? - the changes won't go active until all the ports are idle.

You coudl try restarting the voicemail service too

Take Care

Matt
If at first you don't succeed, skydiving is not for you.
 
Upvote 0 Downvote
does the module work?

point a ddi with the destination VM:Directory

see if that lets you access it.

or one thing i did last nweek was program a load of stuff that didnt work and i realised i was working offline

just a thought
 
Upvote 0 Downvote
Are you just trying to create a short code to test it yourself???

Create a short code on voicemail pro eg. Test and set it to goto the module you want to test.

eg.
Shortcode - *90
Feature - Voicemail Node
Telephone Number - (Name of the short code you created)

 
Upvote 0 Downvote
Change the name of the module
The name must be unique
The ipoffice already has a "Directory" wich could be the problem
When there is a duplicate name you will get silence


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
Upvote 0 Downvote
I did do a save & make live, I also restarted the entire VMPro server and the IPO, with no luck.

When I use a DDI instead of a shortcode I get the same result.

I will try changing the name of the module, but I am doubtful. I have tried it with the a module called "AutoAttendant" and "RemoteAccess" also, with the same results.

Thanks for the suggestions, keep them coming.

 
Upvote 0 Downvote
What does debugview show?

Take Care

Matt
If at first you don't succeed, skydiving is not for you.
 
Upvote 0 Downvote
Can you try to change the telephone field in : "?Directory"

I have looked in a config where i have a shortcode in a forward field of a user
This shortcode does not contain the ?
But a shortcode dailed by a user does contain the ?


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
Upvote 0 Downvote
Just run the vmpro service locale and on the desktop
Then you will see what happens

Go to services and right click on the service ( not the DBservice)

Change it to the locale account and check interact with desktop
restart the service

It will show like vmlite
Click "run" and dail the shortcode


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
Upvote 0 Downvote
I tend to use the debug view application that is on the earlier Admin CD (dect\system32 directory)

It means that you don't have to fiddle with the service settings - that can cause issues with otehr things if not put back correctly.

Take Care

Matt
If at first you don't succeed, skydiving is not for you.
 
Upvote 0 Downvote
Here is the output of debugview once I got it running and dialed my shortcode for AutoAttendant. See anything odd? (Sorry for the PIC, I couldn't successfully copy and paste it)


Note: The user name is Extn253, and the Extension is 364, so that isn't a bug, just an oversight on my part.
 
Upvote 0 Downvote
mattKnight,

Will that debugview work with 4.1? What CD version do I need to download to get it?

Thank You
 
Upvote 0 Downvote
it is opening your module AutoAttend. Are you sure that the module is set up right?

Kevin Wing
ACA- Implement IP Office
Carousel Industries
 
Upvote 0 Downvote
Thank you for the link Escorthosis!

I have been able to do some more testing, and found out it is a problem with the Voicemail Pro server itself. When I use my laptop as the server the auto attendants work as designed. Here is the debugview output for each server:

Code: 
Working:

Session: 00000064 - Receive OPEN  for session 00000064, call-id 292
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 - Access = ACCESS_UNCLUED_VOICEMAIL:
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 -     Mailbox: PSMSAutoAttend
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 -     Calling Party: 364
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 -     Display String: Extn253>PSMSAutoAttend
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 -     Target Party: 
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 -     Greeting Modifier: 
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 -     Language: enu
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 -     Call Ident: 292
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 -     Call Status: Unknown (0)
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 -     Call Type: Internal
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 -     Call Direction: Incoming
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 -     Called Party: 
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 -     DDI Number: 
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 -     Calling Party Name: Extn364
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 -     Called Party Name: 
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 - FindMailBoxByCLI 364
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 - Found MailBoxByCLI Extn364
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 - FindMailBoxByCLI 364
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 - Found MailBoxByCLI Extn364
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 - Found VMPNode PSMSAutoAttend
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 - Executing request to run node PSMSAutoAttend.Start Point.1
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 - Executing node PSMSAutoAttend.Start Point.1
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 - Executing request to run node PSMSAutoAttend.Menu.0
23/06 10:00:53.859 vmprov5s (09,5) 3448,3216:   Session: 00000064 - Executing node PSMSAutoAttend.Menu.0


Not Working:

04BFB008 PSMSAutoAttend (4), session=00000066
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 - Receive OPEN  for session 00000066, call-id 312
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 - Access = ACCESS_UNCLUED_VOICEMAIL:
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 -  Mailbox: PSMSAutoAttend
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 -  Calling Party: 364
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 -  Display String: Extn253>PSMSAutoAttend
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 -  Target Party:
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 -  Greeting Modifier:
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 -  Language: enu
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 -  Call Ident: 312
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 -  Call Status: Unknown (0)
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 -  Call Type: Internal
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 -  Call Direction: Incoming
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 -  Called Party:
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 -  DDI Number:
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 -  Calling Party Name: Extn364
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 -  Called Party Name:
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 - FindMailBoxByCLI 364
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 - Found MailBoxByCLI Extn364
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 - FindMailBoxByCLI 364
23/06 10:11:54.533 vmprov5s (09,5) 3132,3016:   Session: 00000066 - Found MailBoxByCLI Extn364
23/06 10:11:54.535 vmprov5s (06,5) 3132,3016:   VMClient::RxOpen - Created dialog 04B36AF8
23/06 10:11:54.535 vmprov5s (09,5) 3132,3016:   Session: 00000066 -  - Internal: !Internal!=Y
23/06 10:11:54.536 vmprov5s (09,5) 3132,3016:   Session: 00000066 - Configuring for reliable disconnect, IDLE time is 300.000s
23/06 10:11:54.536 vmprov5s (06,5) 3132,3016:   VMClient::RxActive 04BFB008 (session=00000066)
23/06 10:11:54.536 vmprov5s (09,5) 3132,3016:   Session: 00000066 - Receive ACTIVE  for session 00000066, call-id 312

Any ideas? The working server is my SP2 laptop, the non working server is a SP1 Vista machine.

Thanks!
 
Upvote 0 Downvote
I think that the problem might be the SP1
Remove it and try again

ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
 
Upvote 0 Downvote
Came with SP1 by default, so I can't get rid of it....

Thanks for the info, you are probably right.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

upinflamezzz
  • Locked
  • Question
300# to voicemail not working
Replies
2
Views
560
upinflamezzz
upinflamezzz
lsavaya
  • Locked
  • Question
Voicemail Pro client Compatibility issue
Replies
4
Views
615
lsavaya
lsavaya
sheldoom
  • Locked
  • Question
Voicemail Pro Mailbox Password
Replies
5
Views
741
budbyrd
budbyrd
Chris S
  • Question
Question about analog extension modules
Replies
13
Views
667
ipohead
ipohead
Abraham Sheehan
  • Locked
  • Question
Voicemail PRO UC module SFTP Backup
Replies
5
Views
731
Abraham Sheehan
Abraham Sheehan

Part and Inventory Search

Sponsor

Back
Top