|
Joined: Feb 2004
Posts: 323
Member
|
Member
Joined: Feb 2004
Posts: 323 |
It's been a couple of years since I worked on a DX-80 but I remember that the first inskin VM's would not allow you to change from blind to any other option. Comdial said that it was the only method that would work with the DX-80 and it sounds like they never really got that fixed. Wait for ring is for the voice mail to be able to detect busy conditions and retreive the callbefore transfer if ring is detected it handles the call like blind. When the busy conditon is encountered it has to flash back to get the call from transfer hold and this is probably where the clipping occurs. Blind allows the call to be returned to the system with the proper reason codes. Comdial products are designed to integrate with the Key Voice in such a way that you should use blind transfer for most situations.
HTH
Kerry
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Aug 2003
Posts: 67
Member
|
Member
Joined: Aug 2003
Posts: 67 |
That makes sense. I just got a call back from the customer a few minutes ago and they said that the program change(Blind Transfer) seemed to fix the problem. No more cut-off's!!! But she said that there is one more thing that is different from the last voice-mail that was in there. When there are new messages on a phone. They check the messages and then hang-up. Then the display will blip. The display will blip from saying "New Messages: 7" to "New Messages: " It will blip 7 times that same message and then the display will clear and go back to its normal state, Date/time/ext #/name. Is there something that can be changed so that it won't do that or will it do it forever and the customer has to suffer for ever and ever. LOL Sorry evil streak. Thanks for all the help.
|
|
|
|
Joined: Mar 2002
Posts: 3,630
Moderator-Avaya, Nortel
|
Moderator-Avaya, Nortel
Joined: Mar 2002
Posts: 3,630 |
how many ports and how many of the ports are set for notification?
|
|
|
|
Joined: Aug 2003
Posts: 67
Member
|
Member
Joined: Aug 2003
Posts: 67 |
It's a four port VM. What do you mean by notification. I don't have message notification to where it calls a phone or a pager. Is that what you mean?
|
|
|
|
Joined: Mar 2002
Posts: 3,630
Moderator-Avaya, Nortel
|
Moderator-Avaya, Nortel
Joined: Mar 2002
Posts: 3,630 |
Under outcalling for the line configuration, you set which ports are able to outcall. These ports are also used to light the MWLs. You might have an issue with these.
|
|
|
|
Joined: Aug 2003
Posts: 67
Member
|
Member
Joined: Aug 2003
Posts: 67 |
What kind of issues would that be. Not all the ports are set for updating or too many. I haven't heard of that before. I have never had this problem before or people never said anything. I have an older DX-80 voicemail installation manual and I looked in it and didn't see anything except for allowing the VM ports to dial out. Is that what you are talking about?
|
|
|
|
Joined: Jun 2004
Posts: 1,367
Member
|
Member
Joined: Jun 2004
Posts: 1,367 |
JUST MY TWO CENTS: I always set up my VM's to unsupervised transfers. I always liked the idea of the phone sys. handling the call and freeing up the valuable VM ports. Not to mention I have to worry less about integration conflicts.
|
|
|
|
Joined: Mar 2001
Posts: 3,268
Member
|
Member
Joined: Mar 2001
Posts: 3,268 |
Nick: I think what Z-Man is talking about is in the LINE INFORMATION setup screen ---there is a column in there that asks "Outgoing allowed?" You can configure more ports to be used for MW paths by saying "YES". I think on an 8 port system--I generally make 2 ports out outgoing- --that's just allowing them for outgoing use--not restricting them for outgoing use. I don't recall there being much (or any) discussion of this in the DX-80 VM book. The older KeyVoice Corporate Office books have alot more stuff in them. I, too, have to agree with BillF--those VM ports are most always at a premium--and if you use supervised transfers---you seriously decrease the effectiveness of your VM ports every time you get a call. A supervised transfer uses a port at least twice as long as a blind transfer does. When traffic is minimal--it makes no difference, but when traffic is heavy---you've got a VM system that is going to be blocked up.
|
|
|
|
Joined: Aug 2003
Posts: 67
Member
|
Member
Joined: Aug 2003
Posts: 67 |
Changed the ports to allow outgoing calls and received a call from the customer saying that everything is working fine. I usually set up the ports to allow outgoing calls. Is there any cons for setting up all of the ports for outgoing calls? Like on a 4-port VM setting all 4 for outgoing calls allowed. I do that because quite a few people like to have the message notification so I allow all 4 for outoging calls. If there is a downfall for doing that please let me know.
|
|
|
|
Joined: Apr 2004
Posts: 731
Member
|
Member
Joined: Apr 2004
Posts: 731 |
The only down fall I can think of is: If your message waiting get que'd up to go out port 1 and your system is pretty busy, then the message delivery will be delayed. This may be important if your using it for emergency delivery. I always set up port 1 for no outbound and everything else for allowed outbound. ------------------
|
|
|
Forums84
Topics94,402
Posts639,370
Members49,808
|
Most Online5,661 May 23rd, 2018
|
|
0 members (),
224
guests, and
228
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|