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

[Alexander Anikin (JIRA)]

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

Alexander Anikin updated ASTERISK-24065:
----------------------------------------

    Assignee: Alexander Vysokovskih  (was: Alexander Anikin)
      Status: Waiting for Feedback  (was: Triage)

Hi Alexander,
Looks like to CUCM reestablish MasterSlaveDetermination procedure after back call from hold. I'm not sure what all h.323 endpoints do so.
Could you attach capture file with signalling data between asterisk and cucm in this case?

> 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: 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)