Message button to direct to 3rd party VM 2

[IPOtech111]

I am working a Server Edition R9.1 with a 3rd party VM system. Access to the 3rd party VM is via a hunt group with some SIP extensions making the connection. I need to be able to have the Message key on a 9611 phone go to the 3rd party VM and not the VMPro. I have tried changing the "SET MSGNUM" field in the 46xxsettings file but no luck, Message button still going to VMPro. Another thread on here recommended changing the default *17 short code to a dial feature with the telephone number of the hunt group but that did not work either. Below is the example from my 46xxsetting file. I did notice the note about the parameter being ignored for 96xx station types, so is this not possible to do with 9611's? I did also adjust the backlight settings on the 46xxsettings file to just ensure that the phones were receiving the file correctly and they were. Any thoughts are apprectiated. Thanks.

# Voice Mail Telephone Number
## Specifies the telephone number to be dialed
## automatically when the telephone user presses the
## Messaging button. The specified number is used to
## connect to the userӳ Voice Mail system.
##
## Note 1: This parameter setting is ignored for extensions
## configured as 96xx station types on the call server.
## Note 2: This parameter is supported on 364x phones and
## can be up to 50 characters, no spaces.
SET MSGNUM 7900
##

 

[IPOtech111]

I figured out a way around this. Rather than trying to actually change the way the Message button functioned through the 46xxsettings file I just put a transfer action in the VMPro Client for the Collect Default Start Point that transfers the call to 7900.

 

[Westi]

that means you run 2 voicemails, make sure it won't bite you in the behind with timing.

but clever workaround

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[IPOtech111]

Yeah. They aren't using the VMPro for anything but since it's server edition I don't really have a way to adjust it in Manager. I suppose I could stop the VMPro service on the server but then my workaround wouldn't function. Now the other thing is the "To VMail" button that comes up on the phone when you receive a call.

 

[Westi]

put a default action into the default leave point to do the same as the collect one but with maybe the target information in the call.
Not sure how the CTI will get the info but it just may work

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[IPOtech111]

Good thinking Westi, not sure why I didn't think of that myself when I was doing the collect start point. I will give that a shot.

 

[IPOtech111]

No luck there unfortunately. I can get the call to transfer to the other vm when doing this but I cannot get it to recognize which mailbox it needs to leave the message for. I tried puting in $TARGET in the source of transfer but then the voicemail system acts as if that extension is trying to login and I am prompted to enter my security code. If I leave the source of transfer blank it then prompts to enter the extension number of the person you wish to reach.

 

[Jgale99]

IPOtech111 - I do not suppose you got a solution to the to VMail button? I am working through the same thing.

 

[janni78]

He said how he solved it in the second post.

"Trying is the first step to failure..." - Homer

 

[IPOtech111]

The Message key, yes, I resolved and posted in my second post. But the To VMail button issue I have not found a resolution for.