Re: [Chan-sccp-b-discussion] V2 I/O Error

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Attn, David

Diederik helped me get the trunk built on my openbsd sparc64 platform, got the module loaded up and encountered the same error as before, however with a little more debug information.

    -- SCCP: Accepted connection from 192.168.4.186
    -- SCCP: Using ip 192.168.4.7
[Feb 27 22:05:14] WARNING[14882]: sccp_socket.c:81 sccp_read_data: SCCP: read() returned 240, wanted 50570: Undefined error: 0
 [SCCP] Fire event 64
 eventtype: 64 listenerType: 1, -> result: 0 false
 eventtype: 64 listenerType: 8, -> result: 0 false
 eventtype: 64 listenerType: 112, -> result: 64 true
[Feb 27 22:05:14] ERROR[14882]: sccp_hint.c:150 sccp_hint_eventListener: Error posting deviceUnregistered event (null device)
 eventtype: 64 listenerType: 128, -> result: 0 false

Ive got a development server up to address the issue, Diederik and I can both get you on it, its full routed ip and you can have root access on it to do whatever you need

I think the 64bit sparc platform is messing up the counters on the socket reads, DdG said your the man for socket handling in this project and asked me to provide this information to you.

Cheers,
-Ryan

On Feb 26, 2010, at 6:44 AM, Diederik de Groot wrote:

