[asterisk-bugs] [JIRA] (ASTERISK-20709) Asterisk sends wrong Caller IDs in first SIP NOTIFY message
Joshua Colp (JIRA)
noreply at issues.asterisk.org
Tue Dec 19 05:21:07 CST 2017
[ https://issues.asterisk.org/jira/browse/ASTERISK-20709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joshua Colp updated ASTERISK-20709:
-----------------------------------
Affects Version/s: 13.18.4
> Asterisk sends wrong Caller IDs in first SIP NOTIFY message
> -----------------------------------------------------------
>
> Key: ASTERISK-20709
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-20709
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_sip/Subscriptions
> Affects Versions: 11.0.1, 13.18.4
> Environment: Asterisk 11.0.1 (11.1.0-rc1 also affected), Polycom 650 Firmware 4.0.3 rev F
> Reporter: Stefan Reuter
> Attachments: ASTERISK-20709.patch, wrong_caller_id.pcap
>
>
> The fix for ASTERISK-16735 does not work with Polycom phones. Asterisk sends the wrong Caller IDs with the first SIP NOTIFY message and follows up with a seconds message with the correct Caller IDs. Polycom phones do not update the display and continue to show the wrong Caller IDs from the first message.
> First SIP NOTIFY message conatins wrong remote and local identity (both extension/address of called phone):
> {code}
> <remote>
> <identity display="1202">sip:1202 at reucon.com</identity>
> <target uri="sip:1202 at reucon.com"/>
> </remote>
> <local>
> <identity display="1202">sip:1202 at reucon.com</identity>
> <target uri="sip:1202 at reucon.com"/>
> </local>
> {code}
> Second SIP NOTIFY message contains correct remote and local identity:
> {code}
> <remote>
> <identity display="Stefan Reuter">sip:1201 at reucon.com</identity>
> <target uri="sip:1201 at reucon.com"/>
> </remote>
> <local>
> <identity display="phone-02">sip:1202 at reucon.com</identity>
> <target uri="sip:1202 at reucon.com"/>
> </local>
> {code}
> See attached pcap file.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list