Two files attached. "not-working.txt" is when I call from my cell in to my extension. You'll notice that its not even checking for the caller ID text. The second file is "working.txt" which is what happens when a call into a specifically defined inbound route like our conference bridge (no SIP phone; just an inbound route that directs the call to the conference IVR). This would seem to indicate that the inbound route for default (matches the inbound DID to the extension versus going through the explicit inbound routes) is where something is missing.
BTW, thanks for all the help.
I think your right about the way in which the call arrives. I feel as if there should be a way around this. Do you use a catch all route? If so, can you see what happens when you disable it?
I *think* that establishing inbound routes in the extension, verses the inbound routes page is the same. When I establish in inbound route to a specific extension destination in the inbound routes section, it shows up in the extension definition. Or, did I miss your point?