From: "Dmitry Akindinov" Received: by mx.demos.su (CommuniGate Pro PIPE 5.0.14) with PIPE id 548508685; Tue, 05 Mar 2013 12:11:35 +0400 X-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD, SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2-st1.demos X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 3.3.2-st1.demos (2011-06-06) X-Spam-Report: -1.3 points, 5.0 required; * -0.0 SPF_HELO_PASS SPF: HELO matches SPF record * -0.0 SPF_PASS SPF: sender matches SPF record * -0.8 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain * -0.5 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 AWL AWL: From: address is in the auto white-list Received: from moscow.stalker.com ([89.175.185.228] verified) by mx.demos.su (CommuniGate Pro SMTP 5.0.14) with ESMTP id 548508688 for CGatePro@mx.ru; Tue, 05 Mar 2013 12:11:31 +0400 Received: from [37.204.175.169] (account dimak@mail.moscow.stalker.com HELO [192.168.0.112]) by mail.moscow.stalker.com (CommuniGate Pro SMTP 6.0.2zf) with ESMTPSA id 36430141 for CGatePro@mx.ru; Tue, 05 Mar 2013 12:11:26 +0400 Message-ID: <5135A8AA.9080301@stalker.com> Date: Tue, 05 Mar 2013 12:11:22 +0400 Organization: Stalker Labs User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: CommuniGate Pro Russian Discussions Subject: Re: [CGP] Error Code=500-failed to route the address References: In-Reply-To: Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit Здравствуйте, On 2013-03-05 12:05, victor.shkrob@sevastopol-hotel.com.ua wrote: > Добрый день! > Неделю назад перестал работать один из SIP провайдеров. > Сначала грешили на провайдера, дергали его, т.к. у них закрыт пинг. > Потом на роутер. > В конце-концов решили проверить софт-телефоном. > Телефон заработал нормально. > И ещё интерессный факт - входящие звонки работают. > Не подскажите в чем может быть проблема? > Вот лог CGPro (версия 5.4.9, OC - Windows 8 x64) > > 09:39:37.557 4 PBXLEG-002098 enqueued > 09:39:37.557 2 PBXLEG-002098 'gatewaycaller' created for pbx@domen.ua > 09:39:37.557 5 PBXLEG-002098 REQUEST posted > 09:39:37.557 4 PBXLEG-002098 INVITE request received > 09:39:37.557 2 PBXLEG-002098 DIALOG-000080(inp) started with 1401@domen.ua(sip:1401@192.168.11.92:3488)(canTransfer) > 09:39:37.557 2 PBXLEG-002098 session refresh=1800(active) > 09:39:37.557 2 PBXLEG-002098 peer authenticated as '1401@domen.ua' > 09:39:37.557 4 PBXLEG-002098 remote SDP set: peer > 09:39:37.557 5 PBXLEG-002098 remote SDP: [[871-29689 [192.168.11.92] audio([192.168.11.92]:62498(3,0,8,101)]] > 09:39:37.557 5 PBXLEG-002098 leg state=8 > 09:39:37.557 4 PBXLEG-002098 signalling completed(init) > 09:39:37.557 5 PBXLEG-002098 pbx state=1(inited), active > 09:39:37.557 2 PBXLEG-002098 gatewaycaller.sppr(Main) started > 09:39:37.557 2 PBXLEG-002098 ProgramLog: "calling '0444660466'..." > 09:39:37.558 2 PBXLEG-002098 ProgramLog: "Price: #0" > 09:39:37.558 2 PBXLEG-002098 ProgramLog: "callerLeg:{\"\"=\"sip:0444660466@89.162.254.10\";Call-ID=F71EC2B42AB82E598A0EB534BF1B42DC30D2A05C.gwout7828;From=\"sip:0444961494@outbound.ip\";Max-Forwards=#69;Via=89.162.254.10;activeSide=YES;callBridged=YES;impersonate=1401@domen.ua;provisionDTMF=YES;}" > 09:39:37.558 2 PBXLEG-002098 spawning PBXLEG-002100 > 09:39:37.558 5 PBXLEG-002098 remote SDP(0) retrieved: [[871-29689 [192.168.11.92] audio([192.168.11.92]:62498(3,0,8,101)]] > 09:39:37.558 2 PBXLEG-002098 Event([bridgeStart]) to NODE-002100 sent > 09:39:37.558 2 PBXLEG-002098 bridge(NODE-002100) starting > 09:39:37.558 5 PBXLEG-002098 pbx state=8(starting bridge), timeout=600s > 09:39:37.558 5 PBXLEG-002098 timeout set for 600 secs > 09:39:37.558 5 PBXLEG-002098 EVENT posted > 09:39:37.558 5 PBXLEG-002098 pbx state=8(starting bridge (final)), timeout=0s > 09:39:37.558 1 PBXLEG-002098 bridge(NODE-002100) start transaction failed. Error Code=500-failed to route the address->Server Internal Error > 09:39:37.558 1 PBXLEG-002098 bridge(NODE-002100) start transaction failed. Error Code=Server Internal Error > 09:39:37.558 2 PBXLEG-002098 bridge(NODE-002100) breaking Надо лог по PBXLEG-002100 отфильтровать, с ним что-то нехорошее произошло. А ещё лучше - по F71EC2B42AB82E598A0EB534BF1B42DC30D2A05C с галочкой Keyed. -- Best regards, Dmitry Akindinov