linphone-developers
[Top][All Lists]
Advanced

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

Re: [Linphone-developers] commit c5b17b4aa388c6d3b0b14e8ac96fe1b9a07ce2f


From: Peter Meerwald
Subject: Re: [Linphone-developers] commit c5b17b4aa388c6d3b0b14e8ac96fe1b9a07ce2f7 (fwd)
Date: Tue, 23 Mar 2010 16:18:35 +0100 (CET)
User-agent: Alpine 2.00 (DEB 1167 2008-08-23)

Hello Simon, 

> There is something I don't understand, please tell me:
> Normally 487 should come after a CANCEL, that is sent by
> linphone_core_terminate_call(). However linphone_core_terminate_call()
> sets the state GSTATE_CALL_ENDED.
> So how could GSTATE_CALL_OUT_INVITE stay forever ?

I'm directly calling a Grandsteam GXV-3000 on the local network, no 
proxies involved; I just don't pick up the call and wait...

$ ./linphonec -S
GSTATE_POWER_STARTUP
GSTATE_POWER_ON
Warning: video is disabled in linphonec, use -V or -C or -D to enable.
linphonec> call sip:address@hidden
Contacting <sip:address@hidden>
linphonec> GSTATE_CALL_OUT_INVITE sip:address@hidden
linphonec> Remote ringing.
Request Cancelled.
linphonec>

I do get a 'CALL_REQUESTFAILURE or GLOBALFAILURE or SERVERFAILURE', so 
linphone_call_failure() is called, not linphone_call_terminated()

my IP is 192.168.233.53; the communication is as follows:

.53 -> .108: SIP/SDP Request: INVITE
.108 -> .53: SIP Status 100: Trying
.108 -> .53: SIP Status 180: Ringing
after some time
.108 -> .53: SIP Status 487: Request Cancelled
.53 -> .108: SIP Request: ACK

and state is still GSTATE_CALL_OUT_INVITE 



if I call via Asterisk, everything is OK:

linphonec> call sip:address@hidden
Contacting <sip:address@hidden>
linphonec> GSTATE_CALL_OUT_INVITE sip:address@hidden
linphonec> Remote ringing.
Service Unavailable
linphonec> GSTATE_CALL_ERROR
GSTATE_CALL_IDLE

regards, p.

-- 

Peter Meerwald
Kaigasse 3 / 8
A-5020 Salzburg / AUSTRIA
+43-664-2444418 (mobile)




reply via email to

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