The debugs indicate that the Avaya system is reponding with a "404 Not Found" error. That typically indicates that it does not have a route for that number. Have you checked the Avaya system to see if there is a route that matches? Is the CME system suppose to strip any digits off of the DNIS before sending it out?
Perhaps you got this working now but I recently worked out trunking between CME & Avaya IP Office using either SIP or H323.
Not sure what the nature of your problem is, perhaps troubleshooting from Avaya's end may assist but if you're receiving a 404 Not Found error, you may need to look at your incoming call route on the Avaya system for the trunk linking to the CME or ensure that you have the H23 trunk on Avaya's end pointing to the correct ip interface on CME.
If unsure and the debugs aren't helping, you can build two h323 trunks on Avaya's end pointing to the other interface (meaning that which the call originates from on the CME's end)
H323 probably being the easier method to configure.
Sample dial peer being:
dial-peer voice 1000 voip
description route to Avaya (I always do this out of practice)
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...