Like Matt said, perform a sip debug. You will most likely see that CUCM is responding with something. It may be something like 404 not found. If that is the case look at the Called number in the SIP Invite and make sure it matches your dial plan in CUCM.
On Dec 31, 2010, at 9:00 AM, Matthew Berry wrote: > You could do a "debug ccsip messages" on the CUBE and see what's taking place > in the SIP messages between the gateway and CUCM. Send that on over for us > to take a look at. > > Matthew Berry > Sr. Voice Engineer - CCIE 26721 > <F906EF75-D025-431C-B55C-27FF496CF05D[6].png> > CDW Advanced Technology Services > 7145 Boone Avenue North | Brooklyn Park, MN 55428 > Single Number Reach: +1.763.592.5987 > matthew.ber...@cdw.com > > From: "ccielab...@gmail.com" <ccielab...@gmail.com> > Date: Fri, 31 Dec 2010 08:59:20 -0600 > To: "ccie_voice@onlinestudylist.com" <ccie_voice@onlinestudylist.com> > Subject: [OSL | CCIE_Voice] Inbound SIP call to CUCM from CUBE goes unanswered > > I'm testing a cube configuration in my lab setup. > I have H.323 coming from CME to CUBE running on R1 and then SIP to the CUCM > via a SIP trunk. > I see the proper dialpeers being triggered in CUBE, but the CUCM doesn't seem > to respond to the SIP call setup inbound. > > Calls from CUCM to CME via CUBE work , so I'm pretty confident the SIP trunk > is functional. > > Short of trying to look through CUCM traces, is there a good debug on R1/Cube > that would provide some insight into whats going on? > > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
