Support for Conference Management Rest API #5

Activity

1. deruelle

   added

   2. Enhancement

   on Sep 26, 2014
2. deruelle

   added this to the 7.2.1 milestone on Sep 26, 2014
3. ivelin

   assigned

   gvagenas

   on Oct 2, 2014
4. ivelin

   added

   REST API

   on Oct 2, 2014
5. gvagenas

   added a commit that references this issue on Dec 23, 2014

   Merged in ammendonca/telscale-restcomm/TS.RESTCOMM-399 (pull request #5)

   ...

   a17dd1c
6. ivelin

   modified the milestones: 7.2.1, 7.3.0 on Jan 16, 2015
7. desipepova

   modified the milestones: 7.2.2This milestone has been deleted, 7.3.0 on Feb 8, 2015
8. gvagenas

   modified the milestones: 7.2.2This milestone has been deleted, 7.3.0 on May 27, 2015
9. 57 remaining items

   Load more

10. maria-farooq commented on May 31, 2016

    

    maria-farooq

    on May 31, 2016

    More actions

    Archive.zip
11. gvagenas commented on May 31, 2016

    

    gvagenas

    on May 31, 2016

    Contributor

    More actions

    @maria-farooq the pcap trace doesn't contain any sip traffic. Can you check again?
12. maria-farooq commented on May 31, 2016

    

    maria-farooq

    on May 31, 2016

    More actions

    hi @gvagenas attaching fresh logs,they have confirmed sip traffic.

    Archive.zip

    in mediaserver log

    2016-05-31 15:02:57,074 DEBUG [RtpMember] (service-scheduler-2) rtt=3755021041 - 0 - 0 = 3755021041 => 65536ms
    2016-05-31 15:02:59,792 DEBUG [MgcpProvider] (service-scheduler-2) Receive  message 81 bytes length
    2016-05-31 15:02:59,792 DEBUG [MgcpProvider] (service-scheduler-2) Parsing message: MDCX 147483691 mobicents/bridge/1@172.20.10.2:2427 MGCP 1.0
    C:1
    I:5de
    M:sendonly
    
    2016-05-31 15:02:59,792 DEBUG [MgcpProvider] (service-scheduler-2) Dispatching message
    2016-05-31 15:02:59,792 INFO  [MgcpTransaction] (service-scheduler-2) tx=147483691 Started, message= MDCX mobicents/bridge/1@172.20.10.2:2427, call agent = /172.20.10.2:2727
    2016-05-31 15:02:59,919 WARN  [JitterBuffer] (service-scheduler-3) Buffer overflow!
    2016-05-31 15:02:59,939 WARN  [JitterBuffer] (service-scheduler-3) Buffer overflow!
    2016-05-31 15:02:59,958 WARN  [JitterBuffer] (service-scheduler-2) Buffer overflow!
    2016-05-31 15:02:59,979 WARN  [JitterBuffer] (service-scheduler-1) Buffer overflow!
    
    and here onward Buffer overflow continuous
    
    
13. maria-farooq commented on May 31, 2016

    

    maria-farooq

    on May 31, 2016

    More actions

    I tried feeding extra memory as well to mediaserver as guided by @hrosa
    https://github.com/RestComm/mediaserver/blob/master/bootstrap/src/main/config/run.sh#L137
14. gvagenas commented on May 31, 2016

    

    gvagenas

    on May 31, 2016

    Last edited by gvagenas

    Contributor

    More actions

    @maria-farooq
    I can see RMS receives the MUTE request at

    2016-05-31 15:02:59,792 DEBUG [MgcpProvider] (service-scheduler-2) Parsing message: MDCX 147483691 mobicents/bridge/1@172.20.10.2:2427 MGCP 1.0
    C:1
    I:5de
    M:sendonly
    

    and then again reports the same request but no response

    2016-05-31 15:03:03,794 DEBUG [MgcpProvider] (service-scheduler-6) Parsing message: MDCX 147483691 mobicents/bridge/1@172.20.10.2:2427 MGCP 1.0
    C:1
    I:5de
    M:sendonly
    

    and again the same request but no response

    2016-05-31 15:03:11,794 DEBUG [MgcpProvider] (service-scheduler-4) Parsing message: MDCX 147483691 mobicents/bridge/1@172.20.10.2:2427 MGCP 1.0
    C:1
    I:5de
    M:sendonly
    

    After this, there is nothing related to this Request and of course Restcomm will timeout this MGCP request.

    There are a lot Buffer Overflow messages that I know are coming from Linphone.

    In the past, I had some issues with Linphone and I would like you to make the same test with Jitsi.
    Use Jitsi to make a call to a conference room and try to mute Jitsi to check if we have the same MGCP timeout.

    If with Jitsi same exception happens we need to check with @hrosa

    Thanks
    George
15. maria-farooq commented on May 31, 2016

    

    maria-farooq

    on May 31, 2016

    More actions

    thanks @gvagenas will test with jitsi and update here, meanwhile
16. maria-farooq commented on May 31, 2016

    

    maria-farooq

    on May 31, 2016

    Last edited by maria-farooq

    More actions

    @gvagenas @hrosa problems is faced even with jitsi
17. hrosa commented on May 31, 2016

    

    hrosa

    on May 31, 2016

    Contributor

    More actions

    @maria-farooq please open issue on Media Server repo and link it to this one. Thank you.
18. maria-farooq commented on May 31, 2016

    

    maria-farooq

    on May 31, 2016

    More actions

    @hrosa RestComm/media-core#165 created
    Thanks
19. gvagenas

    added 2 commits that reference this issue on Jun 30, 2016

    Minor fix for the ConferenceDetailRecord Json response.

    ...

    d271622

    Fixes for the testsuite

    ...

    015b594
20. gvagenas

    added this to the 7.8.0 milestone on Jun 30, 2016
21. gvagenas commented on Jun 30, 2016

    

    gvagenas

    on Jun 30, 2016

    Contributor

    More actions

    PR reviewed and merged . Great job @maria-farooq
22. gvagenas

    closed this as completedon Jun 30, 2016
23. maria-farooq

    added a commit that references this issue on Jul 4, 2016

    Merge branch 'master' into issue-1154

    ...

    be860b6