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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Get busy when going to VM

Status
Not open for further replies.

vdn

Programmer
Mar 24, 2008
22
US
Getting occasional busys when going to MM VM. This is a V3.0 site with a MSS and two MAS servers. Both MAS have two PRI QSIG lines into them. I'm seeing this error msg in the Windows event log on both MAS and think it might be related to these intermittent errors.This error happens at the same time for lines 46 & 45. I reset both MAS with no luck. The MWI port is the last channel on the 2nd PRI in both MAS.


Event Type: Error
Event Source: gv_vserver
Event Category: Call Management
Event ID: 1711
Date: 3/26/2008
Time: 4:59:35 PM
User: NT AUTHORITY\SYSTEM
Computer: TCMAS1
Description:
Line device call cc_AnswerCall, failed on Channel 46, Error:- Error reason = aa - Unknown ISDN Error.
 
Did this just start or has it always done this? It sounds like the MWI port / Group may not be setup right on the MM.

Is MWI working without any problems?

Ken Means

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)
 
The intermittent voice mail issues just started a few weeks ago.They were having some issues with MWI so we installed the latest 3.0 patches a few months ago.

This event error might not have any thing to do with the "busy" issue we are experiencing.I didn't set this system up but they have the MWI set for the last port on the second PRI on each MAS. Is that a problem?

Thanks,

Dan
 
Like Ken was saying make sure the programming in the PBX and in MM follows the config note.

I was initially thinking that perhaps your channel 46 (at least on TCMAS1) wasn't a member of your MM trunk group (Avaya terms for the PBX, not sure what PBX you are using). But that didn't make sense because the call is hitting that port and could only do so if it was a member of the trunk group.

I wouldn't worry about those events (which I think are supressed in 3.1 and beyond) as those tend to happen when a call is attempting to connect to a particular channel and when MM goes to pickup that channel the caller is no longer there (hung up or they disconnected before MM could answer).

I would worry about the busies though since you have alot of ports and unless your system is horribly under planned, should not occur.

Are both servers taking about the same amount of calls? or is one server taking all the calls until that server is using up all of it's ports then is switches to the other server? If you are integrated to an Avaya PBX there are alot of ways to configure trunk(s) and route entries depending on the customer's preference of how they want the system to function.

 
Thanks for the insight.

Basically this has been working fine for a long time and recently they just started noticing occasional busies. I believe they are load-leveling between the servers but I will check.

Thanks again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top