Summary:ASTERISK-08895: Wrong FROM header
Reporter:Martynas Spokas (chivilis)Labels:
Date Opened:2007-02-27 07:09:05.000-0600Date Closed:2011-06-07 14:02:41
Versions:Frequency of
Environment:Attachments:( 0) verbosedebug.txt
Description:I have to phones (552 and 573). When I make call from 573 to 552 the wrong FROM header is sent.

Here is the SIP debug: (the wrong place is <sip:552@...> but it should be <sip:573@...>

<-- SIP read from
SIP/2.0 200 OK
Via: SIP/2.0/UDP;branch=z9hG4bK1ac77444;rport
From: "573" <sip:552@>;tag=as0becf55d
To: <sip:552@>;tag=1348426098
Call-ID: 3922dca72a66adc0437a0cea5eb92e03@
CSeq: 102 CANCEL
Contact: <sip:552@>
Content-Length: 0

Comments:By: Serge Vecher (serge-v) 2007-02-27 11:09:27.000-0600

We need to see a call from start to end, not just a snippet. Please test with 1.2.15 and produce the log as per following if still an issue:
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:
set debug 4
set verbose 4
sip debug
5) Reproduce the problem
6) Trim startup information and attach verbosedebug.txt to the issue.

By: Martynas Spokas (chivilis) 2007-02-27 12:23:12.000-0600

The file uploaded ;-)

By: Martynas Spokas (chivilis) 2007-02-27 12:36:35.000-0600

The only thing I have changed is "573" to "Martyns" - but same <sip:552@..>

By: Serge Vecher (serge-v) 2007-02-27 12:48:36.000-0600

is this from 1.2.15, like I've asked?

By: Martynas Spokas (chivilis) 2007-02-27 12:52:04.000-0600

No, I have tested with the same 1.2.14, because I am using 1.2.14-BRIstuffed-0.3.0-PRE-1x pakage. I know how to upgrade to 1.2.15, can you post the instructions or smth.?

By: Serge Vecher (serge-v) 2007-02-27 13:05:25.000-0600

Download Asterisk 1.2.15 directly from http://www.asterisk.org . We do not support BRIstuffed-patched versions of Asterisk via this bug-tracker. However, if you are able to reproduce this problem with a clean Asterisk installation, we will be able to look into resolving this.

By: Martynas Spokas (chivilis) 2007-02-27 14:04:55.000-0600

I have tried with clean asterisk 1.2.15, there is no such problem. Maybe someone could say if was such fix from 1.2.14, because I could not find something useful in ChangeLOG?

By: Serge Vecher (serge-v) 2007-02-27 14:56:18.000-0600

I've checked the changelog too and I'm not clear which specific fix did it as well. This may be a problem caused by a BRIstuffed patches -- this is why we don't support patches versions of Asterisk via this bugtracker -- we just don't know what other people change in the code. Please use Asterisk 1.2.15 or contact the author of BRIstuff patches. Case closed.