linphone-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Linphone-users] URGENT help


From: Karthikeyan S
Subject: RE: [Linphone-users] URGENT help
Date: Wed, 12 Jun 2002 17:36:36 +0530

Hi simon,

I tried with that dummy bitio.c.IT got compiled , thanx for that.
So with 0.8.8 Linphone I tested the robot (sipomatic). But suddenly Linphone
got crashed.
I am attaching the debug report.

#############
Script started on Wed Jun 12 17:43:53 2002
]0;address@hidden: /home/ngnsip/address@hidden Linphone]$
linphone
L3 -1023884042- <osipua.c: 59> info: Starting osip stack and osipua layer.
L4 -1023884042- <udp.c: 75> info: Entering osipua thread.
Xlib: connection to ":0.0" refused by server Xlib: Client is not authorized
to connect to Server
Gtk-WARNING **: cannot open display: :0
]0;address@hidden: /home/ngnsip/address@hidden Linphone]$ su
Password:
]0;address@hidden: /home/ngnsip/address@hidden Linphone]# linphone
L3 -1023884057- <osipua.c: 59> info: Starting osip stack and osipua layer.
L4 -1023884057- <udp.c: 75> info: Entering osipua thread.
Found 2 interfaces.
Found eth0 interface with ip address 10.4.7.241

GnomeUI-WARNING **: Could not open help topics file NULL
Adding <sip:address@hidden> to the list of alias.
Added payload type 3 3 gsm/8000/1
Added payload type 115 115 lpc10-15/8000/1
Added payload type 8 8 pcma/8000/1
Added payload type 0 0 pcmu/8000/1
Acceptable blocksize for query (2048) is 2048
 dsp opened.
SUB_DIVIDE said error=-1,errno=22
SUB_DIVIDE said error=0,errno=22
Warning: dsp block size set to 16384.
blocksize is 16384.
L3 -1023884082- <osipmanager.c: 137> info: port already listened
Added payload type 3 3 gsm/8000/1
Added payload type 115 115 lpc10-15/8000/1
Added payload type 8 8 pcma/8000/1
Added payload type 0 0 pcmu/8000/1
state=0
L3 -1023884088- <sdp_rfc2327.c: 1309> The rfc2327 says there should be at
least an email or a phone header!- anyway, we don't mind about it.
L3 -1023884088- <transaction.c: 34> INFO: allocating transaction ressource 1
1215320193
L3 -1023884088- <ict.c: 31> INFO: allocating ICT context
L3 -1023884088- <transaction.c: 209> sipevent evt->transactionid: 1
L3 -1023884088- <transaction.c: 210> sipevent tr->state: 0
L3 -1023884088- <transaction.c: 211> sipevent evt->type: 16
L3 -1023884088- <transaction.c: 212> sipevent evt->sip: 811b388
L2 -1023884088- <udp.c: 192> Sending message:
INVITE sip:address@hidden:5064 SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5060
From: <sip:address@hidden>;tag=34137 To: <sip:address@hidden:5064> Call-ID:
address@hidden CSeq: 1 INVITE Contact: <sip:address@hidden>
user-agent: oSIP/Linphone-0.8.0 Content-Type: application/sdp
Content-Length: 222    v=0 o=root 123456 654321 IN IP4 127.0.0.1 s=A
conversation c=IN IP4 127.0.0.1 t=0 0 m=audio 7077 RTP/AVP 3 115 8 0
a=rtpmap:3 gsm/8000/1 a=rtpmap:115 lpc10-15/8000/1 a=rtpmap:8 pcma/8000/1
a=rtpmap:0 pcmu/8000/1 L2 -1023884088- <udp.c: 159> info: RECEIVING UDP
MESSAGE:
SIP/2.0 100 Trying via: SIP/2.0/UDP 127.0.0.1:5060 from:
sip:address@hidden;tag=34137 to: sip:address@hidden:5064 cseq: 1 INVITE
call-id: address@hidden user-agent: oSIP/Linphone-0.4.2
content-length: 0
L3 -1023884088- <transaction.c: 243> sipevent evt: method called!
L3 -1023884088- <transaction.c: 209> sipevent evt->transactionid: 1
L3 -1023884088- <transaction.c: 210> sipevent tr->state: 1
L3 -1023884088- <transaction.c: 211> sipevent evt->type: 13
L3 -1023884088- <transaction.c: 212> sipevent evt->sip: 810e040
L1 -1023884088- <ict_callbacks.c: 41> OnEvent_New_Incoming1xxResponse!
invite state=1
L3 -1023884088- <transaction.c: 243> sipevent evt: method called!
L2 -1023884088- <udp.c: 159> info: RECEIVING UDP MESSAGE:
SIP/2.0 180 Ringing via: SIP/2.0/UDP 127.0.0.1:5060 from:
sip:address@hidden;tag=34137 to: sip:address@hidden:5064 cseq: 1 INVITE
call-id: address@hidden contact: sip:address@hidden:5064 user-agent:
oSIP/Linphone-0.4.2 content-length: 0
L3 -1023884088- <transaction.c: 209> sipevent evt->transactionid: 1
L3 -1023884088- <transaction.c: 210> sipevent tr->state: 2
L3 -1023884088- <transaction.c: 211> sipevent evt->type: 13
L3 -1023884088- <transaction.c: 212> sipevent evt->sip: 8113168
L1 -1023884088- <ict_callbacks.c: 41> OnEvent_New_Incoming1xxResponse!
Acceptable blocksize for query (2048) is 2048
 dsp opened.
