[asterisk-bugs] [JIRA] (ASTERISK-21071) Open channel for incoming call after RING; +CLIP responses from rfcomm; faster reporting of incoming calls
Heiko Bihr (JIRA)
noreply at issues.asterisk.org
Wed Feb 13 12:10:58 CST 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-21071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202888#comment-202888 ]
Heiko Bihr edited comment on ASTERISK-21071 at 2/13/13 12:09 PM:
-----------------------------------------------------------------
[^recognize_clip_after_ring.patch] is a patch to chan_mobile.c, that handles RING just like +CIEV: 4,1
With this patch, a channel is opened directly after the first +CLIP response in the above sample. This reduces the waiting time, before an incoming call is reported to asterisk core.
was (Author: heiko.bihr):
make response sequence RING; +CLIP open an asterisk channel
> 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: 3,1
> +CIEV: 4,1
> RING
> +CLIP: "+49xxxxxxxx",145
> {quote}
> chan_mobile detects an incoming call, if it receives +CIEV. 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
More information about the asterisk-bugs
mailing list