Summary:ASTERISK-18153: Wrong Caller ID Sent in Invite From Header From Realtime SIP User
Reporter:Max A Glucksmann (maxgo)Labels:
Date Opened:2011-07-19 10:57:56Date Closed:2011-07-19 11:29:20
Status:Closed/CompleteComponents:Channels/chan_sip/DatabaseSupport Channels/chan_sip/General
Versions:1.4.42 Frequency of
Environment:Realtime SIP registered user places the call to another registered user (can be either flat or realtime too). When call is placed from the flat user, the error is not present.Attachments:
Description:A call is placed from a realtime user, with the phone being registered. The call goes through Asterisk, which receives the INVITE message with the correct From header. When Asterisk sends the new INVITE to the destination, the "From" header contains the same user number as the "To" header. For instance, a call from 1011001 to 1011002:

Caller at (extension 1011001)
Server at
Destination at: (extension 1011002)

<--- SIP read from --->
INVITE sip:1011002@ SIP/2.0
Via: SIP/2.0/UDP;branch=z9hG4bK1837327784109568286;rport
From: Max <sip:1011001@>;tag=114835825
To: "1011002" <sip:1011002@>

After going through the dial-plan, a message is sent to the destination, but show the destination number in the From header, resulting in the wrong caller id number being shown:
   -- Executing Dial("SIP/1011001-092ac368", "SIP/1011002|36")
Audio is at port 16814
Adding codec 0x100 (g729) to SDP
Adding codec 0x4 (ulaw) to SDP
Reliably Transmitting (NAT) to
INVITE sip:1011002@;rinstance=c15f50c908eb3ac4 SIP/2.0
Via: SIP/2.0/UDP;branch=z9hG4bK0f471560;rport
From: "Max" <sip:1011002@>;tag=as394ddc13
To: <sip:1011002@;rinstance=c15f50c908eb3ac4>

See that now, From says 1011002 when it should say 1011001. The header is not affected by setting the CALLERID(number) variable right before the Dial command, although it does affect the cdr entry. In the realtime user callerid fiel, it is correctly set as "Max" <1011001>.
Comments:By: Max A Glucksmann (maxgo) 2011-07-19 11:29:20.964-0500

Sorry, had set incorrectly the "fromuser" field (thought it meant something else)...