Avaya Aura System Manager error when Commit Dial Pattern

[osheros]

I don't see any forum specific to Avaya Aura System or Session Manager so this seems to be good enough.

I'm running System and Session Manager 6.0 (in the process of downloading the 10 files I need to upgrade these to 6.1 but PLDS won't let me get the System Manager files, ugh).

Anyway, when I try to add new or change existing Dial Patterns, I get a big ugly error when I click Commit (see below). I've rebooted the System Manager VM and both of my Session Manager boxes, checked the replication status, ran the diag tests, etc. No issues reported anywhere.

Anybody have any thoughts? I'm working on getting the boxes added to our maintenance agreement but Avaya is not fast on that and they won't help me at all without it (good policy, Avaya).


The following errors have occurred:
Detailed Cause: java.sql.BatchUpdateException: Batch entry 0 insert into NRPDigitmap (updatedatetime, version, opMode, scrush_id, syncState, notes, csdomain_id, deny, digitpattern, maxdigits, mindigits, routingorigination_id, treatasemergency, zone_id, id) values ('2011-11-03 10:17:29.792000 -06:00:00', '0', '0', NULL, '0', 'ABQ DIDs 5058555200 to 5259', '1', '0', '50585552', '10', '10', '2', '0', NULL, '327683') was aborted. Call getNextException to see the cause.5. Batch entry 0 insert into NRPDigitmap (updatedatetime, version, opMode, scrush_id, syncState, notes, csdomain_id, deny, digitpattern, maxdigits, mindigits, routingorigination_id, treatasemergency, zone_id, id) values ('2011-11-03 10:17:29.792000 -06:00:00', '0', '0', NULL, '0', 'ABQ DIDs 5058555200 to 5259', '1', '0', '50585552', '10', '10', '2', '0', NULL, '327683') was aborted. Call getNextException to see the cause. [java.sql.BatchUpdateException] org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch update4. Could not execute JDBC batch update [org.hibernate.exception.GenericJDBCException] javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch update3. org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch update [javax.persistence.PersistenceException] javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Can't commit because the transaction is in aborted state2. [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Can't commit because the transaction is in aborted state [javax.transaction.RollbackException] java.lang.RuntimeException: javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Can't commit because the transaction is in aborted state1. javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Can't commit because the transaction is in aborted state [java.lang.RuntimeException] -

 

[osheros]

Hmm.. I think the server was out of disk space. And now the database is corrupt. I have a backup of the XMLs, thankfully, but now it's time to beg my Avaya account rep to open a ticket for me.

 

[jaxuser]

Don't know how else to contact you for this question. I read an old thread of yours from 2010 regarding MM to CS1K issue where no answer calls to key 1 going to backdoor or MM if key 0 busy...what did you do to resolve this? Having same issue and bumped it to Avaya but no word on fix yet.
Thank you.

 

[osheros]

I takled to a couple techs that said they think there's a setting in the system that is wrong but they can't say specifically which one. They believe if I changed the way key 1 is setup, this wouldn't be a problem. However, we haven't gotten around to it.

Instead most of the user on this system are still using Call Pilot for voiceamail. For the few people we've moved to MM, I added the funky extension as a secondary extension to each user's account. This could be a permanent solution except that you cannot import secondary extensions into MM. So basically I'm stalled out on my MM deployment right now at this site until I fix the buttons or find the bad setting. I have another project to convert the site to using our 5-digit dial plan so I figured that would be the chance to fix it by fixing the keys.

Hope that answers your question.

 

[jaxuser]

I'm waiting a callback from Avaya on this...been working with them for 2 weeks now. We know it works as it works on another systm for this customer. South to North works but North to South does not. Same s/w rls, same Deplist, same programming...really weird; maybe if we get mine fixed it will help you. Only issue we are having is with 4 digit dialing between locations, got external working. PBX is sending CLID on rollovers instead of dialed DN.

 

[jaxuser]

osheros...

restatement of issue I had>>>>
callers from another site dialing 4 digits into CS1K with Key 0 of called ext. being busy; calls hunt up to Key 1 and on no answer go to Modular Messaging "backdoor". External calls coming in with same scenario went to personal greeting. Internal calls with same scenario went to personal greeting.
Worked with Avaya for weeks...fix was to change NCRD to NO in RDB for route that 4 digit callers came in on.

Don't know if this will help you or not but I wanted to let you know what our fix was.