linphone-users
[Top][All Lists]
Advanced

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

Re: [Linphone-users] Calls immediately terminated when destination picks


From: Alastair Johnson
Subject: Re: [Linphone-users] Calls immediately terminated when destination picks up
Date: Mon, 21 Jun 2010 22:32:49 +0100
User-agent: KMail/1.12.4 (Linux/2.6.31-gentoo-r6; KDE/4.3.5; x86_64; ; )

On Monday 21 June 2010, Tim Crews wrote:
> Hello:
> 
> We are running linphone on Windows 7 32-bit.  We are using a sequence of
> linphonecsh commands to initiate a phone call to a Cisco phone, by way
> of a Cisco CallManager server.  For example:
> 
> linphonecsh init
> linphonecsh dial sip:address@hidden
> 
> The phone at extension 6875 rings, as desired.  However, when that phone
> is answered, the call is immediately terminated without any explanation
> that is apparent on the client side.  This also happens with the GUI
> client.  It happens using several different PCs to initiate the call.
> 
> If we use linphonec instead, with verbose logging turned on, e.g.
> 
> linphonec -l log.txt -s sip:address@hidden -S -d 6
> 
> we get exactly the same behavior.  It is not obvious to me from the log
> data (see below) why the call is being terminated.  The only warning
> that is logged has to do with missing video.  This is an audio-only call.
> 
> Can you provide any pointers on what we are doing wrong in setting up
> the phone calls?

I may have missed something, but looks to me like the other end is hanging up 
the call after connection. linphone receives a BYE from the other end, and 
acknowledges it. The other end gives "Reason: Q.850;cause=172" but a cursory 
search for ITU-T Q.850 suggests the cause codes don't go beyond 127. Perhaps 
Cisco can tell you what cause 172 is.

It may be worth capturing the actual network traffic as well as the linphone 
log in case there's a processing error.

> Thanks in advance for any help you can provide.
> 
> Tim Crews
> 
> -------------------------------
> 
> Here is the log file.  I hope it is not against list etiquette to post a
> 300-line log file.  I didn't see any advice against it.

[snipped most of the log]

> ortp-message-Received message:
> BYE sip:address@hidden:5060 SIP/2.0
> Via: SIP/2.0/UDP 192.168.24.240:5060;branch=z9hG4bKC3742213
> From: <sip:address@hidden>;tag=A941D3C-270A
> To: <sip:address@hidden>;tag=7487
> Date: Mon, 21 Jun 2010 18:56:26 GMT
> Call-ID: 2656
> User-Agent: Cisco-SIPGateway/IOS-12.x
> Max-Forwards: 70
> Timestamp: 1277146586
> CSeq: 101 BYE
> Reason: Q.850;cause=172
> Content-Length: 0
> 
> 
> ortp-message-Message received from: 192.168.24.240:57022
> ortp-message-Message received from: 192.168.24.240:57022
> ortp-message-MESSAGE REC. CALLID:2656
> ortp-message-Message received from: 192.168.24.240:57022
> ortp-message-This is a request
> ortp-message-allocating transaction ressource 3 2656
> ortp-message-allocating NIST context
> ortp-message-cb_rcvunkrequest (id=3)
> ortp-message-cb_rcv? (id=3)
> ortp-message-DNS resolution with 192.168.24.240:5060
> ortp-message-getaddrinfo returned the following addresses:
> ortp-message-192.168.24.240 port 5060
> ortp-message-Message sent: (to dest=192.168.24.240:5060)
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP 192.168.24.240:5060;branch=z9hG4bKC3742213
> From: <sip:address@hidden>;tag=A941D3C-270A
> To: <sip:address@hidden>;tag=7487
> Call-ID: 2656
> CSeq: 101 BYE
> User-Agent: Linphone/3.3.1 (eXosip2/3.3.0)
> Content-Length: 0



reply via email to

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