> 
> Hi Ryan,
> 
> See comments below:
> 
> On Thu, 2010-02-25 at 12:05 -0700, Ryan wrote: 
>> OpenBSD has several versions available.. here is what I have installed. 
>> 
>> 
>> -bash-4.0$ libtool --version
>> ltmain.sh (GNU libtool) 1.5.26 (1.1220.2.493 2008/02/01 16:58:18)
>> 
>> 
>> autoconf-2.59  autoconf-2.60  autoconf-2.61
>> automake-1.9
>> autoheader-2.59  autoheader-2.60  autoheader-2.61
>> 
>> 
>> -bash-4.0$ gmake -v
>> GNU Make 3.81
>> 
>> 
>> The build system is entirely broken for OpenBSD 4.6 (latest), Ive had to do a ton of horrible hacks to get it this far. I am sure I have pretty much broken it by now. autoreconf blows up horribly, probably complaining about all the stuff I commented out.. I'll re-fetch trunk and try again.
> 
> That might be a good idea, I have made some changes in the latest version to cope with other autoconf problems. 
>> 
>> 
>> v2 builds just fine :-(
> It uses a very simple make system (Which you could easily adapt to you custom needs if necessary) 
>> 
>> 
>> I can provide a stock openbsd 4.6 sparc64 platform you guys can use to get your build system happy on OpenBSD, My PBX is a 500Mhz Netra X1 but I have a faster sparc server colocated that has enough free resources at the moment I can donate an openbsd logical domain temporarily until I need the resources back, which wont be for several months at least. 
> That would be fantastic. To fix these kinds of problems in our build system i would need access to a machine. Please message me directly with details for me to connect. We can chat via ICQ if you like: 18161207
> 
> I would love to get this fixed as soon as possible.
> 
> Regards,
> 
> Diederik 
>> 
>> 
>> Cheers,
>> -Ryan
>> 
>> 
>> 
>> 
>> 
>> On Feb 25, 2010, at 2:29 AM, Diederik de Groot wrote:
>> 
>>> Hi Ryan,
>>> 
>>> Would you be so kind and run "autoreconf -vfi" in the root of the chan_sccp-b folder and send me the output. This should install a new version of libtool for your platform. I should also get rid of the "AC_PROG_LIBTOOL" error. 
>>> 
>>> Can you also send me the following versions:
>>> autoconf -v
>>> automake -v
>>> autoheader -v
>>> libtool -v
>>> make -v 
>>> 
>>> Thanks
>>> 
>>> Diederik
>>> 
>>> On Thu, 2010-02-25 at 09:24 +0100, David Dederscheck wrote:
>>>> 
>>>> Ah, there we have another libtool error.
>>>> 
>>>> @dkgroot: I'd like to ask you to kindly take care of this again ;-)
>>>> 
>>>> 
>>>> Cheers,
>>>> -David.
>>>> 
>>>> On 25.02.2010, at 09:20, Ryan wrote:
>>>> 
>>>> > I'd love to get the trunk built on OpenBSD 4.6, I tweaked it a  
>>>> > little to get it to be happy with automake-1.9 but I cant get past  
>>>> > this error with the packaged libltdl-1.5.26
>>>> >
>>>> > -bash-4.0# ./bootstrap.sh
>>>> > Generating the configure script ...
>>>> >
>>>> > Running configure script...
>>>> >
>>>> > checking build system type... sparc64-unknown-openbsd4.6
>>>> > checking host system type... sparc64-unknown-openbsd4.6
>>>> > checking target system type... sparc64-unknown-openbsd4.6
>>>> > checking for uname... /usr/bin/uname
>>>> > checking for gcc... gcc
>>>> > checking for C compiler default output file name... a.out
>>>> > checking whether the C compiler works... yes
>>>> > checking whether we are cross compiling... no
>>>> > checking for suffix of executables...
>>>> > checking for suffix of object files... o
>>>> > checking whether we are using the GNU C compiler... yes
>>>> > checking whether gcc accepts -g... yes
>>>> > checking for gcc option to accept ISO C89... none needed
>>>> > checking for g++... g++
>>>> > checking whether we are using the GNU C++ compiler... yes
>>>> > checking whether g++ accepts -g... yes
>>>> > checking for a BSD-compatible install... /usr/bin/install -c
>>>> > ./configure: line 4207: AC_PROG_LIBTOOL: command not found
>>>> > checking for gawk... no
>>>> > checking for mawk... no
>>>> > checking for nawk... nawk
>>>> > checking whether ln -s works... yes
>>>> > checking whether make sets $(MAKE)... yes
>>>> > checking for inline... inline
>>>> > checking for ggrep... no
>>>> > checking for grep... /usr/bin/grep
>>>> > checking for svn... /usr/local/bin/svn
>>>> > checking for bash... /bin/sh
>>>> > checking for bash... /usr/local/bin/bash
>>>> > checking for gm4... no
>>>> > checking for m4... /usr/bin/m4
>>>> > checking for gsed... no
>>>> > checking for sed... /usr/bin/sed
>>>> > checking for cat... /bin/cat
>>>> > checking for tr... /usr/bin/tr
>>>> > checking for uname... /usr/bin/uname
>>>> > checking for whoami... /usr/bin/whoami
>>>> > checking for lt_dladvise_init in -lltdl... no
>>>> > configure: error: installed libltdl is too old
>>>> >
>>>> > Cheers,
>>>> > -R
>>>> >
>>>> > On Feb 25, 2010, at 1:01 AM, David Dederscheck wrote:
>>>> >
>>>> >> Hi ryan,
>>>> >>
>>>> >> AFAIK there are some shortcomings of the TCP socket interface in all
>>>> >> versions of chan_sccp other than our current trunk.
>>>> >> In fact, if a message can't be sent in one single write() request, it
>>>> >> would just give this warning and be left like that.
>>>> >>
>>>> >> I suggest you try the current trunk, where we finally fixed this very
>>>> >> embarrassing bug, and if there are any OpenBSD/sparc64 specific
>>>> >> problems, we shall also take care of that together.
>>>> >> We'd very much like chan-sccp-b to be portable and well behaving on
>>>> >> any platform.
>>>> >>
>>>> >> Thanks for joining us,
>>>> >> -David.
>>>> >>
>>>> >> On 25.02.2010, at 08:54, Ryan wrote:
>>>> >>
>>>> >>> I am getting the following error trying to connect my 7906G to
>>>> >>> Asterisk 1.4.25.1 on OpenBSD (sparc64) using the v2 trunk from
>>>> >>> subversion. I am trying to get SCCP working and this is the only
>>>> >>> device I have so far.
>>>> >>>
>>>> >>> ......
>>>> >>>  -- SCCP channel driver up and running on 192.168.4.7:2000
>>>> >>>  -- SCCP listening on 192.168.4.7:2000
>>>> >>>  -- SCCP: Looking for 'message/text' in the devices list
>>>> >>> ......
>>>> >>> == Using SCCP TOS bits 96
>>>> >>>  -- SCCP: Accepted connection from 192.168.4.186
>>>> >>>  -- SCCP: Using ip 192.168.4.7
>>>> >>> [Feb 25 00:48:41] WARNING[22298]: sccp_socket.c:70 sccp_read_data:
>>>> >>> SCCP: read() returned 240, wanted 33871: Input/output error
>>>> >>>  -- SCCP: Old session marked down
>>>> >>>
>>>> >>> The phone just spins on registering, any thoughts?
>>>> >>>
>>>> >>> Cheers,
>>>> >>> -R
>>>> >>> ------------------------------------------------------------------------------
>>>> >>> Download Intel&#174; Parallel Studio Eval
>>>> >>> Try the new software tools for yourself. Speed compiling, find bugs
>>>> >>> proactively, and fine-tune applications for parallel performance.
>>>> >>> See why Intel Parallel Studio got high marks during beta.
>>>> >>> http://p.sf.net/sfu/intel-sw-dev
>>>> >>> _______________________________________________
>>>> >>> Chan-sccp-b-discussion mailing list
>>>> >>> Cha...@li...
>>>> >>> https://lists.sourceforge.net/lists/listinfo/chan-sccp-b-discussion
>>>> >>
>>>> >>
>>>> >> ------------------------------------------------------------------------------
>>>> >> Download Intel&#174; Parallel Studio Eval
>>>> >> Try the new software tools for yourself. Speed compiling, find bugs
>>>> >> proactively, and fine-tune applications for parallel performance.
>>>> >> See why Intel Parallel Studio got high marks during beta.
>>>> >> http://p.sf.net/sfu/intel-sw-dev
>>>> >> _______________________________________________
>>>> >> Chan-sccp-b-discussion mailing list
>>>> >> Cha...@li...
>>>> >> https://lists.sourceforge.net/lists/listinfo/chan-sccp-b-discussion
>>>> >
>>>> >
>>>> > ------------------------------------------------------------------------------
>>>> > Download Intel&#174; Parallel Studio Eval
>>>> > Try the new software tools for yourself. Speed compiling, find bugs
>>>> > proactively, and fine-tune applications for parallel performance.
>>>> > See why Intel Parallel Studio got high marks during beta.
>>>> > http://p.sf.net/sfu/intel-sw-dev
>>>> > _______________________________________________
>>>> > Chan-sccp-b-discussion mailing list
>>>> > Cha...@li...
>>>> > https://lists.sourceforge.net/lists/listinfo/chan-sccp-b-discussion
>>>> 
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> Download Intel&#174; Parallel Studio Eval
>>>> Try the new software tools for yourself. Speed compiling, find bugs
>>>> proactively, and fine-tune applications for parallel performance.
>>>> See why Intel Parallel Studio got high marks during beta.
>>>> http://p.sf.net/sfu/intel-sw-dev
>>>> _______________________________________________
>>>> Chan-sccp-b-discussion mailing list
>>>> Cha...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/chan-sccp-b-discussion
>>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> Download Intel&#174; Parallel Studio Eval
>>> Try the new software tools for yourself. Speed compiling, find bugs
>>> proactively, and fine-tune applications for parallel performance.
>>> See why Intel Parallel Studio got high marks during beta.
>>> http://p.sf.net/sfu/intel-sw-dev_______________________________________________
>>> Chan-sccp-b-discussion mailing list
>>> Cha...@li...
>>> https://lists.sourceforge.net/lists/listinfo/chan-sccp-b-discussion 
>> 
>> ------------------------------------------------------------------------------
>> Download Intel&#174; Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________ Chan-sccp-b-discussion mailing list Cha...@li... https://lists.sourceforge.net/lists/listinfo/chan-sccp-b-discussion
> 
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev_______________________________________________
> Chan-sccp-b-discussion mailing list
> Cha...@li...
> https://lists.sourceforge.net/lists/listinfo/chan-sccp-b-discussion