[asterisk-bugs] [JIRA] (ASTERISK-24065) ooh323 irregularities in the sequence of TCS/MSD/OLC after TCS=0

[Alexander Vysokovskih (JIRA)]

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

Alexander Vysokovskih edited comment on ASTERISK-24065 at 7/23/14 12:17 AM:
----------------------------------------------------------------------------

Alexander,

CUCM use EmptyCapabilitySet as "method" of putting on hold as well as returning from hold and as well as transfer the call.
According to ITUs TCS/MSD negotiations required before OLC negotiation. Currently in this case chan_ooh323 send OLC before MSD negotiation. 



was (Author: laowai):
Alexander,

CUCM use EmptyCapabilitySet as "method" of putting on hold as well as returning from hold and as well as transfer the call.
According to ITUs TCS/MSD negotiations required before OLC negotiation. Currently chan_ooh323 send OLC before MSD negotiation. 


> ooh323 irregularities in the sequence of TCS/MSD/OLC after TCS=0
> ----------------------------------------------------------------
>
>                 Key: ASTERISK-24065
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24065
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Addons/chan_ooh323
>    Affects Versions: 11.11.0
>         Environment: Putting call on hold or transfer the call to asterisk from CUCM (SlowStart,Tunneling OFF).
>            Reporter: Alexander Vysokovskih
>            Assignee: Alexander Vysokovskih
>         Attachments: call.bad.txt, call.good.txt, ooh245.hold.patch
>
>
> We have a irregularities in the sequence of TCS/MSD/OLC from asterisk after receiving EmptyCapabilitySet request (TCS=0). In this case CUCM (SlowStart, Tunneling OFF) does not work correctly after putting call on hold of transfer the call to asterisk.



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