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!

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

Prefix & Monitoring

Status
Not open for further replies.

troyz

IS-IT--Management
Dec 5, 2004
79
US
Ok I have 2 different issues. I am on ver3.0

I added a prefix of 91 to the PRI Lines so the phone manager users can dial from the missed calls list. (before adding it gave a shortcodes invalid). That works fine now.

My problem is that it adds the 91 to all calls in voicemail, for example a (920) 867-5309 (Tommy Tutone) would be read as a call from extension 919208675309. Which my users find annoying when writing the number down. Is there a way to fix this short of taking out the prefix, and not letting phone manager users be able to dial missed calls?

Second Problem: ( I am almost positive this showed up in 3.0)

When doing a call monitor I get a call rejected with the tone if the call is not in the connected status. Meaning if the person being monitored is dialing, or is ringing then you get a call rejected. Scenario: Sales Group Manager uses Phone Manager Pro to see which Sales Rep is on the phone, Phone Manager does not show if dialing, ringing or call is actually connected. So repeatedly throughout the day this person will get call rejected, call rejected many times while trying to do call monitoring. This is very annoying. Any way to fix this?
 
What you experencing is an "Avaya Fix" Pre 3.0 you could set up a monitor to an enactive station and leave it up catching the calls as they came to it. In 3.0 you can only initate a monitor on an active call. I took it Avaya and they say " oh ya, we fixed it" So it is WAD (working as designed)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top