Re: chan_lcr bad quality
Ralf Schlatterbeck <[email protected]>
| Newsgroups | gmane.linux.isdn.i4l.user |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Oct 21, 2013 at 08:35:17PM +0200, Thomas Witt wrote: > > The transmission is barely intelligible, I suspect massive package loss. > > > Why don't you figure out to get some debug informations for the mISDN > > people and post it on pastebin for the developers to have a look on it > > to figure out if it's a chan_lcr coding issue or just asterisk tweaks to > > accomplish?! > > Same. My question was HOW can I get meaningful debug info? All I got now is: > > [call=1002 ast=lcr/3 line=1696] Message 15 from LCR unhandled. > (once, in asterisk cli) > > ERROR (in message_epoint() line 2954) Pdss1(ext-0-out) isdn port with > (caller id *******) received a wrong message: 3 > (three times in LCR cli) > > mISDN_send: error -12 > (too numerous to count, in dmesg) This message is generated by the mISDN Kernel driver if the userspace doesn't serve the connection in time. This happens if the userspace program is too slow or -- as I had numerous times with the current lcr driver -- there is a deadlock in chan_lcr. Since you *are* receiving audio I guess you don't see a deadlock but some other condition that prevents LCR / Asterisk from servicing the pipe to the kernel. Ralf -- Ralf Schlatterbeck email: [email protected]