I discovered that my ATA registred with PBXes extension doesn't respond on incoming calls. System log shows: Zitat: Jul 14 21:16:25 VERBOSE[24516] logger.c: -- Called doronin-2000 Jul 14 21:16:26 VERBOSE[6382] chan_sip.c: SIP response 100 to standard invite Jul 14 21:16:26 VERBOSE[6382] logger.c: -- Got SIP response 486 "Busy Here" Jul 14 21:16:26 VERBOSE[24516] logger.c: -- SIP/doronin-2000-3473 is busy Jul 14 21:16:26 VERBOSE[24516] chan_sip.c: Hangup call SIP/doronin-2000-3473, SIP callid 37ef61a11abc5d12617299933552d42b@64.118.93.76 Jul 14 21:16:26 VERBOSE[24516] logger.c: == Everyone is busy/congested at this time (1:1/0/0) Jul 14 21:16:26 VERBOSE[24516] logger.c: We're at 64.118.93.76 port 38478 Jul 14 21:16:26 VERBOSE[24516] logger.c: Video is at 64.118.93.76 port 43566 Jul 14 21:16:26 VERBOSE[24516] logger.c: Adding codec 0x4 (ulaw) to SDP Jul 14 21:16:26 VERBOSE[24516] logger.c: Adding non-codec 0x1 (telephone-event) to SDP Jul 14 21:16:26 VERBOSE[24516] logger.c: -- Playing 'vm-theperson' (language 'en') I checked ATA - it shows no active calls, and I can make outgoing calls with no problems. What could cause extension think that it's busy when it isn't?
This post has been edited 1 time(s), it was last edited by dor on 15.07.2008 at 03:19.
Sometimes, ATAs loose their registration to their SIP Proxy, in this case the PBXes server. In your case what kind of ATA is provisioned at extension 2000?
It’s Linksys PAP2T. I eventually found the cause. I found my own CID in “block last caller” field, triggered by dialing *60. After clearing this field I obviously could reach my ATA again J I guess one is better be careful with dialing anything starting with *60…
Unexected SIP response 486 "Busy Here"
