487 Request Cancelled -- Dropped Calls

Status
Not open for further replies.

selarton

Forum User
Joined
Aug 26, 2019
Messages
1
Reaction score
0
Hello everybody,

I'm experiencing an issue across my network at several different locations with calls dropping and at times one way audio.
Below are the logs from an example dropped call. These issues also only seem to happen when phone calls are received.
Any help is greatly appreciated. Thanks!

Code:
08/26/2019 9:55:09 AM - Leg L:203.1[Extn:6100] is terminated: Cause: CANCEL from 10.11.16.110:5060
08/26/2019 9:55:06 AM - L:204.1[Line:10006<<PHONENUMBER] target's endpoint Extn:6100 is Busy
08/26/2019 9:55:06 AM - [Flow] Target endpoint for 6100 is Extn:6100
08/26/2019 9:54:42 AM - Leg L:202.3[Extn:6100] is terminated: Cause: 487 Request Cancelled/INVITE from 10.11.16.110:5060
08/26/2019 9:54:40 AM - [CM503025]: Call(C:203): Calling T:Line:10005>>PHONENUMBER@[Dev:sip:[email protected]:5060] for L:203.1[Extn:6100]
08/26/2019 9:54:40 AM - [CM503027]: Call(C:203): From: Extn:6100 ("" <sip:[email protected]:5060>) to T:Line:10006>>PHONENUMBER@[Dev:sip:[email protected]:5060]
08/26/2019 9:54:40 AM - [CM503004]: Call(C:203): Route 2: from L:203.1[Extn:6100] to T:Line:10006>>PHONENUMBER@[Dev:sip:[email protected]:5060]
08/26/2019 9:54:40 AM - [CM503027]: Call(C:203): From: Extn:6100 ("" <sip:[email protected]:5060>) to T:Line:10005>>PHONENUMBER@[Dev:sip:[email protected]:5060]
08/26/2019 9:54:40 AM - [CM503004]: Call(C:203): Route 1: from L:203.1[Extn:6100] to T:Line:10005>>PHONENUMBER@[Dev:sip:[email protected]:5060]
08/26/2019 9:54:40 AM - Call(C:203): Call from Extn:6100 to PHONENUMBER matches outbound rule 'Out_10_Compass'
08/26/2019 9:54:40 AM - [Flow] Call(C:203): has built target endpoint: Out#:>>Rule{Out_10_Compass}>>PHONENUMBER for call from L:203.1[Extn:6100]
08/26/2019 9:54:40 AM - [CM503010]: Call(C:203): Making route(s) from Extn:6100 to <[email protected]:5060>
08/26/2019 9:54:40 AM - [CM505001]: Endpoint Extn:6100: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Yealink SIP-T46S 66.83.0.55 001565c8c51a] PBX contact: [sip:[email protected]:5060]
 
Hi @selarton

Can you give some more information about your setup? (see link above by @aws2p)

And also a better description of the issue? (ie. call drops when making outgoing call or maybe incoming call or extension to extension etc)
 
A "487 request terminated" can be what a UAS will send to the client after the client sends a CANCEL request for the original unanswered INVITE request.

Translated this could easily be when a call has taken place but the destination user has "Cancelled" the call before a session has been established, often seen when you have a call queue/group (an agent picks up and the call is cancelled to the other users of the group).

I cannot say without more information as to your particular issue, but can say in regards to the 487 code that it can often be a red herring.
 
Status
Not open for further replies.

Forum statistics

Threads
111,933
Messages
589,810
Members
164,808
Latest member
jsbjsb