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

dcitelecom (JIRA) noreply at issues.asterisk.org
Tue Apr 23 10:43:38 CDT 2013


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

dcitelecom updated ASTERISK-21672:
----------------------------------

    Description: 
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.

Log attached

  was:
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.

I have a log but don't know how to attach it.

    
> Early media not properly handled on inbound 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
>
> 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.
> 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