[asterisk-bugs] [JIRA] (ASTERISK-27744) Incoming queued calls are occasionally forwarded with wrong From: header

Janko Zgaga (JIRA) noreply at issues.asterisk.org
Thu Mar 22 05:01:42 CDT 2018


    [ https://issues.asterisk.org/jira/browse/ASTERISK-27744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242770#comment-242770 ] 

Janko Zgaga commented on ASTERISK-27744:
----------------------------------------

Thanks for your reply. Guess I'll have to pull Asterisk from the testing branch and check that one, as the version I'm currently running is the latest in Debian stable (stretch). I do dislike going to testing versions though for this very reason (dealing with bugs).

> Incoming queued calls are occasionally  forwarded with wrong From: header
> -------------------------------------------------------------------------
>
>                 Key: ASTERISK-27744
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27744
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 13.14.1
>         Environment: Linux 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86_64
>            Reporter: Janko Zgaga
>            Assignee: Janko Zgaga
>
> With incoming calls forwarded to a static queue, I occasionally see wrong From: header on the call, once forwarded to the local extension (From: gets the same sip id as To:) You can find a log of one such call at http://www.itd.si/Buldozer/astlog.zip
> There's more calls in there, but interesting one is the first one - Call-ID: BW0904004831603182087347519 at 172.18.1.14 (log continues until it's end). You'll see that a call, coming in from
> From: <sip:027031065 at 192.168.213.126;user=phone>;tag=2026492818-1521187440483-
>  gets forwarded to
> To: <sip:01238471 at 192.168.1.108:5080;ob>
> as
> From: <sip:01238471 at 192.168.1.1>;tag=as7dc0234c
>  ... numbers are (consistently) obfuscated
> I have started seeing such calls from 2017-10-24, but can't really say which version of Asterisk it was back then. I update to latest debian stable releases on monthly basis so it should be a debian release from around that time. It seems to happen some 11% of the time. Do let me know if more info is needed.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list