[asterisk-bugs] [JIRA] (ASTERISK-21672) Early media not properly handled on outbound TCP trunk

Michael L. Young (JIRA) noreply at issues.asterisk.org
Tue Apr 23 12:29:38 CDT 2013


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

Michael L. Young closed ASTERISK-21672.
---------------------------------------

    Resolution: Won't Fix
    
> Early media not properly handled on outbound TCP trunk
> ------------------------------------------------------
>
>                 Key: ASTERISK-21672
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21672
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/CallCompletionSupplementaryServices
>    Affects Versions: 10.12.1
>         Environment: FreePBX distro 3.211.63-7
> Centos 6.3, Asterisk 10.12.1
>            Reporter: dcitelecom
>         Attachments: Early media debug.log
>
>
> Voxbone DID (defined in inbound routes) is sent out to customer trunk ABCco (TCP) trunk. 
> They reply with 183 session progress (early media announcement) and Asterisk sends 180 ringing back to Voxbone.
> This is problematic where the DID is forwarded to a cell phone and the phone is off or the forwarding number was entered wrong. In both cases the user should hear an early media announcement that the user is not available or the number is not in service. Instead they hear a ring tone and don't know there is a problem. Log attached

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list