I have run into this situation many times before, and you will never see any call information on the mgcp gateway until you have complete l2 and l3 isdn backhaul to the UCM. From your IOS gateway, it will show as registered, but from the UCM, it will show as unregistered. Once you have the PRI connected, the status on the UCM will change to registered and you will be able to see isdn l2 (q921) and l3 (q931) call information.
ok, found it and going through it now. I think it basically is saying what it uses for that route pattern (911) and uses the RG, RL, etc that I stated earlier. Still looking through it.
ok, here is what I think it says: under "call flow" (I think this is where I should be looking), it gives me the route pattern Im dialing (911), says that it hits the right route list, says that it hits the righ route group, device "end device name" is correct S0/SU0/DS1email@example.com, device says "registered". Alternate matches = none. Any ideas?
Maybe it just doesnt if the PRI isnt connected, and a loopback doesnt work for this????? Im not sure, as I have never really tried this in a lab before. I just thought Id like to test it out and so I tried it. Not KNOWING if it will work or not.
Im going to go ahead and rate this, even though Im not sure why it doesnt show up. I appreciate the help Matt. I learned about the DNA, so this has been very helpful to me. I think its configured correctly, Im just not sure why it doesnt show at the gateway. Both see each other as registered, call flow seems to go out that PRI line (looped back) according to DNA. I wonder if the call must go "through" the gateway instead of "to" the gateway before it shows??? Not sure, but Im guessing that may be it.
I have seen this problem before where no voip debug comes through, is the Route List registered? try resetting it.
Did you do a show isdn status? It must say "Multiple FRAME Established". I highly doubt this is going to work without a PRI turned up. Simply looping the interface will not be enough.
Otherwise, try "debug isdn q921" and see if you are getting SABME messages in the debugs. If you see it sending in one direction, then simply looping the interface will not work.