[asterisk-bugs] [JIRA] (ASTERISK-26414) app_externalivr: ExternalIVR attended transfer - no audio

[balamurugan (JIRA)]

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

balamurugan commented on ASTERISK-26414:
----------------------------------------

I can analyse and see if we can fix this issue . can you provide the pcap captured with sip and rtp and share the pcap 
Also if could provide the client ip and server ip i have to look for in the pcap that will better .

> app_externalivr: ExternalIVR attended transfer - no audio
> ---------------------------------------------------------
>
>                 Key: ASTERISK-26414
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26414
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_externalivr
>    Affects Versions: 11.23.1, 13.11.2
>         Environment: Debian 7 64bit
>            Reporter: Chris Maciejewski
>            Assignee: Unassigned
>         Attachments: asterisk.log
>
>
> Hi,
> When attended transfer to ExternalIVR is completed *after* ExternalIVR app starts no audio is sent to SIP client.
> To reproduce the bug:
> 1. Download example config which can be found here:
> https://github.com/level7systems/asterisk-cfg/tree/ExternalIVR-xfer
> 2. Register SIP client for ext 201 and ext 202.
> 3. Perform call scenario as below:
> a) 201 calls 202
> b) 202 performs attended transfer to ext 125 (ExternalIVR). 202 waits 10 seconds before completing the transfer
> c) when transfer is completed there is no audio sent to 201
> Note: if the same scenario is performed, however in step b) 202 waits only 3 seconds before completing the transfer audio is sent to 201 correctly. So it seems the issue doesn't occur if attended transfer is completed *before* ExternalIVR app starts and happens only if transfer completes when ExternalIVR app already started.
> Note 2: the same problem affects ver. 11.22.0 as well.
> Regards,
> Chris



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