openmeetings-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sqli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENMEETINGS-544) some bug with SIP
Date Wed, 20 Mar 2013 16:11:18 GMT

    [ https://issues.apache.org/jira/browse/OPENMEETINGS-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607778#comment-13607778
] 

Sqli commented on OPENMEETINGS-544:
-----------------------------------

I use revision 1449605.
I'm installing the last build to verify again.
                
> some bug with SIP
> -----------------
>
>                 Key: OPENMEETINGS-544
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-544
>             Project: Openmeetings
>          Issue Type: Bug
>          Components: VoIP/SIP
>    Affects Versions: 2.1 Apache Release
>         Environment: OpenMeetings REV 1449605
>            Reporter: Sqli
>            Assignee: Timur Tleukenov
>
>  Hi,
> I have some problems with red5sip's configuration.
> The connection with asterisk works.
> I use "alaw" codec, and I can join conference with PhoneIP.
> 1 - Sip Dialer dialer doesn't work.
> 2 - Sip transport sometimes crashes and reconnects immediately.
> I have this error:
> " [WARN] o.r.s.n.r.BaseRTMPClientHandler: Stream data was null for client id: 3"
> " [ERROR] o.r.s.a.RTPStreamForMultiplex: Stream %d buffer overflow. Buffer is cleared"
> 3 - When I start red5sip I have this warning message.
> " [WARN ] n.s.e.c.ConfigurationFactory: No configuration found. Configuring ehcache from
ehcache-failsafe.xml found in the classpath: jar:file:/opt/red5sip/lib/ehcache-2.2.0.jar!/ehcache-failsafe.xml"
> 4 - During a conference, the sound is correct but not very 'confortable':
> example: crackling, voice lag (1/2secondes delay)
> Do you have an "optimum" configuration to link openmeetings and asterisk?
> I would like to test with another codec, what codec can Red5sip support? 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message