[Home]

Summary:ASTERISK-19450: there always an extra byte added to contact header while send "ACK" request.
Reporter:zhiqiang wang (rainlake)Labels:
Date Opened:2012-02-29 13:41:34.000-0600Date Closed:2012-06-05 15:46:14
Priority:MinorRegression?
Status:Closed/CompleteComponents:Applications/General
Versions:SVN Frequency of
Occurrence
Related
Issues:
Environment:openwrt on dockstar.Attachments:( 0) 800_ack_contact_ugly_fix.patch
( 1) issueA19450_one_va_end_too_many.patch
Description:there always an extra byte added to contact header while send "ACK" request. like
ACK sip:x@192.168.x.x:10000;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 192.168.x.x:5060;branch=xxxxxxxxxxx;rport
Max-Forwards: 70
From: "800x" <sip:800x@192.168.x.x>;tag=xxxxxxx
To: <sip:800x@192.168.x.x:10000;transport=UDP>;tag=xxxxxxxxxxxxxxxxxxxxx
Contact: <sip:800x@192.168.x.x:5060>B
Call-ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx@192.168.x.x:5060
CSeq: 102 ACK
User-Agent: x.x.x
Content-Length: 0

have already applied patch for arm
#if defined(__sparc__) || defined(__arm__)

looks like still a problem with __ast_string_field_ptr_build_va


Comments:By: zhiqiang wang (rainlake) 2012-02-29 13:44:30.219-0600

this patch may fixed it.
just do not know why. I'm not an asterisk expert.
By: Walter Doekes (wdoekes) 2012-02-29 14:15:55.940-0600

Hi,
you say you're using SVN, but I can't tell which version you're using.

So it's the 'B' at the end of the Contact that's the problem? Your patch is not the right fix, but if it works for you, the problem is probably close.

Try this one.
By: zhiqiang wang (rainlake) 2012-02-29 20:29:08.527-0600

I am using 1.8.8.0. it's not important. I really can not remember when it come out. I have not use asterisk for a long time since I have this problem.(may be 1.8.7.x)

it should be alignment problems. maybe somewhere over write this location. I do not know.

my patch do solve this problem. but this bug may still be there.
By: Jonathan Rose (jrose) 2012-06-05 15:45:59.741-0500

va_args stuff reported in this issue was cleaned up in another patch (r362354 specifically). Please open a fresh issue report against 1.8.13.0 or later if you can reproduce this problem in current branches.