SUB_DIVIDE said error=-1,errno
#############

sipomatic debug report ##############
L3 -1023883661- <osipua.c: 59> info: Starting osip stack and osipua layer.
L0 -1023883661- <osipmanager.c: 152> error: Failed to bind socket !
L4 -1023883661- <udp.c: 75> info: Entering osipua thread.
################

Pls provide me ur directions on this and gimme ur guidelines to run the
sipomatic test. I used
sip:address@hidden:5064 and lo as the interface. Is there i need to make.

thanx and regds
karthik



-----Original Message-----
From: Simon Morlat [mailto:address@hidden
Sent: Tuesday,June 11, 2002 8:01 PM
To: address@hidden
Cc: address@hidden
Subject: RE: [Linphone-users] URGENT help


Sorry:
try to replace bitio.c by a stupid program:
"void main(){}" > bitio.c

Concerning sound card problems, check that you have no other application
using it while linphone is calling. You are welcomed to toggle the
button called "kill application using sound card when necessary" in the
property box, section sound.



Le mar 11/06/2002 à 15:28, Karthikeyan S a écrit :
> Hai,
>
> UR right i was using the 0.4.2 version. That is because i still got the
> problem of bitio.c
> which i got in 0.8.0.
>
> Also pls tell me of possible sound card access problems and how to avoid
it.
>
> thanx and regds
> karthik
>
>
> -----Original Message-----
> From: Karthikeyan S [mailto:address@hidden
> Sent: Tuesday,June 11, 2002 6:53 PM
> To: 'Simon Morlat'
> Cc: 'address@hidden'
> Subject: RE: [Linphone-users] URGENT help
>
>
> hai,
>
>
> -----Original Message-----
> From: Simon Morlat [mailto:address@hidden
> Sent: Tuesday,June 11, 2002 5:47 PM
> To: address@hidden
> Cc: address@hidden
> Subject: RE: [Linphone-users] URGENT help
>
>
> Le mar 11/06/2002 à 06:39, Karthikeyan S a écrit :
> > hai Simon,
> >
> > First of all thanx for ur directions.
> > I am now using the latest 0.8.0 as u said and i tried to compile.
> > It gives the following error while compiling
> >
> > make[1]: Entering directory
> `/home/ngnsip/Linphone/linphone-0.8.0/lpc10-1.5'
> > /bin/sh ../libtool --mode=link gcc  -g -O2 -Wall -Wunused  -w   -o bitio
> > bitio.o liblpc10.la
> > gcc -g -O2 -Wall -Wunused -w -o bitio bitio.o  ./.libs/liblpc10.al -lm
> > bitio.o: In function `g_error':
> > /usr/include/glib-1.2/glib.h:1328: undefined reference to `g_logv'
> > bitio.o: In function `g_message':
> > /usr/include/glib-1.2/glib.h:1337: undefined reference to `g_logv'
> > bitio.o: In function `g_warning':
> > /usr/include/glib-1.2/glib.h:1346: undefined reference to `g_logv'
> > collect2: ld returned 1 exit status
> > make[1]: *** [bitio] Error 1
> > make[1]: Leaving directory
> `/home/ngnsip/Linphone/linphone-0.8.0/lpc10-1.5'
> > make: *** [install-recursive] Error 1
>
> Strange error: it does not show here, probably because of difference in
> compilers. It is fixed for next version, however to avoid it, please do
> the following:
> in lpc10-1.5/ directory
> rm bitio.c
> touch bitio.c
> The error occurs when compiling bitio.c, that is not a required program
> for linphone (it was just for basic testing, a long time ago.
> I hope this workaround will work.
>
> No simon its not working its reports the following
>
> /bin/sh ../libtool --mode=link gcc  -g -O2 -Wall -Wunused  -w   -o bitio
> bitio.o liblpc10.la
> gcc -g -O2 -Wall -Wunused -w -o bitio bitio.o  ./.libs/liblpc10.al -lm
> /usr/lib/gcc-lib/i386-redhat-linux/2.96/../../../crt1.o: In function
> `_start':
> /usr/lib/gcc-lib/i386-redhat-linux/2.96/../../../crt1.o(.text+0x18):
> undefined reference to `main'
> collect2: ld returned 1 exit status
> make[2]: *** [bitio] Error 1
> make[2]: Leaving directory
`/home/ngnsip/Linphone/linphone-0.8.0/lpc10-1.5'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/ngnsip/Linphone/linphone-0.8.0'
> make: *** [all] Error 2
>
>
>
> > The problem which i reported yesterday is on version 0.7.1 with libosip
> > version 0.7.8
> > The machine has RH 7.1 installed with Intel i810  82801AA Ac'97 audio
> sound
> > card.
> > Now i tried to test the sipomatic with the currect configuration. I got
> the
> > following debug output after Linphone got connected with sipomatic
robot.
> >  U can c the ACK)
> > I used address@hidden:5064 and lo as the interface.
> >
> > L0 -1023770307- SND ACK f:sip:address@hidden t:sip:address@hidden:5064
> cseq:1
> > callid:515640063
> > L1 -1023770307- <callback.c> OnEvent_New_OutgoingAck!
> > L3 -1023770307- <trn_manager.c> method called: 81158a0
> > Lost (or Only -1 bytes written.
> > Lost (or Only -1 bytes written.
> > Lost (or lateOnly -1 bytes written.
> > Lost (or late) Only -1 bytes written.
> > Lost (or late) paOnly -1 bytes written.
> > Lost (or late) pacOnly -1 bytes written.
> > Lost (or late) packeOnly -1 bytes written.
> > Lost (or late) packetsOnly -1 bytes written.
> > Lost (or late) packets:Only -1 bytes written.
> > Lost (or late) packets: 5Only -1 bytes written.
> > Lost (or late) packets: 562Only -1 bytes written.
> > Lost (or late) packets: 593 Only -1 bytes written.
> > Lost (or late) packets: 655   Only -1 bytes written.
> > Lost (or late) packets: 717     Only -1 bytes written.
> > Only -1 bytes written.: 748
> > LoOnly -1 bytes written.810
> > LosOnly -1 bytes written.41
> > Lost Only -1 bytes written.
> > L4 -1023770318- <udp_listen.c> RCV MESSAGE ON UDP!
> > BYE sip:address@hidden SIP/2.0
> > via: SIP/2.0/UDP 127.0.0.1:5064
> > from: sip:address@hidden
> > to: sip:address@hidden
> > cseq: 1 BYE
> > call-id: address@hidden
> > contact: sip:address@hidden
> > user-agent: oSIP/Linphone-0.4.2
> > content-length: 0
> >
> !!!!!!!!!
> user-agent: oSIP/Linphone-0.4.2
> !!!!!!!!!
> Are you sure you are using linphone-0.7.1 ? I'm a bit suprise with this
> sip message. Are you sure you have not an older version of linphone
> installed somewhere ?
> Please check that.
>
> Ok i will check that. Thanx
>
> Finally, the -1 bytes written are related to a sound device access
> problem. But before investigating more, please check your linphone's
> version.
> The best thing is to use 0.8.0.
>
> Ok i will use the same but pls provide me an alternative for bitio.c error
>
> thanx and regds
> karthik
>
>
>
>
>
***************************************************************************
> This message is proprietary to Future Software Limited (FSL)
> and is intended solely for the use of the individual to whom it
> is addressed. It may contain  privileged or confidential information
> and should not be circulated or used for any purpose other than for
> what it is intended.
>
> If you have received this message in error, please notify the
> originator immediately. If you are not the intended recipient,
> you are notified that you are strictly prohibited from using,
> copying, altering, or disclosing the contents of this message.
> FSL accepts no responsibility for loss or damage arising from
> the use of the information transmitted by this email including
> damage from virus.
>
***************************************************************************
>
> _______________________________________________
> Linphone-users mailing list
> address@hidden
> http://mail.freesoftware.fsf.org/mailman/listinfo/linphone-users
>


***************************************************************************
This message is proprietary to Future Software Limited (FSL) 
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information 
and should not be circulated or used for any purpose other than for 
what it is intended. 

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message. 
FSL accepts no responsibility for loss or damage arising from 
the use of the information transmitted by this email including
damage from virus.
***************************************************************************



reply via email to

[Prev in Thread] Current Thread [Next in Thread]