*17 short code premature prompt night service not working correctly 1

[DanieliaAdmin]

Trying to figure out an old problem for an Avaya IPOffice environment, during night service outside callers go directly in a remote voicemail voice prompt (*17 shortcode) instead of getting the night attendant prompt; I fix the issue with a reboot of the vmail server however I think this is more of a band aid than a true fix. Anyway, I’ve traced the call transactions and wondered if anyone had any ideas on a better fix; the first trace from sysmonitor is the premature ip office prompt no night service working ; the last two traces were done after a reboot of the vmail server with night service working correctly, let me know your thoughts.


1st trace night attendant not working goes directly to *17 shortcode:

33876mS CMExtnRx: v=, p1=1004
CMVoiceMailMsg
Line: type=RAS 1
Call: lid=0 id=1004 in=0
Called[Summary] Type=Default (100) Calling[0,33,0] Type=Default



2nd & 3rd traces night attendant working:

2nd trace -
31236mS PRN: CLAIM called on call which is not ACD A=5.24.1 B=0.4779.0
31252mS CMExtnRx: v=, p1=1004
CMTransfer
Line: type=RAS 1
Call: lid=0 id=1004 in=0
Called[139] Type=Default (100)
Product Unknown
Cause=126, Transfer(IPO)


3rd trace -
50232mS PRN: CLAIM called on call which is not ACD A=5.1.1 B=0.4786.0
50253mS CMExtnRx: v=, p1=1004
CMTransfer
Line: type=RAS 1
Call: lid=0 id=1004 in=0
Called[139] Type=Default (100)
Product Unknown
Cause=126, Transfer(IPO)

 

[IPOKoolaid]

I'd try running the debug utility. It shows you exactly what the voicemail system is doing. Its much better than trying to figure out what sys mon is saying.

Also, how are you routing calls to the AA? What does your incoming call route look like? Is your AA configured as a mdl or shortcode in VMPRO?

 

[DanieliaAdmin]

Thanks for replying. I believe I found the fix, there was a conflicting programmed routine in the nightservice leave in VMPRO.