Summary:ASTERISK-18940: Channel SIP do not get answer
Reporter:Vitaliy Vitaliy (vetal)Labels:
Date Opened:2011-11-30 09:47:25.000-0600Date Closed:2011-12-13 09:20:39.000-0600
Versions: Frequency of
is the original version of this clone:ASTERISK-18991 CLONE - Channel SIP do not get answer
Environment:Centos 5.4 and FreeBSD 8.1Attachments:( 0) bad.dump
( 1) myDebugLog
( 2) wrongoptionsmethod.patch
Description:I hear 1 word, and then silense, tcpdump look to be OK.

This do not happend on Asterisk 1.6


   -- Executing [74957410001@test:1] Dial("SIP/00002-00000000", "SIP/ez/01#7495
7410001") in new stack
 == Using SIP RTP CoS mark 5
   -- Called SIP/ez/01#74957410001
   -- SIP/ez-00000001 is ringing
   -- SIP/ez-00000001 is making progress passing it to SIP/00002-00000000
[Nov 30 22:43:50] NOTICE[27741]: chan_sip.c:20192 handle_response_peerpoke: Peer
'ez' is now Lagged. (1ms / 0ms)
   -- No one is available to answer at this time (1:0/0/0)
   -- Auto fallthrough, channel 'SIP/00002-00000000' status is 'NOANSWER'
Comments:By: Vitaliy Vitaliy (vetal) 2011-11-30 09:51:57.865-0600

Dump of call

By: Paul Belanger (pabelanger) 2011-12-01 11:14:38.903-0600

This issue lacks information, see below

We require a complete debug log to help triage the issue. This document will provide instructions on how to collect debugging logs from an Asterisk machine for the purpose of helping bug marshals troubleshoot an issue: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

By: Leif Madsen (lmadsen) 2011-12-01 14:08:37.971-0600

Based on the information provided I see nothing wrong.

By: Vitaliy Vitaliy (vetal) 2011-12-02 00:14:58.217-0600

I attach full Debug of call

By: Vitaliy Vitaliy (vetal) 2011-12-05 07:06:47.605-0600

I attach full debug file

By: Paul Belanger (pabelanger) 2011-12-05 11:17:14.869-0600

This is a configuration issue, not a bug.

By: Vitaliy Vitaliy (vetal) 2011-12-06 03:48:17.484-0600

Please can you help with config for this trouble, and why it is not happen in Astersik version 1.6?

Also, when I make in config for peer - qualify=yes
I get for example:
[Nov 30 22:43:50] NOTICE[27741]: chan_sip.c:20192 handle_response_peerpoke: Peer
'ez' is now Lagged. (56929ms / 0ms)

This ms always different.
Thank you for help

By: Stefan Schmidt (schmidts) 2011-12-13 07:19:08.674-0600

i dont think its a config issue. he has shown me his sip config and qualify is turned off for this peer so it should never happend that an incoming options packet cause this message to appear.

i have taken a look at the code and i see that in handle_response OPTION is the only thing which is matched against p->method and not to the sipmethod field which is used from the Cseq header. IMHO this could lead to this wrong values.

I think this problems comes from an incoming packet which is handled as Option even if its not the right method to use.

please try the attached patch if this helps.

By: Vitaliy Vitaliy (vetal) 2011-12-13 15:20:29.409-0600

Thank you! It works for me. No more problems.