[asterisk-bugs] [JIRA] (ASTERISK-20282) Call pickup incompatibility with Cisco 1760V + RPID

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-20282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan updated ASTERISK-20282:
-----------------------------------

    Assignee: Jeremy Kister  (was: Matt Jordan)
      Status: Waiting for Feedback  (was: Triage)

There's a bit of interesting things that go in call pickup that makes this scenario a bit tricky.  Do you mind attaching a DEBUG 5 (or greater) log with 'sip set debug on' illustrating the problem?  I'd like to narrow down the portion in Asterisk that is causing the UPDATE request to be sent to the Cisco phones to figure out why Asterisk is sending it, and whether or not its expected behavior.  Thanks!
                
> Call pickup incompatibility with Cisco 1760V + RPID
> ---------------------------------------------------
>
>                 Key: ASTERISK-20282
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20282
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General, Channels/chan_sip/Interoperability
>    Affects Versions: 1.8.15.0
>            Reporter: Jeremy Kister
>            Assignee: Jeremy Kister
>         Attachments: cisco-group-with-rpid.txt, extensions.conf, features.conf, group-without-rpid.txt, group-with-rpid.txt, single-with-rpid.txt, sip.conf
>
>
> I have a Cisco 1760V with FXO ports hooked to POTS lines talking SIP to 
> asterisk 1.8.15.0.
> imagining in extensions.conf:
> exten => 1,1,Dial(SIP/121)
> exten => 2,1,Dial(SIP/121&SIP/122)
> When a caller dials extension 2 /and/ I have
>   trustrpid=yes
>   generaterpid=yes
>   sendrpid=yes
> in sip.conf and I use the pickup exten, the caller is disconnected.
> if i set the rpid generate/send = no for the cisco peer, the user is 
> connected.
> calls to exten 1 work regardless of rpid settings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira