Solved Yealink T48s does not answer calls

[Hawhoo]

HI
I just got a brand new t48s Auto provisioned and firmware at 66.81.0.61 (version approved by 3CX / not the latest)
outgoing: works fine
incoming: the phone flashes the caller info and than issues a cause:487 to the pbx
I do not understand the 1st two lines (127.0.0.1)
05/15/2017 12:21:10 PM - [CM503003]: Call(C:173): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488
05/15/2017 12:21:10 PM - [CM503003]: Call(C:173): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Terminated/INVITE from 127.0.0.1:5488
05/15/2017 12:21:10 PM - [CM503003]: Call(C:173): Call to <sip:[email protected]:5060> has failed; Cause: 487 Request Cancelled/INVITE from x.x.x.x.:5060

Any Ideas

 

[lneblett]

The log is basically indicating that the system, not the phones, cancelled the call. This is usually indicative of a call going to multiple extensions in a ring all scenario and a) the caller hung-up, b) the call was answered by others or c) the call got diverted to another destination (timeout for example, then to VM). The cancel causes the phones to quit ringing. In your case, there appears to be multiple instances of extension 1112. I assume the blanked out IPs are local, which means no risk in posting, but you may need to check the phone and see how many lines are set to the same 1112 and if the extension is set to handle more than one call at a time. If you look further into the logs for call 173, it may reveal more of what happened to the call.

 

[Hawhoo]

Ineblett, yes you are correct the Ring goes to Two phone T46G and the new T48s ( and rings a cell simultaneously).
The T48s replaced a T38G which worked flawless in this scenario.
I disconnected the T46G with identical results
The T38G ->T48s and 3CX upgrade from 15.3 to 15.5 happened at the same time so maybe not a T48s issue after all I'll disable the cellphone simultaneous ring and dig a bit deeper. Thanks for you input

 

[Hawhoo]

Fixed I Had a W52P connected to this line as well (auto provisioned ) but no headset was assigned to the configured line so the W52p must have issues the disconnect request!

 

[YiannisH_3CX]

Glad the issue is resolved and thank you for sharing your solution