From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Mon, 5 Dec 2005 16:25:07 +0300 From: Maxim Bodyansky To: Sisyphus Message-ID: <20051205132507.GA8339@ember.istranet.ru> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="OgqxwSJOaUobr8KG" Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4.2.1i X-Auth-User: maximbo, whoson: (null) Subject: [sisyphus] asterisk =?koi8-r?b?zsUg0sXHydPU0snS1cXUIMvMycXO1M/X?= sip X-BeenThere: sisyphus@lists.altlinux.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ALT Linux Sisyphus discussion list List-Id: ALT Linux Sisyphus discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 13:26:09 -0000 Archived-At: List-Archive: List-Post: --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit День добрый. Обновление asterisk'а до версии 1.2-alt10 вылилось в интересные последствия. Отныне любая попытка регистрации sip-клиента приводит к блокировке chan_sip. Диалог устройств в аттаче. Действующие лица: 192.168.0.2 -- телефон с именем 123 192.168.0.1 -- asterisk с dns-именем faust.ru Может сталкивался кто с такими ловушками? -- WBR, Maxim Bodyansky --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="sip.log" <-- SIP read from 192.168.0.2:5060: REGISTER sip:faust.ru SIP/2.0 From: To: Max-Forwards: 70 Call-ID: 408679214@192.168.0.2 CSeq: 401 REGISTER Contact: ;+sip.p2t="true";expires=1000 User-Agent: Minisip Via: SIP/2.0/UDP 192.168.0.2:5060;branch=z9hG4bK1884156211 Content-Length: 0 --- (10 headers 0 lines)--- Using latest REGISTER request as basis request Sending to 192.168.0.2 : 5060 (non-NAT) Transmitting (no NAT) to 192.168.0.2:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.0.2:5060;branch=z9hG4bK1884156211;received=192.168.0.2 From: To: Call-ID: 408679214@192.168.0.2 CSeq: 401 REGISTER User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Max-Forwards: 70 Contact: Content-Length: 0 --- Transmitting (no NAT) to 192.168.0.2:5060: SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 192.168.0.2:5060;branch=z9hG4bK1884156211;received=192.168.0.2 From: To: ;tag=as2d606eab Call-ID: 408679214@192.168.0.2 CSeq: 401 REGISTER User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Max-Forwards: 70 Contact: WWW-Authenticate: Digest realm="asterisk", nonce="2a6ec3b9" Content-Length: 0 --- Scheduling destruction of call '408679214@192.168.0.2' in 15000 ms <-- SIP read from 192.168.0.2:5060: REGISTER sip:faust.ru SIP/2.0 From: To: Max-Forwards: 70 Call-ID: 408679214@192.168.0.2 CSeq: 402 REGISTER Contact: ;expires=1000 User-Agent: Minisip Authorization: Digest algorithm="MD5", username="123", realm="asterisk", nonce="2a6ed3b9", uri="192.168.0.2", response="b19e75ed93739d6f48692ec979d559de" Via: SIP/2.0/UDP 192.168.0.2:5060;branch=z9hG4bK1286335101 Content-Length: 0 --- (11 headers 0 lines)--- Using latest REGISTER request as basis request Sending to 192.168.0.2 : 5060 (non-NAT) Transmitting (no NAT) to 192.168.0.2:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.0.2:5060;branch=z9hG4bK1286335101;received=192.168.0.2 From: To: Call-ID: 408679214@192.168.0.2 CSeq: 402 REGISTER User-Agent: Asterisk PBX Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY Max-Forwards: 70 Contact: Content-Length: 0 --- --OgqxwSJOaUobr8KG--