Summary:ASTERISK-09122: Call is hungup when SDP is not found in an ACK to 407
Reporter:Mike Thomas (mthomasslo)Labels:
Date Opened:2007-03-28 00:18:33Date Closed:2007-07-11 19:59:10
Versions:Frequency of
Environment:Attachments:( 0) error.txt
( 1) verbosedebug.txt
Description:Upgraded working system to 1.4.2, now all incoming calls from a MetaSwitch VP-3510 (ver4.2) error out with the following error:
Chan_Sip.C:4771 process_sdp: Insufficient information for SDP (m = '', c = ''). I ran a SIP debug log on a typical call (attached) and the c and m both have valid values:
m=audio 32936 RTP/AVP
c=IN IP4
Comments:By: Serge Vecher (serge-v) 2007-03-28 08:29:57

the log you've posted does not contain the error message you've mentioned. Please make sure to be posting complete transaction logs. You need to redo the log anyway, since debug info was not turned on. Please redo as per following:
1) Prepare test environment (reduce the amount of unrelated traffic on the server);
2) Make sure your logger.conf has the following line:
  console => notice,warning,error,debug
3) restart Asterisk with the following command:
  'asterisk -Tvvvvvdddddngc | tee /tmp/verbosedebug.txt'
4) Enable SIP transaction logging with the following CLI commands (1.4/trunk commands in parenthesis):
set debug 4 (core set debug 4)
set verbose 4 (core set verbose 4)
sip debug (sip set debug)
5) Reproduce the problem
6) Trim startup information and attach verbosedebug.txt to the issue.

Also, it would be helpful to do the same debug for, so we can see what's different. Thanks.

By: Serge Vecher (serge-v) 2007-03-29 08:33:23

interesting, I'm not sure the SDP is required when acking a 407.

By: Mike Thomas (mthomasslo) 2007-04-01 17:23:14

Changing the syntax 0f the insecure=very to insecure=port,invite in sip.conf for this connection solved the problem.

By: Olle Johansson (oej) 2007-04-02 05:35:06

I think the problem it that it actually issues a Content-Type: Application/SDP but there's no attachment. Since the Content-Length is declared to be zero, this should not be an issue.

By: Curt Moore (jcmoore) 2007-05-29 22:17:50

So, is this still an issue since changing the insecure setting seems to have resolved the problem?

By: Joshua C. Colp (jcolp) 2007-06-04 14:32:17

Underlying issue fixed in 1.4 as of revision 67068 and trunk as of revision 67069. Thanks!