[Home]

Summary:ASTERISK-17529: SIPAddHeader in dialplan not in SIP INVITE
Reporter:Jonas Kellens (jonaskellens)Labels:
Date Opened:2011-03-09 08:37:49.000-0600Date Closed:2011-07-26 14:25:06
Priority:MinorRegression?No
Status:Closed/CompleteComponents:PBX/General
Versions:1.6.2.16 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:The dialplan :

exten => 5006,1,NoOp()
exten => 5006,n,SIPAddHeader(Privacy: id)
exten => 5006,n,Set(CALLERID(all)="959600" <959600>)
exten => 5006,n,Dial(SIP/959600/5006)

The CLI shows :

[Mar  9 15:23:18]     -- Executing [5006@from-VOIP:1] NoOp("SIP/voip2-00000831", "") in new stack
[Mar  9 15:23:18]     -- Executing [5006@from-VOIP:2] SIPAddHeader("SIP/voip2-00000831", "Privacy: id") in new stack
[Mar  9 15:23:18]     -- Executing [5006@from-VOIP:3] Set("SIP/voip2-00000831", "CALLERID(all)="959600" <959600>") in new stack
[Mar  9 15:23:18]     -- Executing [5006@from-VOIP:4] Dial("SIP/voip2-00000831", "SIP/959600/5006") in new stack


The SIP INVITE :

INVITE sip:5006@sip.domain.be SIP/2.0
Via: SIP/2.0/UDP 192.168.1.106:5063;branch=z9hG4bK-b39016f3
From: "VC" <sip:voip2@sip.domain.be>;tag=689d032893d3782bo2
To: <sip:5006@sip.domain.be>
Remote-Party-ID: "VC" <sip:voip2@sip.domain.be>;screen=yes;party=calling
Call-ID: 185558ac-c5698077@192.168.1.106
CSeq: 101 INVITE
Max-Forwards: 70
Contact: "VC" <sip:voip2@192.168.1.106:5063>
Expires: 240
User-Agent: Linksys/SPA941-5.1.8
Content-Length: 401
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: replaces
Content-Type: application/sdp
Comments:By: Russell Bryant (russell) 2011-07-26 14:24:44.916-0500

Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.4 and 1.6.x branches has ended. For continued maintenance support please move to the 1.8 branch which is a long term support (LTS) branch. For more information about branch support, please see https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions

If this is still an issue, please open a new issue so it can be re-triaged appropriately. Thanks!