Incoming call congestion problem....urgent help needed

I have asterisk 1.8.4.1 installed in our server along with freepbx.My problem is that whenever an incoming calls are made,the call comes in to asterisk but it finds all the extension lines as congested and hangs up.I had an inbound route to transfer the incoming calls on my pri number 555 to a sip extension registered with asterisk.But whenever i call the lines are found as congested.

these are my configs:
dahdi-channel.conf: http://pastebin.com/neznAxFh
chan_dahdi.conf: http://pastebin.com/XFqCiHi1
inbound route: http://imgur.com/BXfqx
extension: http://imgur.com/rVV78
from-pstn context in freepbx was used
debug info for call : http://pastebin.com/CykAK5bk

The calls come in to asterisk for sure,but for some reason it finds the line of the sip extension congested.Anyone help plz…cant figure out the problem.

You say you have an inbound route - however no inbound route was found for 555

- Accepting call from '8095737305' to '555' on channel 0/10, span 1
    -- Executing [[email protected]:1] NoOp("DAHDI/i1/8095737305-4", "Catch-All DID Match - Found 555 - You probably want a DID for this.") in new stack
    -- Executing [[email protected]:2] Goto("DAHDI/i1/8095737305-4", "ext-did,s,1") in new stack
    -- Goto (ext-did,s,1)

This does prove that chan 0/10 is in the from-pstn context

The first debug shows a call hitting the catch all route and then not having a route.

-- Executing [[email protected]:47] NoOp("DAHDI/i1/8095737305-4", "Returned from dial-one with nothing to call and DIALSTATUS: NOANSWER") in new stack
#
Accepting call from '8095737305' to '555' on channel 0/10, span 1
#
    -- Executing [[email protected]:1] NoOp("DAHDI/i1/8095737305-4", "Catch-All DID Match - Found 555 - You probably want a DID for this.") in new stack

Furthermore you have your inbound catch all route (no DID populated) set to go to Vikas with the very long extension number. I assume that extension is not registered.

I don’t think you have your logic setup to do what you described. The system is doing what it is told to do.

You need an inbound route matching 666 to go to a registered extension.