[asterisk-bugs] [JIRA] (ASTERISK-21071) Open channel for incoming call after RING; +CLIP responses from rfcomm; faster reporting of incoming calls

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-21071:
----------------------------------------

Since this represents an improvement and a behavioral change, you should:
# Write the patch against trunk. Improvements are not committed in release branches.
# See if other users of chan_mobile can confirm that your patch does not adversely affect their systems. That will make it easier for the patch to be accepted.

Thanks!
                
> Open channel for incoming call after RING; +CLIP responses from rfcomm; faster reporting of incoming calls
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21071
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21071
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Addons/chan_mobile
>    Affects Versions: 10.12.0
>         Environment: Fedora 17 i386
>            Reporter: Heiko Bihr
>            Severity: Minor
>         Attachments: recognize_clip_after_ring.patch
>
>
> My old Nokia 6230i emits the following response sequence for an incoming call
> {quote}
> RING
> +CLIP: "+49xxxxxxxx",145
> +CIEV: 4,1
> RING
> +CLIP: "+49xxxxxxxx",145
> {quote}
> chan_mobile detects an incoming call, if it receives +CIEV: 4,1. It then waits for a +CLIP response to get the caller id and after that opens a channel.
> On my mobile, there are 4 seconds of waiting time between the two RING answers in the above sequence. These 4 seconds must pass for every incoming call, before it is reported to asterisk.

--
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